|
|
NC alarms
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26288
[Channel %1: ] Block %2: Maximum number of %3 protection area elements has been
exceeded by %4.
Parameters:
%1 = Channel number
%2 = Block number
%3 = Maximum permissible number of protection area elements
%4 = Additional number
Explanation:
The maximum permissible number of protection area elements has been exceeded.
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
The permissible number of protection area elements is determined by option data OD19830 $ON_COLLISION_MASK.
Retrofit the corresponding option.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26289
[Channel %1: ] Block %2: The maximum number %3 of 3D collision pairs has been exceeded
by %4.
Parameters:
%1 = Channel number
%2 = Block number
%3 = Maximum permissible number of 3D collision pairs
%4 = Additional number
Explanation:
The maximum permissible number of 3D collision pairs has been exceeded.
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
The permissible number of 3D collision pairs is determined by option data OD19830 $ON_COLLISION_MASK.
Install the corresponding option.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26290
[Channel %1: ] Block %2: CAD file $NP_FILENAME[%5] = %3: Maximum number of %6
protection area facets has been exceeded.
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = File name
%4 = Index of the protection area element | free protection area facets
Explanation:
The maximum permissible number of protection area facets has been exceeded.
Note:
Parameter 4 contains the descriptions of parameters 5 and 6 separated by the character "|".
- 5 = Index of the protection area element
- 6 = Free protection area facets
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Increase the permitted number of protection area facets (MD18895 $MN_MM_MAXNUM_3D_FACETS) or reduce the
number of defined facets in the CAD files.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
Alarms
492
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
26291
[Channel %1: ] Block %2: Maximum number of %3 protection area facets for internal
protection areas was exceeded.
Parameters:
%1 = Channel number
%2 = Block number
%3 = Maximum number of internal protection area facets
Explanation:
The maximum number of internal protection area facets was exceeded.
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Increase the number of permissible internal protection area facets (MD18894 $MN_MM_MAXNUM_3D_FACETS_INTERN).
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26292
[Channel %1: ] Block %2: Maximum number of %6 input points exceeded in the CAD file
$NP_FILENAME[%5] = %3.
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = File name
%4 = Index of the protection area element | maximum number of input points
Explanation:
The maximum permissible number of input points has been exceeded.
Note:
Parameter 4 contains the descriptions of parameters 5 and 6 separated by the character "|".
- 5 = Index of the protection area element
- 6 = Maximum number of input points
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Increase the number of permitted protection area facets (MD18895 $MN_MM_MAXNUM_3D_FACETS) or reduce the
number of defined facets in the CAD file.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26293
[Channel %1: ] Block %2: CAD file %3 could not be written.
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = File name
Explanation:
An internally created CAD file could not be written to the file system.
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Increase the memory capacity for the NC file system.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26294
[Channel %1: ] Block %2: CAD file $NP_FILENAME[%4] = %3 is not a valid VRML file
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = File name
%4 = Index of protection area element
Explanation:
The CAD file does not contain valid VRML data.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
493
NC alarms
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Check the format of the input CAD/VRML data.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26295
Protection area %1 was only roughly approximated.
Parameters:
%1 = Name of protection area
Explanation:
An automatic protection area could only be defined approximately on account of a lack of memory space.
Reaction:
Interface signals are set.
Alarm display.
Remedy:
Increase the number of permissible internal protection area facets (MD18894 $MN_MM_MAXNUM_3D_FACETS_INTERN).
Programm
Clear alarm with the Delete key or NC START.
continuation:
26296
[Channel %1: ] Block %2: CAD file $NP_FILENAME[%4] = %3 is not a valid STL file
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = File name
%4 = Index of protection area element
Explanation:
The CAD file does not contain any valid STL data
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Check the format of the CAD/STL file.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26297
[Channel %1: ] Block %2: CAD file $NP_FILENAME[%4] = %3 is not a valid NPP file
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = File name
%4 = Index of protection area element
Explanation:
The CAD file does not contain any valid NPP data
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Check the format of the NPP file.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26298
[channel %1: ] block %2: The Include file %4 which was to be read in the CAD file %3 could not
be found.
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = File name
%4 = File name
Explanation:
The Include file which was to be read in the specified CAD file could not be found.
Alarms
494
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Check name and path details of the Include file.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26299
[Channel %1: ] Block %2 Parameterization error %6 for edge %5 of tool '%3'.
Parameters:
%1 = Channel number
%2 = Block number, label
%3 = Name of the protection area of the tool
%4 = D number of tool edge | Error number
Explanation:
Definition of the tool is faulty. The cause of the error is defined more closely by the following error number:
-
1. The cutting edge position is invalid. Valid range is [0...9].
-
2. The cutting direction is invalid, Valid range is [0...4].
-
3. The DPV parameter $TC_DPV is invalid, Valid range is [0...6].
-
4. The holder angle ($TC_DP10) together with the clearance angle ($TC_DP24) do not define any valid cutting edge of
a turning tool. The sum $TC_DP10 + $TC_DP24 must be less than 180 degrees so that the insert angle is greater than zero.
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
Correct input parameters.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
26300
Loss of sign-of-life of the external collision avoidance.
Explanation:
The configured timeout (MD16904 $MN_COLLISION_EXT_TIMEOUT) for communication with the external collision
avoidance has expired.
Reaction:
NC Stop on alarm.
Alarm display.
Interface signals are set.
NC not ready.
Remedy:
Check external system for errors, if necessary lengthen timeout.
Programm
Clear alarm with the RESET key in all channels. Restart part program.
continuation:
26301
[Channel %1: ] Block %2: The maximum number %3 of 3D protection area facets has been
exceeded by %4.
Parameters:
%1 = Channel number
%2 = Block number
%3 = Maximum permissible number of protection area facets
%4 = Additional number
Explanation:
The maximum permissible number of protection area facets has been exceeded.
Reaction:
Correction block is reorganized.
Interface signals are set.
Alarm display.
Remedy:
The permissible number of protection area facets is determined by option data OD19830 $ON_COLLISION_MASK.
Retrofit corresponding option.
Programm
Clear alarm with NC START or RESET key and continue the program.
continuation:
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
495
NC alarms
26302
External collision avoidance: Waiting for connection.
Explanation:
An external collision avoidance was configured. NCK is waiting for the system to connect.
Reaction:
Alarm display.
Interface signals are set.
Remedy:
External system start, check connection if necessary.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
26350
External collision avoidance: System deactivated.
Explanation:
The external system has been deactivated. There is no collision protection!
Reaction:
Alarm display.
Interface signals are set.
Remedy:
Activate external system.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
26351
External collision avoidance: Initializing.
Explanation:
The external system has been connected but is not yet ready.
Reaction:
Alarm display.
Interface signals are set.
Remedy:
Waiting. Checking whether external system is signaling errors.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
26352
External collision avoidance: Measuring mode.
Explanation:
The external system is in measuring mode.
Reaction:
Alarm display.
Interface signals are set.
Remedy:
For details, see the external system output.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
26353
External collision avoidance: Error on inactive tool %1. Error code %2.
Parameters:
%1 = Tool number
%2 = Error code
Explanation:
The external system is signaling an error on an inactive tool.
Reaction:
Alarm display.
Interface signals are set.
Remedy:
Check external system and rectify reported error.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
26354
External collision avoidance: A motion is being slowed down or stopped (%1, %2, %3, %4).
Parameters:
%1 = Error code
%2 = Error code
%3 = Error code
%4 = Error code
Explanation:
A motion is being slowed down or stopped.
Reaction:
Alarm display.
Interface signals are set.
Alarms
496
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Remedy:
For details, see the external system output.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
26355
External collision avoidance: System is signaling a warning (%1, %2, %3, %4).
Parameters:
%1 = Error code
%2 = Error code
%3 = Error code
%4 = Error code
Explanation:
External system is signaling a warning.
Reaction:
Alarm display.
Interface signals are set.
Remedy:
For details, see the external system output.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
26370
External collision avoidance: Stop due to collision (%1, %2).
Parameters:
%1 = Error code
%2 = Error code
Explanation:
Reaction:
Alarm display.
NC Start disable in this channel.
NC Stop on alarm.
Interface signals are set.
Remedy:
Programm
Clear alarm with the RESET key. Restart part program
continuation:
26371
External collision avoidance: Stop (error on active tool %1, error code %2).
Parameters:
%1 = Tool number
%2 = Error code
Explanation:
The external system is signaling an error on the active tool.
Reaction:
Alarm display.
NC Start disable in this channel.
NC Stop on alarm.
Interface signals are set.
Remedy:
Check external system and rectify reported error.
Programm
Clear alarm with the Delete key or NC START.
continuation:
26372
External collision avoidance: Communication error (OPC UA, error code %1).
Parameters:
%1 = Error code
Explanation:
Reaction:
Alarm display.
NC Start disable in this channel.
NC Stop on alarm.
Interface signals are set.
Remedy:
Programm
Clear alarm with the Delete key or NC START.
continuation:
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
497
NC alarms
26373
External collision avoidance: Log error (%1, %2).
Parameters:
%1 = Error code
%2 = Error code
Explanation:
Reaction:
Alarm display.
NC Start disable in this channel.
NC Stop on alarm.
Interface signals are set.
Remedy:
Programm
Clear alarm with the Delete key or NC START.
continuation:
26374
External collision avoidance: System is signaling an error (%1, %2, %3, %4).
Parameters:
%1 = Error code
%2 = Error code
%3 = Error code
%4 = Error code
Explanation:
The external system is signaling an error.
Reaction:
Alarm display.
NC Start disable in this channel.
NC Stop on alarm.
Interface signals are set.
Remedy:
Check the external system error output / log files for details.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27000
Axis %1 is not safely referenced
Parameters:
%1 = Axis name, spindle number
Explanation:
There are two reasons for this alarm:
- the machine position has not yet been acknowledged by the user,
- the machine position has not yet been verified through follow-up referencing.
Even if the axis is already referenced, there is no confirmation that referencing has supplied the correct result. For example,
wrong results can occur if the axis was moved after the control was switched off, with the result that the standstill position
saved prior to switching off is no longer correct. To make sure that this does not happen, the user must acknowledge the
displayed actual position after the first referencing process.
When the user enable has first been set, follow-up referencing must be carried out each time the control is booted (with
absolute encoders, this follow-up referencing is executed automatically). This procedure is carried out to verify the standstill
position saved prior to switching off of the control.
Via the MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL (MD>=3), the alarm display can be set in such a way that the group
alarm 27100 is displayed for all SI axes.
Reaction:
Alarm display.
SGA "Axis safely referenced" is not set. SE will be switched off, if the actual safety position has not yet been confirmed by a
user agreement. If the user agreement has been set, SE will remain active. The safe cams are calculated and output.
However, their significance is limited as referencing has not been confirmed.
Remedy:
Traverse the axis to a known position, change to operating mode "Referencing" and press softkey "Agreement". Check the
positions displayed in the agreement screen on the machine. If they match the expected or known position, confirm this by
using the toggle key. If the user agreement has already been set, reference the axis again.
The user agreement can be changed only via keyswitch position 3 or after password entry.
WARNING:
If the axis is not referenced safely and the user agreement is not available, the following will apply:
- the safe cams are not yet safe
- the safe end positions are not yet active.
Alarms
498
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27001
Axis %1 error in a monitoring channel, code %2, values: NCK %3, drive %4
Parameters:
%1 = Axis name, spindle number
%2 = Additional info cross-comparison index
%3 = NCK comparison value extension
%4 = Additional info comparison value drive
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
499
NC alarms
Explanation:
A mutual comparison of the state of the safety-related monitoring functions is made cyclically between the two monitoring
channels (NCK and drive). The comparison is performed separately for each NCK/drive combination.
In each monitoring cycle (MD10091 $MN_INFO_SAFETY_CYCLE_TIME), one criterion from a comparison list is compared
between NCK and drive. In the next monitoring cycle, the next criterion is compared, etc. Once the complete comparison
list has been processed, processing of the comparisons starts again. The resulting total comparison time for processing the
list is displayed in MD10092 $MN_INFO_CROSSCHECK_CYCLE_TIME (factor x MD10091 $MN_INFO_SAFETY_CYCLE_TIME
- the factor may differ in the various software versions).
The alarm "Fault in a monitoring channel" is output if the mutual comparison of the two monitoring channels finds a
difference between input data or monitoring results. One of the monitors is no longer functioning reliably.
The cross-check index output in the alarm text is also named the STOP F code. The STOP F code where the NCK found the
first cross-check error is also output in alarm 27001.
The STOP F code of the drive (belonging to alarm C01711) can be found on the diagnostic display or in parameter r9795.
If there is a difference over multiple comparison steps, a number of STOP F code values can be displayed at these points one
after the other).
There are fault profiles that can be detected by several comparisons in the comparison list, i.e. the displayed STOP F code
value does not always provide clear information about the error cause. The relevant procedure is explained with the
individual error codes:
- 0 No error found in this channel; following alarm to drive alarm C01711.
- 1 Result list 1: Difference in SBH, SG, SBR or SE result, e.g. due to inconsistent activation of the monitoring channels. For
further information, see drive parameters r9710[0], r9710[1].
- 2 Result list 2: Difference in SN, n_x result. For further information, see drive parameters r9711[0], r9711[1].
- 3 Actual value difference greater than setting in MD36942 $MA_SAFE_POS_TOL.
- 4 Not assigned.
- 5 Function enables MD36901 $MA_SAFE_FUNCTION_ENABLE.
- 6 Velocity limit MD36931 $MA_SAFE_VELO_LIMIT[0].
- 7 Velocity limit MD36931 $MA_SAFE_VELO_LIMIT[1].
- 8 Velocity limit MD36931$MA_SAFE_VELO_LIMIT[2].
- 9 Velocity limit MD36931$MA_SAFE_VELO_LIMIT[3].
- 10 Tolerance for safe operating stop MD36930 $MA_SAFE_STANDSTILL_TOL.
- 11 Limit position MD36934 $MA_SAFE_POS_LIMIT_PLUS[0].
- 12 Limit position MD36935 $MA_SAFE_POS_LIMIT_MINUS[0].
- 13 Limit position MD36934 $MA_SAFE_POS_LIMIT_PLUS[1].
- 14 Limit position MD36935 $MA_SAFE_POS_LIMIT_MINUS[1].
- 15 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[0] + MD36940 $MA_SAFE_CAM_TOL.
- 16 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[0].
- 17 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[0] + MD36940 $MA_SAFE_CAM_TOL.
- 18 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[0].
- 19 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[1] + MD36940 $MA_SAFE_CAM_TOL.
- 20 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[1].
- 21 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[1] + MD36940 $MA_SAFE_CAM_TOL.
- 22 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[1].
- 23 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[2] + MD36940 $MA_SAFE_CAM_TOL.
- 24 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[2].
- 25 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[2] + MD36940 $MA_SAFE_CAM_TOL.
- 26 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[2].
- 27 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[3] + MD36940 $MA_SAFE_CAM_TOL.
- 28 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[3].
- 29 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[3] + MD36940 $MA_SAFE_CAM_TOL.
- 30 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[3].
- 31 Actual position tolerance MD36942 $MA_SAFE_POS_TOL. MD36949 $MA_SAFE_SLIP_VELO_TOL for active actual value
synchronization (slip)
- 32 Ref. position tolerance MD36944 $MA_SAFE_REFP_POS_TOL.
- 33 Delay SG[x] -> SG[y] MD36951 $MA_SAFE_VELO_SWITCH_DELAY.
- 34 Delay cross-check MD36950 $MA_SAFE_MODE_SWITCH_TIME.
Alarms
500
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
- 35 Delay pulse disable Stop B MD36956 $MA_SAFE_PULSE_DISABLE_DELAY.
- 36 Delay pulse disable test stop MD36957 $MA_SAFE_PULSE_DIS_CHECK_TIME
- 37 Delay Stop C -> SBH MD36952 $MA_SAFE_STOP_SWITCH_TIME_C.
- 38 Delay Stop D -> SBH MD36953 $MA_SAFE_STOP_SWITCH_TIME_D.
- 39 Delay Stop E -> SBH MD36954 $MA_SAFE_STOP_SWITCH_TIME_E.
- 40 Stop reaction when SG exceeded MD36961 $MA_SAFE_VELO_STOP_MODE.
- 41 Stop reaction when SE exceeded MD36962 $MA_SAFE_POS_STOP_MODE.
- 42 Standstill speed MD36960 $MA_SAFE_STANDSTILL_VELO_TOL.
- 43 Memory test, stop reaction.
- 44 Actual position value + SG[0] MD36931 $MA_SAFE_VELO_LIMIT[0].
- 45 Actual position value - SG[0] MD36931 $MA_SAFE_VELO_LIMIT[0].
- 46 Actual position value + SG[1] MD36931 $MA_SAFE_VELO_LIMIT[1].
- 47 Actual position value - SG[1] MD36931 $MA_SAFE_VELO_LIMIT[1].
- 48 Actual position value + SG[2] MD36931 $MA_SAFE_VELO_LIMIT[2].
- 49 Actual position value - SG[2] MD36931 $MA_SAFE_VELO_LIMIT[2].
- 50 Actual position value + SG[3] MD36931 $MA_SAFE_VELO_LIMIT[3].
- 51 Actual position value - SG[3] MD36931 $MA_SAFE_VELO_LIMIT[3].
- 52 Standstill position + tolerance MD36930 $MA_SAFE_STANDSTILL_TOL.
- 53 Standstill position - tolerance MD36930 $MA_SAFE_STANDSTILL_TOL.
- 54 Actual position value + n_x + tolerance MD36946 $MA_SAFE_VELO_X + MD36942 $MA_SAFE_POS_TOL.
- 55 Actual position value + n_x MD36946 $MA_SAFE_VELO_X.
- 56 Actual position value - n_x MD36946 $MA_SAFE_VELO_X.
- 57 Actual position value - n_x - tolerance MD36946 $MA_SAFE_VELO_X - MD36942 $MA_SAFE_POS_TOL
- 58 Active external standstill request.
- 59 SG override factor 1 MD36932 $MA_SAFE_VELO_OVR_FACTOR[0].
- 60 SG override factor 2 MD36932 $MA_SAFE_VELO_OVR_FACTOR[1].
- 61 SG override factor 3 MD36932 $MA_SAFE_VELO_OVR_FACTOR[2].
- 62 SG override factor 4 MD36932 $MA_SAFE_VELO_OVR_FACTOR[3].
- 63 SG override factor 5 MD36932 $MA_SAFE_VELO_OVR_FACTOR[4].
- 64 SG override factor 6 MD36932 $MA_SAFE_VELO_OVR_FACTOR[5].
- 65 SG override factor 7 MD36932 $MA_SAFE_VELO_OVR_FACTOR[6].
- 66 SG override factor 8 MD36932 $MA_SAFE_VELO_OVR_FACTOR[7].
- 67 SG override factor 9 MD36932 $MA_SAFE_VELO_OVR_FACTOR[8].
- 68 SG override factor 10 MD36932 $MA_SAFE_VELO_OVR_FACTOR[9].
- 69 SG override factor 11 MD36932 $MA_SAFE_VELO_OVR_FACTOR[10].
- 70 SG override factor 12 MD36932 $MA_SAFE_VELO_OVR_FACTOR[11].
- 71 SG override factor 13 MD36932 $MA_SAFE_VELO_OVR_FACTOR[12].
- 72 SG override factor 14 MD36932 $MA_SAFE_VELO_OVR_FACTOR[13].
- 73 SG override factor 15 MD36932 $MA_SAFE_VELO_OVR_FACTOR[14].
- 74 SG override factor 16 MD36932 $MA_SAFE_VELO_OVR_FACTOR[15].
- 75 Velocity limit n<nx MD36946 $MA_SAFE_VELO_X or velocity hysteresis n<nx MD36947
$MA_SAFE_VELO_X_HYSTERESIS.
- 76 Stop reaction SG1 MD36963 $MA_SAFE_VELO_STOP_REACTION[0].
- 77 Stop reaction SG2 MD36963 $MA_SAFE_VELO_STOP_REACTION[1].
- 78 Stop reaction SG3 MD36963 $MA_SAFE_VELO_STOP_REACTION[2].
- 79 Stop reaction SG4 MD36963 $MA_SAFE_VELO_STOP_REACTION[3].
- 80 Modulo value for safe cam MD36905 $MA_SAFE_MODULO_RANGE.
- 81 Actual velocity tolerance MD36948 $MA_SAFE_STOP_VELO_TOL.
- 82 SG override factor SGE 0...15 = active SGE position. -1 = SG override inactive (neither SG2 nor SG4 active, or function
is not selected in MD36901 $MA_SAFE_FUNCTION_ENABLE).
- 83 Acceptance test time different MD36958 $MA_SAFE_ACCEPTANCE_TST_TIMEOUT.
- 84 Delay time Stop F -> Stop B MD36955 $MA_SAFE_STOP_SWITCH_TIME_F.
- 85 Delay time pulse disable bus failure MD10089 $MN_SAFE_PULSE_DIS_TIME_BUSFAIL.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
501
NC alarms
- 86 Single encoder system MD36914 $MA_SAFE_SINGLE_ENC.
- 87 Encoder assignment MD36912 $MA_SAFE_ENC_INPUT_NR.
- 88 Cam enable MD36903 $MA_SAFE_CAM_ENABLE.
- 89 Encoder limit frequency MD36926 $MA_SAFE_ENC_FREQ_LIMIT.
- 90 Cam SGA outside MD36940 $MA_SAFE_CAM_TOL different
- 91 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[4] + MD36940 $MA_SAFE_CAM_TOL.
- 92 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[4].
- 93 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[4] + MD36940 $MA_SAFE_CAM_TOL.
- 94 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[4].
- 95 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[5] + MD36940 $MA_SAFE_CAM_TOL.
- 96 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[5].
- 97 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[5] + MD36940 $MA_SAFE_CAM_TOL.
- 98 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[5].
- 99 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[6] + MD36940 $MA_SAFE_CAM_TOL.
- 100 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[6].
- 101 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[6] + MD36940 $MA_SAFE_CAM_TOL.
- 102 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[6].
- 103 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[7] + MD36940 $MA_SAFE_CAM_TOL.
- 104 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[7].
- 105 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[7] + MD36940 $MA_SAFE_CAM_TOL.
- 106 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[7].
- 107 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[8] + MD36940 $MA_SAFE_CAM_TOL.
- 108 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[8].
- 109 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[8] + MD36940 $MA_SAFE_CAM_TOL.
- 110 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[8].
- 111 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[9] + MD36940 $MA_SAFE_CAM_TOL.
- 112 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[9].
- 113 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[9] + MD36940 $MA_SAFE_CAM_TOL.
- 114 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[9].
- 115 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[10] + MD36940 $MA_SAFE_CAM_TOL.
- 116 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[10].
- 117 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[10] + MD36940 $MA_SAFE_CAM_TOL.
- 118 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[10].
- 119 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[11] + MD36940 $MA_SAFE_CAM_TOL.
- 120 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[11].
- 121 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[11] + MD36940 $MA_SAFE_CAM_TOL.
- 122 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[11].
- 123 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[12] + MD36940 $MA_SAFE_CAM_TOL.
- 124 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[12].
- 125 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[12] + MD36940 $MA_SAFE_CAM_TOL.
- 126 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[12].
- 127 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[13] + MD36940 $MA_SAFE_CAM_TOL.
- 128 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[13].
- 129 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[13] + MD36940 $MA_SAFE_CAM_TOL.
- 130 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[13].
- 131 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[14] + MD36940 $MA_SAFE_CAM_TOL.
- 132 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[14].
- 133 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[14] + MD36940 $MA_SAFE_CAM_TOL.
- 134 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[14].
- 135 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[15] + MD36940 $MA_SAFE_CAM_TOL.
- 136 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[15].
- 137 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[15] + MD36940 $MA_SAFE_CAM_TOL.
Alarms
502
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
- 138 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[15].
- 139 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[16] + MD36940 $MA_SAFE_CAM_TOL.
- 140 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[16].
- 141 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[16] + MD36940 $MA_SAFE_CAM_TOL.
- 142 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[16].
- 143 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[17] + MD36940 $MA_SAFE_CAM_TOL.
- 144 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[17].
- 145 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[17] + MD36940 $MA_SAFE_CAM_TOL.
- 146 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[17].
- 147 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[18] + MD36940 $MA_SAFE_CAM_TOL.
- 148 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[18].
- 149 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[18] + MD36940 $MA_SAFE_CAM_TOL.
- 150 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[18].
- 151 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[19] + MD36940 $MA_SAFE_CAM_TOL.
- 152 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[19].
- 153 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[19] + MD36940 $MA_SAFE_CAM_TOL.
- 154 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[19].
- 155 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[20] + MD36940 $MA_SAFE_CAM_TOL.
- 156 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[20].
- 157 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[20] + MD36940 $MA_SAFE_CAM_TOL.
- 158 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[20].
- 159 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[21] + MD36940 $MA_SAFE_CAM_TOL.
- 160 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[21].
- 161 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[21] + MD36940 $MA_SAFE_CAM_TOL.
- 162 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[21].
- 163 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[22] + MD36940 $MA_SAFE_CAM_TOL.
- 164 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[22].
- 165 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[22] + MD36940 $MA_SAFE_CAM_TOL.
- 166 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[22].
- 167 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[23] + MD36940 $MA_SAFE_CAM_TOL.
- 168 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[23].
- 169 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[23] + MD36940 $MA_SAFE_CAM_TOL.
- 170 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[23].
- 171 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[24] + MD36940 $MA_SAFE_CAM_TOL.
- 172 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[24].
- 173 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[24] + MD36940 $MA_SAFE_CAM_TOL.
- 174 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[24].
- 175 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[25] + MD36940 $MA_SAFE_CAM_TOL.
- 176 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[25].
- 177 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[25] + MD36940 $MA_SAFE_CAM_TOL.
- 178 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[25].
- 179 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[26] + MD36940 $MA_SAFE_CAM_TOL.
- 180 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[26].
- 181 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[26] + MD36940 $MA_SAFE_CAM_TOL.
- 182 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[26].
- 183 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[27] + MD36940 $MA_SAFE_CAM_TOL.
- 184 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[27].
- 185 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[27] + MD36940 $MA_SAFE_CAM_TOL.
- 186 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[27].
- 187 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[28] + MD36940 $MA_SAFE_CAM_TOL.
- 188 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[28].
- 189 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[28] + MD36940 $MA_SAFE_CAM_TOL.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
503
NC alarms
- 190 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[28].
- 191 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[29] + MD36940 $MA_SAFE_CAM_TOL.
- 192 Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[29].
- 193 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[29] + MD36940 $MA_SAFE_CAM_TOL.
- 194 Cam position MD36937 $MA_SAFE_CAM_POS_MINUS[29].
- 195 Cam track assignment SN1 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[0].
- 196 Cam track assignment SN2 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[1].
- 197 Cam track assignment SN3 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[2].
- 198 Cam track assignment SN4 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[3].
- 199 Cam track assignment SN5 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[4].
- 200 Cam track assignment SN6 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[5].
- 201 Cam track assignment SN7 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[6].
- 202 Cam track assignment SN8 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[7].
- 203 Cam track assignment SN9 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[8].
- 204 Cam track assignment SN10 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[9].
- 205 Cam track assignment SN11 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[10].
- 206 Cam track assignment SN12 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[11].
- 207 Cam track assignment SN13 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[12].
- 208 Cam track assignment SN14 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[13].
- 209 Cam track assignment SN15 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[14].
- 210 Cam track assignment SN16 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[15].
- 211 Cam track assignment SN17 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[16].
- 212 Cam track assignment SN18 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[17].
- 213 Cam track assignment SN19 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[18].
- 214 Cam track assignment SN20 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[19].
- 215 Cam track assignment SN21 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[20].
- 216 Cam track assignment SN22 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[21].
- 217 Cam track assignment SN23 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[22].
- 218 Cam track assignment SN24 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[23].
- 219 Cam track assignment SN25 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[24].
- 220 Cam track assignment SN26 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[25].
- 221 Cam track assignment SN27 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[26].
- 222 Cam track assignment SN28 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[27].
- 223 Cam track assignment SN29 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[28].
- 224 Cam track assignment SN30 MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[29].
- 225 Result list 3: Inconsistent results for "Safe cam track" of cams SN1..6.
- 226 Result list 4: Inconsistent results for "Safe cam track" of cams SN7..12.
- 227 Result list 5: Inconsistent results for "Safe cam track" of cams SN13..18.
- 228 Result list 6: Inconsistent results for "Safe cam track" of cams SN19..24.
- 229 Result list 7: Inconsistent results for "Safe cam track" of cams SN25.. 30.
- 230 Filter time constant n<nx MD36945 $MA_SAFE_VELO_X_FILTER_TIME.
- 231 Velocity hysteresis n<nx MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
- 232 Safe smoothed actual velocity.
- 233 Actual velocity nx: MD36946 $MA_SAFE_VELO_X.
- 234 Actual velocity nx - tolerance: MD36946 $MA_SAFE_VELO_X - MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
- 235 Actual velocity -nx + tolerance: -MD36946 $MA_SAFE_VELO_X + MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
- 236 Actual velocity -nx: -MD36946 $MA_SAFE_VELO_X.
- 237 SGA "n<nx" different outside MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
- 238 Not assigned.
- 239 Not assigned.
- 240 Not assigned.
- 241 Not assigned.
Alarms
504
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
- 242 Not assigned.
- 243 Not assigned.
- 244 Not assigned.
- 245 Not assigned.
- 246 Not assigned.
- 247 Not assigned.
- 248 Not assigned.
- 249 Not assigned.
- 250 Not assigned.
- 251 Not assigned.
- 252 Not assigned.
- 253 Not assigned.
- 254 Not assigned.
- 255 Not assigned.
- 256 Result list 1: Difference in SBH, SG, SBR, or SE result, e.g. due to inconsistent activation of the monitoring channels.
For additional information, see drive parameters r9710[0], r9710[1].
- 257 Not assigned.
- 258 Not assigned.
- 259 Not assigned.
- 260 Not assigned.
- 261 Not assigned.
- 262 Not assigned.
- 263 Not assigned.
- 264 Not assigned.
- 265 Result list 1: Difference in SBH, SG, SBR, or SE result, e.g. due to inconsistent activation of the monitoring channels.
For additional information, see drive parameters r9710[0], r9710[1].
- 266 Changeover speed to safe operating stop MD37920 $MA_SAFE_STANDSTILL_VELO_LIMIT.
- 267 Delay time for switch to safe operating stop MD37922 $MA_SAFE_STANDSTILL_DELAY.
- 1000 Control timer expired: If one channel informs another of an SGE change, this control timer is used to check whether
the update timer in the other channel has expired.
- 1002 User agreement inconsistent: Data for user agreement inconsistent in the two monitoring channels after 4 seconds.
The following values are displayed in the alarm text:
%3 State of the NCK user enable.
%4 State of the drive user enable.
- 1003 Reference tolerance MD36944 $MA_SAFE_REFP_POS_TOL exceeded.
- 1004 Plausibility error in user enable.
- 1005 Pulses already disabled on test stop selection.
- 1009 Pulses not disabled after test stop time MD36957 $MA_SAFE_PULSE_DIS_CHECK_TIME.
- 1011 NCK/drive acceptance test states are inconsistent.
- 1013 NCK user enable from PLC SRAM and NCK user enable from NCK machine data are inconsistent.
- 1014 NCK axis number from PLC SRAM and NCK axis number from startup are inconsistent.
- 1020 Communication disrupted between NCK monitoring channel and drive monitoring channel.
- 1023 Error during efficiency test in Sensor Module.
- 1024 NCK standstill position from PLC SRAM and NCK standstill position from the NCK machine data are inconsistent.
- 1025 Plausibility error in park selection: Encoder reporting parking without user request.
- 1026 Plausibility error in cam synchronization between NCK and PLC ("Safe cam track" function).
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
505
NC alarms
Remedy:
Find the difference between the monitoring channels. Error code shows the cause of the alarm.
It may be the case that safety-relevant machine data is no longer consistent (reload if so) or
that the safety-relevant inputs do not have the same level (check).
If an error of this nature cannot be found, an error may have occurred in the CPU (a memory cell may have "tipped over", for
example). This error may be temporary (remove with power-on) or permanent (replace hardware if the error is displayed
again after power-on).
Error codes for STOP F:
0: No errors in this channel. Look for the cause in the other channel.
1: Result list 1. Inconsistent control of the functions via the SGEs; analyze precise error coding in SINAMICS r9710[0],
r9710[1].
2: Result list 2. Check cam tolerance, analyze precise error coding in SINAMICS r9711[0], r9711[1].
3: Actual position value. Incorrect encoder evaluation (check MDs). Standstill position not stored consistently.
4: No cross check.
5: Function enables. Enter MDs consistently.
6: Limit value for SG1. Enter MDs consistently.
7: Limit value for SG2. Enter MDs consistently.
8: Limit value for SG3. Enter MDs consistently.
9: Limit value for SG4. Enter MDs consistently.
10: Standstill tolerance. Enter MDs consistently.
11: Upper limit value SE1. Enter MDs consistently.
12: Lower limit value SE1. Enter MDs consistently.
13: Upper limit value SE2. Enter MDs consistently.
14: Lower limit value SE2. Enter MDs consistently.
15: Safe cam 1+ (+tolerance). Enter MDs consistently.
16: Safe cam 1+. Enter MDs consistently.
17: Safe cam 1- (+tolerance). Enter MDs consistently.
18: Safe cam 1-. Enter MDs consistently.
19: Safe cam 2+ (+tolerance). Enter MDs consistently.
20: Safe cam 2+. Enter MDs consistently.
21: Safe cam 2- (+tolerance). Enter MDs consistently.
22: Safe cam 2-. Enter MDs consistently.
23: Safe cam 3+ (+tolerance). Enter MDs consistently.
24: Safe cam 3+. Enter MDs consistently.
25: Safe cam 3- (+tolerance). Enter MDs consistently.
26: Safe cam 3-. Enter MDs consistently.
27: Safe cam 4+ (+tolerance). Enter MDs consistently.
28: Safe cam 4+. Enter MDs consistently.
29: Safe cam 4- (+tolerance). Enter MDs consistently.
30: Safe cam 4-. Enter MDs consistently.
31: Position tolerance. Enter MDs consistently.
32: Reference position tolerance. Enter MDs consistently.
33: Time velocity changeover. Enter MDs consistently.
34: Tolerance time SGE changeover. Enter MDs consistently.
35: Delay time pulse disable. Enter MDs consistently.
36: Time for checking pulse disable. Enter MDs consistently.
37: Transition time STOP C to SBH. Enter MDs consistently.
38: Transition time STOP D to SBH. Enter MDs consistently.
39: Transition time STOP E to SBH. Enter MDs consistently.
40: Stop reaction to SG. Enter MDs consistently.
41: Stop reaction to SE. Enter MDs consistently.
42: Creep speed pulse disable. Enter MDs consistently.
43: Memory test stop reaction.
44: Actual position value + limit value SG1.
Alarms
506
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
45: Actual position value - limit value SG1.
46: Actual position value + limit value SG2.
47: Actual position value - limit value SG2.
48: Actual position value + limit value SG3.
49: Actual position value - limit value SG3.
50: Actual position value + limit value SG4.
51: Actual position value - limit value SG4.
52: Standstill position + tolerance.
53: Standstill position - tolerance.
54: Actual position value "+ nx" + tolerance.
55: Actual position value "+ nx".
56: Actual position value "- nx".
57: Actual position value "- nx" + tolerance.
58: Current stop request.
59: SG override factor 1. Enter MDs consistently.
60: SG override factor 2. Enter MDs consistently.
61: SG override factor 3. Enter MDs consistently.
62: SG override factor 4. Enter MDs consistently.
63: SG override factor 5. Enter MDs consistently.
64: SG override factor 6. Enter MDs consistently.
65: SG override factor 7. Enter MDs consistently.
66: SG override factor 8. Enter MDs consistently.
67: SG override factor 9. Enter MDs consistently.
68: SG override factor 10. Enter MDs consistently.
69: SG override factor 11. Enter MDs consistently.
70: SG override factor 12. Enter MDs consistently.
71: SG override factor 13. Enter MDs consistently.
72: SG override factor 14. Enter MDs consistently.
73: SG override factor 15. Enter MDs consistently.
74: SG override factor 16. Enter MDs consistently.
75: Velocity limit n<nx or velocity hysteresis. Enter MDs consistently.
76: Stop reaction with SG1. Enter MDs consistently.
77: Stop reaction with SG2. Enter MDs consistently.
78: Stop reaction with SG3. Enter MDs consistently.
79: Stop reaction with SG4. Enter MDs consistently.
80: Modulo value for safe cams. Enter MDs consistently.
81: Velocity tolerance for safe acceleration monitoring. Enter MDs consistently.
82: SG override factor SGEs. Control SGEs consistently.
83: Acceptance test duration. Enter MDs consistently.
84: Stop F -> Stop B delay time. Enter MDs consistently.
85: Bus failure pulse disable delay time. Enter MDs consistently.
86: Make MD36914 $MA_SAFE_SINGLE_ENC and drive parameter p9526 consistent.
87: Make MD36912 $MA_SAFE_ENC_INPUT_NR and p9526 consistent.
88: Make MD36903 $MA_SAFE_CAM_ENABLE and drive parameter p9503 consistent.
89: Encoder limit frequency. Enter MDs consistently.
90: Check cam positions, MD36940 $MA_SAFE_CAM_TOL.
91: Safe cam 5+ (+ tolerance). Enter MDs consistently.
92: Safe cam 5+. Enter MDs consistently.
93: Safe cam 5- (+ tolerance). Enter MDs consistently.
94: Safe cam 5-. Enter MDs consistently.
95: Safe cam 6+ (+ tolerance). Enter MDs consistently.
96: Safe cam 6+. Enter MDs consistently.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
507
NC alarms
97: Safe cam 6- (+ tolerance). Enter MDs consistently.
98: Safe cam 6-. Enter MDs consistently.
99: Safe cam 7+ (+ tolerance). Enter MDs consistently.
100: Safe cam 7+. Enter MDs consistently.
101: Safe cam 7- (+ tolerance). Enter MDs consistently.
102: Safe cam 7-. Enter MDs consistently.
103: Safe cam 8+ (+ tolerance). Enter MDs consistently.
104: Safe cam 8+. Enter MDs consistently.
105: Safe cam 8- (+ tolerance). Enter MDs consistently.
106: Safe cam 8-. Enter MDs consistently.
107: Safe cam 9+ (+ tolerance). Enter MDs consistently.
108: Safe cam 9+. Enter MDs consistently.
109: Safe cam 9- (+ tolerance). Enter MDs consistently.
110: Safe cam 9-. Enter MDs consistently.
111: Safe cam 10+ (+ tolerance). Enter MDs consistently.
112: Safe cam 10+. Enter MDs consistently.
113: Safe cam 10- (+ tolerance). Enter MDs consistently.
114: Safe cam 10-. Enter MDs consistently.
115: Safe cam 11+ (+ tolerance). Enter MDs consistently.
116: Safe cam 11+. Enter MDs consistently.
117: Safe cam 11- (+ tolerance). Enter MDs consistently.
118: Safe cam 11-. Enter MDs consistently.
119: Safe cam 12+ (+ tolerance). Enter MDs consistently.
120: Safe cam 12+. Enter MDs consistently.
121: Safe cam 12- (+ tolerance). Enter MDs consistently.
122: Safe cam 12-. Enter MDs consistently.
123: Safe cam 13+ (+ tolerance). Enter MDs consistently.
124: Safe cam 13+. Enter MDs consistently.
125: Safe cam 13- (+ tolerance). Enter MDs consistently.
126: Safe cam 13-. Enter MDs consistently.
127: Safe cam 14+ (+ tolerance). Enter MDs consistently.
128: Safe cam 14+. Enter MDs consistently.
129: Safe cam 14- (+ tolerance). Enter MDs consistently.
130: Safe cam 14-. Enter MDs consistently.
131: Safe cam 15+ (+ tolerance). Enter MDs consistently.
132: Safe cam 15+. Enter MDs consistently.
133: Safe cam 15- (+ tolerance). Enter MDs consistently.
134: Safe cam 15-. Enter MDs consistently.
135: Safe cam 16+ (+ tolerance). Enter MDs consistently.
136: Safe cam 16+. Enter MDs consistently.
137: Safe cam 16- (+ tolerance). Enter MDs consistently.
138: Safe cam 16-. Enter MDs consistently.
139: Safe cam 17+ (+ tolerance). Enter MDs consistently.
140: Safe cam 17+. Enter MDs consistently.
141: Safe cam 17- (+ tolerance). Enter MDs consistently.
142: Safe cam 17-. Enter MDs consistently.
143: Safe cam 18+ (+ tolerance). Enter MDs consistently.
144: Safe cam 18+. Enter MDs consistently.
145: Safe cam 18- (+ tolerance). Enter MDs consistently.
146: Safe cam 18-. Enter MDs consistently.
147: Safe cam 19+ (+ tolerance). Enter MDs consistently.
148: Safe cam 19+. Enter MDs consistently.
Alarms
508
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
149: Safe cam 19- (+ tolerance). Enter MDs consistently.
150: Safe cam 19-. Enter MDs consistently.
151: Safe cam 20+ (+ tolerance). Enter MDs consistently.
152: Safe cam 20+. Enter MDs consistently.
153: Safe cam 20- (+ tolerance). Enter MDs consistently.
154: Safe cam 20-. Enter MDs consistently.
155: Safe cam 21+ (+ tolerance). Enter MDs consistently.
156: Safe cam 21+. Enter MDs consistently.
157: Safe cam 21- (+ tolerance). Enter MDs consistently.
158: Safe cam 21-. Enter MDs consistently.
159: Safe cam 22+ (+ tolerance). Enter MDs consistently.
160: Safe cam 22+. Enter MDs consistently.
161: Safe cam 22- (+ tolerance). Enter MDs consistently.
162: Safe cam 22-. Enter MDs consistently.
163: Safe cam 23+ (+ tolerance). Enter MDs consistently.
164: Safe cam 23+. Enter MDs consistently.
165: Safe cam 23- (+ tolerance). Enter MDs consistently.
166: Safe cam 23-. Enter MDs consistently.
167: Safe cam 24+ (+ tolerance). Enter MDs consistently.
168: Safe cam 24+. Enter MDs consistently.
169: Safe cam 24- (+ tolerance). Enter MDs consistently.
170: Safe cam 24-. Enter MDs consistently.
171: Safe cam 25+ (+ tolerance). Enter MDs consistently.
172: Safe cam 25+. Enter MDs consistently.
173: Safe cam 25- (+ tolerance). Enter MDs consistently.
174: Safe cam 25-. Enter MDs consistently.
175: Safe cam 26+ (+ tolerance). Enter MDs consistently.
176: Safe cam 26+. Enter MDs consistently.
177: Safe cam 26- (+ tolerance). Enter MDs consistently.
178: Safe cam 26-. Enter MDs consistently.
179: Safe cam 27+ (+ tolerance). Enter MDs consistently.
180: Safe cam 27+. Enter MDs consistently.
181: Safe cam 27- (+ tolerance). Enter MDs consistently.
182: Safe cam 27-. Enter MDs consistently.
183: Safe cam 28+ (+ tolerance). Enter MDs consistently.
184: Safe cam 28+. Enter MDs consistently.
185: Safe cam 28- (+ tolerance). Enter MDs consistently.
186: Safe cam 28-. Enter MDs consistently.
187: Safe cam 29+ (+ tolerance). Enter MDs consistently.
188: Safe cam 29+. Enter MDs consistently.
189: Safe cam 29- (+ tolerance). Enter MDs consistently.
190: Safe cam 29-. Enter MDs consistently.
191: Safe cam 30+ (+ tolerance). Enter MDs consistently.
192: Safe cam 30+. Enter MDs consistently.
193: Safe cam 30- (+ tolerance). Enter MDs consistently.
194: Safe cam 30-. Enter MDs consistently.
195: Cam track assignment SN1. Enter MDs consistently and check cam enable and parameterization.
196: Cam track assignment SN2. Enter MDs consistently and check cam enable and parameterization.
197: Cam track assignment SN3. Enter MDs consistently and check cam enable and parameterization.
198: Cam track assignment SN4. Enter MDs consistently and check cam enable and parameterization.
199: Cam track assignment SN5. Enter MDs consistently and check cam enable and parameterization.
200: Cam track assignment SN6. Enter MDs consistently and check cam enable and parameterization.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
509
NC alarms
201: Cam track assignment SN7. Enter MDs consistently and check cam enable and parameterization.
202: Cam track assignment SN8. Enter MDs consistently and check cam enable and parameterization.
203: Cam track assignment SN9. Enter MDs consistently and check cam enable and parameterization.
204: Cam track assignment SN10. Enter MDs consistently and check cam enable and parameterization.
205: Cam track assignment SN11. Enter MDs consistently and check cam enable and parameterization.
206: Cam track assignment SN12. Enter MDs consistently and check cam enable and parameterization.
207: Cam track assignment SN13. Enter MDs consistently and check cam enable and parameterization.
208: Cam track assignment SN14. Enter MDs consistently and check cam enable and parameterization.
209: Cam track assignment SN15. Enter MDs consistently and check cam enable and parameterization.
210: Cam track assignment SN16. Enter MDs consistently and check cam enable and parameterization.
211: Cam track assignment SN17. Enter MDs consistently and check cam enable and parameterization.
212: Cam track assignment SN18. Enter MDs consistently and check cam enable and parameterization.
213: Cam track assignment SN19. Enter MDs consistently and check cam enable and parameterization.
214: Cam track assignment SN20. Enter MDs consistently and check cam enable and parameterization.
215: Cam track assignment SN21. Enter MDs consistently and check cam enable and parameterization.
216: Cam track assignment SN22. Enter MDs consistently and check cam enable and parameterization.
217: Cam track assignment SN23. Enter MDs consistently and check cam enable and parameterization.
218: Cam track assignment SN24. Enter MDs consistently and check cam enable and parameterization.
219: Cam track assignment SN25. Enter MDs consistently and check cam enable and parameterization.
220: Cam track assignment SN26. Enter MDs consistently and check cam enable and parameterization.
221: Cam track assignment SN27. Enter MDs consistently and check cam enable and parameterization.
222: Cam track assignment SN28. Enter MDs consistently and check cam enable and parameterization.
223: Cam track assignment SN29. Enter MDs consistently and check cam enable and parameterization.
224: Cam track assignment SN30. Enter MDs consistently and check cam enable and parameterization.
225: Result list 3. Check cam tolerances, evaluate precise error coding in drive r9735[0,1].
226: Result list 4. Check cam tolerances, evaluate precise error coding in drive r9736[0,1].
227: Result list 5. Check cam tolerances, evaluate precise error coding in drive r9737[0,1].
228: Result list 6. Check cam tolerances, evaluate precise error coding in drive r9738[0,1].
229: Result list 7. Check cam tolerances, evaluate precise error coding in drive r9739[0,1].
230: Make MD36945 $MA_SAFE_VELO_X_FILTER_TIME and drive parameter p9545 consistent.
231: Make MD36947 $MA_SAFE_VELO_X_HYSTERESIS and drive parameter p9547 consistent.
232: Increase MD36947 $MA_SAFE_VELO_X_HYSTERESIS, Increase setting of MD36945 $MA_SAFE_VELO_X_FILTER_TIME.
233: Check MD36946 $MA_SAFE_VELO_X, MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
234: Check MD36946 $MA_SAFE_VELO_X, MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
235: Check MD36946 $MA_SAFE_VELO_X, MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
236: Check MD36946 $MA_SAFE_VELO_X, MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
237: Check MD36946 $MA_SAFE_VELO_X, MD36947 $MA_SAFE_VELO_X_HYSTERESIS.
238 Not assigned.
239 Not assigned.
240 Not assigned.
241 Not assigned.
242 Not assigned.
243 Not assigned.
244 Not assigned.
245 Not assigned.
246 Not assigned.
247 Not assigned.
248 Not assigned.
249 Not assigned.
250 Not assigned.
251 Not assigned.
252 Not assigned.
Alarms
510
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
253 Not assigned.
254 Not assigned.
255 Not assigned.
256 Result list 1: Inconsistent activation of the functions via the SGEs, evaluate precise error coding in SINAMICS r9710[0],
r9710[1].
257 Not assigned.
258 Not assigned.
259 Not assigned.
260 Not assigned.
261 Not assigned.
262 Not assigned.
263 Not assigned.
264 Not assigned.
265 Result list 1: Inconsistent activation of the functions via the SGEs, evaluate precise error coding in SINAMICS r9710[0],
r9710[1].
266 Check MD37920 $MA_SAFE_STANDSTILL_VELO_LIMIT.
267 Check MD37922 $MA_SAFE_STANDSTILL_DELAY.
1000: Control timer expired. Too many switching operations on the SGEs (e.g. due to contact problems, loose contact).
1002: User agreement timer expired.
1003: Reference tolerance violated. Compare the reference position with the current safe actual position.
1004: Plausibility of user agreement is violated.
1005: Pulses already disabled during test stop selection. Test stop selection with missing pulse enable, error in the wiring
of the SGE "Pulses have been deleted".
1009: Trigger a subsequent stop after test stop. Check the wiring. Check the SGE configuration via MD36976
$MA_SAFE_PULSE_STATUS_INPUT. Check the time level for test stop.
1011: Acceptance test timer expired.
1013: Restore data consistency with power-on.
1014: Restore data consistency with power-on..
1020: Cyclic communication between NCK and drive no longer functioning.
1023: Check Sensor Module.
1024: Restore data consistency with power-on.
1025: Plausibility violation in park selection. Check encoder hardware and communication with encoder.
1026: Check communication between PLC and drive and between PLC and NCK.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
If STOP B was triggered, a power OFF/ON of the control will be required.
27002
Axis %1 test stop is running
Parameters:
%1 = Axis name, spindle number
Explanation:
Proper functioning of the switch-off signal path is just being tested by setting of the SGE "Test stop selection".
Reaction:
Alarm display.
Remedy:
The message serves only for user information.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
The alarm will disappear automatically after expiry of the delay time - defined in MD36957
$MA_SAFE_PULSE_DIS_CHECK_TIME - and after removal of SGE "Test stop selection", if the control recognizes pulse
suppression, i.e. the test has been completed successfully. An unsuccessful test can be recognized by alarm 27001 with error
code 1005 or by alarm 27024.
27003
Checksum error found: %1 %2
Parameters:
%1 = Note on code section or table
%2 = Table number
Explanation:
Checksum error in safety-relevant code or safety-relevant data. The safe monitoring functions (Safety Integrated) in the NCK
could be affected.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
511
NC alarms
Reaction:
Alarm display.
Remedy:
Continue to work very carefully. Power OFF/ON of the control required. If this error occurs again, contact your service
personnel.
Programm
Switch control OFF - ON.
continuation:
27004
Axis %1 difference safe input %2, NCK %3, drive %4
Parameters:
%1 = Axis name, spindle number
%2 = Monitoring input
%3 = Interface identifier NCK input
%4 = Interface identifier drive input
Explanation:
A difference has been found at the specified safe input. The state of the specified input signal differed in the two monitoring
channels NCK and drive for the duration set in MD36950 $MA_SAFE_MODE_SWITCH_TIME.
Monitoring affected:
SS/SV = Difference in SGE "Deselection of safe operating stop/Safe velocity"
SS = Difference in SGE "Safe operating stop"
SV = Difference in SGEs "Selection safe velocity"
SP = Difference in SGE "Selection safe limit positions"
SVOVR = Difference in SGEs "Selection SG correction"
Interface identifier NCK input (SPL interface):
<io>
= Parameterised SPL interface ($A_OUTSI, $A_INSE)
<bit>
= Bit number in SPL interface (1...192)
<value>
= Value of NCK SGE (0,1)
Interface identifier drive input:
DBX<byte><bit>=<value >
<byte>
= Byte number in axis-specific DB (22, 23, 32, 33)
<bit>
= Bit number in byte (0...7)
<value>
= Value of drive SGE (0,1)
This alarm can be masked by setting MD10096 $MN_SAFE_DIAGNOSIS_MASK, bit 0 = 0.
Reaction:
Alarm display.
Remedy:
Check settings for safe input signals (SPL parameterization, PLC DB parameters).
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27005
Axis %1 error in data cross check: static actual value difference
Parameters:
%1 = Axis name, spindle number
Explanation:
Via the data cross check between NCK and drive monitoring channel, a difference in actual values was detected, which is
greater than the maximum tolerance defined in MD36942 $MA_SAFE_POS_TOL. This can be checked by means of the safe
position values for the two monitoring channels displayed in the service menu.
The alarm is displayed only, if monitoring with absolute reference (SE/SN) has been enabled for the specified axis and if the
user enable has been set. The alarm is cleared, as soon as the user enable is deleted or the actual value difference between
the two monitoring channels falls again below the maximum permissible difference.
Reaction:
Alarm display.
Remedy:
If the alarm is present statically, the user enable must be deleted. When the control is then rebooted, the machine can be
brought to the safe state again and operation resumed by a new referencing process and setting of the user enable. Prior
to setting the user enable, the actual position of the axis displayed in the "User enable" screen must be compared with the
current machine position. This is obligatory to ensure the proper functioning of the safe limit positions (SE) and safe cams
(SN).
A change of the user acknowledgment is only possible with key switch position 3 or after input of a password.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
Alarms
512
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
27007
Axis %1 acceptance test mode is active
Parameters:
%1 = Axis name, spindle number
Explanation:
Via the operator panel, an SI acceptance test has been started for example with the acceptance test wizard. The acceptance
test mode is activated via the NCK and drive for the time of this acceptance test. In the acceptance test mode, SI PowerOn
alarms can be acknowledged with the Reset key.
Reaction:
Alarm display.
Remedy:
Deselect the acceptance test, for example with the acceptance test wizard or wait until completed (acceptance test time can
be parameterized via MD36958 $MA_SAFE_ACCEPTANCE_TST_TIMEOUT).
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27008
Axis %1 SW limit switch deactivated
Parameters:
%1 = Axis name, spindle number
Explanation:
Via the HMI, the SI acceptance test Safe limit position has been started, for example with the acceptance test wizard. For
these acceptance tests, the single-channel software limit switches are deactivated for the axis/spindle, in order to assure
that the safe limit positions can be approached.
Reaction:
Alarm display.
Deactivation of the single-channel software limit switch for the displayed axis/spindle.
Remedy:
Deselect the acceptance test, for example with the acceptance test wizard, or wait until completed.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27010
Axis %1 tolerance for safe standstill exceeded
Parameters:
%1 = Axis name, spindle number
Explanation:
The axis has moved too far away from the setpoint position. It is further away than allowed in MD36930
$MA_SAFE_STANDSTILL_TOL.
The alarm can be reprogrammed in the MD11412 $MN_ALARM_REACTION_CHAN_NOREADY (channel not ready).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Channel not ready.
Stop axis with STOP B. As soon as the actual speed value is lower than defined in MD36960
$MA_SAFE_STANDSTILL_VELO_TOL, but at the latest after the time set in MD36956 $MA_SAFE_PULSE_DISABLE_DELAY has
elapsed, the pulses will be disabled (STOP A).
Remedy:
Check the tolerance of zero speed monitoring: does the value match the precision and control dynamics of the axis? If not,
increase tolerance. If yes, check the machine for any damage and rectify it.
Programm
Switch control OFF - ON.
continuation:
27011
Axis %1 safe velocity exceeded
Parameters:
%1 = Axis name, spindle number
Explanation:
The axis has moved too quickly and faster than allowed in MD36931 $MA_SAFE_VELO_LIMIT.
If the function "Correction safe velocity" is enabled in MD36901 $MA_SAFE_FUNCTION_ENABLE, the active correction value
from MD36932 $MA_SAFE_VELO_OVR_FACTOR[0...15] for the permissible velocity must be considered for SG2 and SG4.
Special case:
With active SBH/SG and a 1-encoder system, the velocity that corresponds to an encoder limit frequency has been exceeded.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
513
NC alarms
Reaction:
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Axis stop with STOP A, C, D or E, depending on the configuration in MD36961 $MA_SAFE_VELO_STOP_MODE or MD36963
$MA_SAFE_VELO_STOP_REACTION.
Remedy:
If no obvious operator error occurred: Check the input value of the MD; check SGEs: Is the correct safe velocity selected?
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27012
Axis %1 safe end position exceeded
Parameters:
%1 = Axis name, spindle number
Explanation:
The axis has exceeded the limit position entered in MD36934 $MA_SAFE_POS_LIMIT_PLUS or MD36935
$MA_SAFE_POS_LIMIT_MINUS.
Reaction:
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Stop the axis with STOP C,D or E, depending on the configuration in MD36962 $MA_SAFE_POS_STOP_MODE.
Remedy:
If no obvious operator error occurred: Check the input value of the machine data and check the SGEs: Has the correct one
of 2 limit positions been selected?
The alarm will persist as long as the axis is beyond the limit position. To be able to move it again, either
- push the axis manually,
- switch to another limit position pair so that the axis is in the permitted range again,
- cancel the user enable and trigger a PO reset. The alarm "Axis is not safely referenced" appears and the limit switch
monitoring functions are deactivated. Move the machine back so that it is in the permitted range again. Then give the user
enable again.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
Remove the user agreement for this axis. Then press the RESET key causing the program to be canceled and the alarm to be
deleted. Traverse the axis in JOG mode to the valid traversing range. After fault correction of the NC program and an axis
position check, the user agreement can be set again and the program can be restarted.
27013
Axis %1 Safe monitoring for acceleration exceeded
Parameters:
%1 = Axis name, spindle number
Explanation:
After the initiation of STOP B or C, the velocity exceeded the tolerance value entered in MD36948
$MA_SAFE_STOP_VELO_TOL.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Channel not ready.
Pulse interlock by triggering a STOP A.
Remedy:
Check MD36948 $MA_SAFE_STOP_VELO_TOL. Check the braking behavior of the affected drive.
Programm
Switch control OFF - ON.
continuation:
27020
Axis %1 stop E triggered
Parameters:
%1 = Axis name, spindle number
Alarms
514
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Explanation:
This alarm is output with alarms 27011 "Safe velocity exceeded" or 27012 "Safe limit position exceeded" (if these are
configured in MD36961 $MA_SAFE_VELO_STOP_MODE, MD36963 $MA_SAFE_VELO_STOP_REACTION or MD36962
$MA_SAFE_POS_STOP_MODE) or alarm 27090 after occurrence of a SPL data cross-check error.
Reaction:
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Trigger a LIFTFAST ASUB and internal activation of the safe operational stop (SBH) after expiry of the time set in MD36954
$MA_SAFE_STOP_SWITCH_TIME_E.
Remedy:
Eliminate causes of the alarms 27011 "Safe velocity exceeded" or 27012 "Safe limit position exceeded" or 27090 "Error in
data cross-check NCK-PLC" (see description of these alarms).
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27021
Axis %1 stop D triggered
Parameters:
%1 = Axis name, spindle number
Explanation:
This alarm is output together with alarms 27011 "Safe velocity exceeded" or 27012 "Safe limit position exceeded" (if these
are configured in MD36961 $MA_SAFE_VELO_STOP_MODE, MD36963 $MA_SAFE_VELO_STOP_REACTION or MD36962
$MA_SAFE_POS_STOP_MODE) or alarm 27090 after occurrence of an SPL data cross-check error.
Reaction:
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Trigger a "Deceleration on the path" and internal activation of the safe operational stop (SBH) after expiry of the time set in
MD36953 $MA_SAFE_STOP_SWITCH_TIME_D.
Remedy:
Eliminate causes of the alarms 27011 "Safe velocity exceeded" or 27012 "Safe limit position exceeded" or 27090 "Error in
data cross-check NCK-PLC" (see description of these alarms).
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27022
Axis %1 stop C triggered
Parameters:
%1 = Axis name, spindle number
Explanation:
This alarm is output together with alarms 27011 "Safe velocity exceeded" or 27012 "Safe limit position exceeded" (when
configured as such in MD36961 $MA_SAFE_VELO_STOP_MODE, MD36963$MA_SAFE_VELO_STOP_REACTION or MD36962
$MA_SAFE_POS_STOP_MODE).
Reaction:
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Triggering of "Deceleration on the current limit / OFF3 ramp" and internal activation of the safe operating stop (SBH) after
expiry of the time set in MD36952 $MA_SAFE_STOP_SWITCH_TIME_C.
Remedy:
Eliminate causes of alarm 27011 "Safe velocity exceeded" or 27012 "Safe limit position exceeded" (see description of these
alarms).
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27023
Axis %1 stop B triggered
Parameters:
%1 = Axis name, spindle number
Explanation:
This alarm is output together with alarm 27010 "Tolerance for safe operating stop exceeded" or after alarm 27001 "Defect
in a monitoring channel" or 2710x "Difference in function ..."..
The alarm can be reprogrammed in MD11412 ALARM_REACTION_CHAN_NOREADY (channel not ready).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
515
NC alarms
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Channel not ready.
Triggering of a "Deceleration on the current limit / OFF3 ramp" and activation of the timer for a switchover after STOP A (see
MD36956 $MA_SAFE_PULSE_DISABLE_DELAY).
Remedy:
Eliminate causes of alarm 27010 "Tolerance for safe standstill exceeded" or 27001 "Defect in a monitoring channel" or 2710x
"Difference in function ..." (see description of these alarms).
Programm
Switch control OFF - ON.
continuation:
27024
Axis %1 stop A triggered
Parameters:
%1 = Axis name, spindle number
Explanation:
This alarm follows an
- alarm 27011 "Safe velocity exceeded" (when configured as such in MD36961 $MA_SAFE_VELO_STOP_MODE, MD36963
$MA_SAFE_VELO_STOP_REACTION),
- alarm 27013 "Safe monitoring for acceleration exceeded",
- alarm 27023 "Stop B triggered",
- unsuccessful test stop.
The alarm can be reprogrammed in the MD11412 ALARM_REACTION_CHAN_NOREADY (channel not ready).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Channel not ready.
Trigger a "Pulse suppression".
Remedy:
Eliminate causes of
- alarm 27011 "Save velocity exceeded",
- alarm 27013 "Safe monitoring for acceleration exceeded",
- alarm 27023 "Stop B triggered",
- unsuccessful test stop
(see description of these alarms).
Programm
Switch control OFF - ON.
continuation:
27032
Axis %1 checksum error of safe monitoring. Confirmation and acceptance test required.
Parameters:
%1 = Axis name, spindle number
Explanation:
The relevant MDs for parameterization of the axis-specific safety functionality are protected by a checksum. The alarm
indicates that the current checksum no longer corresponds to the stored checksum, this means that an MD has either been
changed without authorization or is faulty.
In the setup phase (SPL setup mode active), instead of the axis-specific checksum single alarms (27032, 27035, and 27060),
the axis-specific group alarm 27132 is displayed. In MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL, the alarm display can
be reduced still further so that only one alarm is displayed for all axes (global group alarm 27135).
Alarms
516
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check MDs. Have the checksum recalculated. Re-accept safety functions (motion monitoring).
Programm
Switch control OFF - ON.
continuation:
27033
Axis %1 parameterisation of MD %2[%3] invalid, error code %4
Parameters:
%1 = Axis name, spindle number
%2 = MD name
%3 = MD array index for MD name
%4 = Error code, reference to the cause (see alarm description)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
517
NC alarms
Explanation:
The parameterization of the specified machine data is incorrect. An additional indication is the array index of the machine
data. If the machine data is a single machine data item, a zero is specified as the array index. This alarm occurs in accordance
with the displayed error code in the following connections:
1: Conversion of the specified MD to the internal calculation format causes an overflow.
2: Error in parameterization of the input/output assignments for the SGEs/SGAs.
3: One of the activated cam positions lies outside the actual value modulo range.
4: The function "actual value synchronization 2-encoder system" (slip) has been selected for a 1-encoder system.
5: The function "actual value synchronization 2-encoder system" (slip) has been selected at the same time as a function with
an absolute reference (SE/SN).
6: A safety function has been enabled in MD36901 $MA_SAFE_FUNCTION_ENABLE although the safety functions SBH/SG
have not been enabled.
7: An axis-specific SGE/SGA has been parameterized on the SPL interface (segment number = 4) and the function enable for
the external stops (MD36901 $MA_SAFE_FUNCTION_ENABLE, bit 6) is missing.
8: The cam synchronization has been activated via bit 7 in MD36901 $MA_SAFE_FUNCTION_ENABLE without enabling the
cams via bits 8...15.
12: A zero has been entered in MD36917 $MA_SAFE_ENC_GRID_POINT_DIST.
13: A zero has been entered in MD36918 $MA_SAFE_ENC_RESOL.
14: The parameterized cam modulo range MD36905 $MA_SAFE_MODULO_RANGE is not an integer multiple of 360
degrees.
15: An axis-specific SGE/SGA has been parameterized on the SPL interface (segment number = 4) and SGE "Deselection ext.
stop A" (assigned via MD36977 $MA_SAFE_EXT_STOP_INPUT[0]) has been parameterized inverted (bit 31 = 1) or SGE
"Deselection ext. stop A" has not been parameterized on the SPL interface $A_OUTSI.
16: MD10097 $MN_SAFE_SPL_STOP_MODE has been parameterized on value 4 (stop E) although the external stop E has
not been enabled on all axes with SI function enables (MD36901 $MA_SAFE_FUNCTION_ENABLE not equal to 0).
17: In MD36907 $MA_SAFE_DRIVE_PS_ADDRESS, an invalid value has been parameterized or the same address has been
assigned to multiple axes.
18: The internal preassignment of MD36919 $MA_SAFE_ENC_PULSE_SHIFT from the drive parameterization was not
possible because values would have to be set outside the permissible range. Adjust the encoder parameterization in the
drive.
19: MD36932 $MA_SAFE_VELO_OVR_FACTOR has been parameterized with decimal places.
20: The value entered in MD36934 $MA_SAFE_POS_LIMIT_PLUS and MD36935 $MA_SAFE_POS_LIMIT_MINUS have been
swapped. The upper limit is less than or equal to the lower limit.
21: In MD30300 $MA_IS_ROT_AX and MD36902 $MA_SAFE_IS_ROT_AX, various settings have been made.
22: The parameterized cam modulo range MD36905 $MA_SAFE_MODULO_RANGE and the modulo range in MD30330
$MA_MODULO_RANGE are not divisible by one another with an integer result.
-23: Testing of the brake mechanism was enabled without enabling safe operation for this axis in MD36901
$MA_SAFE_FUNCTION_ENABLE or enabling the link to the drive-autonomous safety functions in MD37950
$MA_SAFE_INFO_ENABLE. Testing of the brake mechanism is only permissible with safety functions in this axis.
24: MD36961 $MA_SAFE_VELO_STOP_MODE or MD36963 $MA_SAFE_VELO_STOP_REACTION has been parameterized
with an impermissible value.
25: Alarms 27000/F01797 are to be suppressed during parking (MD36965 $MA_SAFE_PARK_ALARM_SUPPRESS!=0). For
this, SGA "Axis safely referenced" must be parameterized in MD36987 $MA_SAFE_REFP_STATUS_OUTPUT.
26: The logical base address configured in Step 7 and addressed in MD36906 $MA_SAFE_CTRLOUT_MODULE_NR, MD10393
$MN_SAFE_DRIVE_LOGIC_ADDRESS do not match, or the slot addressed in this way has the wrong length.
27: Cam position MD36936 $MA_SAFE_CAM_POS_PLUS[n] or MD36937 $MA_SAFE_CAM_POS_MINUS[n] is
parameterized too near to the modulo limit.
28: In MD36901 $MA_SAFE_FUNCTION_ENABLE, "Safe cams" are enabled in bits 8...15, while in MD36903
$MA_SAFE_CAM_ENABLE the function "Safe cam track" is enabled.
29: Minus cam position MD36937 $MA_SAFE_CAM_POS_MINUS[n] is greater than the plus cam position MD36936
$MA_SAFE_CAM_POS_PLUS[n]. This is not allowed for the function "Safe cam track."
30: The distance between 2 cams on one cam track (MD36937 $MA_SAFE_CAM_POS_MINUS[n] and MD36936
$MA_SAFE_CAM_POS_PLUS[m]) is too small. ("Safe cam track" function)
31: The cam length, that is the distance between plus cam position (MD36936 $MA_SAFE_CAM_POS_PLUS[n]) and minus
cam position (MD36937 $MA_SAFE_CAM_POS_MINUS[n]), is too small.("Safe cam track" function)
32: For at least 2 cams enabled in MD36903 $MA_SAFE_CAM_ENABLE, identical values are entered in MD36938
$MA_SAFE_CAM_TRACK_ASSIGN[n]. ("Safe cam track" function)
Alarms
518
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
33: The value parameterized in MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[n] for a cam enabled in MD36903
$MA_SAFE_CAM_ENABLE is invalid. ("Safe cam track" function)
34: More than 15 cams have been assigned to one cam track in MD36938 $MA_SAFE_CAM_TRACK_ASSIGN[n]. ("Safe cam
track" function)
35: Cam modulo functionality has been selected in MD36905 $MA_SAFE_MODULO_RANGE, although this is not supported
for the "Safe cam track" function.
36: The parameterized monitoring cycle time MD10091 $MN_INFO_SAFETY_CYCLE_TIME does not match the monitoring
cycle time parameterized in the drive monitoring channel (p9500).
37: The velocity hysteresis n<nx in MD36947 $MA_SAFE_VELO_X_HYSTERESIS is greater than 3/4 of the velocity limit n<nx
in MD36946 $MA_SAFE_VELO_X.
38: The velocity hysteresis n<nx in MD36947 $MA_SAFE_VELO_X_HYSTERESIS is less than or equal to 0.
39: The velocity tolerance n<nx in MD36947 $MA_SAFE_VELO_X_HYSTERESIS is less than the slip tolerance in MD36949
$MA_SAFE_SLIP_VELO_TOL.
40: An axis-specific SGE/SGA addresses the SPL interface outside of the scope enabled by the relevant option.
41: The total encoder resolution (combination of coarse and fine resolution in MD36918 $MA_SAFE_ENC_RESOL and
MD36919 $MA_SAFE_ENC_PULSE_SHIFT) is invalid or exceeds the supported actual value format.
42: Simultaneous enable of NC-controlled brake test and drive-integrated brake test is not permitted.
43: For an axis with safety functions, no PROFIdrive drive has been parameterized in MD30100
$MA_CTRLOUT_SEGMENT_NR for the setpoint/actual value channel assignment. Enable SIC/SCC link (MD37950
$MA_SAFE_INFO_ENABLE) or reset the NC-controlled brake test enable (MD37000 $MA_FIXED_STOP_MODE).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check and change the specified MD. Allow the checksum to be recalculated. Re-accept safety functions.
Programm
Switch control OFF - ON.
continuation:
27034
Parameterization of MD %1[%2] invalid.
Parameters:
%1 = MD name
%2 = MD array index for MD name
Explanation:
The parameterization of the specified machine data is incorrect. This alarm occurs in the following contexts:
- An invalid value has been set for MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL.
- An invalid value has been set for MD13343 $MN_SAFE_RDP_CONNECTION_NR.
- An invalid value has been set for MD13333 $MN_SAFE_SDP_CONNECTION_NR.
- An invalid value has been set for MD13307 $MN_PROFISAFE_IPO_RESERVE.
- The logical basic addresses parameterized in MD13372 $MN_SAFE_PS_DRIVE_LOGIC_ADDR and enabled via MD37950
$MA_SAFE_INFO_ENABLE,bit1 exceed the maximum possible number of slots.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check and correct the specified machine data.
Programm
Switch control OFF - ON.
continuation:
27035
Axis %1 new hardware component, confirmation and functional test required.
Parameters:
%1 = Axis name, spindle number
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
519
NC alarms
Explanation:
The IDs for the corresponding hardware components (encoder, motor module) read out by the drive do not match the NCK
parameterization.
In the setup phase (SPL setup mode active), instead of the axis-specific checksum single alarms (27032, 27035, and 27060),
the axis-specific group alarm 27132 is displayed. In MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL, the alarm display can
be reduced still further so that only one alarm is displayed for all axes (global group alarm 27135).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
If the alarm occurs during setup, proceed as follows:
- Confirm the checksumMD36998 $MA_SAFE_ACT_CHECKSUM[1] (keyswitch position 3 or password has to be entered).
Resume setup.
If the alarm occurs after an encoder module or a DRIVE-CLiQ motor has been replaced, proceed as follows:
- In the Diagnostics operating area, confirm the hardware checksum in MD36998 $MA_SAFE_ACT_CHECKSUM[1] with the
softkey (keyswitch position 3 or password has to be entered).
- Readjust the actual value encoder.
- Check SI actual value acquisition: velocities, traversing direction, absolute position (set user agreement if necessary).
- Record the new checksum value in MD36998 $MA_SAFE_ACT_CHECKSUM[1] and the last entry in the change history in
MD36993 $MA_SAFE_CONFIG_CHANGE_DATE[0].
- Record the hardware and software version data for the new component.
Programm
Switch control OFF - ON.
continuation:
27036
Axis %1 encoder parameterization MD %2[%3] has been adjusted.
Parameters:
%1 = Axis name, spindle number
%2 = MD name
%3 = MD array index for MD name
Explanation:
Encoder parameterization of the encoder read out by the drive for the SI monitoring functions does not match NCK
parameterization in the displayed MD. The relevant NCK MD has been adjusted.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
In addition, a Stop F is triggered that may cause follow-up alarm 27001 with error code 0 as well as alarms 27023 and 27024.
Alarm 27001 with error code 0 can be avoided by alarm reduction (MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL higher
or equal to 1).
Remedy:
Continue with setup, correct checksum
Programm
Switch control OFF - ON.
continuation:
27037
Axis %1 and %2 with the same PROFIsafe address %3.
Parameters:
%1 = Axis name, spindle number
%2 = Axis name, spindle number
%3 = PROFIsafe address
Explanation:
The PROFIsafe addresses of these two axes read out by the drive are identical.
Alarms
520
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Set the correct PROFIsafe addresses of the drives.
Programm
Switch control OFF - ON.
continuation:
27038
Axis %1 value %2 in drive parameter %3 violates the limits of NCK MD %4.
Parameters:
%1 = Axis name, spindle number
%2 = Value in drive parameter
%3 = Drive parameter number, for example parameter 979.
%4 = NCK machine data name.
Explanation:
A SINAMICS drive delivers values in a parameter that violates the permissible value range for an NCK machine data or internal
limits. If several drive parameters are listed, there is a problem with the combination of these drive parameters. In this case,
the result of the link is displayed as the value.
The following causes are possible:
r469: Resolution of the absolute position for linear absolute encoders invalid or the ratio between the grid division and
measurement step not binary.
r470: Incorrect number of valid bits of the redundant coarse position value.
r471: Incorrect number of fine resolution bits of the redundant coarse position value.
r472: Incorrect number of relevant bits of the redundant coarse position value or 0".
r470/471/472: shift factor for coarse position bits in the finely resolved actual value result in an illegal value (parameter
values do not match).
r473: Invalid number of non safety-relevant measurement steps in the POS1 position value.
r474: A bit unknown to the NCK is set. At this location, the alarm output can be suppressed using MD10096
$MN_SAFE_DIAGNOSIS_MASK, bit 3 = 1.
r475: Incorrect number of the most significant bit of the redundant coarse position.
r979: Error in the encoder format according to PROFIdrive
r9527: Invalid encoder type
Reaction:
Alarm display.
Remedy:
Investigate as to why an incorrect value has been entered in the specified drive parameter(s) (e.g. for internal software errors
in the drive, refer to the drive documentation).
Programm
Switch control OFF - ON.
continuation:
27039
Axis %1 parameterization MD %2[%3] changed, confirmation and functional test required.
Parameters:
%1 = Axis name, spindle number
%2 = MD name
%3 = MD array index for MD name
Explanation:
The parameterization read out by the drive for the SI monitoring functions does not match the NCK parameterization in the
displayed MD. The relevant NCK MD has been adjusted.
The following relation exists between the NCK MDs and the drive parameters:
- MD36969 $MA_SAFE_BRAKETEST_TORQUE_NORM corresponds to p2003
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
521
NC alarms
Remedy:
Continue with setup, correct checksum.
- If MD36969 $MA_SAFE_BRAKETEST_TORQUE_NORM is displayed:
The change to p2003 must be taken into account in the parameterization of MD36969 $MA_SAFE_BRAKETEST_TORQUE.
The holding torque to be parameterized for the brake test must be reset.
MD36969 $MA_SAFE_BRAKETEST_TORQUE = desired test torque of the brake / p2003 * 100.
Then an acceptance test of the functioning of the brake test must be made.
Programm
Switch control OFF - ON.
continuation:
27040
Axis %1 waiting for motor module.
Parameters:
%1 = Axis name, spindle number
Explanation:
Alarm on ramp-up as long as the motor module is not yet ready for SI.
Communication to the motor module is not yet active on ramp-up, the safety functions are not yet available.
The alarm indication can be set in MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL so that only one alarm is displayed for
all axes.
Reaction:
Interface signals are set.
Alarm display.
Remedy:
The alarm will remain present during ramp-up if the drive does not communicate. Otherwise the alarm will only be displayed
briefly and then deleted automatically.
Possible causes for the continual presence of this alarm:
- The safe motion monitoring is only activated in MD36901 $MA_SAFE_FUNCTION_ENABLE, but not in the corresponding
parameter of the assigned drive (p9501).
- The axis -> drive assignment in MD36906 $MA_SAFE_CTRLOUT_MODULE_NR, MD10393
$MN_SAFE_DRIVE_LOGIC_ADDRESS or p0978 is incorrect.
- PROFIBUS connector has fallen out.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27050
Axis %1 SI communication failure.
Parameters:
%1 = Axis name, spindle number
Explanation:
Communication with the drive for Safety Integrated motion monitoring is additionally monitored.
This monitoring has found an error.
Reaction:
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
In addition, a STOP F is triggered that may cause follow-up alarm 27001 with error code 0 as well as alarms 27023 and
27024. Alarm 27001 with error code 0 can be avoided by alarm reduction(MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL
higher or equal to 1).
Remedy:
Check the connections between NCK and drive.
Check the configuration of the PROFIBUS telegram (e.g. SI slot configured).
Check the assignment of the NCK SI axis to the SI slot (MD36906 $MA_SAFE_CTRLOUT_MODULE_NR, MD10393
$MN_SAFE_DRIVE_LOGIC_ADDRESS).
Check for assignment of the telegram configuration for the slave OM
Check for compliance with the EMC requirements
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27060
Axis %1 Drive assignment checksum error. Confirmation and acceptance test required!
Parameters:
%1 = Axis name, spindle number
Alarms
522
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Explanation:
The axis-specific MDs $MA_SAFE_... and MD10393 $MN_SAFE_DRIVE_LOGIC_ADDRESS are protected by a checksum. The
alarm indicates that the current checksum no longer corresponds to the stored checksum, this means that an MD has either
been changed without authorization or is faulty.
In the setup phase (SPL setup mode active), instead of the axis-specific checksum single alarms (27032, 27035, and 27060),
the axis-specific group alarm 27132 is displayed. In MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL, the alarm display can
be reduced still further so that only one alarm is displayed for all axes (global group alarm 27135).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data, have the checksum recalculated and confirm. Re-accept the safety functions (connections NCK axis -
drive/encoder).
Programm
Switch control OFF - ON.
continuation:
27070
Checksum error parameterization SPL and SPL interfaces. Confirmation and acceptance test
required!
Explanation:
The NCK-MDs for parameterizing the SPL I/O and SPL functionality (including $MN_PROFISAFE..., MD133xx/134xx
$MN_SAFE_SDP/RDP...) are protected by a checksum. The alarm indicates that the current checksum no longer corresponds
to the stored checksum. This means that an MD has either been changed without authorization or is faulty.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data, have the checksum recalculated and confirm. Re-accept the safety functions (PROFIsafe, FSEND/
FRECV).
Programm
Switch control OFF - ON.
continuation:
27071
Checksum error safe PLC parameterization. Confirmation and acceptance test required!
Explanation:
The NCK MDs MD13312 $MN_SAFE_SPL_USER_DATA are protected by a checksum. The alarm indicates that the current
checksum no longer corresponds to the stored checksum, this means that an MD has either been changed without
authorization or is faulty.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data, have the checksum recalculated and confirm. Re-accept the safety functions
Programm
Switch control OFF - ON.
continuation:
27072
Checksum error enable safe communication. Confirmation and acceptance test required!
Explanation:
The NCK-MDs for enabling the SPL connection (including MD13302/13303 $MN_PROFISAFE_IN/OUT_ENABLE_MASK,
MD13330/13340 $MN_SAFE_RDP/SDP_ENABLE_MASK) are protected by a checksum. The alarm indicates that the current
checksum no longer corresponds to the stored checksum. This means that an MD has either been changed without
authorization or is faulty.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
523
NC alarms
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data, have the checksum recalculated and confirm. Re-accept the safety functions (PROFIsafe, FSEND/
FRECV).
Programm
Switch control OFF - ON.
continuation:
27073
Checksum error S7 PROFIsafe configuration. Confirmation and acceptance test required!
Explanation:
The F parameters required for PROFIsafe communication are protected by a checksum. The alarm indicates that the current
checksum no longer corresponds to the stored checksum, this means that an MD has either been changed without
authorization or is faulty.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the PROFIsafe configuration on the S7 side. Have the checksum recalculated. Re-accept safety functions (PROFIsafe
I/Os).
Programm
Switch control OFF - ON.
continuation:
27090
Error in data cross check NCK-PLC, %1[%2], NCK: %3; %4<ALSI>
Parameters:
%1 = Name of system variable in which the error was detected
%2 = System variable array index extension
%3 = NCK comparison value extension
%4 = Cross-check array index extension
Alarms
524
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Explanation:
Differences in the compared data have been found in a cyclic data cross-check between NCK and PLC. Parameter %1 indicates
the incorrect system variable ($A_INSI, $A_OUTSI, $A_INSE, $A_OUTSE, or $A_MARKERSI) with array index %2.
Special cases:
- Display "Error in NCK-PLC data cross-check, $MN_PREVENT_SYNACT_LOCK[0], ..." means that the SPL setup status has been
set differently in the NCK and PLC.
- Display "Error in NCK-PLC data cross-check, $MN_SAFE_SPL_STOP_MODE[0], ..." means that the SPL stop reaction (Stop D
or E) has been set differently in the NCK and PLC.
- Display "Error in NCK-PLC data cross-check, $MN_SAFE_SPL_USER_DATA[n], ..." means that different user data have been
set in NCK and PLC.
- Display "Error in NCK-PLC data cross-check, TIMEOUT[0], NCK: 0" means that the communication between NCK and PLC is
generally disturbed and that a data cross-check can no longer be performed.
- Display "Error in NCK-PLC data cross-check, $A_FSDP_ERR_REAC[n], $A_FRDP_SUBS[n], $A_FRDP_ERR_REAC[n]..." means
that different system variables have been specified in NCK and PLC.
With alarm parameter %4, a specific alarm message can be configured on the HMI for all listed system variables:
-
0: Error SPL commissioning status ($MN_PREVENT_SYNACT_LOCK[0,1] - DB18 DBX36.0)
-
0: Error SPL stop reaction ($MN_SAFE_SPL_STOP_MODE - DB18 DBX36.1).
-
0: Error SPL user data ($MN_SAFE_SPL_USER_DATA - DB18 DBD256,260,264,268)
-
0: Error FSENDDP error reaction ($A_FSDP_ERR_REAC[n] - DB18 DBW190, DBW210, DBW220, DBW448, DBW458 ...
DBW568)
-
0: Error FRECVDP error reaction ($A_FRDP_ERR_REAC[n] - DB18 DBW222, DBW234, DBW246, DBW580, DBW592 ...
DBW724)
-
0: Error FRECVDP replacement values ($A_FRDP_SUBS[n] - DB18 DBW220, DBW232, DBW244, DBW578, DBW590 ...
DBW722)
-
1
64: Error in system variable $A_INSE[1...64]
- 65...128: Error in system variable $A_OUTSE[1...64]
- 129...192: Error in system variable $A_INSI[1...64]
- 193...256: Error in system variable $A_OUTSI[1...64]
- 257...320: Error in system variable $A_MARKERSI[1...64]
- 321...448: Error in system variable $A_INSE[65...192]
- 449...576: Error in system variable $A_OUTSE[65...192]
- 577...704: Error in system variable $A_INSI[65...192]
- 705...832: Error in system variable $A_OUTSI[65...192]
- 833...960: Error in system variable $A_MARKERSI[65...192]
In order to parameterize alarm 27090, file ALSI_xx.com must be incorporated in the data management and declared in the
HMI with an entry in MBDDE.INI in section[IndexTextFiles] ALSI=f:\dh\mb.dir\alsi_. The machine manufacturer can redefine
this file to incorporate additional texts in the alarm that are useful for its system. If the file is redefined, the newly created
file must be declared in the system with an entry in MBDDE.INI.
The display of alarm 27090 can be modified via MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL: MD10094
$MN_SAFE_ALARM_SUPPRESS_LEVEL = 2 : Alarm 27090 will now only be displayed for the first data difference found.
Reaction:
Alarm display.
Trigger a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality, as soon as the
SPL setup phase (MD11500 $MN_PREVENT_SYNACT_LOCK[0,1] unequal to 0) is completed.
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 axis-specific SGEs to internal interface $A_OUTSI
- Incorrect assignment of the axis-specific 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 setup status set in NCK and PLC
- Different SPL stop reaction set in NCK and PLC
Programm
Clear alarm with the RESET key. Restart part program
continuation:
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
525
NC alarms
27091
Error in data cross check NCK-PLC, stop of %1
Parameters:
%1 = Extension indicating the monitoring channel that triggered the stop
Explanation:
The monitoring channel specified in the alarm text (NCK or PLC) has triggered a stop D or E (depending on the
parameterization in MD10097 $MN_SAFE_SPL_STOP_MODE). The alarm 27090 provides further information about the
cause of the stop D/E.
Reaction:
Alarm display.
Trigger a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality, as soon as the
SPL setup phase (MD11500 $MN_PREVENT_SYNACT_LOCK[0,1] unequal to 0) is completed.
Remedy:
Evaluate the alarm parameters of alarm 27090 and amend the SPL, or check the internal SPL interfaces to the safety
monitoring channels in the NCK and drive.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
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
Explanation:
The delay time (1s) for communication monitoring was exceeded in the monitoring channel specified in the alarm text (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).
Programm
Switch control OFF - ON.
continuation:
27093
Checksum error NCK-SPL, %1, %2, %3
Parameters:
%1 = Extension indicating the type of error
%2 = Extension indicating the reference variable
%3 = Extension indicating the actual variable
Explanation:
A checksum error has occurred in the NCK SPL. The file /_N_CST_DIR/_N_SAFE_SPF has subsequently been modified. The safe
programmable logic (SPL) in the NCK may have been corrupted.
Parameter %1 provides more information about the nature of the modification:
- FILE_LENGTH: The file length has changed.
- FILE_CONTENT: The file content has changed.
- FILE_PROTECTED: Exiting the SPL setup phase has restricted access rights to the file, and these have been violated.
The following information is also displayed in the the alarm text:
- the value calculated as reference (file length, checksum of file content) (%2)
- the actual cyclically calculated value (%3).
Reaction:
Alarm display.
Remedy:
Check the file and the time of the last modification to the file. Reload the original file and start the monitoring system again
with a PowerOn.
Programm
Switch control OFF - ON.
continuation:
27095
%1 SPL protection not activated
Parameters:
%1 = Name of the component on which the protection is not activated (NCK or PLC)
Explanation:
The protection features are not activated for the SPL. The setup phase of the SPL is not yet complete. No stop reaction (Stop
D or E) was initiated on an error in data cross-comparison between NCK and PLC.
Reaction:
Alarm display.
Remedy:
- Remedy for NCK: Activate the protection features with MD11500 $MN_PREVENT_SYNACT_LOCK[0,1]. The number range
of the synchronized action IDs used in the SPL must be entered in this MD.
- Remedy for PLC: Activate the protection features by setting the appropriate data bit in DB18.
Alarms
526
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27096
SPL start not allowed
Explanation:
To start the SPL in the protected state (MD11500 $MN_PREVENT_SYNACT_LOCK[0,1] not equal 0), the Safety Integrated
functionality must first be activated for at least one axis (via MD36901 $MA_SAFE_FUNCTION_ENABLE) and operated with
an active drive. Moreover, at least one SGE/SGA of this axis must have been parameterized for an SPL interface. If these
conditions are not met, it is only possible to operate SPL in the setup state.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Channel not ready.
Remedy:
Deactivation of the SPL protection in MD11500 $MN_PREVENT_SYNACT_LOCK[0,1]
or
- Setup of the axis-specific Safety Integrated functionality and
- Parameterization of at least one SGE/SGA for a SPL interface and
- Activation of the associated drive object
Programm
Switch control OFF - ON.
continuation:
27097
SPL start not executed
Explanation:
SPL start not executed after the time set in MD13310 $MN_SAFE_SPL_START_TIMEOUT elapsed.
This alarm can be masked with MD10096 $MN_SAFE_DIAGNOSIS_MASK, bit 1 = 1.
Reaction:
Alarm display.
Remedy:
Find the cause of the failure of the SPL to start. Possible causes may be:
- There is an NC or drive error (e.g. after encoder replacement, EMERGENCY STOP, PROFIsafe alarms)
- There is a syntax error in the SPL
- Safety Integrated alarm present (e.g. "Safe limit position overrun")
- Name or path of SPL for PROG_EVENT Start written incorrectly; make sure upper and lower cases are used correctly
- Simultaneous start of an ASUB and PROG_EVENT, parameterization MD 11602 $MN_ASUP_START_MASK (stop causes e.g.
read-in disable)
- Problems when calling FB4/FC9
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27098
SPL commissioning phase terminated
Explanation:
The SPL setup phase has just been terminated by changing MD11500 $MN_PREVENT_SYNACT_LOCK. After the next Power
ON, file /_N_CST_DIR/_N_SAFE_SPF is subject to the monitoring mechanisms defined for the SPL (access protection,
checksum calculation). Changes to the SPL can only be made in the unprotected mode.
Reaction:
Alarm display.
Remedy:
Perform a control Power ON. Check and document any changes to the logic in the SPL by means of an acceptance test.
Programm
Switch control OFF - ON.
continuation:
27099
Double assignment in SPL assignment MD %1[%2] - MD %3[%4]
Parameters:
%1 = MD name 1
%2 = MD array index for MD name 1
%3 = MD name 2
%4 = MD array index for MD name 2
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
527
NC alarms
Explanation:
Different applications have double assigned SPL inputs ($A_INSE) in the displayed machine data.
These could be:
- PROFIsafe communication
- F_DP communication
Possible machine data involved:
- MD10388 $MN_PROFISAFE_IN_ASSIGN
- MD13346 $MN_SAFE_RDP_ASSIGN
Reaction:
Alarm display.
Remedy:
Correct the stated MD.
Programm
Switch control OFF - ON.
continuation:
27100
At least one axis is not safely referenced
Explanation:
There are two reasons for this alarm:
- the machine position of at least one of the axes monitored with SI has not yet been acknowledged by the user, or
- the machine position of at least one of the axes monitored with SI has not yet been verified through follow-up referencing.
Even if the axis is already referenced, there is no confirmation that referencing has supplied the correct result. For example,
wrong results can occur if the axis was moved after the control was switched off, with the result that the standstill position
saved prior to switching off is no longer correct. To make sure that this does not happen, the user must acknowledge the
displayed actual position after the first referencing process.
When the user enable has first been set, follow-up referencing must be carried out each time the control is booted (with
absolute encoders, this follow-up referencing is executed automatically). This procedure is carried out to verify the standstill
position saved prior to switching off of the control.
Via the MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL (MD>=3), the alarm display can be set in such a way that an alarm
is given for each axis individually which has not been safely referenced.
Reaction:
Alarm display.
SGA "Axis safely referenced" is not set. SE will be switched off, if the actual safety position has not yet been confirmed by a
user agreement. If the user agreement has been set, SE will remain active. The safe cams are calculated and output.
However, their significance is limited as referencing has not been confirmed.
Remedy:
Move all SI axes to known positions and change to "Referencing" mode. Check the positions on the machine displayed in the
user confirmation field and set "User confirmation" via the selection/toggle key. If the user confirmation for the axes has
already been set, reference the axes again.
Changing the user confirmation will be possible only in key switch position 3 or after password entry
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27101
Axis %1 difference in function safe operational stop, NCK: %2 drive: %3
Parameters:
%1 = Axis name, spindle number
%2 = Monitoring status safe operating stop
%3 = Monitoring status safe operating stop
Explanation:
During cross-check of result list 1, a difference was found between the NCK and drive monitoring channels in the status of
safe operating stop monitoring.
Safe operating stop: Bit 0,1 in result list 1
Displayed monitoring status (NCK/drive (%2/%3)):
- OFF = Monitoring is inactive in this monitoring channel
- OK = Monitoring is active in this monitoring channel, limit values are not violated
- L+ = Monitoring is active in this monitoring channel, upper limit exceeded
- L- = Monitoring is active in this monitoring channel, lower limit exceeded
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Alarms
528
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Remedy:
Check whether the safe inputs have switched to the same status in both monitoring channels within the permissible time
tolerance.
For further diagnostics, the drive parameters r9710[0], r9710[1] and the servo trace signals "Result list 1 NCK" and "Result
list 1 drive" can be used.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27102
Axis %1 difference in function safe velocity %2, NCK: %3 drive: %4
Parameters:
%1 = Axis name, spindle number
%2 = SG level for which the difference was determined
%3 = Monitoring status safe velocity
%4 = Monitoring status safe velocity
Explanation:
During cross-check of result list 1, a difference was found between the NCK and drive monitoring channels in the status of
safe velocity monitoring.
- Safe velocity 1: Bit 6, 7 in result list 1
- Safe velocity 2: Bit 8, 9 in result list 1
- Safe velocity 3: Bit 10, 11 in result list 1
- Safe velocity 4: Bit 12, 13 in result list 1
Displayed monitoring status (NCK/drive (%3/%4)):
- OFF = Monitoring is inactive in this monitoring channel
- OK = Monitoring is active in this monitoring channel, limit values are not violated
- L+ = Monitoring is active in this monitoring channel, upper limit exceeded
- L- = Monitoring is active in this monitoring channel, lower limit exceeded
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Remedy:
Check whether the safe inputs have switched to the same status in both monitoring channels within the permissible time
tolerance.
For further diagnostics, the drive parameters r9710[0], r9710[1] and the servo trace signals "Result list 1 NCK" and "Result
list 1 drive" can be used.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27103
Axis %1 difference in function safe limit position %2, NCK: %3 drive: %4
Parameters:
%1 = Axis name, spindle number
%2 = Number of safe limit position
%3 = Monitoring status safe limit position
%4 = Monitoring status safe limit position
Explanation:
During cross-check of result list 1, a difference was found between the NCK and drive monitoring channels in the status of
safe limit position monitoring.
- Safe limit position 1: Bit 2, 3 in result list 1
- Safe limit position 2: Bit 4, 5 in result list 1
Displayed monitoring status (NCK/drive (%3/%4)):
- OFF = Monitoring is inactive in this monitoring channel
- OK = Monitoring is active in this monitoring channel, limit values are not violated
- L+ = Monitoring is active in this monitoring channel, upper limit exceeded
- L- = Monitoring is active in this monitoring channel, lower limit exceeded
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
529
NC alarms
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Remedy:
Check whether the safe inputs have switched to the same status in both monitoring channels within the permissible time
tolerance.
For further diagnostics, the drive parameters r9710[0], r9710[1] and the servo trace signals "Result list 1 NCK" and "Result
list 1 drive" can be used.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27104
Axis %1 difference in function safe cam plus %2, NCK: %3 drive: %4
Parameters:
%1 = Axis name, spindle number
%2 = Cam number
%3 = Monitoring status safe cam plus
%4 = Monitoring status safe cam plus
Alarms
530
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Explanation:
During cross-check of result list 2 ("Safe cams" function) and result list 3/4/5/6/7 ("Safe cam track" function), the status of
safe cam plus monitoring was found to be different in the NCK and drive monitoring channels.
The following applies to the "Safe cams" function:
- Safe cam 1+: bit 0, 1 in result list 2
- Safe cam 2+: bit 4, 5 in result list 2
- Safe cam 3+: bit 8, 9 in result list 2
- Safe cam 4+: bit 12,13 in result list 2
The following applies to the "Safe cam track" function: (each of the result lists 3-7 contains 6 cam results)
- Safe cam 1+: bit 0, 1 in result list 3
- Safe cam 2+: bit 4, 5 in result list 3
- Safe cam 3+: bit 8, 9 in result list 3
- Safe cam 4+: bit 12,13 in result list 3
- Safe cam 5+: bit 16,17 in result list 3
- Safe cam 6+: bit 20,21 in result list 3
- Safe cam 7+: bit 0, 1 in result list 4
- Safe cam 8+: bit 4, 5 in result list 4
- Safe cam 9+: bit 8, 9 in result list 4
- Safe cam 10+: bit 12,13 in result list 4
- Safe cam 11+: bit 16,17 in result list 4
- Safe cam 12+: bit 20,21 in result list 4
- Safe cam 13+: bit 0, 1 in result list 5
- Safe cam 14+: bit 4, 5 in result list 5
- Safe cam 15+: bit 8, 9 in result list 5
- Safe cam 16+: bit 12,13 in result list 5
- Safe cam 17+: bit 16,17 in result list 5
- Safe cam 18+: bit 20,21 in result list 5
- Safe cam 19+: bit 0, 1 in result list 6
- Safe cam 20+: bit 4, 5 in result list 6
- Safe cam 21+: bit 8, 9 in result list 6
- Safe cam 22+: bit 12,13 in result list 6
- Safe cam 23+: bit 16,17 in result list 6
- Safe cam 24+: bit 20,21 in result list 6
- Safe cam 25+: bit 0, 1 in result list 7
- Safe cam 26+: bit 4, 5 in result list 7
- Safe cam 27+: bit 8, 9 in result list 7
- Safe cam 28+: bit 12,13 in result list 7
- Safe cam 29+: bit 16,17 in result list 7
- Safe cam 30+: bit 20,21 in result list 7
Displayed monitoring status (NCK/drive (%3/%4)):
- OFF = Monitoring is inactive in this monitoring channel
- OK = Monitoring is active in this monitoring channel, limit values are not violated
- L+ = Monitoring is active in this monitoring channel, upper limit exceeded
- L- = Monitoring is active in this monitoring channel, lower limit exceeded
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Remedy:
Check whether the safe actual values are the same in both monitoring channels.
The drive parameters r9711[0,1] (diagnostics result list 2 [NCK, drive]) and r9735[0,1] / r9736[0,1] / r9737[0,1] /
r9738[0,1] / r9739[0,1] (diagnostics result list 3/4/5/6/7 [NCK, drive]) can be used for further diagnostics.
A diagnostics is also possible using the servo trace signals "Result list 2/3/4/5/6/7 NCK" and "Result list 2/3/4/5/6/7 drive".
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
531
NC alarms
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27105
Axis %1 difference in function safe cam minus %2, NCK: %3 drive: %4
Parameters:
%1 = Axis name, spindle number
%2 = Cam number
%3 = Monitoring status safe cam minus
%4 = Monitoring status safe cam minus
Explanation:
During cross-check of result list 2 ("Safe cams" function) and result list 3/4/5/6/7 ("Safe cam track" function), the status of
safe cam minus monitoring was found to be different in the NCK and drive monitoring channels.
The following applies to the "Safe cams" function:
- Safe cam 1-: bit 2, 3 in result list 2
- Safe cam 2-: bit 6, 7 in result list 2
- Safe cam 3-: bit 10, 11 in result list 2
- Safe cam 4-: bit 14, 15 in result list 2
The following applies to the "Safe cam track" function: (each of result lists 3-7 contains 6 cam results)
- Safe cam 1-: bit 2, 3 in result list 3
- Safe cam 2-: bit 6, 7 in result list 3
- Safe cam 3-: bit 10,11 in result list 3
- Safe cam 4-: bit 14,15 in result list 3
- Safe cam 5-: bit 18,19 in result list 3
- Safe cam 6-: bit 22,23 in result list 3
- Safe cam 7-: bit 2, 3 in result list 4
- Safe cam 8-: bit 6, 7 in result list 4
- Safe cam 9-: bit 10,11 in result list 4
- Safe cam 10-: bit 14,15 in result list 4
- Safe cam 11-: bit 18,19 in result list 4
- Safe cam 12-: bit 22,23 in result list 4
- Safe cam 13-: bit 2, 3 in result list 5
- Safe cam 14-: bit 6, 7 in result list 5
- Safe cam 15-: bit 10,11 in result list 5
- Safe cam 16-: bit 14,15 in result list 5
- Safe cam 17-: bit 18,19 in result list 5
- Safe cam 18-: bit 22,23 in result list 5
- Safe cam 19-: bit 2, 3 in result list 6
- Safe cam 20-: bit 6, 7 in result list 6
- Safe cam 21-: bit 10,11 in result list 6
- Safe cam 22-: bit 14,15 in result list 6
- Safe cam 23-: bit 18,19 in result list 6
- Safe cam 24-: bit 22,23 in result list 6
- Safe cam 25-: bit 2, 3 in result list 7
- Safe cam 26-: bit 6, 7 in result list 7
- Safe cam 27-: bit 10,11 in result list 7
- Safe cam 28-: bit 14,15 in result list 7
- Safe cam 29-: bit 18,19 in result list 7
- Safe cam 30-: bit 22,23 in result list 7
Displayed monitoring status (NCK/drive (%3/%4)):
- OFF = Monitoring is inactive in this monitoring channel
- OK = Monitoring is active in this monitoring channel, limit values are not violated
- L+ = Monitoring is active in this monitoring channel, upper limit exceeded
- L- = Monitoring is active in this monitoring channel, lower limit exceeded
Alarms
532
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Remedy:
Check whether the safe actual values are the same in both monitoring channels.
The drive parameters r9711[0,1] (diagnostics result list 2 [NCK, drive]) and r9735[0,1] / r9736[0,1] / r9737[0,1] /
r9738[0,1] / r9739[0,1] (diagnostics result list 3/4/5/6/7 [NCK, drive]) can be used for further diagnostics.
A diagnostics is also possible using the servo trace signals "Result list 2/3/4/5/6/7 NCK" and "Result list 2/3/4/5/6/7 drive".
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27106
Axis %1 difference in function safe velocity nx, NCK: %2 drive: %3
Parameters:
%1 = Axis name, spindle number
%2 = Monitoring status safe velocity nx
%3 = Monitoring status safe velocity nx
Explanation:
During cross-check of result list 2, a difference was found between the NCK and drive monitoring channels in the status of
safe velocity nx monitoring.
- Safe velocity nx+: Bit 16, 17 in result list 2
- Safe velocity nx-: Bit 18, 19 in result list 2
Displayed monitoring status (NCK/drive (%2/%3)):
- OFF = Monitoring is inactive in this monitoring channel
- OK = Monitoring is active in this monitoring channel, limit values are not violated
- L+ = Monitoring is active in this monitoring channel, upper limit exceeded
- L- = Monitoring is active in this monitoring channel, lower limit exceeded
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Remedy:
Check whether the safe actual values in both monitoring channels are the same.
For further diagnostics the drive parameters r9711[0,1] and the servo trace signals "Result list 2 NCK" and "Result list 2 drive"
can be used.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27107
Axis %1 difference in function cam modulo monitoring, NCK: %2 drive: %3
Parameters:
%1 = Axis name, spindle number
%2 = Monitoring status safe cam modulo range
%3 = Monitoring status safe cam modulo range
Explanation:
During cross-check of result list 2, a difference was found between the NCK and drive monitoring channels in the status of
cam modulo range monitoring.
Safe cam modulo range: Bit 20, 21 in result list 2
Displayed monitoring status (NCK/drive (%2/%3)):
- OFF = Monitoring is inactive in this monitoring channel
- OK = Monitoring is active in this monitoring channel, limit values are not violated
- L+ = Monitoring is active in this monitoring channel, upper limit exceeded
- L- = Monitoring is active in this monitoring channel, lower limit exceeded
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
533
NC alarms
Reaction:
NC Start disable in this channel.
Alarm display.
A Stop F was triggered.
If safe monitoring was active, STOP B was also triggered automatically. In this case, a power OFF/ON of the control will be
required.
Remedy:
Check whether the safe actual values in both monitoring channels are the same.
For further diagnostics the drive parameters r9711[0,1] and the servo trace signals "Result list 2 NCK" and "Result list 2 drive"
can be used.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27110
Axis %1 fault during data transmission index %2.
Parameters:
%1 = Axis name, spindle number
%2 = Index in data cross-check.
Explanation:
Faulty communication between NCK and drive caused that data cross-check of data and indicated index could not be
executed three times in a row.
Reaction:
Alarm display.
In addition, a Stop F is triggered that may cause follow-up alarm 27001 with error code 0 as well as alarms 27023 and 27024.
Alarm 27001 with error code 0 can be avoided by alarm reduction (MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL higher
or equal to 1).
Remedy:
Check the connections between NCK and drive
Check the configuration of the PROFIBUS telegram (e.g. SI slot configured)
Check the assignment NCK-SI axis to SI slot (MD36906 $MA_SAFE_CTRLOUT_MODULE_NR, MD10393
$MN_SAFE_DRIVE_LOGIC_ADDRESS)
Check the assignment of the telegram configuration for the slave OM
Verify compliance with the EMC guidelines
Replace the hardware.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27111
Axis %1 fault during encoder evaluation of the safe actual value.
Parameters:
%1 = Axis name, spindle number
Explanation:
The redundantly determined safe actual value does not match the fine resolution actual value of the same encoder.
Reaction:
Alarm display.
In addition, a Stop F is triggered that may cause follow-up alarm 27001 with error code 0 as well as alarms 27023 and 27024.
Alarm 27001 with error code 0 can be avoided by alarm reduction (MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL higher
or equal to 1).
Remedy:
Check encoder mounting
Check encoder parameterization
Check the NCK-MDs MD36916 $MA_SAFE_ENC_IS_LINEAR, MD36917 $MA_SAFE_ENC_GRID_POINT_DIST, MD36918
$MA_SAFE_ENC_RESOL, and the drive parameter field r0979
With the DRIVE-CLiQ encoder, additionally check the NCK-MDs MD36924 $MA_SAFE_ENC_NUM_BITS, MD36929
$MA_SAFE_ENC_CONF, and drive parameter r047x
With the DRIVE-CLiQ linear encoder, additionally check the NCK-MDs MD36909 $MA_SAFE_ENC_MEAS_STEPS_RESOL,
MD36913 $MA_SAFE_ENC_MEAS_STEPS_POS1, and drive parameter r0469/r0473
Verify compliance with the EMC guidelines
Replace the hardware
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27112
Axis %1 CRC error of the safe actual value.
Parameters:
%1 = Axis name, spindle number
Alarms
534
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Explanation:
An error has been detected on verifying data consistency of the safe actual value (CRC).
Possible causes for the persistence of the alarm:
- The NCK monitoring channel for safe motion monitoring is not communicating with the monitoring channel of the
assigned drive, but with that of another axis.
- Error in the encoder parameterization
- Incorrect encoder evaluation type
- Faults in communication between NCK and drive
Reaction:
Alarm display.
In addition, a Stop F is triggered that may cause follow-up alarm 27001 with error code 0 as well as alarms 27023 and 27024.
Alarm 27001 with error code 0 can be avoided by alarm reduction (MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL higher
or equal to 1).
Remedy:
Check the correctness of the assignment of the drive in the hardware configuration, MD36906
$MA_SAFE_CTRLOUT_MODULE_NR, MD10393 $MN_SAFE_DRIVE_LOGIC_ADDRESS, and p0978.
Check encoder mounting
Check encoder parameterization
Check the NCK-MDs MD36916 $MA_SAFE_ENC_IS_LINEAR, MD36917 $MA_SAFE_ENC_GRID_POINT_DIST, MD36918
$MA_SAFE_ENC_RESOL, and the drive parameter field r0979
With the DRIVE-CLiQ encoder, additionally check the NCK-MDs MD36924 $MA_SAFE_ENC_NUM_BITS, MD36929
$MA_SAFE_ENC_CONF, and the drive parameter r047x
With the DRIVE-CLiQ linear encoder, additionally check the NCK-MDs MD36909 $MA_SAFE_ENC_MEAS_STEPS_RESOL,
MD36913 $MA_SAFE_ENC_MEAS_STEPS_POS1 and drive parameters r0469/r0473
Check whether the encoder evaluation has been replaced (SMI, SMC, SME)
Check whether the encoder evaluation type has been replaced (SMx, DRIVE-CLiQ encoder)
Check the encoder identifier in MD36928 $MA_SAFE_ENC_IDENT
Verify compliance with the EMC guidelines.
Replace the hardware.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27113
Axis %1 hardware encoder error of the safe actual value.
Parameters:
%1 = Axis name, spindle number
Explanation:
Encoder evaluation outputs a hardware fault.
The following reasons are possible:
- Dirt in the optical encoder evaluation
- Signal transfer problems
- Missing encoder serial number after replacing an encoder (concerns encoders with serial number, built-in motors, or third-
party motors)
Reaction:
Alarm display.
In addition, a Stop F is triggered that may cause follow-up alarm 27001 with error code 0 as well as alarms 27023 and 27024.
Alarm 27001 with error code 0 can be avoided by alarm reduction (MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL higher
or equal to 1).
Remedy:
After adjusting the encoder, initiate transfer of the serial number (applies to absolute encoders only)
Verify compliance with the EMC guidelines
Replace the encoder hardware
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27124
Stop A triggered at least in 1 axis
Explanation:
This is an informational alarm indicating that Stop A has been triggered in at least 1 axis and Power On is required for alarm
acknowledgment.
This alarm occurs if the alarm priority function was activated in MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
535
NC alarms
Reaction:
Interface signals are set.
Alarm display.
Trigger a "Pulse suppression" for the affected axis.
Remedy:
Find the error cause by means of further alarm messages.
Programm
Switch control OFF - ON.
continuation:
27132
Axis %1 checksum group error safe monitors. Confirmation and acceptance test required!
Parameters:
%1 = Axis name, spindle number
Explanation:
The relevant MDs for parameterizing the axis-specific safety functionality are protected by a checksum. The alarm indicates
that at least one axis-specific checksum no longer matches the stored checksum, which means that an item of data has
either been changed without authorization or is defective.
This alarm is displayed during the setup phase (SPL setup mode active) as an axis-specific group alarm for checksum alarms
27032, 27035, and 27060. In MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL, the alarm display can be reduced still
further so that only one alarm is displayed for all axes (global group alarm 27135).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check MDs. Have checksums recalculated. Check hardware components and drive assignments, repeat acceptance of safety
functions (motion monitors).
Programm
Switch control OFF - ON.
continuation:
27135
Checksum group error safe monitors on at least one axis. Confirmation and acceptance test
required!
Explanation:
The relevant MDs for parameterizing the axis-specific safety functionality are protected by a checksum. The alarm indicates
that on at least one axis at least one axis-specific checksum no longer matches the stored checksum, which means that an
item of data has either been changed without authorization or is defective.
This alarm is displayed during the setup phase (SPL setup mode active) as a global group alarm for the axis-specific checksum
alarm 27132. This alarm reduction is parameterized in MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL (100s digit set).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check MDs. Have checksums recalculated and confirm. Check hardware components and drive assignments, repeat
acceptance of safety functions (motion monitors).
Programm
Switch control OFF - ON.
continuation:
Alarms
536
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
27140
Waiting for motor module of at least one axis.
Explanation:
Alarm during startup as long as the motor module of at least one axis is not yet ready for SI.
Communication with the motor module during startup has not yet been activated; the safety functions of at least one axis
are not yet available.
In MD10094 $MN_SAFE_ALARM_SUPPRESS_LEVEL (MD<3), the alarm display can be set to display for each axis individually
whether communication has been activated.
The alarm persistently occurs during startup if at least one drive is not communicating. Otherwise, the alarm only briefly
appears and is cleared automatically.
Possible causes of the persistent occurrence of the alarm:
- The safe motion monitoring functions are only activated in MD36901 $MA_SAFE_FUNCTION_ENABLE, but not in the
corresponding parameter of the associated drive (p9501).
- The assignment axis -> drive in MD36906 $MA_SAFE_CTRLOUT_MODULE_NR, MD10393
$MN_SAFE_DRIVE_LOGIC_ADDRESS or p0978 is incorrect.
- PROFIBUS connector fallen out.
Reaction:
Interface signals are set.
Alarm display.
Remedy:
Check the correctness of parameter p9501 or the assignment of the drives in MD36906 $MA_SAFE_CTRLOUT_MODULE_NR,
MD 10393 $MN_SAFE_DRIVE_LOGIC_ADDRESS, p0978.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27200
PROFIsafe: cycle time %1 [ms] too long
Parameters:
%1 = Parameterized cycle time
Explanation:
The PROFIsafe communication cycle time resulting from MD10098 $MN_PROFISAFE_IPO_TIME_RATIO and MD10071
$MN_IPO_CYCLE_TIME exceeds the permissible limit value (25 ms).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Adapt cycle time via MD10098 $MN_PROFISAFE_IPO_TIME_RATIO or correct the reduction of the IPO cycle.
Programm
Switch control OFF - ON.
continuation:
27201
PROFIsafe: MD %1[%2]: bus segment %3 error
Parameters:
%1 = MD name
%2 = MD array index
%3 = Parameterized bus segment
Explanation:
An incorrect bus segment was entered in the specified machine data. The value must be 5.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct specified MD.
Programm
Switch control OFF - ON.
continuation:
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
537
NC alarms
27202
PROFIsafe: MD %1[%2]: address %3 error
Parameters:
%1 = MD name
%2 = MD array index
%3 = Parameterized PROFIsafe address
Explanation:
The PROFIsafe address parameterized in the stated MD is incorrect. The value must be greater than 0.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct specified MD.
Programm
Switch control OFF - ON.
continuation:
27203
PROFIsafe: MD %1[%2]: SPL assignment error
Parameters:
%1 = MD name
%2 = MD array index
Explanation:
The SPL interface in the displayed MD is incorrect. Possible causes:
- Bit values greater than those defined for the SPL interface (bit value > maximum bit value)
- Number of bits greater than number of bits per slot (upper bit value - lower bit value > 32)
- Number of bits too large for this PROFIsafe module (upper bit value - lower bit value + 1 > 8)
- No SPL assignment parameterized (both bit values equal to zero)
- Incorrect SPL assignment (bit value equal to zero)
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct specified MD.
Programm
Switch control OFF - ON.
continuation:
27204
PROFIsafe: double assignment MD %1[%2] - MD %3[%4]
Parameters:
%1 = MD name 1
%2 = MD array index for MD name 1
%3 = MD name 2
%4 = MD array index for MD name 2
Explanation:
A duplicate assignment has been parameterized illegally in the specified machine data:
Multiple inputs of PROFIsafe modules parameterized on the same $A_INSE. MDs affected:
- MD10388 $MN_PROFISAFE_IN_ASSIGN
Multiple $A_OUTSE parameterized on the same output of a PROFIsafe module. MDs affected:
- MD13301 $MN_PROFISAFE_OUT_FILTER
Multiple substitute values of passive SPL connections parameterized on the same $A_INSE. MDs affected:
- MD10388 $MN_PROFISAFE_IN_ASSIGN
Alarms
538
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct the stated MD.
Programm
Switch control OFF - ON.
continuation:
27205
PROFIsafe: number of signals in MD %1 [%2] <> MD %3[%4]
Parameters:
%1 = MD name 1
%2 = MD array index for MD name 1
%3 = MD name 2
%4 = MD array index for MD name 2
Explanation:
The parameterized number or the signals used must be the same in both machine data.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct the stated MD.
Programm
Switch control OFF - ON.
continuation:
27206
PROFIsafe: MD %1[%2] maximum number of F user data (%3 bits) exceeded.
Parameters:
%1 = MD name
%2 = MD array index for MD name
%3 = Maximum F user data bits.
Explanation:
The parameterized data indicated in the machine data are outside the F user data range of the F module.
Note
When machine data MD10386/10387 $MN_PROFISAFE_IN/OUT_ADDRESS is displayed, the sub slot address parameterized
in it will exceed the F user data range of the F module.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct specified MD.
Programm
Switch control OFF - ON.
continuation:
27207
PROFIsafe: MD %1[%2] max. sub slot number: %3 exceeded
Parameters:
%1 = MD name
%2 = MD array index for MD name
%3 = Max. number of sub slots
Explanation:
The sub slot parameterized in the indicated machine data exceeds the max. permissible number of sub slots per PROFIsafe
module.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
539
NC alarms
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Reduce the number of sub slots by changing the splitting of F user data of the PROFIsafe module.
Programm
Switch control OFF - ON.
continuation:
27208
PROFIsafe: MD %1[%2]: max. sub-slot address %3 exceeded.
Parameters:
%1 = MD name
%2 = MD array index
%3 = Maximum sub-slot address.
Explanation:
A sub-slot address was entered in the MD that is too high. The entered value must not exceed the displayed maximum sub-
slot address.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct specified MD.
Programm
Switch control OFF - ON.
continuation:
27220
PROFIsafe: Number of NCK F modules (%1) <> Number of S7 F modules (%2)
Parameters:
%1 = Number of parameterized NCK F modules
%2 = Number of parameterized S7 F modules
Explanation:
The number of F modules parameterized via the NCK machine data MD10386/10387 $MN_PROFISAFE_IN/OUT_ADDRESS
is:
- Greater than the number of PROFIBUS slaves in the S7 PROFIBUS configuration
- Smaller than the number of F modules in the S7 PROFIBUS configuration
- Greater than the number of F modules in the S7 PROFIBUS configuration
If the specified number of S7-F modules = 0, none of the configured F modules configured in the S7 PROFIBUS configuration
were found.
In most cases, the reason for this alarm is an error in the parameterization of the PROFIsafe master address.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the F parameterization in MD10386/10387 $MN_PROFISAFE_IN/OUT_ADDRESS.
Check the F configuration in the S7 PROFIBUS configuration.
Check the parameterized PROFIsafe master address in MD10385 $MN_PROFISAFE_MASTER_ADDRESS and in the S7
PROFIBUS configuration.
Programm
Switch control OFF - ON.
continuation:
Alarms
540
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
27221
PROFIsafe: NCK F module MD %1[%2] unknown
Parameters:
%1 = MD name
%2 = MD array index
Explanation:
The F module parameterized in the specified machine data is unknown under this PROFIsafe address in the S7 PROFIBUS
configuration.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the PROFIsafe addresses in the NCK MD and S7 PROFIBUS configuration.
Programm
Switch control OFF - ON.
continuation:
27222
PROFIsafe: S7 F module PROFIsafe address %1 unknown
Parameters:
%1 = PROFIsafe address
Explanation:
The F module with the specified PROFIsafe address has not been parameterized as an F module in the NCK MD.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the S7 PROFIBUS configuration. Enter the module in the NCK MD.
Programm
Switch control OFF - ON.
continuation:
27223
PROFIsafe: NCK F module MD %1[%2] is not a %3 module
Parameters:
%1 = MD name
%2 = MD array index
%3 = Module type
Explanation:
The F module parameterized in the specified NCK MD has not been entered as an input/output module in the S7 PROFIBUS
configuration.
Displayed incorrect module type (%3):
- INPUT: NCK F parameterization expects INPUT module
- OUTPUT: NCK F parameterization expects OUTPUT module
- IN/OUT: NCK F parameterization expects INPUT or OUTPUT module
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the module in the S7 PROFIBUS configuration.
Programm
Switch control OFF - ON.
continuation:
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
541
NC alarms
27224
PROFIsafe: F module MD %1[%2] - MD %3[%4]: double assignment of PROFIsafe address
Parameters:
%1 = MD name 1
%2 = MD array index 1
%3 = MD name 2
%4 = MD array index 2
Explanation:
In the NCK MD or in the S7 F parameters, the same PROFIsafe address has been parameterized for the F modules
parameterized in the specified machine data. Therefore, no clear communication link is possible between F master and F
slave.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check and correct the S7 F parameterization and NCK MD.
Programm
Switch control OFF - ON.
continuation:
27225
PROFIsafe: slave %1, configuration error %2
Parameters:
%1 = PROFIBUS slave address
%2 = Configuration error
Explanation:
An error occurred during evaluation of the S7 PROFIBUS configuration for the specified slave. This configuration error is
further specified in alarm parameter %2:
- PRM header: The PRM telegram for this slave could not be interpreted unequivocally.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check and correct the S7 PROFIBUS configuration.
Programm
Switch control OFF - ON.
continuation:
27240
PROFIsafe: PLC not running up, info: %1
Parameters:
%1 = Current information from the PROFIsafe ramp-up NCK-PLC
Explanation:
No PROFIsafe configuration is available to the NCK after the time set in MD10120 $MN_PLC_RUNNINGUP_TIMEOUT.
The current status of the PROFIsafe startup NCK PLC is displayed in the alarm text.
- 0 = Configuration not available; interface with the NCK is not supported by FB15.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
- Increase MD10120 $MN_PLC_RUNNINGUP_TIMEOUT
- Check the PLC operating status.
- Check the PLC operating system software version.
- Delete the F parameterization in the NCK MD.
Programm
Switch control OFF - ON.
continuation:
Alarms
542
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
27241
PROFIsafe: different version, NCK: %1, PLC: %2, (%3)
Parameters:
%1 = Interface version of the NCK
%2 = Interface version of the PLC
%3 = Internal identifier of interface
Explanation:
The NCK and PLC components have different implementations of a required interface. The F communication cannot be
initialized.
The alarm text contains the following information:
- version of the interface on the NCK side (%1)
- version of the interface on the PLC side (%2)
- internal identifier of the interface (%3)
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
- Check the PLC operating system and NCK software versions.
- Upgrade the PLC operating system.
- Delete the NCK F parameterization.
Programm
Switch control OFF - ON.
continuation:
27242
PROFIsafe: F module %1, %2 faulty; error code %3, %4
Parameters:
%1 = PROFIsafe address
%2 = Incorrect F parameter
%3 = Error information
%4 = Error information
Explanation:
An error was detected during the evaluation of the F parameters.
%2 = CRC1: CRC specified by F parameters faulty.
%2 = F_WD_Timeout: The monitoring time parameterized in Step 7 is too short for the PROFIsafe cycle time set in MD
$MN_PROFISAFE_IPO_TIME_RATIO.
%2 = F_Data_Len: The defined length of the message frame is incorrect.
%2 = F_CRC_Seed: The parameterized type of CRC calculation is not supported.
%2 = CRC2_Len: The length of the CRC message frame is incorrect.
%2 = PS_Version: Error in parameterized PROFIsafe profile version
%2 = Param: Error in internal parameter structure
%2 = Unknown(x): Error code of PLC
%3 = Further information about the incorrect parameters
%4 = Further information about the incorrect parameters
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
543
NC alarms
Remedy:
Depending on the cause of error stated in alarm parameter %2, the following remedy is necessary:
%2 = CRC1: PLC overall reset, reload the S7 F configuration.
%2 = F_WD_Timeout: Reparameterize the PROFIsafe cycle time or F monitoring time.
%2 = F_Data_Len: Change configuration of the module. Reload the S7 F configuration.
%2 = F_CRC_Seed: Change configuration of the module. Reload the S7 F configuration.
%2 = CRC2_Len: Change configuration of the module. Reload the S7 F configuration.
%2 = PS_Version: Change configuration of the module. Reload the S7 F configuration.
%2 = Param: PLC overall reset, reload the S7 F configuration.
%2 = Unknown: PLC overall reset, reload the S7 F configuration.
Programm
Switch control OFF - ON.
continuation:
27250
PROFIsafe: configuration in DP M changed; error code %1 - %2
Parameters:
%1 = NCK project number
%2 = Current PLC project number
Explanation:
The DP master shows a modified S7 PROFIBUS configuration. Error-free operation can no longer be guaranteed.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Communication with F slaves is finished.
A STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) is triggered on all axes with safety functionality.
Remedy:
Restart the PLC/NCK.
Programm
Switch control OFF - ON.
continuation:
27251
PROFIsafe: F module %1, %2 reports error %3
Parameters:
%1 = PROFIsafe address or name
%2 = Reporting component (master/slave)
%3 = Error code
Explanation:
Communication is faulty between the F master and the stated F module.
In %2, the component is indicated that revealed the error:
- Master: Error was revealed in the F master.
- Slave : Error was revealed in the F slave.
If the alarm was revealed in the "F slave," the following error codes (%3) are possible:
- CN: An error was revealed in the telegram sequence
- CRC: A CRC error was revealed
- TO: The parameterized commmunication timeout was exceeded or the PROFIsafe address was set incorrectly
- LBF: Communication error, telegram mirroring
If the alarm was revealed in the "F master," the following error identifiers (%3) are possible:
- CN: An error was revealed in the telegram sequence
- CRC: A CRC error was revealed
- TO: The parameterized communication timeout was exceeded
- EA: F slave transmits empty telegrams
- TF: Timer overflow
All the error codes stated can be displayed combined, depending on the fault profile.
Alarms
544
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
Mode group not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Triggering of a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality. Failsafe
values are activated for the stated module.
Remedy:
Check the I/O bus. Restart F slave modules. Restart the NCK/PLC.
Check the parameterized logical basic addresses (note direct and indirect addressing) for other uses in other parts of the PLC
configuration.
Other possibilities for diagnostics:
- Prevent execution of the user program
- General reset of PLC and load basic program from the toolbox
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27252
PROFIsafe: slave/device %1, bus %2, sign-of-life error
Parameters:
%1 = Slave/device identifier
%2 = Bus to which the slave/device is connected.
Explanation:
The specified DP slave or the PN device no longer communicates with the master/controller.
Reaction:
Mode group not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Triggering of a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Stop of the PROFIsafe drivers affected. Stopped PROFIsafe driver of F modules of type F-DI or F-DIO output failsafe values (0)
toward the SPL as F useful data.
Remedy:
Check the DP/PN wiring. Restart F modules. Restart the NCK/PLC.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27253
PROFIsafe: communication fault F master component %1, error %2
Parameters:
%1 = Error component
%2 = Error code
Explanation:
The F master signals that communication between the NCK and PLC is no longer working.
In %1, the incorrect component is stated:
- PLC: The PLC no longer executes the OB40 request.
- PLC-DPM: DP master is no longer in OPERATE status.
The error code stated in %2 provides further information about the cause:
- 1,2,4: PLC processing of the OB40 not finished.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Triggering of a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Stop of the PROFIsafe drivers affected. Stopped PROFIsafe driver of F modules of type F-DI or F-DIO output failsafe values (0)
toward the SPL as F useful data.
Remedy:
Extend the PROFIsafe cycle time via MD10098 $MN_PROFISAFE_IPO_TIME_RATIO.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
545
NC alarms
Programm
Switch control OFF - ON.
continuation:
27254
PROFIsafe: F module %1, error on channel %2; %3<ALSI>
Parameters:
%1 = PROFIsafe address or name
%2 = Channel type, channel number
%3 = System variable array index extension
Explanation:
The F module signals that an error occurred in the interface of the specified channel.
This alarm is only triggered for ET200S F modules.
The channel type (input or output channel) is indicated by the abbreviations IN and OUT in %2.
A specific alarm message can be programmed for each of the system variables on the HMI via parameter %3:
-
1
64: Error in system variables $A_INSE[1...64]
- 65...128: Error in system variables $A_OUTSE[1...64]
- 321...448: Error in system variables $A_INSE[65...192]
- 449...576: Error in system variables $A_OUTSE[65...192]
-
-1: Error in an input or output channel for which there is no SPL assignment
Reaction:
Mode group not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Trigger a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Remedy:
Check wiring. Wiring OK: replace F module.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27255
PROFIsafe: F module %1, general error
Parameters:
%1 = PROFIsafe address or name
Explanation:
The specified PROFIsafe module signals an error. A more exact specification of the error's cause cannot be made without
further assistance.
This alarm is triggered for all types of PROFIsafe slaves.
Reaction:
Mode group not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Trigger a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Remedy:
Check wiring.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27256
PROFIsafe: Current cycle time %1 [ms]> parameterized cycle time
Parameters:
%1 = Current PROFIsafe communication cycle time
Explanation:
The current PROFIsafe communication cycle time is greater than the value set via MD10098
$MN_PROFISAFE_IPO_TIME_RATIO. The parameterized PROFIsafe communication cycle time is continually exceeded on the
PLC side.
Alarms
546
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
Mode group not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Trigger a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Remedy:
Adapt cycle time via MD10098 $MN_PROFISAFE_IPO_TIME_RATIO.
At least the value displayed in the alarm text must be set.
The set cycle time affects the runtime load of the PLC module. This also has to be taken into consideration when making the
setting.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27257
PROFIsafe: %1 %2 reports system error %3 (%4)
Parameters:
%1 = Type of communication
%2 = PROFIsafe address or name of the F module
%3 = Error code
%4 = Component
Explanation:
A system error has been detected in the PROFIsafe communication. Depending on the error, the relevant PROFIsafe driver
or the entire PROFIsafe communication will be stopped.
For the communication type (%1), the following displays are possible:
- F module
- SPL
One of the following F components (%2) may be affected:
- PROFIsafe address or name of the affected F module (with communication type = F module)
- "-" (with communication type SPL)
One of the following error causes is possible (see error code %3):
- SF: Asynchronous error state (StateFault)
- SP: No update of the SPL input/output data (SPL I/O communications)
The error codes stated may also be displayed combined, depending on the fault profile.
One of the following components (%4) may be affected:
- NCK
- PLC
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) triggered on all axes with safety functionality.
Stop of the affected PROFIsafe drivers. Stopped PROFIsafe drivers of F modules of type F-DI or F-DIO output failsafe values
(0) as F user data to the SPL.
Remedy:
Power OFF/ON of the control. If the error occurs again, inform the service department.
Programm
Switch control OFF - ON.
continuation:
27299
PROFIsafe: Diagnostics %1 %2 %3 %4
Parameters:
%1 = Error code 1
%2 = Error code 2
%3 = Error code 3
%4 = Error code 4
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
547
NC alarms
Explanation:
Error in PROFIsafe configuration.
The alarm text states the component (PLC or NCK) that detected the error.
Reaction:
Alarm display.
Remedy:
If you experience such a system error, please contact Technical Support.
Please supply the following information to ensure quick processing:
- Alarm number together with alarm text
- Description of the operation/mode before the alarm message
- Generate log files using the key combination: <Ctrl> + <Alt> + <D>
Programm
Clear alarm with the Delete key or NC START.
continuation:
27300
F_DP: Cycle time %1 [ms] is too long
Parameters:
%1 = Parameterized cycle time
Explanation:
The F_DP communication cycle time resulting from MD13320 $MN_SAFE_SRDP_IPO_TIME_RATIO and MD10071
$MN_IPO_CYCLE_TIME exceeds the permissible limit value of 250ms.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct cycle time via MD13320 $MN_SAFE_SRDP_IPO_TIME_RATIO and/or MD10071 $MN_IPO_CYCLE_TIME
Programm
Switch control OFF - ON.
continuation:
27301
F_DP: MD %1[%2]: SPL interface faulty
Parameters:
%1 = MD name
%2 = MD array index
Explanation:
The SPL interface in the displayed MD is incorrect: Possible causes:
- Bit values greater than those defined for the SPL interface (bit value > maximum bit value)
- Number of bits too large (upper bit value - lower bit value > 16)
- No SPL assignment parameterized (both bit values equal to zero)
- Incorrect SPL assignment (bit value equals zero)
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct specified MD.
Programm
Switch control OFF - ON.
continuation:
27302
F_DP: Double assignment MD %1[%2] - MD %3[%4]
Parameters:
%1 = MD name 1
%2 = MD array index for MD name 1
%3 = MD name 2
%4 = MD array index for MD name 2
Alarms
548
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Explanation:
An invalid double assignment has been parameterized in the stated MD:
SPL inputs ($A_INSE) are multiply occupied by F_DP communication. Relevant MD:
- MD13346 $MN_SAFE_RDP_ASSIGN:
F user data of an F_SENDDP are multiply occupied by sub-slots. Relevant MD:
- MD13337 $MN_SAFE_SDP_FILTER
Logical base addresses are multiply occupied by different SPL connections. Relevant MD:
- MD13334 $MN_SAFE_SDP_LADDR, MD13344 $MN_SAFE_RDP_LADDR
Connection numbers are multiply occupied by different SPL connections. Relevant MD:
- MD13333 $MN_SAFE_SDP_CONNECTION_NR, MD13343 $MN_SAFE_RDP_CONNECTION_NR
Parameter DP_DP_ID is multiply occupied by different SPL connections. Relevant MD:
- MD13331 $MN_SAFE_SDP_ID, MD13341 $MN_SAFE_RDP_ID
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct the stated MD.
Programm
Switch control OFF - ON.
continuation:
27303
F_DP: Number of signals in MD %1 [%2] <> MD %3[%4]
Parameters:
%1 = MD name 1
%2 = MD array index for MD name 1
%3 = MD name 2
%4 = MD array index for MD name 2
Explanation:
Different numbers of F user data signals have been parameterized in machine data MD13336/13346 $MN_SAFE_SDP/
RDP_ASSIGN, MD13337/13347 $MN_SAFE_SDP/RDP_FILTER.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct the stated MD.
Programm
Switch control OFF - ON.
continuation:
27305
F_DP: Parameter MD %1 [%2] <> MD %3[%4]
Parameters:
%1 = MD name 1
%2 = MD array index for MD name 1
%3 = MD name 2
%4 = MD array index for MD name 2
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
549
NC alarms
Explanation:
An SPL connection has been parameterized with multiple SPL interfaces (sub-slots), in which different values have been
entered in the F_DP communication parameters or the SPL connection number (%1 and %3).
Note:
SPL interfaces (sub-slots) of an SPL connection are characterized by equal values for:
- F_DP communication parameter
- SPL connection number
The following NCK machine data may be affected:
- MD13334/13344 $MN_SAFE_SDP/RDP_LADDR or
- MD13335/13345 $MN_SAFE_SDP/RDP_TIMEOUT or
- MD13333/13343 $MN_SAFE_SDP/RDP_CONNECTION_NR
- MD13338/13348 $MN_SAFE_SDP/RDP_ERR_REAC
- MD13349 $MN_SAFE_RDP_SUBS
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct the stated MD.
Programm
Switch control OFF - ON.
continuation:
27306
F_DP: Maximum number of active SPL connections (%1) exceeded for %2.
Parameters:
%1 = Maximum possible number of SPL connections
%2 = Type of communication
Explanation:
More than the permissible number of SPL connections, marked by different identifiers (MD13331/13341 $MN_SAFE_SDP/
RDP_ID), have been parameterized in the active parameter data sets for the specified communication type (F_SENDDP/
FRECVDP).
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct the identifiers of the active SPL connections or deactivate SPL connections (MD13330/13340 $MN_SAFE_SDP/
RDP_ENABLE_MASK).
Set option for expanded number of connections.
Programm
Switch control OFF - ON.
continuation:
27350
F_DP: %1 communication, connection %2 reports error %3
Parameters:
%1 = Type of communication
%2 = Name or DP_DP_ID of the communication relationship
%3 = Error code
Alarms
550
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Explanation:
The F_DP communication with the external communication partner is faulty, and the programmed error response is
$A_FSDP_/FRDP_ERR_REAC = 0 or 1.
The following displays are possible for the communication type (%1):
- F_SENDDP
- F_RECVDP
The name or the DP_DP_ID (identifier) of the SPL connection is displayed as the connection (%2).
One of the following causes of the error is possible (see error code %3).
- SN: An error has been detected in the telegram sequence.
- CRC: A CRC error has been detected.
- TO: The parameterized communication timeout was exceeded.
All the error codes stated may also be displayed combined, depending on the fault profile.
Reaction:
Mode group not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
1. F_SENDDP/F_RECVDP: system variable $A_FSDP/FRDP_ERROR = TRUE
2. F_SENDDP/F_RECVDP: system variable $A_FSDP/FRDP_DIAG <> 0
3. F_RECVDP: system variable $A_FRDP_ACK_REQ = TRUE
4. F_RECVDP: Output of the substitute values defined in system variable $A_FRDP_SUBS
5. An alarm and Stop D/E are also triggered with the programmed error reaction $A_FSDP_/FRDP_ERR_REAC = 0
Remedy:
Check the PROFIBUS communication and the communication partner.
Check the parameterized logical basic addresses (note direct and indirect addressing) for other uses in other parts of the PLC
configuration.
Other possibilities for diagnostics:
- Prevent execution of the user program
- General reset of PLC and load basic program from the toolbox
Note:
A user acknowledgment via DB18.FRDP_ACK_REI only acknowledges F_DP communication. The alarm is still displayed and
must be acknowledged separately via NC RESET.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27351
F_DP: %1 communication, connection %2 reports error %3
Parameters:
%1 = Type of communication
%2 = Name or DP_DP_ID of the SPL connection
%3 = Error code
Explanation:
The F_DP communication with the external communication partner is faulty, and the programmed error reaction is
$A_FSDP_/FRDP_ERR_REAC = 2 (alarm, display only).
The following displays are possible for the communication type (%1):
- F_SENDDP
- F_RECVDP
The name or the DP_DP_ID (identifier) of the F_DP communication link is displayed as the connection (%2).
One of the following causes of the error is possible (see error code %3).
- SN: An error has been detected in the telegram sequence.
- CRC: A CRC error has been detected.
- TO: The parameterized communication timeout was exceeded.
All the error codes stated may also be displayed combined, depending on the fault profile.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
551
NC alarms
Reaction:
Alarm display.
1. F_SENDDP/F_RECVDP: system variable $A_FSDP/FRDP_ERROR = TRUE
2. F_SENDDP/F_RECVDP: system variable $A_FSDP/FRDP_DIAG <> 0
3. F_RECVDP: system variable $A_FRDP_ACK_REQ = TRUE
4. F_RECVDP: Output of the substitute values defined in system variable $A_FRDP_SUBS
Remedy:
Check the PROFIBUS communication and the communication partner
Check the parameterized logical basic addresses (note direct and indirect addressing) for other uses in other parts of the PLC
configuration.
Other possibilities for diagnostics:
- Prevent execution of the user program
- General reset of PLC and load basic program from the toolbox
User acknowledgment via DB18.FRDP_ACK_REI or NC-RESET
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27352
F_DP: Communication error %1, error %2
Parameters:
%1 = Error component (NCK/PLC)
%2 = Error code
Explanation:
Communication between the NCK and PLC is no longer working.
Faulty component on which the communication error occurred (%1):
- PLC: The PLC was not able to process the OB40 request for F_DP communication within the maximum monitoring time of
500ms.
The following cause of error is possible (see error code %2):
- <> 0: PLC execution of OB40 not completed.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Triggering of a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Processing stop of F_DP communication is triggered.
Stopped SPL connections of type F_RECVDP output failsafe values (0) towards SPL as F useful data.
Remedy:
Check and, if necessary, increase the F_DP cycle time.
Programm
Switch control OFF - ON.
continuation:
27353
F_DP: Current cycle time %1 [ms] > parameterized cycle time
Parameters:
%1 = Current F_DP communication cycle time
Explanation:
The current F_DP communication cycle time is greater than the value set via MD13320 $MN_SAFE_SRDP_IPO_TIME_RATIO.
The parameterized communication cycle time is continually exceeded on the PLC side.
Reaction:
Mode group not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Trigger a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Remedy:
Adapt cycle time via MD13320 $MN_SAFE_SRDP_IPO_TIME_RATIO.
At least the value displayed in the alarm text must be set.
The set cycle time affects the runtime load of the PLC module. This also has to be taken into consideration when making the
setting.
Alarms
552
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27354
F_DP: %1 communication, connection %2 reports SFC%3 error %4
Parameters:
%1 = Type of communication
%2 = Name or DP_DP_ID of the communication relationship
%3 = SFC block number
%4 = Error code
Explanation:
The F_DP communication with the external communication partner is faulty. The PLC reports an error when trying to access
via the parameterized interface.
The following displays are possible for the communication type (%1):
- F_SENDDP
- F_RECVDP
The name or the identifier (DP_DP_ID) of the F_DP communication link is displayed as the connection (%2).
The PLC block (%3) that detected an error and the cause of error based on the error code (%4) are also displayed.
This alarm can be masked with MD10096 $MN_SAFE_DIAGNOSIS_MASK, bit 2 = 1.
Reaction:
Alarm display.
Remedy:
Check the PROFIBUS communication and the communication partner
Check the parameterized, logical basic address in MD13334/13344 $MN_SAFE_SDP/RDP_LADDR.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
27355
F_DP: %1 communication, connection %2 reports system error %3 (%4)
Parameters:
%1 = Type of communication
%2 = Name or DP_DP_ID of the SPL connection
%3 = Error code
%4 = Component
Explanation:
A system error was detected during F_DP communication. Depending on the error, the relevant SPL connection or the entire
F_DP communication will be stopped.
The following displays are possible for the communication type (%1)
- F_SENDDP
- F_RECVDP
- SPL
The following displays are possible as the connection (%2):
- Name or DP_DP_ID (identifier) of the SPL connection ( for communication type = F_SENDDP or F_RECVDP)
- "-" ( for communication type = SPL)
One of the following causes of error is possible (see error code %3):
- SF: asynchronous error state (StateFault)
- LS: sign-of-life monitoring (LifeSign)
- TD: discrepancies in the F telegram data (TelegramDiscrepancy)
- OD: discrepancies in the output data (OutputdateDiscrepancy)
- with communication type = F_SENDDP: $A_FSDP_ERR_REAC - DB18 DBW190, DBW210, DBW220, DBW448, DBW458 ...
DBW568
- with communication type = F_RECVDP: $A_FRDP_SUBS
- DB18 DBW220, DBW232, DBW244, DBW578, DBW590 ...
DBW722
$A_FRDP_ERR_REAC - DB18 DBW222, DBW234, DBW246, DBW580, DBW592 ... DBW724
- SP: no update of the SPL input/output data (SPL I/O-communication)
The error codes stated may also be displayed combined, depending on the fault profile.
The affected component (%4) is also displayed in the alarm text:
- NCK
- PLC
- system variable (when error code = OD)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
553
NC alarms
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Triggering of a STOP D/E (settable via MD10097 $MN_SAFE_SPL_STOP_MODE) on all axes with safety functionality.
Stopped SPL connections of type F_RECVDP output failsafe values (0) as F user data.
Remedy:
Power OFF/ON of the control. If the error occurs again, inform the service department.
Programm
Switch control OFF - ON.
continuation:
27801
Safety operating mode inconsistent: MD %1 = %2; PLC configuration = %3
Parameters:
%1 = $MN_SAFE_MODE
%2 = Value from $MN_SAFE_MODE
%3 = Value of the PLC configuration
Explanation:
The value in the MD13370 $MN_SAFE_MODE does not match the value of the PLC configuration.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Align the safety operating modes by making a change in the MD13370 $MN_SAFE_MODE or the PLC configuration.
If -1 is displayed for the value of the PLC configuration, the following applies: the safety operating mode defined in the PLC
configuration is not permitted. The PLC configuration must be changed.
Programm
Switch control OFF - ON.
continuation:
27810
Axis %1 Safety operating mode inconsistent: $MN_SAFE_MODE = %2; MD: %3 = %4
Parameters:
%1 = Axis name, spindle number
%2 = Machine data value
%3 = MD name
%4 = Machine data value
Explanation:
The safety operating mode parameterized with MD13370 $MN_SAFE_MODE does not match the safety enables
parameterized with the displayed machine data.
This alarm occurs in the following contexts:
- For the safety operating mode "SINUMERIK Safety Integrated plus (F-PLC)", safety enables are set in MD36901
$MA_SAFE_FUNCTION_ENABLE.
- For the safety operating mode "SINUMERIK Safety Integrated (SPL)", safety enables are set in MD37950
$MA_SAFE_INFO_ENABLE, however mixed operation (SIC/SCC in ncSI-mode) is not allowed.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Prevention of cyclic SIC/SCC or PROFIsafe communication between the NCK and drive.
Remedy:
Align safety operating mode for all NC axes.
Programm
Switch control OFF - ON.
continuation:
Alarms
554
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
27811
Axis %1 Parameterizing error: MD %2 [%3] invalid
Parameters:
%1 = Axis name, spindle number
%2 = MD name
%3 = MD array index for MD name
Explanation:
The parameterization of the displayed machine data is incorrect.
This alarm occurs in the following contexts:
- During evaluation of the SIC/SCC telegram number in MD13376 $MN_SAFE_INFO_TELEGRAM_TYPE or in drive parameter
p60122, an invalid SIC/SCC telegram number was found (not equal to 701).
- The check of the logical base addresses from MD13374 $MN_SAFE_INFO_DRIVE_LOGIC_ADDR has indicated that a slot
with this address does not exist, or the SIC/SCC telegram has an incorrect length and "SIC/SCC" communication cannot be
enabled.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Prevention of cyclic PROFIsafe communication between PLC and drive.
Prevention of cyclic SIC/SCC communication between the NCK and drive.
Remedy:
Parameterize a valid SIC/SCC telegram number (701).
Configure or parameterize with valid logical basis addresses for the SIC/SCC slots or PROFIsafe slots.
Programm
Switch control OFF - ON.
continuation:
27812
Axes %1 and %2 parameterized with the same SIC/SCC address %3.
Parameters:
%1 = Axis name, spindle number
%2 = Axis name, spindle number
%3 = Logical base address SIC/SCC
Explanation:
The same base address for communication with a drive was selected for the specified axes. This is not permissible.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Correct the drive assignment for the two specified axes.
Different logical base addresses must be selected for assignment to the specified axes via MD37954
$MA_SAFE_INFO_MODULE_NR and MD13374 $MN_SAFE_INFO_DRIVE_LOGIC_ADDR.
Programm
Switch control OFF - ON.
continuation:
27813
F logic option not set
Explanation:
The option for F logic MD19500 $ON_SAFE_PLC_LOGIC is not available.
The safety operating mode "SINUMERIK Safety Integrated plus (F-PLC)" is set in the MD13370 $MN_SAFE_MODE.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Prevention of cyclic PROFIsafe communication between PLC and drive.
Prevention of cyclic SIC/SCC communication between the NCK and drive.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
555
NC alarms
Remedy:
Align option data and safety operating mode.
Programm
Switch control OFF - ON.
continuation:
27830
Axis %1 Control not ready for the drive-integrated safe brake test
Parameters:
%1 = Axis name, spindle number
Explanation:
The motion control rejects the request for the drive-integrated "safe brake test" via the VDI interface.
Possible causes:
- When the brake test was selected via the VDI, the interpolator or the axis had not stopped, therefore the axis in motion or
exact stop was not (no longer) given.
- A new brake test was requested, but the previous brake test had not yet finished in the control.
- Another axis was in motion in the channel.
Reaction:
Alarm display.
Remedy:
The alarm disappears automatically if the conditions in the motion control for performing the drive-integrated "safe brake
test" are fulfilled, or the request for the drive-integrated "safe brake test" is withdrawn.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27900
PROFIBUS DP: SI fault on axis %1, code %2, value %3, time %4.
Parameters:
%1 = Axis name, spindle number
%2 = Fault code of the drive (r9747).
%3 = Fault value of the drive (r9749)
%4 = Fault time of drive (r9748).
Explanation:
The drive signals SI fault %2 with the further information %3 at instant %4.
Reaction:
Alarm display.
Remedy:
See drive documentation for fault codes/fault values.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
27910
PROFIBUS DP: SI fault on axis %1, code %2, value %3, time %4.
Parameters:
%1 = Axis name, spindle number
%2 = Fault code of the drive (r9747).
%3 = Fault value of the drive (r9749)
%4 = Fault time of drive (r9748).
Explanation:
The drive signals SI fault %2 with the further information %3 at instant %4.
Reaction:
NC Start disable in this channel.
Alarm display.
A start of the part program is prevented by an SI fault reported by the drive.
The SI fault requires a safe acknowledgment.
Remedy:
See drive documentation for fault codes/fault values.
Programm
Alarm display showing cause of alarm disappears. No further operator action necessary.
continuation:
28000
NCU link connection to all other NCUs of the link network has been canceled
Explanation:
All NCUs in the NCU link network exchange data cyclically (sign-of-life). If this alarm occurs, sign-of-life signals have not been
received from any other NCUs on the NCU network. This fault in the link can have various causes:
- Defective hardware.
- The machine data which configure the NCU link are not the same on all NCUs.
- An identical interpolator cycle time has not been selected on all NCUs.
Alarms
556
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the IPO cycle on all the NCUs.
If necessary, check NCU link-specific alarms first.
Programm
Switch control OFF - ON.
continuation:
28001
NCU link connection to the NCU %1 of the link network has been canceled
Parameters:
%1 = NCU number
Explanation:
All NCUs in the NCU link network exchange data cyclically (sign-of-life). If this alarm occurs, sign-of-life signals have not been
received from one other NCU on the NCU network. (see alarm parameters) This fault in the link can have various causes:
- Defective hardware.
- The machine data which configure the NCU link are not identical on all NCUs.
- An identical interpolator cycle time has not been selected on all NCUs.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
- Check the IPO cycle on all the NCUs.
- If necessary, check NCU link-specific alarms first.
Programm
Switch control OFF - ON.
continuation:
28002
Error on activation of machine data, NCU network-wide machine data were modified by NCU
%1
Parameters:
%1 = NCU number
Explanation:
During the activation of machine data with NEWCONFIG or during an operator panel RESET, NCU network-wide machine
data were modified on another NCU. This alarm can only occur when a link connection is active.
Reaction:
NC not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Repeat the operator action or, if NEWCONFIG is activated by an NC program, terminate the program with Reset.
Programm
Clear alarm with the RESET key. Restart part program
continuation:
28003
Synchronization of the life cycle in the NCU link failed after %1 attempts.
Parameters:
%1 = Loop counter
Explanation:
At a specific point in time during NCK ramp-up, the NCK switches to the cyclic plane; in other words, the IPO and servo tasks
start to work. If these points in time deviate too significantly in the NCU link grouping, this alarm 280003 will appear. This
delay time can be increased in IPO cycle steps by increasing the machine data LINK_LIFECYCLE_MAX_LOOP.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
557
NC alarms
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
If you experience such a system error, please contact Technical Support.
Please supply the following information to ensure quick processing:
- Alarm number together with alarm text
- Description of the operation/mode before the alarm message
- Generate log files using the key combination: <Ctrl> + <Alt> + <D>
Programm
Switch control OFF - ON.
continuation:
28004
NCU link: NCU %1 of the link network is not on the bus
Parameters:
%1 = NCU number
Explanation:
Error message of the NCU link module. When the NCU link was powered up, the local NCU (indicated by the alarm) detected
that the NCU with the number in the alarm parameter was not on the bus although it should be connected according to the
MD settings.
This fault in the link can have various causes:
- Defective hardware.
- The machine data which configure the NCU link are not identical on all NCUs.
- An identical interpolator cycle time has not been selected on all NCUs.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the machine data configuration and link hardware.
Programm
Switch control OFF - ON.
continuation:
28005
NCU link: NCU %1 of the link network not running synchronously
Parameters:
%1 = NCU number
Explanation:
Error message of the NCU link module. When the NCU link was powered up, the local NCU (indicated by the alarm) detected
that the NCU with the number in the alarm parameter was not running synchronously.
This fault in the link can have various causes:
- The machine data which configure the NCU link are not identical on all NCUs.
- An identical interpolator cycle time has not been selected on all NCUs.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data configuration.
Programm
Switch control OFF - ON.
continuation:
Alarms
558
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
NC alarms
28007
NCU link: conflict in configuration data of NCU %1
Parameters:
%1 = NCU number
Explanation:
Error message of the NCU link module. When the NCU link was powered up, the local NCU (indicated by the alarm) detected a
conflict between its configuration and the configuration of the NCU in the alarm parameter.
Example: MD18782 $MN_MM_LINK_NUM_OF_MODULES defines the number of nodes on the NCU link network. The alarm
occurs if this MD has a different setting on different NCUs.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data configuration.
Programm
Switch control OFF - ON.
continuation:
28008
NCU link: conflict in timer setting of NCU %1
Parameters:
%1 = NCU number
Explanation:
Error message of the NCU link module. When the NCU link was powered up, the local NCU (indicated by the alarm) detected a
conflict between its timer configuration and the configuration of the NCU in the alarm parameter.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data configuration.
Programm
Switch control OFF - ON.
continuation:
28009
NCU link: conflict in bus parameters of NCU %1
Parameters:
%1 = NCU number
Explanation:
Error message of the NCU link module. When the NCU link was powered up, the local NCU (indicated by the alarm) detected a
conflict between its timer bus configuration and the configuration of the NCU in the alarm parameter.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check machine data configuration.
Programm
Switch control OFF - ON.
continuation:
28010
NCU link: the NCU %1 has not received a message %2, %3
Parameters:
%1 = NCU number
%2 = Reason
%3 = Data block
Explanation:
Error message of the NCU link module. During operation of the NCU link, a message from the local NCU to the NCU
specified in the alarm parameter has failed. A hardware error may have occurred (e.g. sporadic disturbances on the
communication line).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
559
NC alarms
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
The message does not fail until several attempts have been made to repeat the communication. The number of repetitions
can be increased with MD12550 $MN_LINK_RETRY_CTR.
Programm
Switch control OFF - ON.
continuation:
28011
IPO time insufficient for NCU link. Link cycle time: %1
Parameters:
%1 = Microseconds
Explanation:
Error message of the NCU link module. All messages must be transmitted within one interpolator cycle. This applies
particularly to messages retries. The time was not sufficient! The parameter indicates how many microseconds the NCU link
module needs in order to send the message.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Increase the interpolator cycle time, i.e. modify one of the following MDs on all NCUs.
IPO_SYSCLOCK_TIME_RATIO
SYSCLOCK_CYCLE_TIME
Programm
Switch control OFF - ON.
continuation:
28012
NCU link: synchronization cycle signal failure %1 times
Parameters:
%1 = Number of cycles
Explanation:
Error message of the NCU link module that does not occur at NCU 1. The NCUs are synchronised via their own NCU-link clock
line. A large number of successive cycle signals failed to appear. The parameter indicates how many successive cycles have
failed.
Reaction:
NC not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the hardware.
Programm
Switch control OFF - ON.
continuation:
28020
NCU link: too many links configured %1
Parameters:
%1 = Number of link connections
Explanation:
Unfortunately, the transmission capacity of the NCU link is insufficient for this link configuration.
The link configuration is determined by the following MDs:
- MD18781 $MN_NCU_LINK_CONNECTIONS
- MD10002 $MN_AXCONF_LOGIC_MACHAX_TAB
- MD12701 $MN_AXCT_AXCONF_ASSIGN_TAB1 ... and all further container defs.
Alarms
560
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
|