1 Update Information No
ADRESS MASK BROADCAST ROUTER HOST DOMAIN NAMESERVER
1.4.3 New Update Procedures Once Software 340 49x-02 Has Been Installed
Previous The previous procedure for software updates can continue to be used. In addition, service packs can be selected and deleted in the selection dialog box.
What’s new? The following files are now necessary for an update, and must be located in the same directory:
- setup.zip
- setup.omf (setup.exe in Windows)
- setup.ini (this is to be created by the OEM, and is only necessary if the update is to occur according to a specific sequence)
Please note that this currently means that the version of the software to be installed is not displayed in advance.
Software updates and service packs are loaded in the same manner.
Automatic update possible. If your directories are structured appropriately, this method makes it possible to update the control automatically when it is booted. If there is an “install” directory on your iTNC containing a setup.ini control file, an update is performed automatically according to the
instructions in this control file (see “Control file for automatic update (setup.ini)” on page 1 – 34).
The following directories are checked during booting for the presence of a control file:
• iTNC without Windows - TNC:\install\
or, if a USB memory device is connected
- USB0:\install\ (USB0: first partition of the first USB memory device) • iTNC with Windows
- D:\install\
or, if a USB memory device is connected
- G:\install\ (G: corresponds to the drive letter of the USB memory device – network drives are not permitted!)
Start the update via the keyword SETUP
No naming convention according to the usual format is necessary
Copying of the update files (setup.omf/exe and setup.zip) to the system partition occurs automatically as part of the update program in directories with the following naming convention:
• iTNC without Windows
- Software update: SYS:\zip\<Id.Nr.>_<ver> - Service pack: SYS:\zip\<Id.Nr.>_<ver>_SP<n> • iTNC with Windows
- Software update: C:\Program Files\install\<Id.Nr.>_<ver> - Service pack: C:\Program Files\install\<Id.Nr.>_<ver>_SP<n>
Note
You can download the two files necessary for the update (setup.zip and
setup.omf) from the HEIDENHAIN FileBase under “NC Milling iTNC530 > Software” as a single ZIP file, e.g. 340490_002.zip, and unzip them in your Update directory.
September 2005 NC Software 340 490-02/340 491-02 and 340 492-02/340 493-02 1 – 33
A query appears, asking whether the necessary binary to ASCII conversions should be performed. If yes, then a procedure in case there is not enough memory is requested:
- Cancel if not enough memory - Delete largest or oldest files first
This can be automated in the control file mentioned above.
Only files whose binary version has changed are converted.
The NC software has been prepared in such a manner that when an update is performed or a service pack loaded, the PLC program and PLC partition can be updated as well, according to the requirements of the OEM. When the NC software is updated, the OEM uses the HEIDENHAIN PC software PLCdesignNT to add all necessary files to the setup.zip archive. These files are copied to the appropriate locations during an update.
If the PLC:\_mpupdate directory is created during the automatic update by the OEM, then files that automatically update or expand the active and selected MP or OEM.SYS files when the control is started can be saved here.
Files containing the name merge.* (merge.mp and merge.oem.sys) expand the MP and OEM.SYS files by the entries contained in them. Files containing the name overwrite.* (overwrite.mp and overwrite.oem.sys) contain updated entries for the corresponding files, and overwrite entries with the same names in the MP and OEM.SYS files.
MP subfiles are ignored here.
After successful installation, these ASCII files are automatically reconverted to binary format.
Warning
No manual changes may be made to these directories, since they might be required for restoring earlier software versions.
Note
The support necessary for this from PLCdesignNT will be available starting in the next release (version 2.3). It is not possible to update only the PLC data but not the NC software.
Control file for automatic update (setup.ini)
In order to automate an update as much as possible, a control file with the name setup.ini is necessary. This file can be created with a simple text editor.
An example of a setup.ini file:
Interactive=1 Confirm=1 Language=GERMAN
SavePlc=TNC:\backup\340422_012.zip
The following settings are selectable:
Parameters Description
Interactive=[0,1] Deletion of the NC software archive (old software versions) and binary to ASCII conversion must be confirmed by the user.
0: No
1: Yes [default]
Confirm=[0,1] Start of update and reboot process must be confirmed by the user
0: No
1: Yes [default]
ServiceRequest=[0,1] A service request is triggered after an update (only if remote diagnosis is active)
0: No [default] 1: Yes
ConvertToAscii=[0,1] (only if Interactive=0)
Binary to ASCII conversion with automated update process (not with service pack)
0: No
1: Yes [default]
CopyToSys=[0,1] The setup archive to be installed is copied to the directory SYS:\zip (iTNC with Windows:
C:\Program Files\install). This makes it possible to return to this software version later.
0: No
1: Yes [default]
DeleteFiles= [DATE,SIZE,CANCEL] (only if Interactive=0)
Procedure during binary to ASCII conversion during automated update if there is not enough memory available on the TNC or PLC partition
DATE: Delete oldest files first SIZE: Delete largest files first CANCEL: Cancel the update [default]
DeleteArchives= [DATE,SIZE,CANCEL] (only if Interactive=0)
Procedure is there is not enough room on the SYS partition for the update
DATE: Delete oldest archive first SIZE: Delete largest archive first CANCEL: Cancel the update [default]
September 2005 NC Software 340 490-02/340 491-02 and 340 492-02/340 493-02 1 – 35 Language=[ENGLISH,
GERMAN] (only if Confirm=0)
Language for the dialog guidance during the update if no user activities are required for starting the update and rebooting (Confirm=0)
GERMAN: German dialog text ENGLISH: English dialog text [default]
DelSource=[0,1] Delete the source files (setup.zip, setup.ini, setup.omf/exe) once the update has completed successfully
0: No [default] 1: Yes
DeleteIni=[0,1] Delete the setup.ini file after a successful update.
0: No [default] 1: Yes
SavePlc=<name> If the software is updated from 340 49x-02 or higher to a newer version, then the entire PLC partition can be stored as a ZIP file in binary format. This makes it possible to restore this software state including the PLC files.
Here you enter the path and file name for the ZIP file in which the entire PLC partition is saved in binary format. Please consider the software version when assigning the file name. RestorePlc=<name> The “Restore” function is used to restore the
PLC data to a certain software state.
Here you enter the path and file name for the ZIP file containing the PLC data state (in binary format) appropriate to the NC software version to be installed. This should be the ZIP file which was saved with the “SavePlc” function, containing the corresponding PLC state and saved on the PLC partition.
New update for iTNC without Windows
Manual update
The following procedure is used to perform a manual update (without a
setup.ini file in the setup directory) or an installation of a service pack: 8HEIDENHAIN recommends making a backup for the control
8Connect the drive or USB device containing the files necessary for the update (setup.zip, setup.omf)
8In the Programming and Editing mode, press the MOD key 8Enter the keyword Setup
8In the browser, select the directory and the corresponding Setup.omf file 8Select the desired language for the update guidance
8Choose the desired action for the event that there is not enough memory available on the TNC or PLC partition for the binary to ASCII conversion: - Cancel if not enough space: The update procedure is cancelled if there is not enough space available, and a message to this effect appears. In this case you must save the files (*.h, *.i, and tables) externally, if they are needed, and then remove them manually in order to make space for the conversion.
- Delete largest files first: The largest files (*.h, *.i, and tables) are deleted until there is enough space for the conversion.
- Delete oldest files first: The oldest files (*.h, *.i, and tables on the PLC and TNC partitions) are deleted until there is enough space for the conversion.
8If there is not enough space on the SYS partition, select deletion of the oldest setup files. This procedure is repeated until there is enough memory space available.
8Confirm the update actions listed and that are to be performed.
8After the update has finished successfully, confirm the restart of the control.
Automated update
If one of the following directories exists when an iTNC without Windows is booted,
- TNC:\install\
or, if a USB memory device is connected
- USB0:\install\ (USB0: first partition of the first USB memory device) and if a setup.ini control file is saved in this directory, then an automated update is performed according to the instructions in this control file (see “Control file for automatic update (setup.ini)” on page 1 – 34).
An automated update is usually a part of a manual update. This means that you can use the control file to reduce the number of user actions necessary for the update to a minimum, and at the same time make a backup of the PLC partition.
Note
If a setup.ini file exists in the setup directory when you update manually, then the update is performed according to the instructions in this file. See “Control file for automatic update (setup.ini)” on page 34.
September 2005 NC Software 340 490-02/340 491-02 and 340 492-02/340 493-02 1 – 37
Update via remote operation
How to perform an update via remote operation:
8In the Programming and Editing mode of the iTNC, press the MOD key 8On the iTNC, activate remote maintenance by pressing the Service ON soft
key.
A “service request” is triggered and a connection is established. 8Transmit the setup.omf and setup.zip files to a suitable directory on the
control (e.g. TNC:\update)
8Continue the update via remote operation as described under “Manual update”
Notes on updating via remote operation
If remote maintenance is active when the update is started, the remote maintenance is deactivated (this does not affect the current remote operation).
After the reboot or after the update was cancelled due to an error, a service request is triggered. The service request information indicates whether the update was successful.
If the control does not boot due to missing or incorrect machine parameters, a service request is triggered until the “power interrupt” stage of the boot process is reached.
New update for iTNC with Windows
Manual update
The following notes apply to software updates and installations of service packs for the iTNC with Windows:
The actual update process is started as previously in Windows.
Service packs are now installed according to this method. The soft keys on the control for installing service packs have been omitted.
Since the update procedure itself is now capable of stopping the
NC software in order to perform an update, the procedure for stopping the NC software via the Control Panel has been omitted.
In addition, analogous to the iTNC without Windows, manual binary to ASCII conversion is no longer necessary. This can now also be performed during the update procedure. A warning appears if no automatic conversion is possible.
Automated update
If one of the following directories exists when an iTNC with Windows is booted,
- D:\install\ (D: corresponds to the TNC partition) or, if a USB memory device is connected
- G:\install\ (G: corresponds to the drive letter of the USB memory device – network drives are not permitted!)
and if a setup.ini control file is saved in this directory, then an automated update is performed according to the instructions in this control file (see “Control file for automatic update (setup.ini)” on page 1 – 34). If this file does not exist, the update must be started manually via the SETUP keyword. An automated update is usually a part of a manual update.