The three types of log files produced by Unitrunker are turned off by default. When turned on, these log files can potentially consume lots of disk space. A 24 hour run of P25 decode data can exceed 100 megabytes. To keep disk space manageable, logs are rotated every 24 hours at local midnight. Rotate means the previous day's log is closed and a new log file is opened. The log file name includes the year, month and day. The previous day's log file is gzip compressed. This compression usually nets a 10 to 1 ratio. Operating full time, you can expect to log a week's worth of data with just 200 megabytes of disk space. That's 100 megs max for the current day plus another 100 megs for seven or more days' worth of compressed logs. It is possible for a single uncompressed log file to exceed 100 megabytes.

Tip: zgrep can search compressed logs in-place (without first uncompressing them).

Tuner Logs

Control and inline receivers have the option of producing "Tuner" logs. The tuner log records the exchange of commands and responses between radio and computer. They have a high value for debugging; particularly for supporting a new model. You can enable the tuner log by checking "Logging" in the Control section of the receiver configuration. To see your tuner log files in Windows Explorer, click the folder icon at the top of the receiver window.

Event Logs

History logs mirror the History panel in the site window. These are text files with comma delimited columns listed below. Use them for traffic analysis, statistics, or what ever you like. Enable event / site logging by checking the "Logging" option on the Site's Info tab. To see your event log files in Windows Explorer, click the folder icon at the top of the site window.

  1. Timestamp as YYYYMMDDHHMMSS
  2. Site number in unformatted decimal
  3. Action: Call, Leaves, Joins, Login, Logout, Drop, Add, Busy, Deny, Kill
  4. Source type I or G
  5. Source ID in unformatted decimal
  6. Target type I or G
  7. Target ID in unformatted decimal
  8. Channel number in unformatted decimal
  9. Call Type

Decode Logs

Decode logs record packet or message level content. Message format, structure and nomenclature varies by protocol. These messages drive the behavior of Unitrunker. The decoding receiver can optionally save raw decoded messaging as a text file. Check the "Logging" option in the Decode section of the signal receiver. Decode logs have a high value for debugging. To see your decode log files in Windows Explorer, click the folder icon at the top of the receiver window.