I'm reviewing the code whilst finishing off on the last details on the APM (voltage monitor, xbee connection, etc.) . I noticed that the APM makes rather heavy use of the eeprom also in flight.
From what I gather, the eeprom is written to after calibration to store the radio min/max, IMU calibrated values and so forth. This is to allow an "airstart" afterwards.
Can somebody explain to me what this "airstart" really is and what it was intended for? It looks like something to do with 'in-air restart/reboot recovery'. I'd like to understand the concerns here, it doesn't look like it is something to do with flying a bit, shutting down, driving somewhere else and just throwing the plane back up again. It seems more related to a recovery from a power failure or reboot in the air. Can someone explain why the airstart was designed in like this?
I believe also that a different waypoint upload mechanism may be used. Will the code that uses the eeprom go into the final version? If yes, would a patch be accepted that turned off these features based on some #define in APM_Config.h?
You need to be a member of diydrones to add comments!
Replies
Air Start has saved me from a crash on multiple occasions with ArduPilot.
A different waypoint upload mechanism from what? The Waypoint Writer tool? That is just the first tool made available. There will be others, and there are a variety of ways they can operate.