# New error message from LimeSuiteCalibrate

**URL:** <https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342>\
**Category:** LimeSDR\
**Created:** [16 June 2017 20:58 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342 "2017-06-16T20:58:49Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertkb](https://avatars.discourse-cdn.com/v4/letter/r/b19c9b/32.png) [@robertkb](https://discourse.myriadrf.org/u/robertkb)\
**Post date:** [16 June 2017 20:58 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/1 "2017-06-16T20:58:49Z")

</div>

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

The corresponding SoapySDRUtil versions are:  
Lib Version: v0.6.0-gfcecfdae (April, succeeds)  
Lib Version: v0.6.0-g2f6a449e (June, fails)

Does anybody have any ideas about why this is happening?

thanks.

---

<div class="post-metadata">

**Author:** ![Kc7noa](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/kc7noa/32/144_2.png) [@Kc7noa](https://discourse.myriadrf.org/u/Kc7noa)\
**Post date:** [16 June 2017 23:07 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/2 "2017-06-16T23:07:05Z")

</div>

Same here …

> [@Something wrong with calibration procedure](https://discourse.myriadrf.org/t/something-wrong-with-calibration-procedure/1163/34):
>
> I was able to record where the cal failure takes place. After working on other things for a few months, I got back to the LimeSDR the other day. I updated the firmware and rebuilt SoapySDR and LimeSuite from git (this is on Ubuntu 16.04). The LimeSuite Device Info screen says: Firmware: 3 Hardware: 4 Protocol: 1 Gateware: 2 Gateware rev: 8 And SoapySDRUtil --info says: ###################################################### Soapy SDR – the SDR abstraction library ######…

Can you back date (and compile) limesuite and find what version worked last?

---

<div class="post-metadata">

**Author:** ![Kc7noa](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/kc7noa/32/144_2.png) [@Kc7noa](https://discourse.myriadrf.org/u/Kc7noa)\
**Post date:** [16 June 2017 23:08 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/3 "2017-06-16T23:08:22Z")

</div>

Oh … im sorry …

Is it a Soapysdr issue? …

---

<div class="post-metadata">

**Author:** ![Kc7noa](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/kc7noa/32/144_2.png) [@Kc7noa](https://discourse.myriadrf.org/u/Kc7noa)\
**Post date:** [16 June 2017 23:51 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/4 "2017-06-16T23:51:30Z")

</div>

Looks like several minor changes to soapysdr from April 10th on … hope its not too hard to find the last working version

> **[pothosware/SoapySDR](https://github.com/pothosware/SoapySDR/commits/master)**
>
> Vendor and platform neutral SDR support library. Contribute to pothosware/SoapySDR development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![robertkb](https://avatars.discourse-cdn.com/v4/letter/r/b19c9b/32.png) [@robertkb](https://discourse.myriadrf.org/u/robertkb)\
**Post date:** [17 June 2017 12:58 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/5 "2017-06-17T12:58:14Z")

</div>

Could somebody from Myriad RF please comment on the question raised in this thread?

---

<div class="post-metadata">

**Author:** ![andrewback](https://avatars.discourse-cdn.com/v4/letter/a/22d042/32.png) [@andrewback](https://discourse.myriadrf.org/u/andrewback)\
**Post date:** [17 June 2017 13:21 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/6 "2017-06-17T13:21:22Z")

</div>

@IgnasJ, @joshblum, perhaps one of you could comment on this error.

---

<div class="post-metadata">

**Author:** ![hTo137](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@hTo137](https://discourse.myriadrf.org/u/hTo137)\
**Post date:** [17 June 2017 17:26 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/7 "2017-06-17T17:26:58Z")

</div>

> [@robertkb](#):
>
> Does anybody have any ideas about why this is happening?

Yes, somone knows.

> <https://github.com/myriadrf/LimeSuite/issues/128>
>
> The commit note said: 
> commit 28abe7b3e8f0056aac030ea37e0ac6952f0553aa
> Author:… Josh Blum \<josh@joshknows.com\>
> Date: Mon May 22 17:48:15 2017 -0700
> 
> remove apply/store corrections
>     
> \* these were used with the older calibration utility
> 
> \--------------------
> 
> I was using these too.  
> 
> In the absence of a specification or reference manual, it is hard to know what features 
> are commitments to the programmer and which features will disappear.  
> 
> I use the STORE\_TX and STORE\_RX corrections because I have seen problems (that is, 
> dreadful settings) with the built-in calibration routines.  
> 
> Please put these keyword selections back. It is very very hard to write software for a moving
> target.  
> 
> matt

---

<div class="post-metadata">

**Author:** ![robertkb](https://avatars.discourse-cdn.com/v4/letter/r/b19c9b/32.png) [@robertkb](https://discourse.myriadrf.org/u/robertkb)\
**Post date:** [17 June 2017 20:57 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/8 "2017-06-17T20:57:57Z")

</div>

Thank you for pointing this out.

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?

---

<div class="post-metadata">

**Author:** ![hTo137](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@hTo137](https://discourse.myriadrf.org/u/hTo137)\
**Post date:** [17 June 2017 21:21 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/9 "2017-06-17T21:21:36Z")

</div>

Have you already tried

`LimeUtil --cal`

Have seen that mentioned here.

---

<div class="post-metadata">

**Author:** ![Kc7noa](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/kc7noa/32/144_2.png) [@Kc7noa](https://discourse.myriadrf.org/u/Kc7noa)\
**Post date:** [18 June 2017 17:42 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/10 "2017-06-18T17:42:02Z")

</div>

Well … need to find the LimeUtil code and change the sample rate … its out of range for my USB2 buss

: | 0 | 2047 |  
############################################################  
SetFrequency using cache values vco:0, csw:13  
############################################################  
Tx calibration values found in cache:  
| DC | GAIN | PHASE  
—±----±-----±-----  
I: | 0 | 2047 | 0  
Q: | 0 | 2047 |  
############################################################  
SetFrequency using cache values vco:0, csw:13  
Error tuning (skipping): Cannot set desired sample rate. CGEN clock out of range  
SetFrequency using cache values vco:0, csw:13  
Error tuning (skipping): Cannot set desired sample rate. CGEN clock out of range  
SetFrequency using cache values vco:0, csw:13  
############################################################  
Tx calibration values found in cache:  
| DC | GAIN | PHASE  
—±----±-----±-----  
I: | 0 | 2047 | 0  
Q: | 0 | 2047 |  
############################################################  
SetFrequency using cache values vco:0, csw:13  
############################################################  
Tx calibration values found in cache:  
| DC | GAIN | PHASE  
—±----±-----±-----  
I: | 0 | 2047 | 0  
Q: | 0 | 2047 |  
############################################################

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@  
@@ Calibrating for freq = 6.2 MHz  
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

SetFrequency using cache values vco:0, csw:13  
Error tuning (skipping): Cannot set desired sample rate. CGEN clock out of range  
SetFrequency using cache values vco:0, csw:13  
Error tuning (skipping): Cannot set desired sample rate. CGEN clock out of range  
SetFrequency using cache values vco:0, csw:13  
############################################################  
Tx calibration values found in cache:  
| DC | GAIN | PHASE  
—±----±-----±-----  
I: | 0 | 2047 | 0  
Q: | 0 | 2047 |  
############################################################  
SetFrequency using cache values vco:0, csw:13  
############################################################  
Tx calibration values found in cache:  
| DC | GAIN | PHASE  
—±----±-----±-----  
I: | 0 | 2047 | 0  
Q: | 0 | 2047 |  
############################################################  
SetFrequency using cache values vco:0, csw:13  
Error tuning (skipping): Cannot set desired sample rate. CGEN clock out of range  
SetFrequency using cache values vco:0, csw:13  
Error tuning (skipping): Cannot set desired sample rate. CGEN clock out of range  
SetFrequency using cache values vco:0, csw:13  
############################################################  
Tx calibration values found in cache:  
| DC | GAIN | PHASE  
—±----±-----±-----  
I: | 0 | 2047 | 0  
Q: | 0 | 2047 |  
############################################################  
SetFrequency using cache values vco:0, csw:13  
############################################################  
Tx calibration values found in cache:  
| DC | GAIN | PHASE  
—±----±-----±-----  
I: | 0 | 2047 | 0  
Q: | 0 | 2047 |

---

<div class="post-metadata">

**Author:** ![Axeman](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/axeman/32/728_2.png) [@Axeman](https://discourse.myriadrf.org/u/Axeman)\
**Post date:** [19 June 2017 18:37 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/11 "2017-06-19T18:37:55Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![hTo137](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@hTo137](https://discourse.myriadrf.org/u/hTo137)\
**Post date:** [19 June 2017 20:16 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/12 "2017-06-19T20:16:28Z")

</div>

> [@Axeman](#):
>
> 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.

---

<div class="post-metadata">

**Author:** ![Kc7noa](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/kc7noa/32/144_2.png) [@Kc7noa](https://discourse.myriadrf.org/u/Kc7noa)\
**Post date:** [19 June 2017 20:24 UTC](https://discourse.myriadrf.org/t/new-error-message-from-limesuitecalibrate/1342/13 "2017-06-19T20:24:25Z")

</div>

> [@Axeman](#):
>
> 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.

Same here … just found that the LimeUtil --cal seems to function so i set it to run to 3.8ghz …  
Prolly take several hours to complete i sapose …