You shall not go lower than 70MHz!!

[fla5hrat]

A genuine strange one now although I can see where it's coming from and if anyone can tell me what they'd like to see screen dumps, logs, whatever happy to provide.

New Pluto+ owner - not an everyday user of sdrA but I'd like to be, getting more proficient. Anyway I have a Ham It Up from Nooelec in the chain and not issues with using it with hackrf on sdrA, no issues with sdrconsole and no issues with sdrconsole with the Pluto+ and the hamitup either.

The weird thing is when I go into the transverter option and set the offset, I cannot scroll any lower than 70MHz, if I want to go to 10MHz I have to set Freq to 110MHz then scroll the "hundred" down to zero...even then the spectrum window stays at "70MHz" and when I mouse over my tricky 10MHz it resets (no clicking, just mouse over) to 70MHz.

I'm wondering if there's a hard coded frequency limit attached to "PlutoSDR" which is what it sounds like, but where I'd guess having a transverter value would cancel that setting, it doesn't seem to be in this case.

I'd love to get this networked device working happily...next step if this gets resolved is working out the buffering.

The PlutoSDR entry on the wiki only mentions the Uri in user args section,so I don't know if there are any other args I can put there to fix? I can see that it's mentioned the upper and lower limits which is clearly what's at play here, is there an override? Or is there somewhere in the source I can change a T to F and compile?

[srcejon]

What exact value did you set for the transverter option?

See: https://github.com/f4exb/sdrangel/blob/ ... rdialog.md

[fla5hrat]

I'm a f#$^#@ng idiot - I was treating the main freq window 000,000,000 as Hz not KHz and the transverter window 000,000,000,000 as KHz not Hz - so sorry!