Description
Describe the bug
ADSB heading angle handling is incorrect. Transponder report message reference states heading is [-pi, pi] where 0 is north.
Currently, the driver code adds pi to the heading angle before wrapping to pi causing 0 heading to be south in the uorb message. This is reconciled in adsb conflict handling by adding 180 deg and in adsb vehicle mavlink msg by adding pi.
To Reproduce
- Flash drone with transponder report enabled in dds_topics.yaml
- Prepare drone with adsb receiver
- Connect companion computer through uxrce
- Observe angle difference between qgroundcontrol GUI and TransponderReport message
Expected behavior
When obtaining heading from ADSB, heading should be 0 when vehicle is pointing north.
Screenshot / Media
No response
Flight Log
No response
Software Version
1.15.2
Flight controller
Cube Orange Plus
Vehicle type
Fixed Wing
How are the different components wired up (including port information)
No response
Additional context
No response