Posts Tagged APRS
I recently got into DMR radio and picked up an Anytone D878UV. While exploring some of the features of the radio, I found information on doing SMS over DMR. As interesting as it looked, it was not well documented. This post is going to be an effort to pull some of the resources together in one place for other folks who might find it useful, and document what I’ve been able to get working.
This will all be based on use of the Anytone 1.18 CPS, available here.
To start, you’ll want to make sure your radio is programmed to interface with the Brandmeister network correctly. Make sure that in the CPS under Public > Optional Setting > Digital Func you have SMS Format set to M-SMS. Also, according to this post, you will need to have Digi APRS RX turned off for the channel you are set to, as it may interfere (I haven’t confirmed this).
Next, in Brandmeister SelfCare, ensure that your radio is set correctly. I was able to get this to work with Brand set to Chinese Radio.
With these set, you should be able to send a message containing the word “HELP” to 262993 and get a response. More of the commands are documented on this page in German (Google Translate version here).
I found that when using KF5INZ Easy-Digi board and DireWolf v1.2 for APRS, you will need to specify both DTR and RTS control in the DireWolf configuration file, or DireWolf will hold PTT down. All other programs seem to work normally. Example configuration line for DireWolf:
PTT COM4 DTR RTS
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.
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.