set custom HEX ID

[alexanderdross]

As I use a transponder with ADS-B out, I want to use the same HEX ID for GxAirCom, such as for Flarm TX.
In the web interface at http://192.168.4.1/, I can view the HEX ID used by the T-Beam, but I cannot modify or update it.

Is there a plan to enable this feature in the future?

[rvt]

Hey Alexander, I assume you are using stratux here. The option was in there to set the HEX code programatically from stratux when you change the hexcode in the UI of stratux. If that does not work anymore, I know that virus pilot did work on this. Cheers, Ries

…

On 5 May 2025, at 12:14, Alexander Dross ***@***.***> wrote: alexanderdross created an issue (gereic/GXAirCom#200) <#200> As I use a transponder with ADS-B out, I want to use the same HEX ID for GxAirCom, such as for Flarm TX. In the web interface at http://192.168.4.1/ <http://192.168.4.1/>, I can view the HEX ID, but I cannot modify or update it. Is there a plan to enable this feature in the future? — Reply to this email directly, view it on GitHub <#200>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFP7LQUNG3KB4MSQV4BZMD2442XPAVCNFSM6AAAAAB4OH3ESWVHI2DSMVQWIX3LMV43ASLTON2WKOZTGAZTSMRRGEZTOMI>. You are receiving this because you are subscribed to this thread.

[alexanderdross]

Hi @rvt this should be without the use of Stratux - by just using T-Beam and GxAirCom firmware. when using its web interface, there is a field showing its HEX ID which is not editable, unfortunately

[alxwolf]

@alexanderdross you can send a string from stratux to /dev/serialin

echo '$PGXCF,<version>,<Output Serial>,<eMode>,<eOutputVario>,<output Fanet>,<output GPS>,<output FLARM>,<customGPSConfig>,<Aircraft Type (hex)>,<Address Type>,<Address (hex)>, <Pilot Name>' > /dev/serialin

And yes, would be nice to do that via GUI in GXAircom. Disappeared from Stratux for me, too. V1.6r1-eu032

[alxwolf]

@alexanderdross @gereic

#186 killed this feature (I assume, accidentally).

Asked to get it back: #186 (comment)

[luar123]

That was not intended, sorry. I guess it could be reverted easily, then it wouldn't be standard compliant but shouldn't break anything.
Maybe a better solution would be to send a custom request from stratux? Just an idea....

Anyway, there is a more critical issue with ICAO hex ID: You can not use them for Fanet (you could but you shouldn't as it could lead to two devices having the same ID). So if you use this feature please don't enable Fanet TX.
There is an additional Fanet message type (not implemented by gxaircom) that can include the ICAO ID for exactly that purpose (not sure if this is used by any other device to match the IDs, though). So the ideal solution would be to implement this message type, add an additional field for an optional ICAO address and use ICAO or internal ID for Flarm TX, internal ID for Fanet Tx and send ICAO as additional message with Fanet.

[alxwolf]

Yes that's "dirty" - but it worked :)

Stratux actually checks for 3 things:

"GXAircom" in $PFLAV message, "$LK8EX1" message and the $PGXCF message.

Sadly, I've spent a full afternoon and couldn't even find out why the firmware in bin directory has UDP as output and whenever I compile locally I get BLE, and both variants don't have serial output and Beidou and Galileo satellite messages are disabled until "GPS config" is clicked...

So, I'd rather leave this to someone who has a clue... would be great if we could stratux' tracker.go and GXAircom cooperate again.

Did not know about the FANet topic...

[rvt]

when I wrote the stratux compatibility I just wanted to know if it was GxAirCom, and if so simply configure GxAirCom.
I do believe it's important to stick to proper standards, so when no Obs is present in PFLAV it should not be send...

Create a custom sentence in GxAirCOm that stratux can detect (or others) sounds like to correct thing to do..

ABout FANET: From stratux perspective we just care about conspicuity, so re-using a HEX is indeed possible, but I don't think in real world that's going to be any issue at all. We have seen far to many near incidents and also some accidents to worry about that..

For the people that don't know: most of the time the HEX code is the same as the transponder code.

[alxwolf]

@rvt agree, that would be clean.

Now, we already have a $PGXCF message. And that is in the hands of GXAircom alone...

Would it hurt to broadcast this config periodically? AFAIK Foreflight does that too, to announce its presence.

Probably would not hurt and provide a clear statement to Stratux (and others) about available features.

[misterdoud]

it s very simple with the las stratux version
make sure you have selected ont the web interface of GXaircom

output UPD
additional output over serial
output GPS config GPS
output FLARM
output FANET
output Vario LK8EX1

after you can check on the stratux interface and you can have a new modul fore setup the GXaircom