Modbus issues after upgrade of Freelance (v8.1 -> 2016)
We have upgraded a Freelance system from version 8.1 to Freelance 2016:
Old Windows XP computers with Freelance v8.1 have been replaced with new Windows 10 computers with Freelance 2016, project file has been upgraded and firmware has been upgraded.
Plant has been running for a couple of weeks now, and everything seems to be working fine, except for an issue with modbus communication...
Customer is reporting false alarms from input signals coming on existing modbus link. These alarms are pretty frequent, sometimes as often as every hour.
When this occurs, the signals aren't dropping to zero, but actually peaking, and remaining on peak value for 15-20 secons before returning to normal value.
There is no sign of this change in value on sender side...
Does anyone have any experience with this?
This question has not yet been answered.