Hi to everyone, 

Today I add CPU315-2 dp as a dp slave in CPU416-3 DP. but when i download hardware on cpu it goes to fault. EXTF LED light on permanently and BUS2F blinking. I attached here my diagnostic buffer details

Hello jabbi;

If byou read your diagnostic messages (for the S7-400 CPU) you will see repeated calls for OB 86 and OB 85.

OB 86 (the distributed I/O node failure OB) is called by the CPU's OS when it detects the loss (or return) of a Profibus or Profinet node. That explains the BUSF LED being active.

OB 85 (the programming error OB) is called when the CPU program attempts to access an I/O address that does not respond (as it probably is found on the missing node).

All of the messages I have seen seem to be linked to the loss of node 30 on the bus; is that the address of your slave CPU?

You could connect to this slave CPU and open its own diagnostic buffer, and see if there is any indication of what could cause it to lose contact with the master CPU.

At the minimum, check the Profibus connectors, termination switch and cable setup to see if any problems can come from that physical connection.

Hope this helps,

Daniel Chartier

 Dear dchartier, 

When i online my hardware no cross in hardware cpu315-2 which i add in dp slave master side. And when i check module information of cpu315-2 and monitoring its signal it receives some signal but 1st 8 bytes no respondes and analog signal not comes proper. But digital signal comes 

dchartier

Hello jabbi;

If byou read your diagnostic messages (for the S7-400 CPU) you will see repeated calls for OB 86 and OB 85.

OB 86 (the distributed I/O node failure OB) is called by the CPU's OS when it detects the loss (or return) of a Profibus or Profinet node. That explains the BUSF LED being active.

OB 85 (the programming error OB) is called when the CPU program attempts to access an I/O address that does not respond (as it probably is found on the missing node).

All of the messages I have seen seem to be linked to the loss of node 30 on the bus; is that the address of your slave CPU?

You could connect to this slave CPU and open its own diagnostic buffer, and see if there is any indication of what could cause it to lose contact with the master CPU.

At the minimum, check the Profibus connectors, termination switch and cable setup to see if any problems can come from that physical connection.

Hope this helps,

Daniel Chartier

Hello jabbi;

Thanks for the reply, however this does not answer the first imposrtant query: is your slave CPU setup setup as node #30 ion the network?

If yes, please upload the diagnostic buffer from that CPU and show it here.

If not, what is the slave at address #30.

Hope this helps,

Daniel Chartier

 Hello dchartier, 

I solved my problem. Problem in Slve side. Addressing problem. Actually we send 40 bytes of data and actually it is42 bytes. 

dchartier

Hello jabbi;

Thanks for the reply, however this does not answer the first imposrtant query: is your slave CPU setup setup as node #30 ion the network?

If yes, please upload the diagnostic buffer from that CPU and show it here.

If not, what is the slave at address #30.

Hope this helps,

Daniel Chartier