Just a thought…
You can log QSO activity on the node by enabling the archivedir=/path/to/some/location argument within specific node(s) within your rpt.conf file. This will log activity to a daily file of node activity in TXT form, but it also dumps WAVs for each node keydown… which fills up and will eventually kill your SD Card…
You get lines like this though in the TXT:
20200529080130,TXKEY,4xxxx
20200529080130,RXUNKEY,2xxxx
20200529080130,TXUNKEY,4xxxx
20200529080130,RXKEY,2xxxx
20200529080130,TXKEY,4xxxx
20200529080130,RXUNKEY,2xxxx
20200529080130,TXUNKEY,4xxxx
20200529080130,TXUNKEY,MAIN
20200529080148,RXKEY,2xxxx
20200529080148,TXKEY,4xxxx
20200529080148,TXKEY,MAIN
20200529080148,RXUNKEY,2xxxx
20200529080148,TXUNKEY,4xxxx
20200529023229,LINKDISC,4xxxx
20200529023315,LINK,4xxxx
Disclaimer: This fills up disks fast and will KILL SD CARDS.
- Don’t use this unless you have a need/want to, and don’t leave it turned on long if you’re running the sequences on a Pi node.
- If you have a hardware/virtual machine Hub node with a bigger normal disk, try running there and staying “linked” to the Pi node experiencing trouble.
Hope this helps
Byron