search

aprsorg / aprs-deviceid

APRS device identification data: tocalls.txt + mic-e-types.txt current master allocations (YAML, JSON, XML)
60 stars 23 forks source link

Yaesu FTM-500D #118

Closed wb2osz closed 9 months ago

wb2osz commented 11 months ago

The discussion here https://groups.io/g/APRS/topic/101247433#1944 provides evidence that "_4" is the suffix for Yaesu FTM-500D.

73, John WB2OSZ

hessu commented 9 months ago

Hi,

Yes, it is existent, but the vendor has not made any communication to me or anyone else. It'd be good if they would establish some sort of communication channel to avoid overlapping allocations, and so that we could get in touch with them when bugs occur.

wb2osz commented 9 months ago

The "tocall" value is also missing. Based on the pattern seen,

The FTM-500D would probably be APY500 but I have no evidence for this yet.

I sent a note to Yaesu asking them to confirm.

73, John WB2OSZ

hessu commented 9 months ago

Hi,

I'd really prefer Yaesu to provide this information first hand, just like everyone else. An allocation database won't work well if everyone just picks up identifiers without coordination and waits for us to catch them.

The second reason is that it'd be very good to have a contact point with them in case of interoperability issues; sometimes it's been very useful to be able to contact someone when something goes wrong on the APRS-IS. Sometimes it's very difficult.

I've tried a bit to contact them, but no luck yet. I'll try again.

hessu commented 9 months ago

Update: Yaesu has responded and indicated they will be coordinating this now. Stay tuned for updates.

hessu commented 9 months ago

YAESU Customer Relations has provided the details over email today, and also promised to get in touch when new models are coming out. Handled this in ticket #134 and PR #135 .