The MODBUS_ENERGY Driver does not store the "Connection timeout" setting in the driver configuration dialog on Windows Server 2012 R2 operating systems.

The MODBUS_ENERGY Driver does not store the "Connection timeout" setting in the driver configuration dialog on Windows Server 2012 R2 operating systems.

Summary

A "Connection timeout" parameter can be defined for the MODBUS_ENERGY driver in the driver configuration dialog under the "Settings" tab. However the defined timeout parameter is not stored correctly when closing the dialog on Windows Server 2012 R2 operating Systems.

Description

A "Connection timeout" parameter can be defined for the MODBUS_ENERGY driver in the driver configuration dialog under the "Settings" tab. However the defined timeout parameter is not stored correctly when closing the dialog on Windows Server 2012 R2 operating Systems.

Solution

An issue was resolved which caused the defined "Connection timeout" Parameter not to be stored correctly. The MODBUS_ENERGY Driver now stores the parameter correctly when closing and reopening the dialog on Windows Server 2012 R2 operating systems. 

Information

The "Connection timeout" parameter can be used to define a time in milliseconds that the driver should wait for a responce from the slave. A communication error will be displayed if there is no responce within this time.

Issue Number: 35408
Fixed on Date: 22.10.2015
Versions: 7.10 0 BUILD 24229 | 7.20 0 BUILD 23281

    • Related Articles

    • The MODRTU32 Driver does not store the "Stopped on Standby-Server" setting in the driver configuration dialog.

      Summary The "Stopped on Standby-Server" setting can be enabled for the MODRTU32 driver, however the setting is not stored correctly after closing the driver configuration dialog.  DescriptionThe "Stopped on Standby-Server" setting can be enabled for ...

    • Redundant License Configuration

      Starting from zenon version 8.00 it is possible to share each license over the CodeMeter network. This allows you to have a dedicated license server. The license server can be any PC or virtual machine which runs CodeMeter. One license for two ...

    • Checklist: OPCDA Server

      Time estimate: 20 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. Do NOT use DCOM in combination ...

    • Checklist: Communication to TwinCat via BeckhoffNG driver

      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. TwinCAT ADS communication library ...

    • FAQ: What are Installation and Security considerations of the zenon Smart Server and Smart Client?

      The attached document (English only) describes in some detail the specifics of the zenon Smart Server Application and the zenon Smart Client Application. Also a short explanation of security features and components is given. More information about ...