APRS messaging bug in the Yaesu FT1D

UPDATE 1-19-2017: Another ham reached out to me about this, mentioning that it may be related to having extra spaces at the end of your callsign if it’s less than 6 characters. I loaded my programming in RT System’s FT-1D Programmer and went to Settings > Radio Menu Settings, then clicked the APRS tab. Here I was able to verify that an extra space does exist in the “My Callsign” field. I’ve decided not to test this further, but it should be trivial for someone to verify whether or not removing this extra space fixes this issue.

I have a Yaesu FT1D that supports APRS messaging. I set the callsign in my radio (via SET:12), and I set my APRS callsign as my callsign with SSID -7 via SET:9>23. (See the FT1D manual here or an explanation about APRS SSIDs here.)

I tried sending a message to CQSRVR and ANSRVR to test, but I never got any replies. I have a low-budget digipeater set up in another room using a laptop and another HT, so I checked the screen. The packets were received, gated, and responses were received and transmitted, but my radio never showed anything under messages.

I installed PocketPacket (iOS App Store) and using SSID -5 for it. I sent a message from my radio to my -5 SSID. It showed up on my iPhone. I replied to that message, addressed to SSID-7, it did not show up on my radio.

A bit frustrated, I sent a message to my callsign without SSID. It showed up on my radio. However, when I replied from my radio, the -7 SSID was appended, and so replies to the -7 SSID wouldn’t show up.

By changing my APRS SSID via SET:9>23 to my callsign only without SSID, I was able to get messaging working as expected.

So, in a nutshell:

Issue: APRS messages are not displayed on the radio when an SSID of non-zero is set via SET menu 9>23.

Occurrence: Always

Steps to reproduce: Set an SSID to your callsign via the above-mentioned settings menu. Transmit an APRS message from another device to your callsign-with-SSID. It is not shown on the radio. Transmit an APRS message from another device to your callsign-without-SSID. It is shown on the radio.

Workaround: Set menu 9>23 to your callsign without SSID.

Expected behavior: When the SSID is set via menu 9>23, messages are shown as addressed to your callsign-with-SSID.

I will be emailing Yaesu regarding this issue and hopefully they can fix it in a firmware update.


, , ,

  1. #1 by ae5zc on August 20, 2016 - 4:48 pm

    I seem to be having a related problem.. I can see an “OM>ae5zc-15” message popup on the display when I send to my HT (ae5zc-7), but I can’t ever see the message in the message list… I am using the latest firmware as of today. Did you ever resolve your issue(s)?

    • #2 by MB on August 23, 2016 - 6:47 pm

      Was there another firmware released recently? I wasn’t aware of it. I’ll have to take another look at this. In the meantime, can you try configuring your HT for no SSID and see if you receive the message?

      • #3 by ae5zc on September 30, 2016 - 11:21 pm

        Sorry for the delay, and sorry that I wasn’t more clear. I meant to say that I had the latest firmware that was available. I *DID* recently configure my FT1D for no SSID as you mentioned in the post and I *DID* start receiving messages (after trying minutes before with an SSID and getting none, as I had originally reported). So… I completely agree… there’s a bug. I wrote in to Yaesu tech support and described the problem the day before my original post… I got what seemed like a canned response to send in my unit to let them “check it for me”… but really seems like a firmware bug to me.

        • #4 by MB on October 10, 2016 - 10:45 pm

          Sorry for the delay on my end as well :)

          I did recently upgrade the firmware on my FT1D but I haven’t had a chance to check if this bug still occurs. If so, it’s a bit of a disappointment.

          EDIT–This bug still exists on the latest firmware, as of 2016-10-13. :(