Error profibus dp step7 S7-400

Hello;

In the same view you show us, there are 3 nodes showing a fault (a red slash symbol).

Double-clicking on each one will open the diagnostic buffer for each, and if you SAVE AS.. each one we can have access to the informatopn provided, in a .txt form.

Or you could at least take a screenshot of the diagnostic buffer for the faulty ET 200L units so we know what they are complaining about.

Hope this helps,

Daniel chartier

Hello;

Siemens error message hints are very explicit. In this case, the message states "Parameters must be assigned to the DP slave again.

Look at the icon for slave 120: notice there is no model number next to the node address, unlike all the other slaves? And look at the I/O description for the I and Q addresses, they are preceded with a ???

These have to be be reassigned, probably by re-introducing an ET 200L slave from the Porfibus catalog, assing the same node address, and the same I/O addresses you had originally. Then compile and download the HWConfig to the PLC.

Hope this helps,

Daniel Chartier

Hello;

One issue I see in the configuration of the Profibus parameters for slave no 98 (IM 155-6) is that the Failsafe parameter has been selected, but the CPU 414-2DP that you have is not an F-CPU. That might be a descrepancy that the CPU reacts to...

If that does not help, we nee to examine what the CPU is complaining about on your system.

That means we need to see the contents of the CPU's diagnostic buffer. Double-clicking on the CPU in your first screenshot will open the diagnostic buffer, and you will see a button marked Save As.. at the bottom of the diagnostic buffer screen. This button will generate a text file containing all the logged messages in the buffer. Posting it here qill give us a lot more diagnostic information, and we might be able to come back with some ideas on what does not work on your system.

Hope this helps,

Daniel Chartier

Hello,

The Fail Safe checkbox in general DP parameters was already enabled by default and the software did not allow me to change this option, maybe that is exactly the problem, it really seems that it is the slave 98 IM-155 that is causing some kind of conflict , now I will have to wait some time until I can work on it again, I only had 3 days with the machine to try to make this change and I had to give it back to the operators to continue with their production! I'll reschedule a new date to continue working on it, so I can send CPU buffer 414 for your review, I can't give up now that I've gotten this close! Thank you very much for your help and attention with this topic!

Hello,

if I could give some recommendations, tips. For first, it is better attach file of diag buffer (txt file that you've download from PLC to PC), it is better to read it at that source than here with more lines at Topic. Next my observations but same as Daniel already mentioned. Some Slaves indicating still problems, you can see them on Online status. Your buffer saya address 112 with lenth 8, you can easy click on each Slave and see what addresses it has set for data exchange and maybe easy then see where address 112 is existed, in range of defined area of data. Then you can be sure what device does problems. Other part is check your code where maybe that data are proceeded, in code can be set write or other manipulation, who knows. try investigate further. To me, very important and careful check of PB DP cables and connectors, especially shield connected to connector plate is very important. termination, parts of each network between each Slaves. One next tip, it is common that some Slave devices have own DIP switches to configure address and Speed, here is important to check this if all is as your PLC HW cfg (addresses of that Slaves as you see there) are correct with reality, speed also.