Commissioning Manual
6FC5397-4EP10-0BA8, 07/2018
283
Handling the encrypted cycles
The machine manufacturer must transfer the encrypted cycles (.CPF files) to the control and perform a power-on reset
before executing the encrytped cycles. If no power-on reset is performed, the processing of a .CPF file causes the NC alarm
15176.
An encrypted cycle can be deleted or unloaded just like an .SPF or .MPF file. All the encrypted .CPF files are also backed up
when an archive is generated.
Executing an encrypted cycle
● An encrypted cycle cannot be directly selected for execution. It can only be called from a part program - or directly in
MDI.
● An encrypted cycle cannot be executed with the external execution function.
Using encrypted cycles at one or more machines
●
Using encrypted cycles at only one machine
If a cycle must not be used at another machine, then it can be permanently linked to a particular machine. The machine
data MD18030 $MN_HW_SERIAL_NUMBER can be used for this purpose.
When the control powers on, the unique hardware serial number of the CF card is saved in this machine data. If a cycle
is to be permanently linked to a machine, then the serial number of the CF card (MD18030) must be queried in the call of
the cycle. If the cycle identifies a serial number that does not match, then an alarm can be output in the cycle and so
prevents further processing. As the code of the cycle is encrypted, there is always a fixed link to a defined hardware.
●
Using encrypted cycles at several machines
If a cycle is to be permanently linked to several defined machines, then each of the hardware serial numbers must be
entered in the cycle. The cycle must be re-encrypted with these hardware serial numbers.
To Next Page
Loading...
Need help?
General
