Hi Valery L

Did you manage to solve your problem? I have a similar problem.

​

------------------------------------------------------------------------------------------
Split from OB122 PLC diagnostic buffer decoding.

Hello,

if you read your diag buffer lines, you can easy read what problem is (read/write), what area (PIB/PQB <address>) and where this action is performed (FB number). Generally, device number (Slave address) is expected to be Online and accessed. PB cable problem? Device with described DP address turned OFF? Check that as your buffer shows, very easy.

Thank you for your response,

Yes I have tried to trace the problem but I do not have any address associated with the ones I have in the diagnostic buffer: 6650, 6648, 3652, 3654, 3950...

Hello,

pls check what modules you're accessing (AI,AO,...) and check module address. Simply if you have some modules with sensors or other type you simply access them from code and dsetination address is accessed PIB or PIW. Look at your HW cfg and check that module address from diag buffer with each modules attached at your HW cfg where this address can exists. Look, your post is really very weak to give some eaxct help in case we don't know nothing what is happened at your side and if all your HW cfg is same as actual existed real. You need check each HW and compare with HW cfg, then simply program want access that modules (I expect them, confirm pls) for data.