7.8.3.2 Start-up
At startup, the safety FW checks the safety parameters for validity, if the parameters are not valid or the safe address
switches S11/S12 are set to FFh at power up, it is changed into the state “Configuration needed”. If a valid configuration
is found (CRC and version are correct) the normal operation is called.
At startup, the STO is active and a startup lock event is active, in this state an IO Failure will be displayed. To leave this
startup lock state an acknowledge over the safe fieldbus or safe IO is required.
In the delivery state, or when the complete drive firmware is reinstalled or defaulted, the safety parameters are valid but
no safety function is active shown by state “Operation No Safety Active”.
7.8.3.3 Configuration needed
This state is entered if the no valid safety configuration is found or if the safe address switches S11/S12 are set to FFh at
start-up.
In case of the safe address switches S11/S12 are set to FFh, a valid flash card with a configuration must be inserted. If
this is found the process to load the configuration from the flash card is started. This process is described in detail in
chapter 7.7.5 - Load and validate all Parameters from the FC .
In case of the safe address switches are not set to FFh or no valid flash card is found, the firmware keeps in this state,
the communication to the drive is active and a configuration is awaited. When the configuration is loaded, a restart is
necessary.
7.8.3.4 Load FS Parameter From Flashcard
This state is called from configuration needed when the safe address switches S11/S12 are set to FFh at power up. The
configuration is automatically loaded from the flash card. For details see 7.7.5 - Load and validate all Parameters from
the FC .
When a valid configuration is loaded, the normal operation is started.
7.8.3.5 Normal Operation
After start-up is finished and a valid safety configuration is loaded, the normal operation becomes active. In this state the
safety functions are active. Depending on the configuration the brake and position signals are monitored. The safety
functions will become active when requested.
7.8.3.6 IO Failure
The state “IO Failure is reached after startup “startup lock” or when an error with IO-wiring is detected. IO failures are
active, as long as the error source is present. The IO failures can be acknowledged.
All possible failures are listed in chapter 7.8.3.10 - Failure classification and reaction.
7.8.3.7 Internal Failure
The state “Internal Failure” is reached if a HW failure is detected. If this occurs the HW has normally to be replaced. In
this state the communication is still active and the failure is displayed with the LinMot-Talk. The internal failures can only
be acknowledged by a reboot (reset, or power cycle).
All possible failures are listed in chapter 7.8.3.10 - Failure classification and reaction.
2S Drive Systems / 0185-1174_E_1V1_SM_C1251-2S / NTI AG
0185-1174_E_1V1_SM_C1251-2S / 2021-11-26 16:43 (Rev. 12500)
Page 84 of 150
