![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJSwcZLKRyZHaL_T0l6wzmZ9JXLzqYnHelacAE75n4giLlKblukkFvCytAg47B_-VR-EVLKpYkfJNZZsWIi3BRU17nnyz3kNJ1rvIdGKnazohZAFLRBfyGOFjb3UlKCPDZxcoQ57tun0k/w400-h225/aprsshot2.png) |
Anytone AT-D878UV as heard by rtl-sdr+gqrx. Garbled coordinate data in APRS position transmission causes it to be ignored by receiving stations. |
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWpobcN-ptFvcR2WsmTZP7gl9r_PSY8XHKuEMFG4vslpiYAF9NGvKqwmLSX32arWOUD85oaFCIgkb4D22HlUMuYRL_GVO2KB8A_Yb0cB3mXXAtjiEMjMiMEG2EbWmaQFybn7AkxyIriew/s400/aprs_2.png) |
A second example showing other stations' APRS traffic for comparison |
Update 2/27: Found some information
here leading me to a solution for the APRS issue. Below is a screenshot of my 878 APRS settings which have resolved the unintelligible transmission problem:
Take note of the time delay settings (with red dots) as well as the lack of a coma in "APRS signal path". These changes resulted in my APRS transmissions clearing up and finally showing up on
aprs.fi:
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtVm_p_Y9UIYSfkLmtv75-33UQnXE49ZljqjPa0gUgA9tl9Q8JvqzMbGN6ClZMCJ6OBu4TkUdcDyvNPoKJHOrFVtdHE4Zb8Qq0GmSYE4Hf-B7oeknK8pJzit7vFatMCY9ohSHLhvUDfn8/s400/aprs_works.png) |
Success! |
Update 2020: Updating the CPS and radio firmware to the latest (and matching) versions seems to have eliminated the above issues. Through the last year I have been using the 878 with to transmit my position in a number of challenging outdoor environments and it has performed and held up well. Looking forward to APRS messaging capability in the future.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiD2F-2vWRWKy9gRJPafkNnneuIfmliIsHyNZKNswdhAhrvHjTzdIt533uHReoG7u7aB1sNQkskuQEF_aqjvXqJmojiZ3OZvAFq_OgRK2yxdK9YEiK6RCuASdZc-mCHdXzh86cgq6rPXtc/w360-h640/20200617_125726.jpg) |
Anytone AT-D878UV DMR & Analog VHF/UHF radio
|
No comments:
Post a Comment