Hello sir,

I have same issue but little different,  we have Schneider drive slave and slave Remote profibus DP IO. We are facing some issue that Remote panel (Slave 8)getting stopped, it is the last device in the network. Before this we have Schneider drive (Slave 7).

it was stopped  and started. Now running but sometimes making this issues.

we already changed profibus connector. In simatic manager we already installed  OB82, OB86.

Is there is any problem in cable? how i can rectify this issue.

dchartier

Hello Raph;
In your Diagnostic Buffer messages you have many calls to OB82 (hardware interrupt OB) with the message:
"Requested OB: Diagnostic interrupt OB (OB82)
OB not found, or disabled, or cannot be started in the in the current operating mode"

The first thing you should do is to insert an empty OB 82 in your PLC program and download it to the CPU.
You can do this by right-clicking on the blocks forlder in Simatic Manager, create New, OB. Call it OB 82, and save and download.
The presence of that OB will allow the diagnostic buffer to gather more information on the cause off the problems and prevent the CPU from going to STOP mode (if that is the only type offault present).
then launch your PLC once more, the SF LED will still be lit but the PLC should remain in RUN mode. the diagnostic buffer should contain more precise information on the problem now.
If you get the same message for another missing OB in the diagnostic buffer, add the requested one, or add all diagnostic OBs at once.
See the attached file, taken from the manual: SIMATIC Programming with STEP 7 V5.5

Hope this helps,
Daniel Chartier

Sam-J

Hello sir,

[snip].

we already changed profibus connector. In simatic manager we already installed  OB82, OB86.

Is there is any problem in cable? how i can rectify this issue.

dchartier

[snip]
 
You can do this by right-clicking on the blocks forlder in Simatic Manager, create New, OB. Call it OB 82, and save and download.
The presence of that OB will allow the diagnostic buffer to gather more information on the cause off the problems and prevent the CPU from going to STOP mode (if that is the only type offault present).
then launch your PLC once more, the SF LED will still be lit but the PLC should remain in RUN mode. the diagnostic buffer should contain more precise information on the problem now.
[snip] 

Hope this helps,
Daniel Chartier

 

Hello,

As explained by Expert Daniel Chartier you should add OB86 (in your case since error is related to DP - I/O failure) in your PLC project & download it in PLC CPU. Next time when error trigers, SF will lit. You should collect information from diagnostic buffer which will help you to analyse the problem. 

So add OB86 & download it in your PLC CPU & collect diagnostic buffer information when this problem triggers. You can save diagnostic buffer file in text format & attach here so that forum member could help you.

Problem could be either with cable or connector terminal or with profibus module of slave unit. You need to analyse problem with help of diagnostic buffer information.

HTH.