In the event of simultaneous use of network variables and safety network variables: →Note:
Projects with network variables (→ S. 104)
On first log-in to the fail-safe controller the programmer is asked to enter an instance
identification. The instance identification is the serial number of the device without the leading
zeros.
Example:
Serial number: 000000569158
Instance identification: 569158
To determine the serial number of the device:
→ Label underneath the Fieldbus interface (X6/X7) or
→ GUI/web interface:
► >
To transfer the safe application of the CODESYS project to AC4S:
Requirements:
> Communication path of the fail-safe PLC is correctly set (→Configure programming interface
(→ S. 20)).
1 Load safe application to AC4S
► In the safety extension area of the device tree:
Mark [SafetyApp] and activate with [Projekt] > [Aktive Applikation setzen].
► Select [Online] > [Login].
> CODESYS changes to the online mode.
> CODESYS compiles the safe application and transfers it to the AC4S.
► Observe the warnings and notes.
2 Start safe application
► Start [SafetyApp].
> [SafetyApp] is in the RUN state.
3 Optional: Teach code sequences
► Teach code sequences of the safe AS-i input slaves (→Process safety time for the AC4S (→ S. 93)).
4 Optional: Create safe boot application
► Pin safe application (→ CODESYS online help).
► Select [Online] > [Create boot application].
> CODESYS stores the safe application non-volatilely on AC4S.
When the safe boot application has been created on the AC4S, the fail-safe PLC remains in
the "Debug operation" operating status.
► Note remarks about changing the operating states (→Change between the states
(→ S. 111))
To Next Page
Loading...
