Web Config Changes:
- Revised Standalone / Slave settings
The SA380TX-L can operate in "standalone" mode (An independent data logging device), or "slave" mode (Acting as a peripheral device as part of a master-slave network).
The previous check-box selection proved confusion for users, this setting has been changed to a drop-down menu to make the present mode of operation clear to the user.
Additionally, When set as a "slave", nearly all settings are controlled by the "master" device, settings on the TX-L that are no longer applicable in "slave" mode are greyed out and made unavailable.
- Real Time "Queued Events"
There is a subtle change in terminology here, the "Events to Send" entry in the real time display has been changed to "Queued Events".
An event can be:
- A single analogue or digital acquire-on-change sample.
- A single trigger-capture waveform.
- A single EbiTrack message.
- A single Syslog Message.
- The batching and buffering process will attempt to empty the entire buffer when the buffer size exceeds the "buffer length" configuration parameter, or no data has been sent for "buffer timeout" settings.
- This subtle change will drastically reduce the time taken to clear data buffers containing large numbers of events.
- Syslog messages are only sent when RailDAQ protocol is selected. If MIMOSA protocol is selected, then Syslog Events are "skipped".
- User alerted if a firmware package appears to be incompatible with the TX-L prior to upgrade.
Prevents obsolete or corrupt firmware from being placed on the device.
GSM Connectivity Changes
- Full support for 3G modems (with 2G fallback).
All SA380TX-L devices serial number 7200 onward feature 3G GSM modems. This devices will exhibit more reliable and faster GSM communications. In areas with poor 3G network coverage, the devices will fall-back to the the 2G GSM network.
TCP/IP socket connection attempts will retry 5 times before entering MIMOSA fallback. This will improve connection availability in instances of poor GSM network performance.
The TX-L will now aggressively attempt to connect to the GSM network in areas of poor connectivity. This will also improve connection availability in instances of poor GSM network performance.
The registration status (3G or 2G) will be displayed in the "Registration" field in the "GSM Modem" area of the real-time display.
To provide the user with better feedback about the state of the TCP/IP socket connection to the central data server, the behaviour of the "Server" LED has been revised. The Server light will blink rapidly for up to 5 minutes when attempting a TCP/IP transaction prior to entering MIMOSA fallback. Whilst in MIMOSA fallback, the server light blinks slowly.
Last transmission to the Central Data Server successful. Device is now idle
|Server||Fast Blink||Device is attempting TCP/IP transmission to the server.|
|Server||Slow Blink||Transmission to the Central Data Server has recently failed. Device is now in FALLBACK|
Connected to the GSM Network
Modem Powered On
Slow Alternating Flash (1 sec)
Fast Flash (0.25 sec)
Processor Sync Error*
Steady On or Off
Data Read/Write from database
Analogue or Digital Input Event Detected
Data Transmit/Receive on RS485 Port
Automated Firmware Upgrade and Configuration via Centrix
If the RailDAQ protocol is adopted, the SA380TX-L now supports remote firmware upgrade and configuration via the Centrix platform.
- This exciting new feature allows the user to deploy upgrades / hot-fixes to all or a selection of deployed SA380TX-L automatically.
- Reading and writing of config via Centrix will allow users to configure and troubleshoot loggers in the field, without a fixed IP address connection.
- It will enable sophisticated configuration management and provide a auditable trial of config changes.
- It allows mpec to provide top quality product support.
These features will be gradually rolled out in Centrix over the coming months. SA380TX-L devices must be upgraded to 2676 or later firmware manually before these features can be leveraged.
Major Bug Fixes
- Database resilient to corruption. Previously seen on loggers under high-load in service.
- EbiTrack Timestamp Error Fix. Data from EbiTrack receivers could be timestamped incorrectly.
- RailDaq Push Configuration: TX-L will now send all enabled channels to Centrix.
Minor Bug Fixes
- MIMOSA DAInt Datatype Expanded: Can now report 32 character numbers as 16 characters did not provide enough resolution in certain circumstances.
- EbiTrack Timestamp Errors: In rare circumstances, the time-stamping of EbiTrack events could be erroneous. This is no longer the case.
- EbiTrack Names: Reduced to 31 characters to prevent name string overflows.
- Logger Restart may be caused by polling the logger for large quantities of historic data.