Logging Screen

Prior to version 1.0.5 the logging functions of this program were useful but incredibly difficult to figure out how to use --- even for me. :-)

 I've essentially rewritten the entire logging functions and I hope it will make this feature a bit more user friendly.

I'm attempting to get this one right. It is fairly intuitive. Type a callsign into the box and it's logged in the method indicated assuming the "Enable" check mark is present.

Each station is logged into it's own separate file. This way you can capture traffic from specific stations to unique files.

In the Plain Text Logs column you can enter the beginning of a pattern followed by an asterisk. Above, all stations from KA0ULN will be logged including all SSIDs. Every station that begins with NØ will be logged. You can use this capability to log all the callsigns from a particular ham by entering their full call with NO SSID and an asterisk. The program will then log each of his SSIDs to separate log files. Or you can widen the scope. You can't enter an asterisk by itself as a means of capturing data from all stations. However, you can start logging everything by clicking [File/Save/All Packets]. This options is also available from the main screen's File menu. The drawback to this method, all data is written commingled in a single file. So, it can get tiresome to "read" later.

Callsigns can be entered in multiple columns and they will be logged into those different types of files.

Track logs will only contain packets that are separated in distance by the amount you indicate on the setup screen.

Digipeater logs will only record directly heard digipeaters, not every packet that contains this callsign in the path.

Double click on any of the stations in the log entry columns and it will be deleted (a confirmation is required).

Double click on any of the active stations on the right and the associated log file will be loaded into either a text viewer or spreadsheet program if you have specified a spreadsheet on the Setup screen. Spreadsheets are loaded as temporary copies to prevent the active logs from being locked and inaccessible by ANS.

Several types of information packets, Messages, Objects, Items and 3rd Party Traffic can be logged into either text files or spread sheet files.

I'm somewhat open to suggestions. Well, I always welcome them, but I don't always incorporate them in a timely manner if at all. AprsNetSpy is definitely not on my front burner. However, from time to time I do like to poke around with it. As you can see from the Version History page here, that doesn't happen all that often.