Untitled

Windows Server 2003 (W2K3) Installation 1
Windows XP Professional Installation 2

Windows 2000 (W2K) Installation 3
W2K3 Configuration for ECS Applications 4
XP Configuration for ECS Applications 5
ECS/SDR Installation 6
ECS/SDR Service Pack Installation 7
Time Synchronization 8
QCX Installation 9
Ha Long SQL Backup and Restore 10
Vietnam QCX GMS Support 11
Document No. 80010127 Import from the QCX v7 output tray 12
Order No. 970056060 QCX Driver General Description 13
Project No. QCX1156 QCX Driver Point Value Acquisition 14
Siemens (Without Softnet) I/O System 15
Driver for Generic Receiving Station 16
QCX Driver for Generic Sampler 17
ECS Installation v7.0.6 QCX Driver for Generic Automatic Plant Station 18
QCX Installation v7.0.5 QCX Driver for ARL WinXRF 19
Volume 1/1 20
21
22
23
24
25
26
27
28
FLSmidth Automation 29
Hoffdingsvej 34 30
DK-2500 Valby 31
Copenhagen 32
Denmark 33
34
35
36
37
Phone: +45 36 18 27 00 38
Telefax: +45 36 18 27 99 39
TAB
TAB
Reference Manual
Windows Server 2003

Installation
FLSmidth A/S - Automation
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Last modified $Modtime:: 3/06/06 5:56p $
Author cna-in
Last modified by $Author:: Cna-in $
Name of Word File $Workfile:: W2K3Installation30_English.doc $
All rights reserved.
Disclaimer:
The information in this document is subject to change without notice and should not be construed as a commitment
by FLSmidth A/S. FLSmidth assumes no responsibility for any errors that may appear in this document.
In no event shall FLSmidth be liable for direct, indirect, special, incidental or consequential damages of any nature
or kind arising from the use of this document, nor shall FLSmidth be liable for incidental or consequential damages
arising from use of any software or hardware described in this document.
Options specified and described in the FLSmidth documentation as part of the general description - but initially
neither ordered by the customer nor confirmed by the seller - will not commit the supplier to any further and future
supply and/or installation.
The software described in this document is furnished under a license and may be used, copied, or disclosed only in
accordance with the terms of such license.
Copyright © FLSmidth A/S.

Contents
Windows Server 2003 Installation 1
Introduction 1
Preparation 1
Windows Server 2003 Standard Edition installation: 2
Configuration Information 2
Windows Server 2003 Installation Procedure 2
How to create a Windows Server 2003 Domain 2
Making a Computer member of a Domain 2
Adding an additional Domain Controller 2
Service Pack Installation 2
Printer Installation 2
Glossary of Terms 3
Index 5
Reference Manual Windows Server 2003 Installation Contents • iii

Windows Server 2003
Installation
Introduction
The procedure used to install the Microsoft Windows Server 2003 operating system on a personal computer is
described in the following sections;
• Preparation
• Windows Server 2003 Installation Procedure
• How to create a Windows Server 2003 Domain
• Making a Computer member of a Domain
• Adding an additional Domain Controller
• Service Pack Installation
• Printer Installation
Preparation
Hardware
Verify the following before starting the Windows Server 2003 installation:
1. The personal computer is in the Microsoft Windows Server 2003 HW Compatibility List
2. The computer comprises:
• A minimum of 512 Mbytes of RAM
• A minimum of 20 Gbytes of system disk space
• A Bootable CD-ROM drive
• A floppy drive
3. The computer is properly connected to the network (10/100/1000 Mbit twisted pair)
Software Media
Locate the following before starting the Windows Server 2003 installation:
Reference Manual Windows Server 2003 Installation Windows Server 2003 Installation • 1
Windows Server 2003 Standard Edition installation:
The following Compact disks:
• Microsoft Windows Server 2003 Standard Edition
• Microsoft Windows Server 2003 Service Pack (if applicable)
Refer to the ECS SW product for the required level of Windows Server 2003 Service pack
Configuration Information
Obtain the following information from your network administrator:
• Computer name
• Workgroup or Domain name
• TCP/IP address
• TCP/IP subnet mask
In order to browse network resources the following information is also required:

• TPC/IP address for DNS server
• TCP/IP for Default Gateway
Windows Server 2003 Installation Procedure
How to create a Windows Server 2003 Domain
Making a Computer member of a Domain
Adding an additional Domain Controller
Service Pack Installation
Printer Installation
2 • Windows Server 2003 Installation Reference Manual Windows Server 2003 Installation
Glossary of Terms
Reference Manual Windows Server 2003 Installation Glossary of Terms • 3

Index
Error! No index entries found.
Reference Manual Windows Server 2003 Installation Index • 5

TAB
TAB
Reference Manual
Windows XP Installation
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: XPInstallation30_English.doc $
Disclaimer:

Contents
Windows XP Professional Installation 1
Introduction 1
Preparation 1
Hardware 1
Software Media 2
Windows XP Professional Installation Procedure 3
Making a Computer Member of a Domain 5
Installing a Local Printer 7
Installing a Network Printer 8
Glossary of Terms 9
Index 11
Reference Manual Windows XP Installation Contents • iii

Windows XP Professional
Installation
Introduction
The procedures used to install the Microsoft Windows XP Professional operating system on a personal computer are
described in the following sections:
• Preparation
• Windows XP Professional Procedure
• Making a computer member of a Domain
Preparation
Hardware
Verify the following before starting the Windows XP Professional installation.
1. The personal computer is in the Microsoft Windows XP Professional HW Compatibility List

2. The computer includes:
- A minimum of 128/256 Mbytes of RAM (Professional/Server)
- A minimum of 6/8 Gbytes of system disk space (Professional/Server)
- A bootable CDROM drive
- A floppy drive
3. The computer is properly connected to the network (10/100 Mbit twisted pair).
Reference Manual Windows XP Installation Windows XP Professional Installation • 1

Software Media
Locate the following before starting the Windows XP Professional installation.
For Windows XP Professional installation:

1 The following compact disks:
- Microsoft Windows XP Professional professional

- Microsoft Windows XP Professional Service Pack
Refer to the ECS SW product for the required level of Windows XP Professional Service Pack
• Computer name
• TCP/IP address
• TCP/IP address for DNS server
2 • Windows XP Professional Installation Reference Manual Windows XP Installation

Windows XP Professional Installation Procedure
The following describes the Microsoft Windows XP Professional installation procedure used by FLSmidth
Automation.
The installation procedure depends on the recommendation suggested by FLSmiidth Automation for your specific
site.
During the installation procedure, the user is prompted for specific information. Enter the default
response unless instructed to do otherwise in the following steps.
1. Insert the Windows XP Professional CD and reboot the system. (Make sure the BIOS of the computer are
set to boot from the CD-rom.)
2. If your computer is equipped with a special hard disk controller e.g. a special SCSI or RAID controller,
press the <F6>key when the Windows XP Professional Setup screen appears. You will be prompted
for a support disk from the hardware supplier. Refer to the documentation for the computer.
3. When the Welcome to Setup screen appears, press the <Enter>key. (To setup Windows XP
Professional now, press Enter.)
4. To accept the licensing terms, press the <F8>key.
5. Delete any old partitions and create a new one of a least 6 GB for a Windows XP Professional professional
and 8 GB for Windows XP Professional Server.
6. Select Format the partition using the NTFS file system.
The file system must be formatted using NTFS to take advantage of all NT security
features.
7. Enter the following directory for the installation.
\\WINNT
8. After the partition is formatted and the setup has copied files to the hard disk, the computer restarts by
itself.
9. At the Regional Settings prompt, select Customize for the keyboard layout.
Select Add… and choose your current Input locale to U.K. unless othervise specified. Click Set as
default for your new Keyboard layout.
10. Enter a friendly name of the administrator and a friendly company or plant name.
Name: <Administrator > For example: Administrator
Organization: <Company Name> For example: FLS Automation
11. For Windows XP Professional Server Setup only.
Set licensing Mode to: Per Server. Number of concurrent connections:
Enter the number of connections that your license allows.
12. Enter Your Product Key.
The Product Key is included in the Windows XP Professional kit, either on the CD cover or
a label on the computer.
13. Enter the computer name, e.g. ECS755SVR1
14. Enter the Administrator account password
15. For Windows XP Professional Server Set-up only.
Windows XP Professional Components Uncheck IIS, choose default and Next.
16. Adjust Date & Time and Time Zone according to your lacation.
The Time Zone must be the same on all computers, and there must be a checkmark in
Automatically adjust clock for daylight saving changes.

17. Networking Settings choose Custom Settings.
18. In Networking Components the following components must be installed and there must be a checkmark
with each component:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
Internet Protocol (TCP/IP)
19. Mark Internet Protocol (TCP/IP) and click Properties
Click Use the following IP address: and enter an appropriate IP address, Subnet mask and Default gateway.
If there is a DNS server on your network enter the IP address in Preferred DNS server.
20. For a W2K Server mark File and Printer Sharing….. and click properties. Select Maximize datathrougtput
for network applacation.
21. If the computer is member of a workgroup click No, this computer is not on a network, or is on a network
without a domain. Type a workgroup name in the following box.
Workgroup or computer domain: <Workgroup>For example: ECS755
If the computer is member of a Domain click Yes, make this computer a member of the following domain:
Workgroup or computer domain: <Domain> For example: ECS755
Enter the User Name and Password, for a user that has the ability to add computers to the domain.
User Name <User name> For example: Administrator
Password <password> For example: password
22. Click Finish to reboot the computer
23. The Network Identification Wizard starts.
Click Next
Choose Who can logon to this computer.
Click Next
Click Finish.
Login to Windows XP Professional as Administrator and install additional device drivers not recognised by Windows
XP Professional setup, e.g. Video adapters, Sound Cards, ATA-100 IDE controllers etc. Check Device Manager for
questions marks. (Devices not properly installed).
Refer to the documentation for the computer.

Making a Computer Member of a Domain
If you did not make the computer a member of an existing domain during installation you can join the computer to a
domain after the installation of Windows XP Professional is complete.
Right My Network Places on the desktop and click Properties
Double click Local Area Connection and click Properties
Mark Internet Protocol(TCP/IP) and click Properties
Ensure that the correct DNS server(s) are listed
Right click My computer on the desktop and click Properties
Choose Network Identification and Properties
In Member of click Domain and type the NetBIOS name of the domain.
The NetBios name of a domain is the default name you choose during creation of the domain, e.g.
the NetBIOS name of domain ecs755.flsa is ECS755.
Click OK
Enter the User Name and Password, for a user that has the ability to add computers to the domain
Click OK and OK to reboot the computer.
At the Log on to Windows expand Options
In Log on to: choose the domain e.g. ECS755, type the password for the account and click OK

After installation of Windows XP Professional you have to apply the current service pack. If you after the installation
install additional Windows XP Professional components you also have to apply the service pack.
1. Locate the service pack, either on a CD-Rom, on your local hard disk or on the network
2. Open Windows Explorer and browse to locate the service pack directory \i386\update
3. Double click update.exe
4. Select Accept the License Agreement and click Install
5. Click Restart when asked
6. Install additional patches as MDAC2.7, Microsoft Hot fixes etc.
A printer can be installer either as a Local printer or as a Network printer. A Local printer is connected directly to a
port on the computer (LPT or COM) or to a Standard TCP/IP Port you create. A Network Printer is connected to a
shared printer on another computer.
Use the driver CD that comes with the printer.

Installing a Local Printer
Installing a Plug and Play printer only works if the printer is connected directly to a LPT or COM port on the
computer.
1. Run Start/Settings/Printers
2. Double click Add Printer
3. Select Local Printer and Next
4. If no Plug and Play printers found click Next
5. Choose the port the printer is connected to and click Next
• If the printer is connected to a print server on the network select Create a new port:
• In the dropdown select Standard TCP/IP Port and click Next
• Type the IP address of the print server and a port name.
• Click Next and Finish

6. Choose a printer from the list. If the printer is not listed you must have a driver from the printer
manufacturer and click Have Disk…Click Next
7. Type a friendly name for the printer. Click Next
8. Select Do not share this printer and Click Next
9. Click yes to Do you want to print a test page? Click Next
10. Click Finish to the summary window.

Installing a Network Printer
Before you can connect to a network printer, you must have an account on the computer sharing the printer and have
the proper privileges to use the printer. Furthermore you must be logged in with that account on your computer to
access the printer.
When you use network printing, you have to install the printer for each account.
3. Select Network Printer and Next
4. Select Type the printer name, or click Next to browse for a printer
5. Browse for the printer you want to install and click Next.
6. Click Finish to the summary window

Glossary of Terms
Reference Manual Windows XP Installation Glossary of Terms • 9

Index
Reference Manual Windows XP Installation Index • 11

TAB
TAB
Reference Manual
Windows 2000 Installation

Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: W2KInstallation30_English.doc $
Disclaimer:

Contents
Windows 2000 Installation 1
Introduction 1
Preparation 1
Hardware 1
Software Media 2
Windows 2000 Installation Procedure 3
How to create a Windows 2000 Domain 5
Creating a Domain 5
Making a computer member of a Domain 10
Adding an additional Domain Controller 11
Adding a Domain Controller 11
Installing a Local Printer 13
Installing a Network Printer 14
Glossary of Terms 15
Index 17
Reference Manual Windows 2000 Installation Contents • iii

Windows 2000 Installation
Introduction
The procedures used to install the Microsoft Windows 2000 operating system on a personal computer are described
in the following sections:
• Preparation
• Windows 2000 Installation Procedure
• How to create a Windows 2000 Domain
• Adding an additional Domain Controller
Preparation
Hardware
Verify the following before starting the Windows 2000 installation.
1. The personal computer is in the Microsoft Windows 2000 HW Compatibility List
2. The computer includes:
- A minimum of 128/256 Mbytes of RAM (Professional/Server)
- A minimum of 6/8 Gbytes of system disk space (Professional/Server)
- A bootable CDROM drive
- A floppy drive
3. The computer is properly connected to the network (10/100 Mbit twisted pair).
Reference Manual Windows 2000 Installation Windows 2000 Installation • 1

Software Media
Locate the following before starting the Windows 2000 installation.
For Windows 2000 Professional installation:

1. The following compact disks:
- Microsoft Windows 2000 professional
- Microsoft Windows 2000 Service Pack
Refer to the ECS SW product for the required level of Windows 2000 Service Pack
For Windows 2000 Server installation:

1. The following compact disks:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Service Pack
Refer to the ECS SW product for the required level of Windows 2000 Service Pack
• Computer name
• TCP/IP address

• TCP/IP address for DNS server
2 • Windows 2000 Installation Reference Manual Windows 2000 Installation

Windows 2000 Installation Procedure
The following describes the Microsoft Windows 2000 installation procedure used by F.L.Smidth A/S - Automation.
The installation procedure depends on the recommendation suggested by FLSmidth - Automation for your specific
site.
During the installation procedure, the user is prompted for specific information. Enter the default response unless
instructed to do otherwise in the following steps.
1. Insert the Windows 2000 CD and reboot the system. (Make sure the BIOS of the computer are set to boot
from the CD-rom.)
2. If your computer is equipped with a special hard disk controller e.g. a special SCSI or RAID controller,
press the <F6>key when the Windows 2000 Setup screen appears. You will be prompted for a support
disk from the hardware supplier. Refer to the documentation for the computer.
3. When the Welcome to Setup screen appears, press the <Enter>key. (To setup Windows 2000 now, press
Enter.)
4. To accept the licensing terms, press the <F8>key.
5. Delete any old partitions and create a new one of a least 6 GB for a Windows 2000 professional and 8 GB
for Windows 2000 Server.
6. Select Format the partition using the NTFS file system.
The file system must be formatted using NTFS to take advantage of all NT security
features.
7. Enter the following directory for the installation.
\\WINNT
8. After the partition is formatted and the setup has copied files to the hard disk, the computer restarts by
itself.
9. At the Regional Settings prompt, select Customize for the keyboard layout.
Select Add… and choose your current Input locale to U.K. unless othervise specified. Click Set as
default for your new Keyboard layout.
10. Enter a friendly name of the administrator and a friendly company or plant name.
Name: <Administrator > For example: Administrator
Organization: <Company Name> For example: F.L.Smidth A/S - Automation
11. For Windows 2000 Server Setup only.
Set licensing Mode to: Per Server. Number of concurrent connections:
Enter the number of connections that your license allows.
12. Enter Your Product Key.
The Product Key is included in the Windows 2000 kit, either on the CD cover or a label on
the computer.
13. Enter the computer name, e.g. ECS755SVR1
14. Enter the Administrator account password
15. For Windows 2000 Server Set-up only.
Windows 2000 Components Uncheck IIS, choose default and Next.
16. Adjust Date & Time and Time Zone according to your lacation.
The Time Zone must be the same on all computers, and there must be a checkmark in
Automatically adjust clock for daylight saving changes.

17. Networking Settings choose Custom Settings.
18. In Networking Components the following components must be installed and there must be a checkmark
with each component:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
Internet Protocol (TCP/IP)
19. Mark Internet Protocol (TCP/IP) and click Properties
Click Use the following IP address: and enter an appropriate IP address, Subnet mask and Default gateway.
If there is a DNS server on your network enter the IP address in Preferred DNS server.
20. For a W2K Server mark File and Printer Sharing….. and click properties. Select Maximize datathrougtput
for network applacation.
21. If the computer is member of a workgroup click No, this computer is not on a network, or is on a network
without a domain. Type a workgroup name in the following box.
Workgroup or computer domain: <Workgroup>For example: ECS755
If the computer is member of a Domain click Yes, make this computer a member of the following domain:
Workgroup or computer domain: <Domain> For example: ECS755
Enter the User Name and Password, for a user that has the ability to add computers to the domain.
22. Click Finish to reboot the computer
23. The Network Identification Wizard starts.
Click Next
Choose Who can logon to this computer.
Click Next
Click Finish.
Login to Windows 2000 as Administrator and install additional device drivers not recognised by Windows 2000
setup, e.g. Video adapters, Sound Cards, ATA-100 IDE controllers etc. Check Device Manager for questions marks.
(Devices not properly installed).
Refer to the documentation for the computer.

How to create a Windows 2000 Domain
Due to the complexity of installing, configuring and maintaining a Windows 2000 Domain we highly recommend to
use a Workgroup installation for a ECS system instead of a Domain installation.
When you install a Window 2000 server you install it as a stand-alone server in a workgroup or as Member server in
a domain. After the installation you promote the server to a Domain Controller (DC) and create the domain if it does
not exist. If there is no other domain on the network, or the Domain will not be a child to an existing domain, the
domain you create is called a Root Domain. The DNS (Domain Name System) name of a Root Domain must contain
a ”.” (dot), e.g. ecs755.flsa . Furthermore there must be at least one DNS Server on the network.
To create a Domain and Domain Controller you must:

• Set the computer to use itself as the DNS server
• Set the primary suffix to the DNS
• Install and configure a DNS server
• Run dcpromo.exe to create the domain and promote the computer to a Domain Controller
Creating a Domain
Set the computer to use itself as the DNS server
1. Right click My Network Places and select Properties.
2. Right click Local Area Connection and select Properties
3. Select Internet Protocol (TCP/IP) and click Properties
4. Under Preferred DNS server: type the IP address of the computer
5. Click Advanced and DNS

6. In DNS suffix for this connection: type the name of the domain you are about to create, e.g. ecs755.flsa
Set the primary suffix to the DNS

7. Right click My Computer and select Properties
8. Under Network Identification click Properties and More…
9. In Primary DNS suffix of this computer: type the name of the domain you are about to create, e.g.
ecs755.flsa
10. Reboot the computer when asked
Install and configure a DNS server

11. Start Add/Remove Programs and click Add/Remove Windows Components

12. Select Networking Services and click Details…
13. Set a checkmark in Domain Name System and click OK
14. Select Start/Programs/Administrative Tools/DNS
15. Right click the computer and select Configure the server…
16. Select This is the first DNS server on the network
17. Select Yes, create a forward lookup zone
18. Select Standard Primary
19. In Zone Name type the name of the domain, e.g. ecs755.flsa
20. Check Create a new file… and click Next

21. Check Yes, create a reverse lookup zone, and click Next
22. Check Standard primary and click Next
23. In Network ID: type the first part of the subnet and click Next.
If your subnet mask is 255.0.0.0 you type the first number e.g. 10, if your subnet mask is 255.255.0.0
you type the first 2 numbers e.g. 10.26 etc.

24. Check Create a new file with this file name: and click Next
25. A summary will be displayed and click Finish to complete the installation.
26. In the DNS MMC expand the Forward Lookup Zones, right click the domain and select Properties
27. Under General set Allow dynamic updates? to Yes and click OK
28. Expand Reverse Lookup Zones and right click the subnet and select Properties
29. Under General set Allow dynamic updates? to Yes and click OK
Run dcpromo.exe to create the domain and promote the computer to a Domain Controller
30. Select Start/Run, type dcpromo and click OK
31. Click Next to start the wizard and check Domain controller for a new domain. Click Next
32. Check Create a new domain tree, and click Next
33. Check Create a new forest of domain trees, and click Next
34. In New Domain Name type the full name for the domain, e.g. ecs755.flsa, and click Next

35. In NetBIOS Domain Name choose default and click Next
The NetBIOS name is used later when you add a computer to the domain. In this example the
NetBIOS name of domain ecs755.flsa is ECS755.
36. In Database and Log Locations click Next
37. In Shared System Volume click Next
38. Check Permissions compatible only with Windows 2000 servers and click Next
39. In Directory Services Restore Mode Administrator Password type the password of the administrator
account
Password: <password> For example: password
40. Click Finish to the summary window to complete the creation of the domain and promotion of the computer
to a Domain Controller
41. Click Restart Now
42. You are now ready to make other computers member of the newly created domain.

Making a computer member of a Domain
If you did not make the computer a member of an existing domain during installation you can join the computer to a
domain after the installation of Windows 2000 is complete.
1. Right My Network Places on the desktop and click Properties
2. Double click Local Area Connection and click Properties
3. Mark Internet Protocol(TCP/IP) and click Properties
4. Ensure that the correct DNS server(s) are listed
5. Right click My computer on the desktop and click Properties
6. Choose Network Identification and Properties
7. In Member of click Domain and type the NetBIOS name of the domain.
The NetBios name of a domain is the default name you choose during creation of the
domain, e.g. the NetBIOS name of domain ecs755.flsa is ECS755.
8. Click OK
9. Enter the User Name and Password, for a user that has the ability to add computers to the domain
10. Click OK and OK to reboot the computer.
11. At the Log on to Windows expand Options
12. In Log on to: choose the domain e.g. ECS755, type the password for the account and click OK

Adding an additional Domain Controller
In a Windows 2000 Domain there is no Backup Domain Controllers, all Domain Controllers are “Primary”. To
install an additional Domain Controller you join the computer to the Domain and then promote the computer to a
Domain Controller. In order to gain full redundancy you have to install a DNS server on the second Domain
Controller as well.
To add an additional Domain Controller to a Domain you must:
• Join the computer to the domain.
• Set the computer itself as Alternate DNS server
• Install and configure a DNS server
• Run dcpromo.exe to promote the computer to a Domain Controller
Adding a Domain Controller

Join the computer to the Domain
1. If the computer was not joined the Domain during installation do it now. See earlier chapter
2. Right click My Network Places and select Properties.
3. Right click Local Area Connection and select Properties
4. Select Internet Protocol (TCP/IP) and click Properties
5. Under Alternate DNS server: type the IP address of the computer
Install and configure a DNS server

6. Start Add/Remove Programs and click Add/Remove Windows Components
7. Select Networking Services and click Details…

8. Set a checkmark in Domain Name System and click OK
9. Select Start/Programs/Administrative Tools/DNS
10. Right click the computer and select Configure the server…
11. Select Yes, create a forward lookup zone
13. In Zone Name, type the name of the Domain, e.g. ecs755.flsa
14. In Zone File click Next
15. In Reverse Lookup Zone select Yes, create a reverse lookup zone
17. In Network ID: type the first part of the subnet and click Next.
If your subnet mask is 255.0.0.0 you type the first number e.g. 10, if your subnet mask is
255.255.0.0 you type the first 2 numbers e.g. 10.26 etc.
Run dcpromo.exe to promote the computer to a Domain Controller
18. Select Start/Run, type dcpromo and click OK
19. Click Next to start the wizard and check Additional domain controller for an existing domain. Click Next
20. In Network Credentials type the user name and password of the administrator
21. In Additional Domain Controller click Next

22. In Database and Log Locations click Next
23. In Shared System Volume click Next
24. In Directory Services Restore Mode Administrator Password type the administrator password, e.g.
<password>
25. In the Summary window click Next
26. Click Reboot to complete the installation of an additional domain controller.

After installation of Windows 2000 you have to apply the current service pack. If you after the installation install
additional Windows 2000 components you also have to apply the service pack.
1. Locate the service pack, either on a CD-Rom, on your local hard disk or on the network
2. Open Windows Explorer and browse to locate the service pack directory \i386\update
3. Double click update.exe
4. Select Accept the License Agreement and click Install
5. Click Restart when asked
6. Install additional patches as MDAC2.7, Microsoft Hot fixes etc.
A printer can be installer either as a Local printer or as a Network printer. A Local printer is connected directly to a
port on the computer (LPT or COM) or to a Standard TCP/IP Port you create. A Network Printer is connected to a
shared printer on another computer.
Use the driver CD that comes with the printer.
Installing a Local Printer

Installing a Plug and Play printer only works if the printer is connected directly to a LPT or COM port on the
computer.
3. Select Local Printer and Next
4. If no Plug and Play printers found click Next
5. Choose the port the printer is connected to and click Next
• If the printer is connected to a print server on the network select Create a new port:
• In the dropdown select Standard TCP/IP Port and click Next
• Type the IP address of the print server and a port name.

• Click Next and Finish
6. Choose a printer from the list. If the printer is not listed you must have a driver from the printer
manufacturer and click Have Disk…Click Next
7. Type a friendly name for the printer. Click Next
8. Select Do not share this printer and Click Next
9. Click yes to Do you want to print a test page? Click Next
10. Click Finish to the summary window.
Installing a Network Printer

Before you can connect to a network printer, you must have an account on the computer sharing the printer and have
the proper privileges to use the printer. Furthermore you must be logged in with that account on your computer to
access the printer.
When you use network printing, you have to install the printer for each account.
3. Select Network Printer and Next
4. Select Type the printer name, or click Next to browse for a printer
5. Browse for the printer you want to install and click Next.
6. Click Finish to the summary window

Glossary of Terms
Reference Manual Windows 2000 Installation Glossary of Terms • 15

Index
Reference Manual Windows 2000 Installation Index • 17

TAB
TAB
Reference Manual
Managing Windows Server

2003 for ECS Applications
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: W2K3Configuration_english.doc $
Disclaimer:

Contents
Windows W2K3 Pre-Setup 1
Introduction 1
Computer Configuration 4
System 4
Printers 4
User Configuration 5
Windows Components 5
Start Menu and Task Bar 5
Desktop 6
Control Panel 6
System 6
Account Dependent Configuration 7

Desktop Appearance 7
Folder options 11
System Properties 13
Windows Server 2003 SP1 14
Added Windows Services 14
Index 17
Reference Manual Managing Windows Server 2003 for ECS Applications Contents • iii
Windows W2K3 Pre-Setup
Introduction
Windows Server 2003 is the successor of Windows 2000 Server. The major differences are enhanced security
settings, more granularity over group policy settings and the concept of ‘Shadow files’, which allows backing up
files in-use.
Many of the new settings are configured/controlled using the Group Policy Editor. This editor is not available neither
from the ‘Programs’ folder nor from the ‘Administrative Tools’ folder under ‘Control Panel’. The editor can be
invoked as follows:
Start > Run > Type gpedit.msc
Press OK
The launching Microsoft Management Console (MMC) will look as shown (having selected Standard view)
Initial Group Policy Editor View (having selected ‘Standard’ view)
Reference Manual Managing Windows Server 2003 for ECS Applications Windows W2K3 Pre-Setup • 1
Programmable policies are found by expanding a folder and or its subfolder(s), e.g. ‘Administrative Templates’ with
subfolder ‘Windows Components’. Expanding ‘Windows Explorer’ provides an overview of policies for this
component.
Windows Explorer policies
In order to change the setting for a particular policy doubly click it. In the property sheet there will be three options –
Not configured, Enabled or Disabled. In this particular example select ‘Enabled’ in order to ‘Do not allow Windows
Messenger to be run’. Final click Apply to enable the policy and then OK to exit. Alternately just Click OK to
enable the policy and close the property sheet. The property sheet is shown below.
2 • Windows W2K3 Pre-Setup Reference Manual Managing Windows Server 2003 for ECS Applications
Property sheet for ‘Do not allow Windows Messenger to be run’.
Note: Changing a policy with the Group Policy Editor implies that this setting is in use for all user accounts.
Thus it is not possible to make individual account settings using this editor.
Reference Manual Managing Windows Server 2003 for ECS Applications Windows W2K3 Pre-Setup • 3
Computer Configuration
System
The following setting should be changed:
Expand ‘Computer Configuration\Administrative Templates\System’
Display Shutdown Event Tracker -> Disabled
Printers
The following setting must be disabled in order to allow W2K3 printing via W2K printer’s shares:
Expand ‘Computer Configuration\Administrative Templates\Printers’
Disallow installation of printers using kernel-mode driver -> Disabled
4 • Computer Configuration Reference Manual Managing Windows Server 2003 for ECS Applications
User Configuration
Windows Components
Launch the Group policy Editor and expand ‘User Configuration\Administrative Templates\Windows
Components’
The following policies should be changed:
Windows Messenger\Do not allow Windows Messenger to be run -> Enabled
Windows Messenger\Do not automatically start Windows Messenger initially -> Enabled
Windows Update\Remove access to use all Windows Update features -> Enabled
Start Menu and Task Bar

Launch the Group policy Editor and expand ‘User Configuration\Administrative Templates\Start Menu &
Task Bar’
The following settings should be changed:
Disable and remove links to Windows Update -> Enabled
Remove My Documents icon from Start Menu -> Enabled
Disable personalized menus -> Enabled
Prevent grouping of taskbar items -> Enabled
Force classic Start Menu -> Enabled
Remove Balloon Tips On Start Menu items -> Enabled
Reference Manual Managing Windows Server 2003 for ECS Applications User Configuration • 5
Desktop
The following Desktop settings should be changed:
Expand ‘User Configuration\Administrative Templates\Desktop’
Remove My Documents icon on the Desktop -> Enabled
Control Panel
The following Control Panel settings should be changed:
Expand ‘User Configuration\Administrative Templates\Control Panel’
Force classic Control Panel Style -> Enabled
Display\Screen Saver -> Disabled
System
The following System settings should be changed:
Expand ‘User Configuration\Administrative Templates\System’
Download missing COM components -> Disabled
Windows Automatic Updates -> Enabled
6 • User Configuration Reference Manual Managing Windows Server 2003 for ECS Applications
Account Dependent
Configuration
Desktop Appearance
Launch “Display’ item in the Control Panel. The display property looks as shown below.
Themes property sheet
The Themes service is default disabled and the ‘Windows Classic ‘ theme is selected by default. Next select the
‘Screen Saver’ property
Reference Manual Managing Windows Server 2003 for ECS ApplicationsAccount Dependent Configuration • 7
‘Screen Saver’ property sheet
Press ‘Power’ and the following property sheet are displayed.
8 • Account Dependent ConfigurationReference Manual Managing Windows Server 2003 for ECS Applications
‘Power Options Property’
From the pull-down menu select ‘Presentation’ and press ‘Apply’

Finally select the ‘Hibernate’ tab and verify that Hibernation is deselected (disabled).
Power options Hibernation Property
Folder options
It is noted that changing the ‘Folder Options’ is done a per user basis.
Launch ‘Folder Options’ in the control panel. Having gone through the above settings its property sheet looks as
shown
In the View property sheet the settings outlined below are recommended.
The recommended settings are displayed at the following two pictures.
When configuration is completed press Apply and then Apply to All Folders (if not dimmed).
System Properties
This “System Property” is done on a per user basis.
Launch ‘System’ in the control panel. Select the Advanced tab and then the Performance tab. Set Visual
Effects to Adjust for best performance. The recommended setting is shown in the picture
Windows Server 2003 SP1
As of Windows Server 2003 SP1 major changes in security settings have been made. The changes breaks existing
ECS program executions. To avoid this kind of problems installation in the following order is recommended:
1. Install Windows Server 2003

2. Install Windows Server 2003 SP1
3. Install ECS
If Windows Server 2003 SP1 is installed on top of a running ECS system proceed as follows:
1. Refresh the ECS installation, i.e. install the ECS system and all the relevant hot fixes.
Added Windows Services

Installing ECS version 7.0.4 or 7.0.5 with the latest hot fix for XP and W2K3 will disable the following services in
Windows server 2003:
• WmdmPmSN (Portable Media Serial Number)

• WZCSVC (Wireless Zero Configuration)
• ERSvc (Error reporting)
• SharedAccess (Windows Firewall/Internet Connection Share (ICS))
• IP6Fw (IPv6 Internet Connection Firewall driver)
• Uploadmgr (Upload Manager)
Glossary of Terms
Reference Manual Managing Windows Server 2003 for ECS Applications Glossary of Terms • 15
Index
Reference Manual Managing Windows Server 2003 for ECS Applications Index • 17
TAB
TAB
Reference Manual
Managing Windows XP for

ECS Applications
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: XPConfiguration_English.doc $
Disclaimer:

Contents
Windows XP Pre-Setup 1
Introduction 1
Welcome Screen (Log On to Windows) 3
Windows Components 3
Start Menu and Task Bar 3
Desktop 3
Control Panel 3
System 4
Desktop Appearance 4
Folder options 6
Power settings 8
System Properties 9
XP service pack 2 10
Added Windows services 10
Index 13
Reference Manual Managing Windows XP for ECS Applications Contents • iii

Windows XP Pre-Setup
Introduction
Windows XP is the successor of Windows 98 based on Windows 2000 features. It is therefore preconfigured as a
Multimedia platform. Having installed an ECS system all accounts will be displayed on the Welcome Screen and an
account might have a bath top duck as an activation icon. For ECS application this and a lot of other features are not
acceptable. This document goes through a number of steps converting a Windows XP Professional system into a
Windows 2000 look alike system.
Many of the features are configured using the Group Policy Editor. This editor is not available neither from the
‘Programs’ folder nor from the ‘Administrative Tools’ folder under ‘Control Panel’. The editor can be invoked as
follows:
Start > Run > Type gpedit.msc
Press OK
The launching Microsoft Management Console (MMC) will look as shown (having selected Standard view)
Initial Group Policy Editor View (having selected ‘Standard’ view)
Programmable policies are found by expanding a folder and or its subfolder(s), e.g. ‘Administrative Templates’ with
subfolder ‘Windows Components’. Expanding ‘Windows Explorer’ provides an overview of policies for this
component.
Reference Manual Managing Windows XP for ECS Applications Windows XP Pre-Setup • 1

Windows Explorer policies
In order to change the setting for a particular policy doubly click it. In the property sheet there will be three options –
Not configured, Enabled or Disabled. In this particular example select ‘Enabled in order to ‘Do not allow Windows
Messenger to be run’. Final click Apply to enable the policy and then OK to exit. Alternately just Click OK to
enable the policy and close the property sheet. The property sheet is shown below.
Property sheet for ‘Do not allow Windows Messenger to be run’.
Note: Changing a policy with the Group Policy Editor implies that this setting is in use for all user accounts.
Thus it is not possible to make individual account settings using this editor.
2 • Windows XP Pre-Setup Reference Manual Managing Windows XP for ECS Applications

Welcome Screen (Log On to Windows)
In order to replace the welcome screen with a normal ‘Log On to Windows’ screen locate the ‘User Accounts’
entry in the control panel.
Double-click User Accounts to open the property sheet and then click ‘Change the way Users log on or off’.
Next uncheck the ‘Use the Welcome screen’ and then press ‘Apply Options’.
Log off to verify the ‘Log On to Windows’ setting.
Windows Components
Launch the Group policy Editor and expand ‘User Configuration\Administrative Templates\Windows
Components’
The following policies should be changed:
Windows Messenger\Do not allow Windows Messenger to be run -> Enabled
Windows Messenger\Do not automatically start Windows Messenger initially -> Enabled
Windows Update\Remove access to use all Windows Update features -> Enabled
Start Menu and Task Bar

Launch the Group policy Editor and expand ‘User Configuration\Administrative Templates\Start Menu &
Task Bar’
The following settings should be changed:
Remove links and access to Windows Update -> Enabled
Remove My Documents icon from Start Menu -> Enabled
Turn off personalized menus -> Enabled
Prevent grouping of taskbar items -> Enabled
Force classic Start Menu -> Enabled
Remove Balloon Tips On Start Menu items -> Enabled
Desktop
The following Desktop settings should be changed:
Expand ‘User Configuration\Administrative Templates\Desktop’
Remove My Documents icon on the Desktop -> Enabled
Control Panel
The following Control Panel settings should be changed:
Expand ‘User Configuration\Administrative Templates\Control Panel’
Force classic Control Panel Style -> Enabled
Display\Screen Saver -> Disabled

System
The following System settings should be changed:
Expand ‘User Configuration\Administrative Templates\System’
Download missing COM components -> Disabled
Windows Automatic Updates -> Enabled
Desktop Appearance
It is noted that changing the ‘Desktop Appearance’ is done on a per user basis.
Launch ‘Display’ item in the Control Panel. Select the Appearance property sheet.
Appearance property sheet
Change ‘Windows XP style’ to ‘Windows Classic’ and press apply. The property sheet then gets the classic
appearance.

Classic Appearance property sheet
Changing the background is done by selecting the Themes property. Initially this property sheet looks as shown
below.

Selecting Windows Classic and pressing Apply changes the background
Folder options
It is noted that changing the ‘Folder Options’ is done a per user basis.
Launch ‘Folder Options’ in the control panel. Having gone through the above settings its property sheet looks as
shown

In the View property sheet the settings outlined below are not only recommended but with respect to the ‘Use simple
file sharing (Recommended)’ it is mandatory. Checking this feature implies that it is impossible to view security
settings on shares, folders and files.
The recommended settings are displayed at the following two pictures.
Most important is to disable (uncheck)

“Use simple file sharing (Recommended).”
When configuration is completed press Apply and then Apply to All Folders (if not dimmed).

Power settings
The recommended power settings are the display and hard disks are never turned off. This setting can be achieved by
selecting ‘Presentation’ under ‘Screen Saver’ in the ‘Display’ properties. (Select Display under the Control
Panel). The pictures provide the details.
Selecting Power ...
Power setting for monitor and hard disks
Finally, it must be checked that the hibernation is disabled. Selecting the Hibernate tab does this. The recommended
setting is shown in the picture

System Properties
This “System Property” is done on a per user basis.
Launch ‘System’ in the control panel. Select the Advanced tab and then the Performance tab. Set Visual
Effects to Adjust for best performance. The recommended setting is shown in the picture

XP service pack 2
As of service pack 2, XP has undergone extensive security modifications and a lot of default security settings have
been added/modified.
DCOM security has been enhanced intensively and remote launching of dcom applications (ECS server
programs/services) require dcom configuration changes. Other changes including that ANONYMOUS users can no
longer launch remote dcom application by default, has no implication on ECS programs as these have never relied
on this feature.
In order to further enhance security the built-in Windows firewall (ICF/ICS) is enabled by default. As DCOM and
firewalls do not work well together the firewall must be disabled in order to allow remote clients to launch dcom
application running behind the Firewall. Installing service pack 2 enables the firewall unconditionally. Thus
installing this service pack after the ECS installation will effectively disable the ECS server
applications and thus render the ECS system useless.
It is recommended that installations be done in the following order:

1. Windows XP
2. Windows XP SP2
3. ECS
If Windows XP SP2 is installed on top of an ECS system proceed as follows:

1. Refresh the ECS installation, i.e. install the ECS system and all the relevant hot fixes.
Or
2. Manually disable the services listed below
3. Modifying the dcom security (Using the ‘Component Services’ Snap-in) in order to allow members of
the ‘Flsa Users’ group to Launch and Access com servers both from the local computer as well as from
remote computers. (The group must be added under all four security settings)
Added Windows services

As Windows XP Professional does come with heavy support of Multi Media devices it has a number of multimedia
services that should be disabled. Installing ECS version 7.0.4 and 7.0.5 with the latest hot fix for XP and W2K3 will
disable the following services:
• WmdmPmSn (Portable Media Serial Number)

• Themes (Themes)
• WZCSVC (Wireless Zero Configuration)
• FastUserSwitchingCompatibility (Fast User Switching Compatibility)
• ImapiService (IMAPI CD-Burning COM Service)
• WebClient (Web Client)
• ERSvc (Error reporting)
• Wscsvc (Security Center)
In addition the following services will also be disabled:

• IP6Fw (IPv6 Internet Connection Firewall driver)
• SharedAccess (Windows Firewall/Internet Connection Share (ICS))

Glossary of Terms
Reference Manual Managing Windows XP for ECS Applications Glossary of Terms • 11

Index
Reference Manual Managing Windows XP for ECS Applications Index • 13

Reference Manual
ECS Installation
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: SdrW2KInstallation30_English.doc $
Disclaimer:

Contents
ECS Installation 1
Introduction 1
Hardware Requirements 1
Installation Preparation 1
Installation Procedure 2
Installation from CD-ROM 2
Installation from FLSA Dev Support Web 2
ECS Customization 3
Display Settings 4
Power Options 5
Server Setting 5
Domain Setup 6
Netlogon Share on DC (Domain Controller) 6
Policy 6
User Roaming Profiles 7
Activation of Roaming Profiles 7
ECS Un-Install 9
Un-Install Procedure 9
Index 13
Reference Manual ECS Installation Contents • iii

ECS Installation
Introduction
This help document describes the procedure used to install the ECS process system software.
Hardware Requirements
The host system must meet or exceed the following requirements:
Computer Personal Computer must be member of the Microsoft Windows 2000 HW Compatibility List.
Memory Minimum 128 MB RAM for a professional and 256 MB RAM for a server
Disk Space Minimum 6 GB for a professional and 8 GB for a server.
Display Resolution 1280 x 1024 pixels or better, minimum 32768 colors.
Operating System Microsoft Windows 2000. The following operating system variants are supported:
• Professional
• Server
• Domain Controller
Application Software No additional software is required.
Installation Preparation
Before the ECS installation is started, verify the following:
1. Networked host system must have correct network settings. It is important to ensure that a networked host
has been given a computer name that is unique within the associated workgroup.
2. Any previous ECS installation has been properly un-installed.
3. If installing the ECS system in a Domain environment, the Domain Controller must be installed and
configured.
Reference Manual ECS Installation ECS Installation • 1

Installation Procedure
An ECS system can be installed either from a CD-ROM supplied by F.L.Smidth A/S - Automation or from a file
obtained through the FLSA Dev Support Web. The installation procedure for either source is provided below.
Please observe that an ECS system is a licensed product. The software cannot execute in a Server (MOP)
configuration without the installation of a hardware dongle and a license file. F.L.Smidth A/S - Automation supplies
these items. The license file can be added either during the installation of the ECS system or after the installation has
completed.
Installation from CD-ROM

1. Logon to the host system as Administrator.
2. Insert a CD-ROM with the ESC system and wait for the installation program to auto start. If the auto start
fails, open the Explorer and display the contents of the CD-ROM root directory. Double-click the
Setup.exe file to start the installation program.
3. Follow the instructions presented by the installation program. In particular, be aware of the following
topics:
• A license is only needed when the system will be configured as a Server.
• When the Sentinel Driver Installation starts choose default and Next. Remember to remove the dongle
during installation.
• In the Enter Account Name window, do not modify the default user name - flsa.
• When the View log file option is offered, make a careful examination of the installation log to identify
any errors. (This file will also be available after the installation).
• Accept the option: Yes, I want to restart my computer now when posted by the installation
program. Upon request, logon as user FlsaMain.
When the installation program completes successfully, the ECS system starts up in the Maintenance mode ready
for configuration.
Installation from FLSA Dev Support Web

2. Open an Internet Explorer and connect to the FLSA Dev Support Web: http://www.flsadev.dk. Find the
desired version of the ECS system and follow the instructions on how to download the corresponding self-
extracting exe file. Wait for the download to complete.
3. When the download has completed the ECS NTech Release Installation window is displayed
automatically, if you had selected Open. If you had selected Save as you must double click on the file to get
the Unzip dialog.
2 • ECS Installation Reference Manual ECS Installation

Accept the proposed temporary folder in which the system files will be unzipped or add a subfolder with the
same name as the system to be installed. If the folder defined already exists, delete its contents. Enable the
Overwrite Files Without Prompting and when Done Unzipping Run: .\setup\setup.exe check
boxes.
4. Click on the Unzip button and wait for the unzip operation to complete. When the completion message is
acknowledged the installation program will start automatically if the When Done Unzipping Run…
checkbox is enabled. Otherwise, the installation program must be started manually by opening the Explorer
and double clicking on the Setup.exe file in the temporary folder.
5. Follow the instructions generated by the installation program. In particular, be aware of the following
topics:
• A license is only needed when the system will be configured as a Server.
• When the Sentinel Driver Installation starts choose default and Next. Remember to remove the dongle
during installation.
• In the Enter Account Name window, do not modify the default user name - flsa.
• When the View log file option is offered, make a careful examination of the installation log to identify
any errors. (This file will also be available after the installation).
• Accept the option: Yes, I want to restart my computer now when posted by the installation
program. Upon request, logon as user FlsaMain .
When the installation program completes successfully, the ECS system starts up in the Maintenance mode ready
for configuration.
ECS Customization
After a successful installation, the system needs to be customized for proper performance.
Group Policy
Open Group Policy and select Computer Configuration/Windows Settings/Security Settings/Local Policies/User
Right Assignment. Right click Change the system time and disable this right for Power Users.
Screen Savers
Open Windows Explorer and browse to\\WINNT\System32 and delete all 3D Screen savers, i.e. files in the form
*3D*.src
Indexing Service
Open Administrative Tools/Services. Stop Indexing Service. Right click Indexing Service and select Properties. In
Startup type: choose Disable
Pagefile
1. Rightclick My Computer and select Properties. Under Advanced /Performance Options…click Change to
Virtual memory
2. Set Initial size and Maximum size to aprox 3 times physical memory.
3. E.G. 128 MB physical memory gives a pagefile size of 400MB, 256MB physical memory gives 800MB
4. Click Set and OK
5. Close System Properties window and restart.

Display Settings
In order to operate the ECS system successfully the following display settings should be made.
1. Open the Display Properties window by right clicking on the desktop and selecting Properties from
the menu displayed.
2. Select the Settings tab.
3. Set the Screen Area to 1280 by 1024 pixels and the Color Palette to 32768 Colors or greater.
4. Click Advanced… and the Monitor tab. Set Refresh Frequency to the highest value for the actual
Desktop Area setting. Reduce this value if the screen tilts or appears in reduced size.
5. Select the Effects! tab.
6. Disable the Show window contents while dragging option.

Power Options
1. Open the Display Properties window by right clicking on the desktop and selecting Properties from
the menu displayed.
2. Select the Screen Saver tab.
3. Click the Power… button.
4. Select the Power Schemes tab.
5. Under Power schemes select Presentation.
Server Setting
In order to operate the ECS system successfully the following server settings must be made.
1. Right click My Network Places on the desktop and select Properties.
2. Right click Local Area Connection and select Properties.
3. Select File and Printer Sharing for Microsoft Networks and click Properties…
4. In Server Optimization: set Maximize data throughput for network applications
5. Click OK and Yes to restart your computer now.

Domain Setup
Due to the complexity of installing, configuring and maintaining a Windows 2000 Domain we highly recommend to
use a Workgroup installation for a ECS system instead of a Domain installation.
In a dual ECS system installed as a Domain you must configure both the servers as Domain Controllers and for a
truly redundant system both servers must host a DNS server.
Netlogon Share on DC (Domain Controller)

For installing and configuring a Windows 2000 domain, refer to W2KInstallation30_English.doc
The domain users use the Netlogon share when they are validated in the domain. The netlogon share contains the
policy files and the roaming profiles.
The Netlogon share replicates among all domain controllers:
C:\winnt\sysvol\sysvol\ "domainname"\scripts
In a Windows 2000 domain you don't have to configure the replication, this is done automatically by Windows 2000.
Policy
To assign policies to the user and system, refer to the online help document for SDR W2K Security.

User Roaming Profiles
Roaming profiles can be used both in a workgroup or domain installation. If the roaming profile is not available at
login W2K gives a warning and uses the local profile instead. When you log out from a roaming profile, W2K saves
the profile both as a roaming profile and a local profile.
Flsa roaming profiles are located in the c:\FlsaDev\Profiles folder on the ECS Server. In order to use these
profiles you must share this directory as FlsaProfiles. Set the permissions to Everyone read and Administrator
to full control. In this manner users are not able to save changes to their profile when they log out.
Activation of Roaming Profiles

Workgroup
To activate roaming profiles for a user open My Computer, System Tools, Local Users and Groups.
Double-click the user, select the profile tab and enter the profile path.
Path : \\<Server Name>\FlsaProfiles\%USERNAME%
Click OK to accept the changes and then close the Local Users and Groups.

Domain
In a domain you open the Active Directory Users and Computers. Double-click the user, select the profile tab
and enter the profile path.
If you want the roaming profiles to be replicated among the domain controllers you have to copy the profiles to the
Netlogon share on the domain controllers. Right click My computer and select Properties. Select the User
Profiles tab and click the user you want to copy. Click Copy to… and enter the path to the NETLOGON share. In
the profiles tab for the user you have to type the new path to where the profile is located.

ECS Un-Install
This section describes the procedure used to remove an existing ECS installation from a host system.
Un-Install Procedure
It will be necessary to have Administrator privileges before performing the following procedure.
1. From the Maintenance utility, restart the computer in maintenance mode. When the logon prompt
appears, log on as FlsaMain.
2. From the Maintenance window, select the Backup tab, enable all data sets listed and make a backup to
the backup folder. Examine the backup log to ensure that the backup process completed successfully. This
action only applies to a Server system.
3. From Computer Management start the Services utility. Select the SDR Starter (System) service
and click on Stop.
4. Open the Windows NT Task Manager utility and click on the Processes tab. Locate and select
SdrWatchDogUi30. Click on the End Process command.
5. From the Explorer, open the …\FLSADev\Bin\Sys folder and double-click on the PtaReg30.exe file.
Type DevUnReg SDR at the PtaReg> prompt and press the keyboard <Enter> key. This will unregister
all SDR services.
6. From the Start menu, select Run.... Type RegEdit in the Open field and press OK. This will start the
Registry Editor. Select the HKEY_LOCAL_MACHINE\SOFTWARE\FLS Automation A/S entry
and delete it.
7. Rename the …\FLSADevBackup folder to (For example:C:\ECSBackUp). This action only applies to a
Server system where data has been backed up as described in step 2.
8. Copy the license file located in ...\FLSADev\Bin\License to a temporary location (For example:
C:\ECSBackUp). This action only applies to a Server system where the license file will be used in the
new ECS installation.
9. Logon as Administrator.
10. Delete the following folders: ...\FLSADev and ...\FLSALog
11. Open an Explorer and navigate to the Scheduled Tasks under the ‘My Computer/Control Panel’.
Then delete the task ‘EcsBackupTask’ if it exists.
12. Start the Component Service program. Then select ‘Properties’ for ‘My Computer’. Select the
property sheet designated ‘Default Security’ or ‘COM Security’. In the former case remove the group
‘Flsa Users’ from the ‘Default Access Permissions’ and from the ‘Default Launch Permissions’
and in the latter case remove the group ‘Flsa Users’ from all entries under ‘Access Permissions’ and
‘Launch and Activation Permissions’.
13. From Computer Management start the Local Users and Groups. Expand Users and delete the
Flsa, FlsaMain and FlsaServer users. Expand Groups and delete the Flsa Administrators and Flsa
Users groups.
14. From Computer Management start the Local Users and Groups. Expand Users and delete the
Flsa, FlsaMain and FlsaServer users. Expand Groups and delete the Flsa Administrators and Flsa
Users groups.
15. Open c:\Document and Settings and delete the Flsa, FlsaMain and FlsaServer folders.
16. Delete the following files, if present:
...\Document and Settings\ Administrator\Local Settings\ Temp\ SdrRegisterErr.txt
...\...\Document and Settings\ Administrator\Local Settings\Temp\SdrRegisterOut.txt

Glossary of Terms
Reference Manual ECS Installation Glossary of Terms • 11

Index
Reference Manual ECS Installation Index • 13

Reference Manual
ECS Service Pack

Installation
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: SDRW2KServicePack30_English.doc $
Disclaimer:

Contents
ECS Service Pack Installation 1
Introduction 1
ECS System Release 1
ECS Service Pack 1
Installation Procedure 2
Glossary of Terms 5
Index 7
Reference Manual ECS Service Pack Installation Contents • iii

ECS Service Pack Installation
Introduction
This document describes the details related to ECS system service packs.
ECS System Release

An ECS system software release consists of two parts. The first part is the runtime system representing all the files
required to install and run an ECS system. The second part is the service pack that can be used to upgrade the
runtime system from the previous release to the current release level.
The name of a runtime system depends on whether it represents a primary release or a service release: An ECS
software release is named according to the convention:
SDRv<major_version_number>.minor_version_number>.sr<release_number>
The major and minor version numbers identify the primary release. The software is referred to as the primary
release when no service packs are applied. This is also referred to as service release 0 (zero). When the primary
release is upgraded from a service pack, the software is called a service release.
If the software is a primary release (Service_release_number = 0) then the name is identified as shown:
SDRv<Major_version_number>.<Minor_version_number>
e.g. SDRv7.0
When the SDRv7.0 system is upgraded, a service release pack is installed. The service pack is identified as
SDRv7.0sp1. After the service pack is installed, the runtime system is identified as SDRv7.0sr1.
ECS Service Pack

A service pack is a collection of ECS files combined with an installation program. It is provided either on a CD-
ROM or in the form of a self-extracting executable file. The service pack provides a means for obtaining a newer
version of an ECS system with less effort than otherwise required to make a complete reinstallation of the runtime
system.
A service pack can only upgrade a runtime system to a higher service release level. In other words, a service pack
cannot be used to take a system to a higher major or minor version.
A service pack will upgrade a system from the first minor release to the service release level given by the service
pack. For example, to obtain SDRv7.0sr2 one only need to apply the service pack SDRv7.0sp2. The service packs
are cumulative, i.e. you don’t have to install e.g. SDRv7.0sp1 before you install SDRv7.0sp2
The service pack will prevent users from down grading the system. E.g. preventing users from installing
SDRv7.0sp1 on a system previously upgraded to service release SDRv7.0sr2.
Reference Manual ECS Service Pack Installation ECS Service Pack Installation • 1
Obtaining a Service Pack
There are two ways in which to obtain a service pack:
1. From a CD-ROM supplied by F.L.Smidth A/S - Automation
2. From the FLSA Software Support Web: http://www.flsadev.dk. (This service is only available to users
registered by FLSmidth Automation ).
What does the service pack do

The service pack generally replaces files on the system that need's an update. More specific we can say that new files
of this service pack are always copied. Files that are changed since the primary release will be replaced on the target
system, except for the contents of the directories .\Prodb located in the "Flsadev" on the target system hard disk.

Preparation
It is strongly recommended that the release notes associated with the service pack be reviewed prior to installation.
The release notes are contained in the ReadMeSdr.htm file in the root directory of the service pack CD-ROM or
the FLSA Software Support web site.
It should be verified that the service pack matches the runtime system installed. This is only true if both have the
same major and minor version number. The runtime system for a primary release corresponds to service release level
0.
If there is a suspicion that the existing installation has become corrupted it may be preferable to obtain and reinstall a
new runtime system instead of trying to make an upgrade with a service pack.
If an upgrade of an existing installation involves a migration across several release levels, for example bringing the
system SDRv7.0sr2 to a level corresponding to SDRv7.0sr5, an alternative could be to reinstall the runtime
system in the desired version.
Installation Procedure
Before a service pack can be installed the following must be completed in the defined order:
1. Restart the computer in maintenance mode. Logon as FlsaMain.
2. As always, perform a backup to tape or disk before updating your system with a service pack. However, do
not restore the backup after the service pack installation, because the service pack does not modify dynamic
databases in .\Prodb and you may end up downgrading your system with the old files of the backup.
3. From the Maintenance window select the Backup tab and select all the data sets listed. Make a backup
to the backup folder.
4. Restart the computer in maintenance mode again. Logon as FlsaMain.
5. Close the Maintenance window.
6. Open the Windows 2000 Task Manager utility, click on the Processes tab and do End Process to
stop the SdrWatchDogUi30.
Proceed to CD-ROM Installation or Web Site Installation.
2 • ECS Service Pack Installation Reference Manual ECS Service Pack Installation
CD-ROM Installation
1. Insert the service pack CD-ROM and wait for the installation program to autostart.
2. When the installation has finished, check the installation log for any errors and restart the computer. Logon
as user FlsaMain.
3. Check the ECS system settings and redo any changes that may have occurred as a result of applying the
service pack.
4. From the Maintenance window, restart the computer in run mode. Logon as user Flsa.
Web Site Installation

A user name and a password to the service pack facility are required.
1. Connect to the FLSA Software Support Web: http://www.flsadev.dk.
2. Find the desired service pack and follow the download instructions.
3. When the download has completed, the ECS Service Pack Installation window is automatically
displayed. Accept the proposed temporary folder in which the service pack files will be unzipped.
4. Enable the Overwrite Files Without Prompting and when Done Unzipping Run:
.\setup\setup.exe checkboxes.
5. Press the Unzip button and wait for the unzip operation to complete. When the completion message is
acknowledged, the service pack installation program will start automatically.
6. When the service pack installation has finished, check the installation log for any errors and restart of the
computer. Logon as user FlsaMain.
7. Check the ECS system settings and redo any changes that may have occurred as a result of applying the
service pack.
8. Now make a new backup of your system that contains the files of the service pack. This will prevent you
from down grading your system by restoring backups made prior to the service pack installation.
9. From the Maintenance window, restart the computer in run mode. Logon as user Flsa.
Reference Manual ECS Service Pack Installation ECS Service Pack Installation • 3
Glossary of Terms
Reference Manual ECS Service Pack Installation Glossary of Terms • 5

Index
Reference Manual ECS Service Pack Installation Index • 7

Reference Manual
Time Synchronization
(W2K/XP/W2K3)
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: SdrTimeSynchronization_English.doc $
Disclaimer:

Contents
Time Synchronization 1
Introduction 1
Implementation Issues 2
Pitfalls 6
Concluding Remarks 6
Glossary of Terms 7
Index 9
Reference Manual Time Synchronization (W2K/XP/W2K3) Contents • iii

Time Synchronization
Introduction
In Windows 2000 Microsoft implemented the Simple Network Time Protocol (SNTP) to ensure that computers in
domains had their time synchronized, i.e. all computers have identical date and time. Whether or not the time is true
in absolute terms was less important. Time synchronization is required in domain configurations as these use
Kerberos authentication, which depends heavily on precise time information.
Workgroup configurations can also benefit from the SNTP implementation to ensure that the individual computers
are synchronized with respect to their partner computer. A few registry settings must be added to accomplish this
time synchronization.
The ECS Partner Setup Configuration UI just defines these registry key and starts/restarts the Windows Time service
(W32Time) in workgroup configurations, while it leaves everything to the operating system in domain
configurations.
As of Windows XP and later versions Microsoft has implemented the full Network Time Protocol (NTP), which
makes it possible to obtain precise absolute times over the Internet or through specialized Time Provider equipment.
To ensure compatibility between the SNTP and the NTP protocol both uses the same port (UDP:123).
With respect to domain configurations there seems to be no changes. However, there are important changes with
respect to workgroup configurations. The Date/Time Properties UI has got a new tab designated ‘Internet Time’ and
most features can be configured using the Group Policy Editor. Misconfiguration is eminent as registry key name
NtpServer is found under at least 3 different key (Software, policy and services). Thus major changes in the registry
have been found.
These UI/registry changes require modification of the ECS Partner Setup Configuration UI program.
Reference Manual Time Synchronization (W2K/XP/W2K3) Time Synchronization • 1

Implementation Issues
This paragraph addresses workgroup configurations only.
Windows 2K
Under the W32Time service Parameters key in the registry add the following entries:
• LocalNTP (must be set to one – implies that the local computer is acting as a time provider)
• NtpServer (must be set to the name of the selected time server)
Followed by:
• net stop w32time
• net start w32time
In order to ensure that the setting are effective.

These steps are done on all workgroup computers partly during installation and partly during configuration.
The relevant registry settings are shown in registry snapshot.
Windows XP/2K3
The registry has been extended and reorganized to accommodate changes in the W32Time service, in properties of
the ‘Date/Time’ UI (‘Internet Time’ tab) and in the policy editor (gpedit.msc).
The following 3 parts of the registry hold the configuration information for the ‘Windows Time’ service:
1. The registry keys for the ‘Windows Time’ service (W32Time) are located under the key
‘CurrentControlSet\Services\W32Time’.
2. The registry subkeys for the ‘Date/Time’ UI are located under the main key
‘SOFTWARE\Microsoft\windows\CurrentVersion\DateTime’.
3. The ‘Policy Editor’ sets/removes subkyes under the key W32Time located under the generic key
‘SOFTWARE\Policies\Microsoft’.
The name of NtpServer, e.g. the name of the ‘Time Server’, can be specified in 3 different parts of the registry. To
avoid confusion usage of the ‘Policy Editor’ is discouraged.
In order to use the ‘Update Now’ button on the ‘Internet Time’ tab, the name of the designated Time Server must
be entered in the ‘Server’ pulldown list and the changes must be saved pressing the ‘Apply’ button. Pressing the
‘Apply’ button results in two changes in the registry (one below the software key and one below the services key).
2 • Time Synchronization Reference Manual Time Synchronization (W2K/XP/W2K3)

Furthermore, the ‘Time server’ specified must be classifiable as a ‘reliable time source’. Synchronizing with a
‘non-reliable time source’ returns the error:
An error occurred while Windows was synchronizing with <server>. The time sample was rejected because: The
peer’s stratum is less than the host’s stratum.
In order to simply configuration all computers will be configured as follows:
Under the subkey ‘NtpServer’ of the key \W32Time\TimeProviders\ the following entry will be modified:
• Enabled (will be set to one – implies that the local computer can act as time provider)
The registry settings should now look as follows:
Under the subkey ‘NtpClient’ of the key \W32Time\TimeProviders\ the following entry will be modified:
• SpecialPollInterval (will be set to 300 (5 minutes) - implies that the computer is synchronized every 5
minutes)
The registry settings should look as shown.
Under the subkey ‘Parameters’ of the key \W32Time\ the following entries will be modified:
• NtpServer (must be set to the name of the selected timeserver. Followed by ‘,0x1’)
• Type (must be set to ‘NTP’)

The registry settings should look as shown below.
Under the subkey ‘Config’ of the key \W32Time\ the following entry will be modified:
• AnnounceFlags (must be set to 5 in order to designate the computer as reliable)
The registry settings will now look as shown
Finally, the following entries under the ‘Servers’ subkey (located under
SOFTWARE\Microsoft\windows\CurrentVersion\DateTime) must be modified:
• Default (must be set to zero)
• 0 (must be set to name of the time provider)

The registry settings will now look as shown below
In order to make the changes effective the following commands should be given:
• w32tm /config /update
The above configuration implies that time synchronization works properly and that the content of the ‘Internet Time’
property sheet will look as shown below after a successfully time synchronization
Manual synchronization can be performed using the command

• W32tm /resync

Pitfalls
Using the above settings implies that the following error is returned when ‘Update Now’ is pressed on a computer
being defined as its own timeserver:
An error occurred while windows was synchronizing with <server>. The time sample was rejected because: Round-
Trip delay too large.
In Windows XP and Windows Server 2003 systems it appears as if time synchronization takes place at predefined
points of time only. This implies that rebooting a computer might not result in a time synchronization operation. In
case of Windows 2000 systems time synchronization is always performed following a reboot. Furthermore changing
the time on the computer designated as the timeserver will not result in an immediate update on computers
depending on this server.
Furthermore as of Windows XP with SP1 and Windows Server 2003 it is not possible to change the poll rate due to
the problem reported in Microsoft Knowledge Base Article – 823456.
Concluding Remarks
To cope with the changes in the functionality of the w32time program modifications not only in the ECS Partner
Setup Configuration UI program and its support programs but also some minor modification in the installation
program are required.
A hot fix has been developed for ECS version 7.0sr3. The Partner Configuration and the Partner Setup Configuration
UI’s will attempt to synchronize with the timeserver, whenever the ‘Apply’ button is pressed and when the
Application itself exits. Please note, that time synchronization takes a while on Windows XP and Windows Server
2003 Systems.

Glossary of Terms
Reference Manual Time Synchronization (W2K/XP/W2K3) Glossary of Terms • 7

Index
Reference Manual Time Synchronization (W2K/XP/W2K3) Index • 9

Reference Manual
QCX Installation
On Windows 2000
F.L.Smidth - Automation A/S
Høffdingsvej 77
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version QCXv7 $Revision:: 4 $

Author Hoegni Baerentsen
Last modified by $Author:: Hewa $
Name of Word File $Workfile:: QcxW2KInstallation30_English.doc $
Index Range 0-1000
Disclaimer:
by F.L.Smidth A/S. F.L.Smidth assumes no responsibility for any errors that may appear in this document.
In no event shall F.L.Smidth be liable for direct, indirect, special, incidental or consequential damages of any nature
or kind arising from the use of this document, nor shall F.L.Smidth be liable for incidental or consequential damages
Options specified and described in the F.L.Smidth documentation as part of the general description - but initially
Copyright © F.L.Smidth A/S.

Contents
QCX Installation ........................................................................................3
Introduction................................................................................................................................ 3
Software Requirements....................................................................................................... 3
Hardware Requirements ..................................................................................................... 4
Installation Preparations ..................................................................................................... 4
Microsoft .NET Framework 1.1................................................................................................. 4
Microsoft SQL Server 2000 Installation .................................................................................... 4
Prerequisites........................................................................................................................ 4
SQL Server Installation Procedure on the QCX server ...................................................... 5
SQL Server Installation Procedure on QCX clients............................................................ 6
QCX Installation Procedure....................................................................................................... 6
Installation from CD-ROM................................................................................................. 6
Installation from FLSA Dev Support Web ......................................................................... 7
QCX Un-Install Procedure......................................................................................................... 8
Un-Install Procedure........................................................................................................... 8
Reference Manual QCX NTech Installation Contents • i

QCX Installation
Introduction
This help document describes the procedure used to install the QCX system software.
Software Requirements
The QCX system is an add-on module of the ECS/SDR process control software
family, which must be installed before QCX. Please refer to the ECS/SDR Installation
Reference Manual for information about how to install ECS/SDR.
Next, Microsoft SQL Server 2000 must be available, as QCX relies on it as its database
tool. Please refer to the appropriate section below for further information.
Furthermore, the QCX/BlendDesigner application requires the .NET framework 1.1.
Please refer to the appropriate section below for further information.
Finally, if reporting and trending facilities are required, PlantGuide must also be
installed before QCX (please notice, PlantGuide is a licensed F.L.Smidth -
Automation product). As PlantGuide to a wide extent bases its functions on
Microsoft Excel 2000, Microsoft Office must be installed prior to PlantGuide. For
detailed information about PlantGuide installation and Office 2000, please refer to the
PlantGuide Installation Reference Manual.
Reference Manual QCX NTech Installation QCX Installation • 3

Hardware Requirements
The host system must meet or exceed the following requirements:
Computer Personal Computer must be member of the Microsoft Windows 2000 HW
Compatibility List.
Memory Minimum 256 MB RAM for a professional and 512 MB RAM for a server
Disk Space Minimum 6 GB for a professional and 8 GB for a server.
Display Resolution 1280 x 1024 pixels or better, minimum 32768 colours.
Operating System The following operating system variants are supported:
• Microsoft Windows 2000 (at least SP4): Professional, server, domain
controller
• Microsoft Windows 2003
• Microsoft Windows XP (at least SP 2)
Installation Preparations
Before the QCX installation is started, verify the following:
1. Networked host system must have correct network settings. It is important to
ensure that a networked host has been given a computer name that is unique
within the associated workgroup.
2. Any previous QCX installation has been properly un-installed.
3. If installing the QCX system in a Domain environment, the Domain
Controller must be installed and configured.
Microsoft .NET Framework 1.1

The .NET Framework 1.1 is required for the QCXC/BlendDesigner application. The
.NET Framework 1.1 is included in windows 2003, but not in windows 2000 and XP. It
is royalty free and may be installed from Microsoft's homepage of from a CD obtained
from F.L.Smidth - Automation.
Microsoft SQL Server 2000 Installation

The SQL Server 2000 is installed from a CD purchased for the project and it must be
installed on the QCX server. QCX can run against SQL Server 2000 Professional or
Standard. Hereafter it must be update to SP3.
QCX clients do not in general require database access, but if SQL Server related
facilities (such as the QCX Backup/Restore application) should be accessible from
clients, SQL Server 2000 client tools must be installed on the clients as necessary.
Prerequisites
• CD-ROM with the SQL Server 2000 software
• CD key. Can found on a label at the CD-ROM case.
4 • QCX Installation Reference Manual QCX NTech Installation

SQL Server Installation Procedure on the QCX server
1. Logon as Administrator, insert the SQL Server CD-ROM and wait for
the installation program to auto-start.
2. Select: “SQL Server 2000 Components”, then select “Install Database
Server”, installation method “Local Computer“, “Create a new instance of
SQL Server or install Client Tools”.
3. Enter name and client’s company and accept terms.
4. In the “Installation Definition” dialog select “Server and Client Tools”.
5. In the “Instance Name” dialog select “Default”.
6. In the “Setup Type” dialog select “Typical”.
7. On the menu “Services Accounts” select: “Use same account” and “Use
local system account.
8. In the “Authentication Mode” dialog select “Mixed Authentication”
9. Select "password" as password for the SQL SA account
10. If it was SQL Server 2000 Professional you installed, you are finished
and should restart the computer. If IS WAS SQL Server 2000 Standard,
you need the purchased licenses before you restart. In the “Choose
Licensing Mode” dialog select “Per seat for …” and enter the purchased
number of licenses.

SQL Server Installation Procedure on QCX clients
1. Logon ad Administrator, insert the SQL Server CD-ROM and wait for the
installation program to auto-start.
2. Select: “SQL Server 2000 Components”, then select “Install Database
Server”, installation method: “Install on local computer“, “Create a new
instance of SQL server or install Client Tools”.
3. Enter name and client’s company and accept terms.
4. In the “Installation Definition” dialog select “Client Tools Only”.
5. Accept components selected in the “Select Components” dialog.
6. Restart the computer
QCX Installation Procedure

A QCX system can be installed either from a CD-ROM supplied by F.L.Smidth -
Automation A/S or from a file obtained through the FLSA Dev Support Web. The
installation procedure for either source is provided below.
Please observe that the QCX system is a licensed product. The software cannot execute
in a server configuration without the installation of a hardware dongle and a license
file. These items are supplied by F.L.Smidth - Automation A/S. The license file
can be added either during the installation of the QCX system or after the installation
has completed.
The QCX CD-ROM contains all available QCX modules, but only those modules for
which you have purchased a license will be able to execute on the QCX server.
Therefore only select the relevant modules when you are asked during installation.
Installation from CD-ROM

1. Logon to the host system as FlsaMain.
2. Insert a CD-ROM with the QCX system and wait for the installation program to
auto-start. If the auto-start fails, open the Explorer and display the contents of the
CD-ROM root directory. Double-click the Setup.exe file to start the installation
program.
3. Follow the instructions presented by the installation program. In particular, be
aware of the following topics:
A license is only needed when the system will be configured to run on the
QCX server.
When asked to select sub-systems to install, be careful only to select those
sub-systems for which you have purchased the necessary licenses.
When the View log file option is offered, make a careful examination of the
installation log to identify any errors. (This file will also be available after the
installation in the FlsaDev directory).
Accept the option: Yes, I want to restart my computer now when posted by
the installation program. Upon request, logon as user FlsaMain (password =
password).
When the installation program completes successfully, the QCX system starts up in the
Maintenance mode ready for configuration.

Installation from FLSA Dev Support Web
2. Open an Internet Explorer and connect to the FLSA Dev Support Web:
http://www.flsadev.dk. Find the desired version of the QCX system and follow the
instructions on how to download the corresponding self-extracting exe file. Wait
for the download to complete.
3. When the download has completed the ECS NTech Release Installation window
is displayed automatically, if you had selected Open. If you had selected Save as
you must double click on the file to get the Unzip dialog.
Accept the proposed temporary folder in which the system files will be unzipped
or add a subfolder with the same name as the system to be installed. If the folder
defined already exists, delete its contents. Enable the Overwrite Files Without
Prompting and when Done Unzipping Run: .\setup\setup.exe check boxes.
4. Click on the Unzip button and wait for the unzip operation to complete. When the
completion message is acknowledged the installation program will start
automatically if the When Done Unzipping Run… checkbox is enabled.
Otherwise, the installation program must be started manually by opening the
Explorer and double clicking on the Setup.exe file in the temporary folder.
5. Follow the instructions generated by the installation program. In particular, be
aware of the following topics:
A license is only needed when the system will be configured as a Server.
When the View log file option is offered, make a careful examination of the
installation log to identify any errors. (This file will also be available after the
installation).
Accept the option: Yes, I want to restart my computer now when posted by
the installation program. Upon request, logon as user FlsaMain .
When the installation program completes successfully, the QCX system starts up in the
Maintenance mode ready for configuration.

QCX Un-Install Procedure
This section describes the procedure used to remove an existing QCX installation from
a host system.
Un-Install Procedure
It will be necessary to have Administrator privileges before performing the following
procedure.
1. From the Maintenance utility, restart the computer in maintenance mode. When
the logon prompt appears, log on as FlsaMain.
2. From the Maintenance window, select the Backup tab, enable all data sets listed
and make a backup to the backup folder. Examine the backup log to ensure that the
backup process completed successfully. This action only applies to a server
system.
3. Backup the QCX system SQL Server databases, using the QCX Backup/Restore
application. This action only applies to a server system.
4. From the Explorer, open the …\FLSADev\Bin\Sys folder and double-click on the
PtaReg30.exe file. Type DevUnReg SDR /s=qcx at the PtaReg> prompt and press
the keyboard <Enter> key. This will unregister all QCX components.
5. If you need to un-install ECS/SDR as well, please refer to the ECS/SDR
Installation Reference Manual

User Manual
ECS SQL (Backup and

Restore)
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Last modified $Modtime:: 12/13/05 11:49a $
Author cna-in
Name of Word File $Workfile:: SdrSqlJobsUi30_english.doc $
Disclaimer:

Contents
SQL Job List 1
Introduction ............................................................................................................................... 1
Tool Bar..................................................................................................................................... 2
Host Connection ........................................................................................................................ 2
Job list........................................................................................................................................ 2
Retry policy ................................................................................................................. 4
Media header ............................................................................................................... 4
Backup header ............................................................................................................. 4
Edit physical location for disk devices ........................................................................ 5
Glossary of Terms 7
Index 9
User Manual ECS SQL (Backup and Restore) Contents • iii

SQL Job List
Introduction
The SQL Job List enables users to perform SQL backup and restore operations of the SQL databases. However, the
application may also be used to execute site-specific SQL maintenance jobs.
Furthermore, the SQL Job List provides header information for backup devices.
The description in this document is largely limited to SQL operations for ECS/PlantGuide – QCX/Reports
application or short just PLG. However, any other product using SQL can be included as long the product creates the
relevant databases, provides the relevant Job lists, licensing and UserAccessControl (UAC) rights.
For PLG the Job List might look as shown below:
User Manual ECS SQL (Backup and Restore) SQL Job List • 1
Tool Bar
Start. Starts the currently selected SQL job.
Stop. Stops the currently selected SQL job.
Open File. Opens the current log file associated with the selected SQL job.
Help. Activate the online help tool.
Host Connection
The frame labelled "Host" displays the host name of the connected SQL server and the login user name. If the SQL
job list application is running on a PLG server the host name will equal the server name. Running on an
ECS/PLG/QCX client is currently unsupported.
If SQL connection using trusted connection (windows 2000 login) can be established the login user name will equal
the windows 2000 login name. If not, SQL login will be used, using the SQL FlsaServer login.
Job list
The job list displays the enabled PLG jobs defined for the connected SQL server agent. A PLG job is defined as a
job with a category name containing the sub string "PLG". If a job should be removed from the list it can either be
deleted or disabled using the SQL Server Enterprise Manager. Refer to the Microsoft SQL Server Books Online for
an introduction to the SQL Server Enterprise Manager, the SQL server agent and SQL server agent jobs.
The following columns are displayed for each PLG job:
Name:
The name of the PLG job.
Category:
The category of the PLG job. One of the following:
PLG Disk Backup: The job is used for backup to disk
PLG Tape Backup: The job is used for backup to tape
PLG Disk Restore: The job is used for restore from disk
PLG Tape Restore: The job is used for restore from tape
Status:
The current status of the job. One of:
Idle: The job is not running
Executing: The job is currently being executed by the SQL server agent. The field will also display the number and
name of the current job step being executed
Last:
Date and time of last completed execution.
2 • SQL Job List User Manual ECS SQL (Backup and Restore)
Last status:
The status of the last job execution performed by the SQL server agent. One of:
Unknown: The job was never executed
Failed: An error occurred during the last execution
Succeeded: The last execution of the job completed successfully
Cancelled: The last execution was cancelled
Next:
The date and time of the next automatically scheduled execution. Automatic scheduling is configured using SQL
Server Enterprise Manager/SQL server agent.
The colour of the icon to the left of the PLG job indicates either the current status or the last status of the
corresponding job. If the current status is "Idle" they indicate the status of the last completed execution:
Unknown (grey): The job was never executed
Failed (red): An error occurred during the last execution
Succeeded (green): The last execution of the job completed successfully
Cancelled (yellow): The last execution was cancelled

If the job is currently being executed the following icon will be shown:
Executing (magenta)
The icon will be rotating in order to indicate that the job is currently being executed.
If the job step is currently between retries the following icon will be shown:
Retries (blue)
Retry policy
A PLG SQL job is divided into job steps. E.g.
1. Backup PLG configuration database

2. Verify backup of PLG configuration database
3. Backup PLG sample data database
4. Verify backup of PLG sample data database
During execution the PLG SQL job list will display the job step currently being executed. If a job step fails the SQL
Server agent will retry execution of the given job step. As default job steps for tape backup and restore has been
configured to wait 2 minutes between retries and to attempt retry 3 times. Job steps for disk backup and restore do
not use retry.
Settings regarding retry policy may be modified using SQL Server Enterprise Manager/SQL server agent.
Media header
The media header may be retrieved and displayed by right clicking the desired device in the job list and selecting the
entry Media header.
Backup header
The backup header may be retrieved and displayed by right clicking the desired device in the job list and selecting
the entry Backup header.
The location of the backup file may be modified using the entry field labelled Physical location. The location
consists of a path and file name. Alternatively, the location may be modified using the Open file dialog mapped by
activation of the Browse button.
4 • SQL Job List User Manual ECS SQL (Backup and Restore)
Edit physical location for disk devices
The default location may be modified by right clicking the desired disk device in the job list and selecting the entry
Edit physical location.
The location of the backup file may be modified using the entry field labelled Physical location. The location
consists of a path and file name. Alternatively, the location may be modified using the Open file dialog mapped by
activation of the Browse button.
Glossary of Terms
Backup device
A physical device used for backup and restore. May be a disk file or tape drive etc.
Backup header
Backup information for a backup device.
Host
The computer where the SQL server maintaining the PLG databases is running. The same computer as the PLG
server.
Media header
Header information for a backup device.
PLG database
The SQL PlgData database containing configuartion and sample data.
PLG client
Computer where PLG client applications are running.
PLG server
Computer where the PLG server applications are running.
PLG SQL databases

There is one PLG SQL databases. PlgData which contains configuration data and sample data.
SQL server agent

Agent maintaining and submitting SQL jobs.
SQL Server Enterprise Manager

Main tool for administration of SQL server 2000.
User Manual ECS SQL (Backup and Restore) Glossary of Terms • 7

Index
User Manual ECS SQL (Backup and Restore) Index • 9

Reference Manual
QCX GMS Support

F.L.Smidth A/S - Automation
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version QCXV7 $Revision:: 7 $

Author Dan Mungaard
Last modified by $Author:: Dam $
Name of Word File $Workfile:: QcxGmsIAct30_English.doc $
Index Range 0-1000
Disclaimer:

Contents
QCX GMS Support ....................................................................................3
Introduction................................................................................................................................ 3
GMS operator Functions ..........................................................................5

Introduction................................................................................................................................ 5
Gms Menus ................................................................................................................................ 6
Adding QCX Menus ........................................................................................................... 7
Configuring QCX Menus.................................................................................................... 7
Gms Buttons ............................................................................................................................ 14
Adding QCX Function Buttons ........................................................................................ 14
Configuring QCX Activation Buttons .............................................................................. 14
GMS FSS Servers .....................................................................................1

Dynamic Texts........................................................................................................................... 1
Adding Dynamic Texts....................................................................................................... 2
Configuring Dynamic Texts ............................................................................................... 2
QCX/Autosampling Dynamic Texts................................................................................... 4
QCX/Robolab Dynamic Texts............................................................................................ 6
Glossary of Terms ....................................................................................9
Index ........................................................................................................11
Reference Manual QCX GMS Support Contents • i

QCX GMS Support
Introduction
Three types of access to the QCX system are possible from the OpStation
environment: Activation menus, Activation Buttons and Dynamic texts or data.
Qcx Gms Activation enables user access to chosen QCX functions directly from
the OpStation pictures. QCX Gms Activation consists of 3 parts: A number of
Gms gismos, a language database and a collection of automation classes
providing access to the QCX functionalities.
Access to QCX functions are available either through menus or buttons in the
GMS pictures, the contents of menus can be customised to divide QCX
functionalities into logical groups, e.g. handling all functions regarding a Mill.
Dynamic texts are available for the Auto Sampling system through the QCX
Auto Sampling FSS server.
Fig. 1: OpStation Picture with dynamic texts and menus and menus or buttons
for access to operator functions.
Reference Manual QCX GMS Support Contents • 3

GMS operator Functions
Introduction
The QCX Gms Activation facility provides the user easy access to a number of
the frequently used QCX functionalities, directly from the relevant OpStation
pictures.
The supported functions are:
QCX/Laboratory:
• Trend.
• Report.
• Take sample.
QCX/BlendExpert feeder functions:

• Edit analysis.
• Edit limits.
QCX/BlendExpert mill functions:

• Recalculate setpoints.
• Reset current.
• Reset production.
• Reset product silo.
• Reset all.
• Undo control action.
• Toggle CCA.
• Edit quality targets.
• Control tuning.
• Offline feed.
QCX/BlendExpert silo functions:

• Edit silo contents.

• Reset silo contents
QCX/AutoSampling functions:
• Set sample type average.
• Set sample type spot.
• Set sampler mode Auto.
• Set sampler mode Manual.
• Take sample.
• Abort sample.
• Abort and take sample.
• Set line mode auto.
• Set line mode manual.
• Set station mode Auto.
• Set station mode manual.
• Send carrier in position.
• Sampler configuration.
QCX/Robolab functions:
• Set cell mode automatic or manual.
• Set equipment mode active or passive.
• Reset cell or equipment.
• Reset position
• Move robot to rest position
• Display alarms
• Report
• Trend
These functions can be added to menus or buttons in the OpStation picture as

needed. This manual will give an example of such a setup, which can be used as
a guideline.
Gms Menus
6 • Contents Reference Manual QCX GMS Support

Fig. 2: QCX Gms menu for a mill.
Adding QCX Menus

The QCX functions are added to the Gms picture through a Gismo. The Gismo is
added to the GMS picture in the GMS editor by choosing Palette in the toolbar
and selecting Get Submodel. A list of available submodels will appear, choose
extactmenuQCX and press OK.
The cursor will now appear as the outline of the menu icon and can be added to
the Gms picture by clicking the left mouse button, when the desired menus are
added, click the right mouse button and select Done from the appearing menu.
To delete excess menu icons, mark the icon by clicking left mouse button and
press delete.
Configuring QCX Menus

The QCX menus are configured in two steps. First, text and automation class is
given in the QcxGms.mdb found under the ../NlsDB/ directory, secondly the
individual menu is set-up in the GMS editor.
Database configuration
The QcxGms.mdb by default contains four tables: Mill, Silo, Feeder and
Sampler. These tables define the connection between a text entry in a QCX menu
and an activation class. Each record in a table will result in an entry in menus
built on this table.
If alternative menu configurations are needed, e.g. to allow access to more than
one trend package from a specific menu, an extra table should be made on the
basis of one of the existing tables.
The text fields can be changed by the commissioning engineer as found fit, the
ProgID field, however, has to be configured as seen in table 1 2 and 3. The text
field for e.g. the Trend package could be changed to the Trend package name.
Using these ProgIDs, it is thus possible to customise the QCX menus e.g. by
adding access to more than one trend package from a sampler. The steps needed
would be:
• Copy the "Sampler" table in the QcxGms.mdb giving it a new name.

• Copy the trend record in the desired number and change the text to make it
distinct (e.g. use the desired trend package names).
• Configure the GMS Menu. (See next section)

Table 1
QCX/Laboratory Automation ProgID Function
QcxSmpActLstUI30.clsActSmpPnt Takes (logs in) a sample in a
given sample point.
PlgRepUI30.clsReportActivate Invokes a specified report
package.
PlgTrendUI30.clsTrendActivate Invokes a specified trend
package.
Table 2
QCX/BlendExpert Automation ProgID Function
QcxBlxExtAct30.clsActRecalcSetPts Activates the Recalculate
set-points function.
QcxBlxExtAct30.clsActResetCurrent Activates the Reset current
function.
QcxBlxExtAct30.clsActResetProd Activates the Reset
production function.
QcxBlxExtAct30.clsActResetSilo Activates the Reset product
silo function.
QcxBlxExtAct30.clsActResetAll Activates the Reset all
function.
QcxBlxExtAct30.clsActRestore Activates the Undo control
action function.
QcxBlxExtAct30.clsActCCAtoggle Toggles CCA
QcxBlxExtAct30.clsActEditSetPts Activates the Edit quality
targets function.
QcxBlxExtAct30.clsActCtrlTunning Activates the Control tuning
function.
QcxBlxExtAct30.clsActOffLineFeed Activates the OffLine feed
dialog
QcxBlxExtAct30.clsActEditAnalysis Activates the Edit Analysis
function for a feeder.
QcxBlxExtAct30.clsActEditLimits Activates the Edit limits
function for a feeder.
QcxBlxExtAct30.clsActResetInv Activates the Reset silo
contents function.
QcxBlxExtAct30.clsActEditInv Activates the Edit silo
contents function.
Table 3
QCX/AutoSampling Automation ProgID Function
QcxAusExtAct30.clsActSampleType Toggles the Sample Type
between average and spot
QcxAusExtAct30.clsActSamplerMode Toggles the sampler mode
(automatic take On/Off)
QcxAusExtAct30.clsActTakeSample Initiates a take sample
QcxAusExtAct30.clsActAbortSample Aborts a take sample

QcxAusExtAct30.clsActAbortAndTake Empties the mixer and asks
for a new sample
QcxAusExtAct30.clsActLineMode Toggles line mode
(automatic On/Off)
QcxAusExtAct30.clsActStationMode Toggles Plant station mode
(Automatic On/Off)
QcxAusExtAct30.clsActSendCarrier Ships a carrier from a
sending station.
QcxAusExtAct30.clsActOptionsConfig Displays the Sampler
configuration dialog
Table 4
QCX/Robolab Automation ProgID Function
QcxRobExtAct30.clsActCellMode Sets the cell mode to
automatic or manual
QcxRobExtAct30.clsActRobReset Resets the cell or resets an
equipment
QcxRobExtAct30.clsActRobResetPos Resets a specific position on
a specific equipment
QcxRobExtAct30.clsActRobRest Moves robot to the rest
position
QcxRobOperatorUi30.clsActOperator Invokes the robolab
operator UI
QcxRobOperatorUi30.clsActOprSamples Invokes the robolab
operator samples UI
QcxRobOperatorUi30.clsActAlarms Invokes the alarmlist in the
robolab department
QcxRobOperatorUi30.clsActRobHelp Invoke robolab online help

Gms configuration
The data base configuration gives a template to use in the GMS picture. The
customisation to fit the single unit, however, is done in the GMS editor.
To set up a QCX menu select the menu icon by left clicking the mouse, then
right click the icon and select Rename Variables in the appearing menu. The
following dialog will appear:
Fig. 4: Gms Menu Configuration.

The Database field must be set to "QcxGms", this is the name of the database
configured as described in the previous section.
The Menu Table should be set to the database table containing the desired
records for the menu (see previous section).
P01-P15 are the parameters sent to the connected automation class, if the space
is left blank the DefaultParam is used instead.
The example in Fig. 4 shows a typical silo configuration. The two
QCX/BlendExpert menu points, Reset silo contents and Edit silo contents, both
need a parameter on the form: "[Silo configuration]|[Silo Name]". This
parameter is thus put as DefaultParam.
P03 is the Report entry and it needs a parameter on the form: "[Report package
name]"
P04 is the Trend package and needs a parameter on the form: "[Trend package
name]"
For a full overview of parameters, refer to Table 5. Wrong parameters will result
in error messages like:

Followed by:
Note: Parameters have to be exactly equal to the labels used in

QCX/BlendExpert, including spaces!
Table 5
QCX/Laboratory Automation ProgID Parameter
QcxGmsIAct10.clsActSmpPnt "[Sample point name]"
QcxGmsIAct10.clsActReport "[Report package name]"
QcxGmsIAct10.clsActTrend "[Trend package name]"
QCX/BlendExpert Mill Functions Parameter
QcxBlxProductionUI30.clsActRecalcSetPts "[Line name]"
QcxBlxProductionUI30.clsActResetCurrent do.
QcxBlxProductionUI30.clsActResetProd do.
QcxBlxProductionUI30.clsActResetSilo do.
QcxBlxProductionUI30.clsActResetAll do.
QcxBlxProductionUI30.clsActRestore do.
QcxBlxProductionUI30.clsActCCAtoggle do.
QcxBlxProductionUI30.clsActEditSetPts do.
QcxBlxProductionUI30.clsActCtrlTunning do.
QcxBlxProductionUI30.clsActOffLineFeed "[Line configuration] | [Line
name]"
QCX/BlendExpert Feeder Functions Parameter
QcxBlxProductionUI30.clsActEditAnalysis "[Line configuration] | [Feeder
name]"
QcxBlxProductionUI30.clsActEditLimits do.
QCX/BlendExpert Silo Functions Parameter

QcxBlxProductionUI30.clsActResetInv "[Silo configuration] | [Silo
name]"
QcxBlxProductionUI30.clsActEditInv do.
QCX/AutoSampling Functions Parameter
QcxAusOpsSvr30.clsActSampleType "[Sampler Name] | [Sampler
Type]"
QcxAusOpsSvr30.clsActSamplerMode "[Sampler Name] | [Sampler
Mode]"
QcxAusOpsSvr30.clsActTakeSample "[Sampler Name] | [Sampler
Type]"
QcxAusOpsSvr30.clsActAbortSample "[Sampler Name] | [Sampler
Type]"
QcxAusOpsSvr30.clsActAbortAndTake "[Sampler Name] | [Sampler
Type]"
QcxAusOpsSvr30.clsActLineMode "[Line Name] | [Line Mode]"
QcxAusOpsSvr30.clsActStationMode "[Station Name] | [Station
Mode]"
QcxAusOpsSvr30.clsActSendCarrier "[Station Name] | [Position]"
QcxAusUI30.clsActOptionsConfig [Sampler Name]
QCX/Robolab Functions Parameter
QcxRobExtAct30.clsActCellMode "[Cell Name]"
Table: RobCell
QcxRobExtAct30.clsActRobReset "Cell|[Cell Name]" or
Table: RobEquipment "Eqp|[Equipment Name]"
QcxRobExtAct30.clsActRobResetPos "[Equipment Name]|[Position
Type]|[Position Number]"
Table: RobPosition
or
"[Equipment Name]|[Position
Name]"
QcxAusOpsSvr30.clsActRobRest Example:
Table: Robot "Robot_1|Move|Robot|RESTP
OS|Robot|RESTPOS|NONE"

Gms Buttons
Fig.7: GMS Buttons.
Adding QCX Function Buttons

The QCX functions are added to buttons in the Gms picture through a Gismo.
The Gismo is added to the GMS picture in the GMS editor by choosing Palette
in the toolbar and selecting Get Submodel. A list of available submodels will
appear, choose extActivate and press OK.
The cursor will now appear as the outline of the button icon and can be added to
the Gms picture by clicking the left mouse button, when the desired buttons are
added, click the right mouse button and select Done from the appearing menu.
To delete excess button icons, mark the icon by clicking left mouse button and
press delete.
Configuring QCX Activation Buttons

The QCX activation buttons are configured in two steps. First, the automation
class is given in the QcxGms.mdb found under the ../NlsDB/ directory, secondly
the individual button is set-up in the GMS editor.
Database configuration
The QcxGms.mdb by default contains six tables: Mill, Silo, Feeder Sampler,
Plant station and Line. These tables define the connection between a text entry in
a QCX menu or a QCX activation button and an activation class. Each record in
a table will result in an entry in menus built on this table or can be used by a
button.
The important information in the database tables when configuring a button is
the progID and the index. The text fields are not used for buttons but are
reserved activation menus.
GMS configuration
The data base configuration gives a template to use in the GMS picture. The
customisation to fit the single button, however, is done in the GMS editor.

To set up a QCX activation button select the button icon by left clicking the
mouse, then right click the icon and select Rename Variables in the appearing
menu. The following dialog will appear:
Fig. 9: Gms Activation Button Configuration.
The Menu Table should be set to the database table containing the desired
record for the button (see previous section).
Button Text defines the text seen on the button in the GMS picture.
Button Text Colour defines the text colour seen on the button in the GMS e.g. 7
is black.
Button Text Font defines the Font used for the button text in the GMS picture.
Confirm Specifies whether or not the user should be asked to confirm an action
before it is processed. If set to one, a dialog like fig. 10 will be shown every time
the button is pressed. 0 is recommended.
Fig. 10: Confirm dialog
The Database field must be set to "QcxGms", this is the name of the database
configured as described in the previous section.

extent_height defines the size of the button.
extent_width defines the size of the button.
MenuItemNo defined which table item to access from the button.
MenuTable defined which table in the database the function is defined in.
Parameter In the parameter field, the key for the selected function should be
given in quotes.
The example in Fig. 9 shows a typical button configuration.
For a full overview of parameters, refer to Table 4. Wrong parameters will result
in error messages like:
In some cases followed by:
Note: Labels used as Parameters have to be exactly equal to the labels used in
QCX systems, including spaces!

GMS FSS Servers
Dynamic Texts
Fig. 13: Dynamic Texts.

To be able to provide dynamic texts and values in the GMS pictures, a FSS server will
be added for each QCX application, which supplies important information. in version
7.0.2 or later.
FSS Server Setup

To be able to use dynamic texts in the GMS pictures, the relevant FSS servers have to
be configured in the ECS OpStation Configuration tool found in the start menu under
ECS ->Sdr Administration Tools.
To configure the QCX/AutoSampling FSS server available with QCX version 7.0.2 or
later:
1. Click the "External servers" tab
2. Click "Add"
3. From the dropdown box select "QcxAusOpsSvr30"
4. Give a Server ID, e.g. Aus.
5. If on a DOP, give the MOP name as Host name.
6. Click "OK"
To configure the QCX/Robolab FSS server available with QCX version 7.0.2or later:
1. Click the "External servers" tab
Reference Manual QCX GMS Support GMS FSS Servers • 1

2. Click "Add"
3. From the dropdown box select "QcxRobOpsSvr30"
4. Give a Server ID, e.g. Rob.
5. If on a DOP, give the MOP name as Host name.
6. Click "OK"
This should be done on all computers, where the dynamic texts are added to the GMS
pictures.
The Server name is the ID used to configure the text boxes in the GMS picture (see the
following section).
Adding Dynamic Texts

The Dynamic texts are added to the Gms picture through a Gismo. The Gismo is
added to the GMS picture in the GMS editor by choosing Palette in the toolbar and
selecting Get Submodel. A list of available submodels will appear, choose exttext and
press OK.
The cursor will now appear as the outline of the text box and can be added to the Gms
picture by clicking the left mouse button, when the desired texts are added, click the
right mouse button and select Done from the appearing menu.
To delete excess texts, mark the icon by clicking left mouse button and press delete.
Configuring Dynamic Texts

Each FSS server offers a fixed number of dynamic texts, these are given by the
underlying QCX subsystem. The currently available Texts for the QCX Autosampling
FFS server can be found in table 6.
To set up a dynamic text box, select the text box icon by left clicking the mouse, then
right click the icon and select Rename Variables in the appearing menu. The
following dialog will appear:
2 • GMS FSS Servers Reference Manual QCX GMS Support

Fig. 15: Gms Dynamic Text Configuration.
The Align X decides the text alignment in the textbox.

DataKey is the text parameter sent to the FSS server, see table 5 and 6 for possible
keys
Edge, Fill and text Color, together with Font define the look of the text box
ServerID is the name given to the FSS server in the ECS OpStation Configuration
dialog.

QCX/Autosampling Dynamic Texts
The QCX Autosampling FSS sever provides the following texts
Table 6
Plant Station Key
Message "PlantStation|Message|[Station Name]"
Last Sample "PlantStation|LastSample|[Station Name]"
Last Group Name. "PlantStation|LastGroupName|[Station Name]"
Last Sample Time. "PlantStation|LastSampleTime|[Station Name]"
Mode Aut/Man. "PlantStation|ModeAut|[Station Name]"
Mode On/Off. "PlantStation|ModeOn|[Station Name]"
ErrorState01 "PlantStation|ErrorState01|[Station Name]"
… …
Sequence "PlantStation|Sequence|[Station Name]"
Status "PlantStation|Status|[Station Name]"
Sampler Key
Message. "SamplerEqp|Message|[Sampler Name]"
Last Sample. "SamplerEqp|LastSample|[Sampler Name]"
Last Group Name. "SamplerEqp|LastGroupName|[Sampler Name]"
Last Sample Time. "SamplerEqp|LastSampleTime|[Sampler Name]"
Next Sample Time. "SamplerEqp|NextSampleTime|[Sampler Name]"
Mode Aut/Man. "SamplerEqp|ModeAut|[Sampler Name]"
Mode On/Off. "SamplerEqp|ModeOn|[Sampler Name]"
Sample Type. "SamplerEqp|SampleType|[Sampler Name]"
Point Key
ErrorState01 "Point|ErrorState01|[Point Name]"
… …
Position Key
Last Sample. "SamplerPos|LastSample|[Position Name]"
Last Group Name. "SamplerPos|LastGroupName|[Position Name]"
Last Sample Time. "SamplerPos|LastSampleTime|[Position Name]"
Next Sample Time. "SamplerPos|NextSampleTime|[Position Name]"
Target Key
Last Group Name. "Target|LastGroupName|[Target Name]"
Last Group Text. "Target|LastGroupText|[Target Name]"

Last Sample. "Target|LastSample|[Target Name]"
Last Sample Time. "Target|LastSampleTime|[Target Name]"
Line Key
Mode Aut./Man. "Line|ModeAut|[Line Name]"
Mode On/Off. "Line|ModeOn|[Line Name]"
Text Key
Next Text. "Text|NextText|[Equipment Name]"
Last Text. "Text|LastText|[Equipment Name]"
Next Sample Text. "Text|NextSampleText|[Equipment Name]"
Last Sample Text. "Text|LastSampleText|[Equipment Name]"
Average Text. "Text|AverageText|[Equipment Name]"
Spot Text. "Text|SpotText|[Equipment Name]"

QCX/Robolab Dynamic Texts
The QCX Robolab FSS server provides the following texts
Table 7
Equipment Key
SWMode Aut/Man "Eqp|[Equipment Name]|SWModeAut"
SWMode On/Off "Eqp|[Equipment Name]|SWModeOn"
HWMode Aut/Man "Eqp|[Equipment Name]|HWModeAut"
HWMode On/Off "Eqp|[Equipment Name]|HWModeOn"
SWMode "Eqp|[Equipment Name]|SWModeActive"
Active/Passive
Sample Group "Eqp|[Equipment Name]|Input|SampleGroup"
Equipment Text Key
Text by Key "Eqp|[Equipment Name]|Text|[Key]|"
Text by index "Eqp|[Equipment Name]|Text|[Type]|[Index]|"
Equipment Input #1 Key
Position
[Item] "Pos|[Equipment Name]|Input|1|[Item]"
Equipment Output Key
#1 Position
[Item] "Pos|[Equipment Name]|Output|1|[Item]"
Equipment Internal Key
#1 Position
[Item] "Pos|[Equipment Name]|Internal|1|[Item]"
Equipment Any #1 Key
Position
[Item] "Pos|[Equipment Name]|AnyType|1|[Item]"
Cell Key
Mode Aut/Man. "Cell|[Cell Name]|ModeAut"
Mode On/Off. "Cell|[Cell Name]|ModeOn"
[Item] may be any of:
SampleKey
SampleGroup
SubSampleName
Function
Program
ContainerType
ContainerId
PositionType
Status
ContainerPresent
SupplyContainer
RemoveConatiner

ContainerReturnOk
ContainerClean
DoAllocOk
DoDeallocOk
Flags
(Flags returns a string of '0' and '1's:
ContainerPresent
SupplyContainer
RemoveContainer
ContainerReturnOk
ContainerClean
DoAllocOk
DoDeallocOk
Examples
Getting Cell status

Getting position status

Glossary of Terms
Language database
Database containing translations of all texts available in the QCX system.
OpStation
Operator Station, the graphical user interface to the plant.
Gismo
GMS component allowing user interaction through a graphical element.
GMS
Graphical Modelling System, used for e.g. OpStation pictures.
Reference Manual QCX GMS Support Glossary of Terms • 9

Index
Reference Manual QCX GMS Support Index • 11

Reference Manual
QCX Service
Import from the QCX v7

output tray
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Author HeWA
Last modified by $Author:: Kamal $
Name of Word File $Workfile:: QcxSdbS30_ImpOutTrayV7_English.doc $
Index Range 0-1000
Disclaimer:

Contents
Introduction...............................................................................................1
QCX service for import from the QCX v7 output tray .............................................................. 1
QCX v6.5 sr7 publisher ...................................................................................................... 2
Import from the QCX V7 output tray Service Installation ......................1

Service installation..................................................................................................................... 1
Import from the QCX V7 output tray Service Configuration .................3

Service configuration properties ................................................................................................ 3
Output tray server ............................................................................................................... 3
Output tray database ........................................................................................................... 3
Output tray user .................................................................................................................. 3
Output tray password.......................................................................................................... 3
Connection timeout............................................................................................................. 3
Command timeout .............................................................................................................. 3
Import directory .................................................................................................................. 4
Validate using schema ........................................................................................................ 4
Validation schema .............................................................................................................. 4
Maximum number of samples loaded................................................................................. 4
Maximum number of samples in XML files....................................................................... 4
Priority ................................................................................................................................ 4
Sleep between load of samples ........................................................................................... 4
Sleep between write of XML files ...................................................................................... 4
Import from the QCX V7 output tray Service Status ..............................4

Service status properties ............................................................................................................ 5
First sample......................................................................................................................... 5
Last sample ......................................................................................................................... 5
Last XML file ..................................................................................................................... 5
Number of samples ............................................................................................................. 5
Number of XML files ......................................................................................................... 5
Import from the QCX v7 output tray Communication ............................5

Connection ................................................................................................................................. 5
Reference Manual QCX Service Contents • i

Introduction
QCX service for import from the QCX v7 output tray

This manual provides information on how to import sample data from a QCX v7
output tray to a QCX v7 sample database.
Publisher:
QCX v6.5 sr7
KP300151
Suscriber:
QCX v7.0 sr2
Publisher:
QCX v7.0 sr1
KP301054
Publisher:
QCX v7.0 sr2
The import service is running on the subscribing QCX system, e.g. the PlantGuide
server. The service generates XML files which are stored in the import directory of the
subscribing QCX system. At present only the XML syntax defined in the XML schema
Reference Manual QCX Service Introduction • 1

FlsaDev\ProDb\QcxSampleData30.xsd is supported. Note that import requires QCX
v7.0 sr2 of the subscribing system.
Import is supported from the following versions of the publishing QCX system.
QCX v6.5 sr7 publisher

This is the only v6 version supported. Requires hot fix KP300151. This hot fix installs
the QCX v7 output tray database PlgExport.

Requires hot fix KP301054.

No hot fixes required.
2 • Introduction Reference Manual QCX Service

Import from the QCX V7 output
tray Service Installation
Service installation
To install the service, insert the QCX component CD into the computer’s CD ROM
driver and wait for the installation script to auto-start, then select the Import from QCX
v7 output tray service from the list.
The service installs one answer file in the ProDb directory:
C:\Flsadev\ProDb\QcxSdbS30Answer_ImpOutTrayV7.mdb
Reference Manual QCX Service Service installation • 1

tray Service Configuration
Service configuration properties

The following properties are available for configuration:
Output tray server

The name of SQL server instance running on the publishing QCX system.
Output tray database

The name of the output tray database on the publishing QCX system. If the publisher
is a QCX v6.5. sr7 system the database must be PlgExport. If the publisher is a QCX
v7.0 system the database name is configured on the publisher.
Output tray user

If blank, trusted connection to the publisher is applied (recommended). This requires
that the FlsaServer account exists on the publisher and that the FlsaServer password
is identical on the publisher and the subscriber. If non blank, connection is attempted
using SQL security with the given user.
Output tray password

Only used for connection using SQL security (non blank output tray user). The
password of the given SQL user account on the publishing QCX system.
Connection timeout
Connection timeout in seconds.
Command timeout
Command timeout in seconds.
Reference Manual QCX Service Import from the QCX V7 output tray Service Configuration• 3
Import directory
If blank, the default import directory is applied, i.e. FlsaQcxLog/SampleDataImport.
If non blank, the generated XML files will be stored in the given directory. Note that
a full path must be specified.
Validate using schema

If 1 the generated XML is validate against the schema specified in Validation
schema. If 0 the generated XML is not validated against an XML schema.
Validation schema
Only relevant if Validate using schema is 1. If blank, the standard schema
FlsaDev\ProDb\QcxSampleData30.xsd is used for validation. If non blank, the
generated XML will be validated using the specified schema. Note that a full path
must be specified.
Maximum number of samples loaded

The maximum number of samples loaded in one chunk from the output tray.
Maximum number of samples in XML files

The maximum number of samples stored in one XML file.
Priority
0 is normal priority. –1 is one below normal and –2 is two below normal. Used to
force import to run with low priority in order to obtain faster response for interactive
applications.
Sleep between load of samples

Milli seconds to wait between load of chunk of samples.
Sleep between write of XML files

Milli seconds to wait between write of individual XML files.

tray Service Status
4 • Import from the QCX V7 output tray Service Status Reference Manual QCX Service
Service status properties
The following properties are available as status information for each execution of the
service:
First sample
The first sample loaded from the output tray.
Last sample
The last sample loaded from the output tray.
Last XML file

The file name of the last XML file generated.
Number of samples
Number of samples imported from the output tray.
Number of XML files

Number of XML files generated.
Import from the QCX v7 output

tray Communication
Connection
An ADO connection is made to the SQL output tray database of the publishing QCX
system. The connection may use either trusted connection or SQL security. For a
QCX v6.5 sr7 system the connection is made to MS SQL server 7.0. For a QCX v7
system the connection is made to MS SQL server 2000.
Reference Manual QCX Service Import from the QCX v7 output tray Communication• 5
Reference Manual QCX Service Import from the QCX v7 output tray Communication • 7
Reference Manual
QCX Driver
General Description
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Last modified $Modtime:: 12-04-05 14:22 $
Author Jan Thode
Last modified by $Author:: Jat $
Name of Word File $Workfile:: QcxDrv30_General_English.doc $
Disclaimer:

Contents
QCX Driver General Description 1
Introduction ............................................................................................................................... 1
Equipment Tools Utility 1

Introduction ............................................................................................................................... 1
Main Menu ................................................................................................................................ 1
Equipment Control Tab ............................................................................................................. 2
Equipment Installation Tab........................................................................................................ 4
Equipment Data Edit Tab .......................................................................................................... 6
Equipment Information Tab....................................................................................................... 7
Equipment Status Tab................................................................................................................ 8
Equipment Status Signalling ....................................................................................... 9
Position Status Signalling............................................................................................ 9
Function/Input-position Status Signalling ................................................................. 10
Request Status Signalling .......................................................................................... 11
Text............................................................................................................................ 11
Equipment Database Definitions 12

Introduction ............................................................................................................................. 12
System Table ........................................................................................................................... 12
Communication Table ............................................................................................................. 12
Driver Specific Table............................................................................................................... 12
Error Translation Table............................................................................................................ 12
Item Name Translation Table .................................................................................................. 13
Enclosures 14
Alarms & Events...................................................................................................................... 14
QCX Driver Alarms & Events................................................................................... 14
QCX Driver Communication Alarms & Events ........................................................ 20
QCX Subsystem Error Codes .................................................................................................. 23
Index 29
Reference Manual QCX Driver Contents • iii

QCX Driver General Description
Introduction
This manual provides information about equipment related subjects, not covered by the general QCX configuration
manuals.
Equipment Tools Utility
Introduction
The QCX Equipment Tools UI is used for different engineering task related to equipment drivers. The Equipment
Tools UI is only available on the MOP computer, an only in one incarnation.
Main Menu
The QCX Equipment Tool UI is accessed from the start menu:
Start Menu -> QCX -> QCX Engineering Tools -> Equipment Tools.
Reference Manual QCX Driver QCX Driver General Description • 1

General Help
Provides online access to this current manual.
Active Equipment
The icon, name and text for the equipment currently selected to be the active equipment, followed by the current
equipment status (Up or Down). For most equipment drivers, from a user point of view, there is no difference
between the use of the words driver and equipment.
All commands, apart from the installation related commands, works only on the active equipment. The active
equipment is selected from the equipment control tab.
Equipment Help
Provides online help on equipment hardware, software and configuration for the active equipment.
Equipment Control Tab
2 • Equipment Tools Utility Reference Manual QCX Driver

Equipment List
A list of the existing equipment including the current state of the equipment (Up or Down). Only if the equipment
have the status up, the equipment will be available for executing equipment functions upon request of the QCX
Equipment Administration system.
Equipment Control
Used to start and stop the driver executable e.g. if any data in the equipment driver access database has been
changed. In this case the driver has to be stopped and started again for the changes to take effect as the driver only
reads data from the access database at start-up time.
Start
Starts the driver executable.
Stop
Stops the driver executable. The executable can only be stopped, if there is no requests being processed by the
corresponding driver/equipment.
Reset
Resets all pending or ongoing requests for the driver/equipment. The reset is made both in the QCX Equipment
Administration system and in the driver/equipment.
Reference Manual QCX Driver Equipment Tools Utility • 3

Reset Positions
The Reset Positions button brings up the Reset Positions dialog used to issue reset position commands to a
driver/equipment for all selected input/output/general position. Each selected position triggers a reset position
command to the driver/equipment.
Equipment Installation Tab

Online equipment can only be added to or removed from the QCX system by installation and uninstallation. The
installation procedure includes 2 step. In step one the driver executable and the driver access databases are copied
from a CD to the target QCX system. In step two the equipment is incorporated into the QCX Equipment
Administration system.

Install
Conducts a phase 2 installation on al drivers copied from CD, but not yet incorporated into the QCX Equipment
Administration system. Using this option there is no need to restart the QCX system after installation, only to start
the driver/equipment from the equipment control tab. Alarm Group is the alarm group for the QCX Equipment
Administration system, not the individual equipment drivers.
Create
An additional incarnation of an equipment of the selected driver type is added to the QCX Equipment
Administration system.
Some drivers/equipment allows the operator to configure the number of equipment positions in which case the
Position Configuration fields will be visible.

Uninstall
The selected equipment is removed/uninstalled from the QCX Equipment Administration system.
Equipment Data Edit Tab

All persistent data that an equipment driver uses are stored in an access database. The majority of the tables are not
intended to be modified, but some of them contain data accessible for the user.
Please notice that for any database changes to take effect, the driver executable has to be stopped and then restarted.
Database Tables
Shows a list of accessible database tables.
Database Records
Shows a list of records in the database table currently selected. The table may contain more records, but only the
ones accessible are listed.
Record Data
Show details about the current record field as: Data type, text, description, min/max value and unit.

If the record contains more than one editable field, two buttons with the labels “<<” and “>>” will appear, to be used
for moving between fields inside one record.
Add record
Fore some tables it is legal to add new records. In these cases the Add button will appear.
Delete record
Fore some tables it is legal to delete records. In these cases the Delete button will appear.
Apply record
Used to apply changes to record field data. Pleas notice that the apply works only on the currently displayed record
field.
Equipment Information Tab

Some drivers return information as e.g. run statistics or equipment status information to the QCX Equipment
Administration system. If the currently active equipment returns any data, it will be displayed in the four information
list columns.

Clear
Clears all columns.
Aux. Log
Depending on the selected driver, additional logging information may be avaliable. E.g. PLC block communication
data, serial/net communication log and active/old alarm and warning information.
Equipment Status Tab
Drivers notify process management about their state and request services through status signalling. Three levels of
status signalling are possible, respectively Equipment, Position, Function/Input-position and Request status
signalling.

Equipment Status Signalling
Equipment status signalling is used to inform the process management about the general health and state of the
equipment.
The following equipment status signals are available:
Status: Equipment status, one of :
0 - Unknown
1 - Ready
3 – Busy
4 – Not allocated
5 - Software error
6 - Hardware error
7 - Intermediate
HWAuto: Equipment hardware automatic mode, one of:
Yes
No
STSStatus: Equipment status code:

Bit 0 - Ready
Bit 1 – Operation
Bit 2 – Fault
Bit 4 – Auto
Bit 7 - Local
Position Status Signalling

Position status signalling is used to notify the process management about the state and occupancy of the individual
position.
The following position status signals are available:
Status: Position status, indicates the state and health of the position. One of:

0 - Unknown
1 - Ready
3 – Busy
4 – Not allocated
5 - Software error
6 - Hardware error
7 - Intermediate
ContainerPresent: Indicates if a container is present at the position or not. One of:
Yes
No
SupplyContainer: Indicates that the driver needs process management to supply an empty container to the position.
One of:
Yes
No
RemoveContainer: Indicates that process management should remove a container from the position. One of:
Yes
No
ContainerReturnOk: OK to return container after removal, indicates to process management that it may return the
container to the position when is for some reason has been temporarily removed. One of:
Yes
No
ContainerClean: Position requires clean container, indicates to process management that the container should be
clean before being put in the position. One of:
Yes
No
ContainerType: Indicates the type of container currently being supplied to, present at or removed from the position.
ContainerKey: Indicates the container key currently being supplied to, present at or removed from the position.
ContainerId: Indicates the id of container currently being supplied to, present at or removed from the position.
SampleKey: Indicates the sample key of the sample being present at the position. A sample is always associated
with a container.
SampleGroup: Indicates the sample group of the sample being present at the position. A sample is always
associated with a container.
SubSampleId: Indicates the sub sample id of the sample being present at the position.
Function/Input-position Status Signalling

Function/Input-position status signalling is used by the driver to inform process management about its willingness to
execute some function, using a certain input position.
The following function/position status signals are available:
Status: Function-position status, indicates the state of the function in question at the position. One of:
0 - Unknown
1 - Ready
3 – Busy
4 – Not allocated
5 - Software error
6 - Hardware error
7 - Intermediate
AllocOk: Function-position allocation OK, indicates if it is OK to allocate the function at the position or not. One
of:
Yes
No

DeAllocOk: Function-position de-allocation OK, indicates if it is OK to de-allocate a previously allocated function
at a position. One of:
Yes
No
ContainerType: Indicates the legal container type for the function-position.
ContainerSink: Function-position container sink: indicates if the input position is a container sink when the
function is executed, i.e. whether the container follows the sample into the equipment during execution or not. One
of:
Yes
No
Request Status Signalling

Request status signalling is used by the driver to inform process management about its willingness to execute some
function on currently active requests, e.g. when to execute an allocated equipment function.
The following request status signals are available:
Status: Function-position status, indicates the state of the function in question at the position. One of:
0 - Unknown
1 - Ready
3 – Busy
4 – Not allocated
5 - Software error
6 - Hardware error
7 – Intermediate
DeAllocOk: Request de-allocation OK, indicates if it is OK to de-allocate a previously allocated function at a
position. One of:
Yes
No
SampleKey: Indicates the sample key of the sample being present at the position. A sample is always associated
with a container.
SampleGroup: Indicates the sample group of the sample being present at the position. A sample is always
associated with a container.
SubSampleId: Indicates the sub sample id of the sample being present at the position.
Function: The equipment function of the request.
Position: The equipment position of the request.
Text
Equipment driver specific.

Equipment Database Definitions
Introduction
All persistent data that an equipment driver uses are stored in an access database. This database consists of more than
twenty data tables. Some are only used at installation time and others are irrelevant for the user. This chapter holds a
short description of the five most important data tables, seen from a user point of view.
Generally the description of the different records and their data fields found in the QCX Equipment Tools UI, Data
Edit tab will be sufficient. Consequently, only the records/data fields that needs further explanation are described in
the following sections.
System Table
The system table holds general data common to all equipment drivers:
Global, , AlarmGroup: Alarm group used for alarms/events issued from the driver.
Driver, , LogMask: If set > 0 then logging of driver events will be active. Please notice that it is fully up to the
equipment driver to decide what to log, and that some drivers do not log any events at all. The logging can be viewed
in the ECS alarm lists.
Communication, , LogMask: If set > 0 then logging of equipment driver communication will be active. The
logging can be viewed in the ECS alarm lists. Messages send by the equipment driver are marked with: “Equipment
Name” >> followed by the actual communication message, and messages received by the equipment driver are
marked with: “Equipment Name” << followed by the actual communication message
Communication Table
The communication table holds all configuration regarding driver communication.
Driver Specific Table

The driver specific table holds, as the name implies, driver specific data. Please refer to the relevant QCX driver
documentation, e.g. accessed from the QCX Equipment Tools UI main menu, for a description of the records in the
driver specific table.
Error Translation Table

The error translation table is primarily used for two purposes:
• Error/Warning discrimination: Configuration of if a certain error message should be considered as a warning to
ignore or as an error.
• Error text translation: Translation of less meaningful error messages, into more informative text.
12 • Equipment Database Definitions Reference Manual QCX Driver

Please notice that it is fully up to the driver to decide if/when/how to apply error translation. For most drivers any
message out of sequence, will be tested by use of the error translation table, and if the message is found just to be a
warning, it will be logged in the ESC alarm system (In some cases with a more meaningful text), and the driver will
continue its cycle uninterrupted.
The records in the error translation records contains the fields:
InText1: Search text # 1. Messages received from the physical equipment are search for a match with the text found
in InText1. If InPosition1 is > 0 the text must start at exactly this position in the received message text.
InLength1 defines the length of the search text in InText1.
InPosition1: See above.
InLength1: See above.
InText2: Optional search text # 2. If search text #1 was found, the messages received from the physical equipment
are further search for a match with the text specified in InText2. If InPosition2 is > 0 the text must start at exactly
this position in the received message text else the search is conducted from where search text #1 was found, and up
to the end of the message text. InLength2 defines the length of the search text in InText2.
InPosition2: See above.
InLength2: See above.
ErrorCode: User definable error code to associate with the message. Normally a value of 0 (zero) indicates a
warning and all other values an error.
OutText: An optional text describing the message.
AlarmParamIn: This parameter decides if/how the received message should be logged in the ESC alarm system:
• 0 – No logging
• 1 – Log as information if ErrorCode = 0, else log as an alarm.
• 2 – Log as information.
• 3 – Log as an alarm.
Please notice that the equipment driver can overrule this value.
AlarmParamOut: As for AlarmParamIn, but the text used for logging, will be the one defined in OutText.
Item Name Translation Table

The item name translation table is the basis of a data item name translation, in cases where the data item names used
in the equipment driver, do not match the ones used by the rest of the QCX system as e.g. the QCX Equipment
Administration system. Some drivers takes the data item names received from the HW and sends them directly on to
the Hub together with their values e.g. Si* for the Si data item etc. The item name translation table contains the
information necessary to translate item names from equipment driver names to the ones known by the QCX
Equipment Administration system. Whenever an equipment driver returns analysis values to the QCX Equipment
Administration system, it will always check with the content of the item name translation table and first carry out
any configured item name translation.
The records in the error translation records contains the fields:
EquipmentFunction: Optional equipment function name. If specified the translation is only active for the stated
equipment function, else it will be active for all equipment functions. If more records holds the same ItemId name,
records with equipment function names supersedes the ones without.
ItemId: Equipment driver data item name.
ItemName: Translated data item name.
Reference Manual QCX Driver Equipment Database Definitions • 13

Enclosures
Alarms & Events

This chapter holds a description of the various alarms and event issued from one of the equipment driver subsystems:
QCX Driver and QCX Driver Communication.
Alarms and events are logged in the ECS alarm system formatted as:
<Subsystem> <ErrNo> <Text> <Parameter 1> <Parameter 2) …..
<Subsystem>: Short name of QCX subsystem issuing the alarm. One of:
• QcxDrv – QCX Driver system.
• QcxCom – QCX Driver Communication system.
<ErrNo>: Error number id as found in the tables listed in the following sections.
<Text>: Error text as found in the tables listed in the following sections.
<Parameter n>: Alarm/Event dependent error parameter value. Can be either a text, an integer or a real value.
For many of the QCX Equipment Administration alarms the parameter values of the text type, are actually composed
of several sub text items separated by a period. Generally the text items are listed in an increasing detail level e.g. a
text parameter listed as <User Name> in the following alarm descriptions, might consist of the information:
<User.Equipment.EquipmentFunction.Program.Dataitem>.
QCX Driver Alarms & Events

Regarding the I/O communication errors 7 – 13 described below, for the majority of drivers, the parameters in the
alarm text follows the same pattern:
<EquipmentName> <Equipment driver state #> <Equipment subsystem return code>
But it can vary from driver to driver.
<EquipmentName> : Equipment name.
<Equipment driver state #>: Current driver state #, found in the relevant QCX equipment driver documentation.
<Equipment subsystem return code>: QCX Equipment Communication subsystem return codes:
• 0 – Ok.
• 1 - System error.
• 2 - Not implemented.
• 3 - Not initialised.
• 4 - Pending request.
• 5 - Not Open.
• 6 - Parameter error.
• 7 - Buffer error.
• 8 – Timeout.
14 • Enclosures Reference Manual QCX Driver

• 9 - Open already.
• 10 - Open failed.
• 11 - Open set parameters failed.
• 12 - Open set timeout failed.
• 13 - Write failed.
• 14 - Read failed.
• 15 - Sequence error.
• 16 – Protocol error.
• 17 – Database initialisation error.
• 18 – Database value read error.
ErrNo: 1
Type: Error
Text: <Error Text>
Explanation: Used for driver specific alarm messages. Please refer to the relevant QCX equipment driver manual.
Action: Equipment driver dependant.
ErrNo: 2
Type: Info
Text: <Info Text>
Explanation: Used for driver specific information messages. Please refer to the relevant QCX equipment driver
manual.
ErrNo: 3
Type: Error
Text: <Error Text><FLSA ref. #>
ErrNo: 4
Type: Info
Text: <Info Text><FLSA ref. #>
manual.
Reference Manual QCX Driver Enclosures • 15

ErrNo: 5
Type: Error
Text: <Error Text><FLSA ref. # 1><FLSA ref. # 2>
ErrNo: 6
Type: Info
Text: <Info Text><FLSA ref. # 1><FLSA ref. # 2>
manual.
ErrNo: 7
Type: Error
Text: I/O open error: <Equipment><State><ErrorCode>
Explanation: The equipment driver failed to open the communication.
Action: -
ErrNo: 8
Type: Error
Text: I/O close error: <Equipment><State><ErrorCode>
Explanation: The equipment driver failed to close the communication.
Action: -
ErrNo: 9
Type: Error
Text: I/O write error: <Equipment><State><ErrorCode>
Explanation: The equipment driver failed during a write.
Action: -
ErrNo: 10
Type: Error
Text: I/O read error: <Equipment><State><ErrorCode>
Explanation: The equipment driver failed during a read.
Action: -
ErrNo: 11
Type: Error
Text: I/O sequence error: <Equipment><State><ErrorCode>

Explanation: The equipment driver received an unexpected communication message.
Action: -
ErrNo: 12
Type: Error
Text: I/O error message: <Equipment><State><ErrorCode>
Explanation: Error message received from physical equipment.
Action: -
ErrNo: 13
Type: Info
Text: I/O error message: <Equipment><State><ErrorCode>
Explanation: Information message received from physical equipment.
Action: -
ErrNo: 14
Type: Error
Text: Equipment busy: <Equipment><State>
Explanation: The equipment driver was not able to start a new equipment function because it was busy.
Action: -
ErrNo: 15
Type: Error
Text: Data error: <Equipment><State><Driver Error #>
Explanation: The equipment driver was not able to start a new equipment function because some information was
not found or illegal e.g. unknown equipment function name.
Action: -
ErrNo: 16
Type: Error
Text: Error calling equipment hub: <Equipment.Command><Eqp. Admin. Error #>
Explanation: The QCX Equipment Administration returned an error, when called by an equipment driver.
Action: -
ErrNo: 17
Type: Error
Text: Equipment hub connect error: <Driver executable><Eqp. Admin. Error #>
Explanation: The equipment driver failed to connect to the QCX Equipment Administration system.
Action: Restart the equipment driver.

ErrNo: 18
Type: Error
Text: Database open error: <Equipment.ItemId.TableName>
Explanation: The driver failed to open the equipment driver access database, while trying to access a data item in a
table.
Action: Check the database, restart the equipment driver.
ErrNo: 19
Type: Error
Text: Database table open error: <Equipment.ItemId.TableName>
Explanation: The driver failed to open an equipment driver access database table, while trying to access a data item
in a table.
ErrNo: 20
Type: Error
Text: Database table empty error: <Equipment.ItemId.TableName>
Explanation: The driver tried to access a data item in an equipment driver access database table, but the table was
empty (Holding no records).
ErrNo: 21
Type: Error
Text: Database table get record error: <Equipment.ItemId.TableName>
Explanation: The driver tried to access a data item in an equipment driver access database table, but the operation
failed.
ErrNo: 22
Type: Error
Text: Database item not found: <Equipment>
Explanation: The equipment driver failed to retrieve data from the equipment driver access table: EqpSystem.
ErrNo: 23
Type: Error
Text: Equipment not initialised: <Equipment>
Explanation: The equipment did not initialise correctly at start-up.
Action: Restart equipment driver.
ErrNo: 24

Type: Error
Text: Function data access error: <Equipment.Command><FLSA ref. #>
Explanation: The equipment driver tried to access data for a sample id not active in the driver.
Action: -
ErrNo: 25
Type: Info
Text: Equipment started: <Equipment>
Explanation: Equipment started successfully.
Action: -
ErrNo: 26
Type: Info
Text: Equipment requests shutdown: <Equipment>
Explanation: The equipment driver requests the QCX Equipment Administration system to stop the driver.
Action: -
ErrNo: 27
Type: Info
Text: Equipment shutdown command: <Equipment>
Explanation: The QCX Equipment Administration system informs the equipment driver that a shut down on the
driver will be executed.
Action: -
ErrNo: 28
Type: Error
Text: Database item not initialised: <Equipment.ItemId.TableName>
Explanation: The driver tried to access a data item in an equipment driver access database table, but the data item
contained no value.
ErrNo: 29
Type: Error
Text: License system access failed: <Driver.Equipment>
Explanation: The equipment driver failed trying to access the license system.
Action: -
ErrNo: 30
Type: Error
Text: License system request failed: <Driver.Equipment>

Explanation: The equipment driver failed trying to access the license system.
Action: -
ErrNo: 31
Type: Error
Text: Insufficient license rights: <Driver.Equipment>
Explanation: The equipment driver is not licensed to run on the QCX system.
Action: -
ErrNo: 32
Type: Error
Text: Equipment status error: <Eqpuipment><State><Driver Error #>
Explanation: The equipment driver is not in a state where it can process the requested equipment function e.g. the
physical equipment is offline.
Action: -
ErrNo: 33
Type: Info
Text: Equipment aborted: <Equipment><State>
Explanation: The user aborted an ongoing equipment function on the equipment driver.
Action: -
ErrNo: 34
Type: Error
Text: Id not found: <Equipment><State>
Explanation: The equipment driver was ordered to do some action on a sample id not known to the driver, e.g. to
abort a sample id already aborted/completed.
Action: -
QCX Driver Communication Alarms & Events

ErrNo: 2
Type: Info
Text: <Info Text>
Explanation: Use to log driver I/O communication in the ECS alarm system. The format is EquipmentName >>
Communication message for messages send by the QCX equipment driver and EquipmentName <<
Communication message for messages received by the QCX equipment driver.
Action: -
ErrNo: 7
Type: Error
Text: Database open error: <Equipment.Database>

Explanation: The driver failed to open the equipment driver access database.
ErrNo: 8
Type: Error
Text: Database table open error: <Equipment.Database.Datatable>
Explanation: The driver failed to open an equipment driver access database table.
ErrNo: 11
Type: Error
Text: Database item not found: <Equipment.ItemId>
Explanation: The equipment driver failed to find an equipment driver access database table record.
Action: Check the database configuration.
ErrNo: 12
Type: Error
Text: Database item not set: <Equipment.ItemId>
Explanation: An item accessed by the equipment driver in an access database table record was found, but contained
no value.
Action: Set the value and restart the driver.
ErrNo: 13
Type: Error
Text: Database item illegal value: <Equipment.ItemId> <ItemValue>
Explanation: An item accessed by the equipment driver in an access database table record was found, but contained
an illegal value.
Action: Correct the value and restart the driver.
ErrNo: 14
Type: Error
Text: Communication not initialised: <Equipment>
Explanation: The communication was not initialised properly due to errors of type ErrNo = 7, 8, 11, 12 or 13.
Action: -
ErrNo: 15
Type: Error
Text: Communication initialise error: <Equipment.ItemId> <NT driver error code>
Explanation: The communication was not initialised because the NT communication driver did not accept an item
data value.

Action: -
ErrNo: 16
Type: Error
Text: Communication open error: <Equipment><NT driver error><FLSA ref. #>
Explanation: The NT communication driver failed to open the communication. FLSA ref #:
• 3 – Invalid port #
• 4 – Invalid port configuration parameters (Baudrate etc.)
• 5 – Invalid timeout settings.
Action: -
ErrNo: 17
Type: Error
Text: Communication write error: <Equipment><NT driver error><FLSA ref. #>
Explanation: The NT communication driver failed to execute a write.
Action: -
ErrNo: 18
Type: Error
Text: Communication read error: <Equipment><NT driver error><FLSA ref. #>
Explanation: The NT communication driver failed to execute a read.
Action: -

QCX Subsystem Error Codes
A OCX installation is build up of a number of subsystems, each reporting any subsystem errors with an error coded
belonging to an error code range specific for the subsystem.
Subsystem Error Range Low Error Range High

QcxCvt -2147220991 -2147220960
QcxSdb -2147220959 -2147220864
QcxSmp -2147220863 -2147220672
QcxEqp -2147220671 -2147220480
QcxBlx -2147220479 -2147220400
QcxRep -2147220399 -2147220208
QcxCom -2147220207 -2147220176
QcxDrv -2147220175 -2147220144
QcxOla -2147220143 -2147220080
QcxAus -2147220079 -2147219888
QcxRob -2147219887 -2147219712
QcxExp -2147219711 -2147219680
QcxPil -2147219679 -2147219632
QcxBlockComm -2147219631 -

Glossary of Terms
Data Item
Data items are used for definition and organisation of data stored in the QCX Sample Database. Data items can be
simple (i.e. measured or entered manually) or derived (i.e. computed from simple data items in association with a
formula).
Derived Item
Derived items are data items computed from one or more simple data items, using a formula.
Reference Item
Reference items are used when it is necessary to compute a derived item from simple data items that are provided by
different equipment in different sub-samples.
Bitmap
Bitmaps may be associated with a number of master entities in the QCX system, including sample groups, sub-
samples, sample points, equipment, equipment functions and programs. Bitmaps are user definable.
Formula
A formula defines how a given derived data value is computed. Formulas are associated with data items. A data item
that has a formula attached is referred to as a derived item.
Unit
User definable units may be associated with data items.
Warning Limits
The term often used in Statistical Process Control for upper and lower limits corresponding to ±2σ away from
average.
Control Limits
The term often used in Statistical Process Control for upper and lower limits corresponding to ±3σ away from
average.
Reference Manual QCX Driver Glossary of Terms • 25

Specification Limits
The term often used in Statistical Process Control for upper and lower limits corresponding to specifications of the
process in question.
Sample Group
Samples are grouped according to the material type produced at the point in the process where they are sampled. A
sample group defines the tasks that must be executed every time a sample of that kind is taken.
Sub-sample
Sub-samples represent portions of samples that have been sub-divided. Sub-samples are convenient in situations
where several sample preparations are needed for various analytical purposes, to facilitate tracking of the complete
history of a sample.
Sample Point
Sample points represent points in the process where samples are taken on a routine basis. A sample point can be
associated with several sample groups. A sample group can only be associated with one sample point.
Equipment
Physical devices that can process, handle or transport samples are referred to as equipment. Each piece of equipment
must have at least one equipment function and one program attached.
Equipment Driver
The software and associated databases that implement an equipment i.e. enables the QCX Equipment Administration
system to interact with the physical device attached to the equipment.
The equipment driver encapsulates anything being equipment specific as e.g. the communication protocol. Seen
from a QCX Equipment Administration system point of view, all equipment drivers only differs by the equipment
functions and data items that the equipment driver supports.
Equipment Function
The various capabilities of equipment are referred to as equipment functions, such as Analysis, Sample Transport,
and Offline Data Entry.
At the time the equipment driver is installed, the driver will create the necessary equipment functions in the QCX
Equipment Administration system.
Equipment Function Item

Most equipment drivers require some equipment function specific information, in order to execute an equipment
function, e.g. the magazine position of the sample to analyse. Any such mandatory data value is handed over to the
equipment driver using an equipment function item.
At the time the equipment driver is installed, the driver will create the necessary equipment function items in the
QCX Equipment Administration system.
Program
Programs summarise parameters and data items to be exchanged when an equipment function is applied. A program
is associated with the combination of a piece of equipment and one of the functions it supports.
26 • Glossary of Terms Reference Manual QCX Driver

Program Analysis Item
Program analysis items are simple data items solely used for returning data values from an equipment driver to the
QCX Equipment Administration system.
Program Parameter Item

Program parameter items are simple data items. They resemble the equipment function items, but whereas the
equipment function items are mandatory, the program parameter items are optional. Program parameter items
overrule equipment function items holding the same name.
Report Template
A report template is a predefined layout used to obtain a uniform presentation of desired data. Four types of report
templates are available:
- Single sample report template
- QCX list report template
- User list report template
- User general template
Report Package
A report package is a predefined setup of a report, consisting of a report template, a list of sample groups, a time
span and a report destination setup.
Trend Package
A trend package is a collection of trend series. Up to eight trend series can be stored in one trend package.
Trend Series
A trend series is a range of values of a data item over time.
QCX Sample Database

The storage place for all historical data in the system, including data originating from optional modules like the
QCX/BlendExpert. Use the Sample Display, Trend or Report applications to examine data stored in the database.

Index
Reference Manual QCX Driver Index • 29

Reference Manual
QCX Driver
Point Value Acquisition

Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Author Dan Mungaard
Name of Word File $Workfile:: QcxDrv30_PntValAcq_English.doc $
Index Range 0-1000
Disclaimer:

Contents
Point Value Acquisition Driver ................................................................1
Introduction................................................................................................................................ 1
Equipment installation ............................................................................................................... 1
Equipment Setup........................................................................................................................ 1
Equipment Driver Database Setup...................................................................................... 1
Equipment Function Setup.................................................................................................. 2
Program setup ..................................................................................................................... 3
Driver Alarms ............................................................................................................................ 4
Glossary of Terms ....................................................................................7
Index ..........................................................................................................9
Reference Manual QCX Driver Contents • i

Point Value Acquisition Driver
Introduction
The Point Value Acquisition (PVA) driver provides a way to collect A-point values
and store these in the QCX sample database. Acquisition is triggered either
automatically through an existing sample point or on demand using a sample group.
Equipment installation
For help on driver installation, refer to the OCX/NT Installation help manual. After
installation, make sure the QcxDrv30DXX_PntValAcq.mdb and
QcxDrv30SXX_PntValAcq.mdb (XX representing an integer) data bases are present in
the Flsadev\proDB\ directory. If the databases are still named
QcxDrv30D##_PntValAcq.mdb and QcxDrv30S##_PntValAcq.mdb, refer to the
installation manual.
Equipment Setup
The virtual Point value acquisition equipment can be used in two different ways, via a
sample point or on demand using a sample group.
When acquisition through a sample point is used, only data items defined in then
equipment driver database will be retrieved. If the sample point at the time of
acquisition points to a valid sample group with the PVA equipment included, data will
be stored in the QCX sample database, but a program associated with the equipment
will be ignored.
For use with a independent sample group, a program has to be defined and associated
with the equipment. The program must include the program parameter “SmpName”
that defines the data to be acquired. Only those data items appearing in the program
AND found in the equipment driver database for the given value of the will be
retrieved.
Equipment Driver Database Setup

The PVA driver needs the two standard driver databases placed under
../flsadev/proDB. QcxDrv30S01_PntValAcq.mdb is the static database, which should
not be changed, while QcxDrv30D01_PntValAcq.mdb holds the dynamic data for
customising the driver.
The dynamic database includes a table named “SmpTable”, which defines the data that
the driver will be able to retrieve.
Reference Manual QCX Driver Point Value Acquisition Driver • 1

ID APoint DataItem SmpPnt
1 Apoint_1 Si SmpPoint_1
2 Apoint_2 Al SmpPoint_1
3 Apoint_3 Fe SmpPoint_1
4 Apoint_4 Ca SmpPoint_1
5 LSF SmpPoint_1
6 SIM SmpPoint_1
7 ALM SmpPoint_1
8 Apoint_5 Si Block_1
9 Apoint_6 Al Block_1
10 Apoint_7 Fe Block_1
11 Apoint_8 Ca Block_1
The “SmpTable” includes 4 columns:

1. ID is a unique identification number
1. APoint is the A-point code providing the value to be acquired. If no value
is entered, the corresponding data item is assumed to be derived. Legal
A-point codes can be found in the point list under: START -> ECS ->
FLSA Summit Suite -> Point List.
2. DataItem is the data item to be associated with the acquired value. When
sample point acquisition is applied, the order of which the data items
appear will be the order they are store on the QCX sample database. The
data items must match data items defined in the QCX system.
3. SmpPnt is either an existing sample point to be used when sample point
acquisition is applied, or any text string whose purpose it is to link A-
points with corresponding data items.
The “SmpTable” above illustrates the two possible ways of point value acquisition.
Record 1 to 7 define values that should be acquired when the SmpPoint_1 sample point
is triggered. Si, Al, Fe and Ca will be read from the associated A-points and the derived
values LSF, SIM and ALM computed.
Record 8 to 11 define values that should be acquired concurrently when a the PVA
equipment function is manually executed from a logged-in sample group. The program
associated with the PVA equipment must in this case include the “SmpName” data
item as a program parameter (see below), and at the time of execution the parameter
must have been assigned the value Block_1 (either through the use of default values or
manually entered prior to execution).
Equipment Function Setup

It is possible to change the equipment bitmap and supply a default program if the
equipment is to be used with independent sample groups.
2 • Point Value Acquisition Driver Reference Manual QCX Driver

Program setup
If the point acquisition driver is to be used in connection with a sample point
independent sample group, an equipment program has to be applied.
A program for the point value acquisition driver needs one program parameter and one
or more analysis items.
The programs for the point value acquisition driver demands the “SmpName” data item
be included in the list of program parameters. It is a string value parameter which
should have the desired text identification as default value (refer to Equipment Driver
Database Setup above). The “SmpName” data item will be added as a system data item
when the driver is installed.

The analysis parameters have to match the data items included in the data base for the
supplied sample point. If not, they will be ignored by the driver.
Driver Alarms
Errors from the driver are posted as errors in the SDR alarm system. The error texts are
located in the dynamic QcxDrv30D01_PntValAcq.mdb database in the “EqpLangText”
table.
4 • Point Value Acquisition Driver Reference Manual QCX Driver

The possible error codes are:
Communication with Smp server failed: Communication error, the Smp server might
be down.
Failed to load A-points: The driver was not able to load the data from the SmpTable in
the dynamic driver data base.
Failed to init. Point acquisition driver: A runtime error occurred while attempting to
initialise the Point acquisition driver.
Failed to retrieve data for sample point: A runtime error occurred while retrieving data
from a sample point.
Failed to retrieve program data: A runtime error occurred while retrieving data for a
sample group.
Failed to retrieve data from A-points: A runtime error occurred while retrieving data
from an A-Point.

Glossary of Terms

Index
Reference Manual QCX Driver Index • 9

Reference Manual
Siemens Configuration
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version SdrV7
Author cna-in
Name of Word File $Workfile:: SiemensS5CfgUI30_English.doc $
Disclaimer:

Contents
Siemens Configuration 1
Introduction 1
Network Protocol Installation 1
System Configuration 1
Address Configuration 1
Network Protocol Installation 2
DLC driver installation in Windows 2000 2
DLC driver installation in Windows 2003, Windows XP and above 3
Coexistence of ESC S5 and S7 driver 4
Configuration Requirements in the PLCs (S5’s only) 5
System Configuration 6
General Config 6
S5 PLC Config 7
S7 PLC Config 9
Department Config 17
Address Configuration 18
Siemens S5 and Siemens Address Configuration 19
Siemens S5 addresses and Pmove profile 22
Siemens S7 addresses and Pmove profile 25
Configuration of S5 Event reporting systems 28
ECS configuration 28
PLC configuration 28
Debug trace (for FLSA internal use). 29
Cabling 31
Siemens S5 "PC" DB9 port 31
Siemens S5 "PC" DB25 port 31
Siemens S5 "PC" RJ45 port (10 pin) 31
Converting from SimS7 to Siemens 32
Index 35
Reference Manual Siemens Configuration Contents • iii

Siemens Configuration
Introduction
This manual describes the procedures used to configure the Siemens I/O system. The major sections include:
Network Protocol Installation

Network protocol defines the structure of the software used to communicate between the PLC's and the Servers. This
step installs the network protocol on the Server workstation to match the protocol used in the network PLC's.
Configuration in the PLC's is also required to enable the ECS system to read and write data to and from the PLC's.
System Configuration
Once the Network Protocol has been installed, configuration of the PLCs can begin. This section describes the
Siemens System Configuration software. Descriptions include I/O polling parameters, parameters associated with
individual PLCs, PLC departments, network statistics, and PLC memory locations used to process start, stop, and
alarm reset commands.
Address Configuration
When ECS database points associated with the Siemens S5 and Siemens I/O system is created, the location of the
point (PLC memory location) must be identified. This section describes the procedure used to associate database
points with the Siemens I/O.
Reference Manual Siemens Configuration Siemens Configuration • 1

Network Protocol Installation
Before we begin the installation procedures, locate the following items:
• Installation CDs included with the software distribution
• Windows Installation CD
• Windows Service Pack CD
DLC driver installation in Windows 2000

In order to use the ECS SimS5 and/or the ECS Siemens driver, the DLC driver must be installed on the computer
running the driver.
To install the driver under Windows, follow the instructions below.
Open Network and Dial-up connections from the desktop or the control panel.
Right click the connection that communicate with the Siemens S5 and/or Siemens and select properties.
In the Local Area Connection Properties dialog, press the Install... button.
2 • Siemens Configuration Reference Manual Siemens Configuration

Select the Protocol network component and press Add...
Select the Microsoft as Manufacturer and the Network Protocol "DLC Protocol". Then press OK.
The driver is now installed on your computer. A system restart is normally not necessary, but if asked, - please
restart the computer.
DLC driver installation in Windows 2003, Windows XP and above

Run the following file: \FLSADev\ToolsNT\Protocol\DLC\INSTALL.CMD

Coexistence of ESC S5 and S7 driver
If the ECS server must communicate with both S5 PLC’s and S7 PLC’s this server can handle communication to
both plc systems. If this server is going to be used together with the IO-server using Softnet then two network
adapters are required. The S5 and Siemens protocol must be bound to one adapter and the S7 (Softnet) protocol must
be bound to the other adapter.
Right click the Network connection with the Network device, used to communicate to the Siemens S5/Siemens PLC
and select Properties.
Verify that the DLC protocol is checked and that the SIEMENS Industrial Ethernet (ISO) protocol is Unchecked.
Repeat this verification for the Siemens S7 (Softnet) network but with reversed checkmarks.

Configuration Requirements in the PLCs (S5’s only)
ECS reading data from PLC
In order to enable the ECS system to read data from the PLC, the following data link block must be programmed in
the CP 143:
Block Type FETCH
Active/Passive: Passive
Priority: 2
Read/Write: Yes
Local TSAP-ID: CPU1FETC
(Can differ, but must match the “PLC Read TSAP” entry in the ECS Siemens S5 configuration. Max 8 characters.)
Remote Eth. Addr: xx xx xx xx xx xx
(Must match the ECS system’s Ethernet address or be set to 00 00 00 00 00 00)
Remote TSAP-ID: SIMH1Ann
(Can differ, but must match the “ECS TSAP” entry in the ECS Siemens S5 configuration. Must be unique for each
PLC. Max 8 characters.)
Furthermore the PLC program must have a least one Send-All block for the CP 143 card.
ECS writing data to PLC

In order to enable the ECS system to write data to the PLC, the following data link block must be programmed in the
CP 143:
Block Type: RECEIVE
Priority: 2
Read/Write: Yes
Local TSAP-ID: CPU1RECV
(Can differ, but must match the “PLC Write TSAP” entry in the ECS Siemens S5 configuration. Max 8 characters.)
Remote TSAP-ID: SIMH1Ann
Furthermore the PLC program must have a least one Receive-All block for the CP 143 card.
Additional configuration
The PLC program must also have a Synchronic function block for the CP 143 with the data unit length BLGR
fixed at 255 ( BLGR : 0,255 ).

System Configuration
The Siemens S5 and Siemens I/O system driver supplied by FLSA is configured by selecting Siemens Config in
the desktop Start menu.
If the Siemens S5 and/or Siemens I/O system driver is missing, please run the ECS installation and choose to install
the missing I/O system.
Remember to run the SDR Profile Setting from the ECS menu afterwards. This will create a shortcut to the Siemens
system configuration user interface.
General Config
Figure 1. General Config
Number of errors without alarm This parameter determines how many errors that must occur on one CPU
before the occurrence of error(s) is reported as an alarm. Legal range: 0 to Number of errors before net switch.
Number of errors before net switch This parameter determines how many errors that must occur on one net
before a switch to the other net will be enforced. Legal range: 1 to Number of errors before PLC down.
Min. time between net switch This parameter specifies how many seconds that must elapse since last switch
before a net switch can be enforced. Legal range: 5 to 600 seconds.
Number of errors before PLC down This parameter determines how many errors that must occur before a PLC
is reported down. Legal range: 1 to 100
Max. time values not updated The amount of time the ECS system will allow to pass before a point that does
not receive any updates is marked as "Not Updated". Legal range: 5 to 600 seconds.
Block Read Timeout The number of seconds for a block to timeout after a client stops reading or writing.
Default update frequency Defines how often the Shared port-owner sends alive to the passive port partner. Legal
entries: 1 to 60 seconds.

Shared owner deadband Defines the minimum time-period between port-owner shift. Legal entries: 10 to 999
seconds
S5 Blocks
Max. block size Specifies the maximum number of bytes in any data block. Legal range: 256 to 2048.
DB legal block range Specifies the range of DBs that can be used in point address set-up. Legal range: 1 to 255.
DX legal block range Specifies the range of DXs that can be used in point address set-up. Legal range: 1 to 255.
S7 Blocks
Max. block size Specifies the maximum number of bytes in any data block. Legal range: 256 to 65535.
DB legal block range Specifies the range of DBs that can be used in point address set-up. Legal range: 1 to
8191.
General information shows the number of licensed PLC's, the number of active PLC's and the number of active
PLC blocks.
S5 PLC Config
PLC Select the PLC to be configured or modified. To the right of the PLC selection pull down box the current status
of the selected PLC is displayed (Undefined, Passive, Polling Ok, No Communication).
To the right of the PLC selection pull down box the current status of the selected PLC is displayed (Passive, Polling
Ok, No Communication)
Figure 2. PLC Configuration S5 - General.

General Tab S5
Name enter or change the display name used for the PLC in question.
Active must be checked in order to have communication with the PLC in question.
Event mode must be checked in order to use Event reporting update from PLCs. Use only Event mode if the PLC
program is able to handle Event reporting.
Please refer to the section: Configuration of S5 Event reporting systems, before activation of Event mode.
PLC Type The type of PLC. Possible choices are: Siemens S5 and Siemens S7.
Two Nets must be checked in order to have two networks (A/B) available for communication with the PLC in
question
Net A Type The type of network protocol used for Network A, e.g. OSI TP4 or Serial.
Net B Type The type of network protocol used for Network B, e.g. OSI TP4 or Serial. The Two Nets checkbox
must be checked in order to use this option.
Polling frequency The update interval to be applied for the CPU is set by this parameter. All points will be
updated by the frequency determined by this time interval. Legal range: 100 to 60,000 msec.
Alarm Group The department name associated with this PLC. Communication alarms for the PLC will be logged
in the selected department.
Watchdog period Determines how often the ECS system will write a watchdog bit to the PLC to indicate that the
ECS system is operational. Legal range: 5 to 3600 seconds. If set to 0 the watchdog function will be disabled.
Watchdog address server1
Watchdog address server2
The address of the bit that will be set by the watchdog function. Specified as type, data block, word, bit.
Bit Support If the PLC program implements support for manipulation of individual bits within a data word, this
check box should be set.
Bit Support Address Specifies where bit manipulation requests will be written to the PLC. Specified as type,
data block number and word. The request consists of 4 words: DB number (with bit 15 set to indicate new request),
Word number, and mask, or mask.
PLC status point The ECS database point that will be updated with the status for this PLC.
The point must be a B-point with the SimS5 IO-type, but with no IO addresses assigned. The conversion algorithm
for the point has to be "Interface Status".
If the status of Net A is Passive and the status of Net B is Polling OK, then the value of the PLC status point will be
Polling OK, if Net B is selected active.

S7 PLC Config
PLC Select the PLC to be configured or modified. To the right of the PLC selection pull down box the current status
of the selected PLC is displayed (Undefined, Passive, Polling Ok, No Communication).
To the right of the PLC selection pull down box the current status of the selected PLC is displayed (Passive, Polling
Ok, No Communication)
Figure 3. PLC Configuration S7 - General.
General Tab S7
Name enter or change the display name used for the PLC in question.
Active must be checked in order to have communication with the PLC in question.
PLC Type The type of PLC. Possible choices are: Siemens S5 and Siemens S7 (Here SimS7).
S7-300 PLC If the connected PLC is a S7-300 enable this checkbox, otherwise it will not be possible to poll the
PLC.
Two Nets must be checked in order to have two networks (A/B) available for communication with the PLC in
question
Net A Type The type of network protocol used for Network A, e.g. OSI TP4.
Net B Type The type of network protocol used for Network B, e.g. OSI. The Two Nets checkbox must be checked
in order to use this option.
Polling frequency The update interval to be applied for the CPU is set by this parameter. All points will be
updated by the frequency determined by this time interval. Legal range: 100 to 60,000 msec.
Alarm Group The department name associated with this PLC. Communication alarms for the PLC will be logged
in the selected department.
Watchdog period Determines how often the ECS system will write a watchdog bit to the PLC to indicate that the
ECS system is operational. Legal range: 5 to 3600 seconds. If set to 0 the watchdog function will be disabled.

Watchdog address The address of the bit that will be set by the watchdog function. Specified as type, data block,
word, bit.
Hot Standby PLC Enabled for Hot Standby PLC's.
Hot Standby Status address The address of the Hot Standby status block in Hot Standby PLC's. Specified as
type, data block and start byte. Only applicable to Hot Standby PLC's.
Rack Specify the rack number where the CPU is placed. If Hot Standby PLC is enabled rack numbers for both
CPU’s must be specified.
Slot Specify the slot number in the rack where the CPU is placed. If Hot Standby PLC is enabled slot numbers for
both CPU’s must be specified.
PLC status point The ECS database point that will be updated with the status for this PLC.
The point must be a B-point with the SimS5 IO-type, but with no IO addresses assigned. The conversion algorithm
for the point has to be "Interface Status".
If the status of Net A is Passive and the status of Net B is Polling OK, then the value of the PLC status point will be
Polling OK, if Net B is selected active.
Secondary PLC status point As above, but only applicable for Hot Standby PLC's
S5 OSI Config Tab
Figure 4., PLC Configuration – S5 OSI Configuration
Adapter Number The Ethernet adapter used for communication on net A and B is specified here. The Ethernet
adapters are numbered starting from 0.
ECS Ethernet address Displays the Ethernet (MAC) address of the ECS computer on net A and B.
PLC Ethernet address The Ethernet (MAC) address of the PLC on net A and B.
Server1 ECS TSAP The TSAP-Id of the ECS system for Server1. Must match the remote TSAP-Id configured in
the data link blocks in the CP 143 and must be uniqe for all PLC / nets. Max 8 characters.
Server1 PLC Read TSAP The TSAP-Id of the PLC used to read data to Server1. Must match the local TSAP-Id
configured in the fetch data link block in the CP 143.

Server1 PLC Write TSAP The TSAP-Id of the PLC used to write datadata from Server1. Must match the local
TSAP-Id configured in the receive data link block in the CP 143.
Server2 ECS TSAP The TSAP-Id of the ECS system for Server2. Must match the remote TSAP-Id configured in
the data link blocks in the CP 143 and must be uniqe for all PLC / nets. Max 8 characters. Applicable for Server2 in
dual systems.
Server2 PLC Read TSAP The TSAP-Id of the PLC used to read data to Server2. Must match the local TSAP-Id
configured in the fetch data link block in the CP 143. Applicable for Server2 in dual systems.
Server2 PLC Write TSAP The TSAP-Id of the PLC used to write datadata from Server2. Must match the local
TSAP-Id configured in the receive data link block in the CP 143. Applicable for Server2 in dual systems.
Net Timeout The amount of time the ECS system will wait for a reply from a PLC. Legal range: 100 to 60000
msec.
No. of retries The amount of retries the link will repeat a message before the message is cancled. Legal range:1 -
10.
Net A status point The ECS database point that will be updated with the status for network A.
Net B status point The ECS database point that will be updated with the status for network B.
S7 OSI Config Tab
Figure 5., PLC Configuration – S5 OSI Configuration
Adapter Number The Ethernet adapter used for communication on net A and B is specified here. The Ethernet
adapters are numbered starting from 0.
ECS Ethernet address Displays the Ethernet (MAC) address of the ECS computer on net A and B.
PLC Ethernet address The Ethernet (MAC) address of the PLC on net A and B.
Secondary PLC Ethernet address The Ethernet (MAC) address of the PLC on net C and D. Only applicable for
Hot Standby PLC's
Net Timeout The amount of time the ECS system will wait for a reply from a PLC. Legal range: 100 to 60000
msec.

Net Timeout Sec As above, but only applicable for Hot Standby PLC's.
No. of retries The amount of retries the link will repeat a message before the message is cancled. Legal range:1 -
10.
No. of retries Sec As above, but only applicable for Hot Standby PLC's.
Net C status point The ECS database point that will be updated with the status for network A. Only applicable
for Hot Standby PLC's.
Net D status point The ECS database point that will be updated with the status for network B. Only applicable
for Hot Standby PLC's.
Serial Config Tab (S5 only)
Figure 6. PLC Configuration - Serial Configuration
Port Name Select the COM port used for communication to the PLC. Legal entries are COM1 to max COM port on
computer.
Baud Rate Select the baud rate for the serial communication line. Legal entries are: 1200, 2400, 4800, 9600,
14400, 19200, 38400, 56000, 57600. Typically set to 19200 or 9600.
Parity Select the parity for the serial communication line. Legal entries are: No, Even, Odd. Typically set to Even
parity.
Timeout The amount of time the ECS system will wait for a reply from the PLC. Legal entries: 500 to 60000 milli
seconds.
Tries The number of times the ECS system will try to send a request to the PLC before the request is discarded.
Legal entries: 1 to 10.
Write timeout The amount of time the ECS system will wait for a write to the PLC is finished. Legal entries: 200
to 5000 milli seconds.

Read interval timeout The amount of time the ECS system will wait for the next byte, when at least one byte is
received.
STX Timeout The amount of time the ECS system will wait for a STX byte (start of message) from the PLC. Legal
entries: 200 to 5000 milli seconds.
Port Owner Applicable to dual systems that must share a single physical port in the PLC.
• Shared - Both servers have access to a port in the PLC.

• Always Server1 - Server1 is connected to the PLC and updates Server2. No automatic shift is done in case
of communication problems.
• Always Server2 - Server2 is connected to the PLC and updates Server1. No automatic shift is done in case
of communication problems.
• Server1 - Sever1 is connected to the PLC and updates Server2. Automatic shift is done in case fo
communication problems.
• Server2 - Server2 is connected to the PLC and updates Server1. Automatic shift is done in case fo
communication problems.
Status Rack 0 and Rack 1 Tab

The Status form provides ECS/PLC communication status for each PLC.
Status Rack 1 only applicable for Hot Standby PLC's
Figure 7. PLC Configuration - Network Statistics
Active net Shows which net (A, B, C or D) is active. This option can be used to switch net.
Reads The number of successful reads.
Read Errors The number of unsuccessful reads.

Writes The number of successful writes.
Write Error The number of unsuccessful writes.
Min. poll time The minimum time it has taken for polling all connected points.
Max. poll time The maximum time it has taken for polling all connected points.
Mean poll time The average time for polling all connected points.
Reset The reset command will reset the statistical counters.
Event Tab (S5 only)

This tab contains the configuration and status for the Event reporting function.
Figure 8. PLC Configuration - Event
Refresh period (sec.)

The period between the server will ask for an update of all digital values (B-points)
Select net Server1
Select net Server2
Address (Type, block and word) where server1 or server2 can select which of the connected Sinec H1 net should be
used for event reporting communication.
Word value: 1=Net A selected, 0=Net B selected
Select Event Server1
Select Event Server2
Address (Type, block and word) where server1 or server2 can select or deselect event reporting.
Word value: 1=Event mode enabled, 0=Event mode disabled.
Please note that the PLC program will set the word to 0, if the watchdog (configured in PLC General tab) is not
running.

Server1 PLC Event TSAP
Server2 PLC Event TSAP
The TSAP-Id of the PLC used to send/receive event data to Server1 or Server2. Must match the local TSAP-Id
configured in the send/receive data link block in the CP 143.
Event Transmission Counters:

Events in last message
The number of event updates of B-points in last message .
Total number of Events

The total number of event updates of B-points.
Full messages
The total number of full messages. Used for tuning of event system.
Repeating full messages

The number of repeating full messages. Used for tuning of event system.
Event errors
The number of errors (timeout waiting for events)
Event status
Shows the status of the connections used for event reporting.
Please note that it is only possible to check the active net, therefore the other net will show the status: Down
Clear
The clear command will reset the statistical counters.
Reset
The reset command will reset configuration data.

Communication block display
To view the communication blocks in a PLC, expand the PLC in the tree by pressing the “+” on the left side of the
PLC name.
Figure 9. PLC Configuration – Communication block display
Selecting a block will display the included addresses and points on the right side. A point can be edited by double-
clicking on the point code.

Department Config
The department config tab is used to associate the start and stop commands (Group Start/Stop, Master Stop, Quick
Stop) and the Alarm commands (Alarm Reset and Alarm Silence) with PLC memory locations. First, select the
department to be configured or modified from the Department list.
Figure 10. Department Configuration
Active Enable the check box to activate the department. Remove the check to deactivate the department.
Address set Selects one of the four address sets that can be configured for the department.
PLC Select the PLC where the commands for this department and address set are to be sent.
Command Each command in the left column must be assigned to the appropriate Block, Word, and Bit within
the PLC. The Type selection defines the type of data stored at the PLC location. Type can be “None” (i.e. not used)
or “DB” for data block or “DX” for Extended Data Block (DX only for S5 plcs).

Address Configuration
The ECS database points that are associated with the Siemens S5 and the Siemens I/O systems are connected to the
system through an address location within the PLC. This address location is specified when the point is created.
First, in the ECS Point Configuration utility, select Siemens S5 (16 - SimS5) or Siemens (25 - Siemens) as the
Interface type.
Figure 11. Point Configuration Utility - select Interface 16-SimS5 or 25-Siemens
The Interface type assignment activates the Interface command button. Click on the Interface command to view
the Siemens S5 or Siemens Address Configuration window.

Siemens S5 and Siemens Address Configuration
The Siemens S5 and Siemens Address Configuration window is used to assign the current ECS database point to a
location within the Siemens S5 and Siemens S7 PLC. The point is used to read a location within the PLC or write to
a location within the PLC.
The Pointcode field identifies the current ECS database point.
Figure 12. Siemens S5 and Siemens Interface Address Configuration
PLC Select the PLC where the point location resides.

Input If this is a point location that is read by the ECS system, enter the data location Type, Block, Word, and Bit
in the Input frame.
Output If this is a point location that is written to by the ECS system, enter the data location Type, Block, Word,
and Bit in the Output frame.
Parameter If this point has an parameter block in the PLC that can be read on request from e.g. a faceplate, enter
the block start address as Type, Block and Word.

Possible S5 input types for analog points are:
None Not used.
DB - 11 bit Input from 11 bit A/D converter from DB.
DB - 12 bit Input from 12 bit A/D converter from DB.
DB - 16 bit Signed Integer, one word from DB.
DB - 32 bit Signed Integer, two word from DB.
DB - Float Siemens floating point value, two word from DB.
DB - 12 bit/Status/Time Input from 12 bit A/D converter , status word and time stamp, three words from DB.
DB - Float/Status/Time Siemens floating point value, status word and time stamp, four words from DB.
DX - 11 bit Input from 11 bit A/D converter from DX.
DX - 12 bit Input from 12 bit A/D converter from DX.
DX - 16 bit Signed Integer, one word from DX.
DX - 32 bit Signed Integer, two word from DX.
DX - Float Siemens floating point value, two word from DX.
DX - 12 bit/Status/Time Input from 12 bit A/D converter , status word and time stamp, three words from DX.
DX - Float/Status/Time Siemens floating point value, status word and time stamp, four words from DX.
Possible S5 output types for analog points are:

None Not used.
DB - 11 bit Output to 11 bit D/A converter from DB.
DB - 12 bit Output to 12 bit D/A converter from DB.
DB - 16 bit Signed Integer, one word from DB.
DB - 32 bit Signed Integer, two word from DB.
DB - Float Siemens floating point value, two word from DB.
DX - 11 bit Output to 11 bit D/A converter from DX.
DX - 12 bit Output to 12 bit D/A converter from DX.
DX - 16 bit Signed Integer, one word from DX.
DX - 32 bit Signed Integer, two word from DX.
DX - Float Siemens floating point value, two word from DX.
Possible S5 input types for digital points are:

None Not used.
DB - 16 bit Machine Status Word (1 to 16 bits) from DB.
DB - 32 bit Machine Status Word (1 to 32 bits) from DB.
DB - 16 bit/Time Machine Status Word and time stamp in two words from DB.
DB - 32 bit/Time Machine Status Word and time stamp in three words from DB.
DX - 16 bit Machine Status Word (1 to 16 bits) from DX.
DX - 32 bit Machine Status Word (1 to 32 bits) from DX.
DX - 16 bit/Time Machine Status Word and time stamp in two words from DX.
DX - 32 bit/Time Machine Status Word and time stamp in three words from DX.

Possible S5 output types for digital points are:
None Not used.
DB - 16 bit Set some or all (1 to 16 bits) in DB word.
DB - 32 bit Set some or all (1 to 32 bits) in DB word.
DX - 16 bit Set some or all (1 to 16 bits) in DX word.
DX - 32 bit Set some or all (1 to 32 bits) in DX word.
Possible S5 parameter types are:
None Not used.
DB Read parameter block from DB.
DX Read parameter block from DX.
Possible S7 input types for analog points are:

None Not used.
DB - Live Zero Input from A/D converter configured for live zero.
DB - UniPolar Input from A/D converter configured for unipolar input.
DB - BiPolar Input from A/D converter configured for bipolar input.
DB - 16 bit Signed Integer, one word.
DB - 32 bit Signed Integer, two word.
DB - Float Floating point value, two word.
DB - Float/Sta./Time Floating point value, status word, time stamp.
Possible S7 output types for analog points are:

None Not used.
DB - Live Zero Output to D/A converter configured for live zero.
DB - UniPolar Output to D/A converter configured for unipolar input.
DB - BiPolar Output to D/A converter configured for bipolar input.
DB - 16 bit Signed Integer, one word.
DB - 32 bit Signed Integer, two word.
DB - Float Floating point value, two word.
Possible S7 input types for digital points are:

None Not used.
DB - 8 bit Machine Status Word (bit pattern) from byte.
DB - 16 bit Machine Status Word (bit pattern) from word.
DB - 32 bit Machine Status Word (bit pattern) from long word.
DB - 16 bit/Time Machine Status Word from word, time stamp.
DB - 32 bit/Time Machine Status Word from long word, time stamp.

Possible S7 output types for digital points are:
None Not used.
DB - 8 bit Set bits in byte.
DB - 16 bit Set bits in word.
DB - 32 bit Set bits in long word.
Possible S7 parameter types are:

None Not used.
DB Read parameter block from DB.
Siemens S5 addresses and Pmove profile

The Siemens S5 Ext. and Pmove Address profile must consist of :
plc1 PLC number
plc2 Input type
plc3 Input block
plc4 Input word
plc5 Input bit
plc6 Output type
plc7 Output block
plc8 Output word
plc9 Output bit
plc10 Parameter type
plc11 Parameter block
plc12 Parameter word

Legal values for plc1 are 0 to number of defined plc’s.
Legal values for plc2 are:
Analog points:
None Not used. 0
DB - 11 bit Input from 11 bit A/D converter from DB. 23
DB - 12 bit Input from 12 bit A/D converter from DB. 18
DB - 16 bit Signed Integer, one word from DB. 19
DB - 32 bit Signed Integer, two word from DB. 20
DB - Float Siemens floating point value, two word from DB. 21
DB - 12 bit/Status/Time 12 bit value , status word and time stamp. 27
DB - Float/Status/Time Floating point value, status word and time stamp 28
DX - 11 bit Input from 11 bit A/D converter from DX. 39
DX - 12 bit Input from 12 bit A/D converter from DX. 34
DX - 16 bit Signed Integer, one word from DX. 35
DX - 32 bit Signed Integer, two word from DX. 36
DX - Float Siemens floating point value, two word from DX. 37
DX - 12 bit/Status/Time 12 bit value , status word and time stamp. 43
DX - Float/Status/Time Floating point value, status word and time stamp 44
Digital points:
None Not used. 0
DB - 16 bit Machine Status Word (1 to 16 bits) from DB. 17
DB - 32 bit Machine Status Word (1 to 32 bits) from DB. 24
DB - 16 bit/Time Machine Status Word and time stamp. 25
DB - 32 bit/Time Machine Status Word and time stamp. 26
DX - 16 bit Machine Status Word (1 to 16 bits) from DX. 33
DX - 32 bit Machine Status Word (1 to 32 bits) from DX. 40
DX - 16 bit/Time Machine Status Word and time stamp 41
DX - 32 bit/Time Machine Status Word and time stamp. 42
Legal values for plc3 are depending of input type:

Values defined in “DB legal block range” (defined at General Config tab).
Values defined in “DX legal block range” (defined at General Config tab).
Legal values for plc4:

0 to Max block size - 1 (defined at General Config tab).

Analog points - no meening.
Digital points:
DB - 16 bit Legal values 0 - 15
DB - 16 bit/Time Legal values 0 - 15
DB - 32 bit/Time Legal values 0 - 31
DX - 16 bit Legal values 0 - 15
DX - 16 bit/Time Legal values 0 - 15
DX - 32 bit/Time Legal values 0 – 31

Analog points:
None Not used. 0
DB - 11 bit Output to 11 bit D/A converter from DB. 23
DB - 12 bit Output to 12 bit D/A converter from DB. 18
DB - 16 bit Signed Integer, one word from DB. 19
DB - 32 bit Signed Integer, two word from DB. 20
DB - Float Siemens floating point value, two word from DB. 21
DX - 11 bit Output to 11 bit D/A converter from DX. 39
DX - 12 bit Output to 12 bit D/A converter from DX. 34
DX - 16 bit Signed Integer, one word from DX. 35
DX - 32 bit Signed Integer, two word from DX. 36
DX - Float Siemens floating point value, two word from DX. 37
Digital points:
None Not used. 0
DB - 16 bit Set some or all (1 to 16 bits) in DB word. 17
DB - 32 bit Set some or all (1 to 32 bits) in DB word. 24
DX - 16 bit Set some or all (1 to 16 bits) in DX word. 33
DX - 32 bit Set some or all (1 to 32 bits) in DX word. 40
Legal values for plc7 are depending of output type:



Analog points - no meening.
Digital points:
DX - 32 bit Legal values 0 – 31

None Not used. 0
DB Read parameter block from DB. 22
DX Read parameter block from DX. 38
Legal values for plc11 are depending of parameter type:


Siemens S7 addresses and Pmove profile

The Siemens S7 and Pmove Address profile must consist of :
plc1 PLC number
plc2 Input type
plc3 Input block
plc4 Input byte
plc5 Input bit
plc6 Output type
plc7 Output block
plc8 Output byte
plc9 Output bit
plc10 Parameter type
plc11 Parameter block
plc12 Parameter byte

Legal values for plc1 are 0 to number of defined plc’s.
Analog points:
None Not used. 0
DB - Live Zero Input from A/D converter configured for live zero. 18
DB - UniPolar Input from A/D converter configured for unipolar input. 19
DB - BiPolar Input from A/D converter configured for bipolar input. 20
DB - 16 bit Signed Integer, one word. 21
DB - 32 bit Signed Integer, two word. 22
DB - Float Floating point value, two word. 23
DB - Float/Sta./Time Floating point value, status word, time stamp. 28
Digital points:
None Not used. 0
DB - 8 bit Machine Status Word (bit pattern) from byte. 29
DB - 16 bit Machine Status Word (bit pattern) from word. 17
DB - 32 bit Machine Status Word (bit pattern) from long word. 25
DB - 16 bit/Time Machine Status Word from word, time stamp. 26
DB - 32 bit/Time Machine Status Word from long word, time stamp. 27



Analog points - no meaning.
Digital points:
DB - 8 bit Legal values 0 - 7.
DB - 16 bit/Time Legal values 0 - 15.
DB - 32 bit/Time Legal values 0 - 31.

Analog points:
None Not used. 0
DB - Live Zero Input from A/D converter configured for live zero. 18
DB - UniPolar Input from A/D converter configured for unipolar input. 19
DB - BiPolar Input from A/D converter configured for bipolar input. 20
DB - 16 bit Signed Integer, one word. 21
DB - 32 bit Signed Integer, two word. 22
DB - Float Floating point value, two word. 23
Digital points:
None Not used. 0
DB - 8 bit Machine Status Word (bit pattern) from byte. 29
DB - 16 bit Machine Status Word (bit pattern) from word. 17
DB - 32 bit Machine Status Word (bit pattern) from long word. 25



Analog points - no meaning.
Digital points:

None Not used. 0
DB Read parameter block from DB. 24
Legal values for plc11 are depending of parameter type:



Configuration of S5 Event reporting systems
The Event reporting function can be used for communication with S5 PLC systems using a special program from
FLSA.
Ther Event reporting function is backwards compatible with the SIMH1 driver used on older ECS/VMS systems.
Systems based on Event reporting will under normal conditions respond faster than polled systems and the
communication load will be lower.
All event updates for B-points are timestamped with 10 msec resolution in the PLC.
Following configuration must be used for S5 Event reporting systems:
ECS configuration
General config:
- insert Max time values not updated: This value must be higher than the Refresh Period in Event configuration. Use
e.g. 100 sec.
PLC General Configuration:

- Insert Watchdog address server1: Type DB-16bit, Block: 18, Word: 3, Bit: 0
- Insert Watchdog address server2: Type DB-16bit, Block: 19, Word: 3, Bit: 0
PLC Event configuration:

The values shown in fig 8 PLC Configuration – Event, can be used for a standard FLSA PLC program based on
Event reporting.
PLC General Configuration:

- check the entry Event mode and the Event function program will be started
S5 Address Configuration:
For event driven systems only a subset of the data types can be used.
Following data types are valid for B-points:
None Not used.
DB - 16 bit Machine Status Word (bit pattern) .
PLC configuration
In order to enable the ECS system to use event reporting from PLC, the following 2 data link blocks must be
programmed in the CP 143 for each server:
Block Type: RECEIVE
ANR: 52 (Server1) or 62 (Server2)
Priority: 2
Read/Write: No
Local TSAP-ID: CPU1EVEN
(Can differ, but must match the “PLC Event TSAP” entry in the ECS Siemens S5 configuration. Max 8 characters.)

Remote TSAP-ID: SIMH1Ann or SIMH1Bnn (where nn is PLC number)
Block Type: SEND
ANR: 53 (Server1) or 63 (Server2)
Priority: 2
Read/Write: No
Local TSAP-ID: CPU1EVEN
(Can differ, but must match the “PLC Event TSAP” entry in the ECS Siemens S5 configuration. Max 8 characters.)
Remote TSAP-ID: SIMH1Ann (net A) or SIMH1Bnn (net B) (where nn is PLC number)
Debug trace (for FLSA internal use).

The driver has build in debug trace functions.
In order to use the debug trace function, following 2 programs must be available on the system:
- c:\FlsaDev\ToolsNT\DebugViewer\Dbgview.exe.
(If this program is not available on the system, then you can get it from FLSA.)
- Microsoft Access
In case of problems with the communication it is possible on-line to activate different types of trace functions.
In the database SdrSimS5Config30.mdb and the table GeneralConfig is a field called DebugLevel used to select the
different types of trace functions.
The field DebugLevel can have following values for trouble-shooting:
0: Trace disabled (normal mode !)

2: Trace of S5 input/output messages
6: Trace of S5 protocol state/event information
7: Trace of S5 Events received
8: Trace of S5 Event tuning information

Figure 13. Trace of Siemens S5 communication (DebugLevel=2)
Do following to activate the trace, when the system is in RUN mode:

1. Start the program Dbgview.exe
2. Use Microsoft Access to modify the field DebugLevel.
3. Activate Apply in the display General Config to get the trace active
(Start/ECS Ntech/SDR Administation Tools/Siemens S5 Config ).
4. Save trace in DebugView to disk file for later investigations or printouts
5. Use Microsoft Access to set the field DebugLevel back to 0.
6. Activate Apply in the display General Config to stop trace.
Warning: Remember to turn off the trace after use, because the trace will slow down the system

Cabling
The following cabling cases are intended to be used, when the Siemens S5 PLC's are connected to the ECS system
by serial wire. The communication standard is based on the RS232 specification that imposes the following
limitations: Maximum cable length is 15 meter at 9600 baud.
Use cable that is intended for RS232 communication.
Siemens S5 "PC" DB9 port
Siemens S5 "PC" RJ45 port (10 pin)

Cable specification:
Siemens S5 DB 25-male "PC" DB9-female
Tx 2 - 2 Rx
Rx 3 - 3 Tx
Gnd 7 - 5 Gnd

Siemens S5 DB 25-male "PC" DB25-female
Tx 2 - 2 Rx
Rx 3 - 3 Tx
Gnd 7 - 7 Gnd
Siemens S5 "PC" RJ45 port (10 pin)

Siemens S5 DB 25-male "PC" RJ45 plug
Tx 2 - 6 Rx
Rx 3 - 5 Tx
Gnd 7 - 7 Gnd

Converting from SimS7 to Siemens
To convert points connected to I/O-system SimS7 to I/O-system Siemens the following must be done:
1. Export points with Pmove.

2. Restart system in maintenance.
3. Install new I/O-system (Siemens).
4. Restart system in maintenance.
5. Open Pmove-file.
6. Open table APoints and change all points with interfaceType 4 to interfaceType 25 or change interfaceType
SIMS7 to interfaceType SIEMENS.
7. Open table BPoints and change all points with interfaceType 4 to interfaceType 25 or change interfaceType
SIMS7 to interfaceType SIEMENS.
8. Import the corrected PMove.
9. Restart system in RUN-mode.
10. Finished.

Glossary of Terms
DB
Data block
DX
Extended data block
Reference Manual Siemens Configuration Glossary of Terms • 33

Department 8, 9, 17
DX 7, 17, Error! Not a valid bookmark in entry on
page 20
DX legal block range 7, Error! Not a valid
bookmark in entry on page 23
Index E
ECS Ethernet address 10, 11
Even 12
Extended Data Block 17
G
Group Start/Stop 17
A I
Active 5, 8, 9, Error! Not a valid bookmark in Input Error! Not a valid bookmark in entry on
entry on page 13 page 19
Active/Passive 5 Interface Error! Not a valid bookmark in entry
Adapter Number 10, 11 on page 18
Address set 7, 17 Interface type 18
Alarm commands 17
Alarm Reset 17
Alarm Silence 17 L
Always Server1 13 Local TSAP-ID 5, Error! Not a valid bookmark in
Always Server2 13 entry on page 10, Error! Not a valid
B
Baud Rate 12 M
Bit 8, 17, Error! Not a valid bookmark in entry on MAC 10, 11
page 19 Master Stop 17
Bit Support 8 Max. block size 7
Bit Support Address 8 Max. poll time 14
BLGR 5 Max. time values not updated 6
Block Error! Not a valid bookmark in entry on Mean poll time 14
page 5, 7, 8, 10, 15, 17, Error! Not a valid Min. poll time 14
bookmark in entry on page 19 Min. time between net switch 6
Block Type 5
N
C
Name 12
Command Error! Not a valid bookmark in entry Net A status point 11, 12, 13
on page 14, Error! Not a valid bookmark in Net A Type 8, 9
entry on page 15 Net B status point 11, 12, 13
CP 143 Error! Not a valid bookmark in entry on Net B Type 8, 9
page 5, Error! Not a valid bookmark in entry Net Timeout 11, 12
on page 10 No 7, 9, Error! Not a valid bookmark in entry on
page 11, Error! Not a valid bookmark in
D entry on page 12, Error! Not a valid
data block 8, 17 No Communication 7, 9
DB 7, 8, 17, Error! Not a valid bookmark in entry No. of retries 11, 12
on page 20 Number of errors before net switch 6
DB legal block range 7, Error! Not a valid Number of errors before PLC down 6
bookmark in entry on page 23 Number of errors without alarm 6
DB legal block range Error! Not a valid
Default update frequency 6
Reference Manual Siemens Configuration Index • 35

O Shared owner deadband 7
Siemens S5 31
Odd 12 start and stop commands 17
Output Error! Not a valid bookmark in entry on STX Timeout 13
page 19 Synchronic function block 5
P T
Parameter 8, 9, Error! Not a valid bookmark in Timeout Error! Not a valid bookmark in entry on
entry on page 19, 25 page 11, Error! Not a valid bookmark in
Parity 12 entry on page 12
Passive 5, Error! Not a valid bookmark in entry on Tries 12
page 6 Two Nets 8, 9
PLC 1, Error! Not a valid bookmark in entry on Type 5, 8, 9, Error! Not a valid bookmark in entry
page 4, 22, 31 on page 17, Error! Not a valid bookmark in
PLC Ethernet address 10, 11 entry on page 22
PLC status point 8, 10
PLC status point 10
Pmove profile 22 W
Pointcode 19 Watchdog address 1 8, 10
Polling frequency 8, 9 Watchdog period 8, 9
Polling Ok 7, 9 Windows Installation CD 2
Port Name 12 Word 8, 17, Error! Not a valid bookmark in entry
Possible input types for analog points 20 on page 19
Possible input types for digital points 20 Write Error 14
Possible output types for analog points 20 Write timeout 12
Possible output types for digital points 21 Writes 14
Possible parameter types 21
Priority 5
Q
Quick Stop 17
R
Read Errors 13, 15
Read interval timeout 13
Read/Write 5
Reads 13, 15
Remote Eth. Addr 5
Remote TSAP-ID 5, Error! Not a valid bookmark
in entry on page 10
Reset 1, Error! Not a valid bookmark in entry on
page 14, Error! Not a valid bookmark in
entry on page 15
S
S5 PLC’s and S7 PLC’s 4
S7-300 PLC 9
Send-All block 5
Server1 13
Server1 ECS TSAP 10
Server1 PLC Read TSAP 10, 15
Server1 PLC Write TSAP 11
Server2 11, 13
Server2 ECS TSAP 11
Server2 PLC Read TSAP 11
Server2 PLC Write TSAP 11
Shared 6, 13
36 • Index Reference Manual Siemens Configuration

Reference Manual
QCX Driver
Generic Receiving Station
G-RCV
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Author Dan Mungaard $
Name of Word File $Workfile:: QcxDrv30_G-RCV_English.doc $
Index Range 0-1000
Disclaimer:

Contents
Introduction...............................................................................................1
Generic Receiving Station Driver for QCX ............................................................................... 1
Generic Receiving Station Driver Installation ........................................3

G-RCV Installation .................................................................................................................... 3
QCX Equipment Setup..............................................................................5

QCX Equipment Configuration ................................................................................................. 5
QCX Equipment Functions........................................................................................................ 6
QCX Equipment Database Setup............................................................................................... 6
System ................................................................................................................................ 7
Driver Specific.................................................................................................................... 7
Point Names........................................................................................................................ 8
Point Value Texts ............................................................................................................. 10
QCX Equipment Communication Protocol ............................................................................. 10
QCX Equipment Auxiliary ......................................................................15

QCX Driver Alarms................................................................................................................. 15
Glossary of Terms ..................................................................................17

Introduction
Generic Receiving Station Driver for QCX

This manual provides information on how to integrate a Receiving Station with the
QCX environment.
The Receiving Station is controlled by the QCX system through a PLC, which will be
programmed to meet specific project requirements. The PLC takes care of all low-level
operations, while it is the driver’s job to monitor the state of the equipment and report
back to the QCX/AutoSampling module about changes.
This driver supports any receiving station adhering to the signal layout as
supported by the QCX Autosampling system.
Notice the QCX/AutoSampling module version 7.0sr1 or higher must be available on
systems running this driver.
Reference Manual QCX Driver Introduction • 1

Generic Receiving Station Driver
Installation
G-RCV Installation
Before installing the driver, be sure the system is in Maintenance mode (see
appropriate SDR system documentation).
To install the receiving station driver, insert the QCX equipment driver CD into the
computer’s CD ROM driver and wait for the installation script to auto-start, then select
the G-RCV driver from the list and answer the questions appropriately.
When the driver has been installed you can view the installation log file before you
quit. The computer must hereafter be restarted in run mode to complete the installation
procedure.
Note that the G-RCV driver by default comes along with a configuration for a
receiving station which is handling one divider/dosing position. You may need to tailor
the QcxDrv30S#_G-RCV.mdb file BEFORE restarting your computer. The mdb file
should be modified to reflect the actual divider/dosing positions.
You should also tailor the tables EqpNamedValues and EqpPointID to hold a set of
dividing/dosing parameters for each of the actual number of divider/dosing positions.
Note that a single copy of G-RCV driver is able to service more than one receiving
station equipment. In an automated environment it is however disirable to have on
copy of the driver to control one receiving station only. You should therefore duplicate
the driver (by using the QCX Equipment Tool Utility) and let one copy control one
receiving station only.
Reference Manual QCX Driver Generic Receiving Station Driver Installation • 3

QCX Equipment Setup
QCX Equipment Configuration

The QCX Equipment entity controlling the Receiving Station will automatically
configure itself during driver installation. The default equipment name – G-RCV –
may be changed using the standard QCX Equipment maintenance dialogs.
One G-RCV driver can service a number of Receiving Stations, i.e. you may specify
the same QCX Equipment for several QCX/AutoSampling Receiving Station entities.
Refer to the QCX/AutoSampling documentation for more information on
configuration.
Notice you should stop the G-RCV driver while editing the QCX/AutoSampling
configuration from the AutoSampling operator user interface and restart it after
finished editing.
The QCX G-RCV driver supports two equipment functions, Divide and Dose. The
Divide function controls one or more Dose functions.
Divide Function
The divide Function has the following parameters. They have to be defined in the
“Program Parameters” in QCX Program Configuration tool.
Parameter Description Remark

#Portions Number of dosing sequences to be extracted from The value of the parameter does
the sample not need to specify the exact
numer of portions to be extracted.
The divide Function returns the following result of the dividing function:
Value Description Remark

DosingOK DosingOk = 1: all dosing sequences terminated
OK
DosingOk = 0: at least one dosing function did not
terminate OK (insufficient material)
Reference Manual QCX Driver QCX Equipment Setup • 5

Dose Function
The dose Function has the following parameters. They have to be defined in the
“Program Parameters” In QCX Program Configuration tool.

#Doses Number of sub doses for the current dosing Value transferred to the Bpoint
sequence. QA1RCV01_TAG01DOSB
ConType Selected container type: Value transferred to the Bpoint
QA1RCV01_TAG01DOSCUP
3,4,5 = Small Cup1,2,3
6,7,8 = Big Cup1,2,3
..
DoseAll Empty entire contents of the sample into the Value transferred to the Bpoint
container QA1RCV01_TAG01DOSALL
DosePos Position wher to dose Value transferred to the Bpoint
QA1RCV01_TAG01DOSA
The dose Function returns the following result of the dose function:
Value Description Remark

DosingOK DosingOk = 1: the dosing sequence terminated OK
DosingOk = 0: the dosing function did not
terminate OK (insufficient material)
QCX Equipment Functions

The Generic Receiving Station driver supports the Reset function invoked by clicking
the Reset button in the Equipment tool application, see
Start Menu -> QCX NTech -> Engineering Tools -> Equipment Tools.
The function will reset the internal sequence of the driver and cause the driver to
initiate an ‘Cleaning’ sequence on all output positions ie. Targets inside the receiving
station(s).
A reset of an input position will reset the specific position and will cause the driver to
initiate an ‘Cleaning’ sequence on the corresponding target.
A reset of an output position will reset the specific information for the output
position. The driver will NOT initiate an ‘Cleaning’ sequence on the corresponding
target.
QCX Equipment Database Setup

The QCX driver for the Receiving Station is by default installed with the parameter
settings as summarised below. Each parameter can be modified by the user through
the Equipment tool application, see
Start Menu -> QCX NTech -> Engineering Tools -> Equipment Tools.
6 • Contents Reference Manual QCX Driver

Please notice, if a parameter has been modified, the G-RCV driver needs to be
restarted before the modification will take effect.
Select the G-RCV equipment from the list and click the Data Edit tab:
The following four database tables contain parameters that may be modified by the
user:
System
Select System from the leftmost pane in the window. Consider modifying this
parameter.
• AlarmGroup - The number of the ECS Alarm group with which alarms and
events generated by the driver should be associated.
• LogMask - The driver should (1) or should not(0) provide additional command
information as shown in the Equipment Tools - ‘Information Tab’.
Driver Specific
Select Driver Specific from the leftmost pane in the window. The table contains
parameters related to the way the G-RCV driver will react in various circumstances:
• TimerPeriod - The number of ms the driver should wait between consecutive
polls of the AutoSampling PLC. Default value is 1000ms.
• SequenceHoldTime - The minimum number of ms the driver should stay in
internal states before transition. Default value is 5000ms.
• SignalHoldTime - The number of ms the driver will hold an output signal to the
PLC before resetting the signal. Default value is 10000ms.
• DecodingAlg - Indicates the method used to assess B-point states.
0: Use B-point value texts to decode states, if these are available, otherwise use
raw MSWs.
1: Use bit encoded MSWs (ie. Bit0 ::= station/sampler #1) to decode states

2: Always use raw MSWs to decode states.
• Enable sensor check - The driver should(1) or should not(0) monitor the
presence of a container at the divider position as indicated by the Bpoint ‘Cup
sensor point tag’.If 0 (Zero) the driver will assume the presence of a container
based on the signalling of the removal/supply of a container at the divider
position. Initiation of a dividing/dosing sequence will not be enabled by the
driver unless a container is present at the divider position. Relevant in an
automated environment only.
• Default container type - The default container type to be used at the divider
position. If set to 0 (Zero) the driver should trigger a supply of the correct
container prior to the start of a dosing sequence. Relevant in an automated
environment only.
• Enable supply container - The driver should(1) or should not(0) automatically
trigger a supply of the ‘default container type’ at the end of a dividing sequence
or upon a ‘reset’ of the divider position. Relevant in an automated environment
only.
• Empty hold time - The number of ms the driver should set the ‘EMPTY’ signal
on (1) when initiating a ‘Cleaning’ sequence. I set to 0 (Zero) the ‘EMPTY’
signal will be reset (0) when the divider is detected to be inside the receiving
station Relevant in an automated environment only.
• Enable return container - The driver should(1) or should not(0) trigger an
automatic return of the container between dosing sequences. Relevant in an
automated environment only.
• Enable clean container - The driver should(1) or should not(0) set the
'ContainerClean' flag ie. Should the container be cleaned after removal at the end
of a dosing operation.
• Ignore divider position - The driver should(1) or should not(0) ignore divider
position signalling. Used for receiving station without a divider or where the
divider is fixed inside the receiving station. Relevant in an automated
environment only.
• Optimize divider handling - The driver should(1) or should not(0) optimize
handling of the divider. When divider handling is optimized the EMPTY signal
is set when the dosing sequence for the last portion/subsample is signalled
completed by the PLC. When divider handling is not optimized the EMPTY
signal is set when the cup holding the last portion/subsample has been removed.
Point Names
• Cup sensor (B-Point) - Bpoint indicating the presence(MSW<>0) /
absence(MSW=0) of a container at the divider output position.
• Material OK (B-Point) - Bpoint indicating that sufficient (MSW<>0) /
insufficient (MSW=0) material was dosed for the current dosine sequence. The
Bpoint should be used when the detecting device (ie. A balance or an optical
sensor) is considered as an integrated part of the divider/dosing position in the
receiving station. The dividing process will automatically be cancelled when
insufficient material is detected.
• Material not OK (B-Point) - Bpoint indicating sufficient(MSW=0) /
insufficient(MSW<>0) material for the latest dosing sequence. The Bpoint
should be used when the conatiner has to be transported away from the
divider/dosing position in the receiving station for detection of (in)sufficient
material. The dividing process will automatically be cancelled when insufficient
material is detected.

• Supply container OK (B-Point) - Bpoint indicating if it for the time being is ok
to supply a container (MSW<>0) / or not (MSW=0)

Point Value Texts
Select Point Value Texts from the leftmost pane in the window. The table contains
the list of B-point value texts that must be defined to control a Receiving Station,
together with the default text number (see appropriate SDR system documentation for
more information on B-points). If actual B-point value text numbers are located
elsewhere, the table must be modified accordingly.
Value text Value text #

Accept 21
Arrived 543
Arriving 541
Aut 7
Available 549
Blank 20
Departing 542
Em ptying 548
Filling 544
In 5
Local 14
Man 8
NotUpdated 16
Occupied 550
Operation 506
Off 2
On 1
Out 6
Ready 505
Default B-point value text numbers
QCX Equipment Communication Protocol

The G-RCV driver communicates with the Receiving Station via the AutoSampling
PLC through standard B-point related I/O (for more information about B-points the
reader is referred to relevant SDR system documentation).
The behaviour of all B-points depends on the actual programming of the
AutoSampling PLC. For information about the AutoSampling PLC the reader is
referred to relevant system commissioning documentation.
The receiving station related input B-points listed below are recognised by the driver
(standard names referring to receiving station 1 on line 1 servicing target 1 are used
in the following; on actual systems the B-point names may very well be different).
QA1RCV01_STS - Mandatory. It contains information about the actual state of the

receiving station. If in alarm, the receiving station will be declared in failure.
QA1RCV01_CNTRL - Optional. If in alarm, the receiving station will be declared in
failure.
QA1RCV01_STP - Optional. If in alarm, the receiving station will be declared in
failure. Current step information of the receiving station

QA1RCV01_RUN - Optional. If in alarm, the receiving station will be declared in
failure. Current run information for the receiving station and receiving station units.
QA1RCV01_ERR1 - Optional. If in alarm, the receiving station will be declared in
failure. Current error indication #1.
failure. Current error indication #2.
failure Current error indication #3.
QA1RCV01_LINSRP - Optional. Defines the lines where carriers have arrived and
where the carrier is ready for unloading/unpacking. Relevant for receiving stations
which are able to handle carriers received from multiple lines.
The receiving station related output B-points listed below are recognised by the
driver
QA1RCV01_LINTAG - Optional. Defines the identity text (Value Text) for a target
inside the receiving station which handles more than one internal target ie. Output
position. Set by the driver when an arrived carrier has been selected to be unloaded.
QA1RCV01_LINSPS - Optional. Defines the identity text (Value Text) for a line the
arrived caarier of which has been selected to be unloaded ie. Moved to the
divider/target position. Relevant for receiving stations which are able to handle
carriers received from multiple lines.
The receiving station line related input B-points listed below are recognised by the
driver
QA1RCV01_RCVL01SA - Optional. ‘Sample Arrived’. Set by the PLC when the
contents of a carrier has been emptied into the target, ie. a funnel divider. Used by the
driver in connection with the QA1RCV01_RCVL01SAID1,
QA1RCV01_RCVL01SAID2 and the QA1RCV01_TAG01SAID1,
QA1RCV01_TAG01SAID2, QA1RCV01_TAG01SAID3 signals.
When RCVL01SA is set by the PLC along with RCVL01SAID1 and RCVL01SAID2
the driver enters the busy state for the connected line and tranfers sample specific
data for GMS Opstation display from the sampler equipment or the plant station
position in question to the defined target. The driver will revert to the idle state for
the connected line once the RCVL1SA signal is reset by the PLC
When RCVL01SA is set by the PLC along with TAG01SAID1 and TAG01SAID2
the driver enters the busy state for the target in question and tranfers sample specific
data for GMS Opstation display from the line in question to the defined target. The
driver will revert to the idle state for the target once the RCVL01SA signal is reset by
the PLC
QA1RCV01_RCVL01STS - Optional. ‘Line StatuS’
QA1RCV01_RCVL01ERR1 - Optional. ‘Line ERRor status #1’
QA1RCV01_RCVL01SAID1 - Optional. ‘SAmple IDentification #1’ defining the
plant station which is busy with the carrier in transition.
QA1RCV01_RCVL01SAID2.- Optional. ‘SAmple IDentification #2’ defining the
sampler equipment or the position at the plant station which is busy with the carrier
in transition.
QA1RCV01_RCVL01ASAID1 - Optional. ‘Associated Sample IDentification #1’.
Value of additional operator supplied sample information at sample login time.
QA1RCV01_RCVL01ASAID2 - Optional.

The receiving station target related input B-points listed below are recognised by the
driver
QA1RCV01_TAG01LRSD - Optional ‘Linear Distributor Sample Dosed’ Is set by the
PLC once the dosing process has completed. Reset to 0(Zero) when the
QA1RCV01_TAG01DOSB signal is reset by the QCX system to 0(Zero)
QA1RCV01_TAG01LDMP - Optional ‘Linear Distributor Manual Position’ Defines
current position of the target, ie. current position of the funnel divider. The divider is
either inside the receiving station (POSSTA, MSW=0x0) , outside holding an
automatically received sample (POSLAB,MSW=0x1) or outside as requested by the
operator (POSMAN,MSW=0x3.)
QA1RCV01_TAG01SAID1 - Optional. ‘SAmple IDentification #1’ defining the
originating plant station for the sample currently located in the target.
originating sampler equipment or the position for the sample currently located in the
target.
originating line for the sample currently located in the target.
QA1RCV01_TAG01COND1 - Optional. ‘Handover CONDition #1’. If defined and if
the point is in an alarm state the information of arrived samples in the target positions
will not be passed on to the receiving system ie. A Robolab or Autoprep system.
QA1RCV01_TAG01COND2 - Optional. ‘Handover CONDition #2’. As above.
The receiving station target related output B-points listed below are recognised by the
driver
QA1RCV01_TAG01DOSA - Optional. Dosing parameter A.
QA1RCV01_TAG01DOSB - Optional. Dosing parameter B. Normally used for
specifying the number of portions for the dosing sequence.
QA1RCV01_TAG01DOSCUP - Optional. Dosing parameter Cup. Defines desired cup
size for the dosing sequence.
QA1RCV01_TAG01DOSALL - Optional. Dosing parameter All. Specifies that the
entire contents of the carrier has to be emptied into the cup.
QA1RCV01_TAG01LREMPTY - Optional. Set by the driver when the dividing/dosing
device should be ‘Cleaned’ ie. At the end of every dividing sequence.
QA1RCV01_TAG01RFILTER - Optional. For future use.

QCX Equipment Auxiliary
QCX Driver Alarms

The QCX driver for the Receiving Station may issue alarm and event messages on the
form:
QcxDrv 15 Data error: <driver name> <text>, <number>
where <driver name> always will be G-RCV.
The <text> field contains textual information about the nature of the error. The source
of the error can be the driver itself (unnumbered text), the AutoSampling server (the
text will have a number followed by a colon imbedded) or an operating system error.
More information about server errors may be found in the QCX/AutoSampling
documentation.
The <number> field will in case of operating system errors contain the standard NT
error number.
The driver may issue the following alarms itself:
TimerPeriod - an illegal value was found in the database, using default (1000ms)
SignalHoldTime - an illegal value was found in the database, using default (10000ms)
SequenceHoldTime - an illegal value was found in the database, using default (5000ms)
DecodingAlg - an illegal value was found in the database, using default (1)
ValText: - the shown value text was not found.
BPoint Input: - the shown input B-point was not found.
BPoint Output: - the shown output B-point was not found.
Reference Manual QCX Driver QCX Equipment Auxiliary • 15

Glossary of
Terms

Reference Manual
QCX Driver
Generic Sampler
G-SMP
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Author Dan Mungaard
Name of Word File $Workfile:: QcxDrv30_G-SMP_English.doc $
Index Range 0-1000
Disclaimer:

Contents
Introduction...............................................................................................1
Generic Sampler Driver for QCX .............................................................................................. 1
Generic Sampler Driver Installation ........................................................3

G-SMP Installation .................................................................................................................... 3

System ................................................................................................................................ 6
Driver Specific.................................................................................................................... 6
Point Value Texts ............................................................................................................... 7
QCX Equipment Communication Protocol ............................................................................... 7
QCX Equipment Auxiliary ......................................................................11

Glossary of Terms .....................................................................................i

Introduction
Generic Sampler Driver for QCX

This manual provides information on how to integrate a generic sampler with the QCX
environment.
The generic sampler is controlled by the QCX system through a PLC, which will be
programmed to meet specific project requirements. The PLC takes care of all low-level
operations, while it is the driver’s job to monitor the state of the equipment and report
back to the QCX/AutoSampling module about changes.
The G-SMP driver will support any sample which adheres to the QCX/Autosampling
Bpoint layout.

Generic Sampler Driver
Installation
G-SMP Installation
To install the sampler driver, insert the QCX equipment driver CD into the computer’s
CD ROM driver and wait for the installation script to auto-start, then select the G-SMP
driver from the list and answer the questions appropriately.
procedure.
Note that a single copy of G-SMP driver is able to service more than one sampler
equipment. You may however duplicate the equipment in order to have one copy
service one sampler equipment only.
Reference Manual QCX Driver SMX Sampler Driver Installation • 3

QCX Equipment Setup

The QCX Equipment entity controlling the generic sampler will automatically
configure itself during driver installation. The default equipment name - G-SMP -
may be changed using the standard QCX Equipment maintenance dialogs.
One G-SMP driver can service many generic samplers, i.e. you may specify the same
QCX Equipment for several QCX/AutoSampling SamplerEquipment entities. Refer
to the QCX/AutoSampling documentation for more information on configuration.
Notice you should stop the G-SMP driver while editing the QCX/AutoSampling
configuration from the AutoSampling operator user interface and restart it after
finished editing.

The Generic sampler driver supports the Reset function invoked by clicking the Reset
button in the Equipment tool application, see
Start Menu -> QCX -> Engineering Tools -> Equipment Tools.
The function will reset the internal sequence of the driver.

The QCX driver for the generic sampler is by default installed with the parameter
settings as summarised below. Each parameter can be modified by the user through
the Equipment tool application, see
Please notice, if a parameter has been modified, the G-SMP driver needs to be
Select the G-SMP driver from the list and click the Data Edit tab.
Reference Manual QCX Driver QCX Equipment Setup• 5

The following three database tables contain parameters that may be modified by the
user:
System
parameter.
• AlarmGroup - The number of the ECS Alarm Group with which alarms and
• LogMask - The driver should (1) or should not(0) provide additional command
Driver Specific
parameters related to the way the G-SMP driver will react in various circumstances:
raw MSWs.
• LongTakeSequenceTime - If no ‘sample taken’ signal is available, the sample
will be considered taken after this amount of time in ms. Default value is
30000ms. If a ‘sample taken’ signal is available and has not been set within this
period of time the driver will issue a ‘sequence error’ provided that the ‘Enable
6 • Qcx Equipment Setup Reference Manual QCX Driver

Long Take Sequence’ in the Sampler Equipment Configuration has NOT been
checked.
Point Value Texts

the list of B-point value texts that must be defined to control a generic sampler,
together with the default text number (see appropriate SDR system documentation for
more information on B-points). If actual B-point value text numbers are located
elsewhere, the table must be modified accordingly.

Accept 21
Arrived 543
Arriving 541
Aut 7
Available 549
Blank 20
Departing 542
Emptying 548
Filling 544
In 5
Local 14
Man 8
NotUpdated 16
Occupied 550
Operation 506
Off 2
On 1
Out 6
Ready 505

The G-SMP driver communicates with the generic sampler via the AutoSampling
PLC through standard B-point related I/O (for more information about B-points the
reader is referred to relevant SDR system documentation).
The input B-points listed below are recognised by the driver (standard names
referring to sampler 1on line 1 are used in the following; on actual systems the B-
point names may very well be different).
QA1SMP01_STS - Mandatory. It contains information about the actual state of the
sampler
QA1SMP01_CNTRL - Optional. If in alarm, the sampler will be declared in failure.

QA1SMP01_STP - Optional. If in alarm, the sampler will be declared in failure.
Current step information of the sampler.
QA1SMP01_RUN - Optional. If in alarm, the sampler will be declared in failure.
Current run information for the sampler and sampler units.
QA1SMP01_ERR1 - Optional. If in alarm, the sampler will be declared in failure.
Current error indication #1.
QA1SMP01_MIX - Optional. If in alarm, the sampler will be declared in failure.
Current status of an associated mixer
QA1SMP01_AST - Optional. ‘Average Sample Taken’. If set by the PLC upon a
‘Take Average Sample’ command, the driver will login, ie. create a sample and
update the dynamic information for the sampler for display on the GMS Opstation
pictures
QA1SMP01_EXT - Optional. ‘EXTernal signal’ which indicates that material is
passing the sampler. When set by the external PLC the QA1SMP1_MSR and the
QA1SMP01_MIM will be set by the driver. See also QA1SMP1_OPR.
QA1SMP01_OPR - Optional.’OPeRator signal’. SDRI interface type signal used by
the operator to define that material is passing the sampler. May be used when a
QA1SMP01_EXT signal is not available. The OPR status will overrule the setting of
the EXT signal when setting the MSR and MIM output signals.
QA1SMP01_SUP - Optional. ‘SUPpress sampling’. External signal used by the
Autosampling server to suppress sampling on the sampler in question. Sampling will
be suppressed when the QA1SMP1_SUP is not in normal mode
QA1SMP01_INH - Optional. ‘INHibit alarm’. External signal used by the
Autosampling server to suppress alarms when timed sampling should have taken
place but no material is passing the sampler at that particular point in time.
QA1SMP01_RPAR1 - Optional. Feedback from QA1SMP01_PAR1.
QA1SMP01_RPAR2 - Optional. Feedback from QA1SMP01_PAR2
The output B-points listed in the table below are recognised by the driver
QA1SMP01_TAS - Optional. ‘Take Average Sample’ Set by the driver upon a ‘Take
Average Sample’/’Operator Take Average Sample’ command. Will be set one cycle
later than the QA1SND01_TAG and QA1SND01_TAG2 signals.
QA1SMP01_TSS - Optional. ‘Take Spot Sample’ Set by the driver upon a ‘Take Spot
Sample’/’Operator Take Average’ command. Will be set one cycle later than the
QA1SND01_TAG and QA1SND01_TAG2 signals.
QA1SMP01_AAS - Optional. ‘Abort Average Sample’. Sample’ Set by the driver
upon a ‘Abort Average Sample’/’Operator Abort Average Sample’ command.
QA1SMP01_MSR - Optional. ‘Material passing SampleR’. Set by the driver when
QA1SMP01_OPR is present and set or when QA1SMP01_EXT is present and set.
Note that the status of OPR overrules the status of EXT. If neither QA1SMP01_OPR
nor QA1SMP01_EXT are present, then MSR is always set.
QA1SMP01_MIM - Optional. ‘Material In Mixer’. Set by the driver when:
a. QA1SMP01_MIX is present and is not in failure
8 • Qcx Equipment Setup Reference Manual QCX Driver

b. QA1SMP01_MIX is not present and when QA1SMP01_OPR is present and set or
when QA1SMP01_EXT is present and set. Note that the status of OPR overrules the
status of EXT. If neither QA1SMP01_OPR nor QA1SMP01_EXT are present, then
MIM is always set.
QA1SMP01_ENA - Optional. Will be set accodring to the operator controlled mode
of the sampler (Off: MSW = 0x0, On: MSW = 0x1).
QA1SMP01_PAR1 - Optional. Set by the driver according to the PLC parameter #1
value for the currently active sampling option. The usage of the parameter is
installation specific.
QA1SMP01_TKP - Optional. ‘TaKe Parameters’. Set by the driver when new
parameters are to be transferred.
Inputs relating to the associated plant station

QA1SND01_STS - Mandatory. If the signals QA1SMP01_AST, QA1SMP01_SST
and QA1SMP01_MIX are not present the driver will recognise a sample to be taken
when the QA1SND01_STS has the value text ‘Occupied’
QA1SND01_LINSRP - Optional. ‘Station Ready in Position’.Indicates that the plant
station has a carrier ready for dispatch in one or more positions. If the signal is
present the QA1SND1_TAG and QA1SND1_TAG2 signals will not be set until the
QA1SND1_SRP has been set by the PLC.
QA1SND01_CNTRL - Optional. ‘Station CoNTRoL’. Upon an ‘Abort
Sample’/’Operator Abort Sample’ command the driver will revert to it’s idle state
once the QA1SND01_CNTRL has the value text ‘Available’ or ‘Ready’
Outputs relating to the associated plant station

QA1SND01_LINTAG - Optional. Indicates which receiving station should receive the
carrier. Set one cycle prior to the setting of the QA1SMP01_TAS or then
QA1SMP01_TSS signal.
QA1SND01_LINTAG2 - Optional. Indicates which target at the receiving station
should receive the carrier. Set one cycle prior to the setting of the QA1SMP1_TAS or
then QA1SMP01_TSS signal.
When the driver starts the TAS, TSS, AAS, ENA and TKP signals will be set to
“OFF”. The PAR1, PAR2, PAR3, PAR4, MSR and MIM signals will be set to “0”
(Zero). The QA1SND01_LINTAG and QA1SND01_LINTAG2 signals will be set to
“Blank”

QCX Driver Alarms

The QCX driver for the generic sampler may issue alarm and event messages on the
form:
where <driver name> always will be G-SMP
documentation.
error number.
SignalHoldTime -an illegal value was found in the database, using default (10000ms)
DecodingAlg -an illegal value was found in the database, using default (1)
LongTakeSequenceTime - an illegal value was found in the database, using default (1)

Glossary of Terms
Reference Manual QCX Driver Glossary of Terms • i

Reference Manual
QCX Driver
Generic Plant Station

(Automatic)
G-SND-A
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Author Dan Mungaard
Name of Word File $Workfile:: QcxDrv30_G-SND-A_English.doc $
Index Range 0-1000
Disclaimer:

Contents
Introduction...............................................................................................1
Generic Automatic Plant Station Driver for QCX ..................................................................... 1
Generic Plant Station Driver Installation ................................................3

G-SND-A Installation ................................................................................................................ 3

System ................................................................................................................................ 6
Driver Specific.................................................................................................................... 6
Point Value Texts ............................................................................................................... 7
QCX Equipment Communication Protocol ............................................................................... 7
QCX Equipment Auxiliary ........................................................................9

QCX Driver Alarms................................................................................................................... 9
Glossary of Terms ..................................................................................11

Introduction
Generic Automatic Plant Station Driver for QCX

This manual provides information on how to integrate a Generic Automatic Plant
Station with the QCX environment.
The Generic Automatic Plant Station is controlled by the QCX system through a PLC,
which will be programmed to meet specific project requirements. The PLC takes care
of all low-level operations, while it is the driver’s job to monitor the state of the
equipment and report back to the QCX/AutoSampling module about changes.

Generic Plant Station Driver
Installation
G-SND-A Installation
To install the plant station station driver, insert the QCX equipment driver CD into the
computer’s CD ROM driver and wait for the installation script to auto-start, then select
the G-SND-A driver from the list and answer the questions appropriately.
procedure.
Reference Manual QCX Driver Generic Plant Station Driver Installation • 3

QCX Equipment Setup

The QCX Equipment entity controlling the Automatic Plant Station will
automatically configure itself during driver installation. The default equipment name
- G-SND-A - may be changed using the standard QCX Equipment maintenance
dialogs.
One G-SND-A driver can service many Automatic Plant Stations, i.e. you may
specify the same QCX Equipment for several QCX/AutoSampling Plant Station
entities. Refer to the QCX/AutoSampling documentation for more information on
configuration.
Notice you should stop the G-SND-A driver while editing the
QCX/AutoSampling configuration from the AutoSampling operator user
interface and restart it after finished editing.

The Generic Automatic Plant Station driver supports the Reset function invoked by
clicking the Reset button in the Equipment tool application, see
The function will reset the internal sequence of the driver.

The QCX driver for the Generic Automatic Plant Station is by default installed with
the parameter settings as summarised below. Each parameter can be modified by the
user through the Equipment tool application, see
Please notice, if a parameter has been modified, the G-SND-A driver needs to be
Select the G-SND-A equipment from the list and click the Data Edit tab:

The following three database tables contain parameters that may be modified by the
user:
System
parameter.
• AlarmGroup - The number of the ECS Department with which alarms and
• LogMask - The driver should(1) or should not(0) provide additional command
Driver Specific
parameters related to the way the G-SND-A driver will react in various
circumstances:
raw MSWs.

Point Value Texts
the list of B-point value texts that must be defined to control an Automatic Plant
Station, together with the default text number (see appropriate SDR system
documentation for more information on B-points). If actual B-point value text
numbers are located elsewhere, the table must be modified accordingly.

Accept 21
Arrived 543
Arriving 541
Aut 7
Available 549
Blank 20
Departing 542
Emptying 548
Filling 544
In 5
Local 14
Man 8
NotUpdated 16
Occupied 550
Operation 506
Off 2
On 1
Out 6
Ready 505

The G-SND-A driver communicates with the Automatic Plant Station via the
AutoSampling PLC through standard B-point related I/O (for more information about
B-points the reader is referred to relevant SDR system documentation).
The input B-points listed below are recognised by the driver (standard names
referring to plant station 1 on line 1 are used in the following; on actual systems the
B-point names may very well be different).
QA1SND01_STS - Mandatory. It contains information about the actual state of the
plant station. When it assumes the value text “Departing”, data regarding the
corresponding sample will be stored. If in alarm, the plant station will be declared in
failure. It is also used to indicate if the station is busy; if its text value is different
from “Ready” and “Available”, it is declared busy.

QA1SND01_CNTRL - Optional. If in alarm, the plant station will be declared in
failure. If its text value is “Local”, the plant station CCA (see below) will be set to
“Manual”.
QA1SND01_STP - Optional. If in alarm, the plant station will be declared in failure.
Current step information of the plant station.
QA1SND01_RUN - Optional. If in alarm, the plant station will be declared in failure.
Current run information for the plant station and plant station units.
QA1SND01_ERR1 - Optional. If in alarm, the plant station will be declared in failure.
The output B-points listed in the table below are recognised by the driver
QA1SND01_CCA - Optional. Station Computer Control Accept. If the plant station
CNTRL input point is “Local” or the station is declared in failure, the B-point will be
se to “Manual”, otherwise it will be set to “Automatic”.
QA1SND01_LINSPS - Optional. Will send a carrier from the indicated position.
QA1SND01_LINTAG - Optional. Indicates which receiving station should receive the
carrier. The signal may be used by the sampler equipment driver.
QA1SND01_LINTAG2- Optional. Indicates which target at the receiving station
should receive the carrier. The signal may be used by the sampler equipment driver.
When the driver starts, the CCA point will be set to “Manual” and the others to
“Blank”.

QCX Driver Alarms

The QCX driver for the Generic Automatic Plant Station may issue alarm and event
messages on the form:
where <driver name> always will be G-SND-A.
documentation.
error number.
SignalHoldTime - an illegal value was found in the database, using default (10000ms)
DecodingAlg - an illegal value was found in the database, using default (1)

Glossary of
Terms

Reference Manual
QCX Driver
ARL WinXRF X-Ray

Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Author Dan Mungaard
Name of Word File $Workfile:: QcxDrv30_WinXRF_English.doc $
Index Range 0-1000
Disclaimer:

Contents
Introduction...............................................................................................1
ARL WinXRF Driver for QCX ................................................................................................. 1
Driver installation .....................................................................................3

Driver installation ...................................................................................................................... 3
ARL WinXRF PC HW/SW ..........................................................................4

WinXRF Installation.................................................................................................................. 4
WinXRF Analytical Configuration............................................................................................ 4
WinXRF Automatic Task Configuration ................................................................................... 4
Running WinXRF in QCX Control ........................................................................................... 5
QCX Equipment Communication.............................................................6

QCX Communication Protocol.................................................................................................. 6
Analysis Sequence .............................................................................................................. 6
Error Messages and Warnings ............................................................................................ 7

QCX Equipment Setup ............................................................................................................ 11
QCX-WinXRF PC Communication Setting ..................................................................... 11
Equipment Loading and Move Positions .......................................................................... 11
Equipment Manual Input Channels .................................................................................. 13
Equipment Item Names and translation ............................................................................ 14
Equipment B-Point Status................................................................................................. 16
LOI Support...................................................................................................................... 16
QCX Equipment Auxilliary .....................................................................17

QCX Driver States ................................................................................................................... 17
QCX Driver LOI Support ........................................................................................................ 18
Configuring LOI support in the QCX system................................................................... 18
Configuring LOI support in the ARL WinXRF Application, known dilution ratio.......... 18
Configuring LOI support in the ARL WinXRF Application, unknown dilution ratio...... 20
Robolab Considerations ........................................................................................................... 23
Automatic Mode Operation .............................................................................................. 23
Manual Mode Operation................................................................................................... 23
Equipment Reset............................................................................................................... 23
Equipment Function Abort ............................................................................................... 23

Introduction
ARL WinXRF Driver for QCX

This manual provides information on how to integrate a standalone PC running the
ARL WinXRF X-ray software into the QCX environment. By standalone is meant a
PC not part of the basic QCX HW/SW installation.
The ARL WinXRF application provides a user interface for control of the majority of
ARL’s X-rays, e.g. the ARL9800 TCA. For a complete list of supported X-rays, please
refer to relevant ARL documentation.
The ARL WinXRF software is installed on a standalone PC running either Win95 or
WinNT. This PC is connected to the X-ray via a serial link.
The connection between the ARL WinXRF application and the QCX system is based
on a Win Socket on the network running TCP/IP.
The protocol between the ARL WinXRF application and the QCX system is very
simple. All matters regarding data definition, calibration etc. are handled solely inside
the ARL WinXRF application. The interaction between the ARL WinXRF package
and the QCX system is limited to:
• The QCX system requests ARL WinXRF application status.
• The QCX system requests start of an analysis sequence, identified by a
legal ARL WinXRF program name and a sample position.
• The QCX system requests start of a sample move operation.
• The ARL WinXRF application returns the quantitative analysis result to
the QCX system.
• The ARL WinXRF application returns a warning or an error message to
the QCX system.
This manual is based on the assumption that there is already a PC present running the
ARL WinXRF application, and the necessary WinXRF software options have been
installed to allow control of the X-ray from a remote computer (Automation).

Driver installation
Driver installation
To install the WinXRF driver, insert the QCX equipment driver CD into the
computer’s CD ROM driver and wait for the installation script to auto-start, then
select the WinXRFdriver from the list and answer the questions appropriately.
The driver by default installs with 49 sample loader rack positions and with 2
external belt positions.
Reference Manual QCX Driver Driver installation • 3

ARL WinXRF PC HW/SW
WinXRF Installation
Regarding installation of the ARL WinXRF software package, please refer to the
relevant ARL documentation.
WinXRF Analytical Configuration

The analytical conditions, e.g. which elements to analyse, are defined in the
Analytical Programs in the ARL WinXRF application. To view the analytical
program definitions the ARL WinXRF application must first be taken out of
automatic mode. To bring up the analytical programs menu select from the WinXRF
Main Menu control bar:
WinXRF Main Menu -> Preparation -> Analytical Programs
The data item names found in the list in the upper left part of the menu are the tag
names sent to the QCX system. Each tag name uniquely identifies a data item
analysis value.
For a more detailed description of Analytical Programs configuration, please refer to
the relevant ARL documentation.
WinXRF Automatic Task Configuration

An automatic task for analysing of production samples should be defined in the
WINXRF for facilitating of running of WINXRF in QCX control. To bring up the
automatic task configuration select from the WinXRF Main Menu control bar:
WinXRF Main Menu -> Preparation -> Automatic Tasks -> % Production
Samples
If yout WinXRF PC is running Windows2000 you should select:
WinXRF Main Menu -> Preparation -> Automation Tasks -> Concentration
Analysis
The name of the automatic task should be given as “AUTO”. Leave all other options
in the automatic task configuration as the default settings.
For a more detailed description of Automatic task configuration, please refer to the
relevant ARL documentation.
4 • ARL WinXRF PC HW/SW Reference Manual QCX Driver

Running WinXRF in QCX Control
To enable X-ray control from the QCX system, the ARL WinXRF application must
be set in Automatic Mode. This is done from the WinXRF Main Menu control bar:
WinXRF Main Menu -> Automation -> Enter automatic mode
The ARL WinXRF application comes with a very nice facility for logging the
network communication between the ARL PC and the QCX system.
To view the log, open the Net Interface icon in the PC taskbar. Messages from the
QCX system are coloured yellow, and messages to the QCX system are shown in a
green.
Reference Manual QCX Driver ARL WinXRF PC HW/SW • 5

QCX Equipment Communication
QCX Communication Protocol

The communication between the QCX system and the ARL WinXRF application
uses an ASCII based, 0 (ASCII 0) terminated message protocol.
The commands are built up of individual commands/parameters in the format:
CommandID@ or
CommandID@ followed by any number of parameters in the format
ParameterID=ParameterValue@
The order of the parameters is not significant, which enables ARL to add new
parameters to existing commands in future ARL WinXRF application releases,
without the QCX system SW has to be modified.
To make the messages more readable, a space has been inserted in the examples
below between the commands and parameters. Messages sent by the QCX system are
headed by a >>, and messages received by the QCX system are headed by a << for
clarity.
The actual messages are sent in one unbroken string without spaces and without the
leading << or >>.
Analysis Sequence
The telegrams in a typical analysis sequence are:
>> RESET_IDLE@
>> ARE_YOU_THERE@
<< I_AM_HERE@
>>LOAD_PS_TASK@ Name=”AUTO”@ Category_Prod=P@
Associated_File=<ProgramName>@ Check_for_SCT=Y@
<< TASK_LOADED@Status=Y@
>> PREPARE_PS_ANALYSIS@ SID1=”123456”@ SID2=”SGroup”@
Casette_to_Analyse=<Position>@ Runs_Requested=1@ Runs_Allowed=1@
Return_Results=A@
<< PS_ANALYSIS_PREPARED@ Status=Y@ Duration=20.000@
>> START_ANALYSIS@
Physical measurement …..
6 • QCX Equipment Communication Reference Manual QCX Driver

<< PS_ANALYSIS_RESULT@ Status=G@ Elements=”Al”,”Fe”,”Ca”,”Si”@
Values=1.23,2.34,45.67,12.34@
<< ANALYSIS_DONE@
<ProgramName>: Analytical Program name as defined in the ARL WinXRF

application.
<Position>: Position of sample to be loaded: See Positions description below
Error Messages and Warnings

The format of a warning is:
<< LOG_MESSAGE@ Text=” …. Warning text …..”@
The format of an error message is:
<< MESSAGE_ERROR@ Type=O@ Info=” …. Error text ….”@
Reference Manual QCX Driver QCX Equipment Communication • 7

QCX Equipment Setup

The QCX WinXRF driver supports two equipment functions, Analysis and Move.
Simultaneous Analysis and Move commands are supported.
ANALYSIS Function
The analysis Function has the following parameters. They have to be defined in the
“Program Parameters” in QCX Program Configuration tool.

PCProgram Name of analytical program in the ARL WinXRF
application. 1 – 8 characters
Timeout Timeout of the total measurement cycle, including sample If omitted, default is 90s
loading, pumping time etc (in Seconds)
LoadPos Load position of the sample to analyse See Positions description
below
UnloadPos Unload position of the sample to analyse If omitted then Unload
Position = Load Position
InputLOI Manually entered LOI Option
#Runs Number of runs. Sets WinXRF task parameters Option
Runs_Allowed and Runs_Requested
Note that additional Manual input Parameters may be defined for transfer to the
PCProgram prior to analysis start.PCProgram
MOVE Function
Move Function has the following parameters. They have to be defined in the
“Program Parameters” In QCX Program Configuration tool.

Timeout Timeout of the Move Operation. If omitted Default = 90s

FromEqp Move Sample From Equipment Refers to the actual equipment or to an external
belt
FromPos Move sample From Position Move not allowed From Ejection Position. See
Positions description below
ToEqp Move Sample To Equipment Refers to the actual equipment or to an extenal
belt
ToPos Move Sample To Position Move not allowed to loading Position. See
Positions description below
Abort Function
Abort an ongoing Function (Analysis or Move).
For Move Function, whatever the Status of the dialogue, nothing will be sent to the
equipment and “Aborted” Sample Move will be sent back to QCX.
For Analysis Function, according to the step in the Analysis sequence dialog, an
ABORT_ANALYSIS will be (or nothing will be) sent to the equipment. “Aborted”
Sample Analysis will be sent back to QCX.
Reset Equipment
Reset Equipment will abort all pending Functions (Analysis, Move), reset the
communication by closing the port (which will be opened again for the first read (or
write) From (to) WinXRF. Reset Equipment is necessary if for any reason
WinXRF has been stoped and restarted, otherwise any Read/Write From/To
WinXRF will fail.
To reset Equipment Select :

Start Menu -> QCX -> Engineering Tools -> Equipment Tools
Then Select “ARL WinXRF” Item in the Equipment list and Click Reset Button
10 • QCX Equipment Setup Reference Manual QCX Driver

QCX Equipment Setup
This chapter describes the most important equipment specific data found in the QCX
WinXRF driver disk database: C:\FLSADev\ProDb\QcxDrv20D01_WinXRF.mdb
For a description of general QCX equipment driver database configuration, please
refer to the general help found in:
Start Menu -> QCX -> Engineering Tools -> Equipment Tools ->DATA
EDIT
QCX-WinXRF PC Communication Setting

The database value: IOType, TCP/IP, HostIP must be set to match the IP address
of the WinXRF PC.
The database value: IOType, TCP/IP, HostPort must be set to match the port
number on the WinXRF PC used for communication with a remote computer. This
value is normally set to 1234 on the WinXRF PC.
Note: The Host IP Address in the Pic. Is an example only.
Equipment Loading and Move Positions

• WinXRF supports the following types of positions:
• One Loading Position referenced as –1 or ‘.’ (dot, only one character)

• A maximum of 63 rack positions, referenced form 1 to 63.
• A maximum of 3 Belts position, referenced from B1 to B3 or (501 to 503)
• A maximum of 3 Waiting position, referenced from W1 to W3 or (601 to 603)
• A maximum of 3 Ejection (Basket) position, referenced from E1 to E3 or (701
to 703)
These Positions are not necessary physically present. If needed, physical positions
have to be configured in the equipment and the references to be set in QCX.
For positions, reference setting can be done in:
Start Menu -> QCX -> Engineering Tools -> Equipment Tools ->DATA EDIT->
Driver Specific.
Position Configuration :
• Loading Position
Nothing to configure is referenced as –1 or ‘.’ (dot).
• Rack Positions (2 items to be set)

a) “RackFirstPosition” : the first Position in the rack (if any), in the interval 1
to 63
b) “RackNumberOfPositions” : Number of position in the rack, 0 if none
Example : if you define RackFirstPosition = 1 and RackNumberOfPositions =
49 then rack positions are 1, 2 ….. 49
• Belts Position (2 items to be set)

a) “BeltFirstPosition” : the first belt (if any), reference from B1 to B3
b) “NumberOfBelts” : Number of attached belts 0 if none

Example : if you define BeltFirstPosition = B2 and NumberOfBelts = 3 then
belt positions are B2,B3 and B4
• Waiting Positions (2 items to be set)

a) “FirstWaitingPosition” : the first Waiting (if any) reference From W1 to
W3
b) “NumberOfWaitingPosition” : Number of Waiting Postion, 0 if none
Example : if you define FirstWaitingPosition = W1 and
NumberOfWaitingPosition = 2 then Waiting positions are W1 and W2
• Basket (Ejection) Positions (2 items to be set)

a) “BasketFirstPosition” : the first Basket Position (if any) reference From E0
to E3
b) “BasketNumberOfPositions” : Number of Basket Positions , 0 if none
• Use belt only (1 item to be set, range 0-63)

Value is pertaining to the operation of the WinXRF in an automated
environment, ie. robolab. It defines the number of positions on the sample
loader rack which should be reserved for samples which are introduced
from an external belt.
A value of 0 (zero) forces the driver to analyse from the load position (-
1 or '.') only.
A value of 1 (one) forces the driver to analyse from belt position 1 (B1)
only.
A value n in the range 2-63 limits the driver to make use of the first n
positions on the rack for sample introduced via belt B1. Position n+1
cannot be used for samples introduced by robolab. The remainder of the
rack may be used for manually introduced samples.
Equipment Manual Input Channels

The WinXRF driver supports transfer of values to the manual input channels 1
through 15 (MIC1 … MIC15) if the values are required by the analytical program.
The actual values should be defined as sample group reference items. Please refer to
the QCX Sample Group setup/data items.
EDIT-> Driver Specific

• Manual Input (1 item to be set)
Defines the QCX item name the value of which is to be transferred to the
manual input channel n MICn at the start of the analysis.
Equipment Item Names and translation

Equipment data item names may be translated into item names as recognized by the
QCX system.:
EDIT-> Item NameTranslantion:

• Item Id: Defines the item as identified by the WinXRF PC/Analytical program
• Item Name: Defines the item as recognized by the QCX.
• Equipment Function: Should always be Analysis.

Equipment B-Point Status
It is possible to assign a B-point to the equipment to reflect its status. It can be set in :
EDIT-> Point Names.
The conversion algorithm associated with the point should be the

‘qcx_generic_status’ algorithm.
LOI Support
The database value: General, , ETSupport defines if the QCX WinXRF driver
supports “Error Translation”. 0 – No support, 1 – Supported.
For a description of QCX equipment driver error translation, please refer to the
general help found in:
Start Menu -> QCX -> Engineering Tools -> Equipment Tools. DATA EDIT -
> Driver Specific
The database value: General, , LOISupport defines if the QCX WinXRF driver
supports operator insertion of LOI. 0 – Not supported, 1 – Supported. For a
description of QCX WinXRF driver LOI support, please refer to the next chapter.

QCX Equipment Auxilliary
QCX Driver States

The QCX WinXRF driver is build as a state/event machine. In most of the
alarm/events issued by the QCX WinXRF driver, the state number is included in the
message.
State number/State description:
Alarm /Event Are generaly as Following
QCXDrv <AENo> Message <P1> <P2>
AENo P1 P2 Description
1 9 52 Write to WinXRF failed.
2 12 6 WinXRF failed during LOAD TASK
3 12 8 WinXRF failed during ANALYSIS PREPARATION
4 12 10 WinXRF failed during ANALYSIS RESULT
5 12 21 WinXRF failed during SAMPLE MOVE
6 12 57 Too many simultanous functions (Analysis or Move) have been
requested by QCX
7 15 50 Missing or wrong function parameter value.
8 15 55 The requested QCX function is not supported.
9 35 51 Analysis or Move timeout.
10 35 58 Communication Check Timeout. No answer from WinXRF to
ARE_YOU_THERE Request.
QCX Driver Alarms

The QCX WinXRF driver does not contain any QCX WinXRF driver specific
alarms. For a description of general QCX driver alarms, please refer to the general
help found in:
Reference Manual QCX Driver QCX Equipment Auxilliary • 17

QCX Driver LOI Support
Configuring LOI support in the QCX system

The QCX WinXRF driver/ARL WinXRF application is able to support manual
insertion of LOI
The relevant analytical programs in the ARL WinXRF application must be
configured with the Manual Input Channel: LOI.
The WinXRF programs in the QCX system supporting LOI must be configured with
a program parameter item named InputLOI. This Program parameter is used to define
the LOI value sent to the ARL WinXRF application at analysis time.
In this case the PREPARE_PS_ANALYSIS command includes an extra parameter:
MIC1=<LOI>@
<LOI>: LOI value as entered on the QCX system.
Configuring LOI support in the ARL WinXRF

Application, known dilution ratio
The QCX/BlendExpert module uses analyses with Loss On Ignition for calculation of
production and single estimated analysis (backcalculation). If glass beads are used,
and if the dilution ratio is correct and LOI is known at the time of the analysis the
analysis programs on the WinXRF must be defined to include Loss On Ignition as
follows:
First change compound names as follows:

Preparation --->Analytical Program--->ProgramName---->Element details
change the compound names to:
Si, Al, Fe, Ca, Mg, K, etc.
Define PSEUDO elements as seen below:
18 • QCX Equipment Auxilliary Reference Manual QCX Driver

When the analysis has finished, the ARL WinXRF application will calculate all
PSEUDO elements and send ALL real/pseudo elements to the QCX system.
This exercise MUST be done for all programs using glass beads with correct dilution.
Finally the PSEUDO elements are translated to QCX data items by using the Item
Name Translation table: Si1 translated to Si etc.
Configuring LOI support in the ARL WinXRF

Application, unknown dilution ratio
If glass beads are used, and if the dilution ratio and LOI is NOT known at the time of
the analysis the analysis programs on the WinXRF must be defined to include Loss
On Ignition as follows:
We can normalize the LOI-free sum to 100 by defining a pseudo element formula:
SUM = Si+Al+Fe+Ca+Mg+K etc

Scale the elements to give a sum = 100 by LOI-free normalized analysis:
Si1 = Si*100/SUM
Al1 = Al*100/SUM
Etc = etc
Convert from LOI-free analysis to normal.

Calculation of LOI:
LOI1 = 0.786*Ca1+1.089*Mg1

SUM1 = Si1 + Al1 + Fe1++ + LOI1
This is not quite accurate but it works in most contexts.
Scaling of LOI-free analysis to LOI uncompensated analysis:

Si2 = Si1*100/SUM1
Al2 = Al1*100/SUM1
Etc = etc

When the analysis has finished, the ARL WinXRF application will calculate all
PSEUDO elements and send ALL real/pseudo elements to the QCX system.
This exercise MUST be done for all programs using glass beads with unknown
dilution.
Finally the PSEUDO elements are translated to QCX data items by using the Item
Name Translation table: Si2 translated to Si etc.
Robolab Considerations
Automatic Mode Operation

The sample loader cover should at any time be kept closed when the equipment is
being operated in automatic mode. Samples will not be moved when either cover is
open
During periods where the sample loader rack is empty the WinXRF driver should
periodically (once every minute) check the connection to the WinXRF PC.
Manual Mode Operation

If for some reason you which to do manual operations on the WinXRF PC you
should exit the ‘Automation Mode’ on the WInXRF PC. It is recommended that you
put the equipment into manual mode in the robolab cell before you terminate the
automation mode on the WinXRF PC.
Equipment Reset
Note that if you ‘RESET’ the equipment all information about samples currently
handled by the sample loader rack will disappear. You may however clear the
information for a single sample on the sample loader rack by resetting the
corresponding position, input or output.
Equipment Function Abort

Equipment functions (Analysis) for samples which are introduced via robolab cannot
be aborted by accessing the function in the QCX Active Samples list.
Reference Manual QCX Driver • 23

Untitled

Uploaded by

Document Information

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

Untitled

Uploaded by

Copyright:

Available Formats

Windows Server 2003 (W2K3) Installation 1

Windows XP Professional Installation 2

Windows Server 2003

All rights reserved.

Copyright © FLSmidth A/S.

Reference Manual Windows Server 2003 Installation Contents • iii

In order to browse network resources the following information is also required:

Windows Server 2003 Installation Procedure

How to create a Windows Server 2003 Domain

Making a Computer member of a Domain

Adding an additional Domain Controller

Service Pack Installation

Reference Manual Windows Server 2003 Installation Glossary of Terms • 3

Error! No index entries found.

Reference Manual Windows Server 2003 Installation Index • 5

All rights reserved.

Copyright © FLSmidth A/S.

Reference Manual Windows XP Installation Contents • iii

1. The personal computer is in the Microsoft Windows XP Professional HW Compatibility List

Reference Manual Windows XP Installation Windows XP Professional Installation • 1

For Windows XP Professional installation:

- Microsoft Windows XP Professional professional

In order to browse network resources the following information is also required:

• TCP/IP address for DNS server

2 • Windows XP Professional Installation Reference Manual Windows XP Installation

Reference Manual Windows XP Installation Windows XP Professional Installation • 3

Refer to the documentation for the computer.

4 • Windows XP Professional Installation Reference Manual Windows XP Installation

Reference Manual Windows XP Installation Windows XP Professional Installation • 5

6 • Windows XP Professional Installation Reference Manual Windows XP Installation

• Click Next and Finish

Reference Manual Windows XP Installation Windows XP Professional Installation • 7

8 • Windows XP Professional Installation Reference Manual Windows XP Installation

Reference Manual Windows XP Installation Glossary of Terms • 9

Error! No index entries found.

Reference Manual Windows XP Installation Index • 11

Windows 2000 Installation

All rights reserved.

Copyright © FLSmidth A/S.

Reference Manual Windows 2000 Installation Contents • iii

Reference Manual Windows 2000 Installation Windows 2000 Installation • 1

For Windows 2000 Professional installation:

For Windows 2000 Server installation:

In order to browse network resources the following information is also required:

2 • Windows 2000 Installation Reference Manual Windows 2000 Installation

Reference Manual Windows 2000 Installation Windows 2000 Installation • 3

Refer to the documentation for the computer.

4 • Windows 2000 Installation Reference Manual Windows 2000 Installation

To create a Domain and Domain Controller you must:

5. Click Advanced and DNS

Reference Manual Windows 2000 Installation Windows 2000 Installation • 5

Set the primary suffix to the DNS

10. Reboot the computer when asked

Install and configure a DNS server

6 • Windows 2000 Installation Reference Manual Windows 2000 Installation

20. Check Create a new file… and click Next

Reference Manual Windows 2000 Installation Windows 2000 Installation • 7

8 • Windows 2000 Installation Reference Manual Windows 2000 Installation

Reference Manual Windows 2000 Installation Windows 2000 Installation • 9

10 • Windows 2000 Installation Reference Manual Windows 2000 Installation

Adding a Domain Controller

Install and configure a DNS server

Reference Manual Windows 2000 Installation Windows 2000 Installation • 11

21. In Additional Domain Controller click Next