When I use Moxa switch (IKS-G6524A-20GSFP-4GTXSFP, this switch not support H-sync) to connect MRP with S71513R, PLC red light ON and diagnostic with some errer: [Event ID: 16# 02:4E46 Error: Redundancy failure; Event ID: 16# 06:4040 Error: Error on partner  - No neighbor could be detected ; Event ID: 16# 02:4E10 CPU maintenance demanded: R-CPU pairing/redundancy connection failure, …] Does anyone know the reason and help me?

Hello;

To start on an informative note, here is a link to the S7-1513 Pn manual, showing the basic configuration of the redundant CPU system.

Your error message seems to say that there is no valid pendant connections with your CPU.

Does your setup resemble the screenshot in the attachment below?

https://support.industry.siemens.com/cs/ca/en/view/109972215/169547584267?dl=en

Can you give us a sketch of the way you are trying to connect your Moxa module to the CPUs?

Hope thus helps,

Daniel Chartier

When you contacted the manufacturer of the device preventing redundancy from succeeding (MOXA), what did their support group state was the reason their layer 2 switch is failing to perform as your redunant configuration requires?

Perhaps there are some configuration options within the swtich management system that allow or prevent the redundant PLC from being recognized - perhaps the default settings do not support your redundant needs, but are configurable such that they will.

I recommend starting with MOXA to at least verify your switch's internal management settings are correct for your environment and project needs.

Once that is verified correct, then you can post screenshots of the Portal project's network topology showing the MRP, 2 PLCs, and screenshots showing how the redundancy is configured on each PLC.

But, without knowing the MOXA is configured for success, it's tough going down the support site of things for the portal project.

That said, have you downloaded at least 1 Siemens sample redundant application with S7-1513R's showing how things should work?

I wonder if the PLCs are directly connected to one another via a PN daisy-chain topology (ring), or everything home-runs back to a central network switch (star), or a mixture of both and asking for failure here.

U_d2e5765f-653b-4436-9ce3-c3e02f2b8537

When I use Moxa switch (IKS-G6524A-20GSFP-4GTXSFP, this switch not support H-sync) to connect MRP with S71513R, PLC red light ON and diagnostic with some errer: [Event ID: 16# 02:4E46 Error: Redundancy failure; Event ID: 16# 06:4040 Error: Error on partner  - No neighbor could be detected ; Event ID: 16# 02:4E10 CPU maintenance demanded: R-CPU pairing/redundancy connection failure, …] Does anyone know the reason and help me?

Thank you for your interest, I send the hardware configuration:

I have tried many ways but still not successful!

What I find strange is the 2nd image shows in diag buffer entry #1 (Which I have to ASSUME is a green checkbox - since it is not visible in the screenshot) is an OUTGOING Event.

FYI, Outgoing events are added when an incoming event (red checkbox) has been cleared up and things are back to normal.

In other words, the diag entry says Redundancy has been established in that #1 diag buffer entry.

Diag entry #2 states CPU (ID=1) has entered into redundant mode.

Diag entry #3 is appears to state CPU (ID=2) has entered into redundant mode.

Diag entry #4 is also an OUTGOING event, so whatever the description states, it means that is no longer the case and it is no longer a problem.

What exactly are you concerned about?

For every device in the portal project tree, there is an option for "Online & diagnostics".  I recommend using that for every device without a green checkbox.  Investigate what each device is reporting is the problem and attempt to correct it, or if it is supposed to always be that way, learn to ignore it (this "supposed to always be that way" is virtually never the case in my experience).

Once you know exactly what every device errors exist, look for a single common solution that would fix them all.

It may be as simple as updating the PLC to the latest available firmware (without changing _anything_ in the Portal project) because updated firmware often fixes bugs.

AutoGen_3080975

Thank you for your interest, I send the hardware configuration:

I have tried many ways but still not successful!

With this configuration, it still works fine. However, the PLC diagnostic with error, is it possible to turn off diagnostic mode?