# SafeSky Ownship problem

**URL:** <https://forum.safesky.app/t/safesky-ownship-problem/1952>\
**Category:** English\
**Created:** [March 5, 2025, 7:52pm UTC](https://forum.safesky.app/t/safesky-ownship-problem/1952 "2025-03-05T19:52:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maverick](https://avatars.discourse-cdn.com/v4/letter/m/258eb7/32.png) [@Maverick](https://forum.safesky.app/u/Maverick)\
**Post date:** [March 5, 2025, 7:52pm UTC](https://forum.safesky.app/t/safesky-ownship-problem/1952/1 "2025-03-05T19:52:44Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![marccreal](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@marccreal](https://forum.safesky.app/u/marccreal)\
**Post date:** [March 5, 2025, 10:46pm UTC](https://forum.safesky.app/t/safesky-ownship-problem/1952/2 "2025-03-05T22:46:51Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Maverick](https://avatars.discourse-cdn.com/v4/letter/m/258eb7/32.png) [@Maverick](https://forum.safesky.app/u/Maverick)\
**Post date:** [March 6, 2025, 6:51pm UTC](https://forum.safesky.app/t/safesky-ownship-problem/1952/3 "2025-03-06T18:51:56Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![rvt](https://avatars.discourse-cdn.com/v4/letter/r/43a26b/32.png) [@rvt](https://forum.safesky.app/u/rvt)\
**Post date:** [March 6, 2025, 7:49pm UTC](https://forum.safesky.app/t/safesky-ownship-problem/1952/4 "2025-03-06T19:49:01Z")

</div>

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…