12-03-20 Release 2736
- Mark Beeson (Deactivated)
- Oliver Skidmore (Unlicensed)
Owned by Mark Beeson (Deactivated)
| Firmware Status | LEGACY |
|---|
New Features
The "protocol selection" field of the SA380TX-L has been upgraded such that now the device can be configured to automatically detect the optimal protocol for messaging. This gives you one less thing to worry about during commissioning.
| Option | Meaning |
|---|---|
| UK NR | Forces the SA380TX-L to only use MIMOSA protocol - as used by Network Rail in the UK |
| mpec | Forces the SA380TX-L to only use mpec RailDAQ protocol - used by mpec for our global Centrix deployments |
| Automatic | Allows the SA380TX-L to select the optimal protocol to use with the server to which it is connected RECOMMENDED |
What is MIMOSA protocol?
- MIMOSA is a human-readable text based protocol selected by Network Rail to allow data logging devices from different vendors to connect to the Network Rail Intelligent Infrastructure system.
- It is perfectly fit for purpose for the transmission of asset data, however, due to its text based nature, messages tend to be rather large, limiting throughput on 2G GPRS connected devices.
- Features such as device configuration, time sync and firmware upgrades, although possible, are not well supported by the protocol. This is not so much of an issue for Network Rail Intelligent Infrastructure users, as field devices generally have a resolvable IP interface over which such actions can be performed.
- MIMOSA protocol is supported by the Network Rail Intelligent Infrastructure system and Centrix.
What is mpec RailDAQ protocol?
- mpec RailDAQ (Railway Data Acquisition) protocol is a binary (machine-readable) protocol based on the principles of MIMOSA. It has been developed by mpec to overcome some of the limitations of the MIMOSA protocol.
- The principals of the transmission of analogue and digital data from field assets match those found in the MIMOSA protocol, they are functionally equivalent.
- Due to its binary nature, RailDAQ is more than 10 times more economical in terms of data throughput compared with MIMOSA.
- This greater throughput combined with its more aggressive connection strategy means that field devices are quicker to recover in instances of "coms outage", and less likely to get "backed-up" in instances of heavy load.
- More flexible data bindings specifically designed to work with Centrix make it quicker and easier to deploy new field devices on the Centrix system compared with MIMOSA,
- For Centrix users, lack of direct IP connectivity to field devices is a big drawback. This is because most field devices do not have resolvable IP addresses as they are connected over the public IP network. This leaves devices difficult to configure and upgrade once deployed.
- The RailDAQ protocol has been extended to include features such as:
- Time sync with the server, (meaning all field devices are tightly time aligned).
- Remote configuration (no site visit required to tweak a configuration).
- Firmware upgrade (allows individual and bulk firmware upgrade operations to be instigated from Centrix).
- Only Centrix supports the RailDAQ protocol. mpec recommend RailDAQ protocol for use with the Centrix system.
Bug Fixes
- Power Management: Power control of analogue channels is now more robust when handling brown-out conditions. Some devices were found to erroneously power-down analogue channels upon powering up the modem. This has only been seen in devices prior to leaving the factory and no reports of problems in the field have been received.
- EbiTrack Monitoring: The "Sideband ratio" channel (ratio of upper and lower side-band currents of an EbiTrack 200 receiver) were not being transmitted when in MIMOSA mode for EbiTracks configured in positions 2 to 8. This has now been resolved.
- Triggered Captures (Point / Switch Monitoring): The capture waveform channel was not correctly time-aligned with digital trigger events when transmitted to server from the device when in MIMOSA mode. This has now been resolved.
Before
After