David, There’s a bit more work they’ll be doing before I start. Lots of coding going on here… Simon Brown G4ELI http://sdr-radio.com

I can't see this SDR lark ever really taking off Phil. Cathy ;)

David, Thanks - I'm in close contact with the SDRplay support team and will attend to the SDRplay once this API and new code is available for me. At this very moment in time (07:29 AM, Wednesday

David, Thanks - I'm in close contact with the SDRplay support team and will attend to the SDRplay once this API and new code is available for me. At this very moment in time (07:29 AM, Wednesday

From RTL-SDR.com .... "The SDRplay team have recently released a major update to their API and drivers. The new version is 1.8.0 and they write that it should remove the DC offset, reduce in band

So ein radio badge scheint ne coole hausnummer zu sein CCC ... hmmm chaos computer club?? Kann man den badge da ordern?? Soll kompatibel zum hack rf sein Und 50mhz bis 4 gig tx/rx können Ich

Thanks Simon for the help. What I found was that I made the record directory the same as for my other software, ie. HDSDR and ELAD S2. That caused your scan process to error, probably on one of the

Although I am near certain that I never changed that setting when I achieved success the first time, that was the secret handshake. I set docking to "immediate" and voila... I can get it to dock at

For what it is worth I have best success with Immediate Docking. Colin VK5HI.

What do you have the docking set as? Under Display/Docking I have mine on smart... Paul - NN4F Paul Jones - NN4F Ridgeville, SC EM93TB Email: paul@... Facebook.com/groups/sdrplay

I have SDR Console figured out and running great. But one thing escapes me. From the default layout, I would like to move (and dock) the VFO tuning display ABOVE the top of the frequency explorer

OK… I’ll redo the line for RitOffset. BTW adding the new line in Status6 didn’t change anything. I see Omni-Rig runs as a process rather than an application. j

Hi Jerome. I remember in one of your previous replies that you changed the “pmRitOffset” command as the verify program reported an invalid format type (vfTextUD). This IS a valid format – it

Hi Jerome. I remember in one of your previous replies that you changed the “pmRitOffset” command as the verify program reported an invalid format type (vfTextUD). This IS a valid format – it

OK… I repeated the three tests with everything shutdown except the rig and Client.exe. The results were exactly the same as with Omni-Rig and Console running — so no change there. I will make

Oops… That should have been: [STATUS6] Command=(TX;) ReplyEnd=(;) Validate=(TX.;) Flag1=(..0.)|pmRx Flag2=(..1.)|pmTx Flag3=(..2.)|pmTx Flag4=(..3.)|pmTx Regards Gerard (vk3cg/vk3grs)

Hi Jerome. I will assume that the transceiver went into transmit mode when the Set button next to TX was pressed (let me know if it did not). Those replies are a bit different to what the manual I

Cal, Thanks for helping. Yes I think that is the solution. I just read your earlier post and changed to standard drivers and it seemed to resolve the problem. I will try again in the morning (I am UK

Eeeeek! second one should be 5458323B and third, 5458333B Sorry… j.

950 in receive 5458303B 950 in transmit 548323B 950 in receive TX set pushed 5483333B j.