Maintenance

1. Defective slave

   In case of a defective slave you take an identical substitute slave. The safety monitor accepts this as a substitute and internally adjusts to the new code table. The safety protocol must be updated.

2. Defective safety monitor

   In case of a defective safety monitor the configuration data of the system is stored in the monitor and can be directly transmitted to the new monitor. In addition a safety check must be carried out, i.e. all safe components must be actuated and their functioning checked.

3. Adding slaves

   You can easy add a safe slave to an existing network. The monitor accepts additive safe slaves. The configuration must be updated.

4. Removing slaves

   You can not remove safe slaves from an existing network without a new configuration. To prevent manipulation this is not possible. If a safe slave is removed nevertheless, the safety monitor switches off and does not switch on again. A new configuration must be read into the monitor before.

5. Extended specification

   It is possible to run Safety at Work also under Version 2.1. All components of Safety at Work can of course be run under the extended AS-Interface specification Version 2.1. Safe slaves are, however, always single slaves, i.e. they need a complete AS-Interface address. Splitting into A and B addresses is not possible here. The mixed operation of A/B slaves and safe slaves in one network is possible at any time.