![rtty vs psk31 rtty vs psk31](https://i.ytimg.com/vi/6g60yTSzzQw/mqdefault.jpg)
Most of SSTV and PSK31 activity is on HF SSB, although VHF/UHF digital chat as such should be a lot of fun. But it's not overly popular in most areas, so you might have to talk some friends to play with it. Technically, you can run SSTV or PSK31 over FM, and that "data" connector will suit that purpose perfectly. The "9600" pin audio output is taken before audio filter/amplifier stages of the radio, and has a flatter audio frequency response that is good for high speed data such as 9600 bit/s packet or AIS reception. I quoted the bit rates, since the radio documentation often cites these standard packet radio speeds, although in reality it's just audio, and the radio doesn't really care about any bit rates as such. RX audio out, "9600 bit/s" discriminator output.RX audio out, "1200 bit/s" "normal audio".
![rtty vs psk31 rtty vs psk31](https://i.ytimg.com/vi/mso3Z_EQcLw/maxresdefault.jpg)
The 6-pin data connector is originally designed for attaching packet radio TNCs and other data equipment, and usually has at least the following pins: Currently manufactured dual-band examples include Yaesu FT-7900, Kenwood TM-V71, Icom IC-208H - they all have the same 6-pin mini-DIN "data" connector using the same main pinout. These tend to come and go, so unfortunately I can't provide any links, as they would be out of date in a few weeks.Most modern VHF/UHF FM mobile rigs designed for Amateur Radio use have a "data" connector on the back. If you haven't tried the PSK31 data mode yet (or if you're already QRV on the mode and are interested to see how well your signal is getting into Europe) check out one of the online PSK receivers. To read about it and download a copy, click here.
![rtty vs psk31 rtty vs psk31](https://www.blackcatsystems.com/pics/MultiModeScreenshotPSK31.png)
Rtty vs psk31 how to#
I worked with Moe to develop a demonstration of how to use the DLL in a Borland Delphi program called PSK31Test. The PSK31 Core DLL does that for you, leaving you with the job of creating the user interface.
Rtty vs psk31 code#
However, the hard part for most people is writing the code to generate and decode the PSK31 signal using the sound card. The advantage of writing your own program is that you can make it look and work the way you want.
Rtty vs psk31 software#
One interesting development for those who would like to write their own PSK31 software is the PSK31 Core DLL by Moe Wheatley, AE4JY, developer of WinPSK. For more information about them visit the Official PSK31 WWW Homepage. Many programs are now available that enable you to send and receive PSK31. Many desktop-style transceivers have a dedicated data interface which avoids the nuisance of disconnecting the mike whenever you want to operate on PSK. With many transceivers (including the Elecraft K2) the audio must be connected to the microphone socket after some fairly heavy attenuation. To create a PSK signal for transmitting the sound card generates the audio which is taken from the speaker socket and fed to the transceiver. The output from the radio receiver is fed into the sound card's line input socket and the software decodes it and displays the text on the screen.
Rtty vs psk31 Pc#
Most PSK31 operators use PC software that generates and decodes the audio PSK signal using the computer sound card. I have made many satisfactory contacts using my Elecraft K2 generating just 5W pep output However, PSK31 is much more effective than RTTY, being more resistant to interference and needing less power to achieve solid copy. It uses a very narrow band, phase modulated signal and special data encoding, to allow operators to "chat" in a manner similar to RTTY. PSK31 is a method of communicating by sending data over radio which was developed by Peter Martinez, G3PLX.