Sutron Accububble 5600-0131-4

Questions and Answers

G
Gary JacksonAug 9, 2025
Why Sutron Accububble 5600-0131-4 Measuring Instruments showing no data?
- L
  Lisa WilliamsAug 9, 2025
  If your Sutron Measuring Instruments are showing no data, several factors could be at play. It could be due to faulty wiring, so check all wiring and terminations. Another cause might be no power, in which case you should check the fuse in the data recorder and power at the sensor, remembering there's no fuse in the sensor itself. Also, ensure the data recorder is set up to request data at the proper address and that the sensor is responding to the correct address, verifying internal address dip switches. Finally, verify that the address is proper case and commands are upper case.
N
Nathaniel AndersonAug 19, 2025
What to do if Sutron Accububble 5600-0131-4 showing erroneous data?
- V
  Virginia RiggsAug 20, 2025
  If your Sutron Measuring Instruments are showing erroneous data, consider the following potential causes and solutions: * **Wrong units selected:** Use the M command to verify that the desired units are selected. * **High unstable readings when bubbler is utilized:** Use the XPC and XPT commands to configure the unit for the site, or use 0XPR+240! to purge the line for four minutes. * **Low readings when bubbler is utilized:** Check for leaks in the system by using the XPL command. * **Erroneous offset entered:** Display the field calibration offset using the M3 command and verify it. Re-calibrate the offset. * **Erroneous user scale and offset entered:** Display the user scale and offset using the M3 command and verify.
R
Richard HillAug 28, 2025
What to do if Sutron Accububble 5600-0131-4 Measuring Instruments showing garbled data?
- C
  Cody ShepardAug 28, 2025
  If your Sutron Measuring Instruments are showing garbled data, it could be due to multiple sensors set to the same address. To resolve this, check the address settings of all SDI sensors, remove all other sensors from the recorder, and add them back one at a time. Alternatively, the issue might stem from a command issued to a wild card address (* or ?). In this case, remove all other sensors from the recorder and try again.