HSM Mainhelp

HEUFT SERVICE MANAGER
Operator's Manual
HEUFT Service Manager
HBD602700 ENG Betriebsanleitung HEUFT Service Manager 3.00.006
HBD602700 ENG HEUFT Service Manager 3.00.006
HEUFT HEUFT LTD. HEUFT HISPANIA, S.A. HEUFT QUALIPLUS B.V. HEUFT FRANCE S.A. HEUFT ITALIA s.r.l.
SYSTEMTECHNIK GMBH Tamworth, Madrid, SPAIN Deventer, NETHERLANDS Brumath, FRANCE Vigevano, ITALY
Burgbrohl, GERMANY GREAT BRITAIN Phone: +34 91 6667 300 Phone: +31 570 6617 00 Phone: +33 388 59 3000 Phone: +39 0381 290411
Phone: +49 2636 56 0 Phone: +44 1 827 255800 spain@heuft.com netherlands@heuft.com france@heuft.com italy@heuft.com
info@heuft.com uk@heuft.com
HEUFT SCAN Aps HEUFT USA Inc. HEUFT DO BRASIL Ltda. HEUFT S.A. HEUFT MEXICO S.A. de HEUFT CHINA Co. Ltd.
Gilleleje, DENMARK Downers Grove, USA Alphaville-S.P., BRASIL Beccar, ARGENTINA C.V. Shanghai, CHINA
Phone: +45 4836 5070 Phone: +1 630 968 9011 Phone: +55 11 4195 7671 Phone: +54 11 4719 6945 Naucalpan de Juárez, Phone: +86 216 434 3911
scandinavia@heuft.com usa@heuft.com brasil@heuft.com argentina@heuft.com MEXICO china@heuft.com
Phone: + 55 55 62 84 50
mexico@heuft.com
HEUFT ASIA LTD. HEUFT AUSTRIA OOO HEUFT EURASIA HOTLINE and REMOTE INTERNET
Hong Kong, CHINA Leobersdorf, AUSTRIA Moscow, RUSSIA SERVICE www.heuft.com
Phone: +86 216 434 3911 Phone: +43 2256 65556 0 Phone: +7-495-935-8704 Phone: +49 2636 56 277 E-MAIL:
asia@heuft.com austria@heuft.com eurasia@heuft.com Fax: +49 2636 56 256 info@heuft.com
3
Version Date Comments
3.00.006 01.10.10 Translation of the German version
It is possible that this documentation still contains printing errors. However its contents are regularly checked
and all future editions amended accordingly.
We reserve the right to make modifications which may become necessary due to technical progress.
These technical documents are for your personal use only. They may not
be copied or given to third parties without our previous consent in
writing. HEUFT SYSTEMTECHNIK GMBH © 10/10
4
Table of Contents
The HEUFT Service Manager is capable of the following ............................................................................ 9
Structure of the Operator’s Manual .......................................................................................................... 9
Installing the HEUFT Service Manager....................................................................................................... 10
Debug levels .......................................................................................................................................... 10
Starting the HEUFT Service Manager .........................................................................................................11
Help ........................................................................................................................................................ 11
General information .................................................................................................................................. 13
PILOT software ........................................................................................................................................... 13
The compatibility of the PILOT software versions .................................................................................. 14
Device drivers ............................................................................................................................................. 15
Service pack .......................................................................................................................................... 15
Device drivers test pack ......................................................................................................................... 16
Spare parts lists ..................................................................................................................................... 16
Spare parts list filter ............................................................................................................................... 17
General information regarding the installation of drivers ....................................................................... 18
Language list .......................................................................................................................................... 19
Reorganisation............................................................................................................................................ 20
Equipment................................................................................................................................................... 20
Equipment flags ..................................................................................................................................... 21
Clearing the HEUFT Service Manager for users ........................................................................................ 23
Renewed clearance for the HEUFT Service Manager ........................................................................... 25
Decoding the CD-ROM ............................................................................................................................... 27
Deactivating the CD decoder ................................................................................................................. 27
Device management ................................................................................................................................. 29
Configuring device search with the HEUFT Service Manager .................................................................... 31
Connection via the service port of the SPECTRUM TX ......................................................................... 31
Connection via the network configuration .............................................................................................. 31
Setting up network devices .................................................................................................................... 32
Setting up local devices ......................................................................................................................... 34
Setting up archive devices ..................................................................................................................... 35
Allocating container and case pictures ....................................................................................................... 37
Allocating the picture of a container or a case to a program .................................................................. 38
Sending the allocation data to the HLAN-Manager ................................................................................ 39
Cancelling the picture allocation currently selected ............................................................................... 40

Deleting the allocation of all containers or case pictures in the device .................................................. 40
Saving data ................................................................................................................................................. 41
Entering the contact IP address ............................................................................................................. 41
Selecting the device using the network search ...................................................................................... 41
Creating a data backup .......................................................................................................................... 43
Restoring the data backup on the device selected ................................................................................ 45
"local (standard)" restoration .................................................................................................................. 45
Free RADF selection .............................................................................................................................. 47
HSM restoration filter ............................................................................................................................. 49
Transferring complete programs ..................................................................................................... 49
Transferring individual modules ...................................................................................................... 52
Installing a parameter set ....................................................................................................................... 53
Transferring data backups to the TX archive .............................................................................................. 57
5
Data saving via Internet into the TX archive .......................................................................................... 58
General note on carrying out the hba uploads via a HEUT Gateway Server at the customer's ..... 58
Restarting the data transmission after an external interruption ............................................................. 62
Manual data saving to the TX archive .................................................................................................... 64
Local data backups ................................................................................................................................ 64
Installing device drivers............................................................................................................................... 65
Installing a new device driver ................................................................................................................. 66
Resetting device drivers to original adjustment ..................................................................................... 67
Installing device drivers (service) ................................................................................................................ 69
Setting up a device connection ................................................................................................................... 73
Separating a device connection ............................................................................................................. 75
Sending equipment ..................................................................................................................................... 77
Setting equipment ....................................................................................................................................... 79
Managing inspection pictures ..................................................................................................................... 83
Downloading inspection pictures from the SPECTRUM. ....................................................................... 83
Uploading inspection pictures to the SPECTRUM ................................................................................. 88
Configuring the network .............................................................................................................................. 93
IP addresses, subnet mask and gateway addresses.................................................................................. 95
IP addresses .......................................................................................................................................... 95
Network classes ..................................................................................................................................... 96
Class A ........................................................................................................................................... 96
Class B ........................................................................................................................................... 96
Class C ........................................................................................................................................... 97
Subnet masks ........................................................................................................................................ 97
localhost ........................................................................................................................................ 101
Network adjustments ................................................................................................................................ 102
DHCP (automatic assignment of IP addresses) .................................................................................. 102
Activating DHCP under LINUX (on a HEUFT terminal) ....................................................................... 102
Deactivating DHCP under LINUX and setting a fixed IP number (on the HEUFT terminal) ................ 103
Setting of IP-addresses and subnet mask ........................................................................................... 105
Wiring and configuration examples for networking TX devices ................................................................ 107
Create device CD...................................................................................................................................... 111
Creating a CD image file using a data backup ..................................................................................... 111
Downloading the CD image ................................................................................................................. 116
Restarting an interrupted transmission ......................................................................................... 117
Creating a device CD (burning a CD image) ....................................................................................... 119

Flash management ................................................................................................................................. 123
Small device management .................................................................................................................... 125
Configuring small devices ......................................................................................................................... 127
Entering the device name .................................................................................................................... 127
Entering IP addresses .......................................................................................................................... 128
Having the IP addresses automatically defined by the DHCP server (the HEUFT STRATEGY Gate) 128
Entering fixed IP addresses ................................................................................................................. 129
PC management ...................................................................................................................................... 131
Installing the PILOT .................................................................................................................................. 133
Starting the PILOT ............................................................................................................................... 133
Removing the PILOT and all the SPECTRUM TX devices from the service laptop (deinstalling) ...... 134
Installing the PILOT or the device locally (service) ................................................................................... 135
6
Updating the PILOT ............................................................................................................................. 136
Updating the device drivers ................................................................................................................. 137
Installing an available driver ................................................................................................................. 138
Installing a missing driver ..................................................................................................................... 139
Installing a compatible driver ............................................................................................................... 141
Starting the PILOT ............................................................................................................................... 142
Terminal management ........................................................................................................................... 143
Carrying out a PILOT update (optional) .................................................................................................... 145
Carrying out a STRATEGY Gate update (optional) .................................................................................. 147
Software update of SPECTRUM TX devices (from Release 7 upwards) ................................... 149
Carrying out a software update................................................................................................................. 150
Saving SPECTRUM data.......................................................................................................................... 150
Establishing a connection to the SPECTRUM TX device ......................................................................... 151
Selecting a flash bundle............................................................................................................................ 152
Executing the flashing process ................................................................................................................. 154
Reorganising a device .............................................................................................................................. 156
Saving data back to the device ................................................................................................................. 156
Installing device drivers............................................................................................................................. 156
Replacing a faulty hard disk (as from Release 7.00) ...................................................................... 157
Adjusting the calibration of a touchscreen (optional) ........................................................................... 167
Replacing a faulty CF memory card (as from Release 9.00) ........................................................ 169
Installing device drivers ........................................................................................................................ 173
Adjusting the calibration of a touchscreen (optional) ........................................................................... 183
Appendix ................................................................................................................................................... 185
Reading out the SPECTRUM IP address via the operating panel and making a note of it ................. 186
Reorganising the SPECTRUM via the operating panel ....................................................................... 187
Flash codes of the indicator LEDs on the net CPU .............................................................................. 189
Indicator LEDs on the net CPU ............................................................................................................ 192
Indicator LEDs on the CPU3 card ........................................................................................................ 194
7
8
The HEUFT Service Manager is capable of the following
The HEUFT Service Manager is a program only for HEUFT employees, primarily for members of the HEUFT
service desk, who have this program installed on their service laptops.
The program may not be passed on to a third party.
Under no circumstances should the HEUFT Service Center program be installed

on a service laptop. All the functions of the HEUFT Service Center are part of the
HEUFT Service Manager.
The HEUFT Service Center is only intended for customers. There is no

guarantee that both programs will work if they are installed at the same time!
The program has various tools available which can be useful for handling HEUFT devices.
• Saving device data on your local hard disk

• Retrofitting your devices with equipment
• Carrying out an update of the SPECTRUM TX device software (new device driver)
• Carrying out a PILOT update
All these functions are only possible if there is a network connection between the service laptop and the
HEUFT devices. The service laptop is connected to the SPECTRUM TX device via the service port.
The functions of the HEUFT Service Manager are constantly being developed. Therefore the program has a
modular design.
Structure of the Operator’s Manual

The Operator’s Manual comprises three parts:
• General information regarding subjects such as PILOT software, device drivers and equipment
• Functional description of the individual program modules of the HEUFT Service Manager
• Instructions which use several program modules for example the software update
9
Installing the HEUFT Service Manager
The basic installation for the HEUFT Service Manager is carried out by the HEUFT EDP department. An auto
update function is integrated on each customer’s PILOT CD. Each time the HEUFT Service Manager is
started on your laptop with an inserted customer PILOT CD the program checks whether or not a newer
version is available on the CD. The HEUFT Service Manager is automatically updated if this is the case.
The program is installed on your computer both in English and German. The HEUFT Service Manager checks
the “country settings” of the Windows system control. The program appears in German if a German speaking
country has been selected under “country settings”. English is automatically called up for all other country
settings when the program starts.
Never install the HEUFT Service Center program on a service laptop. All the
functions of the HEUFT Service Center are part of the HEUFT Service Manager.
The HEUFT Service Center is only intended for customers. There is no

guarantee that both programs will work if they are installed at the same time!
Debug levels
It is possible to set how many additional messages (debugs) should be displayed under the menu: “help”,
“debug levels”.
No debug outputs You will be spared additional messages.
Some debug outputs You will receive a choice of messages.
All debug outputs You will see all the messages the program can generate.
All important messages are not debug outputs and are therefore always
displayed. The list of files belonging to a data backup count as debug
outputs.
10
Starting the HEUFT Service Manager
with the button for the HEUFT Service Manager in the “servprog” program
Either:
folder on the desktop (the start page) of the service laptop
or: 1. Go to the “C:\HEUFT\devicelist” directory via the Windows Explorer
2. Double-click on “hsm.bat”.
The “HEUFT Service Manager” program will now open.
Help
You can call up help for the current HEUFT Service Manager page using this
button.
11
12
General information
PILOT software
The PILOT software (PILOT driver) is the browser (including the HLAN-Manager and the script server); in
other words the tool which makes it possible to display pages on the TX surface.
New functions are added to each new PILOT software release. These functions are also linked to a net CPU
software version upgrade (i.e. the respective function is only available when both components have been
upgraded).
PILOT software is always downward compatible i.e. older versions of device drivers can be viewed with a
newer PILOT. However certain functions of a new PILOT can be inactive when viewing a device from an older
release with a PILOT from a new release.
It is not possible to display the pages of newer device drivers with older PILOT software.
The PILOT software includes all the admin pages and the texts for them (e.g. the page for defining new
users).
The following is an example of a PILOT version: USER_7.00.012.zip
USER this refers to a customer's version (i.e. PILOT surface without service tools)
When the TX systems were first introduced a distinction was made between the
MASTER (HEUFT service) and USER versions (customer). This distinction will no
longer be made. The basic installation for a HEUFT service laptop is always
carried out by the EDP department at HEUFT SYSTEMTECHNIK GMBH who also
install the special service authorization for the PILOT.
7.00. The PILOT software release version describes the range of functions (new
functions are only possible as from the next upgrade which in turn are linked to a
certain release period).
The figure before the dot refers to the release number. The figures after the dot
represent the possible test pack numbers (special PILOT versions for a specific
customer order with additional or amended functions). The figures 00 mean that
this is not a test pack.
012. A bugfix number, an additional language or a fault which has been found in the
PILOT software and which must be rectified result in a corresponding bugfix (error
correction). The PILOT version number is not increased in the case of error
correction (ONLY the bugfix number => always install the highest bugfix number of
a particular PILOT software release version).
New PILOT software release versions are always made known as production information. This information
outlines the improvements and/or error corrections.
13
PILOT software
The compatibility of the PILOT software versions

A customer has purchased a new HEUFT device. He wishes to view the new device from an older device.
Which measures are necessary so that the terminal of the old device is able to display the PILOT surface of
the new device?
Old device at the PILOT release of the new device /

customer's Updating method for the terminal of the old device
Hardware
version of 1.00 1.01 1.02 1.03 4.00 5.00 6.00 7.00
Release the terminal
1.00 V1 Update 1 Update 1 Update 2 Update 2 Update 2 Update 2 Special
- case
1.01 V1 OK - Update 1 Update 2 Update 2 Update 2 Update 2 Special
case
1.02 V1 OK OK - Update 1 Update 1 Update 1 Update 1 Update 3
1.03 V2 OK OK OK - Update 1 Update 1 Update 1 Update 3
4.00 V2 OK OK OK OK - Update 1 Update 1 Update 3
5.00 V2 OK OK OK OK OK - Update 1 Update 3
6.00 V2 OK OK OK OK OK OK - Update 3
7.00 V3 OK OK OK OK OK OK OK -
8.00 V3 OK OK OK OK OK OK OK OK
Notes regarding the table
OK An update to the PILOT software is not necessary.
- Device and PILOT releases are the same.
The PILOT software of the new device also has to be installed on the terminal of the old
Update 1
device.
The terminal hardware and the hard disk of the old device have to be brought in line with
Update 2
V2 (replacement of terminal and hard disk)
The terminal hardware and the hard disk of the old device have to be brought in line with
Update 3 V2 (replacement of terminal and hard disk).
The following modules are required depending on the type of terminal:
Front panel in a door HBF910000 St Terminal Update from v2 to v3; door
HBF910000 TERM Terminal Update from v2 to v3;

Front panel of a remote terminal
terminal HBD602700 ENG HEUFT Service Manager 3.00.006
Front panel of a TX cover HBF910000 TX Terminal UPdate from v2 to v3; TX
The amount of work required for an update has to be clarified in individual cases
Special case
depending on the device.
The PILOT Release 7 can only be installed on the hard disk of version 2A10 upwards.
Devices (TB/TI) with the net CPU Release 7 only work correctly with the PILOT Release
7.
The complete terminal has to be replaced in order to upgrade TI devices to the PILOT
Release 7. It does not suffice to replace the hard disk due to the fact that the hardware of
the terminal has also changed.
In principle the PILOT from releases with a higher number can always "see" HLAN-
Manager devices from releases with a smaller number.
14
Device drivers
New price lists (new release) appear at regular intervals for the respective devices. The price lists represent a
certain range of functions. All the modules relating to the range of functions of the price list correspond to a
device driver belonging to the release and the device.
The device drivers include all the script pages specifically for a device (in other words main information page,
detection pages, rejectors etc.).
The following is an example of a device driver: INLINE_0700_0000.zip
INLINE this refers to an InLine device driver
0700 Release No. - in the example this is No. 7.00

The Release No. is linked to the price list i.e. the release with the corresponding
number never changes and is therefore given a certain range of functions (range
of functions – please see price list).
0000 Language – in the example this is German and English (language list)
The respective device driver in the language requested has to be installed in addition if further languages are
to be shown on the surface.
For example a Spanish device driver also has to be installed in a device if Spanish texts are to appear on the
PILOT surface.
For example the Spanish device driver INLINE_0700_0004_ddmmyytttt.zip has to be installed in addition to
the device driver INLINE_0700_0000.zip. The characters _ddmmyytttt are optional. The foreign-language
device driver would be completely translated if the characters were missing (all modules as in the German
and English device driver). However since only those modules are generally translated which are required for
an order so-called partial releases are more likely in the case of foreign-language device drivers. The
characters _ddmmyytttt correspond to the issuing date of the foreign-language partial release device driver
(e.g. INLINE_0700_0004_0512031340.zip).
Service pack
A corresponding service pack for the device driver is created if a fault is found on a script page which must be
rectified.
A service pack only comprises the repaired pages and therefore the size of the file is considerably smaller
than that of a device driver.
The service packs are always numbered in ascending order. A new service pack is created with the next
number if a new fault is found. A new service pack automatically includes the pages of the previous service
pack (i.e. only the latest service pack has to be installed). Therefore the file size of the service pack increases
with the service pack number.
The following is an example of a service pack: INLINE_0700_0000.SP2.zip
INLINE this refers to a service pack for an InLine device driver
0700 Repairs relating to the device driver from Release No. 7.00
0000 Language – in the example this is German/English (language list)
SP2 No. of the service pack - in the example this is No. 2
A service pack has to be installed in all the languages installed if foreign-language device drivers have been
installed in the device.
15
Device drivers
In the example the service pack 2 INLINE_0700_0004.SP2_0512031340.zip relates to the foreign-language

partial release device driver "INLINE_0700_0004_0512031340.zip".
As soon as a new release has appeared it automatically receives the repaired pages of the old release. The
service pack number count which relates to the new release begins with 1 again.
Device drivers test pack

Test packs are supplementary drivers for an existing release and have additional or amended functions to
those of the standard scope of delivery.
They only supplement an existing release and therefore the normal device driver must always be installed first
and then the test packs as required.
In the example test pack 5 INLINE_0700_0000.TP5.zip is based upon Release 7.00 (device driver
INLINE_0700_0000.zip).
A test pack has to be installed in all the languages installed if foreign-language device drivers have been
installed in the device.
Test pack 5 in Spanish INLINE_0700_0004.TP5.zip also has to be installed if test pack 5

INLINE_0700_0000.TP5.zip has been installed in a device which also has a Spanish device driver.
Spare parts lists

Each device has an on-line spare parts list. The files (texts, tree structures and pictures) required for
displaying the on-line spare parts list constitute a so-called spare parts driver.
The spare parts driver specifically for a device is a constantly expanding file and has to cover every earlier
device release status (creation date shows amendments).
The spare parts driver is available in different languages. The German/English spare parts driver includes all
the pictures. The foreign-language spare parts drivers only include foreign-language texts. Therefore the file
size of the foreign-language spare parts drivers is considerably less than that of the German/English spare
parts driver.
The following is an example of a spare parts driver: INLINE_SPL_0000_0611031715.zip
INLINE Device type
SPL Designation for a spare parts driver
0000 Language – in the example this is German/English (language list)
0611031715 Creation date – in the example this is 06.11.03 at 17:15

For example the spare parts driver with the designation INLINE_SPL_0004_0611031715.zip is required if a
Spanish spare parts driver is to be installed in addition to the German/English spare parts driver
INLINE_SPL_0000_0611031715.zip. The uniform date means that both spare parts drivers include the same
spare parts.
The spare parts driver includes all the possible device components and therefore spare parts which are not
used in the device are blanked out (⇒ Spare parts list filter, page 17).
16
Device drivers
Spare parts list filter

The spare parts lists always include the maximum equipment. The spare parts lists can be reduced to the
actual device requirements using a new filter function. An additional file is integrated in the device directory for
this (9xGxxxxxx.knf). This file acts as a filter. The complete spare parts list is used if this file is not available.
The file is automatically created as soon as the corresponding editing is carried out. Editing is possible with all
terminals (but only with system administrator user rights) and can be carried out at the customer’s or be
prepared by the project department.
The edit mode is started via the context-sensitive menu. Focus on the spare parts list icon and then actuate
the context-sensitive menu button.
The spare parts list is displayed after the edit mode has been started. The respective spare part must be
selected if it is not displayed and the context-sensitive menu button actuated. Select the "blank out" selection
item.
Spare parts which are blanked out during normal operating mode have a blue frame.
When you wish to leave the page using the button you are asked whether you wish to save the node
filter.
The filter file (9xGxxxxxx.knf) is an ASCII file which can be viewed with Wordpad. The file is prompted in the
device directory of the HLAN-Manager. The file includes the articles and nodes which should not be displayed
in the on-line help.
17
Device drivers
General information regarding the installation of drivers

Care must always be taken in the case of devices with several languages that all service and test packs are
installed in all the languages. If this is not observed a mixture of English and foreign-language texts could
appear on the pages of the PILOT surface. A translation fault generally comes to mind first. However in 99%
of such instances it emerged that the PILOT, service or test packs were not installed in all the necessary
languages. After selecting the button in the system settings/system info menu a quick look shows a
list of all the drivers installed.
Hard disk version

PILOT version
Settings
GROUP entries
HLAN-Manager
List of the device Script server
drivers
Device drivers
Connected terminals
When a driver is missing in the foreign language confusing texts appear as previously described.
PILOT CDs specifically for a device will be prepared as from Release 7 which only include the drivers relating
to a device (languages, service packs, spare parts drivers). The install device drivers function automatically
selects all device drivers for installation.
There was another tool for installing drivers prior to Release 7 and this tool was supplied with the PILOT CD
as well. PILOT CDs specifically for a device (there were always all sorts of drivers on the CD) did not exist and
therefore authorisation to install a driver was given via a corresponding key code. The key code was
automatically generated within the context of creating a device data sheet or retrofitting data sheet. This had
to be read from the data sheet during the installation of the required driver and entered manually in the
enquiry which appeared regarding the key code. The installation of the required driver could only be carried
out by entering the correct key code.
In principle service packs could be entered without a key code. The service technician is authorised to install
service packs for a standard device (without test packs or edited pages). Service packs may only be installed
after consulting the project department if the device has text packs or edited pages.
A data backup must be extracted to your service laptop in order to

establish whether a device has edited pages (⇒ Saving data, page 41).
If the data backup includes a subdirectory “all” then the device has edited
pages.
18
Device drivers
Language list
Each available language is represented by a number. At present these language numbers are defined as
follows:
1 English
2 German
3 French
4 Spanish
5 Portuguese
6 Italian
7 Danish
8 Swedish
9 Norwegian
10 Finnish
11 Dutch
12 Polish
13 Czech
14 Hungarian
19 Greek
20 Russian
21 Chinese
0000 as a language description in a zip file always means German and English. German and English are
automatically part of each TX device. Additional languages are optional sales modules.
A translation into a foreign language (with the exception of English) is always carried out in relation to an
order. This means that only the modules relating to an order are translated.
19
Reorganisation
A new permanent component table is created in the FlashPROM of the net CPU during the reorganisation
procedure.
The table of modules includes a precise list for each CPU card of the modules available in the system. There
are always two of these tables of modules in the system. A table of modules is always permanently stored and
another one is created each time the system starts (temporary table of modules).
When the system starts all the CPU cards report to a particular module with the modules they have used and
this module then creates the temporary table of modules. The contents of this are compared with the other
permanently stored table of modules.
Either a fault exists (e.g. one of the CPU cards has not run up properly) or a software update has occurred if
there are differences between the two tables of modules.
The reorganisation procedure is always necessary after a software update so that the changed or new
modules are entered in the permanent table of modules.
During the reorganisation procedure nearly all the SPECTRUM parameters are
deleted in addition to the new creation of the permanent component table
(tantamount to a new device in the old system). However the program definitions
remain. Therefore after a reorganisation procedure in the case of devices up to
Release 7.00 the old data backup must always be imported.
A data backup is filed to the "external flash memory" by the operating system of
the net CPU before the actual reorganisation procedure is initiated in the case of
devices from Release 8.00 upwards. This is automatically re-imported after the
reorganisation procedure. The "reload" message appears on the terminal during
this procedure.
Therefore manually importing a data backup is not necessary in the case of

devices from Release 8.00 upwards. However this does not apply to a release
update from an older release version to Release 8.00.
Equipment HBD602700 ENG HEUFT Service Manager 3.00.006
Certain functions in the software can be activated due to the equipment (e.g. the connection of additional
triggers).
In principle two different types of equipment are differentiated as from Release 4.00 upwards. On the one
hand there is equipment which can be freely changed e.g. changing the moving direction of the display on the
info page.
In addition there is the so-called optional equipment. There are functions hidden behind the optional
equipment which the customer has to pay for e.g. the changeover from a standard HF fill level detection to an
HF foam.
Optional equipment cannot simply be permanently changed by a service technician on-site. Such changes to
the equipment can only be carried out at the HEUFT premises. A current data backup has to be produced for
this first and then sent to HEUFT completely (e.g. by e-mail).
20
Equipment
The equipment is changed accordingly within this data backup (changes to the *.radf file). The amended *.radf
file is given a new file name (*N.radf). The N shows that the manipulated radf was supplied as a retrofit (e.g.
9KG000001N.radf).
The amended data backup is then sent to the service technician on-site. He imports the data backup to the
SPECTRUM device. The SPECTRUM device works with the amended equipment the next time it is started.
Equipment flags
Equipment flags can be defined under "Setting equipment", page 79.
Attention: this function is supported by the net CPU as from version Net001xx. This function is not available
on older devices.
For further information please refer to the MasterDataOrganizer on the

technicians' CD.
21
22
Equipment

Clearing the HEUFT Service Manager for users
The HEUFT Service Manager is only operative after clearance as from Release 8 upwards. Clearance occurs
using a code which can be generated from the HEUFT Portal. The HEUFT Service Manager is cleared for 12
weeks after generating the code. A new clearance code which is valid for a further 12 weeks must be loaded
from the HEUFT Portal after the clearance period has expired. Only those who have access to the Portal can
obtain a clearance code.
How long the clearance for the HEUFT Service Manager is still valid is stated in the title.
In the example clearance for the HEUFT Service Manager is still available until 11:12:34 on 14 January 2005.
At the end of this period of time the HEUFT Service Manager will no longer start unless you have a new
clearance code.
In order to enable the HEUFT Service Manager to work you must load your clearance code from the Portal
under "user data", "user option".
The prompting window is behind "refresh clearance for HEUFT Service Manager":
1. Press the button in order to request the clearance code.
The "Portal" generates the code and sends it to you by e-mail.
2. Save the code ("hsmreg.key") from the e-mail on your own hard disk.
3. Start the HEUFT Service Manager.
23
4. Log in using your user name and password for the Portal. This has to be the password with which you
requested your clearance code.
5. Select the clearance file "hsmreg.key" which you have saved on your hard disk.
A message appears which confirms that clearance was successful and states how long clearance is still valid.
6. Restart the HEUFT Service Manager.
A new clearance code can be requested before the old one has expired. This is
advisable before longer service visits as long as simple access to the Portal is still
possible. Each new clearance code permits access for the next 12 weeks.
24
Renewed clearance for the HEUFT Service Manager

Renewed clearance is possible under the "file" menu and the "clear again" submenu.
1. Start the HEUFT Service Manager.
2. Select the menu "clear again".
3. Continue as described above in numbers 4 to 6 (⇒ Page 24).

25
26
Decoding the CD-ROM
The service CD and other HEUFT internal CDs are coded and are not readable without the HEUFT Service
Manager. Decoding is carried out under the "tools" menu.
1. Place the coded CD in the CD drive.
The CD starts but the contents cannot be opened.
2. Select the "start CD-ROM decoder" button in the "tools" menu of the HSM:
3. Confirm the inquiry.
CD decoder has been activated. You have access to the files.
Deactivating the CD decoder

1. Select the "cancel" button in order to deactivate the CD decoder.
You can now continue to access the CD until you close your application or file. You will require the HSM CD
decoder again the next time you access the CD.
27
28
Decoding the CD-ROM

Device management
With the device management system it is possible to:
send equipment
set equipment
allocate container and case pictures
save data
transfer data backups to the TX archive
carry out software updates (flash management)
configure device search (HSC)
install device drivers
install device drivers (service)
set up a device connection
manage inspection pictures
create an overview of the cards
flash the net CPU
configure the network
create device CD
29
30
Configuring device search with the HEUFT Service Manager
Connection via the service port of the SPECTRUM TX
A separate configuration for the device search is not necessary if you connect your
service laptop to the service port of the SPECTRUM TX provided. The default
settings suffice in order to create a connection between service laptop and
SPECTRUM TX.
Service laptop
with DHCP
function
Transposed UTP cable
Net CPU card with

active routing
function.
Transposed UTP cable

Port 1 HLAN (network to other SPECTRUM devices) Terminal (TI or TN) with
Port 2 Terminal (TI or TN)
Port 3 Service laptop
DHCP function
Port 4 Not used at present
You can generally reach the service port with a transposed UTP cable at the
device and do not have to connect a cable directly to the net CPU card.
Service port Service port in the door of the

InLine camera box
Take care that water does not enter the device if it is necessary to open doors as
in the case of the InLine camera box. Never leave the device unattended when
operating with open doors.
Connection via the network configuration

Device search via a network connection with the HSM is only necessary when you cannot connect your
service laptop to the device and have to connect to the network from somewhere else.
The IP addresses can be entered manually for the connection build-up or the devices can be found in the
network using a user-friendly scanning process. The inputs for the “device search” must only be completed
once so that the scanning process can be carried out in the network.
31
The inputs are saved and the HEUFT Service Manager uses these settings each time the program restarts.
Even if the menu is “configure device search (HSC)” continue to work with the
HSM (HEUFT Service Manager) and not the HSC. The name of the menu relates
to its development and cannot be changed at present.
On this page you can define in which areas the program should search for “network devices” and in which
directories for “local devices” and “archive devices”.
A search for devices which are installed in the HLAN (HEUFT Local Area
Network devices
Network) or in the customer’s LAN.
A search for devices which are installed on your service laptop as a PILOT or
Local devices devices for which your service laptop serves as a server (HLAN Manager). The
latter are TB devices without an HLAN Manager at the customer’s.
Archive devices A search for devices which are archived on your service laptop or a server.
Setting up network devices

The program automatically enters a number of preallocated broadcast IP addresses in the “network devices”
line. The broadcast IP addresses correspond to the standard factory adjustment for a HEUFT network
(HLAN).
The set-up for the network devices can be tested in order to check whether or not you can establish a
connection to the HEUFT devices:
1. Click on “network devices” at the bottom left of the selection window.
2. Press scan button and wait for scanning process.
32
All the devices which have been found in the network can be seen at the bottom left of the selection window.
Please contact your network administrator if the program does not find any
devices. Repeat the scanning process for network devices after your have entered
your broadcast IP address or the IP address of the HLAN Manager. Confirm the
entry of IP addresses with the enter key.
33
Setting up local devices

Local devices are those devices or data backups which have been installed on the hard disk of your service
laptop.
1. Click on the upper button “open directory”.
2. Select the directory where the local devices have been stored.
It is advisable to put the local devices in the C:\heuft\hlan\hlanmanager directory

due to the fact the data backup also accesses this directory ⇒ Saving data, page
41.
3. Click on “local devices” at the bottom left of the selection window.
All the devices which have been stored in the directory selected can be seen at the bottom left of the selection
window.
34
Setting up archive devices

User-friendly access to the archived devices is possible by allocating a corresponding directory if you wish to
file the data backups for the HEUFT devices to a separate server or to a special directory.
1. Click on the lower button “open directory”.
2. Select the directory where the archive devices have been stored.
3. Click on “archive devices” at the bottom left of the selection window.
All the devices which have been stored in the directory selected can be seen at the bottom left of the selection
window.
35
36
Allocating container and case pictures
A picture of the container or case (crate, cardboard box) can be allocated to each program (brand) on your
HEUFT TX device which can then be displayed on various PILOT pages. On which pages this "brand picture"
can be viewed depends on the device type.
The photographs must be stored in *.jpg or *.jpeg file format on your computer or on a drive to which your
computer has access.
1. A data backup must be carried out before you allocate your container or case pictures so that the
HEUFT Service Manager knows the current state of your device (⇒ Saving data, page 41).
2. Go to the "allocate container and case pictures" page.

37
3. Select the device from the network device list with which a connection is required or enter the IP
address of the device under "contact IP address".
The HEUFT Service Manager loads the program names of your device from the latest data backup to the
window on the right.
Allocating the picture of a container or a case to a program

4. Select the program from the list to which you wish to allocate a picture.
38
5. Press the button in order to open the window for the directory and file search.
6. Select the file of the picture to which you wish to allocate the program.
The original files of your pictures are not used for the display on the PILOT surface
of your device but your pictures are copied and the copies changed to the
appropriate picture size. Your original files are not changed.
7. Select the pictures and allocate them to the programs until your configuration has been completed.
Sending the allocation data to the HLAN-Manager

At present the allocation is only active within the HEUFT Service Manager. The allocation is only kept
permanently if the configuration has been stored permanently on your HEUFT device.
39
8. Transmit the allocation of the pictures to the programs of the HLAN-Manager of the device with the
button.
The HEUFT Service Manager asks you to carry out a new data backup in order to update your data backup
after a safety inquiry.
It may be necessary to restart the PILOT in order to view the new pictures on the
PILOT.
Cancelling the picture allocation currently selected

It is possible to cancel the allocation of a picture to a particular program.
1. Select the program from the list for which you wish to cancel the picture allocation.
2. Cancel the allocation of the picture to the program with the button.
There is no longer a picture allocated to this program. At present the cancellation of this allocation is only
active within the HEUFT Service Manager. The allocation data must be sent to the HLAN-Manager with the
left button in order to permanently store these in the device.
Deleting the allocation of all containers or case pictures in the device

The allocation of all pictures is stored in the HLAN-Manager of your device. It is possible to cancel the
allocation of all the pictures to the programs in one step.
1. Cancel the allocation of all pictures to the programs with the button.
The safety inquiry indicates that the picture files originally selected (your originals) have not been cancelled.
Now no program has been allocated a picture. The allocation of all container or case pictures on your
computer and in the device (with the HLAN-Manager) has been cancelled.
40
Saving data
A data backup for a device can be carried out on this page. The data is stored on the computer on which your
HEUFT Service Manager is installed. A data backup is not possible from a local or an archive device.
A connection with the device must be set up using the HEUFT Service Manager
before a data backup can be created. There are two possibilities for creating the
connection:
Enter the contact IP address of the device.
Select the device using the network search.
Entering the contact IP address

1. Enter the IP address of the device under "contact IP address".
2. Confirm this entry with the enter key.
3. Continue with ⇒ Creating a data backup, page 43.
Selecting the device using the network search

1. Select "network devices" below left in the selection window.
41
Saving data
2. Click on "broadcast" with the left mouse button and then on "start scanning" with the right mouse
button. Wait for the scanning process.
3. Select the device number from the list of devices found for which you wish to save the data.
It is possible to select the device alternatively using the "IP history" without "start
scanning" if you have already selected the device once before. The IP history
lists the last ten selected devices in chronological order.
The IP address of the device selected is displayed in the input field at the top.
42
Saving data
It is possible to read out the IP address on the operating panel of the device if the
device you are looking for cannot be found on the basis of the list ⇒ Reading out
the SPECTRUM IP address via the operating panel and making a note of it, page
186.
Creating a data backup
This speeds things up!

This speeds up the creation of a new data backup for devices as from Release
10 if you already have a data backup (out-of-date) on your laptop or you have
saved a data backup from the TX archive to your laptop. In such cases the HSM
first compares the backup on the laptop with the current data status on the
device and determines the differences. The HSM only downloads the changed
data afterwards and updates the data backup on the laptop with this.
The HSM has to download the complete database if you have not saved a data
backup to your laptop which can take many times longer. It is faster the next
time.
The program shows whether a data backup of the device has already been saved to the service laptop and
whether it is available. "No backup available" is under "backup status" if a data backup does not exist. The
status "backup available" appears if a data backup exists on the laptop.
1. Save the data for the device selected using the button.
The data backup of the device has been saved to the service laptop and is available if the "info SPECTRUM
data" shows the date and time for which you have created the data backup.
43
Saving data
The program places the data backup in the C:\heuft\hlan\hlanmanager directory.

The program creates a subdirectory for each device with the device number
allocated by HEUFT (e.g. 2PG001234) if such a directory is not already available.
device number.spc Device file (includes a list of all the modules, menu pages and help manuals)
device number.prg Program names

The program names will be stored on the net CPU as from Release 7 onwards
and will no longer appear in the data backup.
device number.prp Backup up of the container names and reject definitions which the operator can
enter. At present this is only used during the sorting process.
device number.dat Users, their passwords and user rights as well as language and preference page
device number.radf Data backup which has been created by a service technician (a so-called backup
file). The customer can overwrite this data backup at any time with the HEUFT
Service Center.
device number_x.radf Data backup which has been created from the PILOT surface (can also be carried
out by the customer).
device number.mel Message stack
device number.knf Spare parts list filter (fading out of spare parts which are not required)
device number.txt Readme text file displayed on the PILOT surface (information regarding special
features)
44
Saving data
Restoring the data backup on the device selected
New optional equipment cannot be imported with the restore function only the
equipment of the data backup. Additional optional equipment is only possible with
⇒ Sending equipment, page 77.
A data backup available on your service laptop can also be installed on the device as a restoration on this
page. The current device data will be overwritten as a result. There are two options available for the
restoration:
⇒ "local (standard)" restoration, page 45
⇒ Free RADF selection, page 47
You will generally carry out a "local (standard)" restoration.

The "free RADF selection" only occurs in special cases when you wish to copy
the data from a SPECTRUM TX device to a similar type of device.
"local (standard)" restoration

Stop the conveyor at the device and secure it to prevent it being
inadvertently switched on before restoring a data backup!
The emergency off push-button must be pressed if the device has an emergency
off push-button.
When restoring a data backup the data currently available in the device is deleted
and overwritten with the new data.
1. Select a device (Entering the contact IP address ⇒ Page 41 or Selecting the device using the network
search ⇒ Page 41).
45
Saving data
2. Copy the data backup (restoration) to the device using the button
(the data is copied to the SPECTRUM device and to the HLAN manager).
3. Confirm the safety enquiry with "OK" if you have stopped the conveyor and secured it to prevent it
being inadvertently switched on and wish to start the data backup restoration.
4. You can decide afterwards whether you wish to "save data without equipment..." or "...with equipment
to SPECTRUM device".
The "save data with equipment to SPECTRUM device" button on the right is generally selected. Press
the button "…without equipment" if you are not sure whether or not the equipment should be changed
(⇒ Equipment, page 20).
46
Saving data
Free RADF selection

Restoring with a free RADF selection is different to the standard restoration. You can choose the data backup
(in other words the *.radf file) yourself in the case of the free selection.
It only makes sense to transfer SPECTRUM TX device data to another

SPECTRUM TX device in special cases. This includes the case that all brands
are run on two lines. In this case the parameters determined for one device can
be transferred to another device of the same type (e.g. from InLine to InLine).
The restoration filter is used if only individual programs are to be copied to

another device (⇒ HSM restoration filter, page 49).
Please note that all the data is transferred at the same time. It is possible that line
/ device specific data is overwritten.
It is always advisable to create a data backup beforehand ⇒ Saving data, page

41.
Optional equipment cannot be imported during restoration with a free RADF

selection either. The equipment is always related to a device and therefore
cannot be copied to another device. Data is always saved without equipment in
the SPECTRUM device.
1. Select a device (Entering the contact IP address ⇒ Page 41 or Selecting the device using the network
search ⇒ Page 41).

inadvertently switched on before restoring a data backup!
The emergency off push-button must be pressed if the device has an emergency
off push-button.
When restoring a data backup the data currently available in the device is deleted
and overwritten with the new data.
2. Click on the button.

47
Saving data
3. Click on the button - "load backup (RADF) from any position".
load backup (RADF) from any position
The window for directory and file search opens.
4. Select the data backup (*.radf). As a rule the *.radf files are in the C:\heuft\hlan\hlanmanager directory.
The file name nearly always begins with the device number (e.g. 2PG012345.radf).
5. Copy the data backup (restoration) to the device using the button.
being inadvertently switched on and wish to start the data backup restoration.
The *.radf selection can be cancelled with the button. Another *.radf file or
the standard restoration can then be selected if required.
48
Saving data
HSM restoration filter

Individual programs can be imported to a device using the HSM restoration filter. It only makes sense to
transfer SPECTRUM TX device data to another SPECTRUM TX device in special cases. This includes the
case that one or several brands are run on two lines. In this case the program parameters determined for one
device can be transferred to another device of the same type (e.g. from InLine to InLine).
In addition the selection can be restricted to certain modules of a program.
Transferring complete programs
1. Select the data backup (*.radf) of the device which contains the source program which is to be
transferred to the other device.
2. Select the restoration filter with the button after the manual radf selection (⇒ Free RADF
selection, page 47).
3. Allocate a target program to the source programs.

49
Saving data
Up to five programs can be selected and copied at the same time in the case of
devices up to and including Release 9.
4. Switch the allocation to "active".
5. Select "use restoration filter".
50
Saving data
6. Do not close the HSM restoration filter window.
The HSM cancels the allocation between the source program and the target
program if you close the window with the button.
7. Change to the "data backup" page without closing the HSM restoration filter window. The HSM
restoration filter window is an independent window of the HSM which closes automatically after the
data has been copied.
8. Copy the data to the device with the button.
being inadvertently switched on and wish to start installing the selected programs.
The *.radf selection can be cancelled with the button. Another *.radf file or
the standard restoration can then be selected if required.
51
Saving data
Transferring individual modules
1. Carry out steps 1 to 3 (⇒ Transferring complete programs, page 49).
2. Select the magnifying glass button of the program from which you wish to take over individual
modules.
3. Select one or more modules - in the example this is the vent slot and neck ring inspection.
4. Confirm with the button.
Use the button to change your selection and to make a new

selection..
5. Switch the allocation to "active".
6. Select "use restoration filter".
52
Saving data
7. Do not close the HSM restoration filter window.
The HSM cancels the selection of the modules if you close the window with the
button.
8. Change to the "data backup" page without closing the HSM restoration filter window. The HSM
restoration filter window is an independent window of the HSM which closes automatically after the
data has been copied.
9. Copy the data to the device with the button.
being inadvertently switched on and wish to start installing the selected program data.
Installing a parameter set

This function makes it possible to install parameter sets:
• for the XY rejector as from Release 10 in order to install new rejection curves (par files)
• for the beetec motor control (blk files)
• for the TORNADO rotating platform control (blk files)
A radf file created by the TFE department has to be installed on the device in order
to install new rejection curves for the XY rejector prior to Release 10 (⇒
Restoring the data backup on the device selected, page 45).
1. Select the button.
53
Saving data
2. Click on the button - "load the files from any position".
3. Select the parameter set (*.par, *.blk). The files are in the directory in which you have filed your file(s)
on your laptop.
4. Enter the number of the program which you wish to install under "target program selection".
The module which should receive the parameter set is not online if the text
"information on parameter set" is red. The

button is not active in this case (selectable).
5. Install the parameter set to the device with the button.
54
Saving data
The file selection can be cancelled with the button. Another file can be
selected afterwards if required.
being inadvertently switched on and wish to start installing the parameter set.
55
56
Saving data

Transferring data backups to the TX archive
It is possible to transfer the device backups saved in the "C:\heuft\hlan\hlanmanager" standard directory as
complete data backup (hba file) via Internet to the HEUFT TX archive using this page. Data backups of
HEUFT TX devices are saved in the HEUFT TX archive and are available via the HEUFT Portal.
The HSM creates a file of the "HEUFT data backup archive" type (hba) for archiving a device data backup. Its
name is composed of "{device number}_{time stamp YYYYMMDDhhmmss}_{user}.hba" (e.g.
2XX000001_20070731151341_ksm.hba).
If there is no connection to the Portal when this page is used, at least a data
backup file (hba file) can be created by means of this function. The hba file has the
advantage that the HSM checks the zipped data backup for its consistency
(completeness and plausibility with regard to contents). There are two possibilities
to place an hba file subsequently as data backup in the TX archive. One option is
to transfer the hba file by means of the HSM when there is again access to the
Portal. The other option is to copy the file into the "txarchive" directory of the office
gateway of the respective HEUFT subsidiary.
The files from the "txarchive" directory of the office gateway are automatically
copied into the HEUFT TX archive.
It does not make sense to transfer hba files via e-mail because the files of devices
as from Release 10 are too large for this means of transmission.
The first step to a "HEUFT backup archive" (hba) is the usual data backup by means of the HSM (⇒ Saving
data, page 41). The HSM can create a hba file based on this data backup.
This hba file contains the consistent data backup of the device, a preparation report and check data for the
archive validity.
The hba file is allocated to the HSM user who has created the file so that a personal confirmation e-mail can
be sent to this user when the file has been placed on the TX archive.
57
Data saving via Internet into the TX archive
General note on carrying out the hba uploads via a HEUT Gateway Server at
the customer's
The possible Internet functions (e-ail, Portal access, FTP access) depend directly
on the firewall of the customer's network if the HEUFT Gateway Server
establishes the Internet access via the customer's LAN (i.e. not via modem). Thus
one or several functions are possibly not available depending on the customer's
firewall setting.
In the case of missing or restricted FTP access messages such as "access
denied" or "permission denied" indicate that the hba upload cannot be carried out.
If it is possible to consult with the customer's IT administrator, it should be asked
whether the port range 56629-56758 can be released for the HEUFT Gateway
Server. After that free FTP access should be possible.
The data backup date can be found in the table in the column next to the device in the standard directory
(C:\heuft\hlan\hlanmanager). The creation date of the hba file can be found in the right column ("last
archived"). An "unknown" note is displayed if there is no hba file available yet.
58
1. Press the button to check the standard directory for data backups C:\heuft\hlan\hlanmanager\.
The HSM displays the current state of the data backups:
green local archive (= hba file) available, which has already been transferred successfully to the
server by the HSM
yellow local archive (= hba file) available, which has not yet been transferred via Internet to the
server ("local")
red no archive (hba file) available yet ("unknown") or the existing archive (= hba file) contains a
data backup which is older than the data backup in the standard directory ("obsolete").
When you click on the "device", "backup date" or "last archived" tabular insert the
table will be sorted according to the respective column. An example: in the case of
the "backup date" tabular insert the table will be sorted according to the creation
date either in ascending or descending order.
2. Press the button to view the entire contents of the data backups check.
The button is marked by a warning triangle when inconsistent data backups are discovered.
Inconsistent data backups are listed in the report. However, they cannot be archived. New backups have to
59
be carried out in these cases.
When the indicator is moved onto the button the list of inconsistent
data backups is displayed.
Consistent data backups can always be archived locally. If there is an internet connection and if the HEUFT
Internet server is available the newly created archives can be placed directly on the TX archive. The server
availability is automatically monitored in the background.
The devices which still have to be archived are automatically selected (tick before the device). The selection
can be changed by clicking the ticks away or by placing the ticks.
You must first create a local data backup (hba file) if you wish to transfer a device
marked in red as data backup to the HEUFT Internet archive.
Tick those devices which are to be archived locally.
When all devices are to be selected or deselected the buttons can

also be used.
select all deselect all

devices devices
Archive the selected devices "locally" on your hard disk by pressing the
button.
Confirm the safety inquiry if you want to archive the device locally and thus create
a hba file.
The updated status now displays the device with a yellow background:
60
3. Establish an Internet connection if no connection has been established yet. The status display on the
HSM page indicates whether there is an Internet connection.
The processing times of the HSM (particularly during a status refresh when the
standard directory is being checked) can be considerably slowed down because
an activated virus scanner must be used with an existing Internet connection.
4. Press the button to start the transfer to the HEUFT Internet archive via the Internet.
5. Confirm the safety inquiry when the selected data backup is to be transferred to the HEUFT Internet
archive.
Afterwards the transfer is started and clearly shown by a transfer monitor:

The "upload completed" message window is displayed upon completion of the transfer. The employee
creating the hba file will be informed about the archiving per e-mail.
You can finish the transfer later on if you are forced to interrupt it with the "cancel"
button because you urgently need the service laptop for another task. Data
already transferred need not be sent again which reduces transmission time.
The message "The transfer was discontinued by the user." will be displayed after
cancelling and confirming the safety inquiry.
61
You can continue the transmission of the remaining data to the HEUFT Internet
archive by pressing the button.
A message indicates which data size has already been transferred and which is
still to be transferred:
The message "upload completed" appears when the data transmission has been
finished successfully.
The display on the HSM page is updated and the new status of the data backups is indicated.
The selected devices have now been archived and have a green background.
Restarting the data transmission after an external interruption

Due to a low Internet transmission rate and depending on the device type HEUFT Backup archives (hba files)
may assume file sizes which require a long transmission time despite compression. In the case of
disconnections the data already transferred does not need to be sent again, which reduces transmission time.
The following message will be displayed when the Internet connection is interrupted.
You can restart the transmission of the remaining data to the HEUFT Internet archive by pressing the
button as soon as the Internet connection has been restored.
62
A message indicates which data size has already been transferred and which is still to be transferred:
The message "upload completed" appears when the data transmission has been finished successfully.
63
Manual data saving to the TX archive
If the hba file is not transferred directly to the HEUFT Internet server it can be copied manually to the TX
archiving setting directories (e.g. this can be carried out by an appropriate employee after the user has
received the hba file via e-mail).
The local archives are stored parallel to the device directories also as hba files directly in the standard
directory on the service laptop.
From now on only hba files must be used for the setting. These hba files must be
copied manually. The hba files replace the device directories and manually
created zip archives.
Local data backups

If there is no Internet connection a "HEUFT backup archive" (hba file) of "red" devices which have not been
archived yet can be created by pressing the button. The status switches to yellow, the date
and time in the "last archived" column are provided with the additional information "local".
64
Installing device drivers
The standard installation for device drivers is described here. All the device drivers on the PILOT CD will be
installed. This is the case as a rule. Installing all the available device drivers at the same time prevents
unnecessary mistakes by selecting the incorrect device drivers. However if you receive separate device
drivers by other means such as by e-mail please refer to the following page ⇒ Installing device drivers
(service), page 69.
A new device driver can

• install additional user languages on the device or
• include a service pack which can improve the function of the SPECTRUM TX device or
• update the spare parts list as a result of a new measuring bridge retrofit or
• equip a new small device (such as the HEUFT xio) for the first time with a device driver.
For further information regarding device drivers please refer to ⇒ Device drivers,
page 15.
The device driver versions which have actually been installed in the device can be checked by selecting the
button in the system settings/system info menu.
hard disk version

settings
GROUP entries
HLAN-Manager
script server
device drivers
connected terminals
65
With the help of the PILOT CD it is possible to install a new device driver.
Installing a new device driver
1. Place the PILOT CD-ROM in the CD-ROM drive.
2. Select the device from the device list which is to receive a new device driver or enter the IP address of
the device under “contact IP address”.
3. Start the evaluation of the PILOT CD-ROM inserted using the lower button.
66
The program displays the evaluation of the PILOT CD-ROM inserted.
4. Press the installation button .
5. The program displays which drivers are available on the PILOT CD-ROM. Confirm the inquiry with OK
if you wish all the drivers selected by the program to be installed. Discontinue the installation if you do
not wish the selected drivers to be installed.
Please refer to the following page ⇒ Installing device drivers (service), page 69
should you only wish to install separate device drivers and not all of them.
6. After the new device drivers have been successfully installed (as from Release 9) the program issues a
message.
7. Please pay attention to the information given in the message. Only switch the device off and on again if
the graphic pictograph on the PILOT surface can no longer be viewed. If the device is operated
from a remote terminal then this terminal must also be switched off and on again.
Resetting device drivers to original adjustment

The device drivers with the "old" PILOT CD-ROM can be reset to the original adjustment if you wish to
recreate the situation before the new device drivers were installed. The procedure is the same as if new
device drivers were installed.
67
68

Installing device drivers (service)
It is possible to install separate device drivers or test packs here whereas only complete driver packages can
be installed on the “installing device drivers” page.
Only use this function in exceptional cases. All device drivers are generally installed at the same time (⇒
Installing device drivers, page 65).
For further information regarding device drivers please refer to ⇒ Device drivers,
page 15.
The installation of separate device drivers or test packs is necessary when contrary to expectations the PILOT
CD which you have brought with you and which relates to the device does not include all the necessary
device drivers. Therefore you have requested one or more new device drivers from the program production
department at HEUFT and received this/these by e-mail. Save the new device drivers on your service laptop.
On this page you can
install additional device drivers and
additional test packs.

It is possible to install separate device drivers or test packs here whereas only complete driver packages can
be installed on the “installing device drivers” page.
The installation of separate device drivers or test packs is necessary when contrary to expectations the PILOT
CD which you have brought with you does not include all the necessary device drivers. Therefore you have
69
requested one or more new device drivers from the program production department at HEUFT and received
this/these by e-mail. Save the new device drivers on your service laptop.
1. Select the device from the device list which is to receive the new device driver or test pack or enter the
IP address of the device under “contact IP address” and confirm the entry.
2. Select the or button according to what you wish

to install.
3. Select the device driver or the test pack (*.zip). These files are generally saved on your service laptop.
The program displays the evaluation of the files selected. All the drivers (service packs, operator languages
…) or test packs appear on a list.
4. All the drivers with a tick in front of the driver type can be installed. Click away the ticks of the drivers
you do not wish to install. Take care to install the service and test packs in all the customer languages
otherwise not all texts will be displayed in the language of the country.
70
5. Click on the button at the bottom of the page in order to install the drivers or
the test packs.
6. After the installation has been successfully completed the program issues a message and asks you to
switch the device off and then on again. If the device is operated from a remote terminal then this
terminal must also be switched off and on again.
The spare parts list filter has to be adapted if you have installed a new version of
the spare parts list (⇒ Spare parts list filter, page 17).
All service and test packs must be uniformly installed in all the languages
required:
71
72

Setting up a device connection
This function is only required in special cases.
The entries under ”hlanmanager_ip” in the pilot.ini file are added to and the
”devicelist.ini” is expanded by ”setting up a device connection”.
You can connect your service laptop with devices on this page which you cannot reach via broadcast. This
can be the case when a device is the other side of a router and the network administration does not allow a
broadcast beyond the router. The program sets up the connection between the PILOT on your service laptop
and the SPECTRUM TX device using the IP address.
A PILOT must be installed on your service laptop in order to set up a device

connection (⇒ Installing the PILOT, page 133).
In addition to this the PILOT must be newer or just as new (current) as the device
to which you wish to connect your service laptop. This means that your PILOT
must be at least a Release 7.00 version if the device is available as a Release 7.00
version.
Your PILOT must be updated if it is a lower release than your device. This is
possible with the PILOT CD of the SPECTRUM TX device with which you wish to
be connected (⇒ Installing the PILOT, page 133).
The release versions can be checked by selecting the icon in the system settings/system info menu.
Hard disk version

PILOT version
Settings
GROUP entries
HLAN Manager
Script server
Device drivers
Connected terminals
The contact IP address for the SPECTRUM TX device can be found on the PILOT
operating surface under ”system menu, system settings , system info” as an IP
under ”SPECTRUM TX”.
It is possible to read out the IP address on the operating panel of the device if the
device does not have a PILOT operating surface ⇒ Reading out the SPECTRUM
IP address via the operating panel and making a note of it, page 186.
73
Setting up a device connection
address of the device under ”contact IP address” and confirm the entry.
2. Press the ”set up device connection” button .
After successfully setting up the device connection the device is now connected to your service laptop.
Your PILOT can be started with the button and the operating surfaces of all the devices with which you
are connected can be viewed.
74
Separating a device connection
This function is only required in special cases.
The entries under ”hlanmanager_ip” in the pilot.ini file for the devices are deleted
and the connection separated by ”separate device connection”. These devices are
also removed from the ”devicelist.ini”.
You can separate the connection from your service laptop to the PILOT operating surface of a SPECTRUM
TX device.
1. Select the device from the network device list or enter the IP address of the device under ”contact IP
address” and confirm the entry.
2. Press the “separate device connection“ button .
The device is now no longer connected to your service laptop. You can no longer view the operating surface
of this device from your service laptop.
75
76
Sending equipment
New additional device functions (so-called retrofits) can be installed on your SPECTRUM TX device by
sending equipment to the device (⇒ Equipment, page 20).
You have received a file (*.radf) suitable for the device either on diskette or by another means (e-mail or CD-
ROM) if you wish to install a retrofit on one of your SPECTRUM TX devices. The file name always begins with
the device number (e.g. 2PG012345.radf).

inadvertently switched on before sending any equipment!
The EMERGENCY OFF push button must be pressed if the device has an
EMERGENCY OFF push button.
The device must be reset after a retrofit has been installed. The functions of the
retrofit must be put into operation afterwards.
1. You can either select the device from the selection list, bottom left of the network devices, (the program
then shows the IP address automatically)
or enter the contact IP address of the device which you wish to retrofit.
77
Sending equipment
2. Please select whether

you wish to retrofit an option from a diskette (retrofitting drive A) or
from the hard disk or the CD-ROM drive (free choice).
3. Select the directory and the file (*.radf) of the retrofit with the button.
4. Loading the retrofit from a directory: press the button.
Or:
loading the retrofit from a diskette: press the button.
The program only displays the button which you have determined by selecting
either ”retrofitting drive A:” or ”free choice”.
5. Confirm the safety inquiry with ”OK” if you have stopped the conveyor and secured it to prevent it being
inadvertently switched on and wish to start the retrofitting of the option. HBD602700 ENG HEUFT Service Manager 3.00.006
The retrofit is available on the SPECTRUM TX device after the retrofitting has been successfully completed
and the device has been switched off and on again.
The device must be reset after a retrofit has been installed. The functions of the
retrofit must be put into operation afterwards.
78
Setting equipment
In principle two different types of equipment are differentiated as from Release 4.00 upwards (⇒ Equipment,
page 20). On the one hand there is the so-called optional equipment. There are functions hidden behind the
optional equipment which the customer has to pay for e.g. the changeover from a standard HF fill level
detection to a HF foam. Optional equipment is "sent" to the device (⇒ Sending equipment, page 77).
In addition there is equipment which can be freely changed e.g. changing the moving direction for the display
on the info page. This equipment is "set".
Certain functions in the software can be activated by means of the equipment.

inadvertently switched on before setting any equipment!
The EMERGENCY OFF push button must be pressed if the device has an
EMERGENCY OFF push button.
1. You can either select the device from the selection list at the bottom on the left of the network devices
(the program then shows the IP address automatically)
or enter the contact IP address of the device which you wish to retrofit.
79
Setting equipment
2. Call up the current equipment tree with the button (at the bottom on the right of the "set
equipment" page).
Make the tree visible by double-clicking on the device number or device name if only the device number and
name are shown.
The window on the left shows the list of modules for the device. Modules with equipment are marked with a
green card symbol.
3. Click on the module the equipment of which you wish to change.
The bit mask and the possible equipment are listed in the window on the right. The possible inputs can be
read from the list under the bit mask as well as a help flag at the tick box. Bit 2 and 4 have been set in the
example (= trigger 3 and 5 are available). All the other triggers have been set to "not available" (= bit set to 0):
Equipment in red is optional equipment! Optional equipment can only be installed

as a retrofit (⇒ Sending equipment, page 77).
Temporary equipment for 24 hours is no longer possible as from Release 8

upwards.
80
Setting equipment
4. Enter the value for the required equipment in the input mask. This is "1" (= trigger 2 available) for trigger
2 in the example.
5. Confirm the changed equipment with the button.
Reset the equipment to the original value with the button if you wish to
restore the original equipment.
The changed bit mask is shown with a yellow background.

6. Close the window with the button.
81
Setting equipment
The equipment selected will be displayed under "actions / prepared equipment".
7. Send the prepared equipment to the device with the button.
8. Confirm the safety inquiry with "OK" if you have stopped the conveyor and secured it to prevent it being
inadvertently switched on and wish to set the equipment.
The changed equipment is available on the SPECTRUM TX device after the work relating to the equipment
has been successfully completed and the device has been switched off and on again.
You will have to commission the new functions afterwards.
82
Managing inspection pictures
Each inspection with image processing has its own clipboard for its detection pictures. Pictures from the
clipboard can be saved permanently in an image storage in the device (⇒ help box on the PILOT surface).
Pictures can be copied to the hard disk of the PC or laptop on which the HEUFT Service Manager is installed
from this image storage. It is also possible to upload pictures, for example as reference pictures, from the hard
disk to the device.
Clipboard Image storage in the device
Downloading inspection pictures from the SPECTRUM.

1. Change to the "manage inspection pictures" page.
83
address of the device under "contact IP address".
3. Select "download from SPECTRUM".
4. Press the button.
The HEUFT Service Manager loads the modules with the image storage of the device to the window on the
left. The file names of the pictures (*.png) or the picture groups (*.tif) of the inspection selected appear in the
window on the right when a module is selected.
Multi-tiff files are hidden behind the *.tif files which can contain several individual tif
files. The pictures of a picture group are saved in a Multi-Tiff file. A Multi-Tiff
compatible program is required for viewing the pictures.
5. Click on the button "define directory where uploading / downloading is to be carried out" in order
to select the directory to which the pictures should be saved.
84
The window for the directory and file search opens.
6. Select the local directory for the image storage.
It makes sense to create a folder for the inspection pictures as illustrated above if a directory has not
been created yet for the inspection pictures.
The HSM creates a subdirectory automatically for the *.png files for each module
in the local directory (PIC/BBBB, BBBB = modules number).
Under no circumstances should the inspection pictures be saved to the directory

with the data backup files. This would interfere with the creation and transfer of
data backups and slow this down considerably.
7. Select the module from the list for which you wish to save a picture/pictures.
Either all the pictures from all the inspections (⇒ Saving all the pictures from all the inspections, page 86) or
individually selected pictures /picture groups (⇒ Saving individual or several selected picture groups, page
86) can be saved.
85
Saving all the pictures from all the inspections
8. Press the button in order to save all the pictures of all the inspections
locally.
The pictures which have been downloaded are displayed under "local picture directory".
Saving individual or several selected picture groups
8. Mark the inspection and the pictures to be downloaded.
9. Press the button in order to save the selected pictures of an

inspection locally.
86
The pictures which have been downloaded are displayed under "local picture directory".
The white field next to the inspections in the device does not mean that pictures
are no longer saved there but that these have already been saved on the hard
disk. Picture files are displayed again after an inspection module has been
selected.
The pictures remain in the device even after "downloading" unless the operator of
the device has changed the contents of the image storage of the device.
87
Uploading inspection pictures to the SPECTRUM

Pictures which have been downloaded to the hard disk of the PC or laptop can also be uploaded to the
SPECTRUM device.
For example it is possible to check the parameter inputs on a test rack using the inspection pictures by
uploading the inspection pictures saved.
88
1. Select the local directory using the button from which the HSM should upload the pictures.
The HSM displays afterwards from which modules the pictures in the directory selected are.
2. All the pictures can be uploaded to the device using the button.
3. If you only wish to upload the pictures of a certain module then that module has to be selected.
89
4. You can now select either individual, several or all the pictures of this module.
Individual picture: the left mouse button
Several pictures: CTRL and the left mouse button
shift and the left mouse button on the first and the last picture to be
A set of pictures
selected
90
5. Confirm the selection from the picture list using the button and start
uploading.
The index number of a picture (e.g. 001 in the case of INSP_1450_001_...)

corresponds to the number of the picture on the PILOT surface.
Index numbers
The picture with the same index number in the device is deleted when uploading a
picture.
It is not possible to upload two pictures with the same number (e.g.
INSP_1450_001_...) but different checksums at the same time because they would
be saved to the same image storage The HSM does not permit this.
The HSM loads the pictures selected to the device when the safety inquiry is confirmed with "OK".
91
92

Configuring the network
The entry of the correct IP (Internet Protocol) addresses is a basic requirement for the operation of the
HEUFT device in a network. The IP address settings must be suitable for the IP settings of the network
available. The appropriate inputs are carried out by the customer’s network administrator or the project
engineers at HEUFT SYSTEMTECHNIK GMBH.
For further information regarding IP addresses and HLAN network please refer to ⇒ IP addresses, subnet
mask and gateway addresses, page 95.
If the device is or is to be integrated in a HEUFT network the network addresses can be entered on this page.
1. You can either select the device from the selection list, bottom left of the network devices, (the program
then shows the IP address automatically)
93
Configuring the network
or enter the contact IP address of the device which you wish to integrate in the network.
2. Confirm the IP address either with the enter key or the button.
3. After you have entered all changes, new or additional IP addresses you can send your entries to the
HLAN-Manager using the send button.
The send button cannot be selected during the current data transmission (data
refresh round). Further entries can only be transferred to the HLAN-Manager
when the data transmission has been successfully completed.
94
IP addresses, subnet mask and gateway addresses
IP addresses
Within a network information to be transmitted is packed in so-called data packets. Addresses are required for
a correct delivery of the packets to the desired receivers such as in the case of normal postal deliveries. So-
called IP addresses (= Internet Protocol Addresses) must be used to distinguish between the individual
stations if TCP/IP (= Transmission Control Protocol/Internet Protocol) is used as protocol within a network.
Generally an IP address has two parts. The first part is called 'netID' (Network Identifier). It indicates the
network address. In analogy to postal codes the netID corresponds to the postal code of a city and is
therefore a designation of a particular city. The second part is called 'hostID' (Host Identifier) and indicates the
individual host within a network ('host' designates a computer or station within the network using internet
technology). As a result the hostID is the street name with the corresponding house number.
In simplified terms an IP address can be displayed as 4. 2. In this case 4 indicates the network and 2 the
station. As we will see later on, this principle is not quite as easy in reality as it seems to be.
Within the IP6 specification an IP address has 32 bits. According to this specification the IP address of a
station can be written as follows:
It is obvious that such a notation is very impractical. Such a notation would very probably cause errors when
having to enter such an address into a computer or keeping it in mind. Even a conversion of such figures into
decimal numbers would not facilitate the handling.
For this reason the so-called dotted notation has been created. In this case the number with 32 bits is simply
divided into 4 bytes (1 byte = 8 bits). Every byte can have a value between 0 and 255. The individual bytes are
visibly separated by a dot.
If exactly the same number as the above mentioned one is written according to the dotted notation, the
following number is obtained:
The advantage is obvious. The same address in this notation is much easier to handle.
95
Network classes
Within the IP specification the IP addresses are subdivided into several classes. The number of netIDs and
hostIDs used of the total of 32 bits decides to which class the address is assigned. Practice has shown that
the most frequently used classes are A, B and C.
In class A, bits 0 to 23 are used as hostID (3 bytes) and bit 24 up to and including bit 31 as netID (1 byte). In
class B, half the number of bits is used as hostID and the other half as netID. Class C only uses one byte as
hostID but 3 bytes as netID.
Network class A
Network class B
Network class C
In each class different numbers of hosts are possible. The larger the number of bits used as hostID the more
stations are theoretically possible within such a network.
Network class bits as hostID Number of possible hosts (theoretical)
A 24 2^24 16,777,216
B 16 2^16 65,536
C 8 2^8 256
The calculation of possible networks is similar. However, in this case it must be considered that particular bits
serve as identifiers of the network class. These bits are consequently defined. In class A, bit 31 is always 0
whereas in class B it is 1. Bit 30 is always 0 (see above illustration). Therefore the following conclusions can
be obtained:
Class A
One byte is used as netID (bit 24 up to and including bit 31). However, since bit 31 has been defined to status
0 the following range of values is obtained:
0000 0000 to 0111 1111
fixed at 0
After a conversion into a decimal number, the possible range of values is between 0 and 127 within this byte.
Consequently, 128 networks of class A may theoretically exist.
Class B
For the first byte of the two bytes used as netID two bits are defined. For this reason the following range of
values results within this byte:
1000 0000 to 1011 1111
fixed at 10
96
After a conversion into a decimal number, a value range of 128 (1000 0000) to 191 (1011 1111) is obtained
thus corresponding to 64 statuses.
However, since another byte is used as netID the number of statuses is multiplied according to its range of
values. As this byte can have values between 0 and 255, the range of values of the first byte must be
multiplied by 256 thus resulting in the total number of possible networks of class B.
64 x 256 = 16,384
Class C
In class C, 3 of the total of 24 bits are defined with the definition only referring to one byte. Therefore the
following conclusion can be obtained:
1100 0000 to 1101 1111
fixed at 110
A value range of 192 (1100 0000) to 223 (1101 1111) thus corresponding to 32 statuses is obtained on the
basis if this.
The following total number of networks of class C is again obtained on the basis of this:
32 x 256 x 256 = 2,097,152
Due to the definition of the respective bits it is always easy to find out the type of network class within the
binary notation. With regard to the above conclusion, the following rule can be defined for the identification of
a particular network class represented by the kind of notation which is used for IP addresses. Only byte 4, i.e.
the first left number is important for the identification of the network class.
IP addresses Network class Possible networks in the

respective class
A 128 only 1 byte as netID

0.x.y.z to 127.x.y.z
part x, y and z as hostID
B 16,384 + part x as netID

128.x.y.z to 191.x.y.z
parts y and z as hostID
C 2,097,152 + parts x and y as netID

192.x.y.z to 223.x.y.z
part z as hostID
Subnet masks
In the previous paragraph the three most frequently used network classes have been introduced.
Theoretically more than 16 million hosts could be located within a network of class A. Even in a network of
class B the number of possible hosts (65536) seems to be rather unreal and impractical. When imagining that
such a number of hosts would be located within a network using Ethernet as network technology it is obvious
that the total bandwidth for the individual host would be very limited. The network would not be able to operate
as the number of participants was too large.
The brilliant concept of subnet masks is used exactly at this stage. A subnet mask is used to subdivide a net
internally into small subnets. The subnets being created in such a way are connected to one another via a
router thus enabling to maintain a communication between all participants. Due to the subnets the total
number of participants is divided to the different subnets. In every subnet almost the full bandwidth is
available now, i.e. is distributed to a much smaller number of participants as compared to a large global
network. Such kind of division cannot be perceived from the outside.
97
To come back again to the analogy of postal deliveries mentioned above subnet masks are nothing else than
the division of a company into internal departments. Letters are generally only sent to a particular company.
When the letter arrives in the company it is opened and distributed within the company. However, the
postman only delivers the letter to the company and is not responsible for the distribution to the respective
department. He does not pay attention to the allocation to the departments because this is irrelevant for him.
The subnet mask is a number with 32 bits as well as the IP address itself (for example 255.255.252.0). To
understand the function of subnet masks it is necessary to link the IP address and the subnet mask logically
via an AND operation (every bit of the IP address is linked logically to the corresponding bit of the subnet
mask via an AND operation). In doing so the following logical operation results for every bit:
As an example the IP address 172.16.3.1 shall be linked with the subnet mask 255.255.252.0 via an AND
operation. For this purpose both numbers are first converted into a binary notation:
IP address 172.16.3.1 => 1010 1100.0001 0000.0000 0011.0000 0001

Subnet mask 255.255.252.0 => 1111 1111.1111 1111.1111 1100.0000 0000
Then the individual bits are linked logically via an AND operation:
When the result is converted again into the dotted notation the following address is obtained:
172.16.0.0
It can be seen that the first two bytes are unaltered since the status of all bits of the first two bytes in the
subnet mask is 1 (255 = 1111 1111). In the third byte only parts of the 8 bits are set to 1 (252 = 1111 1100).
When applying the same procedure to several IP addresses the principle becomes clear:
172.16.0.x & 255.255.252.0 172.16.0.0

172.16.1.x & 255.255.252.0 172.16.0.0
172.16.2.x & 255.255.252.0 172.16.0.0
172.16.3.x & 255.255.252.0 172.16.0.0
172.16.4.x & 255.255.252.0 172.16.4.0

172.16.5.x & 255.255.252.0 172.16.4.0
172.16.6.x & 255.255.252.0 172.16.4.0
172.16.7.x & 255.255.252.0 172.16.4.0
172.16.8.x & 255.255.252.0 172.16.8.0

172.16.9.x & 255.255.252.0 172.16.8.0
172.16.10.x & 255.255.252.0 172.16.8.0
172.16.11.x & 255.255.252.0 172.16.8.0
98
All IP addresses where the third byte is 0 to 3 result in 0 at the corresponding position. The addresses where
the third byte is 4 to 7 result in 4 etc. It can also be said that all participants for which an AND connection leads
to the same result are in the same subnet.
When configuring the TCP/IP protocol of a particular host the own IP address and the used subnet mask must
always be set. In the initialization phase of the host the above described procedure is principally always
carried out, i.e. the own IP and the subnet mask are linked logically with one another via an AND operation.
The subnet where the respective station is located results from such an AND operation. If the station wants to
send a packet the destination address is also linked with the used subnet mask via an AND operation. This
way the system analyses whether the packet is to be sent to a participant belonging to the same subnet or
has to be routed to another subnet.
If the destination address is in the same subnet, the packet can be sent directly to that address. However, if
the destination address is in another subnet, the packet can only be sent indirectly via the router. In this case
the packet is simply sent to the station which has been configured as gateway IP.
The subnet mask used in the example above causes a division of the network into 256 : 4 = 64 subnets. If a
differing number of subnets is desired, another subnet mask must be used accordingly. For example the
division of a class B network into 32 subnets requires the subnet mask 255.255.248.0 (248 = 1111 1000).
Example
The standard subnet mask used at HEUFT SYSTEMTECHNIK GMBH is 255.255.248.0, i.e. up to 32 subnets
(also referred to as branches) can be established. On the production site 'Am Wind' two branches are used.
The TFE department uses subnet 172.17.0.0 (range of IP addresses from 172.17.0.0 to 172.17.7.255). The
production (TEE) uses subnet 172.17.40.0 (range of IP addresses from 172.17.40.0 to 172.17.47.255).
Both subnets are connected to one another by a router. The router has two IP addresses (one address for
each branch). The gateway IP setting is required for the communication between all connected stations. The
setting of the gateway IP depends on the branch allocation. All the stations connected in the TFE network are
assigned the first router IP (172.17.0.3) as gateway IP. All the stations connected in the TEE network are
99
assigned the second router IP (172.17.40.1) as gateway IP (⇒ Setting of IP-addresses and subnet mask,
page 105).
IP: 172.17.0.4 IP: 172.17.1.50

Subnet 255.255.248.0 Subnet mask: 255.255.248.0 TFE network
mask:
Gateway IP: 172.17.0.3 Gateway IP: 172.17.0.3 First router
IP
172.17.0.3
Router
Second
router IP
IP: 172.17.42.100 172.17.40.1
Subnet mask: 255.255.248.0 TEE network
Gateway IP: 172.17.40.1
IP: 172.17.41.100
Subnet mask: 255.255.248.0
Gateway IP: 172.17.40.1
Broadcast IP address
When a data packet is assigned a so-called broadcast IP address as destination address this data packet
does not refer to a particular participant but to all participants within a subnet (⇒ Subnet masks, page 97). As
agreed the last possible IP address within a subnet is reserved as broadcast IP address (i.e. it cannot be used
as an address for a particular host). HBD602700 ENG HEUFT Service Manager 3.00.006
The standard subnet mask used at HEUFT SYSTEMTECHNIK GMBH is 255.255.248.0. The TFE department
uses subnet 172.17.0.0 (range of IP addresses from 172.17.0.0 to 172.17.7.255). In the TFE branch the
address 172.17.7.255 is thus the last possible IP address. The IP address 172.17.7.255 is therefore used as
broadcast IP. The production (TEE) uses subnet 172.17.40.0 (range of IP addresses from 172.17.40.0 to
172.17.47.255). There the broadcast IP address 172.17.47.255 is used.
The pilot.ini file contains for example the following entry:
<pilot_start>
hlanmanager_ip "localhost,172.17.47.255,172.17.7.255"
<pilot_end>
Due to the use of IP addresses 172.17.7.255 and 172.17.47.255 all stations in subnets 172.17.0.0 and
172.17.40.0 are addressed (enquiry whether these stations are all active HLAN-Managers).
100
localhost
In configuration files (such as the pilot.ini file) the designation 'localhost' is used as variable parameter for the
own IP address. Necessary modifications due to a change of the IP address of the own station can thus be
saved.
The pilot.ini file contains for example the following entry:
<pilot_start>
hlanmanager_ip "localhost,172.17.47.255,172.17.7.255"
<pilot_end>
Due to the entry 'localhost' the own platform is addressed (enquiry whether the own station is an active HLAN-
Manager).
101
Network adjustments
Network adjustments
DHCP (automatic assignment of IP addresses)

The IP address (⇒ IP addresses, subnet mask and gateway addresses, page 95) is dynamically assigned by
the net CPU. For this purpose the net CPU has been equipped with a DHCP function (Dynamic Host
Configuration Protocol). The DHCP dynamically assigns the IP address to the terminal or service laptop. In
doing so ensure that only one device can be connected to each port (port 2 or port 3; only at port 1 several
devices may be connected).
In addition terminal and service laptop must be changed to the dynamic request for the IP address. This
setting is carried out at the operating system level.
Service laptop
with DHCP
function
Crossed UTP cable
Net CPU with active

routing function
Crossed UTP cable

Terminal (TI or TN) with
Port 1: HLAN (network to other SPECTRUM TX devices) DHCP function
Port 2: Terminal (TI or TN)
Port 3: Service laptop
Port 4: Not used at present
Activating DHCP under LINUX (on a HEUFT terminal)

A keyboard is absolutely necessary for activating the DHCP function.
1. Connect the keyboard to the terminal. HBD602700 ENG HEUFT Service Manager 3.00.006
2. Open the 'local menu' on the terminal (ALT + F1 or left mouse button).
102
Network adjustments
3. Select the 'Configure Network' menu point.
4. Next select item 1 'Enable DHCP'.
5. Confirm the 'DHCP enabled' message.
Deactivating DHCP under LINUX and setting a fixed IP number (on the HEUFT terminal)
A keyboard is absolutely necessary for deactivating the DHCP function and assigning a fixed IP number.
1. Connect the keyboard to the terminal.
2. Open the 'local menu' on the terminal (ALT + F1 or left mouse button).
3. Select the 'Configure Network' menu point.
103
Network adjustments
4. Next select item 2 'Disable DHCP and configure network'.
5. Enter the intended IP address for the terminal and confirm with 'OK'.
6. Enter the intended gateway address (⇒ IP addresses, subnet mask and gateway addresses, page 95)
(this entry is only relevant if a connection to another subnet is intended). Confirm with 'OK'.
7. Enter the required subnet mask (⇒ Subnet masks, page 97) and confirm with 'OK' (the standard subnet
mask for HEUFT devices is 255.255.248.0). If the terminal is integrated into a customer network the
subnet mask depends on the customer's network environment. HBD602700 ENG HEUFT Service Manager 3.00.006
104
Network adjustments
8. Afterwards an overview of all entries is displayed. If the settings comply with the intended entries,
confirm with 'yes'.
9. Confirm the following message:
Setting of IP-addresses and subnet mask

The SPECTRUM IP-number and the IP address (⇒ IP addresses, subnet mask and gateway addresses,
page 95) of the HLAN-Manager are generally configured via the SPECTRUM TX operating panel. In the case
of SPECTRUM TX devices as from release 4.00, the subnet mask (⇒ Subnet masks, page 97) and the
gateway IP address (⇒ IP addresses, subnet mask and gateway addresses, page 95) can also be configured
via the operating panel. In the case of older devices only the MasterDataOrganizer can be used for this
purpose.
A SPECTRUM TX occupies four consecutive IP addresses as from the number xxx.xxx.xxx.100 (e.g.
xxx.xxx.xxx.100 to 103 or xxx.xxx.xxx104 to 107 etc.).
1. Change to the access level 3 of the operating panel (switch to the access module with M+/M-,
then select the following key combination: confirm, arrow key down, confirm,
arrow key up, confirm).

105
Network adjustments
2. Enter the IP addresses.

Key combination:
Select the program module
whilst A is displayed
continue with input
To start with set the IP number of the SPECTRUM. "SP" indicates

that it is the SPECTRUM IP.
Press to change values.
Use the button to go to the next stage.
Then set the IP number of the responsible HLAN-Manager. "HL"

indicates that it is the IP for the HLAN-Manager.
Then set the IP number of the GATEWAY TXserver. "GA"

indicates that it is the IP for the GATEWAY TXserver.

Then set the IP number of the subnet mask. "SU" indicates that
this is the IP for the subnet mask.
3. Wait for the automatic reset (the display gets dark for a very short moment). Afterwards the device
operates with the new settings.
106
Wiring and configuration examples for networking TX devices
The following examples illustrate the wiring and configuration (IP numbers) of TX devices.
Key:
Uncrossed UTP cable
Crossed UTP cable
Example 1: InLine with preceding sorting unit. The sorting unit is designed as TB device. It shall also be
operated via the InLine terminal. For this reason the HLAN-Manager of the InLine must also support the
sorting unit. No further devices shall be connected (a switch is thus not required).
InLine SPECTRUM TI SX SPECTRUM TB

SP IP 172.17.40.100 SP IP 172.17.40.104
HL IP 172.17.40.101 HL IP 172.17.40.101
The settings in the pilot.ini and the devicelist.ini files of the InLine must be adapted accordingly. In the 'pilot.ini'
file the 'device_select' entry has to be changed from 'first' to 'devicelist'.
The settings can also be adapted on the

PILOT surface (system menu, system
settings, PILOT settings).
107
In addition the device number of the sorting

unit must be supplemented in the
'devicelist.ini' file (⇒ Setting of IP-
addresses and subnet mask, page 105).
Example 2: More than two SPECTRUM TX devices are to be networked with one another. As a result a
switch (in the past: a hub) is necessary. The HLAN-Manager of the InLine supports the sorting unit (SX as TB
device). The fill level control has its own HLAN-Manager (TI device). Every device shall be accessible on each
terminal.
InLine SPECTRUM TI SX SPECTRUM TB VX SPECTRUM TI

SP IP 172.17.40.100 SP IP 172.17.40.104 SP IP 172.17.40.108

HL IP 172.17.40.101 HL IP 172.17.40.101 HL IP 172.17.40.109
The settings in the pilot.ini file of the InLine and the fill level detection must be adapted accordingly. In the
'pilot.ini' file the 'device_select' entry has to be changed from 'first' to 'all' (⇒ Setting of IP-addresses and
subnet mask, page 105).
108
Example 3: Two SPECTRUM TB devices shall be operated via a TF terminal (remote terminal).
TF terminal
DHCP deactivated
IP 172.17.40.50
SPECTRUM TB SPECTRUM TB
SP IP 172.17.40.100 SP IP 172.17.40.104
HL IP 172.17.40.50 HL IP 172.17.40.50
The DHCP function must be deactivated on the TF terminal (⇒ Deactivating DHCP under LINUX and setting
a fixed IP number (on the HEUFT terminal), page 103). The terminal must be assigned a fixed IP number (in
the example this is 172.17.40.50). All SPECTRUM TB devices are assigned the IP number of the terminal as
HL IP (⇒ Setting of IP-addresses and subnet mask, page 105). In the 'pilot.ini' file of the terminal the
'device_select' entry has to be changed from 'first' to 'devicelist'. The device numbers of both devices must be
entered in the 'devicelist.ini' file.
109
110
Create device CD
It is possible to create a device CD (PILOT-CD) for the device after a successful service visit using this page.
This device CD can be given to the customer as a current data backup. For this the service technician
creates a current data backup and sends it to the TX archive using the HSM. The service technician can order
the creation of a "CD image" of the device CD via the portal if placing the data backup in the TX archive has
been confirmed by e-mail.
The CD image is a file which contains all the data necessary for creating a CD.
This not only includes the files which should be copied to the CD but also
information regarding the structure of the file system. It is possible to produce fast,
accurate copies of a data carrier with a CD image.
The person placing the order receives an e-mail after the CD image has been completed. The CD image can
be downloaded from the "HEUFT Internet server" using the HSM.
It is possible to burn device CDs using the HSM if the service lap top has a CD burner.
Creating a CD image file using a data backup

The HSM creates a file of the type "HEUFT backup archive" (hba) in order to archive device data backups.
The hba file is the basis for creating a CD image.
1. The first step to a "HEUFT backup archive" (hba) is the usual data backup by means of the HSM (⇒
Saving data, page 41).
111
2. The HSM creates a hba file using this data backup and sends the hba file to the TX archive (⇒
Transferring data backups to the TX archive, page 57).
The hba file can also be sent by e-mail to a HEUFT employee who places the data
backup in the TX archive as an alternative to transmission by means of the HSM.
A further possibility is to find the device number in the HEUFT portal and to upload
the hba file from your service laptop to the TX archive under "upload" in the
"device backup" subfolder.
The fastest method is transmission by means of the HSM (⇒ Transferring data
backups to the TX archive, page 57).
The service technician who created the hba file always receives a personal confirmation e-mail if the hba file
has been successfully places in the TX archive.
Only the service technician who created the hba file receives a personal
confirmation e-mail. If another HEUFT employee places the file in the TX archive
this employee does not receive a confirmation e-mail.
The e-mail contains a fault message if the hba file is rejected. In this case you
must create a new data backup and transmit the data backup to the TX archive.
You can continue with number 3 if you receive a positive confirmation e-mail.
3. Connect to the HEUFT portal and log in.
4. Search for the device number in the portal using "search device".
112
5. Select the "device CD" menu item in the subfolder.
Only request a CD image when you have received a positive confirmation e-mail
regarding the placing of the current hba file. Otherwise you will receive a CD
image based on an obsolete status.
6. Press the button in order to request the creation of a CD image.

The portal user who has requested the CD image will receive an e-mail from the source serve upon
successful creation. The source server creates the CD image file.
113
The e-mail contains a fault message if there is not a consistent data backup:
7. Go to the "Create device CD" page of the HSM.
The HSM checks automatically whether the connection to the HEUFT Internet server is online or offline when
the "Create device CD" page is opened. The status is show at the top on the right.
Accessing the HEUFT Internet file server is only possible when the HEUFT Internet file server is "online".
114
8. Click on "download CD image" in the "installed functions" menu in order to display the file list.
All the CD image files are displayed in the column on the right which are available to be downloaded from the
HEUFT Internet server for the service technician who is logged in. The actual CD image file ("iso" format) is
available for downloading as a very compressed "7z" archive ("7-zip" / "seven-zip" format). The file name
starts with the device number followed by your HEUFT identification code and the time of creation. The
HEUFT identification code is always the abbreviated name of the employee who created the hba data backup.
The file names have a coloured background displaying their status:
red File is available on the server - the file download has not been started yet.
yellow The file has been partly downloaded - downloading can be continued. Downloading can be
interrupted and continued at a later stage should a hold-up occur during data transmission.
green The file has been completely downloaded.
115
Additional information regarding the data backup, such as the file size, is displayed by clicking on one of the
file names.
Downloading the CD image

1. Click on the file name in order to download a CD image file. The file name has a blue background. Start
the transmission of the file with the button.
116
2. A safety inquiry appears afterwards. Confirm the safety inquiry with "OK" if you really want to download
the file.
A transmission monitor shows how long the transmission is expected to take.
The processing times of the HSM (particularly during a status refresh when the
standard directory is being checked) can be considerably slowed down because
an activated virus scanner must be used with an existing Internet connection.
The file is checked at the end of downloading to see that it is correct and complete which can take a few
seconds. The HSM emits a fault message if a fault has occurred in which case the downloading has to be
repeated.
The CD image files are filed to a fixed directory "C:\heuft\jtools\hsm\download" and can be used for burning
device CDs (⇒ Creating a device CD (burning a CD image), page 119).
Restarting an interrupted transmission
The transmission can be interrupted in the case of hold-ups as regards the data transmission or if you wish to
carry out other work with your service laptop. The part of the zip file which has already been saved to your
laptop remains. Partly downloaded files are marked yellow by the HSM. It is possible to continue the
transmission or restart it at a later stage.
117
1. Select the file with the yellow background again. Start the transmission of the file with the
button.
2. An inquiry appears afterwards asking you whether you wish to continue downloading or start
downloading again.
The file is checked at the end of downloading to see that it is correct and complete which can take a few
seconds. The HSM emits a fault message if a fault has occurred in which case the downloading has to be
repeated completely (new download).
118
Creating a device CD (burning a CD image)
1. Select the "burn CD image" menu. The HSM displays all the files from which device CDs can be
created.
2. Place an official HEUFT blank CD into the drive in which you wish to burn the CD. The blank CD to be
officially used is an independent part (HPB500527 ST) and has a label printed on it.
3. Click on the file name in order to burn a CD image file. The file name has a blue background. Start the
burning process with the button.

119
4. A safety inquiry appears afterwards. Confirm the safety inquiry with "OK" if you really want to burn the
CD image (the device CD).
5. The CD is automatically burned after the iso.7z file has been unpacked. The following window appears
whilst the CD is being burned:
The following message appears if you have forgotten to insert a blank CD: "insert
a writable CD/DCD Disc...". :
Place an official HEUFT blank CD into the burning drive.
Press the button in order to start the burning process.
120
6. Enter the current creation data for the burned CD (device number, date and creator of the CD) by hand
using a waterproof pen in the pre-printed section of the CD label.
7. Test the CD.
8. The CD image file can be deleted from your laptop if the CD is in order:
select "burn CD image".
9. Press the button if you wish to delete the files which are in the "download" directory (burning
a CD image).
Go to the C:\heuft\jtools\hsm\download directory with the Windows Explorer and

delete the files there manually if you only wish to delete individual files and not all
the files.
It is advisable to delete the 7z CD image files after servicing has been completed
and the device CD created. This makes it clear that the service visit has been
completed. This also avoids a device CD being created from an old data backup
by mistake (an older service visit).
121
10. Confirm the safety inquiry "do you want to free the hard disk storage space?" with "release" if you wish
to delete the files.
11. Give the device CD to the customer.
122
Flash management
All TX devices from Release 0500 upwards have so-called FlashPROMs instead of the EPROMs used
originally. The advantage of this is that during a SPECTRUM software update it is possible to simply copy
(flash) to the FlashPROMs. The tiresome replacement of memory packs is therefore no longer necessary.
Memory packs with EPROM Memory packs with FlashPROM

(the old method) (new since Release 0500)
The so-called flash bundle is supplied for the flashing process on-site for safety reasons (stability of the
programs to be flashed). Flash bundles generate the production of the programs.
A flash bundle is specifically created for one device and includes the programs for two possible SPECTRUM
statuses: “original software” and “upgrade”.
The flash bundle presupposes that the original software is in the device. ”Original
software“ is the software which is assumed to be actually available in the device.
Only in this way can retrofit software be installed.
The reverse is also possible when flashing: the retrofit software is in the device. It is
replaced by the initial original software as a result of the flashing.
The flash management system is required for the software update of the SPECTRUM TX device. We have
summarized the description of a software update in a separate chapter due to the fact that the software
update uses several HSM program modules: ⇒ Software update of SPECTRUM TX devices (from Release 7
upwards), page 149.
123
124
Small device management
With the small device management system it is possible to (for such devices as the HEUFT xio):
configure small devices

125
126
Configuring small devices
The entry of the correct IP (Internet Protocol) addresses is a basic requirement for the operation of a small
device. The IP address settings must be suitable for the IP settings of the network available. The appropriate
inputs are carried out by the customer’s network administrator or the project engineers at HEUFT
SYSTEMTECHNIK GMBH.
Using this page you can allocate the small devices (e.g. the HEUFT xio) a device name and the IP addresses.
The IP addresses can either be defined automatically or the network administrator can allocate them. For
further information please refer to the Operator’s Manual for the small device (e.g. the HEUFT xio).
Entering the device name
1. Select the small device from the broadcast list.
Small devices which have not been configured yet respond with their device
number and “SET-ME-UP”.
2. Please enter the name of the small device under “device name”.
This is either a new name which has not been allocated yet or
the name of the previous small device which will be replaced by the new small device.
For example the latter is the case when a small device has been replaced due to a fault which cannot
be repaired.
127
Entering IP addresses
There are two possibilities for allocating the small device an IP address:
⇒ Having the IP addresses automatically defined by the DHCP server (the HEUFT STRATEGY Gate),
page 128
⇒ Entering fixed IP addresses, page 129
Please ask the network administrator if you are unsure of the options available for your small device.
Having the IP addresses automatically defined by the DHCP server (the HEUFT STRATEGY
Gate)
The DHCP server (the HEUFT STRATEGY Gate) allocates IP addresses independently within a certain fixed
area with the help of the “dynamic host configuration protocol”.
1. Click on the field next to “receive IP addresses automatically”.
The HEUFT STRATEGY Gate allocates the IP addresses and enters them in the fields with the grey
background.
2. Transmit the configuration to the small device using the button.
The HEUFT Service Manager causes the small device to be reset.
128
Entering fixed IP addresses

The small device receives a fixed IP address if it is not connected to a DHCP server. Either the network
administrator or the HEUFT Project Department can assign fixed IP addresses.
1. Click on the field next to “fixed IP address”.
2. Enter the IP addresses for the small devices, the HLAN Manager, the Gateway and the subnet mask.
3. Transmit the configuration to the small device using the button.
The HEUFT Service Manager resets the small device.

Please refer to the Operator’s Manual for the small device for information on how
to proceed with commissioning.
129
130

PC management
With the PC management system it is possible to:
install the PILOT
install the PILOT or the device locally (service)

131
132
Installing the PILOT
The basic installation for the Service PILOT is carried out by the EDP
department. The service technician has access to the blue pages as a result.
It is possible to install all the drivers (device drivers, spare parts lists and the PILOT) from a TB device onto
your service laptop using this function. The device can be operated via the PILOT surface with the PILOT.
The service laptop is connected to the SPECTRUM TX device via the service port. The SPECTRUM TX
device must have a sufficient number of HEUFT PILOT access licences if access is only possible via another
network connection to the SPECTRUM TX device (⇒ Setting up a device connection, page 73).
1. Place the PILOT CD in the CD-ROM drive.
2. Use the button to update the status. The program issues a message when a PILOT update is
necessary.
3. Press the start button .

A message appears when the installation has been successfully completed.
Starting the PILOT
1. Go to the ”set up device connection” page and start the PILOT with the button.
1. Or: with the button in the ”servprog” program folder on the desktop (the start page) of the service
laptop of the PILOT.
133
Installing the PILOT
Removing the PILOT and all the SPECTRUM TX devices from the service laptop (deinstalling)
Never carry this out. This function is only for the customer and has been taken
over from the HEUFT Service Center (HSC).
1. Press the button.
A message appears when the deinstallation has been successfully completed.
134
Installing the PILOT or the device locally (service)
When you wish to view the PILOT surface of a device offline, a valid data backup is necessary. In addition all
script pages for the PILOT surface have to be available on your own platform. The function on this HSM page
enables the installation of all necessary device drivers, service packs and spare parts drivers. For this
purpose the HSM analyses the spc file of the data backup and determines all necessary drivers on the basis
of this file.
If the drivers are not available on your own platform (service laptop) ("C:\heuft\drivers" directory) the HSM can
load them also directly from the Portal and install them afterwards. However, an Internet connection to the
Portal must be established for this purpose.
What the service laptop needs for a local installation:
• the HEUFT service infrastructure in the "C:\heuft" local directory
• the necessary device drivers in the "C:\heuft\drivers" directory
• the necessary PILOT drivers ("user zip") in the "C:\heuft\enxarchiv\user" directory
• the consistent data backups of the devices in the "C:\heuft\hlan\hlanmanager\{device number}\" directory.
Data backups are consistent if for example the driver entries in the spc file are correct.
1. Update the status with the button. The directories with the data backups and the drivers are
scanned and the possible updates resulting from this are displayed.
Admissible PILOT updates are allocations of user zip files which correspond at least to the version of the
PILOT installed.
Admissible device installations are all devices which are displayed in "green" in the selection list. In the case
of "green" devices all required drivers are available.
According to the selected mode exactly the drivers designated in the spc file are required or compatible
replacement drivers are allocated.
When devices are displayed in "yellow" at least one driver is missing. When devices are displayed in "red" the
complete driver entries are missing. This is an unacceptable state of the data backup which has to be
eliminated by installing the drivers at the on-line device (or in the case of TB devices by an offline installation
of a CD).
135
Updating the PILOT

The PILOT version installed on the laptop is displayed under "status". If a higher PILOT version is available
the "A local PILOT installation is possible." message is displayed.
2. Press the start button in order to install the available PILOT.
3. Confirm the safety inquiry if you wish to install the new PILOT.
136
Updating the device drivers

4. Click on a "yellow" or "green" device in order to analyse the state of the drivers.
All drivers which are necessary for the display on the PILOT surface are displayed under "messages".
Available drivers have already been saved on the laptop, missing drivers are not yet in the driver directory.
⇒ Installing an available driver, page 138
⇒ Installing a missing driver, page 139
"replace" message: install a compatible driver of a higher version (in the case of service packs or spare parts
lists). ⇒ Installing a compatible driver, page 141
137
Installing an available driver

1. Select a "green" device. If a missing driver is available because it is saved in the "C:\heuft\drivers"
directory on the laptop, the message "available driver ..." is displayed:
2. Press the start button in order to install the available drivers:
3. Confirm the safety inquiry if you wish to install all drivers completely.
138
Installing a missing driver

If a missing driver is not available on the laptop, the "missing driver ..." message is displayed.
1. Download the missing drivers from the HEUFT Portal and save them to the "C:\heuft\drivers" directory
(PILOT driver ("user zip") in the "C:\heuft\enxarchiv\user" directory).
2. Update the status with the button.
3. Reselect the device.

139
The "missing drivers" have become "available drivers". The status has changed from yellow to green because
all drivers are available.
4. Press the start button in order to install the available drivers.
When the installation has been successfully completed the available drivers are still displayed under
"messages". There is no check of the installed drivers.
140
Installing a compatible driver

Instead of the missing spare parts drivers (SPL drivers) and/or service packs compatible drivers of a higher
version can also be installed. The display on the PILOT is also possible with compatible drivers.
1. The button is displayed in grey if the search for alternatives is deactivated. Press the button to
activate the search for alternative drivers. The button is displayed in colours if the search is
activated.
If the button is grey, only the missing drivers are displayed and no possible
alternatives.
2. Press the start button in order to install the available drivers.
141
When the installation has been successfully completed the available drivers are still displayed under
"messages". There is no check of the installed drivers.
Starting the PILOT
1. Go to the "set up device connection" page and start the PILOT with the button.
1. Or: start the PILOT with the button in the "servprog" program folder on the desktop (the start
page) of the service laptop.
142
Terminal management
With the terminal management system it is possible to:
carry out a PILOT update (optional)
carry out a STRATEGY Gate update (optional)
upload files to the HLAN-Manager

143
144
Carrying out a PILOT update (optional)
An update of the PILOT operating surface can be carried out on one of the SPECTRUM TX devices using this
page. A PILOT update is advisable in the case of debugging (bugfix), extending the range of functions and
new languages. However only later versions within a release should be installed. The installation of a later
release is only permissible if it is expressly part of the order (⇒ PILOT software, page 13 and ⇒ The
compatibility of the PILOT software versions, page 14).
The actual PILOT version can be checked after selecting the icon in the system settings/system info
menu.
Hard disk version

PILOT version
Settings
GROUP entries
HLAN Manager
Script server
Device drivers
Connected terminals
The device must have an operating terminal with a PILOT operating surface.
Operating terminal with a

PILOT surface
1. Place the PILOT CD in the CD-ROM drive if there is an update file on the PILOT CD otherwise
continue with number 2.
145
Carrying out a PILOT update (optional)
2. Please enter the IP address of the terminal which should undergo a PILOT update in the input field. The
IP address for the terminal can be found on the terminal under “system menu, system settings , system
info” as an IP under “PILOT”.
3. Use the button to update the status.
4. Select PILOT update (USER*.zip). The files are generally in the “bin” subdirectory on a PILOT CD.
However you can also download a USER*.zip file from the hard disk of your laptop.
The message “update completed” appears when the update has been successfully completed.
146
Carrying out a STRATEGY Gate update (optional)
An update of the STRATEGY Gate device can be carried out using this page. An update is advisable in the
case of debugging (bugfix), extending the range of functions and new languages. However only later versions
within a release should be installed. The installation of a later release is only permissible if it is expressly part
of the order (⇒ PILOT software, page 13)
1. Place the STRATEGY Gate CD in the CD-ROM drive if there is an update file on the STRATEGY Gate
CD otherwise continue with number 2.
2. Please enter the IP address of the STATEGY Gate which should undergo an update in the input field.
The SPECTRUM IP address for the STRATEGY Gate can be read via the operating panel (⇒ Reading
out the SPECTRUM IP address via the operating panel and making a note of it, page 186).
3. Use the button to update the status.
147
Carrying out a STRATEGY Gate update (optional)
4. Select STRATEGY Gate update (STRATEGYGATE*.zip). The files are generally in the “bin”
subdirectory on a STRATEGY Gate CD. However you can also download a STRATEGYGATE*.zip file
from the hard disk of your laptop.
The message “update completed” appears when the update has been successfully completed.
148
Software update of SPECTRUM TX devices (from Release 7
upwards)
All TX devices from Release 0500 upwards have so-called FlashPROMs instead of the EPROMs used
originally. The advantage of this is that during a SPECTRUM software update it is possible to simply copy
(flash) to the FlashPROMs. The tiresome replacement of memory packs is therefore no longer necessary.
The instructions describe the update procedure for the SPECTRUM real-time software and the installation of
device drivers.
Memory packs with EPROM Memory packs with FlashPROM

(the old method) (new since Release 0500)
The so-called flash bundle is supplied for the flashing process on-site for safety reasons (stability of the
programs to be flashed). Flash bundles generate the production of the programs.
The flash bundle is produced specifically for one device and includes the programs for two possible
SPECTRUM conditions: "Original software" and "retrofit software".
The flash bundle presupposes that the original software is in the device. "Original"
software is the software which is assumed to be actually available in the device.
Only in this way can retrofit software be installed.
The reverse way of flashing is also possible: the device is equipped with the retrofit
software. It is replaced by the initial original software as a result of the flashing.
The SPECTRUM data has to be saved with the HSM before carrying out a software
update (⇒ Saving data, page 41).
149
Software update of SPECTRUM TX devices (from Release 7 upwards)
Carrying out a software update
A software update requires the following steps:
1. ⇒ Saving SPECTRUM data, page 150
2. ⇒ Establishing a connection to the SPECTRUM TX device, page 151
3. ⇒ Selecting a flash bundle, page 152
4. ⇒ Executing the flashing process, page 154
5. ⇒ Reorganising a device, page 156
6. ⇒ Saving data back to the device, page 156
7. ⇒ Installing device drivers, page 156
Saving SPECTRUM data

The data from the SPECTRUM device must be saved with the HSM before carrying
out a software update!
(⇒ Saving data, page 41)
150
Establishing a connection to the SPECTRUM TX device
A connection with the device must be set up using the HEUFT Service Manager before a software backup can
be carried out. There are two possibilities for creating this connection:
enter the contact IP address of the device and confirm the entry. If you do not know the contact IP address
of the device this address can be read via the operating panel (⇒ Reading out the SPECTRUM IP address
via the operating panel and making a note of it, page 186).
Select the device using the network search. In order to do this you must have configured the device search
(⇒ Configuring device search with the HEUFT Service Manager, page 31). The network search is
described under ⇒ Selecting the device using the network search, page 41.
Neither a separate configuration of the device search nor a network search are necessary if you connect your
service laptop to the service port of the SPECTRUM TX provided. For this reason we will describe “entering
the contact IP address of the device”. Otherwise reference to the network search is listed above.
1. Go to the "flash management (flash bundle)" page.
2. Enter the IP address of the device under "contact IP address".

151
The current card and program occupancy of the device selected is displayed in the action field on the right.
Selecting a flash bundle

1. Select the flash bundle (*.hfb) with the button. Only the files with file names beginning with the
device number can be selected.
2. Select the flash bundle (*.hfb). The *.hfb files are generally in the "\data\flashbundle" subdirectory on
the CD-ROM. The file name always begins with the device number (e.g. 2PG012345_*.hfb).
Flash bundles cannot be selected directly from the CD if you have one of the
following operating systems installed on your service laptop: Windows XP, NT4.0 or
2000. A fault message will appear: "access denied".
In such a case copy the flash bundle from the CD onto the hard disk. Mark the file
which has now been saved to the hard disk and select "properties" with the right
mouse button.
Click the file attribute "write-protected" away.
152
The flash management display is updated after the flash bundle has been selected.
The contents of the flash bundle are shown on the left.
The program checks if the flash bundle is suitable for the flashing process after the flash bundle file has been
selected. It is possible to select between the two software states (original or retrofit) if this is the case.
A fault message appears if the flash bundle is not suitable for the flashing process:
Flashing is not possible either if the device contains more program packages than
the flash bundle or the program packages on the flash bundle do not match with the
program packages on the cards.
3. Select the retrofit software with the button.
153
Executing the flashing process
4. Start the flashing process with the button. The following appears on the operating panel:
FLASH
The fault message "faulty flash action" will appear if only a part of cards is available
on the device compared to the extent of the flash bundle.
The card which is not found is displayed with a question mark.
Check this card in the device. Replace the card if it is faulty. Replace the memory
pack with an empty memory pack if it is faulty.
Then repeat the flashing process.
5. The progress of the flashing process is displayed by the HEUFT Service Manager:
154
To conclude "run mode" is displayed for each card.
F2 appears on the operating panel to indicate that reorganisation is necessary.
F2
6. Go to the network configuration page.

The IP address of the device for which the software has been updated should be displayed under "new
contact IP address".
155
Reorganising a device
7. Select the button in order to reorganise the device (⇒ Reorganisation, page 20).
The button cannot be selected if the device has received Release 0500
status as a result of the flashing process. If this is the case reorganisation must be
carried out via the operating panel ⇒ Reorganising the SPECTRUM via the
operating panel, page 187.
Saving data back to the device

During the reorganisation procedure nearly all the SPECTRUM parameters are
deleted in addition to the new creation of the permanent component table
(tantamount to a new device in the old system). However the program definitions
remain. Therefore after a reorganisation procedure in the case of devices up to
Release 7.00 the old data backup must always be imported.
A data backup is filed to the "external flash memory" by the operating system of
the net CPU before the actual reorganisation procedure is initiated in the case of
devices from Release 8.00 upwards. This is automatically re-imported after the
reorganisation procedure. The "reload" message appears on the terminal during
this procedure.
Therefore manually importing a data backup is not necessary in the case of

devices from Release 8.00 upwards. However this does not apply to a release
update from an older release version to Release 8.00.
8. Saving data back to the device (⇒ "local (standard)" restoration, page 45).
9. The SPECTRUM device has to be switched on for at least 30 seconds.

A device driver only has to be installed if the retrofit order includes a device driver
(test pack or service pack - ⇒ Device drivers, page 15).
The installation of device drivers has to be carried out from a service laptop which is network linked to the
device.
The installation of device drivers is described in the following section ⇒ Installing a new device driver, page
66.
156
Replacing a faulty hard disk (as from Release 7.00)
These instructions apply to TN or TI devices of the PILOT 7.00.000 version upwards.
How to replace a faulty hard disk up to Release 6 is described on the technicians’

CD HBF900051 0700 Part 1 under “Training documents created before the
publication of the OLS - Training”.
Go to the “TX training documents, general” page and select “replacing a faulty
hard disk”.
A service laptop, a new hard disk and a PILOT CD are necessary for replacing the hard disk. There should be
a PILOT CD in the device or you have brought a PILOT CD with you for the service visit.
1. ⇒ Reading out the SPECTRUM IP address via the operating panel and making a note of it, page 186.
2. Open the terminal casing.
3. Check the supply voltage to the operating terminal. This supply voltage is the same as the supply
voltage for the hard disk and must not be below 5 V. If necessary clear the contact resistance at the
plug contacts.
4. Switch the device off at the operating panel .
5. Turn the main power switch to position 0 – "OFF".
157
6. Replace the hard disk.
When connecting the hard disk to the PC board take care that the side of the
ribbon cable marked in colour is connected to PIN 1.
If the ribbon cable is incorrectly connected (offset connection) this can ruin
the ribbon cable (short circuit) or the hard disk.
7. Turn the main power switch to position I – "ON".
8. Use the button to start the device.
A window appears on the terminal (“init_enx”). Wait until the text “ready for connection” appears in the window
(“init_enx”).
9. Connect the service laptop to the service port.
Service port Service port in the door of the

InLine camera box
Generally the service port can be directly connected to the device with a
transposed UTP cable.
10. Update the PILOT software on the terminal with the HEUFT Service Manager ⇒ Carrying out a PILOT
update (optional), page 145.
158
The following message appears after the PILOT update has been completed:
11. Confirm the message with OK. Wait 10 to 20 seconds after completing the update until the terminal
automatically carries out a complete restart. Restart the PILOT if it does not automatically start.
12. Install the device drivers ⇒ Installing a new device driver, page 66.
13. After the installation has been successfully completed the program issues a message and asks you to
switch the device off and then on again. If the device is operated from a remote terminal then this
terminal must also be switched off and on again.
14. Wait until the device selection list appears.
15. Select device from the “device selection list”.
16. Log in as the system manager. Then go to the "PILOT settings" page.
159
All the data which can be entered on this page is exclusively used to control this
PILOT surface (terminal software). It does not affect the other PILOT surfaces in
the network.
17. Set the “criteria for the structure of the device selection list (device_select)” entry to “first” in the
selection list. Alternatively adjust to "devicelist" if several devices have to respond from the same
terminal.
18. Open the "management of the 'devicelist.ini' file" selection window.
160
19. Select the device required and open the context-sensitive menu (either by actuating the jog shuttle or
clicking on the right mouse button). Then select the “include device to 'devicelist.ini'” menu item. Other
devices to be viewed on this terminal should also be added to the “devicelist.ini”.
20. The first (uppermost) device on the devicelist.ini starts automatically with the PILOT when selecting
“first” after “device_select”.
161
21. Go to "entries relating to the access control" in the upper selection list.
22. Terminal entries specifically relating to the customer have to be adapted on this page:
defining the access The option to make changes to the device data on the respective
mask PILOT installation can be restricted by means of the access mask. It is
no longer possible to carry out the corresponding functions from this
terminal when authorization has been restricted using the access
mask. Even if the user has the appropriate authorisation to do this in
accordance with the user definition.
All rights are usually set to in the case of TI and TN terminals. It

generally only makes sense to restrict authorization when a PILOT has

been installed on a PC or a remote terminal.
terminal_mode TN Selecting "TN" results in a transfer of the access rights to the operating
panel of the SPECTRUM device (standard setting for all local
terminals).
TF Selecting "TF" does not result in a transfer of the access rights to the
operating panel of the SPECTRUM device (standard setting for all
remote terminals).
Select “TN” for TN and TI terminals.
access_mask The program calculates the hex code for the “access_mask” from the
access rights.
162
time_to_bolt log-out time (sign off)

Period after which automatic logging out occurs at the terminal if it was
not used.
Entering the value "0" prevents automatic logging out.
Automatic logging out does not occur in the case of user *.
23. Then go to "other entries" in the upper selection list.
24. Entries specifically relating to the customer have to be adapted on this page:
Language during the PILOT Select language from the list.

start-up phase
Programming the PILOT title Put the title together from the “device names”, the “user names”
and the “program names” of your choice. A name will not appear if
“-“ has been selected.
Time zone relating to the Select time zone from the list.
location of the PILOT
163
25. Go to the “HEUFT service settings” menu page.
26. If necessary replace the contact address with the address of the HEUFT subsidiary abroad.
164
27. Go to terminal management to the "upload files to the HLAN-Manager" page.
28. Enter the terminal/HLAN-Manager IP address.
All files can be uploaded by selecting "device directory (user data)" if the device has customer-specific files
stored in the "all" directory.
29. Copy the *.dat ,*.prg, *.prp and *.knf files individually via "file selection" to the HLAN-Manager (at the
terminal).
30. Click on the button – "load the files from any position".
165
31. Select the file for uploading.
The HEUFT Service Manager shows the source selected:
32. Copy the file to the HLAN-Manage with the button.
33. Repeat this procedure until the *.dat,*.prg, *.prp and *.knf files have been uploaded. HBD602700 ENG HEUFT Service Manager 3.00.006
An error message appears if the device number is not available for the HLAN-
Manager selected or an HLAN-Manager cannot be reached via the IP address.
The program emits a message after successful installation.
35. Use the button to restart the device.
166
Adjusting the calibration of a touchscreen (optional)
The screens are touchscreens since Release 8.00 and have been manufactured
since November 2004. Therefore older screens (Release 7 or older) do not have
to be calibrated.
It is advisable to readjust the calibration so that the screen selection corresponds to your screen touch when
operating the touchscreen.
1. Connect the keyboard to the terminal. Place the appropriate keyboard plug in the keyboard socket.
Keyboard socket Keyboard socket in the door of the

camera box of the InLine empty
bottle inspector
2. Call up the local menu with the Alt + F1 key combination.
3. Select the "calibration of touchscreen" menu with the arrow keys or the shortcut keys Alt + T.
167
4. Touch the four circles which appear one after the other with a touchscreen pen. Four arrows point to a
circle in each case.
The calibration program ends automatically after the four circles have been touched. The touchscreen has
now been recalibrated. The display shows the PILOT surface again.
Repeat numbers 2 to 4 until the calibration is correct if you have missed the circles
by mistake and the calibration process has not been successful.
168
Replacing a faulty CF memory card (as from Release 9.00)
These instructions apply to TN or TI devices of the PILOT 9.00.000 version upwards.
CF memory cards are used instead of hard disks as from release 9.
The replacement of defective hard disks for Release 7 and 8 is explained in the
Operator's Manual for the HEUFT Service Manager in the "Replacing a faulty hard
disk (as from Release 7.00)" chapter.
A service laptop, a new CF memory card and a PILOT CD are required for replacing the CF memory card.
There should be a PILOT CD in the device or you have brought a PILOT CD with you for the service visit.
1. ⇒ Reading out the SPECTRUM IP address via the operating panel and making a note of it, page 186.
2. Enter the IP address of the device under “contact IP address”.

169
4. Save the data for the device selected using the button.
The program indicates when a data backup was created and when it is available.
5. Open the terminal casing.
6. Check the supply voltage for the CF memory card. The supply voltage may be between 5.1 and 5.2 V.
170
Older terminals of the version 4 are not yet equipped with the measuring points
shown on the photo. Measure the voltage at the upper one of the three LEDs in
this case.
Measure the 24 V supply voltage of the terminal if the voltage is below or equal to
5.0 V.
Check the feed line from the power supply unit to the terminal if the measuring
instrument for the 24 V supply voltage of the terminal indicates a value smaller or
equal to 20 V.
The 24 V supply voltage of the terminal is correct if the measuring instrument for
the 24 V supply voltage of the terminal indicates a value higher than 20 V. Please
consult the HEUFT hotline on how to proceed because of the insufficient supply
voltage for the CF memory card.
Danger of electric shock!

Remove the memory card only when the device and the main power switch are
switched-off. Otherwise there is danger of electric shock.
171
8. Turn the main power switch to the 0 "OFF" position.
9. Slide out the defective CF memory card and remove it.
When inserting the new CF memory card make sure that the card is inserted
in the right direction and the groove engages in the guide.
A wrongly inserted CF memory card can ruin the guide and the
connecting block.
Guide
Groove
10. Insert the new CF memory card in the holder. HBD602700 ENG HEUFT Service Manager 3.00.006
172
11. Turn the main power switch to position "I" ON.
12. Use the button to start the device.
A window appears on the terminal (“init_enx”). Wait until the text “ready for connection” appears in the window
(“init_enx”).
13. Connect the service laptop to the service port.
Service port for InLine and squeezer

Service port
Generally the service port can be directly connected to the device with a
transposed UTP cable.
14. Update the PILOT software on the terminal with the HEUFT Service Manager ⇒ Carrying out a PILOT
update (optional), page 145.
The following message appears after the PILOT update has been completed:
15. Confirm the message with OK. Wait 10 to 20 seconds after completing the update until the terminal
automatically carries out a complete restart. Restart the PILOT if it does not automatically start.

16. Place the PILOT CD-ROM of the device in the CD-ROM drive.
17. Enter the IP address of the device under "contact IP address" and confirm the entry.
173
18. Start the evaluation of the PILOT CD-ROM inserted using the lower button.
The program displays the evaluation of the PILOT CD-ROM inserted.
19. Press the installation button .

20. The program displays which drivers are available on the PILOT CD-ROM. Confirm the inquiry with OK
if you wish all the drivers selected by the program to be installed.
The program issues a message after the new device drivers have been successfully installed (as from
Release 9).
174
21. Please pay attention to the information given in the message. Only switch the device off and on again if
the graphic pictograph on the PILOT surface can no longer be viewed. If the device is operated
from a remote terminal then this terminal must also be switched off and on again.
22. Wait until the device selection list appears.
23. Select device from the “device selection list”.
24. Log in as the system manager. Then go to the "PILOT settings" page.
All the data which can be entered on this page is exclusively used to control this
PILOT surface (terminal software). It does not affect the other PILOT surfaces in
the network.
175
25. Set the “criteria for the structure of the device selection list (device_select)” entry to “first” in the
selection list. Alternatively adjust to "devicelist" if several devices have to respond from the same
terminal.
26. Open the "management of the 'devicelist.ini' file" selection window.
176
27. Select the device required and open the context-sensitive menu (either by actuating the jog shuttle or
clicking on the right mouse button). Then select the “include device to 'devicelist.ini'” menu item. Other
devices to be viewed on this terminal should also be added to the “devicelist.ini”.
28. The first (uppermost) device on the devicelist.ini starts automatically with the PILOT when selecting
“first” after “device_select”.
177
29. Go to "entries relating to the access control" in the upper selection list.
30. Terminal entries specifically relating to the customer have to be adapted on this page:
defining the access The option to make changes to the device data on the respective
mask PILOT installation can be restricted by means of the access mask. It is
no longer possible to carry out the corresponding functions from this
terminal when authorisation has been restricted using the access
mask. Even if the user has the appropriate authorisation to do this in
accordance with the user definition.
All rights are usually set to in the case of TI and TN terminals. It

generally only makes sense to restrict authorisation when a PILOT has
been installed on a PC or a remote terminal.
terminal_mode TN Selecting "TN" results in a transfer of the access rights to the operating
panel of the SPECTRUM device (standard setting for all local
terminals).
TF Selecting "TF" does not result in a transfer of the access rights to the
operating panel of the SPECTRUM device (standard setting for all
remote terminals).
Select “TN” for TN and TI terminals.
access_mask The program calculates the hex code for the “access_mask” from the
access rights.
178
time_to_bolt log-out time (sign off)

Period after which automatic logging out occurs at the terminal if it was
not used.
Entering the value "0" prevents automatic logging out.
Automatic logging out does not occur in the case of user *.
31. Then go to "other entries" in the upper selection list.
32. Entries specifically relating to the customer have to be adapted on this page:
Language during the PILOT Select language from the list.

start-up phase
Programming the PILOT title Put the title together from the “device names”, the “user names”
and the “program names” of your choice. A name will not appear if
“-“ has been selected.
Time zone relating to the Select time zone from the list.
location of the PILOT
179
33. Go to the “HEUFT service settings” menu page.
34. If necessary replace the contact address with the address of the HEUFT subsidiary abroad.
180
35. Go to terminal management to the "upload files to the HLAN-Manager" page.
36. Enter the terminal/HLAN-Manager IP address.
All files can be uploaded by selecting "device directory (user data)" if the device has customer-specific files
stored in the "all" directory.
37. Copy the *.dat ,*.prg, *.prp and *.knf files individually via "file selection" to the HLAN-Manager (at the
terminal).
38. Click on the button – "load the files from any position".
181
39. Select the file for uploading.
The HEUFT Service Manager shows the source selected:
40. Copy the file to the HLAN-Manage with the button.
41. Repeat this procedure until the *.dat,*.prg, *.prp and *.knf files have been uploaded.
An error message appears if the device number is not available for the HLAN-
Manager selected or an HLAN-Manager cannot be reached via the IP address.
The program emits a message after successful installation.
43. Use the button to restart the device.
182
Adjusting the calibration of a touchscreen (optional)
The screens are equipped with touchscreens as from Release 8.00

(manufacturing since November 2004). Thus older screens (Release 7 or older)
do not need to be calibrated.
The calibration must be readjusted so that the screen selection corresponds to your screen touch when
operating the touchscreen.
1. Connect the keyboard to the terminal. Place the appropriate keyboard plug in the keyboard socket.
The operator's manual for your device indicates where to find the keyboard socket
of your device (refer to the "Sockets for PC keyboard and mouse" section).
Keyboard socket of a
SPECTRUM TX device
2. Call up the local menu with the Alt + F1 key combination.
3. Select the "calibration of touchscreen" menu with the arrow keys or the shortcut keys Alt + T.
183
4. The touchscreen is calibrated at three or four circles depending on the variant. Touch the small circles
which appear one after the other with a touchscreen pen.
Calibration with four circles Calibration with three circles
The calibration program ends automatically after the circles have been touched. The touchscreen has now
been recalibrated. The display shows the PILOT surface again.
Repeat numbers 2 to 4 until the calibration is correct if you have missed the circles
by mistake and the calibration process has not been successful.
184
Appendix
185
Reading out the SPECTRUM IP address via the operating panel and making a note of it
Key combination:
whilst A is displayed
Continue with input
First read out the SPECTRUM IP number. "SP" indicates

that it is the SPECTRUM IP.
Then read out the IP number of the HLAN Manager. "HL"

indicates that it is the IP for the HLAN Manager.
Then read out the IP number of the GATEWAY server.

"GA" indicates that it is the IP for the GATEWAY server.
Then read out the IP number of the subnet mask. "SU"

indicates that this is the IP for the subnet mask.
186
Reorganising the SPECTRUM via the operating panel
Only reorganise the SPECTRUM via the operating panel if the device
has obtained the release level as from 0500 by means of the flashing
process.
⇒ Reorganisation, page 20
1. Change the access level of the operating panel to level 3.
Selecting the access module

187
2. Carry out the reorganisation process of the FlashPROM of the net CPU-card.
Key combination:
=>Display appears
=> Display
appears
Wait until display:
appears
A RESET has to be carried out afterwards within the next 10 seconds. The process is discontinued
if a RESET does not occur within this time.
Carry out a RESET: Press the and buttons simultaneously.

188
Flash codes of the indicator LEDs on the net CPU
red 1 green 1
red 2 green 2
Flash codes activated by the

software
ONLY LED red 1 flashes Cause:

in 1 second cycles synchronisation fault.
The net CPU remains in the synchronisation loop because another CPU
card has not confirmed the synchronisation.
Corrective action:
reset the card.
Reset the card with a reset plug or by switching off the power supply unit.
The card that caused the fault must be found if this fault is still displayed.
For this purpose switch off the voltage supply, remove a single card (not
the net CPU), switch on the voltage supply again and observe the fault
LEDs. Replace this card and repeat the same procedure with another
card if the fault is still present until the fault is no longer displayed.
Replace the CPU card which has been removed and take over the
EPROMs. Replace the net CPU if the fault cannot be located in this way.
LED red 1 remains on after Cause:

a reset the net CPU is stuck in the initialisation phase.
The net CPU is in the initialisation phase or at the entry point to an
unauthorised interrupt in the initialisation phase.
Corrective action:
replace the net CPU card.
LED red 1 comes on shortly Cause:

after a reset, goes out and entry point to an unauthorised interrupt after the initialisation phase.
then remains on
Corrective action:
please call the HEUFT service department.
LED green 1 comes on after Cause:

a reset boot loader activated.
A new operating system software is flashed in the SPECTRUM.
189
LED green 2 comes on after Cause:
a reset the program module has found a difference between the new component
table and the component table in the FlashPROM.
A CPU card has not been initialised correctly.
Corrective action:
restart the device. Find the defective CPU card in the message module
and replace it if the LED lights up again.
Parameters cannot be edited on the operating surface when LED green 2

is on.
LED red 2 is on Cause:

the watchdog has been deactivated.
LEDs red 1 and green 1 are Cause:

flashing alternately after a self-test fault of the net CPU.
reset
Corrective action:
switch the SPECTRUM TX off and on again.
Observe the number of flash pulses (alternating flash codes) and call the
HEUFT service department if the problem persists.
The LEDs red 1 and green 1 Cause:

are flashing at the same system start in the low-voltage range. 5 V operating voltage is less than
time in 0.8 second cycles 4.7 V.
Corrective action:
replace the power supply unit.
190
green 1 yellow
red green 2
Flash codes activated by the

hardware
LED green 1 LED is on:

shared RAM access from the net CPU.
LED red Reset LED:

the red LED stays on as long as the field programmable logic array
(FPGA) is being initialised.
LED yellow LED is on:

shared RAM access from another CPU via the system bus.
LED green 2 LED is on:

data transmission via the video bus.
191
Indicator LEDs on the net CPU
Green LED:
LEDs: green yellow this traffic/link LED is permanently on when there is a
above every Ethernet network connection to a distant station (e.g. HUB) and the
connection connection is in order.
This traffic/link LED flashes when data packages are being

transmitted via this network connection.
Yellow LED:
LED on: bit or data transfer rate 100 Mbit/s
LED off: bit or data transfer rate 10 Mbit/s
The components used are able to identify at which bit rate

the stations can work in order to then adjust themselves
automatically to the highest transmission rate (auto-
negotiation function).
red 1: Init LED

The init LED indicates the initialisation of the card,
normally the LED is off.
red 1 green 1
green 1: reset LED
red 2 green 2 The reset LED indicates a reset, normally the LED is off.
red 2: watchdog LED

This LED comes on when the watchdog has detected a
malfunction. The LED is normally off.
The LED lights up for a short time when switching on.
green 2:
this LED is permanently on when there is a difference
between the data in the FlashPROM and the device data.
The LED is normally off.
192
Sequence after a reset:
Phase 1: The LEDs red 1 and green 1 on the net CPU are switched on.
reset The reset LEDs on the other CPU cards light up for a short time.
Phase 2: The LED green 1 on the net CPU goes out and the LED red 1 remains
initialisation on during the initialisation phase.
The fault LEDs on the other CPU cards light up.
Phase 3: The LED red 1 on the net CPU card goes out and the fault LEDs on the
main program other CPU cards go out.
193
Indicator LEDs on the CPU3 card
LEDs
Green: status LED of the software-controlled conveyor cycle monitoring.

This is inverted after every 0.5 metres of conveyor movement after the
initialisation phase.
Yellow: turbo LED, frequency mode of the CPU clock cycle.

20 MHz if the LED is on and 8 MHz if the LED is off.
Yellow: SREADY signal - normal status, dimly illuminated.

There is a fault when accessing the bus when this LED is brightly
illuminated.
Red: CPU RESET

This LED is on during the start-up phase. This LED is normally off.
Red: NMI-LED
The program routine is blocked via the NMI line/debug signal. The LED is
normally off.
Red: fault LED

The program routine is interrupted or incorrect. During the initialisation
phase this LED comes on for 1 or 2 seconds and goes out after the
completion of the phase. This LED is normally off.
Red: watchdog signal
194

HSM Mainhelp

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HSM Mainhelp

Uploaded by

Copyright:

Available Formats

HEUFT SERVICE MANAGER

3.00.006 01.10.10 Translation of the German version

HBD602700 ENG HEUFT Service Manager 3.00.006

Cancelling the picture allocation currently selected ............................................................................... 40

Creating a device CD (burning a CD image) ....................................................................................... 119

The program may not be passed on to a third party.

Under no circumstances should the HEUFT Service Center program be installed

The HEUFT Service Center is only intended for customers. There is no

• Saving device data on your local hard disk

Structure of the Operator’s Manual

The HEUFT Service Center is only intended for customers. There is no

No debug outputs You will be spared additional messages.

Some debug outputs You will receive a choice of messages.

The “HEUFT Service Manager” program will now open.

The following is an example of a PILOT version: USER_7.00.012.zip

a particular PILOT software release version).

The compatibility of the PILOT software versions

Old device at the PILOT release of the new device /

Notes regarding the table

OK An update to the PILOT software is not necessary.

- Device and PILOT releases are the same.

Front panel in a door HBF910000 St Terminal Update from v2 to v3; door

HBF910000 TERM Terminal Update from v2 to v3;

Front panel of a TX cover HBF910000 TX Terminal UPdate from v2 to v3; TX

The following is an example of a device driver: INLINE_0700_0000.zip

INLINE this refers to an InLine device driver

0700 Release No. - in the example this is No. 7.00

The following is an example of a service pack: INLINE_0700_0000.SP2.zip

INLINE this refers to a service pack for an InLine device driver

0000 Language – in the example this is German/English (language list)

SP2 No. of the service pack - in the example this is No. 2

In the example the service pack 2 INLINE_0700_0004.SP2_0512031340.zip relates to the foreign-language

Device drivers test pack

Test pack 5 in Spanish INLINE_0700_0004.TP5.zip also has to be installed if test pack 5

Spare parts lists

The following is an example of a spare parts driver: INLINE_SPL_0000_0611031715.zip

INLINE Device type

SPL Designation for a spare parts driver

0000 Language – in the example this is German/English (language list)

0611031715 Creation date – in the example this is 06.11.03 at 17:15

Spare parts list filter

General information regarding the installation of drivers

Hard disk version

A data backup must be extracted to your service laptop in order to

Therefore manually importing a data backup is not necessary in the case of

Equipment HBD602700 ENG HEUFT Service Manager 3.00.006

For further information please refer to the MasterDataOrganizer on the

HBD602700 ENG HEUFT Service Manager 3.00.006

1. Press the button in order to request the clearance code.

The "Portal" generates the code and sends it to you by e-mail.

3. Start the HEUFT Service Manager.

6. Restart the HEUFT Service Manager.

Renewed clearance for the HEUFT Service Manager

1. Start the HEUFT Service Manager.

2. Select the menu "clear again".

3. Continue as described above in numbers 4 to 6 (⇒ Page 24).

HBD602700 ENG HEUFT Service Manager 3.00.006

1. Place the coded CD in the CD drive.

The CD starts but the contents cannot be opened.

3. Confirm the inquiry.

CD decoder has been activated. You have access to the files.

Deactivating the CD decoder

HBD602700 ENG HEUFT Service Manager 3.00.006

allocate container and case pictures

transfer data backups to the TX archive

carry out software updates (flash management)

configure device search (HSC)

install device drivers

install device drivers (service)

set up a device connection

manage inspection pictures

create an overview of the cards

flash the net CPU

configure the network

Enter the contact IP address of the device.

Select the device using the network search.