Bad aircraft data
clydebarrow opened this issue · comments
ATTENTION !
- Use this form to report bugs in an Official Release of SoftRF firmware, hardware and web pages only ;
- Issue reports from anonymous users will be most likely invalidated. Reasons for that are well explained here ;
- Prior to asking a question, look into "Closed issues" area to see if it was answered before ;
- No any "ideas" or new feature requests, please ! New feature requests do not subject for taking into consideration unless they come from co-developers ;
- "Enhancements" of existing features are only allowed when you are ready to implement them by yourself. See CONTRIBUTING list for details ;
Recommended:
- screenshot or photo width - from 600 to 800 pixels ;
- aspect ratio - 4:3, 3:4, 16:9 or 9:16.
- substitute 'space' by 'x' character to mark a hardware checkbox
Hardware
- Standalone
- Badge
- Prime Mark III
- Prime Mark II
- Dongle
- SkyView EZ
- SkyView Pico
- Uni
- Ham
- Midi
- Mini
- Academy
- Lego
- ES Edition
- Balkan
- Raspberry Edition
- UAV
- WebTop Serial
- WebTop USB
- UAT978 module
- Flight Recorder
< photo of your hardware > (required)
Firmware version
1.4 installed from Releases page via UF2.
< screenshot of WebUI and/or SoftRF Tool status page > (required)
Firmware settings
< screenshot of WebUI and/or SoftRF Tool settings page > (required)
Describe the bug
Until recently this was inter-operating well with Flarm devices, using the Legacy protocol. Now it receives data, but the reported aircraft data is completely bogus. The distance is impossibly large, and the aircraft type changes randomly.
GPS data received via Bluetooth is correct so the device does have a valid GPS location.
The same behaviour was observed with firmware 1.3, updating did not change this.
To Reproduce
Receive Flarm transmissions with the T-Echo SoftRF model.
Expected behavior
Reported data will be valid.
- "Enhancements" of existing features are only allowed when you are ready to implement them by yourself. See CONTRIBUTING list for details ;
Resolution: invalid
I was aware that feature requests were not welcome here, but perhaps you could explain more why this would be considered an enhancement. What information am I missing? Has there been a change in the Flarm protocol recently that renders SoftRF incompatible?
Volunteer contributors are welcome: https://pastebin.com/YB1ppAbt
