dataman: add SYS_DM_BACKEND parameter #18827
Conversation
dagar
commented
Dec 9, 2021
•
dagar
commented
- new parameter SYS_DM_BACKEND to configure dataman to use the SD file backend (default) or RAM
- reduce NUM_MISSIONS_SUPPORTED from 2000->500 so RAM backend is viable on typical F7
|
Do we want to think about a realistic max for |
dagar
force-pushed
the
pr-dataman_storage
branch
3 times, most recently
from
e9866aa
to
7e703cf
Compare
dagar
force-pushed
the
pr-dataman_storage
branch
from
7e703cf
to
00aa856
Compare
| @@ -49,7 +49,7 @@ | |||
| #elif defined(__PX4_POSIX) | |||
| # define NUM_MISSIONS_SUPPORTED (UINT16_MAX-1) // This is allocated as needed. | |||
| #else | |||
| # define NUM_MISSIONS_SUPPORTED 2000 // This allocates a file of around 181 kB on the SD card. | |||
| # define NUM_MISSIONS_SUPPORTED 500 | |||
There was a problem hiding this comment.
This seems ok although note that a MAVSDK mission with 100 waypoints easily requires 500 mavlink mission items as it expands more complex mission items into several mavlink mission items.
There was a problem hiding this comment.
Ok, let me know if it becomes an issue and we could find a way to make it more configurable or dynamic (at init).
|
Will Mission items include camera photo mav messages during a survey? Because if so a moderate survey would be greater than 500. |
It includes all mavlink mission items. Do you have a particular number in mind? |
|
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
