Using RSP Pro 2 for CW RTTY decoding?

General discussions
frankcarril@aol.com
Posts: 5
Joined: Fri Dec 08, 2017 3:48 pm

Using RSP Pro 2 for CW RTTY decoding?

Post by frankcarril@aol.com » Thu Dec 28, 2017 7:13 pm

I am a new Tech..

I would like to use my RSP SDR to tune to CW on the Ham Bands and then on my same computer (windows) bring up a program like: FLDigi or Ham Radio Deluxe to read out the CW Code?. I was told these can do that, but no one tells me what to do to make it work?
and the Same for RTTY .. Is this possible ??

Can I do this?

Is there a better program to use for printing out the Code and RTTY ?
Is it easy to config these programs ?
How will I know if I am listening to PSK 31 or JT 65 , will I have to configure differently each mode ?
Last edited by frankcarril@aol.com on Thu Jan 01, 1970 12:00 am, edited 0 times in total.
Reason: No reason

RSP2user
Posts: 108
Joined: Mon Oct 09, 2017 7:11 am

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by RSP2user » Fri Dec 29, 2017 1:04 am

FLDigi can be obtained here: https://sourceforge.net/projects/fldigi/files/fldigi/
FLDigi has a help file. FLdigi can be used for CW, PSK, MFSK, RTTY among other applications.
Here is an example of FLDigi and the RSP1 operating with RTTY: https://www.youtube.com/watch?v=F_o4ZDemFQA
FLDigi tutorial for CW (Morse Code): https://www.youtube.com/watch?v=Tif-SVEFIa4
Here is an example of FLDigi and the RSP2 operating with HF Weather Fax: https://www.youtube.com/watch?v=8TNQ5uQHkUg

Reason: No reason

frankcarril@aol.com
Posts: 5
Joined: Fri Dec 08, 2017 3:48 pm

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by frankcarril@aol.com » Fri Dec 29, 2017 6:16 pm

I get my sdr going, find a signal CW ,,,, Bring up Fldigi ,, then have no clue how to make it hear and decode the CW coming out the speakers? Is there a video to help me on that? I am only going to listenand decode ,, no transmitting..
If you want to call me at 575 647 5303 thats fine but understand if nit in this crazy world we live in.
Thanks
Frank c
Last edited by frankcarril@aol.com on Thu Jan 01, 1970 12:00 am, edited 0 times in total.
Reason: No reason

RSP2user
Posts: 108
Joined: Mon Oct 09, 2017 7:11 am

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by RSP2user » Fri Dec 29, 2017 7:29 pm

Frank,

If the tutorial here https://www.youtube.com/watch?v=F_o4ZDemFQA was not enough to get you going, then you may want to go through tutorials on operating the RSP2 as well as tutorials on initially setting up FLDigi. Many examples of various SDR operations that you find on the Internet assume the user is a HAM radio operator or at least has a strong radio electronics background. If you don't have that type of background, you can still get things going, but it will take a bit more study of initial setup tutorials and the user manual for SDRuno. You should first get comfortable tuning in stations and making sure that you can hear the RTTY or CW Morse Code signals well, such as in the example above and in this example https://www.youtube.com/watch?v=wCfsMsj1sws . Once you are receiving the signals and hearing them well and have a good comfort level with how SDRuno operates, then it is time to test with FLDigi. Note that the SDRuno software outputs audio and the FLDigi software will be listening for audio; however, you may have to loop the audio output to the audio input to get the FLDigi software to receive the audio from SDRuno. While this can be done by making a loop back connector for your PC, there is also software that works well here http://www.nerds.de/en/loopbeaudio.html . The software audio loop back solution is usually preferred over the hardware connector solution, if you need an audio loop back. For more examples of SDRuno operation and/or FLDigi setup and operation, you can go to http://www.youtube.com and search on FLDigi as well as SDRuno.

Reason: No reason

frankcarril@aol.com
Posts: 5
Joined: Fri Dec 08, 2017 3:48 pm

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by frankcarril@aol.com » Fri Dec 29, 2017 9:12 pm

Thanks, I am very familiar with SDR and Uno as I use it allot. I find a nice slow CW signal solid and steady. I load up Fligi, then of course it just sits therevwaiting for me to configure or something? The only thing I got from U Tube was to set the mode to CW, which I did. I also get no waterfall in fligi, I have no idea how, and what about the freq on Fligi, am I suppose to set that? What about all the settings in Flgi, baud rate, com ports? and such. You did touch on one thing, loop back, just because my speakers are putting out sound, does Flgi hear it? Who knows, very frustrating, .... I will look at the suggested u tubes suggested...
not sure why everything has to be a project. I hope U Tube can help out with Flgi.
Thanks for taking the time.
Frank c
Last edited by frankcarril@aol.com on Thu Jan 01, 1970 12:00 am, edited 0 times in total.
Reason: No reason

RSP2user
Posts: 108
Joined: Mon Oct 09, 2017 7:11 am

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by RSP2user » Sat Dec 30, 2017 12:13 am

Frank,

Work on getting the audio going with FLDigi. You may or may not need separate loop back audio software, depending on your PC and compatibility with existing features of FLDigi. Refer to the FLDigi sound card configuration for FLDigi here: http://w1hkj.com/FldigiHelp-3.21/html/s ... _page.html . Take time to study the audio setup section. Also, you will need to check your setup and do some testing to see what will work best. If you still can't get the audio connected to FLDigi using the FLDigi audio controls, then you may need to audio loop back software to feed the output audio back to the input.

The FLDigi User's Manual can be found here: http://w1hkj.com/FldigiHelp-3.21/html/index.html

Once you have the audio connected, you should be able to get the RTTY and/or CW Morse Code decoder going in FLDigi. The setup for RTTY and CW operation should be similar to the PSK31 setup here for the RSP1 https://www.youtube.com/watch?v=CM1I7agMCzw , except that you would be setting up for RTTY or CW instead of PSK31. In the example, they use VB-Audio virtual audio cable instead of LoopBeAudio. Either should work fine to loop back the audio.

Once you have things working with the audio and decoding of RTTY and/or Morse Code and/or PSK, if you want to control or view the RF frequency of the RSP2 using FLDigi, note that the RSP2 emulates the Kenwood command set under SDRuno, so FLDigi would need to be set for compatibility with the Kenwood receiver (either directly or by writing an interface for it). Setting the COM port in SDRuno is done from the RX Control window by selecting "SETT." then "CAT." You will need to be able to loop back the serial port transmit to receive so that the serial port output of FLDigi is sent to the serial port input of SDRuno. VSPE (virtual serial port emulator) software is used to loop back serial ports and it is available here: http://www.eterlogic.com/Products.VSPE.html . If you apply this software, set the port up as a single port "Connector." Use an unused COM port, such as COM4 (typically unused). In SDRuno under CAT, check the check box for RX Mode CTRL; set the baud rate the same as FLDigi. Select "Enable & Connect." You should now be able to control or view the frequency settings of the RSP2 from FLDigi, once you have FLDigi properly configured for the Kenwood receiver and the COM port setup properly. The FLDigi rig control information can be found here: http://w1hkj.com/FldigiHelp-3.21/html/r ... _page.html .

Reason: No reason

Roger
Posts: 217
Joined: Fri Dec 29, 2017 7:59 pm

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by Roger » Sat Dec 30, 2017 4:37 am

You might try watching this video which shows step by step how to get SDRuno to pass sound to Fldigi for decode. It shows PSK31 being decoded but FLdigi also does RTTY, CW etc. https://www.youtube.com/watch?v=CM1I7agMCzw. Note FLDigi will not track your receiver frequency because a Virtual Com port and CAT are not setup. To learn about that read the SDRuno user manual
Last edited by Roger on Thu Jan 01, 1970 12:00 am, edited 0 times in total.
Reason: No reason

frankcarril@aol.com
Posts: 5
Joined: Fri Dec 08, 2017 3:48 pm

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by frankcarril@aol.com » Sat Dec 30, 2017 6:52 pm

Making some progress..
I am able now to get the FLifi to Waterfall & type out, but so far garbage... but progress.

I started by watching the Video ... Loading the Cable

Got all the way to Set UP... at that point after clicking I never did get Load the Driver ? like in the Video.
So I just went on...
Loaded UNO ... Opened Input... Seen Hi Fi Cable Output ... not other cable...
Then loaded Dligi
Went to the Audio and set the Input to the Same... HI Fi Cable Output..
Dilgi started typing.. so I know I have a connection... Water fall going but not seeing signals.
Set the Freq.. but really no change,, not sure how to do that...yet..
So that is pretty much where I am at..
I need to know why it did not Ask me about he CK Driver after I ran Set Up
Because that never happened, I guess I will never see it as a INPUT Option? but do see HiFi Cable?
I get no sound now to listen as to tune, but I will get sound if I direct the Speakers to a default of the computer instead of Hi Fi Cable.
but then I lose the input to the SDR ... but I can live with that..
So when I tune the SDR it does make a difference to the Typing , so I got connection, but still garble...
I think I have maybe Speed or some kind of configuration problem.. I got the Fligi set to USB input.. is that right or should it be RTTY or ??
Trouble setting Freq in Fligi... I need to watch video..
Some progress, I see the concept, but not getting there yet.
I have to bounce back and fourth taking care of a sick wife... so I give as much time as possible..
Thanks for your Help
Frank c Please send any more suggestions you can... making progress... I need to watch the Fligi video more..
I am trying .
Thanks
Last edited by frankcarril@aol.com on Thu Jan 01, 1970 12:00 am, edited 0 times in total.
Reason: No reason

RSP2user
Posts: 108
Joined: Mon Oct 09, 2017 7:11 am

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by RSP2user » Sun Dec 31, 2017 2:49 am

Frank,

Taking care of your wife is the most important thing. Regarding FLDigi and the RSP2, it sounds like you have made a lot of good progress and will likely be answering questions on this forum helping others, once you get it all figured out. Just a few notes for you:

1) Garbled text can occur, because the signal is not strong enough (fades in and out - perhaps try a different station with a better signal level); or
2) Garbled text can occur, because the receiver is not exactly where it should be on frequency; or
3) Garbled text can occur, because the timing parameter settings for RTTY or Morse Code decoding in FLDigi are not within the range needed for the signal being received; or
3) Text may be perceived as garbled, but it is just in the format applied by radio operators which includes acronyms and, similar to text messaging on mobile phones, sometimes a few letters to represent whole words. Though, you should still see quite a few recognizable words in there as well.
4) USB (Upper Sideband) is the typical default for CW reception.

Reason: No reason

frankcarril@aol.com
Posts: 5
Joined: Fri Dec 08, 2017 3:48 pm

Re: Using RSP Pro 2 for CW RTTY decoding?

Post by frankcarril@aol.com » Thu Jan 04, 2018 4:28 pm

Thank for your help, its got me to a place where I am looped back in receiving a signal..

I read your 4 suggestions... the one I think is keeping me from receiving a good signal is below.

3) Garbled text can occur, because the timing parameter settings for RTTY or Morse Code decoding in FLDigi are not within the range needed for the signal being received; or

I do not know these settings... and or they the same for RTTY and Morse Code ??

Sorry I been absent, but have some obligation to take care of my wife. So I am often off the air for a while, but want to stick with it..
Thanks for you help.. will be awaiting what you say about the Settings..
Thanks
Frank c
Las Cruces, NM K5NMH
Last edited by frankcarril@aol.com on Thu Jan 01, 1970 12:00 am, edited 0 times in total.
Reason: No reason

Post Reply