Yaesu FTM-500D about aprs-deviceid

[hessu]

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]

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]

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

• tocall: APY300
  vendor: Yaesu
  model: FTM-300D
  class: rig

• tocall: APY400
  vendor: Yaesu
  model: FTM-400
  class: rig

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]

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