# ADS-B and FLARM collision warning

**URL:** <https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687>\
**Category:** English\
**Created:** [June 14, 2022, 3:24pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687 "2022-06-14T15:24:17Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sanke](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/sanke/32/248_2.png) [@Sanke](https://forum.safesky.app/u/Sanke)\
**Post date:** [June 14, 2022, 3:24pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/1 "2022-06-14T15:24:17Z")

</div>

Hello Guys!

I’m currently expecting an issue with the collision warning. Problem is that our clubs motorgliders have both - FLARM and ADS-B Transponder.  
In the app I can only enter either FLARM or transponder Hex-Code.  
So I’m always getting collision warning from myself…  
I really like the app an appreciate the Skydeamon connectivity, but constant warnings are a bummer for me 😕

Hope you guys have a workaround for me  
Greets from EDHS!

---

<div class="post-metadata">

**Author:** ![xtof](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/xtof/32/36_2.png) [@xtof](https://forum.safesky.app/u/xtof)\
**Post date:** [June 14, 2022, 9:12pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/2 "2022-06-14T21:12:20Z")

</div>

Hello @Sanke  
It is not usual to use two different system, but you are not alone and we are working on it, in order to give the possibility to mention 2 different hexa code…  
Work in progress 😉

---

<div class="post-metadata">

**Author:** ![Billy](https://avatars.discourse-cdn.com/v4/letter/b/ecd19e/32.png) [@Billy](https://forum.safesky.app/u/Billy)\
**Post date:** [June 16, 2022, 8:29am UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/3 "2022-06-16T08:29:04Z")

</div>

This is a known issue with all EC. The answer is to put the same code in each it doesn’t matter which one.

---

<div class="post-metadata">

**Author:** ![DesperateUser](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@DesperateUser](https://forum.safesky.app/u/DesperateUser)\
**Post date:** [July 15, 2022, 12:13pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/4 "2022-07-15T12:13:50Z")

</div>

I have the same problem, I use ADS-B and FLARM. Would be great to solve this issue!

---

<div class="post-metadata">

**Author:** ![Tristan](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tristan/32/10_2.png) [@Tristan](https://forum.safesky.app/u/Tristan)\
**Post date:** [July 19, 2022, 8:02am UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/5 "2022-07-19T08:02:41Z")

</div>

This is confirmed, next September release will include the ability to encode several transponder types and codes.

Stay tuned,

SafeSky Team

---

<div class="post-metadata">

**Author:** ![OrtiMai](https://avatars.discourse-cdn.com/v4/letter/o/a9adbd/32.png) [@OrtiMai](https://forum.safesky.app/u/OrtiMai)\
**Post date:** [August 18, 2024, 10:14am UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/6 "2024-08-18T10:14:10Z")

</div>

On old planes, where ADS-B and FLARM devices are different physical systems, there are one hex code each. They are registered as such. Is there a possibility to register them as one aircraft?

---

<div class="post-metadata">

**Author:** ![xtof](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/xtof/32/36_2.png) [@xtof](https://forum.safesky.app/u/xtof)\
**Post date:** [August 26, 2024, 1:42pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/7 "2024-08-26T13:42:34Z")

</div>

Hi,

The rule is very simple…One hex code per aircraft.  
If you don’t respect this, it means that other planes can see you twice…  
This is not good for security…  
The correct hexadecimal code is that of your transponder, which is probably ADS-B.

However, you’re not the first to bring this problem to our attention. We’re looking into the possibility of encoding two hex codes, but we’re not keen on this solution.

Best regards,

---

<div class="post-metadata">

**Author:** ![OrtiMai](https://avatars.discourse-cdn.com/v4/letter/o/a9adbd/32.png) [@OrtiMai](https://forum.safesky.app/u/OrtiMai)\
**Post date:** [August 26, 2024, 5:57pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/8 "2024-08-26T17:57:59Z")

</div>

@xtof , I’m not keen on having two hex codes either.

But many flying clubs have these old planes and they are from a time without ADS-B and FLARM. Both got added as an upgrade and these transponders work well till today.

As the financial resources of these flying clubs are limited, they often use the technical equipment as long as it is good.

Some old FLARM devices are not made for having a HEX-code change. Maybe the manufacturer can do that, but for sure with trading in money.

Thus you’re right. In your smart approach to bring all data together, I’d see two planes. And indeed, that’s what I see in the air with our own club planes as two planes, but all across Germany as well, when these old planes are getting moved around. There are more, then one would think of.

Thus, maybe a plausibility check would be a solution. Yes, we don’t want a formation accidentially beeing identifed as only one plane. But if a plane always shows up with two HEX and if these would be always the same. Why not learn this to be one plane.

Just as a suggestion.

---

<div class="post-metadata">

**Author:** ![xtof](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/xtof/32/36_2.png) [@xtof](https://forum.safesky.app/u/xtof)\
**Post date:** [August 27, 2024, 12:16pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/9 "2024-08-27T12:16:24Z")

</div>

Not so simple. But we think about 2 hex code

---

<div class="post-metadata">

**Author:** ![OrtiMai](https://avatars.discourse-cdn.com/v4/letter/o/a9adbd/32.png) [@OrtiMai](https://forum.safesky.app/u/OrtiMai)\
**Post date:** [April 9, 2026, 7:22pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/10 "2026-04-09T19:22:25Z")

</div>

And news on this one, that I might have missed?

@Tristan & @xtof You guys might remember, that old FLARM devices weren’t able to get set to the same Hex like ADS-B. Thus, we asked for the possibility to add a FLARM Hex and a different ADS-B Hex. Is there a solution now?

---

<div class="post-metadata">

**Author:** ![Tristan](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tristan/32/10_2.png) [@Tristan](https://forum.safesky.app/u/Tristan)\
**Post date:** [April 10, 2026, 6:28am UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/11 "2026-04-10T06:28:25Z")

</div>

Hello, this is still an open point. We were actually thinking of adding the possibility to add a second ‘code’ so that both identifiers could be set, and SafeSky could deduplicate server-side.

I will keep you posted if we can confirm to add this to our roadmap shortly.

Fly Safe,

Tristan

---

<div class="post-metadata">

**Author:** ![OrtiMai](https://avatars.discourse-cdn.com/v4/letter/o/a9adbd/32.png) [@OrtiMai](https://forum.safesky.app/u/OrtiMai)\
**Post date:** [April 10, 2026, 11:48am UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/12 "2026-04-10T11:48:57Z")

</div>

Good to hear, I flew our historic motorglider last weekend and as I’ve connected SafeSyk to SkyDemon, I got constand warning about myself. Thus, I had to turn the voice down, which kills one of your safety features. I don’t wanted to stress here, thus I thought, I get back into contact with you guys.

---

<div class="post-metadata">

**Author:** ![Tristan](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tristan/32/10_2.png) [@Tristan](https://forum.safesky.app/u/Tristan)\
**Post date:** [April 10, 2026, 12:04pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/13 "2026-04-10T12:04:48Z")

</div>

As a quick win for now, you can put to silence the echo of yourself from the SafeSky App.

 ![IMG_1373](https://europe1.discourse-cdn.com/flex017/uploads/safesky/original/1X/b907869bc5c775273085965fe12b951755066e12.jpeg)  
 ![IMG_1374](https://europe1.discourse-cdn.com/flex017/uploads/safesky/original/1X/b7f7f45f4b3c516c7dea37794e3895060c41ba21.png)

---

<div class="post-metadata">

**Author:** ![OrtiMai](https://avatars.discourse-cdn.com/v4/letter/o/a9adbd/32.png) [@OrtiMai](https://forum.safesky.app/u/OrtiMai)\
**Post date:** [April 10, 2026, 12:47pm UTC](https://forum.safesky.app/t/ads-b-and-flarm-collision-warning/687/14 "2026-04-10T12:47:02Z")

</div>

Oh yes, good to know. I never used this. It’s probably a good temporary solution.
