Actually, Jack, this makes more sense. In a way, this would be one way of interoperability between modes.
For those of us who did Amtor and later Pactor and Clover II, the old Aplink and later Winlink systems allowed us to connect to a MBO (Mail Box Operation, I think that was what they used to call them) with any of the modes and the station would be able to switch to the correct mode and store and play the messages. RTTY Journal (or it could have been renamed RTTY Digital Journal) had an extensive article on how this was done. Manageable, but a bit messy to do it. So no matter what mode we had, we could still communicate with these MBO's and they in turn would forward the traffic world wide or whatever was needed. Otherwise, just having a new mode would not make much sense to put that much energy into development. But since regular 300 baud packet is so very poor on HF, just about any improved modulation scheme would be so much better. For sound card modes today, we have the 110 baud packet mode which does work much better, but of course is about a third the speed of 300 baud packet and you would need to match your speed to anyone with that mode. Even then, other modes are so much better now, particularly the ALE400 mode or better yet the 8FSK50 FAE 400 ARQ mode. 73, Rick, KV9U Jack Chomley wrote: > Rick, > Well, its just another mode, to add to the > pile! You get RPR with the SCS DSP > Tracker, APRS is also using it and the DSP > Tracker will send BOTH mode APRS frames out, that > is a standard 300 baud HF Packet data frame, THEN > the next one out is an RPR frame, alternating. > This is so any RPR OR standard 300 baud stations > or IGATEs will pick up the signals. > At least in this case, SCS thought of the 300 > baud HF Packet users on APRS, when they developed this TNC. > The other SCS PTC models also have the RPR mode too. > I think the mode is a good one, given it is a > hardware based one, that can be used in a reasonable cost piece of hardware. > https://www.scs-ptc.com/controller.html > > 73s > > Jack VK4JRC > >
