Modbus Alarm Message L681 FIX=0000 AP=2D1B
Voted best answer
Hello,
with AdvaBuild 3.7 there were new Modbus diagnostic introduced. We had the same issues on various sides after an upgrade to that version.
THe problem has been there alle the time, it was just not raised in older versions.
So in your case you may want to check the Input TimeOut filed of the MVI. We had situations where the PLC just didn't respond fast enhough to an request.
BR
Stefan
with AdvaBuild 3.7 there were new Modbus diagnostic introduced. We had the same issues on various sides after an upgrade to that version.
THe problem has been there alle the time, it was just not raised in older versions.
So in your case you may want to check the Input TimeOut filed of the MVI. We had situations where the PLC just didn't respond fast enhough to an request.
BR
Stefan
Answers
FIX=0000 AP=2D1B MODULE CPREPLY TASK CPRCVLID FIX=NO_FIXED_ERR, AP=CP+CP_AISEGERR
AP1=Primary error code, AP2=First channel number of command segment TEXT: PLC: ERR %d ON INPUT FROM SEG FOR ANA CHAN %d CAUSE: An error occurred trying to read an analog segment. EFFECT: The read operation was not performed. ACTION: Verify the command configuration is correct.
AP1=Primary error code, AP2=First channel number of command segment TEXT: PLC: ERR %d ON INPUT FROM SEG FOR ANA CHAN %d CAUSE: An error occurred trying to read an analog segment. EFFECT: The read operation was not performed. ACTION: Verify the command configuration is correct.
Add new comment