Issues with USRP B200 #608
Labels
Comments
This was referenced Jan 17, 2019
|
I have a USRP B series device and would be happy to help. How can I contribute? |
|
Thank you @robisen1 ! The best way to start is to look at so it explicitly uses the B series for testing or to for automatic detection of attached USRPs. After that, attach your USRP and run the test e.g. from command line with For first we need to find out where exactly the crash happens. Please post the complete log/stacktrace for the test. Please also tell me what OS you are using. Ideally you could test it under Linux, Windows and OS X but any help is appreciated. 👍 |
|
I am using the MSI version for Windows but I am fine with running it on Ubuntu or any other OS you would recommend. Would Ubuntu be better for this?
Thanks,
Robi
On 3/12/2019 11:51:06 PM, Johannes Pohl <notifications@github.com> wrote:
Thank you @robisen1 [https://github.com/robisen1] !
The best way to start is to look at tests/device/TestUSRP.py and change line 20 to
return_code = usrp.open("type=b200")
so it explicitly uses the B series for testing or to
return_code = usrp.open("")
for automatic detection of attached USRPs.
After that, attach your USRP and run the test e.g. from command line with
python -m unittest tests/device/TestUSRP.py
For first we need to find out where exactly the crash happens. Please post the complete log/stacktrace for the test. Please also tell me what OS you are using. Ideally you could test it under Linux, Windows and OS X but any help is appreciated. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [#608 (comment)], or mute the thread [https://github.com/notifications/unsubscribe-auth/AGRdRSExJEdB1izVmdnSFdiEWVeEhM9Kks5vWJ_ZgaJpZM4aFGYE].
|
|
Ideally you would test it on Ubuntu (or any other linux distribution you prefer), since things are a bit easier to debug there. If we found the problem there we can verify if it works on your Windows machine too. |
|
will do
…On Wed, Mar 13, 2019 at 12:11 PM Johannes Pohl ***@***.***> wrote:
Ideally you would test it on Ubuntu (or any other linux distribution you
prefer), since things are a bit easier to debug there. If we found the
problem there we can verify if it works on your Windows machine too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRYVQ74-DjZxkq0ElWFYkEcoIKNsOks5vWU1MgaJpZM4aFGYE>
.
|
|
Sorry this took so long but I did install this on Ubuntu 18.04 and updated
the testUSRP.py. I tried both the type=b200 and the " " approaches and each
threw errors. It says it cannot the library usrp. I have installed
libuhd-dev
thoughts?
[image: Screenshot from 2019-03-30 22-43-54.png]
…On Tue, Mar 12, 2019 at 11:51 PM Johannes Pohl ***@***.***> wrote:
Thank you @robisen1 <https://github.com/robisen1> !
The best way to start is to look at tests/device/TestUSRP.py and change
line 20 to
return_code = usrp.open("type=b200")
so it explicitly uses the B series for testing or to
return_code = usrp.open("")
for automatic detection of attached USRPs.
------------------------------
After that, attach your USRP and run the test e.g. from command line with
python -m unittest tests/device/TestUSRP.py
For first we need to find out where exactly the crash happens. Please post
the *complete log/stacktrace* for the test. Please also tell me what *OS*
you are using. Ideally you could test it under Linux, Windows and OS X but
any help is appreciated. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRSExJEdB1izVmdnSFdiEWVeEhM9Kks5vWJ_ZgaJpZM4aFGYE>
.
|
|
You need to build the device extensions by calling: |
|
will do latter today. thanks. I was thinking that i need to build the uhd from source. |
|
I have everything now working. One thing I need to do before running the
build script was
sudo python3 /usr/lib/uhd/utils/uhd_images_downloader.py
btw I ran "python src/urh/cythonext/build.py" but it gave a error and said
run "/usr/lib/x86_64-linux-gnu/uhd/utils/uhd_images_downloader.py"" but
that file does not live there. it resides at "
/usr/lib/uhd/utils/uhd_images_downloader.py"
here is the b200 running on URH. BTW thanks and I hope this helps others.
[image: Screenshot from 2019-03-31 15-04-51.png]
…On Sun, Mar 31, 2019 at 3:16 AM Johannes Pohl ***@***.***> wrote:
You need to build the device extensions by calling:
python src/urh/cythonext/build.py
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRXleBdrLmbXQoyA8ugRm4ajTHzQRks5vcIrkgaJpZM4aFGYE>
.
|
|
The screenshot is not visible so what exactly do you mean by it is running on URH? Is the unit test passing or does it work in spectrum analyzer / record dialog? |
|
Its passes all tests. I can see signals with Spectrum Analyzer, I can
record signals, etc.
…On Sun, Mar 31, 2019, 4:00 PM Johannes Pohl ***@***.***> wrote:
The screenshot is not visible so what exactly do you mean by it is running
on URH? Is the unit test passing or does it work in spectrum analyzer /
record dialog?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRQQEBCaQKi9ydZLPrklCqQeeoIFHks5vcT3wgaJpZM4aFGYE>
.
|
|
I have a windows system. I can look at it on there. I dont think I have a
OSX system any more but I'll look.
…On Sun, Mar 31, 2019, 5:03 PM Johannes Pohl ***@***.***> wrote:
Very cool, thanks for your support so far! Any chance you can test it
under Windows and/or OS X too? The issues #589
<#589> and #577
<#577> indicate errors on these
systems.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRVzDJhDgfyC40ak2lGL8NVM0P2DPks5vcUzAgaJpZM4aFGYE>
.
|
|
Any news? |
|
I apologize for not doing this sooner. I attempted to install using pip in
python on two systems but keep getting a this error
" running build_ext
Finalizing options
building 'urh.cythonext.auto_interpretation' extension
creating build\temp.win-amd64-3.6
creating build\temp.win-amd64-3.6\Release
creating build\temp.win-amd64-3.6\Release\src
creating build\temp.win-amd64-3.6\Release\src\urh
creating build\temp.win-amd64-3.6\Release\src\urh\cythonext
C:\Anaconda2\envs\pyten36\Library\mingw-w64\bin\gcc.exe -mdll -O -Wall
-DMS_WIN64 -Ic:\anaconda2\envs\pyten36\include
-Ic:\anaconda2\envs\pyten36\include
-Ic:\anaconda2\envs\pyten36\lib\site-packages\numpy\core\include -c
src/urh/cythonext/auto_interpretation.cpp -o
build\temp.win-amd64-3.6\Release\src\urh\cythonext\auto_interpretation.o
/openmp
gcc: error: /openmp: No such file or directory
error: command
'C:\\Anaconda2\\envs\\pyten36\\Library\\mingw-w64\\bin\\gcc.exe' failed
with exit status 1"
should i use the MSI instead?
…On Sun, Apr 7, 2019 at 3:11 AM Johannes Pohl ***@***.***> wrote:
Any news?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRRxPEmAhKGpqVE2Cx0n87WF5IPWmks5vecRDgaJpZM4aFGYE>
.
|
|
The MSI will be harder to debug, so it would be better if we get the source build up and running. Did you install a C compiler on your system? It seems to look for mingw gcc. You could install Visual Studio Community with the bundled C++ Compiler which I know works for URH on Windows. |
|
i have VSS installed and MINGW. Ill look to see if there is a path issue
…On Sat, Apr 13, 2019 at 1:55 PM Johannes Pohl ***@***.***> wrote:
The MSI will be harder to debug, so it would be better if we get the
source build up and running.
Did you install a C compiler on your system? It seems to look for mingw
gcc. You could install Visual Studio Community with the bundled C++
Compiler which I know works for URH on Windows.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRc_fWCfpX91N_-ihvI-PkJhW6zM8ks5vgkRHgaJpZM4aFGYE>
.
|
|
Got it installed. I need to force Anacdona to use the right mingw comipler
version byt installing it in the virtual environment, then setting the
path, then doing a pip install urh.
It starts up. I went to look to see if the file structure was the same as
Linux but it seems different. I don't see a tests folder
…On Sat, Apr 13, 2019 at 2:31 PM robi sen ***@***.***> wrote:
i have VSS installed and MINGW. Ill look to see if there is a path issue
On Sat, Apr 13, 2019 at 1:55 PM Johannes Pohl ***@***.***>
wrote:
> The MSI will be harder to debug, so it would be better if we get the
> source build up and running.
>
> Did you install a C compiler on your system? It seems to look for mingw
> gcc. You could install Visual Studio Community with the bundled C++
> Compiler which I know works for URH on Windows.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#608 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AGRdRc_fWCfpX91N_-ihvI-PkJhW6zM8ks5vgkRHgaJpZM4aFGYE>
> .
>
|
|
It is better to do a git clone of the repositoriy than to install it with Anacondas pip. Then you will have the same file structure as on Linux. You can basically use the same instructions from my post near the top for this. |
|
Ok. I'll try that.
…On Sun, Apr 14, 2019, 12:51 AM Johannes Pohl ***@***.***> wrote:
It is better to do a git clone of the repositoriy than to install it with
Anacondas pip. Then you will have the same file structure as on Linux. You
can basically use the same instructions from my post near the top for this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRV_nMSVLabFuCDkc_RytL2twnQxPks5vgt3ogaJpZM4aFGYE>
.
|
|
I just wanted to say I have not dropped this. I ran into some compilation
issues which are a configuration issue on my side. Hopefully I'll have time
tomorrow to resolve that.
…On Sun, Apr 14, 2019, 12:51 AM Johannes Pohl ***@***.***> wrote:
It is better to do a git clone of the repositoriy than to install it with
Anacondas pip. Then you will have the same file structure as on Linux. You
can basically use the same instructions from my post near the top for this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGRdRV_nMSVLabFuCDkc_RytL2twnQxPks5vgt3ogaJpZM4aFGYE>
.
|
|
Any news so far? From what I can tell you verified it is working on Ubuntu. Since there there are no OS specific changes from URH side when using native USRP backend I assume the error source for reported problems is not in URH. I will close here. If someone has more information just drop a comment and I can reopen it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There seem to be problems with native support for USRP B200 on Windows #589 and OSX #577. Since we do not have a USRP B200 for testing, we need some help. I see two options:
The text was updated successfully, but these errors were encountered: