Document toolboxDocument toolbox

03-02-20 Release 1144


Firmware

Status

Suitable for TX Mod State:
MS1 + MS2MS3+

STEPPING STONE

LEGACY

  •  


New Features

  • Firmware version has dropped the "1.5G" moniker. All firmware releases from hence-forth will simply be referred to as a number. This will make the SA380TX commensurate with all other mpec products.

New Slave Type - Bender BMS for IRDH575

The SA380TX now supports the "Bender-BMS" protocol over RS485. This protocol is used by some of the isolation monitor and fault locator equipment manufactured by Bender GmBH.

This protocol is used by the IRDH575 isometer and fault repeater widely used by Network Rail in the UK.

To configure the SA380TX to monitor an IRDH575 device please follow the following configuration steps:

  • Set the "RS485 Owner". This instructs the SA380TX to converse using the Bender-BMS protocol on the RS485 bus. It means that no other devices may use the RS485 bus on this particular SA380TX.

  • Configure a new "Slave" device (typically in the 1st position) and instruct the SA380TX to expect a Bender device. Note it is only possible to configure a single Bender device, and indeed only a single slave device on the SA380TX in this scenario

  • The SA380TX will then create the following Analogue and Digital Channels that can then be used to set up data acquisitions.

    TypeNameDescription
    AnalogueResistanceThe resistance to earth of all connected feeders in parallel. Measured in kΩ
    DigitalBMS CONNConnection Error Flag. UP = Connection Fault, DN = Connection OK
    DigitalLO alarmIndicates that resistance has dropped below the 1st alarm threshold (Typically 150 kΩ)
    DigitalLO-LO alarmIndicates that resistance has dropped below the 2nd alarm threshold (Typically 50 kΩ)
    DigitalFeeder 1 AlarmIndicates that the worst fault appears on the No. 1 feeder.
    DigitalFeeder 2 AlarmIndicates that the worst fault appears on the No. 2 feeder.
    DigitalFeeder 3 AlarmIndicates that the worst fault appears on the No. 3 feeder.
    DigitalFeeder 4 AlarmIndicates that the worst fault appears on the No. 4 feeder.
    DigitalFeeder 5 AlarmIndicates that the worst fault appears on the No. 5 feeder.
    DigitalFeeder 6 AlarmIndicates that the worst fault appears on the No. 6 feeder.
    DigitalFeeder 7 AlarmIndicates that the worst fault appears on the No. 7 feeder.
    DigitalFeeder 8 AlarmIndicates that the worst fault appears on the No. 8 feeder.
    DigitalFeeder 9 AlarmIndicates that the worst fault appears on the No. 9 feeder.
    DigitalFeeder 10 AlarmIndicates that the worst fault appears on the No. 10 feeder.
    DigitalFeeder 11 AlarmIndicates that the worst fault appears on the No. 11 feeder.
    DigitalFeeder 12 AlarmIndicates that the worst fault appears on the No. 12 feeder.
  • The analogue resistance channel will typically vary in an exponential fashion. A deviation of several 100 kΩ being typically of little concern when the background reading is sat in the mega-ohm range, whilst a difference of 1 kΩ could be substantial if the background reading is at 50  kΩ.To set up a such a relative acquisition follow the instructions below
  • As the resistance is measured from a slave device, a standard Acquire-on-Change is required in order to force updates from the slave device. Set the Acquisition threshold to 1 kΩ, but ensure "Push to Server" is disabled.

  • In order to send a relative acquire-on-change event, you must set up a new "Rail Event" as shown below. This will ensure that data is only transmitted when the value is observed to change by 5% or more from the previously acquired value.



Bug-Fixes / Minor Enhancements

  • Acquire-on-Change config migration fix. Acquisition threshold was nor correctly migrated from the old style, to the new style configuration
  • MIMOSA message web-socket time-out extended to 60 seconds. Prevents 2G devices struggling to send large messages.
  • Minor enhancements to the way in which the device interacts with Centrix during the firmware upgrade process to make the process more efficient.