Many thanks for the updated version Marco. Nice job !

#sdrsharp #plugin #update

I feel stupid, sorry ... I thought that it behaved like the S-meter plugin that you already see the picture before playing ... I should run it just in case. Thanks, it works like a charm, nice!

#sdrsharp #plugin #update

Hi Juan, thank you for the feedback, I am glad my work is somehow useful to the community. Magic-Eye plugin, is built on .NET 4.6 as you noted. This version, has been published to be compatible with .

#sdrsharp #plugin #update

Hi Marco Before my feedback I want to thank your for the effort developing this plugin, also thanks to all the programmers that, pro-bono, are making an effort to make our life easier when using SDR#

#sdrsharp #plugin #update

Hi SDR# enthusiasts, there is a new version of the Magic-Eye SDR# plugin, v 1.6, with bugfixes and some graphical improvements. This version, fixed previous incompatibility with the newest SDR# Studio

#sdrsharp #plugin #update

Yes, and it would be mint. As Youssef said, the 'real' freq should be 'returned' when a set freq command is been sent. I don't know how complex it is to build this in the airpsy API, but it could turn

#update #airspyr2 #firmware

When the front end is all derived from one single oscillator for sample rate and synthesizer correcting for its error is very easy within the SDR software. And then synthesizer step size can be comput

#update #airspyr2 #firmware

Just like I did yesterday for the Lime - Lime has up to 30 Hz steps sizes at 3.5 GHz ☹ . Simon Brown, G4ELI https://www.sdr-radio.com

#update #airspyr2 #firmware

You could generate a new API entry that does that. Then compatibility backwards and forwards would exist. (And it would shut up people who try to use exotic deep in the noise communications technology

#update #airspyr2 #firmware

About half of that in at 145 MHz in the Airspy. To compensate properly for this offset, the set frequency command should return the actual tuned frequency. This requires changing the command handling

#update #airspyr2 #firmware

(It is - about +/- 7 Hz if I recall correctly.) In theory a suitably manic and precision addicted developer for SDRSharp could provide the offset to the display and readout software by calculating the

#update #airspyr2 #firmware

It is.

#update #airspyr2 #firmware

I suspect it is R820T2 synthesizer step size related. {o.o}

#update #airspyr2 #firmware

What is the new offset at 145 MHz?

#update #airspyr2 #firmware

Prog, I am your guest, I do ! Before the new cal @1,5GHz (note that a 40dB atten is put between the output of the bodnar and the R2to avoid saturation) After the new cal (we went from -3,08 to -3,04)

#update #airspyr2 #firmware

If you want to save time, just follow the recommendation.

#update #airspyr2 #firmware

I made it also at 800MHz (max of bodnar without using harmonics) same result exactly.

#update #airspyr2 #firmware

Why would you do that? Calibrate at 1500 MHz for the best resolution. Set the GPSDO to 500 MHz and use the third harmonic.

#update #airspyr2 #firmware

Hi, I just tried the following setup : GPSDO Leobodnar locked on 145.000.000 MHz Airspy R2 with latest improved firmware a) without ext 10MHz ref -> running AirspyCalibrate, following the procedure ->

#update #airspyr2 #firmware

Oh Sorry @Bill Dailey I misunderstood your question. The Pi 4 heatsink is Aluminium Armour for Raspberry Pi 4. Not expensive, easy fit and reduced operating temp considerably. https://www.banggood.com

#airspyr2 #firmware #update