|
Australia7069 Posts
So integrated systems fucking SUCK. Seriously. they fucking SUCK.
Its not like normal coding. you work out the syntax and functions that you need to use and lego that shit together. Run them, compare expected outputs vs actual and debug, ezpz.
no
fucking integrated shit. The code seems SO fucking simple. Its like, RECEIVE DATA, WIPE BUFFER, SEND DATA.
four FUCKING lines. DOESN"T WORK. i just get garbage. Fucking fuck fuck fuck. I go get someone elses code, that works perfectly for him, code it on my system and it doesn't fucking work. So we test every SINGLE fucking circuit point, and its all fine.
Its 11.30pm on saturday night, this is due 9am monday. And NOTHING WORKS
FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUCK
Not really sure what this blog is about i just really wanted to vent. Its so unfair because like, almost ALL our components work, eg: our accelerometer outputs properly to our ADC. our ADC outputs properly to the wireless transmitter. The wireless transmitter outputs properly to SOMEONE ELSES WIRELESS RECEIVER and/or a serial port. And then our fucking wireless receiver picks up fucking GARBAGE. So i try to send a '4' character through the system, and i get some CONSISTENT garbage, its still garbage but it basically repeats. So i'm like cool! i'll work out the pattern. So i try 5, get some different yet consistent garbage. and i'm like OK COOL PATTERN GOING ON i"LL JUST HARD CODE ALL THE POSSIBLE OUTPUTS. THEN I DO FUCKING 6 AND IT WONT EVEN PICK UP THE VIRTUAL COM PORT.
WHAT
THE
FUCK
  
|
Post your code? TL has a lot of really good programmers here. Oh yeah, and programming does suck like that a once in a blue moon.
|
Australia7069 Posts
i'm at home right now, came back to get some food. i'm going back in in about an hour i'll post it then. i dont think its really a code problem tho  its just fucked
|
|
|
The reason why its not simple is because your thinking makes it so. Its all perception.
|
United States24745 Posts
I have no experience with integrated systems but even from my rudimentary experience I know how frustrating coding can be when things just aren't working lol
|
Hyrule19178 Posts
Sounds like your receiver is borked. Get a new one? I'd say talk to your professor and explain that your hardware was giving unreliable and inconsistent results and that you haven't been able to complete the assignment properly. Most professors (especially in IS) will usually be like "okay, use this piece of hardware instead and have it done by Friday" or something.
|
PM R1CH offering him your firstborn.
Problem solved.
|
Australia7069 Posts
HOLY SHIT GUYS! i just got a call from one of my group members in the lab. he has the receiver outputting from the accelerometer kind of. Like its not changing properly, but thats fixable.
YES YES YES!!!!!!!!!!!!!!
Theres still a way to go! but if we get this working i'll upload pictures and/or video of how its going!
omg i'm so happy. i hope its still working when i get in in a couple of hours
omfgggggggggggggggggggggg
|
Canada7170 Posts
lol I've always wanted to post like this when things go wrong, I usually type it out and about halfway through ranting I feel a lot better so I don't post 
And it's always the hardware. Always.
|
On October 24 2010 00:23 mikeymoo wrote:lol I've always wanted to post like this when things go wrong, I usually type it out and about halfway through ranting I feel a lot better so I don't post And it's always the hardware. Always.
I took a "robotics" class and we had to build a simple/small circuit and then make a program (in assembly... fun stuff) where we have to output/count from 1-20.
it was the most PITA thing I've ever done. I wrote a program and nothing was making sense and I literally spent hours tearing my hair out trying to debug it. In the end it turns out that the equipment they give us is so fucking old that every other component is broken. Took us absolutely forever to debug.
|
TossFloss
Canada606 Posts
Whenever working directly with hardware, never assume it functions according to spec. I once took a course where we had to get trains running around a track. Only our old WYSE terminal worked properly.
|
Not sure if it's too late, but I'm 90% of the way through my Bachelor of Engineering (Mechatronics) in Australia and have some experience with integrated systems. Let me know if I can help somehow.
|
Man our breadboards were awful and would eff me up on every CompSci test. I got so fed up with our ancient faulty hardware I switched to Political Science and now I'm teaching myself useful compsci things.
|
On October 24 2010 04:39 Pyrrhuloxia wrote:
Man our breadboards were awful and would eff me up on every CompSci test. I got so fed up with our ancient faulty hardware I switched to Political Science and now I'm teaching myself useful compsci things.
What kind of things are you trying to teach yourself? I'm sort of curious as I want to start doing the same.
|
Haha, wait until you have the final projects class to deal with. Your school program must have one? That's when electronics integration gets to be an absolute fuckshow. Especially when your on a team of four people, two of which don't know their shit, yet somehow make it 4 years deep but still desperately try to help just to get some pathetic measure of peer evaluation marks.
Or the labs you will come across that you finally get to work perfectly the night before your demonstration is due, and the next day you hook everything up and nothing works.
Or the written tests where your given a 2 line description of a program your supposed to write in assembly or VHDL while being given a blank piece of paper, half an hour, and a metaphorical gun to your head.
end rant.
I'd like to say the trouble you explained... well, your now my brother. I feel for you hardcore man.
|
|
|
|
|
|
EPT
