This is just a wild guess but chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, this may be a debug message pertaining to decoding or not decoding (-1) the continuous tone on the receive. I imagine decoding that tone is a continuous thus continuous flow of messages if debug is enabled to your screen. Do you have the chan_usbradio.c file ? You could look at line 2913 to see what's up. On 2018-08-28 09:05 AM, K. Ishikawa wrote:
Mike,
-vv .. doesn't make a difference. Even without -v, it generates the message. Well it's not a big deal, but when I want to see radio related debug messages (e.g., keyed, carrier detect, etc.), they are buried in this particular message and scrolled out of screen instantly. Since it generates 50+ same messages in a second(!), I just feel something maybe minor (I hope) is not working as it should be. I just wondered someone in the group had any clue.
K
On 2018/08/28 21:52, Mike wrote:
While I can't answer your debug question, I run asterisk in the foreground and set verbosity to a desirable level to see what I want to see.
asterisk -r -vvv - The more v's the more verbose
Perhaps that may help...
But, what is the issue with "rxctcssdecode = -1" your tracking ?
...mike/kb8jnm
On 8/28/2018 5:55 AM, K. Ishikawa wrote:
Hi to the group, When I set "radio set debug" in CLI, the screen is inundated with a flow the following message. It keeps printing the same message so fast that I can't catch other debug messages. Can anyone advise how I can eliminate this, please? [Aug 28 18:32:39] NOTICE[3013]: chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, chan Radio/usb_2132 The node itself is working well, as far as I can tell. It's on R-Pi 3 with URI. Thanks, K