MODBUS_ENERGY: driver closes unexpectedly on writing a specific holding register STRING variable

• Related Articles

• When writing a value to a STRING variable of MODBUS_ENERGY Driver with more than 64 characters, only 64 characters including null termination are written.

  Summary When writing more than 64 characters to a STRING variable of MODBUS_ENERGY Driver, only 64 characters including null Termination are written. DescriptionWhen writing more than 64 characters to a STRING variable of MODBUS_ENERGY Driver, only ...

• Modbus Energy driver writes random data after the 0 termination for the string

  Summary When writing a value "abcd" in the runtime to a string variable with a length of 130 characters of a modbus energy driver, the string abcd is written with null termination, followed by random data for the rest of the string length, if the ...

• MODBUS_ENERGY: invalid modbus response to read holding register request does not set INVALID status for variables but uses random value with SPONT instead

  Summary When a Modbus Slave returns a response with an invalid error code "00", according to the modbus specification, the MODBUS_ENERGY driver does not consider this an error and sends random values to the variables with status SPONT to the runtime. ...

• FAQ: From a certain amount of connected Smart Clients the Smart Server closes unexpectedly, what can I do?

  It is possible that the Smart Server closes as it runs out of possible memory address space for a 32-bit application. In this case use the Smart Server 64-bit version.

• MODBUS_ENERGY: Variables remain without value / status under specific circumstances

  Summary Under specific circumstances, the MODBUS_ENERGY driver configured to bundle connections has connections for which variables remain without value and without status, due to connectivity issues for another connection using the same IP address. ...