Common Problems

Master-Slave Devices not Connected

Check A to A, B to B.

If wiring run over 20 m, ensure termination resistors are used.

Check that TX-L is set to be a "Slave" logger

Check Master RS485 ownership is set to "TX Slaves"

Check that slave serial number on TX matches the serial number of the TX-L

How to spot unhealthy master slave (Syslog and about screeshot)

How to spot a healthy master slave (syslog and screenshots)

Device not communicating with Centrix

Modem not registering - SIM not active, poor signal strength

No Data session - Incorrect tariff on SIM, poor signal strength, incorrect APN settings

No Server Connection - Poor signal strength, incorrect server settings, server unavailable

Field Device not visible of Centrix - Device not assigned to site, Security Header Incorrect (Use Replace)

Commissioning Sensors

Connection of Sensors

Double check correct sensor is attached to correct input channel

Double check that each input channel is connected to correct part of the signalling system.(Correct busbars for voltage transducer, correct cable for CT's)

Where current flow to the switch machine is split between two or more conductors, ensure that all current carrying conductors pass through the appropriate CT.

There is no need to wrap multiple "turns" of wire around the CT. simply pass conductors one time through the CT aperture.

As all currents are AC, orientation of the CT is irrelevant.

Check sensors using the real time function - Screen on TX, Web Tool on TX-L

Operate each asset being monitored in turn.

Steady voltage expected on voltage channels whilst switch is idle, a dip is expected when the switch is in motion. Begaviour will be similar for both Normal-to-reverse and reverse-to-normal moves.

-42.5V suggests the voltage sensor is miswired or disconnected from the data logger

0V suggest the voltage sensor is disconnected from the signalling busbar.

no current flow is expected while the switch is idle. A characteristic "points profile" is expected on one of the two CT's assigned to each switch machine, whilst that machine is in motion

When commanded Normal-to-Reverse, current must only be observed on the "Reverse" CT. e.g. 701A RPI (701A Reverse Points Current)

When commanded Reverse-to-Normal, current must only be observed on the "Normal" CT. e.g. 701A NPI (701A Normal Points Current)

If the above convention is not followed, the direction of movement will be captured incorrectly by the data logger.

Unexpected behaviour can usually be cured by inspecting the transducer wiring, or changing which conductors are fed through each CT.

Acquisition of Switch Machine Data

To check the motion and direction of switch machines is being correctly collected and transmitted to Centrix:

On the TX

Use the main display

Historic Data as Confirmation

On a TX-L - Use the captures tick boxes

Historic Data as Confirmation

move each asset in turn, both N-R and R-N.

Please wait longer than 0.5 seconds between N-R and R-N moves.

Moves that occur back-to-back too quickly are tagged as "inavlid" by the data logger. This is in order to suppress false alarms that may be generated if there is a change in route-setting commands to the switch mid-movement. Such events cause anomalous waveforms that would otherwise trick the Centrix system in "thinking" that the switch was developing a failure, when in-fact it is behaving perfectly normally.

On the real-time screens check that the "Captures" are correct

Positive Indicators

• Correct Names (One capture observed for voltage, one capture for current)
• Correct Direction (Both Voltage and Current operate in the same direction)
• Both Captures operate DN→UP at the start of the switch movement
• Both Captures operate UP→DN at the end of the switch movement
• For "Tandem" points, both A and B ends are expected to operate near-simultaneously, athough minor timing differences are to be expected, particularly and the end the capture event.

Negative Indicators

• If the captures is observed to operate in N-R and R-N directions simultaneously, or captures in a certain direction do not fire, it is because:
  • Trigger Channels are incorrectly set up
  • Trigger Levels are incorrectly set up
  • CT's are affixed to the incorrect conductors.

For further confirmation, check the historic records on the data logger for a graphical representation of data

Once again, you are looking for correct time-stamping of start and end events, correct direction and sensible data recorded in-between.

A final check can be completed for ensuring the data is visible in Centrix. This should occur within 1 minute of the switch throw occurring in the field. This can be done on any device that runs a modern browser

Trouble shooting

Loggers pre-configured, so issues most likely to do with fitment of CT's. If problems perisst see Page Links or contract mpec for support.