Prevent SoapySDR and/or LMS7 drivers from printing anything on stdout/stderr

ccsh · 28 August 2017 11:35

Hi,

sorry if this is obivious, but is there some simple way to prevent SoapySDR library and/or LMS7 drivers from printing anything on stdout/stderr? It gets a little bit messy when combined with other informations being displayed in my custom c++ application. I mean these commands which show up when creating new device (LimeSDR support via SoapySDR) or for example changing the master clock rate, like this one:

CGEN: Freq=100 MHz, VCO=2.4 GHz, INT=77, FRAC=131072, DIV_OUTCH_CGEN=11

Thank you in advance for your help!

//edit:
or maybe there is a way to register some handler in order to catch such messages? That would be even better!

mzs · 28 August 2017 20:35

Have you set the SOAPY_SDR_LOG_LEVEL environment variable ?

github.com

pothosware/SoapySDR/blob/master/include/SoapySDR/Logger.h#L24


#include <SoapySDR/Config.h>
#include <stdarg.h>


/*!
* The available priority levels for log messages.
*
* The default log level threshold is SOAPY_SDR_INFO.
* Log messages with lower priorities are dropped.
*
* The default threshold can be set via the
* SOAPY_SDR_LOG_LEVEL environment variable.
* Set SOAPY_SDR_LOG_LEVEL to the string value:
* "WARNING", "ERROR", "DEBUG", etc...
* or set it to the equivalent integer value.
*/
typedef enum
{
   SOAPY_SDR_FATAL    = 1, //!< A fatal error. The application will most likely terminate. This is the highest priority.
   SOAPY_SDR_CRITICAL = 2, //!< A critical error. The application might not be able to continue running successfully.
   SOAPY_SDR_ERROR    = 3, //!< An error. An operation did not complete successfully, but the application as a whole is not affected.
   SOAPY_SDR_WARNING  = 4, //!< A warning. An operation completed with an unexpected result.

ccsh · 29 August 2017 09:00

Thank you for hint, unfortunately it does not help with the previously mentioned messages. I think that they are coming from LMS7 driver.

andrewback · 29 August 2017 13:57

@IgnasJ any ideas?

IgnasJ · 29 August 2017 14:44

There is no way to disable all messages from LimeSuite library. However, the message that you mentioned should not show up in ‘Release’ configuration of LimeSuite. You can try building LimeSuite from source (Release configurations should be default), it may reduce number of messages.

ccsh · 30 August 2017 08:24

I see. Thank you for a quick response. Going to try that later, so far I can live with those lines

tony.bigbee · 30 August 2017 19:43

In the master branch, there are some fairly recent hardcoded print statements added by Lime engineers (GetTemperature comes to mind, added 7 months ago by rjonaitis). You do have to remove them from source and rebuild. Prints from calibration are the only ones I have left in for the moment.
Contact me directly and I can tell you what classes and line numbers I removed. There may be more as I’m not calling every function available.