MSI Interface: The response to an Exception Request includes historic and non historic alarms

• Related Articles

• [MSI Interface]: Invalid Token Request

  Description The Werum MSI Interface cannot communicate with the PAS-X adapter version PASX2X v4.3.0 or higher. An invalid request is sent. Thus, the MSI Interface does not receive a token. Therefore, no messages can be sent to PAS-X. This error has ...

• Checklist: Process closes unexpectedly (***Non-reproducible***)

  Time estimate: 45 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• [MSI Interface] Sending an Exception Message freezes the Service Engine

  Description If an exception message is triggered in the Werum MSI Interface for which an identifier is defined, the Service Engine can freeze. Identifiers enable the correct assignment of the exception message to the linked property. This error has ...

• [MSI Interface] Sending a Exception Message leads to XML deserialize Error

  Description Configured exception messages are not sent in the Werum MSI Interface. This was caused by an XML deserialization error. This error has been fixed. Exception messages are sent again. To benefit from this fix: Update your zenon Software ...

• [MSI Interface] Deleting an Alarm Event Group prevents sending of Exception Messages

  Summary In the Werum MSI Interface, deleting an alarm/event group leads to an error under certain conditions. This has been fixed. Description In the MSI configuration an alarm/event group is used to define an exception message. Later, a group is ...