This post describes the beta version of BASIC Stamp autopilot code. As mentioned in my last post, the two main challenges in this project were dealing with the constraints of integer-only math and a severely restricted variable space (just 26 bytes!).
The first one I got around by treating fractional degrees as full degrees (since the UAV is never going to travel more than one full degree away from launch) and essentially treating them as integers. This was a little tricky, since I'm limited to word-length variables (with a max value of 65,535, which is essentially 4 and half digits of precision) and the GPS natively generates six and half digits of precision (360.9999 W/E). But I truncated the full degrees to just 1 and -1 from the current position, and that let me retain the full precision of the fractional degrees.
The second problem I got around by splitting the program up into five sub-programs (each one is allowed to reuse the variable space in RAM) and switching in real-time between them. I also used the Stamp chip's 121 bytes of "scratchpad" memory to store a lookup table of all the waypoints, and that's available to all the programs, although you can't manipulate the scratchpad memory directly without copying it into a variable.
The current program does three things:
- It intercepts R/C receiver commands to the rudder, elevator and gear switch and translates them into computer commands, which drive the servos through a Parallax servo board or FT639 chip. When it detects that the gear switch has been thrown, it transfers control of the rudder and elevator to the autopilot program, and back again when the switch is returned to its manual position.
- When under autopilot control, it reads GPS coordinates and headings and translates them into directional vectors to the next GPS waypoint. It uses those vectors to steer the rudder.
- It also uses GPS altitude readings to do a crude sort of altitude hold. Because the GSP altitude data is so noisy, the autopilot averages over three readings and treats that as accurate +- 10 meters. It uses that data to adjust the elevator to try to keep the plane within a range of +- 10 meters of the original altitude at which it was put into autopilot mode.
The code has been tested on several different kinds of servo driver chips and GPS modules, as well as with GPS simulators, but not yet in the air. So consider it just instructional at this point. I'm sure there are some bugs, and a lot of settings that need to be tweaked. Also, we have not yet added camera controls and other more sophisticated in-air options, such as circle and hold (although these aren't hard to add, not that we've got the basic hardware interfaces working).
You can download the code at the following link. Load the first program (uav.bsp) and it will call the others at compile and download time.
The recommended hardware is a Basic Stamp BS2p on a dev board using the FT639 servo driver chip and a standard GPS module such as the EM406. Details on these hardware configurations can be found in the main post on this UAV. Other servo drivers, such as the Parallax board can be used, and the details on how to modify the code for them is in the comments of the code
- Basic Stamp autopilot code. [Latest version]
Comments
You're right, I probably should be using the floating point co-processor. But I figured out how to get around that with the usual multiply-by-1000 trick and some standard approximations. So at the moment, I don't need it.
The Rx reading-and-retransmitting code is in the main UAV code. It looks like this:
PULSIN chan2in , HIpulse , chan2
chan2 = (chan2 */ scale)/2
DEBUG DEC chan2 ,TAB
SEROUT sdat, bauds+$8000,["!SC",ch2,ra,chan2.LOWBYTE,chan2.HIGHBYTE,CR]
I'm asking because I'm using it myself and I was wondering if there was a reason you WEREN'T using it, as opposed to not bothering to use it.
(Btw, I've been looking through your code and I can't find where you handle the commands from the Rx, which is something I've been trying to research lately)
I was checking the C code of oopic, and is very similar, but you need to adapt it. I think you gonna have no problems, try to understand the arduino language and then translate it to oopic, the only difference i saw was in the declaration, but the main code seems to be similar. Good Luck
I've never used on oopic board, so I don't know. If you do it and it works, could you get back to use with tricks and tips?
http://youtube.com/watch?v=7xkJseQyhJA
But im using a shipper arduino called boarduino, and i program it with arduino diecimila:
http://www.adafruit.com/index.php?main_page=product_info&cPath=...
https://www.youtube.com/watch?v=MD_-YnFZFP8
-
1
-
2
-
3
-
4
of 4 Next