Yeah. But let’s say:
I am controlling the robot. Because of some kindda strange way the joypad gets disconnected. The last variables are stored, so the robot might move without a joypad. While I am struggling to get the robot respond again, the robot might get damaged.
It would be better to have a routine checking for a joypad, and disabling it’s actions while disconnected?
So what’s the disadvantage of using a timer?
It uses a lot of memory… 
I’ve already got 2 timers. 1 for the data input of the joypad and 1 for the serial communication and the variables.
I will have a look how much memory it uses while running 2 timers.
Hmm… it uses only 5.428 K of memory in the task manager. (stable, no peaks) so that is pretty nice. :mrgreen: Maybe I could use a timer for this then 8)
Also, my powersupply should arrive today. I can’t wait to program the movements 8)
The power supply arrived! So I’ve had some fun with body movements 8)
Check it out:
http://www.plaatjesupload.nl/bekijk/2009/10/20/1256042254-290.jpg
Stay tuned 8)
Hello there!
Thought it would be a good idea to keep you guys informed about the progress.
Currently working on a multi-thread application. This makes me able to control several actions via a background thread. I’m planning on running the robot almost completely via this thread.
Also, the joypad thing comes to life piece-by-piece. It should be able to control the robot via this soon.
Stay tuned for progress. 8)
Little update:
I’m struggling very hard to get the threading to work. This is not good at all…
Keep tuned…
So, did you ever finish this piece of code?
I’m interested in adapting this to work with the nostromo n52 series gamepad, or one of the many joysticks that also have programmable features.
Any info would be great.
Thanks 
I would like to ask you some questions about your projects,im a webmaster searching for informations.
Can you help me?
