Posted by Chris Anderson on December 12, 2007 at 10:44pm
Just a quick note to say that I've updated the code to both the GPS-based Lego autopilot and the compass-based Lego autopilot. The only major change is that the motor functions are more effecient and reliable. The old code reset the motor encoder with each turn and this was leading to some pretty serious drift after just a few turns. The new code uses a proportional turn algorithm that is not only more flexible but also eliminates drift. GPS-based LEGO autopilot code (RobotC)
You use a servo controller to drive the servos. I don't know of a good way to have NXT read RC commands--I just used a multiplexer to switch the servos between RC and NXT.
I followed up your articles on using LEGO for RC planes (I know I am referring to a 2 year old subject) I have a elementary question, its my lack of knowledge in this subject which has kept me from understanind whats already there in numerous places on the net.
I have a Tx-Rx Eclipse system and a Lego NXT and some motors. I know that LEGO NXT outout ports have PWM enabled and its pretty straight forward to drive motors/servos from it. But in an RC system how do I interface the RC receiver to LEGO .........so that what ever I transmit is finally delivered to motors through my LEGO?
I promise I will not bug with such elementrary Qs again.
Comments
I followed up your articles on using LEGO for RC planes (I know I am referring to a 2 year old subject) I have a elementary question, its my lack of knowledge in this subject which has kept me from understanind whats already there in numerous places on the net.
I have a Tx-Rx Eclipse system and a Lego NXT and some motors. I know that LEGO NXT outout ports have PWM enabled and its pretty straight forward to drive motors/servos from it. But in an RC system how do I interface the RC receiver to LEGO .........so that what ever I transmit is finally delivered to motors through my LEGO?
I promise I will not bug with such elementrary Qs again.
Thanks for your time.