Subject to reasonable modifications due to technical advances.
© Fuchs, Printed in Germany
45
Fuchs Group · Tel.: Germany (6 21) 7 76-0 · USA (3 30) 4 25 35 55 · Singapore 7 79 90 91
Internet http://www.pepperl-fuchs.com
Iss
u
e d
a
te
: 21
.1
0.2
011
AS-Interface
Function and startup of the Safety Monitor
•
The chip card is already inserted while the configuration is being written into
the device using
ASIMON 3 G2
software and before validating the code
sequences.
If the AS-i Safety Monitor needs to be replaced, the stored configuration can be
transferred by simply plugging the chip card from the old device into the new one.
8.4
Safety-relevant documentation of the application
Proceed as follows:
•
Create the configuration of the AS-i Safety Monitor for your application.
•
Validate the configuration (done by the safety supervisor).
•
Print out the final configuration protocol and optionally the configuration over-
view (see Section "Configuration documentation" in the software manual).
•
Sign the final configuration protocol (done by the safety supervisor).
•
Take the protocol for the safety-relevant documentation for your application
(machine documentation) and keep it in a safe place.
8.5
Diagnostic data
Attention!
Safety advisory:
Power must always be turned off when removing or inserting the chip card!
Ensure that the chip card contains the configuration intended for and released for
the application!
This can be done by comparing the release codes on the display (sectionMONI-
TOR CONFIG):
•
The safety representative who generated and validated the release code
stores the release code for the master configuration and approves use of the
configuration for specific equipment.
•
The person performing the startup reads out the release code on the display
before starting the equipment and compares it with the release code stored
and approved for the equipment.
After the chip card has been used to load the configuration into the device, the
safety functions of the device must be checked in the equipment.
Checking of the release code and testing the system must be documented in wri-
ting and is part of the system documentation.
Information!
The detailed description of the safety-relevant documentation of the configuration for
your application can be found in the separate software manual.
Information!
A detailed description of the setting for diagnostics mode is described in the section
“Setting diagnostics type” in the separate manual "AS-i 3.0 Command Interface".
