CSCP 012
C-DIAS SAFETY CPU
Page 26
05.10.2018
Handling the micro SD Card
An SD card can only be written on with the Safety Designer. A detailed description can be
found in the LASAL SafetyDesigner configuration tools documentation.
A Safety project, which was programmed with the SafetyDesigner, can be stored on an SD
card. The stored Safety project can then be loaded into an additional C-DIAS Safety CPU
CSCP 012, providing that the module's Flash memory is empty (cleared).
If the configuration on the SD card is different from that on the Safety CPU Flash, the sys-
tem switches to the error status (error message 87).
The SD card cannot be inserted into the Safety CPU during normal operation (Operational
or temporary operational mode). If the SD card is inserted during normal operation, the
Safety CPU switches to the error status (error message 88). However, an SD card can be
removed during normal operation.
Configuring a Safety CPU with the SD card
The configuration is loaded from an SD card a follows:
•
Delete the configuration of the Safety CPU to be programmed
To load the configuration from the SD card, the configuration in the Safety CPU
must first be deleted. This can be done with either the SafetyDesigner or with
help from the CLR_CFG command using validation button on the Safety CPU.
Once the configuration in the Safety CPU is deleted, the Safety CPU can no
longer return to the operational or temporary operational mode. The Safety
CPU remains in the service mode
•
Insert the SD card and deactivate the system
In the next step, an SD card with the valid configuration must be inserted in the
Safety CPU and the system shut down.
•
Restart the system with the SD card
When the system is restarted, the configuration is loaded from the SD card into
the Flash of the Safety CPU. This is only possible it a valid configuration is
stored on the SD card. If the SD card has an incorrect format (error message
86) or the Safety CPU's Flash has not been cleared (error message 87), the
Safety CPU goes into the error status. If the configuration does not match the
available real modules, the distribution process of the configuration triggers an
error (error message 9) and the Safety CPU also goes into safe mode.
