Add new comment

I'll pull the new commits this evening and give it a shot. I'm afraid I'm not a python person so my debugging help is somewhat limited.

The LO value being negative for downconverters makes sense and also explains exactly what I was seeing. The value is stored internally as a 32 bit signed number. I had found that an LO value of +2297MHz would give be pretty close to the correct frequency. Turns out that is 2^32-1998000000Hz. Thanks for the pointer.

BTW, I wanted to complement you on the very useful application. Nitpicking and rough edges aside, it is exactly what I need. Thanks for all the effort.