Difference between revisions of "BorIP"
From SpenchWiki
(Notes sections) |
(→To Do) |
||
Line 35: | Line 35: | ||
** Apparently it still works if device is left connected and powered on. | ** Apparently it still works if device is left connected and powered on. | ||
* Announce via Bounjour/custom broadcast | * Announce via Bounjour/custom broadcast | ||
− | * Ability to set up multiple | + | * Ability to set up multiple streams |
+ | * Buffer & request re-send of section that was dropped (e.g. lost packets) |
Revision as of 10:55, 21 July 2011
Device creation
- The hint is used to specify which device to create, and implies whether the UHD or Legacy interface is used.
- A blank hint implies the default UHD device.
- Entering a digit implies the index for a Legacy device.
- Anything else is fed through to the UHD device factory.
Command-line arguments
- Prepended with either / or -
- port - set port to listen on (28888 by default)
- device - supply without parameter to automatically create default UHD device, or give hint to specify which device to create
Notes
- Cannot disconnect device once it has been 'created' in server. This will cause the server to crash (can't help this).
Bugs
- On first creation of Legacy device, serial will fail to be fetched correctly (will remain blank), but device will still work.
- If application is restarted while programmed USRP remains connected, creation of Legacy device will result in serial now being displayed.
- Cannot start program, then connect Legacy device, then attempt to create
- Must connect USRP first, then start program
- Legacy is more efficient in this compilation than UHD at higher sampling rates
To Do
- (Detect changes in power state and release device to prevent app crash when resuming.)
- Apparently it still works if device is left connected and powered on.
- Announce via Bounjour/custom broadcast
- Ability to set up multiple streams
- Buffer & request re-send of section that was dropped (e.g. lost packets)