aboutsummaryrefslogtreecommitdiff
path: root/src/modules/dataman/dataman.h
Commit message (Collapse)AuthorAgeFilesLines
* dataman: added macro for offboard storage selectionAnton Babushkin2014-07-071-0/+2
|
* Move MISSION_STATE read/write from mavlink to navigator and commanderAnton Babushkin2014-06-131-11/+1
|
* dataman: rename SYSTEM_STATE section to MISSION_STATEAnton Babushkin2014-06-121-2/+2
|
* dataman: allow writing empty items with nullptr pointer to dataAnton Babushkin2014-06-091-1/+1
|
* Create system state entry in dataman - ATTN AntonJean Cyr2014-06-081-1/+25
| | | | | Create persistent system state id for data manager to store system state that will persist across resets.
* dataman: Fix doxygen, no functional changesLorenz Meier2014-05-151-10/+10
|
* Proper data manager restart handlingJean Cyr2014-04-281-2/+3
| | | | | | | | | | | Introduce SYS_RESTART_TYPE parameter having one of 3 values: boot restart, inflight restart, or unknown restart, and defaulting to unknown restart. px4io.cpp sets this parameter according to the type of restart detected. dataman.c retrieves this parameter and clears data entries according to their persistence level. Does nothing if unknown restart.
* Reduce data manager SD card wear and tearJean Cyr2014-04-221-1/+1
| | | | | | | | | | | | | | | | | | | | | When the data manager was first designed each file record contained a 2 byte header and an 126 byte data section, resulting in a record length of 128 bytes. Along the way it was decided to add 2 spare bytes to the record header, but regrettably the data section was not correspondingly reduced in size so we end up with a record length of 130 bytes. This is bad since it does not align with SD card flash sectors and results in more erase/write flash cycles than necessary thus reducing the SD cards life. This update reduced the data section of the data manager to 124, resulting in an optimal record length of 128 bytes. In order to avoid the reuse of data previously written data in the old format, which could result in catastrophic misinterpretation, the data manager file is checked at startup. If it is found to be in the old format, it is deleted and recreated with in the new record length. In this case previously stored data is lost, but that is far safer than the unpredictable result of using the old file.
* Waypoints/Navigator: Use two different dataman storage places, keep old ↵Julian Oes2013-12-251-2/+4
| | | | waypoints until all new ones are written
* Datamanager: Rename mavlink/offboard keyJulian Oes2013-12-161-2/+2
|
* Dataman: Also reserve space for onboard missionsJulian Oes2013-12-161-2/+4
|
* Dataman: Some minor fixesJulian Oes2013-12-031-3/+2
|
* Add data manager module and fence support to navigatorJean Cyr2013-11-031-0/+116
- Add function to geo.c to determine if global position is inside fence - Add navigator support/commands for maintaining fence coords. - Add data manager module to support persistence fence storage. Can store other data, but only used for fence at this time. - Add unit tests for data manager