New Features

The SA380TX itself contains no new features, however the bundled slave firmwares have been updated:

• VTi21 Firmware version 148:
  • Support has been added for Reed FDM and AC sensing VTi21 variants.

• SA380TX-L Firmware version 2739:

  • Changes from beta release 2736 have been incorporated into this full release:

    • Optional automatic configuration of communication protocol

    • MIMOSA bugfixes for missing EbiTrack side band ratio channels and triggered capture time alignment with triggers.

    • See detailed release notes for further information.

  • This version also contains an additional NTP bugfix however this is not relevant to TX-L loggers configured as slaves.

• SA380 Firmware version 614:
  • Fixes an issue with very large configurations.
  • Adds provisional support for remote configuration of standalone SA380 loggers through Centrix.

Bug-Fixes / Minor Enhancements

• Renamed various instances of "protobuf" from web and touch screen UI. "Protocol Buffers" is the technology upon which mpec's RailDAQ protocol is built, however this isn't relevant or clear to the user. "Protobuf slaves" are now referred to as "mpec Slaves" in the user interfaces. "Raildaq Slave" is has also been renamed to "Centrix Connection" for the sake of clarity. Users are reminded that (at present) this connection is only used for configuration and firmware update, and that the MIMOSA connection must also be configured in order for logged data to be pushed to the server.
• Digital channels configured as back contacts could produce spurious transitions in certain circumstances in large master-slave networks.

• In rare circumstances large MIMOSA messages can become stuck in the TX's message queue when the server fails to acknowledge their transmission within the specified timeout. To guard against this, an optional configuration item has been added to discard large messages should the server repeatedly fails to acknowledge. The size of these messages (in bytes) is configurable from the touch screen:

   

  For the vast majority of users this option should remain unset, and it should only be used if experiencing specific problems with messaging.