Document toolboxDocument toolbox

SA380TX and SA380TX-L Training : Commission

Owned by Mark Beeson (Deactivated)
Last updated: Jun 15, 2023 by George Davies
10 min read

As an outcome of this section of the course you shall know how to:

  • Check Firmware version and upgrade if required.

  • Check for GSM connectivity

  • Enter site specific data

  • Configure Master / Slave networks

  • Configure analogue & digital inputs

  • Configure simple digital acquisition

  • Configure DC Track circuits

  • Configure electric drive switch machines

  • Configure Electro hydraulic switch machine configuration 

Finding firmware version

SA380TX

https://mpec.atlassian.net/wiki/spaces/SSD/pages/724500955

SA380TX-L

Firmware version can be found on the “Real-Time” tab

 

Checking the correct firmware version

You may check and obtain the latest versions of firmware from the Mpec Centrix downloads page.

https://www.centrix.org/downloads

This will display the latest Network Rail RADAR approved firmwares.

If SA380TX devices are to be used in Master / Slave Networks then it is critical the SA380TX is of a Modstate 3 or beyond, and running recent firmware.

https://mpec.atlassian.net/wiki/spaces/SSD/pages/711885459

Network Rail presently allow version 1184 firmware for such applications which is a available by special request.

Upgrading Firmware

SA380TX

Firmware upgrade paths for the SA380TX are diverse and quite complex. Please follow the extensive guide here.

https://mpec.atlassian.net/wiki/spaces/SSD/pages/724500869

SA380TX-L

Firmware upgrade is accomplished using the commands tab:

If you are upgrading firmware past a stepping stone version, then you must upgrade to the stepping stone version first.

For exaple:

  • Stepping stone version is 2699.

  • To upgrade from 2678 to 2739, you must first upgrade to version 2699, then upgrade to version 2739.

On occasion, you may discover that web pages fail to upgrade. If this occurs:

  • Be patient, the copy process takes quite a long time. Sometimes the support tools report failure when upgrade has simply yet to complete.

  • If problems persist, please repeat the upgrade.

Connection settings

For Network Rail RADAR applications, your connection settings should already be set.

SA380TX

Detailed information regarding the discovery and setting of the connection profile can be found here:

SA380TX-L

These settings much match in order to connect to the RADAR system.

Verifying the Connection

There are several things that cause connection issues:

  • Poor GSM signal strength. This can prevent failure at any stage

  • Inactive SIMs. This prevents GSM operator registration

  • Incorrectly setup SIM. This can prevent the creation of a TCP/IP session.

  • Network Issues. Issues with the operator network can cause server handshaking or data transmission to fail.

  • NR RADAR server unavailable will cause server handshaking or data transmission to fail.

How to troubleshoot

On an SA380TX, the state of the GSM connection can be found towards the bottom of the “About” screen.

On an SA380TX-L it is found in the “Real Time” info pane:

What to look out for

 

 

Fix

 

 

Fix

GSM Registration

Should be REGISTERED.

on the HOME network

The operator should be O2

Check SIM is active

Check GSM antenna positioning

GSM Signal

Ideally >30%
Signal strength is not a great indicator of signal quality, especially on 3G networks

Check GSM antenna positioning

IP Session Attach

SA380TX

GSM State: PPP

SA380TX-L

Modem State: PPP Start

followed by

A valid IP address is displayed.

Check IP address matches Network Rail address range:

172.16-31.xx.xx

Check SIM has the correct APN active

Check connection profile settings (APN)

Check GSM antenna positioning

Server Unavailable

Modem / GSM State enters FALLBACK

Check connection profile settings (URL)

Liaise with Network Rail RADAR team.

All OK

 

This is required to deploy and identify the datalogger on the radar system.

SA380TX

Set Site Name:

Set Device ID:

 

SA380TX-L

Extensive instructions for setting up master-slave networks can be found here:

Once the network is configured, all further configuration takes place on the SA380TX.

Troubleshooting

  • Check RS485 wiring. Most issues are due to poorly terminated or incorrect wiring.

  • Autodetect feature is no fool-proof. Use manual configuration if autodetect struggles to pick up slaves.

  • Channel lists can quickly get into a mess if slaves are detected multiple times. If in doubt, perform an config erase on the SA380TX and start from a clean slate

 

SA380TX

Analogue Inputs

Via the touchscreen:

  • Typically a case of selecting the correct sensor and assigning the correct name.

  • New sensors can also be created

Example settings for a Clamplock pressure sensor are shown below:

Field

Setting

Notes

XML

Name

Clamp Pressure

 

f=”CLAMP PRESSURE”

Averaging

DC RMS or mean

both filter types will give equivalent output

avg="DC RMS"

avg="mean"

Units

BAR

 

units=”BAR”

Decimals

1

Readings will reported to 1 decimal place

dp=”1”

Value at 4 mA

0

4 mA = 0 BAR

v4ma=”0”

Value at 20 mA

120

20 mA = 120 BAR

v20ma=”120”

Zero Threshold

2

Captures that use this sensor have a noise floor of 2 BAR

zero=”2”

Type

Linear

Linear mapping between 4-20 mA input and BAR output.

Not required

Analogue Channels can be set up using the web interface:

Creating a new sensor requires editing the raw XML.

Note that:

  • Each sensor requires a unique ID (id=”13” in above example)

  • The “lock” field governs whether or not the sensor can be deleted using the touchscreen.

Verification

Where possible, confirm that analogue inputs behave as you would expect:

The real-time display will show the value, units, channel and sensor name.

Digital Channels

Via the touchscreen:

…or via the web interface

Verification

The real-time and home screen can both be used:

SA380TX-L

All channel setup is performed via the web interface

The are a few key differences to the SA380TX

  • The TX-L does not support “sensors”. Sensor setting must be entered individually for every channel.

  • The TX-L supports absolute an relative acquisition. Always use absolute for NR RADAR applications.

  • The sampling / filtering method is global by default, but can be changed per channel. Global settings can be found towards the lower left of the screen.

Verification:

Use the rea-time display to check that the readouts match expectation.

 

Point Calling (TX config instructions)

  1. Name all the channels which matches the diagrams and to see when on digital contacts whether they are front or back contacts. Analogue channels, the names will have to be changed with the correct abbreviation for example IL385A WI and to see whether when naming the analogue channels hvae they got a sensor attached to that particular channels, for example RH 600mA or PCM 20.

  2. If needing to change the sensor type (in most cases PCM 30) which is not on the sensor list, you must go into the XML tab and look for sensor type. Copy and paste LEM PCM 20 into the bottom of the sensors list, it will need a unique ID number which will normally start at 13 and change the sensor type to LEM PCM 30. Also chaage the output values at 4mA which will equal -30 and 20mA which will equal 30.

  3. Default side will have to be changed according to the diagrams so it will normallly be in this particular sequence, such as the mileage, number of chains, enigneering reference (ELR) then _ logger number (if 1 it will be 01) for example:

4. Change Unique Device ID so when on Radar (II) you will need to request the customer for there unique Device ID. When on Centrix the Device ID will be the same as the logger serial number.

5. Device ID for each triggered capture should always start from 0!

6. Name of the point for example IL385A

7. Look at the diagrams and when the LHSC are normal you will have to:

  • First give the Unique ID number

  • Name of the point and whether it is N-R (Normal to Reverse) or R-N (reverse to normal) for example IL385A N-R

  • Give it a capture group always start with 1!

  • Send to server

  • On the start trigger, change the setting to digital, then change the channel so when LHSC points are normal you will need to select RHSC (with name of point for example IL385A). So, RHSC IL385A (normal to reverse).

  • Change setting to Down to UP

  • Pre/Post Trigger-500

  • Stop Trigger- Change to Analogue threshold

  • Select what point your monitoring

  • Change to falling edge

  • Change level number to 1 (always 1)

  • Pre/Post Trigger-500

8. When RHSC is normal in the diagrams use the same settings as before (pre/post trigger, unique ID etc), however, when it is N-R (normal to reverse) you will need to select LHSC and point name. When it is R-N select RHSC. Again, they will have to be changed to Down to UP

9. Only push Rowe Hankins to server not PCM’s

10. When you have triggered captures do not send digital contacts to the server, but when there are no triggered captures send the digital contacts to the server!

11. Set config to logger