Werum MSI Interface(AddIn): Wrong state value is written to variable after receiving message

• Related Articles

• MSI AddIn set to 2 (Message is received) all state tags independently of the received MessageID

  Description When the Werum MSI Interface successfully receives a message, in addition to the state variable configured in the message, the value of all other state variables present in the project is also set to 2 ("Message successfully received"). ...

• Werum MSI Interface AddIn is not running in zenon 11

  Description The Werum MSI Interface AddIn does not work in zenon 11 if the simulator is not running on the same computer. If an IP is defined that is not on the same computer, the web server contained in the AddIn will not start. This error has been ...

• Checklist: SAP Interface does not work

  Time estimate:  30 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 ...

• [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] Parameter values from order parameter messages are not written to variables

  Description In the MSI Interface, parameter values from "order parameter messages" are not written to variables as expected. The LOG file refers to: "System.Collections.Generic.KeyNotFoundException: The specified key was not present in the ...