Hi Jason,

The command message handling in the USRP source in GNU Radio is a bit
interesting. The command may contain many pairs of key->value, most of
which end up in a call to their own handler. There is a debug message
printed for each of these handlers if you have GNU Radio debug messages
enabled.

List of supported keys
https://github.com/gnuradio/gnuradio/blob/a0adcd3347c7ffd6ef3c42ce7705a23978774d3b/gr-uhd/lib/usrp_block_impl.cc#L30

There is also error reporting if the command type isn't correct.
https://github.com/gnuradio/gnuradio/blob/a0adcd3347c7ffd6ef3c42ce7705a23978774d3b/gr-uhd/lib/usrp_block_impl.cc#L538

If you aren't seeing the debug messages then try changing your GNU Radio
logging settings.
https://gnuradio.org/doc/doxygen/page_logger.html

Regards,
Derek

On Mon, Oct 30, 2017 at 2:54 PM, Jason Matusiak via USRP-users <
usrp-users@lists.ettus.com> wrote:

> Is there anyway to get feedback from a sent message command to a USRP
> source in GR?  I was sending some commands and was *pretty* sure I was
> doing it right, but to know for sure I sent a bogus command, and it didn't
> complain (I expected to see something on the terminal).  Is there anyway to
> turn on some sort of print-out to see that it accepted the commands I am
> sending (like changing freqs)?  Or at the very least see when a bad command
> was sent?
>
> _______________________________________________
> USRP-users mailing list
> 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

Reply via email to