usb_open error -12 - Can't open RTL SDR device #1 - Can FMP24 Work With SpyVerter - DSD+ FastLane 2.155

[simpilo]

I have looked in the help file for FMP24 there is no mention of frequency offset for HF up converter usage. If you want to listen to a radio station on 1000khz then you must use 121.000mhz with a 120mhz LO feed into the RTL-SDR from the Spyverter. Just that simple really.

 

[AB9NN]

I fully understand the offset. Long-time ham, lots of repeater offset programming over the years and years. But it doesn't work. For a target freq of 1.160 Mhz I keyed 121.160 and 1.160 Mhz and neither work. On SDR Console and another radio - booming signals. see my print-screen below. It's like FMP24 doesn't get the converted signal passed through from the SpyVerter with the 120 Mhz added to it. It just works directly with the RTL-SDR and it won't go that low. Also - here is my command line used: Using 121.600 did raise my hopes - but - no - alas I think it was only some aircraft band or similiar traffic spikes that I saw... sigh...

FMP24 -i2 -o1 -f121.600 -b12.5

It starts in FM and I do a D to switch to AM.

 

[simpilo]

I see something I never seen before in your image. It appears your RTL-SDR is not locking for 5.07MHZ. I have no clue why. Seems odd to me. My worse guess will be your RTL-SDR might be croaking. Looks abnormal.

 

[slicerwizard]

I fully understand the offset. Long-time ham, lots of repeater offset programming over the years and years. But it doesn't work. For a target freq of 1.160 Mhz I keyed 121.160 and 1.160 Mhz and neither work. On SDR Console and another radio - booming signals. see my print-screen below.

In the last screen shot, I don't see FMP24 tuned to much of anything. Can't read all of the fuzzy screen cap, but it sure doesn't show 121 dot anything in the FMP24 title bar. The console window is complaining about no PLL lock at what, 50.7 MHz? What's going on?

FMP24 -i2 -o1 -f121.600 -b12.5

You're tuning to 120 MHz plus 1600 kHz to listen to 1160 kHz?

 

[AB9NN]

No PLL Lock - yes - don't know what that is from. It only happens when I hand key the frequency - direct entry. If I use a batch file, like the one below, it does not throw that error. See the print screens below. First is SDR Console to confirm signal at 1.270 Mhz. Then see FMP24 screens - same dongle - same freq. One trying 121.270 and one trying 1.270. It logically should be one or the other. Neither shows a signal. I am trying to tune HF and using an AM Broadcast signal as a strong known source for a reference to determine if my coding scheme works or not.

FMP24 -i2 -o1 -f121.270 -b12.5

 

[simpilo]

AB9NN, I can't wrap my head around it. If that dongle is the only one doing that and another dongle doesn't have a problem then I would replace that dongle. I'm baffled.

 

[slicerwizard]

I don't see anything that shows that SDR Console isn't powering the bias T.

 

[AB9NN]

The SpyVerter doesn't run on bias T. It runs on a wall wart (external power supply). Dongle works perfectly on HF when the SpyVerter is used with SDR Console but not with FMP24. Given that, I see no need to replace it.