Send USRP-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."
Today's Topics:
1. [B200 USRP] HDSDR] " Failed to create USRP without device
hint" (numeric)
2. [UHD 3.8.1] Release Announcement (Martin Braun)
3. UHD and the soundcard confliction (wonder freedomfighter)
4. B210 Concurrent Process Access (Peter Witkowski)
5. Re: B210 Concurrent Process Access ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Mon, 15 Dec 2014 14:31:51 -0500
From: numeric <[email protected]>
To: [email protected]
Subject: [USRP-users] [B200 USRP] HDSDR] " Failed to create USRP
without device hint"
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello group,
I just received my USRP b200 circuit board:-) . I thought that I would
start with known software for Windows 8.1 64 bit. I downloaded
uhd_003.008.000-release_Win64_VS2013.exe from the ETTUS website and ran
the installation. It installed to "Program files (x86)\UHD". When I
tried to set the file path to "all users or current users" I get an
error "Warning! PATH too long installer unable to modify PATH!". The
[path >path.txt] from the command prompt, is 639 Hex characters long or
1593 in decimal. Excluding 0xd 0xa (EOL). Ignored the error. Next
installed "ExtIO_USRP+FCD+BorIP_Setup.zip". It installed to "Program
files (x86)\hdsdr". The program HDSDR was previously installed and used
with the QS1R receiver using it's own EXTIO dll file. The QS1R extio dll
was deleted before installing EXTIO_USRP to avoid potential conflicts.
During the installation, zadaig.exe activated.
Question:
Since UHD.dll is already a driver do I need to use zadaig? The device
manager indicated "Westbridge" when the USPR B200 is plugged in, it
changes to B200 after running "uhd_find_devices.exe". I get the same
device hint problem if zidaig is run or not.
What files is EXTIO_USRP looking for?
Question:
What am I doing wrong?
Any help is greatly appreciated,
Rob
------------------------------
Message: 2
Date: Tue, 16 Dec 2014 12:59:34 +0100
From: Martin Braun <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: [USRP-users] [UHD 3.8.1] Release Announcement
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Everyone,
we've just tagged and released our first bugfix release for the 3.8 UHD
series. This release also brings changes to the FPGA code and thus we've
bumped the compat number for X- and E3-Series devices' FPGA images. We
encourage everyone to update, in particular X-Series users because we
fixed some critical data integrity issues for those devices.
You can get this release by either pulling maint branch, or checking
out the release's tag:
https://github.com/EttusResearch/uhd/tree/release_003_008_001
Binary installers will be available through our usual channels soon.
Enjoy,
Martin
## 003.008.001 Changelog:
* B2x0: Fixed PLL settings, Fixed external ref selection, serialized
streamer setup (thread-safety)
* X3x0: Fixed flow control issue, improved DAC ctrl + init logic,
Fixed I/Q alignment issue
* Generation-3 devices: Fixed LED registers
* UHD: Improved tuning logic for manual tunes
* Tools: Multiple kitchen sink fixes, coloured output
* Examples: Multiple bugfixes (multi-channel ops)
* Docs/Manual: Multiple fixes, E310 panel images
------------------------------
Message: 3
Date: Tue, 16 Dec 2014 15:45:49 +0100
From: wonder freedomfighter <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] UHD and the soundcard confliction
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Marcus, Ian both of you were correct, it was my flow graph
and what is most typical is that I misplaced two numbers under interpolation =
5 and decimation= 12: all I needed to do, to correct the flow graph was to
change the numbers the other way around 12 and 5, incredible.
Surprised none of you noticed it??
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141216/754b5f4b/attachment-0001.html>
------------------------------
Message: 4
Date: Tue, 16 Dec 2014 11:53:22 -0500
From: Peter Witkowski <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] B210 Concurrent Process Access
Message-ID:
<CAN1Qg3Ps=5BHZoY00=r3ye+gasojlyjornnvjz-akcb1y+6...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello,
I have a quick question regarding how UHD handles concurrent processes
accessing the same USRP.
Say I have two applications (totally separate processes in Linux) and both
want to talk to the same B210 (and use different channels on the B210).
Can both processes communicate with the device concurrently? I noted that
the make() call to multi_usrp returns a shared pointer, so I was wondering
if (as a result) you can have multiple processes access the same physical
device (with the same device arguments).
Thanks in advance for the help.
--
Peter Witkowski
[email protected]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141216/e48bed2e/attachment-0001.html>
------------------------------
Message: 5
Date: Tue, 16 Dec 2014 11:57:03 -0500
From: [email protected]
To: Peter Witkowski <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] B210 Concurrent Process Access
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
No, there's no provision for that. A single process has to "own" the USB
device handle, and relevant internal UHD structures.
On 2014-12-16 11:53, Peter Witkowski via USRP-users wrote:
> Hello,
>
> I have a quick question regarding how UHD handles concurrent processes
> accessing the same USRP.
>
> Say I have two applications (totally separate processes in Linux) and both
> want to talk to the same B210 (and use different channels on the B210). Can
> both processes communicate with the device concurrently? I noted that the
> make() call to multi_usrp returns a shared pointer, so I was wondering if (as
> a result) you can have multiple processes access the same physical device
> (with the same device arguments).
>
> Thanks in advance for the help.
>
> --
>
> Peter Witkowski
> [email protected]
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com [1]
Links:
------
[1] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141216/b50323a5/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
End of USRP-users Digest, Vol 52, Issue 18
******************************************
