Siemens SINUMERIK 840Di, Руководство пользователя

Страница: 391 / 552

06.03
10.7 Loadable compile cycles (SW 2.2 and higher)
10-391

Siemens AG, 2003. All rights reserved
SINUMERIK 840Di Manual (HBI) – 06.03 Edition
Note
Several compile cycles can be copied to the NCK FSS in succession; you don’t
need to perform an NCK reset after each copy procedure.
10.7.2 Boundary conditions
The following checks are performed for all loaded compile cycles when the NCK
boots:
If the interface version of the compile cycle is incompatible with the interface
version of the NCK system software, the following alarm is issued:
Alarm “7200 Version_conflict_with_CCNCKInterfaceVersion”.
If a compile cycle has a functional dependency on another one which is not
loaded to the NCK, the following alarm is issued:
Alarm “7200 CC<Identifier>_ELF Loader_problem_from_dFixup”.
If the compile cycle is not enabled in conjunction with SINUMERIK
840Di/840DiE, the following alarm is issued:
Not enabled for SINUMERIK 840Di
Alarm “7200 CC<identifier>_ELF NO_840Di”
Not enabled for SINUMERIK 840DiE
Alarm “7200 CC<identifier>_ELF NO_EMBARGO”.
Notice
If after booting the NCK, alarm “7200 . . .” appears, then none of the loaded
compile cycles are active.
10.7.3 Activating and licensing the technological functions
To activate the technological function loaded with the compile cycle to the NCK,
you need to set and license the respective option.
For information about how to activate and license options, please see Section
6.8, page 6-201.
Each loaded compile cycle generates a technological function-specific global
machine data:
$MN_CC_ACTIVE_IN_CHAN_<identifier>[n], with n = 0, 1
in the machine data number range 60900 to 60999.
Interface
versions
Dependencies
System enables
Activating and
licensing the
option
Activating the
technological
function
10 NC Start-Up with HMI Advanced