Bristol FB300 RTU Troubleshooting and Diagnostic Procedures

Quick Answer

Most Bristol FB300 field issues fall into five categories: communication failures (serial/Ethernet/radio), analog input drift or error, digital I/O faults, DNP3 event reporting problems, and power supply issues. Systematic diagnosis using OpenBSI diagnostics and onboard LED indicators resolves the majority of problems without replacing hardware.

Diagnostic Workflow

flowchart TD
  A[Problem reported] --> B{Can you connect with OpenBSI?}
  B -- No --> C[Check power, LEDs, cables]
  C --> D{Power LEDs normal?}
  D -- No --> E[Power supply / fuse issue]
  D -- Yes --> F[Serial/Ethernet cable or config issue]
  B -- Yes --> G{What type of problem?}
  G --> H[Communication to SCADA master]
  G --> I[Analog input reading error]
  G --> J[Digital I/O fault]
  G --> K[DNP3 event issue]
  H --> L[Check DNP3 config, addressing, timeouts]
  I --> M[Check wiring, scaling, transmitter]
  J --> N[Check wiring, interposing relays, card]
  K --> O[Check event classes, deadbands, buffer]

Problem 1 — Cannot Connect with OpenBSI

Symptoms

OpenBSI shows "communication timeout" or "no response" when attempting to connect to the FB300.

Diagnostic Steps

1. Check power: Verify DC voltage at the FB300 power terminals is within spec (10–30 VDC). Check fuses.
2. Check LEDs: The CPU module has status LEDs —
   • PWR (green): Solid = power good. Off = no power or blown fuse.
   • RUN (green): Solid or blinking = CPU executing program. Off = CPU halted or no program loaded.
   • ERR (red): Solid or blinking = hardware fault or configuration error.
   • COM (green/yellow): Blinking = active communication on that port.
3. Verify cable: For RS-232, ensure you're using a straight-through cable (not crossover) unless the FB300 port requires it. For Ethernet, verify link LEDs on both ends.
4. Match parameters: Confirm OpenBSI's serial port settings (baud, parity, stop bits) match the FB300's port configuration.
5. Try a different port: If the FB300 has multiple serial ports, try connecting through an alternate port to isolate a port failure.

Problem 2 — Analog Input Reading Incorrect

Symptoms

Analog value shows 0, full-scale, erratic, or offset from expected reading.

Diagnostic Steps

1. Measure at the transmitter: Use a multimeter to verify the transmitter is outputting the expected mA signal. If the transmitter is faulty, replace it.
2. Measure at the FB300 terminals: Measure the mA signal at the FB300 input terminals to verify the signal arrives without loss. A significant difference indicates a wiring problem (broken wire, loose terminal, water in junction box).
3. Check scaling configuration: Open the point in OpenBSI and verify the zero, span, and input type match the physical transmitter. See our analog scaling guide for common mistakes.
4. Check for ground loops: Disconnect the instrument shield at the RTU end and see if the reading stabilizes. If it does, you have a ground loop — re-route the shield to single-point grounding.
5. Swap channels: Move the suspect input to a known-good channel. If the problem follows the wire, it's a field wiring or transmitter issue. If it stays on the original channel, the I/O card channel may be damaged.

Problem 3 — Digital I/O Not Responding

Symptoms

Digital input doesn't change state in OpenBSI, or digital output doesn't actuate the field device.

Diagnostic Steps

1. Digital inputs:
   • Measure voltage at the FB300 input terminal with a multimeter. For dry-contact inputs, verify the contact closure with an ohmmeter.
   • In OpenBSI, check the raw input state (before any logic processing) to determine if the issue is in wiring or logic.
2. Digital outputs:
   • In OpenBSI, force the output ON and measure voltage at the output terminal. If voltage is present but the field device doesn't respond, check the interposing relay and downstream wiring.
   • If no voltage appears at the terminal when forced, the output channel may be damaged — swap to a spare channel and retest.
3. Check interposing relays: Relay contacts wear out over time, especially on frequently cycled outputs (pump starts). Pull the relay and test with a multimeter for contact resistance.

Problem 4 — SCADA Master Not Receiving Data

Symptoms

SCADA master shows "offline," "communication failure," or stale data for the FB300.

Diagnostic Steps

1. Verify DNP3 addressing: Confirm the FB300's outstation address matches the SCADA master's configuration. A single-digit mismatch causes complete communication failure.
2. Check the communication path: For radio links, verify radio signal strength and that the radio modem is locked to the correct frequency. For cellular, check signal strength and verify the APN and IP address configuration.
3. Review DNP3 event log: In OpenBSI, check the DNP3 communication statistics — look for increasing timeout counts, CRC errors, or fragment reassembly failures.
4. Loopback test: On serial connections, install a loopback plug on the FB300's communication port and verify the port can send and receive data. This isolates port hardware failures from configuration or network issues.

Problem 5 — Power Supply Issues

Symptoms

FB300 resets randomly, LEDs dim momentarily, or the unit fails to power up in cold weather.

Diagnostic Steps

1. Measure voltage under load: A battery that shows 12.6 V unloaded may sag below 10 V under the FB300's current draw, especially in cold weather when battery capacity drops.
2. Check solar charge controller: Verify the controller is charging the battery correctly and that the solar panel output matches the rated specifications (panels degrade over time).
3. Inspect connections: Corroded or loose power connections cause intermittent voltage drops under load. Clean and re-torque all power terminals.
4. Check for parasitic loads: Radio modems, heaters, and other accessories sharing the same battery can draw the voltage below the FB300's minimum input threshold during peak demand.

Preventive Maintenance Checklist

• Inspect and clean enclosure seals, ventilation filters, and desiccant packs quarterly.
• Test battery voltage under load annually (replace batteries every 3–5 years in oilfield environments).
• Verify ground resistance annually with a fall-of-potential test.
• Check all terminal connections for tightness annually (thermal cycling loosens connections over time).
• Review OpenBSI diagnostic logs for communication error trends that may indicate degrading radio or cable infrastructure.
• Update firmware when Emerson releases security patches or bug fixes relevant to your deployment.