It would probably be nice if angular velocities and also acceleration would be exposed in telemetry. I have heard people asking for this quite a bit.
This data could be received by the HIGHRES_IMU message and added to the telemetry plugin in the same way as other data is exposed there.
I am working on solving it. Should both angular speed and acceleration be a part of the same struct in telemetry.h or do i have to make one struct for each of them?
Should both angular speed and acceleration be a part of the same struct in telemetry.h or do i have to make one struct for each of them?
I believe I would put them in the same struct, as they make sense together as "one IMU reading". It's easier to ignore unwanted info than to merge separate messages later. Do you have an opinion there?
I agree with you. I guess I will emulate what has already been done here with PositionNED, VelocityNED and PositionVelocityNED(knowing that PositionNED and VelocityNED are extracted from the same mavlink message just as in the case of angular velocity and acceleration).
Most helpful comment
I am working on solving it. Should both angular speed and acceleration be a part of the same struct in telemetry.h or do i have to make one struct for each of them?