Hi there,
I need to analyse some flight data for a uni project but I need the data to be recorded at around 100 Hz. I have seen (in the sdlog2 parameter file) that the fastest rate is 250 Hz and the default rate is 25 Hz.
Does anyone know if it is possible to change the data logging rate to the sd card through mission planner? Or any other method to change the rate?
I need to analyse some flight data for a uni project but I need the data to
be recorded at around 100 Hz. I have seen (in the sdlog2 parameter file)
that the fastest rate is 250 Hz and the default rate is 25 Hz.
Logging at a faster rate takes away available processor time from other tasks. I am not sure how much “extra time” is available for use… be aware that increasing logging rates may cause performance problems.
1.5) There are ways to determine if performance is suffering (I think the keyword is “Performance Monitoring”) but they may be difficult and I personally can’t give any advice.
If you’re committed to changing the logging rates to see what happens, try modifying is the scheduler task table in ArduPlane.cpp.
Thanks for that.
In order to update the scheduler task and apply it to the Pixhawk do I need to edit the scheduler task table using PX4 Toolchain via Eclipse and then rebuild the firmware with those changes?
I’m very new to Mission Planner and the Arduplane code so I apologise if this is a silly question!
Cheers
It’s most correct to say that you need to “Edit the scheduler task in the ArduPlane firmware, then re-build it and upload to your Pixhawk.”
You are describing (what I think is) one specific way to do that (PX4 Toolchain via Eclipse) but I am not sure… I’m not an Eclipse user. Take a look at this page on Building the Code. (http://ardupilot.org/dev/docs/building-the-code.html) I see there that Eclipse is one of the options that you might pursue.
I work in Linux, and use “make”. (That’s a pretty standard way to work with C/C++ in Linux.)
I have heard that perhaps ArduPilot is transitioning towards a build system called “waf” and I’ve used that before too, so I’ll welcome that change if it ever comes.