Hi, I‘m using Stratux (with T-Beam) together with SafeSky and Skydemon. The T-Beam (Legacy) target is invisible in Skydemon because of the ownship function in Stratux. But it is visible in SafeSky and it produces a danger warning. How can I avoid this? Thanks. Greetings Kai
It might be connected to the issue I came here to report:
Today, I realized, that when creating a new aircraft profile, the Transponder HEX-Code does not get added automatically (when you activate Transponder and try to automatically retrieve the code, it says it cannot find it). In the past, this worked… I tried it with an aircraft that I had successfully added in the past (and later deleted).
Of course, you can always set the Hex code manually.
Is this a temporary problem?
In Stratux I can define multiple ownship hexcodes. In SafeSky I can only define one ownship hexcode.
The aircraft I‘m flying has a transponder with it‘s own hexcode. My Stratux uses an T-Beam with it‘s own hexcode.
The T-Beam is seen by Stratux and it seams that Stratux sends the hexcode of the T-Beam to SafeSky.
SafeSky brings up a danger warning…because the foreign target is extremly close.
I should be able to define a second ownship in SafeSky.
Thanks a lot.
All of the ‘HEX’ codes needs to be the same:
The one in SafeSky needs to match the one one of your ADSB tranceiver on board your airplane (mode-C or mode-S).
Your T-Beam can also have such a code and alsdo must be configured, this can be done from Stratux aswell…