- All the features of ArduPilot 2.0 plus...
- Supports XY sensor in diagonal postion
- Requires Z sensor [UPDATE: FMA is no longer carrying those. While we sort out alternative sources, you can buy them from Dean Goedde for $40 (scroll down for price list)
- Controls throttle if airspeed sensor is attached via the ArduPilot expansion board.
- Supports desktop setup utility for waypoints and autopilot settings. (Waypoints are no longer manually entered in the code. They can only be entered with this utility.)
- Last version of the code to support the original ATMega168-based board. Future versions will require the new ATMega328-based board.
- Field setup procedures are here
- Get it here
- Add waypoints manually; utility displays them on Google Maps
- Set max altitude, speed, circle radius
- Set elevator, aileron/rudder trim
- More features coming
- Get it here ("ArduPilotConfigUtility")
- Requires free Labview runtime engine and serial drivers (install both. Note: if you've already installed Lego's Mindstorms NXT software you may find you've got a driver conflict, because it's based on LabView, too. Uninstall the Mindstorms software first.)
- Works with Xbee wireless modules
- Displays real-time attitude, speed, altitude, current waypoint, heading, distance to next waypoint, etc
- Displays real time position on Google Earth
- Get it here
- Source code is here
Comments
What version of Ardupilot are you using? If you are using 2.2.3, then the baud rate should be 57.6k baud. If you are using 1.0, then it should be 9.6k baud.
Regards,
TCIII
Is the FTDI connected and is the ardupilot powered up ?
If so go to realterminal, and set the baud rate to 9600....power off the ardupilot, and power it on. Connect to the com port that real terminal has enabled for the ftdi.
You should start seeing information, if it looks chinese then the baud rate is wrong. So try 56,700 and keep changing the baud rate until you get data coming out the terminal....
Google earth needs telemetry via its temp .kml communicating to the ardupilot. This is normally done via xbees connected to the ardupilot and the Ground station PC. Unless you develop your own .kml in google earth to communicate with another type of source, possibly the FTDI but I am not sure that would work.
Did you bind them to same ID, same baud rate ?
In the GCS click com port, does your com port show up properly.
How are you hooking up the ardupilot to the xbees ? with adafruit adapter ?
More info will help diagnose your problem...
-Peter