The latest release of SA380TX-L firmware is now available and is approved for use on both the MPEC Centrix platform and the Network Rail RADAR platform.

• The key features of this firmware release are highlighted below as normal.

• It has been a significant time since the prior RADAR approved firmware release. RADAR users may not be be familiar with many of the changes documented in prior releases, therefore a summary of the key changes is provided below for reference.

New Features

SA380TX-L Mod State 5.0 has now been released. This Mod State incorporates a 4G LTE Modem.

• Firmware version 2792 is the baseline firmware for Mod State 5 SA380TX-L dataloggers

• Firmware version 2792 is backwards compatible all SA380TX-L dataloggers

Bug Fixes & Improvements

• Ebitrack Bugfix: “Last Error Code” was not sent to Centrix. Now resolved.

Known Supported Assets

The below list is not exhaustive, as the generic nature of the SA380TX-L lends itself to monitoring pretty much anything with analogue sensors or volt free contacts. The following assets have proven track record of monitoring via the SA380TX-L.

Key New Features:

Clamplock Points Now Compatible with RADAR

The SA380TX-L is now compatible with both Centrix and RADAR hydraulic point monitoring solutions.

To ensure your installation is compatible with RADAR, simply follow these instructions during configuration:

• Create two captures, one for pressure, one for current.

Open

• Ensure start and end triggers for both normal and reserve direction captures match exactly.

  • e.g. Red matches red, blue matches blue, green matches green and yellow matches yellow.

Open

• Doing the above ensure that captures are transmitted to the RADAR platform in form that the system can understand.

Acquire on Change for EbiTrack

The acquire-on-change methodology has been enhanced to allow capture of  "absolute" and "relative" changes in input signals. This was primarily done to accommodate EbiTrack 400 receivers.

Multiple EbiTrack 400 receivers can be configured on a device, with each receiver exhibiting very different levels of "track clear" current between 20 mA and 100 mA. A global absolute Acquire-on-Change setting was unable to capture enough information during the "track occupancy" phase, without gathering too much data in the "track clear" phase or vice-versa. This can be observed in the Centrix graphs below.

Obtaining quality data for GNF Rx results in too much data for FGC Rx

Setting a "relative" change setting of 7% allows good quality data to be obtained during the "track occupied" state, whilst limiting the data collecting during the track clear phase. 7% was chosen, as it lies above the relativistic noise floor of the ITOT channel whilst the track is clear. The Centrix graph below demonstrates the enhanced data quality.

A new GUI element has been added to the config tool to allow the selection of "Absolute", or "Relative" acquire on change types.

To make the distinction clear between the two types of acquisition, and to provide continuity across the mpec product range:

• Absolute Acquire-on-Change is specified in the engineering units of the sensor / channel

• Relative Acquire-on-Change is specified in "Percent", e.g acquire a sample when the signal has changed by "x%". The engineering units are irrelevant.

The user guide explains the change in more detail.

Further Reading:

II/RADAR users may wish to read comprehensive release history using the page navigation tree found on our online documentation platform https://mpec.atlassian.net/wiki/spaces/SSD/pages/687670606 .