API - ISoMappingRule and ISoMappingRuleCollection are located in the wrong namespace

• Related Articles

• IIoT Services API delivers the wrong report parameter data type, equipment tree nesting or time filter granularity when the report parameter name contains an underscore

  Description In the Report Engine, a parameter name with an underscore is used in a report. If this report is deployed with the "Available in IIoT Services" option active, the IIoT Services API returns the wrong report parameter data type, the wrong ...

• MdiElement.Type returns wrong element types

  Summary MdiElement.Type returns wrong element types - e.g. for a button, tpLine is returned. Description MdiElement.Type returns wrong element types - e.g. for a button, tpLine is returned. Solution An issue was addressed in the API - now the ...

• FAQ: How to hook to function execution in the Service Engine over the API?

  COM: RtFunctions contains a new event (PreExecuteFunction) which gets fired before a function is executed. This event handler contains a parameter which is a temporary copy of the function which is about to be executed. ADDIN: An identical event ...

• The default Namespace Index used by the zenon OPC UA server is not entered in the server Namespace array which may lead to OPC UA clients not being able to browse the OPC UA server address space

  Summary OPC UA clients that browse an OPC UA server address space based solely on the entries in the server namsespace array may not display any results following the browse of the server. An example of such an OPC UA client is the OPC UA client in ...

• The OPCUA server process gateway may close unexpectedly with an unhandled exception when configuring the namespace index

  Summary When entering a value "0" for the namespace index in the OPCUA process gateway configuration, an error message is displayed noting that this namespace index is reserved for OPCUA itself. When the message is acknowledged using the enter key on ...