SoftRF Dongle Edition DSX conflict with OGN and FLARM // change of HEX-ID as prefix 0x5B is not processed
opened this issue · comments
Hardware
- Standalone
- Prime Mark II
- Uni
- Dongle
- Mini
- SkyView EZ
- Raspberry Edition
- UAV
- UAT978 module
- Flight Recorder
Firmware version
SoftRF-firmware-v1.0-rc8-S76G.dfu
Firmware settings
N/A
Describe the bug (or ask a question)
I do have a SoftRF Dongle Edition flashed to current firmware, which is not visible in neither OGN nor FLARM environments, so invisible for detection units like Stratux etceteras.
As it turns out, the Dongle uses a HEX-ID for transmission starting 5B and is not processed by OGN and/or FLARM. Research and help of our fellow friends from Stratux and OGN programming revealed prefix 0x5B HEX-IDs belong to a different encoding family and were used for a service called D.S.X, so were subject to exclusion rules in receiving and processing OGN and FLARM.
SoftRF Dongle Edition therefore needs a possibility to change its HEX-ID to be something else than starting 0x5B.
To Reproduce
just take a Dongle transmitting on a 0x5B prefix.
Expected behavior
Visible in OGN and FLARM.
- anonymous user and
- incomplete issue report and
- works fine to me :
Resolution: invalid
Reproduced with OGN software 0.2.8
FLARM traffic is the only affected.
Every of 0x5B**** addresses have been remapped in: f63aa96