LimeSuiteNG debug messages

When running a LimeSuiteNG Sink with GNU Radio, many debug messages are generated in the console. See below.

I’d prefer to restrict these messages to warnings or errors on which I should act.

A scan of the source code suggests that the messages are hard-wired in the LimeSuiteNG source code.

Is there an easy way to restrict them, please? A verbosity setting elsewhere?

Thanks

Dave

LimeSuiteNG :debug: FPGA: StartStreaming
sdrdevice_source :info: RFStream Start()
LimeSuiteNG :debug: Rx receive loop start.
LimeSuiteNG :debug: USB ep:83 Rx0: 3.854 MB/s | TS:958800 pkt:940 o:0(+0) l:0(+0) dma:940/941(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:1919640 pkt:1882 o:0(+0) l:0(+0) dma:1882/1883(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:2880480 pkt:2824 o:0(+0) l:0(+0) dma:2824/2825(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:3841320 pkt:3766 o:0(+0) l:0(+0) dma:3766/3767(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:4802160 pkt:4708 o:0(+0) l:0(+0) dma:4708/4709(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:5763000 pkt:5650 o:0(+0) l:0(+0) dma:5650/5651(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:6723840 pkt:6592 o:0(+0) l:0(+0) dma:6592/6593(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:7684680 pkt:7534 o:0(+0) l:0(+0) dma:7534/7535(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:8645520 pkt:8476 o:0(+0) l:0(+0) dma:8476/8477(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:9606360 pkt:9418 o:0(+0) l:0(+0) dma:9418/9419(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:10567200 pkt:10360 o:0(+0) l:0(+0) dma:10360/10361(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:11528040 pkt:11302 o:0(+0) l:0(+0) dma:11302/11303(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:12488880 pkt:12244 o:0(+0) l:0(+0) dma:12244/12245(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:13449720 pkt:13186 o:0(+0) l:0(+0) dma:13186/13187(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:14410560 pkt:14128 o:0(+0) l:0(+0) dma:14128/14129(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:15371400 pkt:15070 o:0(+0) l:0(+0) dma:15070/15071(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:16332240 pkt:16012 o:0(+0) l:0(+0) dma:16012/16013(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:17293080 pkt:16954 o:0(+0) l:0(+0) dma:16954/16955(+1) swFIFO:0
LimeSuiteNG :debug: USB ep:83 Rx0: 3.858 MB/s | TS:18253920 pkt:17896 o:0(+0) l:0(+0) dma:17896/17897(+1) swFIFO:0

I’ve redirected debug messaging into separate logger, the spam should be gone.

Thank you for the very quick mod.

How do I best view the debug messages if I wish to see them?

I don’t see a direct way of managing logging level directly from GRC, but you can insert gr.logging().set_default_level(gr.log_levels.debug) into the generated python code. Logging - GNU Radio