Logging local RF

I have a gateway and a repeater set-up at my location. I would like to know whenever there has been any local RF activity. Is there an existing log file that holds this info?

I did look at the archivedir functionality but this doesn't seem to be able to differentiate between local RF and traffic received via the internet.

archivedir=/var/log/asterisk/audio
archiveaudio=0 ; Disable saving .wav files

Tom G0JSV

1 Like

That is correct Tom.

It does on HAMVOIP shows RX Key and Unkey and when the Node link keys and unkeys
This is what it will look like when activity from the ASL network connection
20250414083620,RXKEY,4622 (**** This in coming from Node 4622)
20250414083620,TXKEY,MAIN
20250414083626,RXUNKEY,4622 (****Node 4622 stops)

This is what it will look like when RF comes in the RX of the repeater
20250414083628,RXKEY,MAIN (**** RF Repeater Input)
20250414083628,TXKEY,4622
20250414083634,RXUNKEY,MAIN (***** RF from Repeater)
20250414083634,TXUNKEY,4622

I have not looked at the archive log output but I can tell you that the ASL3/app_rpt source code includes code that likely logs the same messages.

./apps/app_rpt.c:	donodelog_fmt(myrpt, "RXKEY,%s", l->name);
./apps/app_rpt.c:	donodelog_fmt(myrpt, "RXUNKEY,%s", l->name);
./apps/app_rpt.c:	donodelog(myrpt, "RXKEY,MAIN");
./apps/app_rpt.c:	donodelog(myrpt, "RXUNKEY,MAIN");

Thanks for the replies. I disconnected the repeater so that it was standalone. Below is the log that was created.

20250415154501,TXKEY,MAIN
20250415154510,RXKEY,MAIN
20250415154510,RXUNKEY,MAIN
20250415154523,TXUNKEY,MAIN
20250415154602,RXKEY,MAIN
20250415154602,TXKEY,MAIN
20250415154602,RXUNKEY,MAIN
20250415154608,TXUNKEY,MAIN
20250415155901,TXKEY,MAIN
20250415155910,TXUNKEY,MAIN
20250415160001,TXKEY,MAIN
20250415160018,RXKEY,MAIN
20250415160021,RXUNKEY,MAIN
20250415160022,RXKEY,MAIN
20250415160023,RXUNKEY,MAIN
20250415160029,TXUNKEY,MAIN
20250415160105,RXKEY,MAIN
20250415160105,TXKEY,MAIN
20250415160105,RXUNKEY,MAIN
20250415160108,RXKEY,MAIN
20250415160109,RXUNKEY,MAIN
20250415160111,RXKEY,MAIN
20250415160111,RXUNKEY,MAIN
20250415160118,TXUNKEY,MAIN
20250415160203,RXKEY,MAIN
20250415160203,TXKEY,MAIN
20250415160205,RXUNKEY,MAIN
20250415160205,RXKEY,MAIN
20250415160206,RXUNKEY,MAIN

This appears to be caused by the repeater telemetry such as idents plus the time and weather announcements. There was no local RF being received on the input of the repeater during this period of logging. So when I see a log event for RXKEY,MAIN I don't know if it was really caused by local RF being received.

Wouldn't Telemetry and ID show "TXKEY,MAIN" only, while RF keyups would show "RXKEY,MAIN and "TXKEY,MAIN" as a pair?

That's how mine works.

There were no local RF keyups in the above log. But yes I did wonder if I had to scan the logs for a corresponding pair. But "RXKEY,MAIN and "TXKEY,MAIN" appear side by side.