Suffixed _4 on BEACON STATUSTXT (FTM-500DE)

[Anaximandro Furtado]

Hi Everyone,

Regardless of any text I put on BEACON STATUSTXT (FTM-500DE), such text will be always suffixed by the string _4 (see below).

I was made aware that such suffix is used to provide information on the radio model and that an entry needs to be added to https://github.com/aprsorg/aprs-deviceid/blob/main/tocalls.yaml in order to hide such suffix on aprs.fi. Another radio that I use, FT-5DE, is suffixed by _3, but on this model such suffix is properly hidden when browsing on aprs.fi. This models seems to have an entry on the YAML file above.

Who can add such entry to https://github.com/aprsorg/aprs-deviceid/blob/main/tocalls.yaml?

Regards,

Anaxi, CR7BGW

[Heikki Hannikainen]

On Thu, 14 Sep 2023, Anaximandro Furtado wrote:

> Who can add such entry to https://github.com/aprsorg/aprs-deviceid/blob/main/tocalls.yaml?

The manufacturer of the Yaesu radio, or their official representative,
should get in touch, make a ticket at
https://github.com/aprsorg/aprs-deviceid to coordinate the allocations.

- Hessu

[Anaximandro Furtado]

It's a shame that this issues is not resolved yet. The current procedure to add new radios requires the maker themselves to initiate the process, action that Yaesu doesn't seems to care much and APRS team could easily fix... I don't get it :(