When removing a DI8x24VDC ST from CPU 1512SP it dosen't go into STOP mode

Hi

One more question :)

I have a project without OB83 (pull or plug of modules). But when I remove a DI8x24VDC ST from my CPU 1512SP F-1 PN, it dosen't go into STOP mode. In the HELP-MENU it says that it dosen't go into STOP mode if it is a CPU 1512SP-1 PN, but is that also the failsafe CPU?

Is this not wrong or have I misunderstood the function?

Best regards

Azkaban

------------------------------------------------------------------------------------------
Split from Error handling OBs.

Hi Towome

The diagnostic buffer indeed says that: "Hardware component removed or missing". But it does not lead to a CPU stop.

But as I understand it, the PLC should go into STOP mode even if OB83 is present?

Best regards

Azkaban

Towome

Hi,

when a configured and activated module is pulled from the distributed I / O, the OB83 is triggered - your module is located centrally on the rack of the CPU and, according to the manual, pulling and plugging of a module always leads to the CPU stop.

So please check diagnostic buffer.

Regards,

Towome

Hi

I just tried to use the OB86 (rack or station failure). The PLC won't go to STOP mode if there is no OB86 or if there is a OB86, even if I tried to remove distributed I/O system by removing the PROFINET cable and the CPUs diagnostic buffer said that there was a fault. When I have the OB86, it is getting called, so I must be doing it the right way.

Best regards

Azkaban

Which interrupt OBs are present in your system?

What diagnostics are enabled for the module(s) in question, or disabled if you look at things the other way?

Local I/O being pulled would not be a rack or station failure (which I think was already stated).

Diagnostics error interrupt OB is where your system would call for both local and remote I/O, so if you want to cause a PLC stop and have that OB, detect module configured but non existent and force the PLC to stop (if that is what you want), but be sure and post a diagnostics entry from the program logic _before_ entering stop mode.

That way, you can see when and why the plc went into stop mode.

Azkaban

Hi

I just tried to use the OB86 (rack or station failure). The PLC won't go to STOP mode if there is no OB86 or if there is a OB86, even if I tried to remove distributed I/O system by removing the PROFINET cable and the CPUs diagnostic buffer said that there was a fault. When I have the OB86, it is getting called, so I must be doing it the right way.

Best regards

Azkaban

Hi huggy_d1

I am simply just trying to understand how OB83 (pull or plug of modules) and OB86 (rack or station failure) is working  I will try to answer your questions..

I have the diagnostics error interrupt OB present in my project. Where do i enable/disable diagnostics for the modules?

I don't have OB83 or OB86 in my project. But when I remove a input module from a ET200SP module that is connected to my CPU with a PROFINET cable (pull or plug error?) or simply just remove the PROFINET cable to the whole ET200SP module (rack or station error?), then the PLC don't go to STOP mode. So it is not because it is local I/Os.

Best regards

Azkaban

You stated in the first post you were trying to resolve a problem with detecting a local module getting pulled.

Later, you stated a remote module going offline was not providing a PLC stop.

Remove the OBs that handle these types of things and see what happens.

Check each local module for diagnostics options in the module properties.  There may be one attribute below the working pane named Diagnostics.

Azkaban

Hi huggy_d1

I am simply just trying to understand how OB83 (pull or plug of modules) and OB86 (rack or station failure) is working  I will try to answer your questions..

I have the diagnostics error interrupt OB present in my project. Where do i enable/disable diagnostics for the modules?

I don't have OB83 or OB86 in my project. But when I remove a input module from a ET200SP module that is connected to my CPU with a PROFINET cable (pull or plug error?) or simply just remove the PROFINET cable to the whole ET200SP module (rack or station error?), then the PLC don't go to STOP mode. So it is not because it is local I/Os.

Best regards

Azkaban

Hi huggy_d1

I first tried to pull a local module (without PLC stop) but you said that a locale module should not make a rack/station failure, so I switched over to try on a remote module instead. In properties the system diagnostic is active.

The only OBs I have in my project now are OB1 (Main), OB30 (Cyclic interrupt) and OB100 (startup). When I pull a input card from the remote module or remove the remote module by removing the PROFINET cable, the PLC gets an error in the diagnostic buffer, but I still dosen't go into STOP mode

huggy_d1

You stated in the first post you were trying to resolve a problem with detecting a local module getting pulled.

Later, you stated a remote module going offline was not providing a PLC stop.

Remove the OBs that handle these types of things and see what happens.

Check each local module for diagnostics options in the module properties.  There may be one attribute below the working pane named Diagnostics.

Azkaban

Hi huggy_d1

I am simply just trying to understand how OB83 (pull or plug of modules) and OB86 (rack or station failure) is working  I will try to answer your questions..

I have the diagnostics error interrupt OB present in my project. Where do i enable/disable diagnostics for the modules?

I don't have OB83 or OB86 in my project. But when I remove a input module from a ET200SP module that is connected to my CPU with a PROFINET cable (pull or plug error?) or simply just remove the PROFINET cable to the whole ET200SP module (rack or station error?), then the PLC don't go to STOP mode. So it is not because it is local I/Os.

Best regards

Azkaban

 

Check the profinet configuration for the remote I/O device around where you set the profinet IP address.  Look for the diagnostics checkbox for when the profinet connection is lost.  I believe it is not checked.  Toggle it, download the hardware configuration and try again.

Hi huggy_d1

Are you sure that is an option?

Beacuse I have looked everywhere and I can't seem to find it

Best regards

Azkaban

huggy_d1

Check the profinet configuration for the remote I/O device around where you set the profinet IP address.  Look for the diagnostics checkbox for when the profinet connection is lost.  I believe it is not checked.  Toggle it, download the hardware configuration and try again.