Regarding JS8call, in addition to keyboard chatting, it also provides a one-way APRS gateway. You can send position and status reports, email, phone-text messages, etc to APRS and it gets processed as regular APRS stuff. I have two JS8 rcv-only stations (SDR, RPi, 30 meters and 40 meters, one setup in California and the other in Washington), that receive and forward to APRS. The robust (but slow) JS8/FT8 coding and protocol have some real advantages over more traditional ACK/NAK services.
Paul - thanks very much for that additional information about JS8call! I remember your description of its utility from a San Juan County Amateur Radio Society presentation.
I am also looking at using APRS with FX.25, a forward-error-correction wrapper over standard X.25 packets. Given the asynchronous packet timing and faster data rate the SNR performance probably isn't as powerful as FT8-style transmission, but FX.25 does provide for quite a bit of FEC. One more rabbit-hole for me to explore!
That looks really interesting. I am hoping for broad coverage on 30 meters so my buoy's signal will be received from wherever it drifts, and plan to send both JS8 and APRS messages on 30m. I assume that Direwolf is being widely used but haven't really looked into how much APRS coverage there is on 30 meters. I could guess that there are at least as many 30m APRS stations as 30m JS8, but that's a guess. I'm going to set up a couple SDR/RPi/Direwolf stations when I find the time. I can probably use one SDR/RPi to feed the JS8Call and Direwolf programs.
You may notice I use the phrase "plan to" a lot. I'm a poster-child for ADD, and flit from one shiny project to another.
Regarding JS8call, in addition to keyboard chatting, it also provides a one-way APRS gateway. You can send position and status reports, email, phone-text messages, etc to APRS and it gets processed as regular APRS stuff. I have two JS8 rcv-only stations (SDR, RPi, 30 meters and 40 meters, one setup in California and the other in Washington), that receive and forward to APRS. The robust (but slow) JS8/FT8 coding and protocol have some real advantages over more traditional ACK/NAK services.
Paul - thanks very much for that additional information about JS8call! I remember your description of its utility from a San Juan County Amateur Radio Society presentation.
Here's a link to that presentation: http://wb6cxc.com/wp-content/uploads/2019/04/Presentation-1-0.pdf
I am also looking at using APRS with FX.25, a forward-error-correction wrapper over standard X.25 packets. Given the asynchronous packet timing and faster data rate the SNR performance probably isn't as powerful as FT8-style transmission, but FX.25 does provide for quite a bit of FEC. One more rabbit-hole for me to explore!
If you’re using Dire Wolf, another FEC option is IL2P. It’s a bit more streamlined than FX.25.
That looks really interesting. I am hoping for broad coverage on 30 meters so my buoy's signal will be received from wherever it drifts, and plan to send both JS8 and APRS messages on 30m. I assume that Direwolf is being widely used but haven't really looked into how much APRS coverage there is on 30 meters. I could guess that there are at least as many 30m APRS stations as 30m JS8, but that's a guess. I'm going to set up a couple SDR/RPi/Direwolf stations when I find the time. I can probably use one SDR/RPi to feed the JS8Call and Direwolf programs.
You may notice I use the phrase "plan to" a lot. I'm a poster-child for ADD, and flit from one shiny project to another.
Here's a link to a video presentation I did for the 2021 MicroHams conference, a bit more recent than what is on my wb6cxc blog: https://www.youtube.com/watch?v=ABRh5U5JzAk&list=PLsDuZAuN7kop31aV4KTjSPDKee7XyoIFi&index=4