Section 6. Network Status and Resolving Communication Problems
Remove Operations When Finished
When this check box is selected (default), operations that are no longer active
will be deleted from the displayed list. If this box is not selected, the last state
of the operation before completion will continue to be displayed in the list. The
displayed list is limited to a maximum of one thousand lines. After reaching the
limit, the oldest lines are deleted as new lines are added.
Save to File
When this check box is selected, the information provided by the server for
each listed operation is saved to a comma delimited text file
(C:\Campbellsci\LoggerNet\Operations.log). The information logged provides
a record of when the operation was added, changed (updated), and deleted by
the server. For each line in the file, the information is ordered as follows:
Event, Start Time, Device Name, Description, State, Priority, Transmit Time,
Receive Time, Timeout Interval, Client, Account, and ID#. Entries in the file
are limited to twelve thousand lines. After reaching the limit, the oldest four
thousand lines are deleted.
Added,1/2/20138:45:00AM,CR3000,tablepoll‐OneMin,,2,,,,,,1
Added,1/2/20138:45:00AM,CR1000,tablepoll‐Sec_60,,2,,,,,,2
Changed,1/2/20138:45:00AM,CR3000,tablepoll‐OneMin,requestingfocus,2,,,1000ms,,,1
Changed,1/2/20138:45:00AM,CR1000,tablepoll‐Sec_60,requestingfocus,2,,,1000ms,,,2
Added,1/2/20138:45:00AM,CR3000,delayhangup,,2,,,,,,3
Changed,1/2/20138:45:00AM,CR3000,tablepoll‐OneMin,requestingfocus,2,1/2/20138:45:00AM,,1000ms,,,1
Changed,1/2/20138:45:00AM,CR3000,tablepoll‐OneMin,requestingfocus,2,1/2/20138:45:00AM,1/2/20138:45:00AM,,,,1
Changed,1/2/20138:45:00AM,CR3000,tablepoll‐OneMin,collectingholesbetween28827and28830,2,1/2/20138:45:00AM,
1/2/20138:45:00AM,1000ms,,,1
Changed,1/2/20138:45:00AM,CR3000,tablepoll‐OneMin,complete,2,1/2/20138:45:00AM,1/2/20138:45:00AM,1000ms,,,1
Deleted,1/2/20138:45:00AM,CR3000,tablepoll‐OneMin,complete,2,1/2/20138:45:00AM,1/2/20138:45:00AM,1000ms,,,1
Added,1/2/20138:45:00AM,CR1000,delayhangup,,2,,,,,,1
Changed,1/2/20138:45:00AM,CR1000,tablepoll‐Sec_60,gettingnewestrecord,2,1/2/20138:45:00AM,,1000ms,,,2
Changed,1/2/20138:45:00AM,CR1000,tablepoll‐Sec_60,gettingnewestrecord,2,1/2/20138:45:00AM,1/2/20138:45:00AM,,,,2
Changed,1/2/20138:45:00AM,CR1000,tablepoll‐Sec_60,collectingholesbetween29and32,2,1/2/20138:45:00AM,1/2/2013
8:45:00AM,1000ms,,,2
Changed,1/2/20138:45:00AM,CR1000,tablepoll‐Sec_60,complete,2,1/2/20138:45:00AM,1/2/20138:45:00AM,1000ms,,,2
Deleted,1/2/20138:45:00AM,CR1000,tablepoll‐Sec_60,complete,2,1/2/20138:45:00AM,1/2/20138:45:00AM,1000ms,,,2
Deleted,1/2/20138:45:00AM,CR1000,delayhangup,,2,,,,,,1
Deleted,1/2/20138:45:00AM,CR3000,delayhangup,,2,,,,,,3
6.2 LogTool
There are four logs kept by LoggerNet that track the operation of the server,
communications with the dataloggers and data collection. These logs can be
used for troubleshooting communication problems. The LogTool utility allows
you to view the communication packets transferred between the computer
running the datalogger support software and other devices in the network.
LogTool can be launched from the Status Monitor, or from the LoggerNet
Toolbar’s Tools category.
Each of the logs is explained here briefly. Operation of the LogTool utility is
also explained. For additional information on interpreting logs, see
Appendix E, Log Files.
6-12
To Next Page
Loading...
General