| Page Properties | ||||||
|---|---|---|---|---|---|---|
|
Summary
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
TODO
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
DC Track Circuit
Second Track Relay
...
Assets
Hy-Drive Points - Motor Current Alarm
Previously Hy-Drive Points Alarms required hydraulic pressure monitoring, in this release the Points Alarm wizard has now been updated to support the training of Points Alarms against a motor current capture channel/s when pressure channels are not available.
In the case of 2 motor current channels, the alarm generated will use thresholds that are the least restrictive based on the training data on the two motor current channels.
DC Track Circuit - Second Track Relay
DC Track Circuit Assets can now allows be configured with an additional track relay (TR2).
...
Track Circuit Assets with this additional relay will use the following logic chart for display on the playback map:
TR1 - DN | TR1 - UP | TR1 - UNKNOWN | TR1 - No Relay | |
|---|---|---|---|---|
TR2 - DN | Occupied | Occupied | Occupied | Occupied |
TR2 - UP | Occupied | Unoccupied | Unoccupied | Unoccupied |
TR2 - UNKNOWN | Occupied | Unoccupied | UNKNOWN | UNKNOWN |
TR2 - No Relay | Occupied | Unoccupied | UNKNOWN | UNKNOWN |
Alarms
...
Logger Contact Alarm
...
Hy-drive points alarm with no pressure channels
Added the ability to use the points alarm wizard to generate a points alarm on a hy-drive asset that does not have any pressure channels, but does have motor current channels. The generation of this alarm uses our standard points generation method, except for when there are 2 motor current channels on the asset.
...
- Sites with multiple Loggers
The original design of the Logger Contact Alarm was very much based on the idea that sites generally have a single logger. Over time, this assumption is less and less valid, and it was apparent that the Logger Contact Alarm needed a rethink.
For sites with multiple loggers, Logger Contact Alarms can now raise multiple times, even when not explicitly cleared by the user. A new raise will be generated and a new email will be sent when any logger on the site goes offline for the defined period.
Additionally, a logger that comes back online while the alarm is raised, and subsequently drops offline again, will retrigger the raise (and send the normal email messages). This behaviour applies to sites with single and multiple loggers.
We hope this will provide users with more insight into the state of their loggers and allow them to more easily react to loss of contact incidents.
Security
Mandatory MFA Warning
...
As part of MPEC’s ongoing ISO 27001 accreditation, any users with admin access will be required to enable Multi-factor authentication (MFA) in the next Centrix release (R108). In addition, it is expected that all users will be required to enable MFA in a future release. As preparation for this, a new alert message will be presented to users without MFA enabled when logging in for the first time.
Minor amendments and fixed issues
Fixed an issue where the Alarm Wizard would fail and not notify the user.
Logger status would sometimes fail to show for certain logger types.
Some reports were failing to deletecould silently fail.
Report deletion now works correctly for all report types.
Raw analogue and digital reports now run against a single hour correctly.
Asset playback page navigation by Tag improved to align better with track occupations.Loggers channels list dates now display in the site’s timezonetag is now aligned to the associated track occupation.
The channels list on the logger management page now shows last contact times in the correct time zone.
Virtual logger log message list now supports live updates for new incoming messages.