(If this is the wrong place to direct this question, please may someone point me in the right direction as to where to ask )
I was conducting testing for a uni project with a cube orange and was controlling this via a custom python script using the pymavlink script. I was trying to stream data, specifically attitude data, to a ground station using RF 868 telemetry modules. For some reason, the data stream was capped at 20 Hz and I have struggled to find reasons online as to why.
I checked the parameter list which seemed to have a limit of 10 Hz on there but when checking online at the documented parameter list, it appears to have a limit of 50 Hz.
Does anyone know what could be causing this 20 Hz limit? Apologies if I have missed any important details here, my knowledge in this area is fairly limited so please ask any required questions. Also, if at all possible, could responses contain some sort of source as this would be handy when writing this up for my report (but replies without this will still be very helpful!)
You can request the vehicle to set a particular message like position data to be streamed at the required rate using mavlink. Did you mean it was capped after doing this?
I stored the data in an array during logging and then saved to a csv file once logging stopped. I found the frequency of the data from the ‘time_boot_ms’ data
I am not quite sure I understand your question. Are you referring to if I had say Mission Planner connected to the FC at the same time as the pymavlink class? If so, then no. Only the mavlink class was connected to the FC during testing. However I did use Mission Planner intermittently in-between tests through the same port as the mavlink script, but this was always disconnected before moving back to the mavlink script before testing.
Mission Planner tends to dominate a telemetry port. It may be the cause of your troubles. But if it hasn’t been connected, you should be able to get 50Hz updates so long as the bandwidth is there for it.
Recommend you use a USB connection for MP debugging and a dedicated UART for your app.
Ah, but did you set the stream rates via mavlink again? Once Mission Planner sets the rate, it persists until the FC gets another request to change the rate.