The following error message does not appear when the calibration script is run against LimeUtil version v17.03.0-g798a81ac, built 2017-04-16; it does appear when the script is run against LimeUtil version17.03.0-g9eca76d1, built 2017-06-10:
Failed at 2090 MHz, skipping…
unknown setting key: STORE_RX_CORRECTIONS
Where 2090 MHz was the first frequency specified on the command line; all subsequent frequencies fail with this error message:
Failed at 2110 MHz, skipping…
ret=-1, flags=0, timeNs=0
I modified the python script LimeSuiteCalibrate so that it no longer calls
limeSDR.writeSetting(“STORE_RX_CORRECTIONS”, “true”)
or
limeSDR.writeSetting(“STORE_TX_CORRECTIONS”, “true”)
Now the first frequency succeeds, but all subsequent frequencies still fail with this message:
Failed at 2090.5 MHz, skipping…
ret=-1, flags=0, timeNs=0
Once again, the command I used was
LimeSuiteCalibrate --freqStart 2.090e9 --freqStop 2.101e9
I also have not been able to calibrate using the LimeSuiteGUI. Has anybody been able to get that to work?
When I hit the “Calibrate All” button, a window pops up and immediately disappears before any text becomes
visible in it, followed by an info window announcing “Calibration Finished”. What else needs to be configured for
this to work? Is there such a thing as a “calibration.ini” file somewhere?
LimeSuiteCalibrate still not working for me but after ‘LimeUtil --update’ and ‘git pull origin master’ on LimeSuite and soapysdr with a rebuild and reinstall this morning I can now ‘LimeUtil --cal --start XXX --stop XXX’ any range and it actually works. It was never reliable before.
Yeah the latest code makes a difference, and the latest gateware to match it.
In looking at other threads a lot of the screengrabs of LimeSuite FFT quicktest looks like people are getting versions mixed up between the gateware and LimeSuite. Zack set me straight on that. Very important that they match.
