Campbell Scientific Vibrating CRVW3 3-Channel Vibrating-Wire Datalogger - Page 94

Troubleshooting CRVW3 Networks, Status Monitor, Connect Screen, SetupScreen, Station Status

Page 94 highlights

CRVW3 3-Channel Vibrating-Wire Datalogger You should observe the solar panel operation (-RC option) to ensure it is charging the battery properly. You can also double-check antenna operation using a temporary base station radio and a laptop running LoggerNet (see Section 10, Complex (Large) Radio Networks). Using the Terminal mode of the CRVW3 from DevConfig can also be used to perform maintenance (see Appendix B, Terminal Mode from Connect Screen or DevConfig). 13. Troubleshooting CRVW3 Networks By following the tasks outlined in Section 11, Operation of CRVW3 Networks, and Section 12, Maintenance of CRVW3 Networks, for operating and maintaining your network of CRVW3 stations, you can identify problems with the system when they emerge or very soon after they occur. The Status Monitor is a key tool for identifying that a problem in the system exists (see Section 11.1, Monitoring Automatic Data Collection, for guidance about using Status Monitor). Some common indicators that something is wrong with a station are: • Automatic (scheduled) collection is not working as shown by the Status Monitor or Table Monitor • You can't connect to the station in the LoggerNet Connect Screen • Clock checks (SetupScreen) are not working • Manual collection doesn't work (Custom Collect and Collect Now) • You can't view the Station Status (Summary and Status Table) • The station is able to communicate, but the data that is collected from that station has problems You should troubleshoot problems as soon as possible after they arise. Some clues relating to the source of the problem can change (become more obscure) over time. Small problems can often escalate into larger ones, due to cascading consequences. Troubleshooting a part of the system that has never worked is strongly related to the installation process. Review Sections 7 through 10 as a first step of investigation in such cases. When a problem arises in a system area that used to work but has recently stopped working, the main question to ask is "What changed?" What changed in the system to cause the station to stop operating? When did the failure begin? Examine key aspects of the system and its recent maintenance history to obtain clues about changes made to the system. Sometimes a change to the system that seems harmless or unrelated turns out to be the cause of the trouble. When you begin troubleshooting a system, you do not yet know the source of the problem. You should suspect all parts of the system (communications, power, repeaters, base station, software, LoggerNet computer station issues) until you determine what went wrong. Use the clues given by the problem to narrow your focus. However, you may need to broaden your focus from time to time if causes of the problem fail to emerge. Sometimes the problem is caused by intentional changes to the system, sometimes it is caused by unintentional changes to the system. Sometimes problems are caused by acts of nature (lightning strikes, storms, animal 84

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112

CRVW3 3-Channel Vibrating-Wire Datalogger
You should observe the solar panel operation (–RC option) to ensure it is
charging the battery properly. You can also double-check antenna operation
using a temporary base station radio and a laptop running
LoggerNet
(see
Section 10,
Complex (Large) Radio Networks
). Using the Terminal mode of
the CRVW3 from
DevConfig
can also be used to perform maintenance (see
Appendix B,
Terminal Mode from Connect Screen or DevConfig
).
13. Troubleshooting CRVW3 Networks
By following the tasks outlined in Section 11,
Operation of CRVW3 Networks
,
and Section 12,
Maintenance of CRVW3 Networks
, for operating and
maintaining your network of CRVW3 stations, you can identify problems with
the system when they emerge or very soon after they occur.
The
Status Monitor
is a key tool for identifying that a problem in the system
exists (see Section 11.1,
Monitoring Automatic Data Collection
, for guidance
about using
Status Monitor
). Some common indicators that something is
wrong with a station are:
Automatic (scheduled) collection is not working as shown by the
Status Monitor
or
Table Monitor
You can’t connect to the station in the
LoggerNet
Connect Screen
Clock checks (
SetupScreen
) are not working
Manual collection doesn’t work (
Custom Collect
and
Collect Now
)
You can’t view the
Station Status
(
Summary
and
Status
Table)
The station is able to communicate, but the data that is collected from
that station has problems
You should troubleshoot problems as soon as possible after they arise. Some
clues relating to the source of the problem can change (become more obscure)
over time. Small problems can often escalate into larger ones, due to cascading
consequences.
Troubleshooting a part of the system that has never worked is strongly related
to the installation process. Review Sections 7 through 10 as a first step of
investigation in such cases.
When a problem arises in a system area that used to work but has recently
stopped working, the main question to ask is
“What changed?”
What changed
in the system to cause the station to stop operating? When did the failure
begin? Examine key aspects of the system and its recent maintenance history
to obtain clues about changes made to the system. Sometimes a change to the
system that seems harmless or unrelated turns out to be the cause of the
trouble.
When you begin troubleshooting a system, you do not yet know the source of
the problem. You should suspect all parts of the system (communications,
power, repeaters, base station, software,
LoggerNet
computer station issues)
until you determine what went wrong. Use the clues given by the problem to
narrow your focus. However, you may need to broaden your focus from time
to time if causes of the problem fail to emerge.
Sometimes the problem is caused by intentional changes to the system,
sometimes it is caused by unintentional changes to the system. Sometimes
problems are caused by acts of nature (lightning strikes, storms, animal
84