¿ªÔÆÌåÓý

How to turn off DW status reports?


 

Is there any way to turn off the following messages,

Past 100 seconds, 4410000 audio samples, 0 errors.


and only report when errs occur?



SR



 

Are you logging the terminal output to file?? You can 'grep' for whatever you want (or don't want) then.

Ian
VK1IAN


Is there any way to turn off the following messages,

Past 100 seconds, 4410000 audio samples, 0 errors.


and only report when errs occur?



SR


 

Ha, that's a thought.?

I was wanting to use this for packet chat, and the status updates just take up room in the chat log.

Thanks,

SR


 

Can you make that work on an ongoing basis with only one call to grep?


 

Not sure I understand what you are asking however if you want all the "Past 100 seconds, 4410000
audio samples, 0 errors" lines removed, assuming you've started direwolf piping it's output to
"direwolf.log", open another terminal and type:

tail -f direwolf.log | grep -v 'Past 100 seconds'

This will display everything except the message mentioned. As ALL output is written to the log file,
you can go back later to look for anything specific.
My command line for starting direwolf is a little more complicated than this as I add a timestamp to
all the lines before they are written to the log file. Happy to provide this as well if required.

Ian

On 07/12/14 08:21, syberraith@... [direwolf_packet] wrote:


Can you make that work on an ongoing basis with only one call to grep?


 

What you mentioned still outputs blank lines.

This did what I want:

?? tail -f dw.log | grep "^\[0L\]"

I believe I'm ready to finish my computer-radio inter-connect now and do some packet chatting.? Although, virtually nobody around here chats over VHF packet radio... :|

Thanks again,

SR


David Ranch
 

There isn't any way to disable all the chattiness of Direwolf today though I've asked John to add some additional command line options in future versions to suppress a lot of these. Until then, I recommend to just redirect all the STDIO to a file and just "grep -v" out the items you don't want to see when viewing it.

--David


 

That's fine.? The log file and grep do what I wanted.? Together with a beacon wrapper script I modidied they make quite the clean packet chat client.? This method requires the use of two windows, although that's fine too.

One last thought is that occassionally the beacon command results in DW attempting to transmit on other then the desired radio channel.? Presumably the desired channel is channel 0, and occasionall I get err reports from DW saying some thing like this with various channel numbers:

ERROR - Request to transmit on radio channel 2.

Any idea what might be causing that?


David Ranch
 

¿ªÔÆÌåÓý


?

That's fine.? The log file and grep do what I wanted.? Together with a beacon wrapper script I modidied they make quite the clean packet chat client.? This method requires the use of two windows, although that's fine too.


Ok and I understand what you're doing with beacon to have an UNPROTO or UI chat but check out Linpac.? It's F10 screen gives you a very nice UNPROTO chat window.

??

One last thought is that occassionally the beacon command results in DW attempting to transmit on other then the desired radio channel.? Presumably the desired channel is channel 0, and occasionall I get err reports from DW saying some thing like this with various channel numbers:

ERROR - Request to transmit on radio channel 2.


Did you enable one channel or two?? Seems like a bug if you've only enabled one channel (I think it defaults to using the RIGHT audio channel of the mic and speaker).

--David


 

In the configuration file I enabled only 1 channel.?? And it seems seldom but random that DW wiill try to send the beacon messages out over channel 2, 7, or 8 etc.? and the message for that particular attempt gets lost.? If I repeat the message, it might continue to attempt to send it out over some other channel other than 0, once or maybe twice more, before resuming repeated transmissions on channel 0 again.?

I lack a clue as to what could cause that.? Beacon seems to lack any facility to specify what channel to send out a message, unless the postfix of -<channel> is added to the call sign to specify the channel.?

I tried using the specifican CALL-0 to force beacon to transmit on channel 0, altough beacon gave me an err.

I have linpac up and running.? I found I could prefix messages with :unproto to chat, although that was a bit awkward.? I'll try F10 and see how that works.


 

As my old Alinco HT and probably all other HTs without a data port use the tip of a stereo plug for the audio input and output, as as the tip is specidied as the left channel.? I would think it best if DW defaulted to using the left channel for one channel operation.