SCP 111-2
S-DIAS SAFETY CPU MODULE
Page 38
08.09.2022
Quit
Communication
Errors
State
A communication error (Error server = 2) is canceled by writing to this server.
If the safety.dlm is used, the dlm can also cancel other errors starting with
version 6(Error server = 1). The Safety dlm be acquired from SIGMATEK
Support. For the Salamander operating system, no dlm is required here.
Canceling can activate Safety outputs and thereby lead to
unexpected responses from machine elements.
If this function is provided through the visualization, a corresponding warning
should be displayed.
The server shows the status of the cancellation:
2
Busy canceling error
1
Busy canceling communication error
0
Ready
-1
Error creating Safety statement via dlm
-2
Deactivation of user input request failed.
-3
Selection of module via Safety number failed
-4
Error during connection set-up with module via dlm (the
SafetyDesigner cannot be online while canceling errors!)
-5
Error canceling in the module failed
-6
Remove the Safety statement via dlm failed
Firmware
Version
State
In this server, the Firmware version of the hardware used is displayed in xx.yy
format. Whereby x represents the major version and y the minor version.
For example, 16#0100 means v1.0
Safety Number
State
Shows the unique safety number of the module
Safety Retry
Counter
State
This server shows the actual number of retries from the Safety bus.
Designer
Project Config
CRC
State
Shows the CRC of the SafetyDesigner project configuration.
This can be compared with the CRC displayed in the SafetyDesigner when
printing the project (or in the print preview).
Designer
Project Name
State
Name of the Safety Designer project
Designer
Project
Revision
State
Revision number of the Safety Designer project
Validation
Button State
State
Shows the status of the validation button
0
Validation button currently not in use
1
The desired command can now be selected by pressing the
button
2
The command is executed
3
Module error
Fast Unsafe
Inputs
Output
Bit field with 32 fast non-Safe inputs. These inputs are configured in the Safety
Designer. More information can be found in the Safety Designer
documentation. The hardware class SCPFastUnsafeInput can be connected
so that the bit field can be broken down into individual servers.
