The parameter group P55x DCS safety monitor includes display and setting values that are specific to the DCS31B option. The factory setting is indicated by underline.
P550 status DCS safety monitor
Display value that cannot be changed.
The parameter P550 displays the current status of the DCS31B option. • RUN: Normal operation.
• STOP: The operation of the DCS31B option was stopped via the programming inter- face.
• ALARM: The DCS31B option has issued an alarm. • ERROR: The DCS31B option has issued an error.
You have the following options to read the corresponding error or alarm message from the fault memory of the DCS31B option:
• via the X87 service interface • with the DBG60B keypad
• with the MOVISAFE® CONFIG configuration software, if P555/P556 is set to "NO RESPONSE".
P551 binary inputs DCS DI1 ... DI8
Display value that cannot be changed.
The parameter P551 displays the current status of the binary inputs of the DCS31B op- tion in the order DI1 ... DI8.
P552 binary out- puts DCS DO0_P ... DO2_M
Display value that cannot be changed.
The parameter P552 displays the current status of the binary outputs of the DCS31B op- tion in the following order:
• DO0_P • DO0_M • DO1_P • DO1_M • DO2_P • DO2_M P553 DCS series number
Display value that cannot be changed.
The parameter P553 displays the series number of the DCS31B option. The series num- ber displayed must be identical with the series number on the nameplate of DCS31B, which is attached to the MOVIDRIVE® MDX61B. You have to enter the series number in the validation report (→ Sec. "Validation").
0
0
P554 CRC DCS Display value that cannot be changed.
The parameter CRC DCS displays the CRC (cyclic redundancy check) of the program stored on the DCS31B option. You have to enter the CRC in the validation report (→
Sec. "Validation").
P555 DCS error response / P556 DCS alarm response
Factory setting: IMM. STOP /FAULT
If the DCS31B option issues a fault (P555) or an alarm (P556), the inverter performs the set response.
The following responses can be programmed:
P557 DCS actual position source
Setting range: Motor encoder (X15) / ext. encoder (X14) / absolute encoder
If the option "Encoder inverter" is set as encoder 1 in the MOVISAFE® CONFIG config- uration software, the setting in P557 determines which encoder signal is evaluated by the DCS31B option.
Response Description
NO RESPONSE No fault is displayed and no fault response is triggered. The fault which is signaled is completely ignored.
DISPLAY FAULT The fault is displayed (in 7-segment display and SHELL), the fault output is set (if programmed). The unit has no other fault responses. The fault can be reset (termi- nal, RS485, fieldbus, auto-reset).
5
Switch-on sequence
5.3
Switch-on sequence
After each restart of the DCS31B option, the following operating states are performed and displayed at the front status LEDs in case of fault-free operation.
Status LED
60577AXX
• LED A/F: Alarm / fault • LED WD: Watchdog • LED B: System B • LED A: System A
Operat- ing state
LED display Mode Description
1 • LEDs "A" and "B" flash in sync (changes every 1.2 s)
• LED "WD" off • LED "A/F" off
STARTUP The processor systems are synchronized and the configuration/firmware data is checked. 2 SENDCONFIG Configuration/firmware data is distributed and
checked again. An internal check is performed for the configuration data.
3 • LEDs "A" and "B" flash in sync (changing every 0.8 s)
• LED "WD" off • LED "A/F" off
STARTUP BUS If applicable.
4 • LEDs "A" and "B" flash in sync (changing every 0.4 s)
• LED "WD" on • LED "A/F" off
RUN Watchdog is active, which means that all out- puts can be switched.
DCS31B
A/F WD B A
NOTE
In operating states 1, 2 and 3, the outputs are switched off automatically by the firm- ware. In the "RUN" mode (operating state "4"), the outputs are controlled by the imple- mented PLC program.
0
0
5.4
Validation report
To make sure that the implemented safety functions function correctly, the user must check and document the parameters and connections after startup and configuration. This is supported by the MOVISAFE® CONFIG configuration software.
You can call up the validation report directly from the programming interface under the menu item [File] / [Configuration report].
You can use the first page of the validation report to enter generation information on the system (type system, customer, supplier, setup operator, etc.). You can use the second page to enter more detailed information on the system / machine. This data is for infor- mation only, but the content and scope must be checked with the approval authorities / inspector.
The last page of the report contains an itemization on the safety check. You must make the following entries here:
• Serial number (identical to the serial number on the nameplate)
• Correspondence between the serial number read off and the serial number on the nameplate of the DCS31B option
• Identity of the subassembly
Here, the inspector of the safety subassembly confirms that the CRC displayed in the programming interface is identical to the one in the DCS31B option. This CRC sig- nature comprises a five-digit number that is displayed in the connection dialog box of the configuration tool in the diagnostic system information section. In this case, the DCS31B option must have an active connection.
Once all header data has been entered, you can generate the validation report by press- ing the "Save" button. The configuration tool creates a text file (.TXT) with the file name of the parameter/parameter dataset. The text file includes the following information: • The 3 pages of the header data listed above
• Encoder configuration
• Parameters of the monitoring functions
Monitoring functions not required are also listed. These functions must also be checked!
NOTES
• The correct program data and parameter data must be loaded to create the valida- tion report.
• All listed parameters and program instructions must be validated at the system / machine and confirmed by a signature in the validation report.
• The inspector must validate all the configured data again in a printout of the valida- tion report.
• All limit values set for the monitoring functions must be tested. • The printed out AWL code must be validated.
6
Procedure
6
Validation
6.1
Procedure
The concept for the DCS31B option is based on the following prerequisites:
Parameter and PLC data stored in the DCS31B option flash memory cannot change au- tomatically. Online tests and corresponding signatures make sure that this is the case by implementing basic measures on the subassembly. However, the configured param- eters cannot be evaluated by the subassembly. This affects parameters for the sensors, thresholds and limit values.
The user must confirm that the data in the test protocol matches the parameters in the subassembly. The user must validate and protocol the parameter values for the travel type, sensors and monitoring functions individually by performing a function test. In ad- dition, the user must validate and protocol the connection of each programmed PLC function by inspecting the code.
The MOVISAFE® CONFIG configuration software generate a suitable output form and stores it in a text file.
The program enters the following information in the text file: • Manufacturer: SEW-EURODRIVE GmbH & Co KG • Type: DCS31B
• Version of the hardware and activated functions You must enter the following data in the text file:
• Serial number (identical to the serial number on the nameplate)
• Correspondence between the serial number read off and the serial number on the nameplate of the unit.
The text file can then be printed out. Any other entries must be made manually: • Date the configuration dataset was created