On Jul 17, 2021, at 11:54 AM, James C. Hall, MD <heartdoc@...> wrote:

Yes, thanks for that clarification, Bill. I’m just getting started and now understand more than I did ! HI

I wouldn’t need polarization diversity (yet) - I just have a couple KLM 13B2’s. :)

73, Jamie

WB4YDL

On Jul 17, 2021, at 11:37 AM, Bill Somerville <g4wjs@...> wrote:



Hi Jamie,

let me clarify a couple of things.

The qthid application is not an SDR console, all it does is allow the user to configure the parameters of the FCD including the LO frequency. MAP65 accepts the raw I/Q output of the FCD and the qthid application is not involved in that path. The qthid application is designed to be launched by applications like MAP65 to adjust the FCD parameters.

ExtIO is an API (Application Programming Interface) designed by the author of Winrad, and also adopted by HDSDR and others. It intent is to abstract away the differences between SDR hardware so that SRD console applications can talk to a common interface. Providers of SDR hardware might also provide an implementation of ExtIO for their devices so existing SDR consoles should be able to talk to their SDRs.

I don't know SDR# that well but if it is capable of delivering a 96,000 Sa/s I/Q stream to an audio device; then configured like that and using something like VAC would allow it to be used with MAP65 in single polarization mode. Polarization diversity via that route is unlikely as I doubt SDR# is able to provide the necessary dual channel I/Q synchronized output delivered as a 4-channel audio output (synchronized and interleaved), for a start it would require SDR# to control two receivers both sharing a common clock input (synchronized).

73
Bill
G4WJS.

On 17/07/2021 16:58, James C. Hall, MD wrote:

Thanks Bill for your reply. Interesting stuff.

Looking around Airspy and the internet, I’m not finding a console program in the same vein as that little one with Funcube dongle. It sorta defaults to SDR#. There is an ExtIO app for other programs (but not Map65). I’ll look around - maybe SDR# outputs at the required I/Q sample rate and I could use an VAC from there (never tried that - but I’m willing).

I’ll dig deeper and get back when I find something. If I have to, I can always put the FCD+ back in line.

73, Jamie
WB4YDL

On Jul 17, 2021, at 5:24 AM, Bill Somerville <g4wjs@...> wrote:

On 17/07/2021 02:01, James C. Hall, MD wrote:

Well I finally got a little time to download the rc that includes Map65 v3 in order to re-kindle my interest in EME. I want to try the new Q65 mode. (I also need South America to finish WAC)

I have been using my antennas on LEO sats (added a 432 MHz antenna on the cross boom that I had before for satellites) and loving the new paradigm of using a SDR receiver direct as a “2nd radio” in SatPC32. I use an Airspy R2. It’s very cool to be able to see the receive passband on SDR Console v3 and use your mouse wheel to fine tune on a chosen signal. You have to use a virtual com port “cable” to get this all to work and that’s something new for me - and was tough to understand at first.

So now I’m trying to get this to work with Map65. I can’t seem to directly choose something like Airspy, although I did see the Funcube dongle + (which I also have). Do I need to use a ‘middle program’ like SDR Console to connect the two ? I saw the Linrad stuff and that’s a non-starter with me. Before, I just had a connection to a receive port I added to the back of my FT-847. My antennas are simple - a pair of KLM 13B2’s.

If I need to post this to the moon net forum, let me know.

73, Jamie
WB4YDL

Hi Jamie,

MAP65 requires I/Q data at 96,000 Sa/s, either one I/Q pair for single polarization or two synchronized I/Q pairs (must be interleaved) for polarization diversity reception. Alternatively there is a dedicated UDP network protocol that Linrad uses to pass I/Q data to a client, that too is supported by MAP65.

So if your SDR console application is capable of outputting I/Q data at 96,000 Sa/s you can feed that to MAP65 via an audio loopback connection like VB Cable or VAC, you may also have some success letting Windows or the loopback application resample the I/Q data to 96,000 Sa/s but that may be somewhat limiting and certainly cannot increase the bandwidth if the input rate is less than 96,000 Sa/s.

As you note, the FCD+ is supported, note that can provide 96,000 Sa/s I/Q data directly with only a small application  (fqthid) to set the LO frequency of the FCD+. Note that the newer FCD Pro+ has a 192,000 Sa/s I?Q output rate, I guess it will work but will get down-sampled to 96,000 Sa/s by Windows or the audio loopback application.

Note that using Linrad to provide the I/Q feed(s) to MAP65 has one significant benefit as Linrad has an excellent noise-blanker implementation.

73
Bill
G4WJS.

Thanks Bill for your reply. Interesting stuff.

Looking around Airspy and the internet, I’m not finding a console program in the same vein as that little one with Funcube dongle. It sorta defaults to SDR#. There is an ExtIO app for other programs (but not Map65). I’ll look around - maybe SDR# outputs at the required I/Q sample rate and I could use an VAC from there (never tried that - but I’m willing).

I’ll dig deeper and get back when I find something. If I have to, I can always put the FCD+ back in line.

73, Jamie
WB4YDL

On Jul 17, 2021, at 5:24 AM, Bill Somerville <g4wjs@...> wrote:

On 17/07/2021 02:01, James C. Hall, MD wrote:

Well I finally got a little time to download the rc that includes Map65 v3 in order to re-kindle my interest in EME. I want to try the new Q65 mode. (I also need South America to finish WAC)

I have been using my antennas on LEO sats (added a 432 MHz antenna on the cross boom that I had before for satellites) and loving the new paradigm of using a SDR receiver direct as a “2nd radioâ€&#65533; in SatPC32. I use an Airspy R2. It’s very cool to be able to see the receive passband on SDR Console v3 and use your mouse wheel to fine tune on a chosen signal. You have to use a virtual com port “cableâ€&#65533; to get this all to work and that’s something new for me - and was tough to understand at first.

So now I’m trying to get this to work with Map65. I can’t seem to directly choose something like Airspy, although I did see the Funcube dongle + (which I also have). Do I need to use a ‘middle program’ like SDR Console to connect the two ? I saw the Linrad stuff and that’s a non-starter with me. Before, I just had a connection to a receive port I added to the back of my FT-847. My antennas are simple - a pair of KLM 13B2’s.

If I need to post this to the moon net forum, let me know.

73, Jamie
WB4YDL

Hi Jamie,

MAP65 requires I/Q data at 96,000 Sa/s, either one I/Q pair for single polarization or two synchronized I/Q pairs (must be interleaved) for polarization diversity reception. Alternatively there is a dedicated UDP network protocol that Linrad uses to pass I/Q data to a client, that too is supported by MAP65.

So if your SDR console application is capable of outputting I/Q data at 96,000 Sa/s you can feed that to MAP65 via an audio loopback connection like VB Cable or VAC, you may also have some success letting Windows or the loopback application resample the I/Q data to 96,000 Sa/s but that may be somewhat limiting and certainly cannot increase the bandwidth if the input rate is less than 96,000 Sa/s.

As you note, the FCD+ is supported, note that can provide 96,000 Sa/s I/Q data directly with only a small application (fqthid) to set the LO frequency of the FCD+. Note that the newer FCD Pro+ has a 192,000 Sa/s I?Q output rate, I guess it will work but will get down-sampled to 96,000 Sa/s by Windows or the audio loopback application.

Note that using Linrad to provide the I/Q feed(s) to MAP65 has one significant benefit as Linrad has an excellent noise-blanker implementation.

73
Bill
G4WJS.

On 7/17/2021 11:24 AM, Karza wrote:
> Of course you can still work on JT9 or JT65modes, but cannot do both at
> the same time.

But why would you want to if newer modes like FST4 and Q65 are superior?

73, Jim K9YC

Looking now  at PSKReporter of JT65 on 2m I find stations reporting: ,,
 144.114,  144.116, 144.117
144.120, 144.121, 144.122, 144.127, 144.128,
 144.133,  144.134,
144.170, 144.181.
What are the official JT65 2m frequencies? On which frequencies shell I call CQ to get an answer?

Amos 4X4MF

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Ralph Katz
Sent: 17. heinäkuutata 2021 20:46
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] #JT9+JT65 combined menu option

On Jul 17, 2021, at 11:37 AM, Bill Somerville <g4wjs@...> wrote:



Hi Jamie,

let me clarify a couple of things.

The qthid application is not an SDR console, all it does is allow the user to configure the parameters of the FCD including the LO frequency. MAP65 accepts the raw I/Q output of the FCD and the qthid application is not involved in that path. The qthid application is designed to be launched by applications like MAP65 to adjust the FCD parameters.

ExtIO is an API (Application Programming Interface) designed by the author of Winrad, and also adopted by HDSDR and others. It intent is to abstract away the differences between SDR hardware so that SRD console applications can talk to a common interface. Providers of SDR hardware might also provide an implementation of ExtIO for their devices so existing SDR consoles should be able to talk to their SDRs.

I don't know SDR# that well but if it is capable of delivering a 96,000 Sa/s I/Q stream to an audio device; then configured like that and using something like VAC would allow it to be used with MAP65 in single polarization mode. Polarization diversity via that route is unlikely as I doubt SDR# is able to provide the necessary dual channel I/Q synchronized output delivered as a 4-channel audio output (synchronized and interleaved), for a start it would require SDR# to control two receivers both sharing a common clock input (synchronized).

73
Bill
G4WJS.

On 17/07/2021 16:58, James C. Hall, MD wrote:

Thanks Bill for your reply. Interesting stuff.

Looking around Airspy and the internet, I’m not finding a console program in the same vein as that little one with Funcube dongle. It sorta defaults to SDR#. There is an ExtIO app for other programs (but not Map65). I’ll look around - maybe SDR# outputs at the required I/Q sample rate and I could use an VAC from there (never tried that - but I’m willing).

I’ll dig deeper and get back when I find something. If I have to, I can always put the FCD+ back in line.

73, Jamie
WB4YDL

On Jul 17, 2021, at 5:24 AM, Bill Somerville <g4wjs@...> wrote:

On 17/07/2021 02:01, James C. Hall, MD wrote:

Well I finally got a little time to download the rc that includes Map65 v3 in order to re-kindle my interest in EME. I want to try the new Q65 mode. (I also need South America to finish WAC)

I have been using my antennas on LEO sats (added a 432 MHz antenna on the cross boom that I had before for satellites) and loving the new paradigm of using a SDR receiver direct as a “2nd radio” in SatPC32. I use an Airspy R2. It’s very cool to be able to see the receive passband on SDR Console v3 and use your mouse wheel to fine tune on a chosen signal. You have to use a virtual com port “cable” to get this all to work and that’s something new for me - and was tough to understand at first.

So now I’m trying to get this to work with Map65. I can’t seem to directly choose something like Airspy, although I did see the Funcube dongle + (which I also have). Do I need to use a ‘middle program’ like SDR Console to connect the two ? I saw the Linrad stuff and that’s a non-starter with me. Before, I just had a connection to a receive port I added to the back of my FT-847. My antennas are simple - a pair of KLM 13B2’s.

If I need to post this to the moon net forum, let me know.

73, Jamie
WB4YDL

Hi Jamie,

MAP65 requires I/Q data at 96,000 Sa/s, either one I/Q pair for single polarization or two synchronized I/Q pairs (must be interleaved) for polarization diversity reception. Alternatively there is a dedicated UDP network protocol that Linrad uses to pass I/Q data to a client, that too is supported by MAP65.

So if your SDR console application is capable of outputting I/Q data at 96,000 Sa/s you can feed that to MAP65 via an audio loopback connection like VB Cable or VAC, you may also have some success letting Windows or the loopback application resample the I/Q data to 96,000 Sa/s but that may be somewhat limiting and certainly cannot increase the bandwidth if the input rate is less than 96,000 Sa/s.

As you note, the FCD+ is supported, note that can provide 96,000 Sa/s I/Q data directly with only a small application  (fqthid) to set the LO frequency of the FCD+. Note that the newer FCD Pro+ has a 192,000 Sa/s I?Q output rate, I guess it will work but will get down-sampled to 96,000 Sa/s by Windows or the audio loopback application.

Note that using Linrad to provide the I/Q feed(s) to MAP65 has one significant benefit as Linrad has an excellent noise-blanker implementation.

73
Bill
G4WJS.