Explanation:
Currently, the alarm occurs only in combination with the SERUPRO action. SERUPRO stands for search via program test.
SERUPRO is currently searching the search target and has therefore switched this channel to the program test mode.
With the START program command in channel 1, another channel 2 would actually be started, which means that axes
would really be started during the search action.
If this alarm is switched off (see help), the user can make use of the above behavior by initially selecting via PLC the
program test mode in channel 2, leaving channel 2 executing until its natural end, stopping channel 2 in order to deselect
program test again.
Reaction:
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Alarm can be switched off with MD10708 $MN_SERUPRO_MASK bit 1.
Programm
continuation:
Clear alarm with the RESET key. Restart part program
16943
[Channel %1: ] Action %2<ALNX> not possible due to ASUB
Parameters:
%1 = Channel number
%2 = Action number/action name
Explanation:
The action in the 2nd parameter was rejected, since an asynchronous subprogram is currently active.
Currently, only the integrated search run is rejected with this alarm. The integrated search run is activated, if search run
is triggered in the Stop program state. In other words: Parts of a program have already been executed and a following
program part is "skipped" with search run in order to continue the program afterwards.
The event is not possible if the program is stopped within an asynchronous subprogram or if an asynchronous subprogram
had been selected before the event. An asynchronous subprogram is selected, when the triggering asynchronous
subprogram event arrives, but the asynchronous subprogram cannot be started (e.g. the asynchronous start program is
not started because of a read-in disable or because the Stop key is active).
In this case, it is irrelevant whether a user ASUB or a system ASUB has been triggered. User ASUBs are activated via
FC-9 or via the fast inputs.
The following events lead to system ASUBS:
- Mode change
- Overstore on
- Canceling subprogram level
- Switching on of single block, type 2
- Setting machine data effective
- Setting user data effective
- Change skip levels
- Dry run on/off
- Program test off
- Correction block alarms
- Editing modi in Teach
- External work offset
- Axis exchange
- Delete distance-to-go
- Measuring
Reaction:
Alarm display.
Remedy:
Repeat the action after the end of the asynchronous subprogram.
Programm
continuation:
Clear alarm with the Delete key or NC START.
16944
[Channel %1: ] Action %2<ALNX> not possible due to active search blocks
Parameters:
%1 = Channel number
%2 = Action number/action name
SINUMERIK 808D ADVANCED alarms
5.2 NCK alarms
Diagnostics Manual
Diagnostics Manual, 06/2015, 6FC5398-6DP10-0BA2
265