Hello,

which system fault occurs exactly?
Have you the diagnostic buffer where the fault is logged?

Have you check that the wireless components you use support thr profinet IO RT profile and technologies?

Regards

Christoph

ChristophD

Hello,

 

which system fault occurs exactly?
Have you the diagnostic buffer where the fault is logged?

Have you check that the wireless components you use support thr profinet IO RT profile and technologies?

Regards

Christoph

 Faulty module (diagnostic interrupt detected)

Error LED (SF)

those are the faults. the plc also requested OB86 so i created one there.. but still, the fault stays there.

about the component for wireless communication, i use ubiquiti nano beam M5. i'm not quite sure if it really support profinet.

Hello,

First, because you speak about a router, remember that Profinet IO is not routable, which means that the controller (CPU) and the IO device (ET200M) must remain in the same LAN (eventually with a wireless part of it as WLAN). CPU and devices must remain on the same side of the router, in the same IP range.

WLAN is slower than LAN, and the default update cycle (2 msec) is impossible to be achieved.
So, you have to increase the cycle time (see screenschot). Can be done for each ET200M individually.
The more ET200M, the slower the update must be.

Another issue is that standard WLAN might not really support prioritization of traffic that requires it.
And that also roaming can be a problem because a missing rapid roaming features.
Siemens has specific features in its Scalance W to support IO devices on a wireless network.
See chapter 4.6 of this manual