cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Basic Functional Scheme for E-stop with Reset and EDM

Basic Functional Scheme for E-stop with Reset and EDM

bclapperton
New Contributor

I have written a basic functional Scheme for an Emergency Stop with (Manual) Reset and EDM in ctrlX Safety Engineering. I would like some confirmation that this is the correct/best way to write this functionality. Or is there a better way?

The scheme outputs a signal Estop_Status that would drive an external relay with a N/C forced guided contact connected to an EDM input. 

Function Description:

  • Estop_Status off after power on.
  • Estop_Status off when emergency stop is pressed. 
  • Estop_Status off when EDM mismatch is detected.
  • Estop_Status Does not come on when EDM mismatch is cleared
  • Rising/Falling sequence on Reset input requried to turn Estop_Status back on
  • Reset input clears any previous EDM error

Functional Scheme below. 

Note: I have used a ctrlX PLC and functional I/O to simulate the external relay and adjust the EDM time to simulate faults. 

bclapperton_0-1684218053371.png

 

4 REPLIES 4

BRamos
Established Member

Hi @bclapperton,

First I would like to tell you some limitations if you are using the current release SAFEX-C.1x Firmware 1.0.1.29-FPGA211 and ctrlX SAFETY Engineering 1.7.1.8239:

  • EDM block reset is not working, the only way to reset the EDM block is to set the Start/Reset element as "Use as Alarm Reset", but this will reset all your PLC logic (Bug #584752)
  • For the restart of the Restart block you can use a normal Confirm Button, you don't need to use a Start/Reset element (you can use it if you want of course)

Because of these limitations I would not recommend to use the logic you posted on the current release sorry 😅

 

Regarding the application itself, I have 2 things to say:

  • Instead of using the Restart block to control the emergency button you can do this, it has the same effect:

BRamos_0-1684227005255.png

BRamos_1-1684227040276.png

BRamos_2-1684227058625.png

  • Regarding the EDM, the function is to monitor loop feedback for contact multiplication following the cat 4 of EN 954 1, is this your use case?

BRamos_3-1684227271415.png

 

Best Regards,

BRamos

Hello @BRamos,

Thanks for the information on resetting estop using Start Type: Monitored

Yes I am using the EDM for monitoring according to cat 4 of EN 954 1. This is a very common use case. I am happy to reset all the PLC logic for now. After Estop or EDM error the system should go back to start conditions anyway. 

Is there any plan to have an error reset block with a logical input? At the moment it looks like the only way error reset is the Start/Reset block which must be a physical input. Sometimes there needs to be multiple fault reset buttons or fault reset via higher level control via fieldbus. 

BRamos
Established Member

Hi @bclapperton,

Happy I could help.

Regarding the EDM improvments, if you see the block properties:

BRamos_0-1684308708931.png

You will be able to separate certain blocks into different reset groups, that you can safely reset without having to restart the logic.

For this reset you will be able to use the Start/Reset Input Element as "Use as Block-Reset", but this is not implemented yet.

Regarding the reset fieldbus, there is the function block "Reset from Network":

BRamos_1-1684309161815.png

However, this block still has very limited operation on the current release:

  • It can only be used when SAFEX-C.1x is FSoE Slave or PROFISAFE Slave.
  • Only works as "Use as Alarm Reset" (Resets all logic).
  • Only works if it is connected to bit 0 of the F-Bus Input block.

 

Given our current timetable my recommendation is to build your project witout expecting these fixes soon.

Best Regards,

BRamos

AllAutomation
Community Moderator
Community Moderator

Hello @bclapperton ,

for EDM and Reset issues please follow the following Bug-IDs in our Extended Release Notes, that you will receive with every release: 501983, 584752, 642842 and 670720.

Since the question is answered for the moment, I close this with the relevant answers as "solution".

@BRamos : FYI

Best regards

Your ctrlX SAFETY team

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist