S7-1500F Diagnostic buffer error ID 16# 06:4040 e 4000

Hi guys,

I need your help for diagnostic buffer error ID 16# 06:4040 Error: Error on partner  - No neighbor could be detected and 16# 06:4000 Error: Data transfer not possible  - Connection error - connection interrupted.

Hardware specific: S7-1511F (6ES7 511-1FK02-0AB0), Firmware v2.6.1, Tia V15.1 project version.

The system consist of 3 encoders connected to the MRP ring redundacy via scalance swicth managed XB216 on port 1 and 2, the network works fine but sometimes these alarms on buffer appears, and i'm not be able to understand if is a device problem, wiring problem or wrong configuration. I setup the switch parameters and the hardware configuration for the MRP ring in according to the user manual "109739614_MRP_DOKU_V10" from siemens. 

the wirings have been verified and are ok.

Any tips to help me? 

Regards

For testing purposes, are you able to configure the system as a simple linear topology (break the ring at some logical point) and operate in that manner for at least 3 times as long as your longest period where none of the topic diag buffer errors happen?

For example, if you are getting these diag buffer errors once an hour, run for 3 hours - or until you get a diag buffer error related to partner's going missing, or something like that.

If your profinet receives no errors in a linear topology, then dig into profinet documentation on how to configure MRP ring redundancy.

In the meantime, be sure and submit your portal project and diagnostics buffer (export it to a file) and submit to Siemens Support via "Support Request" -> Create new request.

This way you can get an official answer while investigating the profinet cabling and verifying device by device all the hardware configuration profinet settings.

Alex_Bass

Hi guys,

I need your help for diagnostic buffer error ID 16# 06:4040 Error: Error on partner  - No neighbor could be detected and 16# 06:4000 Error: Data transfer not possible  - Connection error - connection interrupted.

Hardware specific: S7-1511F (6ES7 511-1FK02-0AB0), Firmware v2.6.1, Tia V15.1 project version.

The system consist of 3 encoders connected to the MRP ring redundacy via scalance swicth managed XB216 on port 1 and 2, the network works fine but sometimes these alarms on buffer appears, and i'm not be able to understand if is a device problem, wiring problem or wrong configuration. I setup the switch parameters and the hardware configuration for the MRP ring in according to the user manual "109739614_MRP_DOKU_V10" from siemens. 

the wirings have been verified and are ok.

Any tips to help me? 

Regards

Hi guys,

I tried to do  the suggested tests: without topology, the last node in the series is continuously lost, same thing with linear topology (without MRP ring). There is probably some problem with the wiring. I will try to close the ring with temporary cable to test if allarms still appears.

Best regards and thanks for support

When building (and commissioning) a complex network topology, it is best to get it working as a very simple network (without a defined topology).  Then, you can use the profinet online resources to see what port is connected to what device, and then make changes against your ideal (and soon to be defined) topology.

Once the simple network layout matches what your desired "topology" needs to be, then go to the topology tab and draw in the links to enforce those specific connections, device-to-device, port-to-port.

Once the topology is downloaded (while offline) and generates all green check-boxes and all devices are online, then worry about redundancy / MRP ring types of things.

It makes commissioning less stressful, making it more methodical and easy for electricians / technicians to help along the way.

Alex_Bass

Hi guys,

I tried to do  the suggested tests: without topology, the last node in the series is continuously lost, same thing with linear topology (without MRP ring). There is probably some problem with the wiring. I will try to close the ring with temporary cable to test if allarms still appears.

Best regards and thanks for support