Tag quality is good but values are zero. got bad address in block error kepware EX6

[RP_11012058]

In kepware there are energy meters tags showing tag quality good but values are shown as zero. All of changes in setting like reducing block size, recreated channel and devices, restarted kepware number of times we got bad address in block error. kepware error guide saying below reason,

Possible Cause:
The driver attempted to read a location in a PLC that does not exist, perhaps out of range. For example, in a
PLC that only has holding registers 40001 to 41400, requesting address 41405 would generate this error.
Once this error is generated, the driver does not request the specified block of data from the PLC again. Any
other addresses being requested from this same block are considered invalid.

Kindly anyone post a solutions for the above problem.

[MKhatri]

Hello,

I hope this email finds you well. I wanted to address the query you brought up regarding the examples you mentioned. It is recommended that you consider reducing the block request size in the Modbus driver for optimal performance. If you have any further questions or need assistance with this adjustment, please feel free to reach out.

Regards,

Mohit

[RP_11012058]

Hai sir,

          I tried with reducing block size in modbus driver settings. reduced from 32 to 4 and checked with 3 and 1 also. So still only 4 tags are showing unknown with bad tag quality also tags quality is good but reading same value in two tags and with zero values. I attached the image of setting page. Will it get resolved when reinstall the kepware or need to add all devices from scratch?

[MKhatri]

Hello,

I hope you are doing well. I am writing to request your assistance in disabling error handling in the device properties. Specifically, I would like you to change the default action to invalidate the tags for one poll cycle by following these steps: Device Properties > Error Handling > uncheck Deactivate tags on illegal address exception parameter.

For more detailed instructions, I have attached an article that provides further information on this issue: https://www.ptc.com/en/support/article/CS291640

Regards,

Mohit