VHK.4120.018.00.en: Af-Kdf 4

VHK.4120.018.00.
en
AF-KDF 4
VISU - HOST communication
Manual no.: VHK.4120.018.00.en
Edition: 03/2014
SERVICE - MADE BY HAUNI Translation of the original instructions

AF-KDF 4COP.XXX.0000.051.00.en VHK.4120.018.00.en
Hauni Maschinenbau AG
Universelle Engineering U.N.I. GmbH
Hauni Richmond, Inc.
Hauni Primary GmbH
Sodim SAS
Decouflé s.à.r.l. .
***
Terms of copyright
This document has been written for authorized, qualified personnel. It deals with the product specified in its title and this
product must be installed and operated in strict accordance with the contents of this document.
The manufacturer accepts no responsibility for any changes made to the product by the user. Before doing anything with
the product, therefore, ensure that it corresponds exactly to all the relevant information and specifications contained in this
document. It is in the user’s interest to contact the manufacturer immediately if discrepancies are discovered or if any uncer-
tainty exists in this respect.
The manufacturer stipulates that all relevant national, local and any other pertinent safety regulations are strictly adhered
to in connection with the operation of the product or any work (adjustments, maintenance, repair etc) carried out on the
product itself.
All documents, including those on data carrier, are protected by copyright. They are provided for personal information only.
You are allowed to make printed copies for your own use when using in connection with the contract. Furthermore, the cop-
ying or reproduction of these documents, or any other form of provision whatsoever to third parties is not permitted. By the
same token, using these documents for fabrication purposes without our consent is not permitted either.
For USA only: "Laser licensed by Patlex Corporation under US Patent No. 4.704.583".
COP.X
Copyrights and exploitation rights
All the software products and software documentation contained in our scope of supply are protected by copyright in favour
of Hauni Maschinenbau AG, Kurt-A.-Körber-Chaussee 8-32, 21033 Hamburg, Tel.: +49 40 7250-01, e-mail: info.documen-
tation@hauni.com, Internet: www.hauni.com (hereinafter referred to as Hauni), or the software authors from whom Hauni
COP.XXX.0000.051.00.en
has acquired a licence.
All copyrights and rights of exploitation are the property of Hauni or the property of the software authors. The Licensee shall
observe the copyrights and rights of exploitation and, in particular, is not allowed to erase the notices drawing attention to
copyright.
Rights of use
In consideration for payment of an agreed purchase price (or when the products are delivered at the latest) Hauni grants
the Licensee the non-exclusive, unlimited and non-transferable right to use the software products and their documentation
in accordance with the contract within the Licensee’s company.
The right to use relates to the actual scope of supply in which the software is implemented or to the contractually agreed
scope of use of the software.
The Licensee is not entitled to pass on the software to third parties. The exception is the passing on of integrated software
when selling complete machines provided an indication is given as to the copyrights and rights of exploitation of Hauni or
the software authors.
Duplicating and editing rights
Any duplication of software and documentation requires Hauni’s prior written consent.
The exception from this rule is the making of a backup copy, provided the Licensee adds to it the corresponding copyright
notices shown in the original.
Any editing or altering of the software also requires Hauni’s prior written consent, unless it has been explicitly released for
editing or altering. If software is processed or changed by the Licensee, any warranty claim against Hauni becomes invalid.
Claims in the event of a violation of these provisions
If there is a violation of these provisions Hauni reserves the right to serve notice in respect of the rights of use and to claim
damages.
Licence provisions of the software suppliers
Any further provisions issued by our software suppliers will be submitted to you if applicable.
***
Subject to technical changes without notice.
Last update:
About this manual
About this manualAF-KDF 4VOR.VHK.0000.060.00.en VHK.4120.018.00.en
Persons to whom this man- This manual is intended mainly for software engineers who deal with
ual applies the exchange of data between the VISU system and a host compu-
ter. Data exchange takes place via an Ethernet connection using the
TCP/IP protocol.
Guide The following features are provided to help you locate information in
the manual:
• Tables of contents of the manual.
• Alphabetical index in the Appendix.
• Page header information.
In addition, there are numerous cross-references (↑ ..-... ) where fur-
ther information can be obtained on the same subject.
Documentation package This operating manual is a part of the machine documentation pack-
age. Further documentation includes:
• The electrical circuit diagram.
• The spare parts catalogue.
• The electronics documentation (optional).
VOR.VHK.0000.060.00.en
• Additional operating instructions (technical instructions, docu-

mentation supplied by subcontractors*).
Settings The settings given in the manual are for performing the basic set-
tings on the machine. These basic settings may need to be modified
to suit individual production requirements.
Note!
Before initial commissioning of the machine, make absolutely sure you have read
Chapter 1, "Safety", in the Operating Manual or in the Safety Manual.
Options This manual also describes equipment which may differ from the
equipment actually fitted on your machine. These descriptions are
identified by the words option or optional. These can either be
chargeable options or design-dependent equipment without any
additional costs.
No claims may be derived from the information, illustrations and
descriptions herein.
* Documentation from sub- For further information on individual equipment from subcontractors,
contractors go to the relevant supplier’s home page and call up the appropriate
documentation for the equipment. The exact designation of the
equipment can be found by referring to the circuit diagrams or the
equipment itself.
VOR.VHK.0000.060.00.en
AF-KDF 4 Table of contents
Table of contents
Table of contentsAF-KDF 4generated VHK.4120.018.00.en
1 General definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
2 Host interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Purpose of the host interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 Host interface parameters and data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.2.1 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.2.1.1 TCP/IP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.2.1.2 Socket and buffer parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.2 Service data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.3 Data protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.3.1 Establishing communication and the communication sequence . . . . . 2-7
2.3.2 Frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.4 Commands and events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.4.1 Commands for production data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.4.1.1 "ReadData": Read symbolic addresses . . . . . . . . . . . . . . . . . . . . . . 2-10
2.4.2 Commands for parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.4.2.1 "ReadBrandParameter": Read brand parameter . . . . . . . . . . . . . . . 2-12
2.4.2.2 "WriteBrandParameter": Write brand parameter . . . . . . . . . . . . . . . 2-15
2.4.2.3 "ReadMachineParameter": Read machine parameter. . . . . . . . . . . 2-16
2.4.2.4 "WriteMachineParameter": Write machine parameter . . . . . . . . . . . 2-17
2.4.2.5 "ReadParameter": Read parameter . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
2.4.2.6 "WriteParameter": Write parameter . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
2.4.2.7 "ReadMessageParameter": Read message parameter. . . . . . . . . . 2-21
2.4.2.8 "WriteMessageParameter": Write message parameter . . . . . . . . . . 2-22
2.4.3 Commands for instructions to the VISU system . . . . . . . . . . . . . . . . . . 2-23
2.4.3.1 "ResetShiftData": Reset shift data . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
2.4.3.2 "SetNewBrand": Initiate a brand change . . . . . . . . . . . . . . . . . . . . . 2-23
2.4.3.3 "SetMessage": Set or reset a message in the VISU system . . . . . . 2-24
2.4.4 Event messages from the VISU system to the host computer . . . . . . . 2-25
2.4.4.1 "MailVISUEvent": Report event to host computer . . . . . . . . . . . . . . 2-25
2.4.4.2 "EventProtocolInit": Activate/deactivate event messages . . . . . . . . 2-26
3 Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Network settings under Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
4 Symbol addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 VISU basic system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1.1 ACFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1.2 ACDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1.3 SLVL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.1.4 SANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.1.5 SHIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.1.6 OMSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
VHK.4120.018.00.en i
Table of contents AF-KDF 4
4.1.7 SHFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4.1.8 BRKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2 VISU machine-specific: AF-KDF 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.1 ProductionCounter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.2 ShiftData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.2.3 EMSData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.2.4 AFData. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.2.5 KDFData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
5 General parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
6 Parameters and messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
A Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-i
ii VHK.4120.018.00.en
AF-KDF 4 General definitions
1 General definitions
General definitionsAF-KDF 4K010.VHK.4120.001.00.en VHK.4120.018.00.en
Data types
typedef BOOL BOOLEAN;// 32-bit; 0 - false, <>0 - true

typedef signed char INT8;
typedef signed short INT16;
typedef signed long INT32;
typedef unsigned char BYTE;
typedef unsigned short WORD;
typedef unsigned long DWORD;
typedef float FLOAT;
typedef char STRING;
typedef unsigned long TIME;
typedef unsigned long DATE;
typedef unsigned long TID;
typedef unsigned short BIT;
// In the following structures, the elements are stored in ascending

// order so that they will remain in ascending order
// when mapped to a DWORD.
typedef struct tagDATA_T

{
BYTE Day; // Byte 0
BYTE Month;
WORD Year;
} DATE_T;
typedef struct tagTIME_T

{
BYTE Second; // Byte 0
BYTE Minute;
WORD Hour;
} TIME_T;
typedef struct tagDATETIME_T
K010.VHK.4120.001.00.en 1-1
General definitions AF-KDF 4
{
BYTE Day; // Byte 0
BYTE Month;
WORD Year;
BYTE Hour;
BYTE Minute;
BYTE Second;
} DATETIME_T;
Addresses
Node Function
address address
1 1 VISU basic system
1 2 VISU machine-specific:
KDF4
1 6 PLC
2 51 Drive system
2 55 ODM (optional)
2 56 Pneumatic measuring tube
(optional)
2 99 General PLC
2 150 KDF functions
2 151 Sampling functions
2 160 Debug functions
2 210 AF functions
2 211 Measuring system functions
1-2 K010.VHK.4120.001.00.en
AF-KDF 4 Host interface
2 Host interface
Host interfaceAF-KDF 4K020.VHK.4860.001.02.en VHK.4120.018.00.en
2.1 Purpose of the host interface
Purpose of the host inter- The purpose of the host interface is to connect a machine to a cen-
face tral computer (host computer) via the VISU system and Ethernet
using the TCP/IP protocol.
Communication
i
Host computer → VISU

i The central computer can perform the following functions via this
system connection:
• Read out machine data.
• Read and set parameters.
• Set messages.
• Reset shift data.
• Perform brand changes.
VISU system → host com-

i The VISU system can inform the host computer of the following
puter events occurring in the machine:
• A message has been assigned or cancelled.
• The operator has reset the shift data.
• The operator has performed a brand change.
Network connection
i The VISU system always acts as a server, i.e. a host wanting to
communicate with the VISU must first establish a 'connection' to the
VISU’s service port via a Berkeley socket.
The host computer can communicate with the VISU system using
the data protocol described in section (↑ 2-7). Host interfacing is a
concurrent process which receives commands and events from the
host from the VISU process database and via the network and proc-
esses them.
Characteristics of the host

i • Ethernet interface via onboard Ethernet RJ 45 of VISU-PC.
interface • Communication via the TCP/IP services integrated in Windows
(and therefore all the services supported by Windows such as
DHCP, DNS, WINS, several gateways etc. are supported).
• Setting up the TCP/IP services via the Windows control panel
('network' icon).
The other settings are made via ini files.
• Offering the VISU system’s server services via Berkeley stream
sockets (BSD 4.3) using two fixed port numbers (implemented
with 'Windows Sockets', version 2.0).
• Two host computers can be connected with HVIP via one port
at the same time.
The VISU accesses parameters, messages and events internally.
However, if the host requests production data ('Symbolic addresses'
K020.VHK.4860.001.02.en 2-1
Host interface AF-KDF 4
(↑ 4-1)) or if it manipulates parameter values), the VISU process

database must first request this data from or transfer it to the control
system.
2.2 Host interface parameters and data
This section describes the data model of the host interface.

These include:
• Parameters which can be used to configure the host interface

in the VISU system and
• Status data supplied by the host interface to the VISU screen
and to a symbolic address (connection data, statistical counter,
...).
2.2.1 Settings
The host interface can be configured by assigning a number of

parameters. This configuration has been preset by "Hauni
Maschinenbau AG" for test operation purposes and must be
adjusted to the customer’s network requirements.
There are two groups of settings:
• TCP/IP parameters.
• Socket parameters.
2.2.1.1 TCP/IP parameters
These parameters determine the VISU PC network settings. These

include at least:
• The IP address of the PC and

• The netmask of the network to which the VISU PC is connected
Depending on the installation, other standard functions offered by
Windows (e.g. gateways, DNS, WINS, DHCP) can be used.
The TCP/IP parameters are preconfigured by Hauni for test opera-
tion purposes. They only have to be set once when the machine is
connected to the customer’s Ethernet network. Depending on the
customer’s network structure, they are factory or even machine spe-
cific (depending on whether the IP address is fixed in the VISU sys-
tem or is assigned dynamically via a service such as DHCP or
WINS). Subsequent changes are only required if the customer’s net-
work infrastructure is modified.
2-2 K020.VHK.4860.001.02.en
Whenever one of these parameters is changed, Windows usually

has to be restarted.
The TCP/IP parameters can only be set on the VISU PC via the Win-
dows control panel ('network' icon) using a full keyboard. They can-
not be set via an VISU parameter report.
2.2.1.2 Socket and buffer parameters
Socket parameters These parameters describe the function of the sockets via which a
host computer can connect with the VISU PC. The most important
socket parameter is the port number via which the VISU system
receives connections.
The socket parameters are fixed settings which usually do not need
to be set at the customer’s - they are part of the software design.
In order to allow the socket parameters to be adjusted quickly if
problems arise on site they are set via the haunimmi.ini file. The fol-
lowing settings can be made:
Section: [HostInterface]
General entries:
Entry Settings Meaning

PendingMlpEvents [1 ... 500] Indicates how many VISU events (e.g. fault mes-
sages) to be transferred to the host computer
Default: 200
can be buffered by the host interface per connec-
tion.
BufferRequestQueueEntrys [1 ... 500] Indicates how many buffer requests can be buff-
ered by the buffer handler in a queue.
Default: 100
Logger [ on | off ] Indicates whether after system start the logger in
the host interface window is to be switched on or
Default: on
off by default.
Port configuration entries

(per port):

PortNN [1024 ... 65535] Service port via which host computers can
establish connections.
Default:
1200
1201
KeepAliveNN [ on | off ] Cyclic transfer of 'keep alive' packages to the
host computer.
Default: on
K020.VHK.4860.001.02.en 2-3

CloseGracefulNN [ on | off ] Indicates how a connection is to be closed:
Default: on on (= graceful) - closes the connection at once,
but transfers the contents of the send buffer to
the host in the background.
off (= hard) - closes the connection at once and
deletes the contents of the send buffer.
DontRouteNN [ on | off ] If set to on, the VISU sends the datagrams
directly to the gateway and does not address
Default: off
them within its own network.
SendBufferNN [0 ... 65535] Size of the send buffer in bytes.
Default: 8192
ReceiveBufferNN [0 ... 65535] Size of the receive buffer in bytes.
Default: 8192
Buffer configuration entries

(per buffer type):

BufferSizeNN [24 ... 65526] Size of the buffer of the relevant type to be cre-
ated.
Default:
8192
30
50000
BufferCountNN [1 ... 200] Number of buffers of the relevant type to be cre-
ated.
Default:
4
20
2
Socket number NN 'NN' represents a socket number in the names of the entries. 'NN'
can assume values in the range '00' to '99'. The maximum allowed
are:
• 10 port definitions and
• 10 buffer types (with max. 200 buffers in total).
Minimum requirements At least one port must be configured to allow a host to sign onto the
VISU PC via the network. Furthermore, at least two buffers must be
configured. The buffer must be big enough to store a complete
frame. The host interface cannot handle frames that are bigger than
the biggest buffer configured.
2-4 K020.VHK.4860.001.02.en
If the values set for ports and buffer are invalid, the settings in hau-
nimmi.ini are ignored. The host interface then starts with the default
values.
2.2.2 Service data
The current status of the host interface is made available in two sym-
bolic addresses:
HOST (HOstSTatus) This address contains information on the overall status and the inter-
face parameter settings.
HOCO (HOstCOnnections) This address contains information on the status, the parameter set-
tings and the connection data relating to currently established con-
nections.
The symbolic addresses have the following structure:
Symbolic address: HOST
Offset Type Description

0 BYTE Describes the current status of the interface via the following codes:
0 - A fault has occurred during initialization
1 - Ready to connect
1 BYTE (reserved)
2 TID Text ID no. relating to the text of the current network status.
4 WORD Current network status:
1.. Network ok
2.. TCP/IP or network card not configured
10000 .. 10100.. A Winsock fault has occurred
6 WORD32 IP address of the VISU with network byte order
10 WORD16 Number of port 1 of the VISU.
12 WORD16 Number of port 2 of the VISU.
14 BYTE Number of connections to host computers currently established.
15 BYTE Maximum permitted number of connections to host computers.
16 STRING [16] IP address of the VISU as an ASCII string, in the format "1.2.3.4"
32 STRING [60] Name of the VISU in the DNS (if configured) as an ASCII string
Symbolic address: HOCO HOCO is organized as an array with 8 elements. Each element con-
tains data related to a connection.

0 (see below) Data of connection 0
K020.VHK.4860.001.02.en 2-5

Structure of the data related

to a connection

0 BOOLEAN TRUE (1) if the connection data block is assigned with an active con-
nection, otherwise FALSE (0).
1 BYTE TRUE (1) if the connection data block is assigned with an active con-
nection, otherwise FALSE (0).
2 WORD (Spare)
4 WORD Fault code in the event of a Winsock or protocol fault related to this
connection.
6 WORD32 IP address of the connection’s host computer with network byte
order.
10 WORD16 Number of the connected port.
12 STRING [60] Name of the host computer as an ASCII string, in the format "1.2.3.4"
72 WORD32 Time connection established in seconds since 01.01.1970 at
00:00:00 hrs.
76 WORD16 Protocol settings for events (↑ 2-10):
bit 0:
0 - Do not send event messages to the host.
1 - Send event messages to the host.
78 WORD Number of commands received from the host.
80 WORD Number of protocol or Winsock faults.
82 WORD Number of confirmed commands to the host.
84 WORD Number of event messages sent by the VISU to the host.
86 to 99 BYTE (reserved)
2-6 K020.VHK.4860.001.02.en
2.3 Data protocol
2.3.1 Establishing communication and the communication sequence
Before a host is able to communicate with the VISU system, it must

first establish a connection to the VISU. Connection is established
and communication is performed via Berkeley sockets of BSD 4.3.
The VISU offers its services as a server; the host computer can use
them as a client. Connection is established and communication
takes place as shown in the diagram below:
Client (Host) Server (VISU)
socket ( ) socket ( )
bind ( ) bind ( )
listen ( )
Establishing a
connection
connect ( ) accept ( )
Command
send ( ) recv ( )
Waiting for Processing

acknow-
ledgement Command
Acknowledgement acknowledgement send ( )
Processing
recv ( )
Decoding Event
>> Event
occurred
Waiting for
VISU event Event
send ( )
Processing
Establishing a connection and communication between host computer and VISU

Fig. 1 (3280HSW_000_00.i.00020_000.01.en.cgm)
A host computer can only establish a new connection by creating a

socket, allocating its own IP address and any port number to the
socket and connecting the socket via call connect() to the VISU’s
service port.
The VISU system now checks whether the new connection has
caused the maximum number of connections to be exceeded. If so,
K020.VHK.4860.001.02.en 2-7
it immediately closes the connection by immediately deleting the

associated socket on its side.
Otherwise it accepts the connection. Communication can now be ini-
tiated by both parties:
Host → VISU The host can send commands to the VISU. After sending a com-
mand, it must (!) wait for the acknowledgement ('solicited message')
from the VISU before sending the next command to the VISU.
VISU → Host The VISU can inform the host of events ('unsolicited messages') on
its own account. However, the host is first required to enable event
messages via the 'SetProtocolConfig' command; when connection
is established, this function is switched off in the VISU system by
default (↑ 2-10).
2.3.2 Frame structure
The connection between host and VISU is implemented via stream

sockets. This socket type can transfer a byte stream bidirectionally.
This mechanism does not ensure that a frame transferred using
send() will be received again perfectly in its entirety with a single
recv() command.
The individual frames in the byte stream must therefore be marked
off. The frame type is also important for identification purposes since
it indicates what it is:
• which command,
• which event message or
• which acknowledgement.
So a frame generally has the following structure:

0 WORD16 Length of the frame in bytes (incl. the length indication itself)
2 BYTE Frame type
4 to BYTE [*] Frame data
<frame
length>
The maximum frame length is 65535 (= 64kB-1).

The different frame types are described in the following section
(↑ 2-10).
Unless specified otherwise, the data types WORD16 and WORD32
are represented in reverse byte sequence (Intel byte sequence), i.e.
the low byte is at the smaller address.
2-8 K020.VHK.4860.001.02.en
Commands from the host computer which only supply a confirma-

tion or a fault code with the acknowledgement, are confirmed by the
VISU with the following general receive acknowledgement:

0 WORD16 3 or 5 (length of frame in bytes)
2 BYTE Positive acknowledgement (odd code): Code of the command
Negative acknowledgement (even code): Fault code (see below)
3 WORD32 Optional: With some commands, the number of the first faulty object
(e.g. parameter number) can be returned. The existence of this
option is indicated explicitly by the suffix (<object name>) in the
description of the individual commands.
from 7 BYTE[] Optional: If a read command has several symbolic addresses or sev-
onwards eral parameters, the correctly requested data is sent to the host in the
event of a negative acknowledgement.
The following fault codes are possible:
Code Name Meaning

02H E_UNKNOWN_TYPE Invalid message type
04H E_PARAM_RANGE Parameter out of its value range
06H E_FRAME_LEN Frame length faulty
08H E_NOT_EXECUTED Command not executed
0AH E_UNKNOWN_ERROR Unknown fault
0CH E_PARAM_READ_ONLY Parameter is write protected
10H E_DEVICE_NOT_FOUND No such device
12H E_DEVICE_NOT_CONNECTED Device not available
14H E_ENTRY_NAME Name of symbolic address not found
16H E_ENTRY_OFFSET No such offset
18H E_ENTRY_SIZE Entry too long
20H E_BRAND_ID Unknown brand number
24H E_PARAMETER_ID Unknown parameter number
26H E_FORMAT_ID Unknown parameter format
28H E_PARAMETER_VALUE Parameter was rejected by the machine
K020.VHK.4860.001.02.en 2-9
2.4 Commands and events
2.4.1 Commands for production data
2.4.1.1 "ReadData": Read symbolic addresses
Function This command allows the host to request data from the VISU from
one or more symbolic addresses. The VISU sends the required data
back to the host together with an acknowledgement.
Note!
The VISU usually needs to request the data from the machine on request via OPC.
This process only takes place once per second. The response time for this com-
mand is slowed down accordingly. This does not apply to addresses of the VISU
itself (node address 1, function address 1); these addresses are always returned at
once.
Command structure (Host

→ VISU)

2 BYTE 11H (frame type)
3 to 72 symbAdr Description of the 1st symbolic address requested
73 to symbAdr Description of the 2nd symbolic address requested
142
: : :
symbAdr: Description of a
symbolic address

0 BYTE Node address: 0 ... 255
1 BYTE Function address: 0 ... 255
2 to 65 BYTE [64] Name of symbolic address (with trailing '\0')
66 WORD16 Offset within the symbolic address from which point onward data is
to be read (counting starts at 0)
68 WORD16 Number of bytes that are to be read
(0FFFFH = from the offset to the end of the symbolic address)
Communication test For a communication test the VISU - host interface simulates a sym-
bolic address:
2 - 10 K020.VHK.4860.001.02.en
Node address: 1 (VISU)

Function: 0 ... 255
Name: TEST
Data: 00 01 02 03 ... FE FF 00 01 ...
The data values are automatically generated in the offset range from
0 to 63999 and can thus be requested from the VISU system up to
the maximum frame length.
Positive acknowledgement

sAdrDat Data of the 1st symbolic address requested
sAdrDat Data of the 2nd symbolic address requested
: : :
sAdrDat: Data of a symbolic

address

2 to 65 BYTE [64] Name of symbolic address (with trailing '\0')
66 WORD16 Offset within the symbolic address from which point onward data is
to be read (counting starts at 0)
68 WORD16 Number of bytes that are to be read
(0FFFFH = from the offset to the end of the symbolic address)
from 70 BYTE[] Data of the symbolic address requested
onwards
Negative acknowledge- General receive acknowledgement using one of the return codes
ment (↑ 2-9):
E_DEVICE_NOT_FOUND
E_DEVICE_NOT_CONNECTED
E_ENTRY_NAME
E_ENTRY_OFFSET
E_ENTRY_SIZE
K020.VHK.4860.001.02.en 2 - 11
E_FRAME_LEN

2 BYTE Return code
sAdrDat Optional, if there is a correctly requested symbolic address:
Data of the 1st symbolic address correctly requested
sAdrDat Data of the 2nd symbolic address correctly requested
: : :
2.4.2 Commands for parameters
2.4.2.1 "ReadBrandParameter": Read brand parameter
Function This command allows the host to request the following data from the
VISU:
• the name of a brand and
• the current brand parameter values.
The read brand parameters command returns the parameters which
are configured with the BRAND attribute in the VISU system.
The brand name must always be included in the command. Like-
wise, the brand name is always returned along with the acknowl-
edgement. If an empty string ('\0') is transferred in the brand name,
then the current brand will be read.
A command can be sent without parameter numbers. In this case,
only the brand name without parameter values is returned along with
the acknowledgement.
If 0FFFFFFFFH is given as the first parameter number, all brand
parameters are sent back along with the acknowledgement.
→ VISU)

3 BYTE [40] Brand name (with trailing '\0')
43 WORD32 Number of the 1st parameter requested
(0FFFFFFFFH = all brand parameters)
47 WORD32 Number of the 2nd parameter requested
2 - 12 K020.VHK.4860.001.02.en

: : :

3 to 42 BYTE [40] Brand name (with trailing '\0')
43 pvalue 1st requested parameter
pvalue 2nd requested parameter
: : :
pvalue: Parameter

0 WORD32 Parameter number = kkffnnnn
kk = node address 0 ... 255
ff = function number 0 ... 255
nnnn = parameter no. 00 .. FFFF
4 BYTE Format of the parameter: corresponds to PDB format:
0 - BOOLEAN (=0 - false; <>0 - true) 1 - Boolean
1 - Unsigned byte 5 - unsigned char
2 - Signed byte 2 - signed char
3 - 16 bit word, unsigned 6 - unsigned int
4 - 16 bit integer (signed) 3 - int
5 - 32 bit word, unsigned 7 - unsigned long
6 - 32 bit integer, signed 4 - long
7 - 32 bit real (IEEE format) 8 - float
9 - int * 10
10 - int * 100
11 - int * 1000
8 - Text ID (32 bit TID text ID no.) 16 - TID
9 - Button function (no value) 12 - PushButton
10 - Shift/break StartEndTime 23 - StartEndTime
11 - String with trailing '\0' 13 - String + '\0'
12 - Date 15 - Date
13 - Time 14 - Time
K020.VHK.4860.001.02.en 2 - 13

from 3 BYTE, Current parameter value (depending on
onwards WORD16, the format)
WORD32,
or string +
'\0'
Parameters of PDB type 0 ('format') cannot be read. Although

parameters of type 9 ('button function') can be read out, they do not
have a value.
Host format for date (12) Type DATE_T

Day As Byte 'byte 0
Month As Byte 'byte 1
Year As Integer 'byte 2+3
End Type
Host format for time (13) Type TIME_T

Second As Byte 'byte 0
Minute As Byte 'byte 1
Hour As Integer 'byte 2+3
End Type
Start/end of shift and break Type STARTEND_T

times
hhStart As Byte 'byte 0: Start in hours
mmStart As Byte 'byte 1: Start in minutes
hhEnd As Byte 'byte 2: End in hours
mmEnd As Byte 'byte 3: End in minutes
End Type
ment (↑ 2-9):
E_FRAME_LEN
E_BRAND_ID
E_DEVICE_NOT_FOUND if parameter 1 != FFFF: (<Parameter no.>)
E_PARAMETER_ID if parameter 1 != FFFF: (<Parameter no.>)
E_UNKNOWN_ERROR
2 - 14 K020.VHK.4860.001.02.en

2 BYTE Return code
3 WORD32 Optional: Parameter number
47 pvalue 1st correctly requested parameter
pvalue 2nd correctly requested parameter
: : :
2.4.2.2 "WriteBrandParameter": Write brand parameter
Function This command allows the host to assign new values to one or more
brand parameters in the machine.
With the write brand parameters command, only those parameters
which are configured with the BRAND and OPC_WRITE attributes
in the VISU system can be assigned new values.
If an empty string ('\0') is transferred in the brand name, then the cur-
rent brand will be written.
The structure of the parameter value is identical with the structure of
the parameter values in the acknowledgement of the 'ReadBrand-
Parameter' command (type description pvalue: (↑ 2-13)).
The command is only acknowledged by the VISU system when the
new parameter values have been transferred to the machine via the
bus. All the parameters given in the command are always re-
assigned. If a fault occurs for at least one parameter, the command
is acknowledged using the return code E_PARAMETER_VALUE,
indicating the number of the last faulty parameter.
→ VISU)

43 pvalue 1st parameter to be written
pvalue 2nd parameter to be written
: : :
Acknowledgement General receive acknowledgement. If a fault occurs, the following

return codes (↑ 2-9) can be sent:
K020.VHK.4860.001.02.en 2 - 15
E_FRAME_LEN
E_DEVICE_NOT_FOUND (<Parameter number>)
E_DEVICE_NOT_CONNECTED (<Parameter number>)
E_BRAND_ID
E_PARAMETER_ID (<Parameter number>)
E_FORMAT_ID (<Parameter number>)
E_PARAM_RANGE (<Parameter number>)
E_PARAMETER_VALUE (<Parameter number>)
E_UNKNOWN_ERROR (<Parameter number>)
2.4.2.3 "ReadMachineParameter": Read machine parameter
Function This command allows the host to request the current machine
parameter values from the VISU system.
The read machine parameters command returns the parameters
which are configured with the MACHINE attribute in the VISU sys-
tem.
If 0FFFFFFFFH is given as the first parameter number, all machine
parameters for the unit selected with the function address are sent
back along with the acknowledgement. In all the other cases the
function address given is not evaluated, as the function address is
already included in the parameter number.

→ VISU)

: : :

2 - 16 K020.VHK.4860.001.02.en

pvalue 1st requested parameter
: : :

ment (↑ 2-9):
E_FRAME_LEN
E_PARAMETER_ID (<Parameter number>), the
parameter is not a machine
parameter.

2 BYTE Return code
7 BYTE Optional, if correct parameters are being requested:
Node address: 0 ... 255
Function address: 0 ... 255
pvalue 1st correctly requested parameter
: : :
2.4.2.4 "WriteMachineParameter": Write machine parameter
machine parameters.
K020.VHK.4860.001.02.en 2 - 17
With the write machine parameters command, only those parame-

ters which are configured with the MACHINE and OPC_WRITE
attributes in the VISU system can be assigned new values.
The command is only acknowledged by the VISU system when the
new parameter values have been transferred to the machine via the
bus. All the parameters given in the command are always re-
is acknowledged using the return code E_PARAMETER_VALUE,
indicating the number of the last faulty parameter.

→ VISU)

: : :

E_FRAME_LEN
E_PARAM_READ_ONLY (<Parameter number>)
E_PARAMETER_VALUE (<Parameter number>)
2.4.2.5 "ReadParameter": Read parameter
Function This command allows the host to request the current values for one
or more parameters from the VISU system.
The read parameters command returns the parameters which are
not configured with the MACHINE attribute and not configured with
the BRAND attribute in the VISU system.
2 - 18 K020.VHK.4860.001.02.en
If 0FFFFFFFFH is given as the first parameter number, all parame-

ters are sent back along with the acknowledgement.
The frame structure is identical to that of the 'ReadMachineParam-
eter' command (↑ 2-16).

→ VISU)

: : :

pvalue 1st requested parameter
: : :

ment (↑ 2-9):
E_FRAME_LEN
E_PARAMETER_ID (<Parameter number>), the
parameter is not a general
parameter.
K020.VHK.4860.001.02.en 2 - 19

2 BYTE Return code
Node address: 0 ... 255
Function address: 0 ... 255
pvalue 1st correctly requested parameter
: : :
2.4.2.6 "WriteParameter": Write parameter
parameters.
With the write parameters command, only those parameters which
are configured with the OPC_WRITE attribute in the VISU system
and do not have the MACHINE attribute not the BRAND attribute
can be assigned new values.
All the parameters included in the command are always re-
is acknowledged using the return code E_PARAMETER_ID,
E_PARAM_RANGE or E_PARAM_READ_ONLY, and the number
of the faulty parameter is sent back along with the acknowledge-
ment.
The structure of the parameter values is identical to the structure of
Parameter' command (type description: pvalue: (↑ 2-13)).
→ VISU)

: : :
2 - 20 K020.VHK.4860.001.02.en

E_FRAME_LEN
E_PARAM_READ_ONLY (<Parameter number>)
2.4.2.7 "ReadMessageParameter": Read message parameter
Function This command allows the host to request one or more priorities of
fault and warning messages from the VISU system.
If 0FFFFFFFFH is given as the first message number, the priorities
for all messages relating to the selected function address are sent
back along with the acknowledgement. In all the other cases the
function address is not evaluated, as it is already included in the
parameter number.

→ VISU)

5 WORD32 Number of the 1st fault message requested
9 WORD32 Number of the 2nd fault message requested
: : :

pprio 1st requested message priority
pprio 2nd requested message priority
K020.VHK.4860.001.02.en 2 - 21

: : :
pprio: Structure of a fault

message priority

0 WORD32 Message number
4 BYTE Current priority of the message
ment (↑ 2-9):
E_FRAME_LEN

2 BYTE Return code
9 pprio 1st correctly requested message priority
pprio 2nd correctly requested message priority
: : :
2.4.2.8 "WriteMessageParameter": Write message parameter
priorities of fault and warning messages in the VISU system.
All the message priorities are always re-assigned. If a fault occurs
for at least one message priority, the command is acknowledged
using the return code E_PARAMETER_ID or E_PARAM_RANGE,
and the message number of the faulty message priority is sent back
along with the acknowledgement.
The representation of the fault message priorities in the command
frame is identical with the structure in the acknowledgement of the
'ReadMessageParameter' command (type description pprio:
(↑ 2-22)).
2 - 22 K020.VHK.4860.001.02.en

→ VISU)

pprio 1st new fault message priority
pprio 2nd new fault message priority
: : :

E_FRAME_LEN
2.4.3 Commands for instructions to the VISU system
2.4.3.1 "ResetShiftData": Reset shift data
Function This command allows the host to instruct the VISU system to reset
its shift data. The VISU system then creates a new, empty shift data
buffer. The contents of the oldest shift data buffer are lost.

→ VISU)

0 WORD16 3 (length of frame in bytes)
Positive acknowledgement General receive acknowledgement (always positive).
2.4.3.2 "SetNewBrand": Initiate a brand change
Function This command allows the host to instruct the VISU system to initiate
a brand change.
K020.VHK.4860.001.02.en 2 - 23
After a brand change, certain modifications or settings may have to

be carried out on the machine.

→ VISU)


return code (↑ 2-9) is sent back:
E_BRAND_ID
2.4.3.3 "SetMessage": Set or reset a message in the VISU system
Function This command allows the host to assign or cancel a message in the
VISU system.
For this purpose, up to 128 message numbers in the VISU system
are reserved for the host. These host messages are handled in the
VISU system like typical fault and warning messages and are allo-
cated to the VISU system. They have the following numbers:
Message number Text ID Priority Pre-assigned as ...

cur min. max.
.
001.002.0500 - 1500 - 1547 250 250 254 Note
001.002.0547
001.002.0548 - 1548 - 1579 200 180 249 Warning message
001.002.0579
001.002.0580 - 1580 - 1595 130 120 149 Stop message (program stop)
001.002.0595
001.002.0596 - 1596 - 1611 70 60 89 Stop message (immediate stop)
001.002.0611
001.002.0612 - 1612 - 1727 40 30 59 Stop message (secondary drives off)
001.002.0727
Before a host uses one of these messages in the VISU system, the
relevant texts should be allocated to the corresponding text ID nos.
from the customer dictionary of the basic system (address 001.002).
The messages all have a default priority which the host can change
to a new value via the 'WriteMessageParameter' command.
2 - 24 K020.VHK.4860.001.02.en
By setting a host message with a suitable stop priority, the host can
stop the machine. The VISU system automatically deletes a stop
message when the machine has come to a standstill. This means
that the host does not need to cancel the message.

→ VISU)

7 BYTE Status:
<> 0 - Assign message
= 0 - Cancel message

return code (↑ 2-9) is sent back:
E_PARAM_RANGE
2.4.4 Event messages from the VISU system to the host computer
2.4.4.1 "MailVISUEvent": Report event to host computer
Function The VISU system sends this message to the host at its own initia-
tive, indicating that one of the following events has occurred:
• A stop or warning message has been set or cancelled.
• The operator or a host computer has initiated a shift data reset.
• The operator or a host computer has initiated a brand change.
These messages do not need to be acknowledged by the host com-
puter.
Command structure (VISU

→ Host)

2 BYTE 0F1H (frame type)
K020.VHK.4860.001.02.en 2 - 25

3 BYTE Event type:
0 - Fault/warning message
1 - Shift data reset
2 - Brand change
ev_msg Additional information about the event (only for fault/warning mes-
sages, see below)
ev_msg for fault and warning

messages

4 BYTE Status:
0 - Off
1 - On
2 - On, machine stop initiated (intial message)
5 BYTE Priority of the message
6 WORD32 Text ID no. for the message: kkffnnnn
kk - node address
ff - function address
nnnn - text ID no.
Acknowledgement None
2.4.4.2 "EventProtocolInit": Activate/deactivate event messages
Function This command allows the host to activate or deactivate the event
message in the VISU system via 'MailVISUEvent'. When a connec-
tion has been established, event messages from the VISU system
via 'MailVISUEvent' are initially disabled.
Furthermore, the host can request all the fault and warning mes-
sages currently assigned in the VISU system to enable it to synchro-
nize with the VISU system.
Command structure (VISU

→ Host)

2 - 26 K020.VHK.4860.001.02.en

3 BYTE Event message via "MailVISUEvent" to the host:
= 0 - Off
<> 0 - On
4 BYTE All fault and warning messages currently assigned are reset:
= 0 - No
<> 0 - Yes
Acknowledgement

ev_msg If active messages are requested: 1st active message
ev_msg If active messages are requested: 2nd active message
: : :
The information of the 'ev_msg' type for an active message has the
same structure as described in section ('MailVISUEvent' (↑ 2-25)).
K020.VHK.4860.001.02.en 2 - 27
2 - 28 K020.VHK.4860.001.02.en
AF-KDF 4 Network configuration
3 Network configuration
Network configurationAF-KDF 4K030.VHK.4860.000.00.en VHK.4120.018.00.en
This chapter describes the settings required to connect to a network.

The additional network card on the VISU PC is intended for connec-
tion to the host.
This network is called the "HMI Network".
3.1 Network settings under Windows XP
Procedure ! Click the "Network" icon in the Windows control panel and
install the following protocol:
– Start → Control Panel → Network Connection
– Select and open "HMI Network".
This will bring up the following window:
Fig. 1 (3291_zi_TAE.v.00002_001.00.gif)
– Select "Internet Protocol (TCP/IP)" and click "Properties".
K030.VHK.4860.000.00.en 3-1
Network configuration AF-KDF 4
Fig. 2 (3291_zi_TAE.v.00001_001.00.gif)
– Set "IP Address", "Subnet mask", etc. (in accordance with

the customer network).
– Additional settings may need to be made in accordance with
the customer network.
3-2 K030.VHK.4860.000.00.en
AF-KDF 4 Symbol addresses
4 Symbol addresses
Symbol addressesAF-KDF 4K040.VHK.4120.003.00.en VHK.4120.018.00.en
4.1 VISU basic system
4.1.1 ACFA
// --- Symbolic address ACFA --------------------------------------------- //

// List of currently active fault messages. The currently active stop/warning
// or information message in the message line is at index = 0. Unused entries
// are set to 0.
#define MAX_ACFA_ENTRIES 100 // Max. number of fault messages

typedef struct tagACFA_ENTRY
{
DWORD No; // Message number
DWORD Tid; // Text ID no. for the message
DWORD Priority; // Priority of the message
DWORD Flags; // Message flags: active / req. acknowl.
} ACFA_ENTRY;
typedef struct tagACFA

{
DWORD Index; // Number of entries
ACFA_ENTRY Message[MAX_ACFA_ENTRIES]; // Stop/warning/information messages
} ACFA;
4.1.2 ACDI
// --- Symbolic address ACDI --------------------------------------------- //

// Currently active stop in the initial message line. If no message is active,
// all elements are set to 0.
typedef struct tagACDI

{
K040.VHK.4120.003.00.en 4-1
Symbol addresses AF-KDF 4
DWORD No; // Message number

DWORD Tid; // Text ID no. for the message
DWORD Pri; // Priority of the message
} ACDI;
4.1.3 SLVL
// --- Symbolic address SLVL --------------------------------------------- //

// Setpoint and actual node list
// Bit code per node:

#define SLVL_NodeSetpoint 0 // Bit = 0: Setpoint node connected
#define SLVL_NodeConnected 1 // Bit = 1: Actual value node connected
#define SLVL_ParInconsist 2 // Bit = 2: Node parameters inconsistent
#define SLVL_DataTransfer 3 // Bit = 3: Data transfer permitted
#define SLVL_OPCConnecting 4 // Bit = 4: OPC connection is being established
#define SLVL_OPCConnected 5 // Bit = 5: Connected to the OPC server
#define SLVL_NodeAvailable 6 // Bit = 6: Node configuration exists
#define SLVL_ReadingNodeConfiguration 7 // Bit = 7: Node configuration is being read
typedef struct tagSLVL // List of nodes

{
DWORD Node[MAX_NODEID+1]; // Node information
} SLVL;
4.1.4 SANA
// --- Symbolic address SANA --------------------------------------------- //

// The symbolic address SANA includes the stop analysis of the machine.
#define MAX_SANA_ENTRIES 100
#define INTERNAL_STOP 0 // Machine stops

#define EXTERNAL_STOP 1 // Other stops
4-2 K040.VHK.4120.003.00.en
typedef struct tagSANA_ENTRY

{
DWORD No; // Stop number
DWORD Tid; // Text ID no. of the stop
DWORD Count; // Stop count
DWORD SType; // Type of stop: internal/external
DWORD Downtime; // Downtime [sec]
} SANA_ENTRY;
typedef struct tagSANA

{
SANA_ENTRY Lst [MAX_SANA_ENTRIES]; // List of stops
} SANA;
The addresses SAN1, SAN2 and SAN3 contain the data for the pre-
vious three shifts.
4.1.5 SHIS
// --- Symbolic address SHIS --------------------------------------------- //

// The symbolic address SHIS includes the stop history of the machine.
#define MAX_SHIS_ENTRIES 200
typedef struct tagSHIS_ENTRY

{
DWORD No; // Stop number
DWORD Tid; // Text ID no. of the stop
DWORD StartTime; // Start of stop [sec]
DWORD EndTime; // End of stop [sec]
DWORD Downtime; // Downtime [sec]
DWORD OrgNo; // Original stop number if stop overwritten
DATETIME_T StartTimeX; // Extended Version of Starttime
K040.VHK.4120.003.00.en 4-3
DATETIME_T EndTimeX; // Extended Version of Endtime

} SHIS_ENTRY;
typedef struct tagSHIS

{
DWORD analysis; // TRUE: Stop recorded by analysis
SHIS_ENTRY Lst // List of all stops
[MAX_SHIS_ENTRIES];
} SHIS;
The addresses SHIS1, SHIS2 and SHIS3 contain the data for the
previous three shifts.
4.1.6 OMSC
// --- Symbolic address OMSC --------------------------------------------- //

// The following structure contains data on the production time and stop time
// of the machine. The address is shift-dependent.
typedef struct tagOMSC

{
DWORD ShiftTime; // Current shift time [sec]
DWORD BreakTime; // Current break time [sec]
DWORD ProductionTime; // Current production time [sec]
DWORD TotalStopCount; // Number of stops;
DWORD TotalStopTime; // Stop time (internal/external total) [sec]
DWORD InternalStopTime; // Stop time (internal reasons) [sec]
DWORD ExternalStopTime; // Stop time (external reasons) [sec]
DWORD ShiftStart; // Start of the current shift
DWORD RunTime; // Runtime in the current shift [sec]
DWORD OpmProduction; // Opmode production

DWORD OpmWaitingStatus; // Opmode waiting status
DWORD OpmRepair; // Opmode repair
4-4 K040.VHK.4120.003.00.en
DWORD OpmMaintenance; // Opmode maintenance / overhaul

DWORD OpmTest; // OpMode Test / Modification
DWORD OpmCleanup; // Opmode clean up
DWORD OpmStandStill; // Opmode standstill
DWORD InternalStopCount; // Number of internal Stops

DWORD ExternalStopCount; // Number of external Stops
DWORD AverageRuntime; // Average Runtime between Stops

} OMSC;
The addresses OMSC1, OMSC2 and OMSC3 contain the data for
the previous three shifts.
4.1.7 SHFT
// --- Symbolic address SHFT --------------------------------------------- //

// The following structures store the shift times (Sunday = 0,
// ..., Saturday = 6). The times are entered in seconds since Sunday,
// 0 hrs. If the start time and end time are both 0,
// then the entry is not defined.
#define SHIFTS_PER_DAY 4 // Number of shifts per day
typedef struct tagTIME

{
DWORD Start; // Start [sec]
DWORD End; // End [sec]
} TIME;
typedef struct tagSHFT

{
TIME Shift[7][SHIFTS_PER_DAY]; // Shift times in a week
} SHFT;
K040.VHK.4120.003.00.en 4-5
4.1.8 BRKT
// --- Symbolic address BRKT --------------------------------------------- //

// The following structures store the break times (Sunday = 0,
// ..., Saturday = 6). The times are entered in seconds since Sunday,
// 0 hrs. If the start time and end time are both 0,
// then the entry is not defined.
#define BREAKS_PER_SHIFT 3 // Number of breaks per shift

typedef struct tagBRKT
{
TIME Break[7][SHIFTS_PER_DAY] // Break times in a week
[BREAKS_PER_SHIFT];
} BRKT;
4.2 VISU machine-specific: AF-KDF 4
4.2.1 ProductionCounter
// --- Symbolic address "ProductionCounter" ---------------------------------------- //

// The following structure stores production data. The address is shift-dependent.
The addresses ProductionCounter1, ProductionCounter2 and

ProductionCounter3 contain the data for the previous three shifts.
typedef struct tagProductionCounter

{
DWORD TotalProduction; // Total production [1000 Fil]
DWORD TotalWasteCount; // Total waste [Fil]
float TotalWastePercent; // Total waste [%]
DWORD ProductionTarget; // Production target [1000 Fil]
DWORD ProductionEstimation; // Production estimation [1000 Fil]
DWORD MFM_Production; // Production [Fil]
{
} ProductionCounter;
4-6 K040.VHK.4120.003.00.en
4.2.2 ShiftData
// --- Symbolic address "ShiftData. .." -----------------------

// The following structure stores production data. The address is shift-dependent.
// The symbolic address offset always starts at 0.
Addresses ShiftData1. ..., ShiftData2. .. and ShiftData3. .. contain

the data for the three most recent shifts.
Name of the symbol address Data type Lengt Description

h
ShiftData.ShiftNo DWORD 4 Shift number
ShiftData.Date DWORD 4 Date
ShiftData.BrandName STRING 41 Cur. brand name
ShiftData.MachineName STRING 41 Machine name
ShiftData.ShiftStart DWORD 4 Start of the current shift
ShiftData.ShiftTime DWORD 4 Shift time [sec]
ShiftData.BreakTime DWORD 4 Break time [sec]
ShiftData.RunTime DWORD 4 Run time in the current shift [sec]
ShiftData.StopTime DWORD 4 Stop time (internal/external total)
[sec]
ShiftData.Stop.Cnt DWORD 4 Number of stops
ShiftData.EffMachineT FLOAT 4 Machine efficiency (time-based)
ShiftData.EffProductionT FLOAT 4 Production efficiency (time-based)
ShiftData.EffMachineP FLOAT 4 Machine efficiency (percent)
ShiftData.EffProductionP FLOAT 4 Production efficiency (percent)
ShiftData.TotalWaste.Cnt DWORD 4 Total waste (counter)
ShiftData.TotalWaste.Pct FLOAT 4 Total waste (percent)
ShiftData.ProdCounter.Cnt DWORD 4 Production counter
ShiftData.BobbinCounter.Cnt DWORD 4 Bobbin counter
Data for software version 1256972_020_xx

i

h
ShiftData.TotalWaste.Cnt DWORD 4 Total waste (counter)
ShiftData.TotalWaste.Pct FLOAT 4 Total waste (percent)
ShiftData.OpenRodWaste.Cnt DWORD 4 Waste: open rod (counter)
K040.VHK.4120.003.00.en 4-7

h
ShiftData.OpenRodWaste.Pct FLOAT 4 Waste: open rod (percent)
ShiftData.StartUpWaste.Cnt DWORD 4 Start-up waste (counter)
ShiftData.StartUpWaste.Pct FLOAT 4 Start-up waste (percent)
ShiftData.StopWaste.Cnt DWORD 4 Stop waste (counter)
ShiftData.StopWaste.Pct FLOAT 4 Stop waste (percent)
ShiftData.SpliceWaste.Cnt DWORD 4 Splice waste (counter)
ShiftData.SpliceWaste.Pct FLOAT 4 Splice waste (percent)
i Data for software version 1256972_021.xx

h
ShiftData.Waste.total.Cnt DWORD 4 Total waste (counter)
ShiftData.Waste.total.Pct FLOAT 4 Total waste (percent)
ShiftData.Analysis.OpenRod.Cnt DWORD 4 Waste: open rod (counter)
ShiftData.Analysis.OpenRod.Pct FLOAT 4 Waste: open rod (percent)
ShiftData.Analysis.StartUp.Cnt DWORD 4 Start-up waste (counter)
ShiftData.Analysis.StartUp.Pct FLOAT 4 Start-up waste (percent)
ShiftData.Analysis.Stop.Cnt DWORD 4 Stop waste (counter)
ShiftData.Analysis.Stop.Pct FLOAT 4 Stop waste (percent)
ShiftData.Analysis.Splice.Cnt DWORD 4 Splice waste (counter)
ShiftData.Analysis.Splice.Pct FLOAT 4 Splice waste (percent)
ShiftData.Analysis.GlueFault1.Cnt DWORD 4 Splice waste (counter)
ShiftData.Analysis.GlueFault1.Pct FLOAT 4 Splice waste (percent)
4.2.3 EMSData
Note!
When connecting to QMU, observe that the interface converter also has an Ether-
net address at the ADAM 4571. If the interface converter is connected to the HMI
network (hub A330) this Ethernet address must also be adapted.
Please refer to Software Installation Instructions PS.4120.XXX.XX for details.
It does not need to be adapted if the interface converter is connected to the control
network (hub A333).
Node 002; function 211
4-8 K040.VHK.4120.003.00.en
Displayed in report R100_002_211

h
ShiftStatisticDataOutOfSpecCount INT32 4 Counter, filter waste,
current shift
ShiftStatisticDataOutOfSpecCount1 INT32 4 Counter, filter waste,
shift -1
shift -2
shift -3
ShiftStatisticDataQualityOutOfSpecDiamStdDev INT32 4 Counter, diameter
waste, standard devia-
tion, current shift
ShiftStatisticDataQualityOutOfSpecDiamStdDev1 INT32 4 Counter, diameter
tion, shift -1
tion, shift -2
tion, shift -3
ShiftStatisticDataQualityOutOfSpecPDMean INT32 4 Counter, pressure
drop waste, mean,
current shift
ShiftStatisticDataQualityOutOfSpecPDMean1 INT32 4 Counter, pressure
drop waste, mean,
shift -1
drop waste, mean,
shift -2
drop waste, mean,
shift -3
ShiftStatisticDataQualityOutOfSpecDiamMean INT32 4 Counter, diameter
waste, mean, current
shift
ShiftStatisticDataQualityOutOfSpecDiamMean1 INT32 4 Counter, diameter
waste, mean, shift -1
K040.VHK.4120.003.00.en 4-9

h

h
PressureDropEMSSingle_Value FLOAT 4 Last single value from
EMS, pressure drop
DiameterEMSSingle_Value FLOAT 4 Last single value from
EMS, diameter
CircumferenceEMSSingle_Value FLOAT 4 Last single value from
EMS, circumference
WeightEMSSingle_Value FLOAT 4 Last single value from
EMS, weight
PressureDropEMSStdDevSpec_Value FLOAT 4 Pressure drop waste
mean
DiameterEMSMeanSpec_Value FLOAT 4 Diameter waste mean
CircumferenceEMSMeanSpec_Value FLOAT 4 Circumference waste
mean
WeightEMSMeanSpec_Value FLOAT 4 Weight waste mean
PressureDropEMSStdDevSpec_Value FLOAT 4 Pressure drop waste
standard deviation
DiameterEMSStdDevSpec_Value FLOAT 4 Diameter waste stand-
ard deviation
CircumferenceEMSStdDevSpec_Value FLOAT 4 Circumference waste
standard deviation
WeightEMSStdDevSpec_Value FLOAT 4 Weight waste stand-
ard deviation
PressureDropEMSMeanStop_Value FLOAT 4 Pressure drop stop
limit mean
DiameterEMSMeanStop_Value FLOAT 4 Diameter stop limit
mean
CircumferenceEMSMeanStop_Value FLOAT 4 Circumference stop
limit mean
WeightEMSMeanStop_Value FLOAT 4 Weight stop limit mean
PressureDropEMSStdDevStop_Value FLOAT 4 Pressure drop stop
limit standard devia-
tion
4 - 10 K040.VHK.4120.003.00.en

h
DiameterEMSStdDevStop_Value FLOAT 4 Diameter stop limit
standard deviation
CircumferenceEMSStdDevStop_Value FLOAT 4 Circumference stop
tion
WeightEMSStdDevStop_Value FLOAT 4 Weight stop limit
standard deviation
PressureDropEMSSingle_ValuePa FLOAT 4 Last single value from
EMS, pressure drop
(Pascal)
PressureDropEMSMeanSpec_ValuePa FLOAT 4 Pressure drop waste
mean (Pascal)
PressureDropEMSStdDevSpec_ValuePa FLOAT 4 Pressure drop waste
standard deviation
(Pascal)
PressureDropEMSMeanStop_ValuePa FLOAT 4 Pressure drop stop
limit mean (Pascal)
PressureDropEMSStdDevStop_ValuePa FLOAT 4 Pressure drop stop
tion (Pascal)
EMS_DMshortTermMeanValue FLOAT 4 Short-term mean of
EMS diameter control-
ler
EMS_DMlongTermMeanValue FLOAT 4 Long-term mean of
ler
EMS_CFshortTermMeanValue FLOAT 4 Short-term mean of
ler (converted to cir-
cumference)
EMS_CFlongTermMeanValue FLOAT 4 Long-term mean of
ler (converted to cir-
cumference)
EMS_PDshortTermMeanValue FLOAT 4 Mean EMS pressure
drop short-term con-
troller
EMS_PDlongTermMeanValue FLOAT 4 Mean EMS pressure
drop long-term control-
ler
EMS_arrayIndexForVISU_long INT16 2 Index for long-term
controller data
K040.VHK.4120.003.00.en 4 - 11

h
EMS_arrayIndexForVISU_short INT16 2 Index for short-term
controller data
EMS_DMAdjPlus BYTE 1 Controller response:
increase diameter
EMS_DMAdjMinus BYTE 1 Controller response:
reduce diameter
EMS_PDAdjPlus BYTE 1 Controller response:
increase pressure
EMS_PDAdjMinus BYTE 1 Controller response:
reduce pressure
EMS_longTermControllerEnable BYTE 1 Long-term controller
enabled
EMS_shortTermControllerEnable BYTE 1 Short-term controller
enabled
EMS_PDshortTermMeanValuePa FLOAT 4 Mean EMS pressure
drop short-term con-
troller (Pascal)
EMS_PDlongTermMeanValuePa FLOAT 4 Mean EMS pressure
drop long-term control-
ler (Pascal)
Name of the symbol address Offset Data type Lengt Description

h
EMSreceiveBuffer 2 INT16 2 EMS receive buffer.
Counter, counts the
data the KDF receives
from the EMS.
EMSreceiveBuffer 129 INT16 2 EMS ID no.
EMSreceiveBuffer 37 INT16 2 Measurement data no.
EMSreceiveBuffer 31 INT16 2 Last information
received from EMS,
hour
received from EMS,
minute
received from EMS,
second
4 - 12 K040.VHK.4120.003.00.en

h
received from EMS,
day
received from EMS,
month
received from EMS,
year
EMSreceiveBuffer 16, bit 0 BIT BIT The last data packet
received contains new
measured values
EMSreceiveBuffer 6, bit 0 BIT BIT Measuring mode on
signal
EMSreceiveBuffer 7, bit 0 BIT BIT Filter rod request sig-
nal
EMSsendBuffer 0 INT16 2 KDF send buffer.
Counter, counts the
data the KDF sends to
the EMS.
ET200Out_1_KDF 6, bit 5 BIT BIT Signal: Production in
progress
ET200Out_1_KDF 6, bit 6 BIT BIT Signal: KDF opera-
tional
ET200Out_1_KDF 16, bit 6 BIT BIT Sensor B15
ET200Out_1_KDF 16, bit 7 BIT BIT Sensor B16

h
ovalitytSingleValueExtern FLOAT 4 Last single value from
EMS, ovality
ovalitytMeanValueExtern FLOAT 4 Mean value, ovality
ovalityDevValueExtern FLOAT 4 Standard deviation,
ovality

Manual setting
EMS results
K040.VHK.4120.003.00.en 4 - 13
Note!
Pressure drop values are displayed in mmWG or Pa, depending on parameter
002.211.0249.

h
EMSGroupSamplingBufferVISU 231 INT16 2 Manual setting results,
sample size
time, hour
time, minute
time, second
time, day
time, month
time, year
EMSGroupSamplingBufferVISU 131 FLOAT 4 Manual setting results,
pressure drop mean
pressure drop stand-
ard deviation
pressure drop change
pressure drop min
pressure drop max
diameter mean
diameter standard
deviation
diameter change
diameter min
4 - 14 K040.VHK.4120.003.00.en

h
diameter max
weight mean
weight standard devia-
tion
weight change
weight min
weight max
roundness mean
roundness standard
deviation
roundness change
roundness min
roundness max
circumference mean
circumference stand-
ard deviation
circumference change
circumference min
circumference max

Automatic setting
EMS single filter measurement data, n = number of filters, n = 0...9
K040.VHK.4120.003.00.en 4 - 15
Note!
002.211.0249.

h
EMSExtBufferVISU n*31 INT16 2 Automatic setting sin-
gle value, time, hour
gle value, time, minute
gle value, time, sec-
ond
gle value, time, day
gle value, time, month
gle value, time, year
EMSExtBufferVISU n*39 FLOAT 4 Automatic setting sin-
gle value, pressure
drop
gle value, diameter
gle value, weight
gle value, roundness
gle value, circumfer-
ence

Automatic setting
EMS results for 10 filters
Note!
002.211.0249.
4 - 16 K040.VHK.4120.003.00.en

h
EMSresultExtBufferVISU 239 INT16 2 Automatic setting
results, time, hour
results, time, minute
results, time, second
results, time, day
results, time, month
results, time, year
EMSresultExtBufferVISU 131 FLOAT 4 Automatic setting
results, pressure drop
mean
standard deviation
min
max
results, diameter
mean
results, diameter
standard deviation
results, diameter min
results, diameter max
results, weight mean
results, weight stand-
ard deviation
K040.VHK.4120.003.00.en 4 - 17

h
results, weight min
results, weight max
results, roundness
mean
results, roundness
standard deviation
results, roundness min
results, roundness
max
results, circumference
mean
standard deviation
min
max

h
DMCFqualityReport array of 480 Mean, standard devia-
FLOAT tion for quality report,
diameter or circumfer-
ence, last 10h
WTqualityReport array of 480 Mean, standard devia-
weight, last 10h
4 - 18 K040.VHK.4120.003.00.en

h
PDqualityReport array of 480 Mean, standard devia-
pressure drop, last
10h
DMCFqualityReport_1h array of 480 Mean, standard devia-
diameter or circumfer-
ence, last 1h
WTqualityReport_1h array of 480 Mean, standard devia-
weight, last 1h
PDqualityReport_1h array of 480 Mean, standard devia-
pressure drop, last 1h
PDPaqualityReport array of 480 Mean, standard devia-
pressure drop, last
10h (Pascal)
PDPaqualityReport_1h array of 480 Mean, standard devia-
pressure drop, last 1h
4.2.4 AFData

h
V0SpeedMMin INT16 2 Speed V0 in m/min
actRatioV1Vkdf FLOAT 4 Current V1 / V KDF ratio
RatioV2V1 FLOAT 4 Current V2 / V1 ratio
K040.VHK.4120.003.00.en 4 - 19

h
shutterPositionIn_mm FLOAT 4 Shutter position in mm
PLZPressure INT16 2 Plasticizer pressure
powerNozzle1 INT16 2 Power nozzle 1
powerNozzleMean INT16 2 Mean power
PLZTemperature INT16 2 Plasticizer temperature
tongueAir1 FLOAT 4 Garniture tongue air 1, optional
tongueAir2 FLOAT 4 Garniture tongue air 2, optional
V0Pressure FLOAT 4 Contact pressure V0
AFtransportAir FLOAT 4 Conveying air in %
4.2.5 KDFData

h
KnifeAdvancesCurrent INT16 2 Actual value remaining knife
advances
MachineSpeed Fil INT32 4 Actual value speed display fil/min
MachineSpeed in metres INT16 2 Actual value speed display
metres/min
SglContainerTempActual INT16 2 Actual value seam glue tank temper-
ature
SglHotmeltChamberTempActual INT16 2 Actual value seam glue hot-melt
chamber temperature
SglPumpTempActual INT16 2 Actual value seam glue pump tem-
perature
SglHoseTempActual INT16 2 Actual value seam glue hose temper-
ature
4 - 20 K040.VHK.4120.003.00.en

h
SglNozzleTempActual INT16 2 Actual value seam glue gun temper-
ature
PlugwrapHeatTempActual INT16 2 Actual value plugwrap heater tem-
perature
PreHeatingTempActual INT16 2 Actual value pre-heater temperature
MeasuringTubeTempActual INT16 2 Actual value measuring tube heater
temperature
SeamSealerTempActual INT16 2 Actual value seam sealer tempera-
ture
IglContainerTempActual INT16 2 Actual value inner glue tank temper-
ature
IglHotmeltChamberTempActual INT16 2 Actual value inner glue hot-melt
chamber temperature
IglPump1TempActual INT16 2 Actual value inner glue pump 1 tem-
perature
IglHose1TempActual INT16 2 Actual value inner glue hose 1 tem-
perature
IglNozzle1TempActual INT16 2 Actual value inner glue gun 1 tem-
perature
IglHose2TempActual INT16 2 Actual value inner glue hose 2 tem-
perature
IglNozzle2TempActual INT16 2 Actual value inner glue gun 2 tem-
perature
GarnitureBedTempActual INT16 2 Actual value garniture bed tempera-
ture
SglActualAmount INT16 2 Setpoint seam glue feed rate
GunInglActualAmount INT16 2 Setpoint inner glue feed rate
K040.VHK.4120.003.00.en 4 - 21
4 - 22 K040.VHK.4120.003.00.en
AF-KDF 4 General parameters
5 General parameters
General parametersAF-KDF 4K050.VHK.4860.001.00.en VHK.4120.018.00.en
i Read/write shift and break times
Note!
A shift change-over takes 5 seconds. VISU parameters (node 1, function 1) can
only be read again when change-over has taken place.
Structures of the start/end

i
of shift and break times
Type STARTEND_T
hhStart As Byte 'byte 0: Start in hours
mmStart As Byte 'byte 1: Start in minutes
hhEnd As Byte 'byte 2: End in hours
mmEnd As Byte 'byte 3: End in minutes
End Type
i Structures of data and time Time in seconds that has expired since 00:00:00 Greenwich time
from 1 January 1970.
With an offset of plus 4 hours in summer time and plus 5 hours in
winter time.
Host format for date
i
Type DATE_T
Day As Byte 'byte 0
Month As Byte 'byte 1
Year As Integer 'byte 2+3
End Type
Host format for time

i
Type TIME_T
Second As Byte 'byte 0
Minute As Byte 'byte 1
Hour As Integer 'byte 2+3
End Type
K050.VHK.4860.001.00.en 5-1
General parameters AF-KDF 4
5-2 K050.VHK.4860.001.00.en
AF-KDF 4 Parameters and messages
6 Parameters and messages

Parameters and messagesAF-KDF 4K060.VHK.0000.000.00.en VHK.4120.018.00.en
PARAMS.LST file The PARAMS.LST file is a text file in which all the parameters and
messages of the machine are listed.
Creating the file When the machine and brand parameters are backed up, a backup
directory is created on the target data carrier (e.g. memory stick).
The directory name is the same as the machine.
• \"Machine directory"_Backup_"Machine name"
The PARAMS.LST file can be found in this directory after the data
has been backed up.
Opening the file A Unicode-compatible editor must be used so that Asian characters
are also displayed correctly when opening the PARAMS.LST file.
We recommend you use Microsoft Word, but a simple editor like
Notepad may also be sufficient.
K060.VHK.0000.000.00.en 6-1
Parameters and messages AF-KDF 4
6-2 K060.VHK.0000.000.00.en
AF-KDF 4 Index
A Index
B
IndexAF-KDF 4generated VHK.4120.018.00.en
Berkeley socket 2-7 Frame 2-4, 2-4

Buffer parameters 2-3 Frame structure 2-8
C H
Central computer (host) 2-1 HAUNIMMI.INI 2-3
Client 2-7 Host 2-1
Commands Host interface 2-1
ReadBrandParameter 2-12
ReadData 2-10 M
ReadMachineParameter 2-16
ReadMessageParameter 2-21 Making line processor 2-1
ReadMlpParameter 2-18
ResetShiftData 2-23 P
SetMessage 2-24 Port 2-4
SetNewBrand 2-23
SetProtocolConfig 2-8 Port number 2-3
WriteBrandParameter 2-15
WriteMachineParameter 2-17 R
WriteMessageParameter 2-22
Read/write shift and break times 5-1
WriteMlpParameter 2-20
Communication 2-7 S
E Server 2-7
Socket parameters 2-3
Establishing connection 2-7
Solicited message 2-8
Ethernet 2-1
Events T
EventProtocolInit 2-26
MailMlpEvent 2-25 TCP/IP 2-1
Parameters 2-2
F
U
Fault codes 2-9
Unsolicited message 2-8
VHK.4120.018.00.en A-i
Index AF-KDF 4
A - ii VHK.4120.018.00.en

VHK.4120.018.00.en: Af-Kdf 4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VHK.4120.018.00.en: Af-Kdf 4

Uploaded by

Copyright:

Available Formats

VHK.4120.018.00.

SERVICE - MADE BY HAUNI Translation of the original instructions

• Additional operating instructions (technical instructions, docu-

1 General definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

2 Host interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 Symbol addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1.7 SHFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

5 General parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

6 Parameters and messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

typedef BOOL BOOLEAN;// 32-bit; 0 - false, <>0 - true

// In the following structures, the elements are stored in ascending

typedef struct tagDATA_T

typedef struct tagTIME_T

typedef struct tagDATETIME_T

2.1 Purpose of the host interface

Host computer → VISU

VISU system → host com-

Characteristics of the host

(↑ 4-1)) or if it manipulates parameter values), the VISU process

2.2 Host interface parameters and data

This section describes the data model of the host interface.

• Parameters which can be used to configure the host interface

The host interface can be configured by assigning a number of

2.2.1.1 TCP/IP parameters

These parameters determine the VISU PC network settings. These

• The IP address of the PC and

Whenever one of these parameters is changed, Windows usually

2.2.1.2 Socket and buffer parameters

Entry Settings Meaning

Port configuration entries

Entry Settings Meaning

Entry Settings Meaning

Buffer configuration entries

Entry Settings Meaning

2.2.2 Service data

Offset Type Description

Offset Type Description

Offset Type Description

Structure of the data related

Offset Type Description

2.3 Data protocol

2.3.1 Establishing communication and the communication sequence

Before a host is able to communicate with the VISU system, it must

Client (Host) Server (VISU)

Waiting for Processing

Establishing a connection and communication between host computer and VISU

A host computer can only establish a new connection by creating a

it immediately closes the connection by immediately deleting the

2.3.2 Frame structure

The connection between host and VISU is implemented via stream

Offset Type Description

The maximum frame length is 65535 (= 64kB-1).

Commands from the host computer which only supply a confirma-

Offset Type Description

The following fault codes are possible:

Code Name Meaning

2.4 Commands and events

2.4.1 Commands for production data

2.4.1.1 "ReadData": Read symbolic addresses

Command structure (Host

Offset Type Description

Offset Type Description