Special thanks go to a number of people. Dick Swan, the creator of RobotC, was the first to create a Bluetooth interface to a GPS device. Steve Hassenplug created an excellent GPS parser for his Green Monster outdoor wheeled Lego robot and was kind enough to share the code. And Ralph Hempel, the creator of pbLua, helped a lot in the early stages of solving the Bluetooth interface problem. Although we ended up going with RobotC, not Lua, in the end, he showed the way.
Coming up next: I've got to tweak the code to work properly in the air, and film a demonstration using real-time telemetry and aerial video to show how well it follows its waypoints when under autopilot control. And after that? Well, we've got some prototype hardware the promises to remove the mechanical complexity of the Lego-to-control-surfaces problem entirely. It would also allow us to bring the elevator under autopilot control, allowing us to do a proper altitude hold. Finally, there's a possibility that we may be able to also do aircraft stabilization with Mindstorms using inertial sensors, which would allow us to eliminate the FMA Co-Pilot that we're currently using. I can't say more about this yet, because it's using unreleased hardware, but stay tuned.
We've only just begun!
Comments
Steve
thanks
p.s. your guys code is really good.
thanks
I tried using the beta code (uav2.c) you posted above on my brick. Quick question ... looking at the text of the code and on the fifth line it states
"const tSensors kCompass= (tSensors) S1;"
tried looking at the rest of the code and there's no reference to the compass sensor. So, is the fifth line code an artifact of the compass simulated GPS system you indicated in previous posting? I have no background on C or RobotC for that matter so an innocent question is will deleting the fifth line not affect the working of the code?
Thanks.