Table 92: Hidden Interface of FB instances towards drives (Vendor specific).Name DescriptionSF_SafeStop1_1 Connection to Drive 1Table 93: Local variableName Data type DescriptionS_EStopOut BOOL Emergency stop requestInputDevice1_active BOOL Status of the relevant input device as provided by the systemInputDevice2_active BOOL Status of the relevant input device as provided by the system7.2.4 Program exampleActivateS_S topInR eadyS_Stopp edSF_SafeStop 1AxisIDM onitoringTim eErrorD iagC odeR esetSF_SafeStop1_1ActivateS_EStopInR eadyS_EStopOutSF_Emerge ncyStopSF_Eme rgen cyStop_1S_StartR esetS_AutoR esetErrorD iagC odeR esetT#10m sS 0_R esetFALSEFALSES1 _S_ EStopIn_ 1ActivateS _C han nelAR eadyS_ EquivalentOutSF_EquivalentSF_Equ ivalen t_1S _C han nelBS _D iscrepan cyT im eErrorD iagC odeS1 _S_ EStopIn_ 2AxisID_1T #100 m sS 3_D rive_R esetS _StoppedError _EStop1Error _SafeStop 1D iag _SafeStop1D iag_E Stop 1Error _Equiv 1D iag _Equiv1T w o channe l line m onitoring:T his F B produ ces a single SAFEBOOLsignal out of t he t w o sepa rated signals fromthe em ergency stop channe ls. TheD isc repancy Tim e is set constantly t o10 m sEm ergen cy Stop w ith restart inhibit:This F B handles t he em ergency stopcond ition . After t he em ergency stop requestas w ell as after pow er up t he safety outputis only released aft er m anu al restart. T hisbeha vior is enabled by setting t heS_ StartR eset and S_Au toR eset inputs t oFALSE .Safe Stop 1 R equest H andling:This FB handles t he Safe Stop 1 R equestfor AxisID_1 and m onitors t hat the axisfollow s t he request w ithin the predefinedm onitoring tim e of 100 m s. Any errorcondition w ithin t he axis has to beacknow ledg ed by a m anual drive resetsignal .InputD evice1_activeActivateS_ ESPE_ InR eadyS_ESPE _OutSF_ESP ESF_ESPE _1S_ StartR esetS_ AutoR esetErrorD iagC odeR esetS2_S _ESPE _InFALSEFALSES0_ R esetInputD evice2_active ANDANDS_E StopOutS_EStopOutESPE : T his F B han dles the light curtaininterface. After intrusion in t he protectedfield, as w ell as aft er pow er up the safetyoutput is only released after m anual restart.This beha vior is enab led by setting t heS_StartR eset and S_AutoR eset inputs toFALSE.Error_ESPE 1D iag_ESPE 1Fig. 135: Program example – Emergency stop with safe stop & equivalent monitoring7.2.5 Additional notesThis example uses different reset signals to acknowledge the emergency stop situation and to acknowledgethe monitoring violation situation of the drive. If the safety requirement specification of the application allowsthe acknowledgement of both situations with the same signalling device, the identical signal from the func-tional application may be used to reset the FB SF_EmergencyStop_1 as well as to reset the FB SF_Safe-Stop1_1.Safety application examplesExample 1: Diagnostics concept > Additional notes30.03.2017AC500-S428