You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain configurations of the Ettus x310 are unable to be found when using uhd_find_devices without any arguments. If this happens then the supervisor.d/usrp.conf command line wait_for_domain uhd_find_devices && nodeBooter ... fails before ever reaching the nodeBooter command and the device manager is never launched.
Possible solutions:
Remove the uhd_find_devices from the supervisor command. The device manager will report if the uhd device is not able to be found and provide sufficient log messages to inform users that the device is not present. If the purpose is to ensure the fpga load is completed before starting the device manager then consider the next solution.
Use the environment variables to build out an argument string for the uhd_find_devices command to look for the specific device. In our particular use case we supply --usrpip <IP> --usrptype x300; if the uhd_find_devices command were passed these arguments such as uhd_find_devices --args "type=x300, addr=<IP>" then the command would successfully find our device and proceed to the nodeBooter command. This solution requires a bit more work as the argument string needs to be dynamically built based on which and how many of the four possible environment variables are used. A simpler solution that might work is including the addr argument if and only if the USRP_IP_ADDRESS variable is set, but this may not solve for all possible cases.
The text was updated successfully, but these errors were encountered:
That's a tough one...and unfortunately we don't have an x300 to test against. The uhd_find_devices call primarily was for the b200 series devices we've used in the past. I don't think we've tried our N2xx since releasing docker-redhawk.
I would be happy to accept a PR if you have a working solution.
Our work around is to just remove the uhd_find_devices && portion of the supervisor command and let the device manager handle informing us when the device isn't present.
Certain configurations of the Ettus x310 are unable to be found when using
uhd_find_devices
without any arguments. If this happens then the supervisor.d/usrp.conf command linewait_for_domain uhd_find_devices && nodeBooter ...
fails before ever reaching the nodeBooter command and the device manager is never launched.Possible solutions:
--usrpip <IP> --usrptype x300
; if the uhd_find_devices command were passed these arguments such asuhd_find_devices --args "type=x300, addr=<IP>"
then the command would successfully find our device and proceed to the nodeBooter command. This solution requires a bit more work as the argument string needs to be dynamically built based on which and how many of the four possible environment variables are used. A simpler solution that might work is including the addr argument if and only if the USRP_IP_ADDRESS variable is set, but this may not solve for all possible cases.The text was updated successfully, but these errors were encountered: