¿ªÔÆÌåÓý

Re: Trouble connecting to APRS2 using direwolf.conf & HT on Rpi 3, decodes beacons well though....


 

Hi Tobias,

Since you are running Direwolf on a Raspberry Pi, you should be able to use any of many different ways available on Linux to save the output on the Direwolf terminal (console).

One way is the utility "tee" which continues to display the messages in the terminal and at the same time copying it to a file specified as commandline argument. Like this:
./direwolf -di | tee /tmp/direwolf-console.log

Another way is the utility "script" which starts a new shell and saves all output in a file (default name is "typescript" but any other name can be specified on the command line. The logging stops when you exit from the sub-shell started by "script". Use it like this:

You type: script /tmp/direwolf-console.log
Outputs : Script started, file is /tmp/direwolf-console.log
You type: ./direwolf -di ; exit

There are other ways to achieve the same result, but some are specific to the GUI environment and Terminal application you are using (which may have built-in logging capability).
If you are using a terminal emulator (such as putty for example) to connect to the Raspberry Pi than those too may allow logging (putty definitely does).

The two methods shown above are simple and tend to be available on nearly every Linux/Unix platform. They will produce a logfile named direwolf-console.log inside the /tmp directory but of course you can pick any name or directory of your own preference.

Having a log file for the entire Direwolf session will make it easier to find the messages you are looking for.

73,
Thomas
KK6FPP

Join [email protected] to automatically receive all group messages.