PROCON-Connect 1.1.0¶
Features¶
97896: Azure IoT Hub is available as a target for the IIoT Connector. Device Twin, Device to Cloud and Direct Methods are supported. Details under Azure IoT Hub.
104953: Dataloggers store meta information from logged tags in the target database. This enables independent evaluation via the connected persistence systems. Details under Data logger.
Fixes¶
93771: Fixed an issue that caused the tag list to not use all the space in full screen mode.
99085: Fixed an issue that caused tags to not check if the default value is within the min/max interval when creating tags.
99088: Fixed an issue that caused the default value when creating string tags to allow a longer string than configured in the Maximum length field.
101581: Fixed an issue that caused the scrolling behavior in the tag list to be impaired if very long strings were included. Values are now always displayed in a single line. If values are too long for the display, they are dotted out at the end. On MouseOver a tooltip shows the whole value.
101582: Fixed an issue that caused the IO type to be displayed incorrectly in the tag editor.
105768: Fixed an issue that caused the event log to be cleared after debug levels were changed.
97471: Fixed an issue that caused the user to not be sufficiently informed about the failure of a tag update via the UI.
103295: Fixed an issue that caused the number of decimal places to be incorrectly taken into account.
107340: Fixed an issue that prevented licensing via WIBU when using a dongle.
99734: Fixed an issue that prevented reconnection attempts if a WIBU CodeMeter server (licensing server) was not available at system startup. The automatic connection attempt is now made every t += 15 seconds up to a maximum t of 5 minutes.
108438: Fixed an issue that caused Influx type data loggers to no longer be displayed under u-OS after restarting the device. The problem was also the cause of no connection details being displayed in the event log under u-OS.
103463: Fixed an issue that caused arrays to be incorrectly recognized and created as simple tags when importing OPC UA.
Known issues¶
If a tag for a driver is imported via the telemetry UI, it does not automatically appear in the tag list. The page must be refreshed, e.g. by pressing F5. Only occurs on u-OS, installations/deployments under Windows and Linux are not affected.