Dear Neel, please find below the output of my flowgraph in Gnuradio and the error message. I use the latest Gnuradio version. I have a setup of 8 mini-computer with B200mini attached. Only two of them show this error, and I still did not figure out why. Once I set the wire-format for the USRP source block in Gnuradio to "automatic" instead of "sc12", the error is gone. Manually setting "sc8" and "sc16" works without giving errors. From my understanding of the B200mini, the "automatic" wire-format is the "sc12" format.
Best Regards, Emanuel ./top_block.py [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-ga1b5c4ae [INFO] [B200] Detected Device: B200mini [INFO] [B200] Operating over USB 3. [INFO] [B200] Initialize CODEC control... [INFO] [B200] Initialize Radio control... [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [AD936X] Performing CODEC loopback test... [INFO] [AD936X] CODEC loopback test passed [INFO] [B200] Setting master clock rate selection to 'automatic'. [INFO] [B200] Asking for clock rate 16.000000 MHz... [INFO] [B200] Actually got clock rate 16.000000 MHz. [INFO] [CORES] Performing timer loopback test... [INFO] [CORES] Timer loopback test passed [INFO] [B200] Asking for clock rate 25.000000 MHz... [INFO] [B200] Actually got clock rate 25.000000 MHz. [INFO] [CORES] Performing timer loopback test... [INFO] [CORES] Timer loopback test passed [INFO] [MULTI_USRP] 1) catch time transition at pps edge [INFO] [MULTI_USRP] 2) set times next pps (synchronously) [INFO] [MULTI_USRP] 1) catch time transition at pps edge [INFO] [MULTI_USRP] 2) set times next pps (synchronously) Press Enter to quit: [ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment WARN: USRP Source Block caught rx error code: 15 [ERRORWARN: USRP Source Block caught rx error code: 15 ] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment [WARN: USRP Source Block caught rx error code: 15 ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment [ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment WARN: USRP Source Block caught rx error code: 15 [ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment WARN: USRP Source Block caught rx error code: 15 [ERROR] WARN: USRP Source Block caught rx error code: 15 [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment [ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment WARN: USRP Source Block caught rx error code: 15 [ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment WARN: USRP Source Block caught rx error code: 15 WARN: USRP Source Block caught rx error code: 15 [ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: bad vrt header or packet fragment WARN: USRP Source Block caught rx error code: 15 ________________________________ Von: Neel Pandeya [neel.pand...@ettus.com] Gesendet: Samstag, 19. Mai 2018 20:17 An: Staudinger, Emanuel Cc: usrp-users Betreff: Re: [USRP-users] B200mini sc12 wire format broken? Hello Emanuel: Could you please post the error message from the console? Does this error persist in UHD 3.11.1.0? --​Neel Pandeya On 4 May 2018 at 06:51, Marcus D. Leech via USRP-users <usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote: On 05/04/2018 01:45 AM, Emanuel via USRP-users wrote: Hi, I switched from UHD release 3.10.2.0 to the latest release 3.11.0.0 and recognized in my Gnuradio application, that UHD gives errors when using the sc12 wire format. However, only when I use the USRP in receive mode. In transmit mode, the sc12 format works. The sc8 and sc16 wire format work well for the receive mode. The same issue comes with 3.11.0.1. Release 3.10.2.0 does not show this error. Did anyone else experience that? Best regards, Emanuel _______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com Could you perhaps share the error log? That would help developers and others... _______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
