Firmware Status | LEGACY |
---|
...
Info | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Analogue Acquisition ChangesThe 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 Obtaining quality data for FGC Rx results in poor data quality data for HRE Rx Setting a "relative" change setting of 10% allows good quality data to be obtained during the "track occupied" state, whilst limiting the data collecting during the track clear phase. 10% 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:
The user guide extracts below explains the change in more detail. Acquire-on-ChangeAll analogue input channels are continuously logged using a process known as “Acquire-on-change”. A sample is acquired when the measured value changes by more than a certain amount. If there is no change, there is no sample acquired. Consider the following waveform. The acquired samples are shown as dots. The waveform first changes at a fairly leisurely pace, then there is a spike. Each time the input changes significantly, a sample is acquired. It can be seen that more data points are acquired around the spike. Acquire-on-change is an excellent match for many railway applications. Where there are long periods without much change, very little data is acquired. Where there is more detail in the waveform, more points are acquired. After the data has been acquired it is possible to go back and just “join the dots” and we have an accurate representation of the entire waveform, with the minimum amount of data logged and transmitted. Two methods of Acquire-on-Change are supported. Absolute: In absolute mode, a fresh sample is acquired each time the raw input signal changes by a fixed constant value, for example 5 mA. E.g. If the last sample was acquired at 50 mA, the next sample will be acquired at +/- 5 mA, which is either 55 mA, or 45 mA. An absolute change of 5 mA is required to trigger the next acquisition. The chart above shows how samples would be acquired along a straight line slope. Absolute acquisition is a good fit where the minimum and maximum range of the input signal are well known and an even level of detail is required at all ranges. Relative: In relative mode, a fresh sample is acquired each time the raw input signal changes by a defined percentage since the previous acquisition. It is defined in percent, for example 5%. E.g. If the last sample was acquired at 50 mA, the next sample will be acquired at +/- 5% of 50 mA, which is either 52.5 mA, or 47.5 mA. A relative change of 5% is required to trigger the next acquisition. The chart above shows how samples would be acquired along a straight line slope. Relative acquisition is a good fit where the minimum and maximum range of the input signal are not well known and where increased resolution is desired for small signals, at the expense of decreased resolution of large signals. Example Applications for Acquire on Change:
See SA380TX-L Applications for more detail. All unit configuration is performed using this screen. AnalogueAnalogue Change Threshold If Acq. Method is set to Relative, this number determines the percentage change relative to the last acquired value required to trigger the acquisition of a sample. If Acq. Method is set to Absolute, this number governs the absolute change in signal level required to trigger acquisition of a sample. For NR II DC track circuit monitoring a change threshold of 6 mA absolute has been suggested. EBI TrackChange Settings These settings dictate how sensitive the “Acquire-on-change” settings are for all monitored EbiTracks. Parameter / Units - These fields are fixed for EbiTrack monitoring and cannot be changed Change Threshold - Change the acquisition sensitivity of each channel in these fields.
The default settings are suitable for NR II EbiTrack 200 applications. Where EbiTrack 400 Receivers are to be monitored, it is suggested that IAVE is set to 10% Relative due to the variance in set-up current levels. See SA380TX-L Unit Configuration for more detail Server LED Indication ChangesThe behaviour of the "Server LED" was incorrect when the SA380TX-L was set to use the "RailDAQ" protocol. The behaviour has been fixed and re-defined. This is explained in the user-guide extract below. LED’sThe TX-L front panel features 8 LEDs. The meaning of these LEDs is detailed in the table below:
*It is normal to observe a “Processor Sync Error” during initial boot and during firmware upgrade. ** The table describes behaviour in MIMOSA protocol mode. In RailDAQ mode, the following behaviour is observed:
See SA380TX-L Hardware for more detail Bug Fixes
|
Info | ||
---|---|---|
| ||
Bug-Fixes
|
Info | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||
New FeaturesWeb Config Changes:
An event can be:
GSM Connectivity Changes
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 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.
Automated Firmware Upgrade and Configuration via Centrix
Major Bug Fixes
Minor Bug Fixes
Known Issues
|
...