Gasboy CFN Series Gilbarco CRIND PC Interface for Site Controller III - Manual (Page 26)

Troubleshooting Technical Debug Options
Page 22 MDE-4337G Gilbarco® CRIND® PC Interface for Site Controller III with Windows® · February 2011
s = send debug output to the screen (default)
f = send debug output to the file crnd_log.cxx (described below)
‘ ’ (space) = toggles the display ON and OFF when debug output is going to the screen
ALT-R = restarts the CRIND session
Debug Log File
All the log files are in a subdirectory named: c:\sc3\crnd_log. Each debug log file is saved as
crnd_log.cxx, where:
c = Comm Port number
xx = cycles from 00 to 99, then 00 over again
When you start for the first time on com1 and press f, the logging will go to:
crnd_log.100 for 1Meg of data, then to
crnd_log.101 for another 1Meg, then
o
o
o
crnd_log.199 for another 1Meg, then
crnd_log.100 and cycles through again.
It is possible to have logging on two sessions at one time. For com2, the file would start at
crnd_log.200 and follow the same format as com1.
If you restart the CRIND session, it starts with the next file after the last one written. For
example, if you quit during crnd_log.123 with (ALT-X) and start over, or restart (ALT-R), and
turn on file logging again it will begin with crnd_log.124.
If you see an event that you want to capture, press ALT-R (then press f again if you want to
continue with logging, which will start a new log file), then you can remove or copy the old
file.