How This Troubleshooting Guide Will Help You
Troubleshooting remote site equipment failures can be tedious and frustrating. It's difficult to even know where to start. Even a simple monitoring problem can have several possible causes. And how do you know you've brought the right tools to even diagnose the problem?
This guide will help you cut through the tedium, the frustration, and the uncertainty of troubleshooting. Step-by-step instructions will show you how to isolate and identify common equipment problems, using the ordinary tools that are always in your toolbox.
| Before You Start: What Tools Do You Need for Troubleshooting? |
3 |
| Section 1: RTU Doesn't Report Alarms |
4 |
| Section 2: Wiring Problems - RTU Doesn't Detect Alarms |
5 |
| Section 3: RTU Sends False or Fluctuating Alarms |
6 |
| Section 4: How to Test RS-232 Connections with a Screwdriver or Paper Clip |
7 |
Section 5: How to Test 202, FSK and RS-422/485 Connections with a Butt Set
|
8 |
| Section 6: Intermittent Polling on 202 and FSK Lines |
9 |
| Section 7: How to Identify Pinouts, with or without a Blinker Box |
10 |
| Section 7a: Identify Pinouts with a Blinker Box |
10 |
| Section 7b: Identify 202, FSK or RS-422/485 Pinouts with a Butt Set |
11 |
| Section 7c: Identify Serial Device Pinouts with a PC |
11 |
| Section 8: Serial Remotes Can't Connect to Master |
12 |
| Section 9: IP Remotes Can't Connect to LAN |
13 |
| Section 10: SNMP Remotes Don't Report Alarms to SNMP Manager |
14 |
| Section 11: Dial-Up Remotes Can't Dial Out |
15 |
Request Info