Demo today at 3:50. The code works (finished it last night, and the report), but demos are always tricky. We shall see. My research also progresses at a rapid clip. I need to have a PCB design done in 2 weeks (!). No rest for the weary I suppose...
.
From:
no subject
or
"Please summarize your project in no more than one paragraph"
From:
no subject
We had to accomplish all of these things while preserving a scheduler clock cycle of 1 ms. We wrote a simple task to drive an output high when the scheduler was idle. We had about 50% idle time, which was significantly better than several other groups. :)
The webpage is here (http://brl.ee.washington.edu/Education/EE472/), and a pdf of the lab manual (if you're feeling excited) is here (http://brl.ee.washington.edu/Education/EE472/lab/CC_Lab.pdf).
From:
no subject
I keep thinking about how to do it for real, not always applicable in classes, I know.
are they throwing varied loads (hills and wind gusts) at you too?
I never got far in electronics- more of a hobby. I do remember finding a book one time in the library that had a whole section dedicated to automotive circuits. I copied the solid state sequential turn signals, and had it on my car until the board started to decay, after about 4 years. I need to find the diagram again, so I can do it better.
From:
no subject
Anyway yeah, they'll be applying varying loads to the electric motor we're using (this is just a simulation, but from a sytems point of view it acts very similarly to the real deal). The actual cruise control algorithm is pretty straightforward... The real hard part is fitting it all in to this tiny underpowered machine and still have it run with what looks like no latency.
It's quite interesting, though a huge amount of work.