Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LimeSDR Plugin - Failed build #133

Closed
FFY00 opened this issue Feb 4, 2018 · 10 comments
Closed

LimeSDR Plugin - Failed build #133

FFY00 opened this issue Feb 4, 2018 · 10 comments
Milestone

Comments

@FFY00
Copy link
Contributor

FFY00 commented Feb 4, 2018

I have the latest drivers from git.

[ 44%] Building CXX object sdrgui/CMakeFiles/sdrgui.dir/gui/commandkeyreceiver.cpp.o
/home/anubis/git/sdrangel/plugins/samplesink/limesdroutput/limesdroutput.cpp: In member function ‘virtual bool LimeSDROutput::handleMessage(const Message&)’:
/home/anubis/git/sdrangel/plugins/samplesink/limesdroutput/limesdroutput.cpp:632:32: error: ‘struct lms_stream_status_t’ has no member named ‘sampleRate’
                         status.sampleRate,
                                ^~~~~~~~~~
[ 44%] Building CXX object sdrgui/CMakeFiles/sdrgui.dir/gui/commandoutputdialog.cpp.o
/home/anubis/git/sdrangel/plugins/samplesource/limesdrinput/limesdrinput.cpp: In member function ‘virtual bool LimeSDRInput::handleMessage(const Message&)’:
/home/anubis/git/sdrangel/plugins/samplesource/limesdrinput/limesdrinput.cpp:631:32: error: ‘struct lms_stream_status_t’ has no member named ‘sampleRate’
                         status.sampleRate,
                                ^~~~~~~~~~
@f4exb f4exb added the question label Feb 4, 2018
@f4exb
Copy link
Owner

f4exb commented Feb 4, 2018

Obviously lms_stream_status_t is in the LimeSuite API amd good chances are that your copy or clone is outdated. See: http://docs.myriadrf.org/LMS_API/structlms__stream__status__t.html

@f4exb
Copy link
Owner

f4exb commented Feb 5, 2018

In fact it is the opposite. sampleRate has been removed from the structure.
As a quick fix try to check out commit 04b57e0 in LimeSuite.
It does not look like it is used so I can probably remove it

@f4exb
Copy link
Owner

f4exb commented Feb 5, 2018

Removed on dev branch

@f4exb f4exb removed the question label Feb 5, 2018
@f4exb f4exb added this to the v3.12.0 milestone Feb 5, 2018
@FFY00
Copy link
Contributor Author

FFY00 commented Feb 5, 2018

Thanks, I'm able to build the dev branch now. Although I can only tune the LimeSDR between 3kHz and 30kHz. The main frequency is synchronized with the NCO frequency.

@f4exb
Copy link
Owner

f4exb commented Feb 5, 2018

I don't know why it is doing that. This is a regression of LimeSuite maybe try to check out an earlier commit. Frequency is in kHz so actually this is 3.8 to 30 MHz.

It looks like it was introduced by myriadrf/LimeSuite@c02f435

So do git checkout ebd027169defc9689d1eefa0f57d4df617b7cc4d in LimeSuite then build and install again. Then rebuild SDRangel. This should fix the issue.

f4exb referenced this issue in myriadrf/LimeSuite Feb 5, 2018
@f4exb
Copy link
Owner

f4exb commented Feb 24, 2018

The frequency limit problem appears with the Mini version only along with other problems. It seems they did a big mess for the Mini in the recent versions of LimeSuite. The "big" one seems unaffected.

@FFY00
Copy link
Contributor Author

FFY00 commented Feb 24, 2018

What do you mean? I have a normal LimeSDR.

@f4exb
Copy link
Owner

f4exb commented Feb 25, 2018

Then you should be able to tune any frequency in the available range (30 to 3800 MHz)

@FFY00
Copy link
Contributor Author

FFY00 commented Feb 25, 2018

When I tested it I wasn't able to. I'll try again when I have time.

@f4exb
Copy link
Owner

f4exb commented Mar 13, 2018

The frequency issue (solved in Lime Suite) is being followed up on #139
This one can be closed.

@f4exb f4exb closed this as completed Mar 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants