Siemens Sinumerik 840D sl Diagnostic Manual page 427

Hide thumbs Also See for Sinumerik 840D sl:
Table of Contents

Advertisement

03/2009
%4 =
DBW220)
%4 =
DBW246)
%4 =
DBW244)
%4 = 1.... 64: Error in system variable $A_INSE[1...64]
%4 =
65...128: Error in system variable $A_OUTSE[1...64]
%4 = 129...192: Error in system variable $A_INSI[1...64]
%4 = 193...256: Error in system variable $A_OUTSI[1...64]
%4 = 257...320: Error in system variable $A_MARKERSI[1...64]
In order to parameterize alarm 27090, file ALSI_xx.com must be incorporated in the data management
and declared in HMI via MBDDE.INI in the section[IndexTextFiles] ALSI=f:\dh\mb.dir\alsi_. The
machine manufacturer can redefine this file, in order to incorporate additional text passages in the
alarm that make sense for their system. If the file is redefined, the newly created file has to be declared
in the system via MBDDE.INI.
The display of alarm 27090 can be modified via MD $MN_SAFE_ALARM_SUPPRESS_LEVEL: MD
$MN_SAFE_ALARM_SUPPRESS_LEVEL = 2 : Alarm 27090 will now only displayed for the first data
difference found.
Reaction:
Alarm display.
Trigger a STOP D/E (settable via MD $MN_SPL_STOP_MODE) on all axes with safety functionality,
as soon as the SPL start-up phase (MD $MN_PREVENT_SYNACT_LOCK[0,1] unequal to 0) is com-
pleted.
Remedy:
Analyze the value displayed and evaluate DB18: SPL_DELTA on the PLC side.
Find the difference between the monitoring channels. Possible causes:
- Incorrect wiring
- Incorrect SPL
- Incorrect assignment of the axial SGEs to internal interface $A_OUTSI
- Incorrect assignment of the axial SGAs to internal interface $A_INSI
- Incorrect assignment of the SPL SGEs to external interface $A_INSE
- Incorrect assignment of the SPL SGAs to external interface $A_OUTSE
- Different SPL startup status set in NCK and PLC
- Different SPL stop reaction set in NCK and PLC
Program Con-
Clear alarm with the RESET key. Restart part program
tinuation:
27091
Error in data cross check NCK-PLC, stop of %1
Parameters:
%1 = Extension indicating the monitoring channel that triggered the stop
Definitions:
The monitoring channel specified in %1 (NCK or PLC) has triggered a stop D or E (depending on the
parameterization in MD $MN_SAFE_SPL_STOP_MODE). The alarm 27090 provides further informa-
tion about the cause for the stop D/E.
Reaction:
Alarm display.
Trigger a STOP D/E (settable via MD $MN_SPL_STOP_MODE) on all axes with safety functionality,
as soon as the SPL start-up phase (MD $MN_PREVENT_SYNACT_LOCK[0,1] unequal to 0) is com-
pleted.
Remedy:
Evaluate the alarm parameters of alarm 27090 and amend the SPL, or check the I/O modules/wiring
or the internal SPL interfaces to the safety monitoring channels in the NCK and drive
SIMODRIVE611D.
Program Con-
Clear alarm with the RESET key. Restart part program
tinuation:
27092
Communication broken off during NCK PLC data cross check, error
detected by %1
Parameters:
%1 = Extension indicating the monitoring channel that detected the error
Definitions:
The delay time (1s) for communication monitoring was exceeded in the monitoring channel specified
in %1 (NCK or PLC). The other monitoring channel did not send a new data packet within this time.
Reaction:
Alarm display.
A timer of 5 secs is started, after the expiry of which
- the external NCK SPL outputs are deleted
- the PLC changes to stop.
Remedy:
Check the system components (the PLC must have the correct version of FB15 and DB18).
© Siemens AG, 2009. All Rights Reserved
SINUMERIK 840D sl, 840Di sl, SINAMICS, Diagnostics Manual (DAsl), 03/2009
0: Error FSENDDP error reaction ($A_FSDP_ERR_REAC[n] - DB18 DBW190, DBW210,
0: Error FRECVDP error reaction ($A_FRDP_ERR_REAC[n] - DB18 DBW222, DBW234,
0: Error FRECVDP replacement values ($A_FRDP_SUBS[n] - DB18 DBW220, DBW232,
Overview of Alarms
NCK alarms
2-427

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents