Sartorius Manual Dcu-Host Interface 1 - 6

INTERFACE DESCRIPTION
DCU - DFC ' HOST
CHANGE HISTORY
VERSION DATE NAME CHANGES
1.5 12.05.03 F. Guthof Ethernet interface
1.6 05.07.05 F. Guthof New Commands : SI, PT, SP, SR, ST

DCU-DFC-Host Interface
Interface Description Host ' Substation
Contents
1 GENERAL.....................................................................................................................4
2 PREREQUISITS FOR DATA TRANSMISSION ........................................................................5
2.1 TRANSMISSION CONTROL VIA HOST COMPUTER .................................................................. 5
2.2 SUBSTATION INITIALIZATION .............................................................................................. 5
2.3 BREAK-GENERATION VIA HOST SYSTEM (RS422, RS232 ONLY) ........................................ 6
2.4 REMOTE MODE ................................................................................................................. 6
2.5 RESERVED CONTROL CHARACTER ..................................................................................... 6
2.6 TELEGRAMM FORMAT ........................................................................................................ 7
2.7 TABLE NUMBERS ............................................................................................................... 8
2.8 RANGE OF VALUES FOR DATA TRANSMISSION FIELDS .......................................................... 8
2.9 RESPONSE TELEGRAMMS OF SUBSTATIONS ....................................................................... 8
2.10 TMEOUT AND REPETITION ............................................................................................... 9
2.11 END OF DATA TRANSMISSION........................................................................................ 10
2.12 DATA SECURITY ........................................................................................................... 10
2.13 CHECK SUM................................................................................................................. 10
2.14 BLOCK TRANSMISSION ................................................................................................. 10
3 TRANSMISSION VOLUME AND DEFINITION OF DATA FIELDS ...............................................11
3.1 STATUS DEFINITION DIRECTION: HOST Ù SUBSYSTEM ................................................... 11
3.2 OPERATING MODES HOST Ù SUBSYSTEM ..................................................................... 12
3.3 PROCESS VALUES HOST Õ SUBSYSTEM ....................................................................... 12
3.4 ALARM PARAMETERS PROCESS VALUES HOST Ù SUBSYSTEM ........................................ 12
3.5 ALARM CONDITIONS PROCESS VALUES HOST Õ SUBSYSTEM .......................................... 13
3.6 PROCESS VALUE TOTALIZER HOST Ö SUBSYSTEM ......................................................... 13
3.7 CONTROLLER HOST Ù SUBSYSTEM ............................................................................... 14
3.8 DIGITAL INPUT HOST Õ SUBSYSTEM .............................................................................. 16
3.9 ALARM PARAMETER DIGITAL INPUT HOST Ù SUBSYSTEM ............................................... 16
3.10 DIGITAL OUTPUT HOST Ù SUBSYSTEM ....................................................................... 16
3.11 DCU-MESSAGES HOST Õ SUBSYSTEM ....................................................................... 17
3.12 DCU-LOGBOOK HOST Õ SUBSYSTEM ...................................................................... 18
3.13 EXTENDED ALARM PARAMETER DIGITAL INPUT HOST Ù SUBSYSTEM .......................... 19
3.14 USER-LOGGING HOST Õ SUBSYSTEM ......................................................................... 20
3.15 SEQUENCE MODE HOST Ù SUBSYSTEM ..................................................................... 21
3.16 SEQUENCE SETPOINTS HOST Ö SUBSYSTEM .............................................................. 22
3.17 SEQUENCE REQUEST HOST Ù SUBSYSTEM ............................................................... 23
3.18 SEQUENCE PARAMETER HOST Ù SUBSYSTEM............................................................ 24
- 1.6 05.07.05 F. Guthof

A File: Page 2
U:\dcu_sys\engin_service\DCU-Host Protocol\manual dcu-host interface 1.6.doc
B of 40
3.19 SEQUENCE STEPS HOST Õ SUBSYSTEM ..................................................................... 25

3.20 RECIPE MODE HOST Ö SUBSYSTEM ........................................................................... 26
4 COMMANDS ...............................................................................................................27
4.1 DCU INITIALIZATION HOST Ö SUBSYSTEM ..................................................................... 28
4.2 PROCESS DATA REQUEST HOST Ö SUBSYSTEM ............................................................. 29
4.3 TRANSMISSION OF PROCESS DATA HOST Ö SUBSYSTEM ................................................ 30
4.4 SYSTEM INFORMATION HOST Õ SUBSYSTEM .................................................................. 31
5 SUBSTATION ERROR TELEGRAMMS HOST Õ SUBSYSTEM ............................................32
6 ASSIGNMENT OF THE DCU - / FIS – INTERFACES.........................................................33
6.1 PERIPHERAL INTERFACE CONNECTOR (RS-232C) DCU S/N > 4000................................ 33
6.2 PERIPHERAL INTERFACE CONNECTOR (RS-232C) DCU S/N < 4000................................ 33
6.3 HOST INTERFACE CONNECTOR (RS-422) ........................................................................ 33
6.4 ETHERNET 10-BASE-T INTERFACE CONNECTOR (RJ-45) ................................................. 34
6.5 ETHERNET SOFTWARE INTERFACE FOR PROGRAMMERS .................................................. 35
7 ASSIGNMENT OF THE DFC – INTERFACES ....................................................................37
7.1 PRINTER INTERFACE CONNECTOR (RS-232C) ................................................................. 37
7.2 HOST INTERFACE CONNECTOR (RS-422) ........................................................................ 37
- 1.6 05.07.05 F. Guthof

A File: Page 3
B of 40
1 GENERAL
The interface described below allows a data communication between a host computer and one of the
following devices:
DCU-System (Biostat B-DCU, Biostat C-DCU ect.) DCU Hardware

FIS (Fermentation Interface System) FIS Hardware
EGAS (Exhaust Gas Analyzer System) DFC Hardware
Biostat B (Lab Fermenter 2,5,10 Ltr.) DFC Hardware
Biostat C (Lab Fermenter 10,15,20 Ltr.) DFC Hardware
Biostat D (Lab Fermenter 30 - 150 Ltr.) DFC Hardware
Micro-DCU (Control unit with external components) DFC Hardware
In the following these systems are named substation. There are different hardware platforms
(DCU,FIS,DFC) of the fermenter process control units. The functions of the Host-Interface depends on
the used hardware as well as the installed software version. In the appendix, there is an overview table
explaining the different functions of the Host-Interface for each control unit and the different software
versions.
After initialization of the Substation the Host can request data from the Substation wihtout restriction. The
Substation receives a telegramm which requests for data being sent to the Host within certain time limits.
The data have been specified during initialization.
Fermentation parameters can only be sent from Host to a Substation if the Substation has been released
for transmission. To achieve this, the functional key must be set to "Remote Mode".
The communication protocol is character oriented and the data are coded according to the 7-Bit-ASCII-
code (DIN 66003,international characters).
The physical transmission medium comprises an asychronously working serial interface, whose driver
can be freely choosen in the Substation, depending on the mode of application.
The following interfaces can be choosen in the Substation:
- RS-232C at peripheral interface connector

- RS-422 at Host computer connector
- Ethernet 10-Base-T (RJ-45) at Ethernet computer connector
The common RS-232C interface is not as insensible to interfering signals as the RS-422 with
differential interface lines. Besides the RS-232C interface only allows point-to-point connections at
comparatively short distances.
The electrical properties of the RS-422 interface are designed for modern multidrop connections. They
comply with DIN 66259 T4 and ISO 8482 and derive from EIA RS-485. Further information can be found
in the corresponding standards and in the operators handbook for the Substation.
The electrical properties of the ethernet interface are designed for modern multidrop connections. They
comply with IEEE 802.3. Further information can be found in the corresponding standards and in the
operators handbook for the Substation.
- 1.6 05.07.05 F. Guthof

A File: Page 4
B of 40
2 PREREQUISITS FOR DATA TRANSMISSION
2.1 TRANSMISSION CONTROL VIA HOST COMPUTER
The data are transmitted between Host and Substation according to the master-slave principle, i.e., the
data transmission can only be started by the Host Computer. A communication between the Substations
themselves (multidrop connection) is not possible.
The host computer can control the data transmission to a Substation via commands. Commands are
available for:
DR requests for process data from the subsystem

DS send process data to the subsystem
SU subsystem initialization
All commands are described in chapter 4 in detail.
A specific Substation is selected by an address field in the command telegramm. For each Substation
the address can be manually set.
2.2 SUBSTATION INITIALIZATION
Prior to the first data request the host computer must initialize the corresponding Substation (command
DR). The initialization command sends parameters to the Substation and thus adapts the data
transmission to the requirements.
The first parameter is a list of data groups which have to be transmitted to the host computer as
response to a data request command.
The second and third parameters are reserved for future applications. The field must be completed by
the following values:
Parameter 2: 5
Parameter 3: 2
Without initialization the Substation sends an error telegramm after receiving a data request command
(DR). For further details see chapter "Commands".
- 1.6 05.07.05 F. Guthof

A File: Page 5
B of 40
2.3 BREAK-GENERATION VIA HOST SYSTEM (RS422, RS232 ONLY)
Before sending a command to the Substation a break condition must be generated on the interface in
order to switch the connected Substation to the "Receive" mode. The duration of the break (depends on
the baudrate) should be approximately the same as the transmission time for two characters. After
resetting the break a 2ms delay time is recommended before sending characters. In each case the
"Break" condition must be generated prior to each command to the Substation by the Host system.
2.4 REMOTE MODE
The Substation can be manually switched to the operating mode "Local" or "Remote" by means of the "
Remote" key of the DCU / Biostat B keypad. But only the "Remote" mode allows a control via the Host
Computer, i.e. only in the "Remote" mode the Substation accepts the set parameters of the Host System.
Except for the initialization command and the setting of the real time and the process time, all
commands with which parameters in the Substation can be changed will be responded by an error
telegramm if the Substation is not in the "Remote" mode.
If the host computer sets the process parameters in the "Remote" mode all other functions, direct access
included (Shut down, Acknowledge etc.) can be realized at any time.
A change from "Remote" to "Local" is only active (delay possible) when a running data
transmission/processing of one block is finished.
2.5 RESERVED CONTROL CHARACTER
The following characters are required for data transmission control.
* - Start character Host telegramm

# - Start character Substation telegramm
: - Delimiter for data fields
@ - End mark for each telegramm
/ - Delimiter for date and time and for initialization formats
, - Delimiter between integer fields of date and time
- 1.6 05.07.05 F. Guthof

A File: Page 6
B of 40
2.6 TELEGRAMM FORMAT
All telegramms must have the following format. Depending on the data group, however, the message
field can change in its structure. The status field always indicates the actual status of the telegramm
sender.
SC ADR : COMMAND : SEQ : STAT : MESSAGE-FIELD : CS EM
SC Start character STAT Status of sender

ADR Unit address* CS Check Sum
SEQ Sequence EM End Mark
* For ethernet connection it can be any number
Structure of message field:
DES : NO : VAL : NO : VAL : ... : DES : NO : VAL : ...
DES Designation (PV,CS...) NO Channel Number

VAL Value
Example:
#1:DR:0:16:PV:1:124.6:2:567.3:....:15:250.0:16:240.5:XXXX@
All designation definitions will be described in detail in the following chapters.
2.7 Transmission formats for date and time
For transmission of date and time (DAT) as well as of process time (AGE) special formats have been
established. For separation of the integer fields specific control characters have been reserved. The
following formats have been defined:
DAT = Day , Month , Year / Hour , Minute , Second
AGE = Hour , Minute
- 1.6 05.07.05 F. Guthof

A File: Page 7
B of 40
2.7 TABLE NUMBERS
In the structure of the message field (see Telegram Format) exists a number field before each value.
These numbers are corresponding to the order in one of the following DCU-Table:
Process Display PVAL Table for process values

Process Display CLOOP Table for controllers
Process Display DGIN Table for digital inputs
Process Display DGOUT Table for digital outputs
These table numbers are shown in the DCU-menu " Process Display" and the corresponding table.
2.8 RANGE OF VALUES FOR DATA TRANSMISSION FIELDS
The range of values for the types of data used in the data field definitions are as follows:
- Byte 0 ... 255

- Integer 0 ... 32767
- Real -1000.0 ... +1000.0
- String <= 255 characters
The transmission of the process values with the mark "REAL" is standardized. The range of values has
been defined as 0 .. 100% = 0 .. +1000.0. The values for controller outputs as well dosing counters are
an exception. The range of controller output values is -100% .. +100% = -1000.0 .. +1000.0 . The range
for dosing counters are not limited in the DCU-System, so the value can be greater than 1000.0 (e.g.
4255.7).
2.9 RESPONSE TELEGRAMMS OF SUBSTATIONS
The contacted Substation responds within the Timeout limit (500ms) with the required reponse
telegramm (specification see below) or with an error telegramm if all the following conditions are given. If
one condition is not given none of the connected Substations will respond.
1. Command telgramm begins with * and ends with @

2. sent check sum = calculated check sum
3. received address = set address
- 1.6 05.07.05 F. Guthof

A File: Page 8
B of 40
2.10 TMEOUT AND REPETITION
In the case of transmission errors the host system can automatically repeat a command by means of
time out supervision and sequence counter. The number of repetitions is not limited and will be
determined by the Host system.
The time out conditions for a host computer are defined as follows:
The time out period begins when the last character has been sent from the host
computer.
The period is finished when the first character of the response telegramm has been
received. Thus the timeout supervision does not depend on the transmission time of a
complete response telegramm.
If no character has been received by the contacted Substation after 500 ms the
timeout condition is activated.
The Substations ensure that the reponse is not transmitted after the timeout period.
Refer to the following example for better understanding:
Host sends command *1:DR:0:0:569@ and receives error telegramm or no

character after the time out period of 500 ms.
Host sends the same command with incremented sequence *1:DR:1:0:570@ if the
maximum repetition number has not been exceeded.
The Substation stores the last sent response until the next command is received in order to be able to
repeat the data (incremented sequence) if necessary.
Note:
The transmission time for one character depends on the set baud rate. Thus the
transmission time for one character at low baud rates is comparatively long. The time
out period of 500 ms takes into account rates of 300 - 19200 Bauds.
- 1.6 05.07.05 F. Guthof

A File: Page 9
B of 40
2.11 END OF DATA TRANSMISSION
The data transmission is only finished if all data blocks (cf. 2.14, block transmission) of one Substation
telegramm are corretly sent to the Host.
A new reponse telegramm is only sent to the Substation if the last data block has been sent to the Host
and if the Host Computer has then sent a new data request command wiht the sequence 0.
2.12 DATA SECURITY
A correct asynchronous single byte transmission is ensured by means of checking the corresponding
error bit in the USART-element. Double parity errors in one byte are recognized by check sums.
2.13 CHECK SUM
The check sum is formed by addition of all ASCII values from the start sign (* or #) up to and including
the delimiter (:) directly in front of the check sum. The calculated value cannot exceed the value of 32385
and is variable, denpendent on the message length.
2.14 BLOCK TRANSMISSION
For extensive data transmission the Substation divides the data into several blocks. When receiving the
next data request command from the Host Computer (no incremented sequence) the next data block will
be sent. If the sequence of the data request command is enlarged the Substation sends again the last
data block to the Host Computer. In the last data block of the Substation response telegramm the status
bit d3 is reset to the inactive condition.
The blocks are divided in such a way that no complete data field (No../Value) is divided.
- 1.6 05.07.05 F. Guthof

A File: Page 10
B of 40
3 TRANSMISSION VOLUME AND DEFINITION OF DATA FIELDS
Due to extensive data quantities in the Substation the process data are divided into different data groups.
For identification of the data groups in the serial data flow each group has a defined designation. Even if
the data group is transmitted in two blocks, each block is designated in such a way. Each process value
also has its defined identification with a number from the corresponding Substation table.
3.1 STATUS DEFINITION DIRECTION: HOST Ù SUBSYSTEM
The status field always indicates the actual status of the sender. Between host and Substation, however,
different function assignments exist. The status field in the reponse telegramm always has the structure
given below. The status definition of the host must not be taken into account here. It is reserved for
future applications. The field, however , must be filled with the defined value of 0.
Statusfield:
Bit Function
D0 Local / Remote 1: Remote

D1 Shut down 1: Active
D2 Config. progr. runs 1: Active
D3 further sending data 1: Active
D4 Normal fermentation 1: Active
D5 Sequence 1: Active
D6 Recipe 1 1: Active
D10 Sequence 1 1: Active
D14 - D15 at present not reserved
For DFC Hardware the information Local/Remote (D0) are transmitted only. All other bits are not used.
The sum of all bit values is transmitted as integer number (decimal)!
Ex.: Statusfield = 17
D0 = Remote mode active Value of D0 = 1
D4 = Normal fermentation active Value of D4 = 16
- 1.6 05.07.05 F. Guthof

A File: Page 11
B of 40
3.2 OPERATING MODES HOST Ù SUBSYSTEM
For synchronization of the real time clocks of the Host Computer and the Substation, the Host can adjust
the time of the Substation. Additionally the running process time of the Host can be adjusted. Both
adjustments are possible in the "Remote" and in the "Local" mode. Inside the DCU there is a connection
between realtime and process time, and is is not possible to send both times together in one command
to the DCU. Therefore you have to use two different commands.
Designation: - String BC "Batch Control"
Number: - Byte 1: Local/Remote Setting

2-5: reserved
6: Process time
7: Real time
Value: to 1 - Byte 0: Set Local Mode
1: Set Remote Mode
to 6 - AGE
to 7 - DAT
Example: for direction DCU Ö Host (all in one message, single send also possible)
#1:DR:0:17:BC:1:1:6:9999,59:7:31,12,1999/23,59,59:2709@
3.3 PROCESS VALUES HOST Õ SUBSYSTEM
Designation: - String PV "Process Value"

Number: - Byte Number of DCU table process display PVAL
Value: - Real Process value (Range 0 .. +1000.0)
Example: :PV:1:187.5:
3.4 ALARM PARAMETERS PROCESS VALUES HOST Ù SUBSYSTEM
Designation: - String PA "Process Value Alarm Parameter"
Value: - Real Low Limit

- Real High Limit
- Byte Mode 1:Enable
- Byte Reserve (0)
- Real Reserve (0.0)
Example: :PA:3:0.0:666.6:1:0:0.0:
- 1.6 05.07.05 F. Guthof

A File: Page 12
B of 40
3.5 ALARM CONDITIONS PROCESS VALUES HOST Õ SUBSYSTEM
Designation: - String PS "Process Value Alarm State"

Value: - Byte DO: Low Alarm
D1: High Alarm
D2: Low Alarm not acknowledged, S. Vers. 3.2
D3: High Alarm not acknowledged, S. Vers. 3.2
Example:
:PS:1:2:2:10: ch 1 high alarm, ch 2 high alarm + not ackn.
3.6 PROCESS VALUE TOTALIZER HOST Ö SUBSYSTEM
Availbale with DCU software version 4.80 or higher.

Designation: - String PT "Process Value Totalizer"
Number: - Byte Channel number of process value
Value - Byte Mode
1 Reset totalizer
Example:
:PT:8:1:
- 1.6 05.07.05 F. Guthof

A File: Page 13
B of 40
3.7 CONTROLLER HOST Ù SUBSYSTEM
For subsystems based on DFC hardware the designations CS for Controller Setpoint as well as
CM for Controller Mode can be set by the Host only. The designations CO for Controller Output
and CR for Controller Reserve are not supported.
Designation: - String CS Controller Setpoint

CO Controller Output
CM Controller Mode
CR Controller Reserve
(For designation CR the Direction of transmission is HOST
Ö DCU only!)
Number: - Byte Number from DCU table process CLOOP
Value: to CS - Real Process value
to CO - Real Process value
to CM - Byte 0: Off
1: Auto
2: Cascade DCU Hardware only
3: Manual DCU Hardware only
4: Profile DCU Hardware only
- 1.6 05.07.05 F. Guthof

A File: Page 14
B of 40
Value: for CR - Byte The parameters for one or more Substation controllers
are transmitted via the designation CR. The number of
Real fields is free and is determined by the first
information byte. Only the Real fields mentioned below
are transmitted (coupled) and all fields not mentioned are
not applicable. Thus 8 Real fields at maximum can be
transmitted consecutively.
Bit D0: MIN-Value

Bit D1: MAX-Value
Bit D2: DEADB-Value 0..100%
Bit D3: XP-Value 0..1000%
Bit D4: TI-Value 0..10000 sec.
Bit D5: TD-Value 0..10000 sec.
Bit D6: reserved
Bit D7: reserved
- Real MIN - Controller output voltage if D0 active

- Real MAX - Controller output limit if D1 active
- Real DEADB – Deadband if D2 active
- Real Controller parameter XP if D3 active
- Real Controller parameter TI if D4 active
- Real Controller parameter TD if D5 active
- Real reserved
- Real reserved
Examples:
*1:DS:0:0:CS:1:150.0:2:250.0:CM:1:1:2:1:2229@
*1:DS:0:0:CR:1:56:300.0:200.0:0.0:1846@
56 Ö XP,TI and TD are transmitted (3 Real fields).
300% for XP, 2000 sec. for TI and 0 sec. for TD
Note:
For PID controller with switchable cascade (PO2 controller) the preset parameter only
effect the currently activated parameter set.
It is possible to send down controller parameters for an PID-Controller (controller

type) only. It isn't possible for a setpoint controller (stirrer speed).
The value range for PID-Parameters are: XP 0..1000%; TI and TD 0..10000 sec.;
Assumption: DCU software version 2.11 or higher
- 1.6 05.07.05 F. Guthof

A File: Page 15
B of 40
3.8 DIGITAL INPUT HOST Õ SUBSYSTEM
Designation: - String DI "Digital Input"

Value: - Byte Values (Number 1-8) from DCU table
process display DGIN
- Byte Values (Number 9-16, if exist)
Example: :DI:255:1:
3.9 ALARM PARAMETER DIGITAL INPUT HOST Ù SUBSYSTEM
Designation: - String DA "Digital Input Alarm Parameter"

Value: - Byte Alarm condition Value from DCU table
process display DGIN (Number 1-8)
- Byte Alarm condition (Number 9-16, if exist)
- Byte Mode 1: Enable (Number 1-8)
- Byte Mode 1: Enable (Number 9-16)
Example: :DA:0:0:255:12:
Remarks: The mode of the digital input „SUPON “ can not be switched to OFF. The DCU will
return and error message in this case!
3.10 DIGITAL OUTPUT HOST Ù SUBSYSTEM
Designation: - String DO "Digital Outputs"

Number: - Byte Values from DCU table
process displays DGOUT
Value - Byte Condition 0...100 PWM
128 Digital Out = 0
255 Digital Out = 1
Example: :DO:1:50:2:255:
Remarks: It is possible to used free digital outputs (DOPXY) only. Internal linked digital outputs
can not be used. For example, the digital output for the ACID pump is linked to the pH
controller and can not be used.
- 1.6 05.07.05 F. Guthof

A File: Page 16
B of 40
3.11 DCU-MESSAGES HOST Õ SUBSYSTEM
By using the data group MS it is possible to transmit messages from an DCU-System or FIS to the host
computer. All messages are transmitted as shown in the DCU display. In case that no message exists
the designation :MS: is transmitted only that means that the fields number and value are not included in
the telegram.
To distinguish whether an alarm occured or has been acknowledged each message will be start with >
or < character and a space:
:MS:1:42:> Power ... Ö Alarm occured

:MS:1:42:< Power ... Ö Alarm acknowledged
The message can be include the delimiter " : " of the communication protocol. To avoid problems the
message length will be transmitted before.
The message function is available with the DCU-Software-Version 3.2
Designation: - String MS "MeSsage"

Number: - Byte Type of the message
1: General Alarm Message
2: System Alarm
Value: - Byte Length of the message
- String Message
Example: :MS:1:42:> Power failure 02:48 02.11.93 09:47:52:

:MS:1:42:< System error SH208 02.11.93 09:47:52:
- 1.6 05.07.05 F. Guthof

A File: Page 17
B of 40
3.12 DCU-LOGBOOK HOST Õ SUBSYSTEM
By using the data group ML it is possible to transmit logbook entries from an DCU-System to the host
computer. In case that no message exists the designation :ML: is transmitted only that means that the
fields number and value are not included in the telegram.
Recommended only with ethernet interface
The message can be include the delimiter " : " of the communication protocol. To avoid problems the
message length will be transmitted before.
The message function is available with the DCU-Software-Version 4.6
Designation: - String ML "MessageLogbook"

Number: - Byte Type of the message
1: General Alarm Message
2: System Alarm
3: Digital Input Alarm
4: Process Value Alarm
5: Panel Input on Switch Panel
6: Host Input
7: Sequence Message
8: Main Switch
9: Panel Input on Panel
10:Initial Parameter
11:Start Parameter
Value: - Byte Length of the message

- String Message (1..140 char)
(Delimiter : <HT> Vertical Tab (Hex 0x09) )
:Date Time<HT>Source<HT>Unit Recipe

Type<HT>Data:
or
:Date Time<HT>Source<HT>Alarm Mark<HT>Alarm:
:DD:MM:YY HH:MM:SS<HT>
CCCCCCCCC NNN <HT>
UN: RN: CCCCCCCCCCCCCCCC <HT>
CCCCC...:
Example:
:ML:3:76:08.03.01 10:10:10<HT>Panel 100<HT>U1: R1: Controller<HT>TEMP SETPT: 100.0

degC:
- 1.6 05.07.05 F. Guthof

A File: Page 18
B of 40
3.13 EXTENDED ALARM PARAMETER DIGITAL INPUT HOST Ù SUBSYSTEM
This data group is available with the DCU-Software-Version 3.2. The function is able to send digital input
values and parameters above channel number 16 (additional card inside the DCU) and includes alarm
acknowledgement. For the communication direction HOST Ö DCU the Host can modify Bit D2 =
Alarmmode only.
Designation: - String DC "Digital Input Alarm Condition"
Nummber: - Byte channel from DCU-Table Process Display DGIN
Value: - Byte Statusbyte bit coded
DO: digital input value
D1: Alarmstate 1 = alarm pending
D2: Alarmmode 1 = enabled
D3: Acknowledgment 1 = not acknowledged
Example:
:DC:1:2:2:4:3:0:
- 1.6 05.07.05 F. Guthof

A File: Page 19
B of 40
3.14 USER-LOGGING HOST Õ SUBSYSTEM
Since the DCU-Software-Version 3.2 a user logging is available. Each user of an DCU-System must be
logged in with a user number and a password. The active user of an DCU-System can be transmitted to
the host via the communication protocol.
Designation: - String UL "User Logging"

Value: - Byte 1..255 user identification
0 no user active
Example:
:UL:12:
- 1.6 05.07.05 F. Guthof

A File: Page 20
B of 40
3.15 SEQUENCE MODE HOST Ù SUBSYSTEM
The sequence control of the Substation has an extensive functional range. Thus the system can transmit
state information to the Host computer. Additionally it is possible to preset some parameters via the Host
system. The corresponding definitions are as follows:
Designation: - String SM "Sequence Mode"

Number: - Byte Number of the sequence 1..4
Value: - Integer Mode of the sequence
Bit D0 Stop Host Ö DCU
Bit D1 Start Host Ö DCU
Bit D2 Step Host Ö DCU
Bit D3 reserved Host Ö DCU
Bit D4 aktive Host Õ DCU
Bit D5 inaktive Host Õ DCU
Bit D6 reserved Host Õ DCU
Bit D7 reserved
Bit D8 Priority = 1 Host Õ DCU
Bits D12 - D15 are reserved
- String Phase of the sequence, 5 characters
Example:
:SM:1:1: :
In the examples mentioned above the Host computer transmits a start command for
the sequence number 1 to a Substation. In the string field for the phase 5 blanks
"Space" must be transmit with the command.
- 1.6 05.07.05 F. Guthof

A File: Page 21
B of 40
3.16 SEQUENCE SETPOINTS HOST Ö SUBSYSTEM
For complete control of the sequence via the Host, the Host can transmit sequence parameter to the
Substation.
Designation: - String SS "Sequence Setpoints"

Value: - AGE Time Setpoint
- Real Controller Setpoint #1 e.g. Sterilization Temp.
- Real Controller Setpoint #2 e.g. Fermentation Temp.
- AGE reserved "0,0"
- Real reserved "0.0"
- Real reserved "0.0"
Example:
:SS:1:0,45:800.0:200.0:0,0:0.0:0.0:
In the example above (Sterilization Sequence), the Host transmits the following
sequence parameters:
- Time Setpoint 45 min, Sterilization duration
- Controller Setpoint #1 120 degrees C, Sterilization temperature
- Controller Setpoint #2 30 degrees C, Fermentation temperature
- 1.6 05.07.05 F. Guthof

A File: Page 22
B of 40
3.17 SEQUENCE REQUEST HOST Ù SUBSYSTEM
The sequence control of the Substation has an extensive functional range. Thus the system can transmit
state information to the Host computer. Additionally it is possible to preset some parameters via the Host
system. The corresponding definitions are as follows:
Designation: - String SR "Sequence Request"

Value: - Integer Mode of the sequence
Bit D0 Stop Host Ö DCU
Bit D1 Start Host Ö DCU
Bit D2 Step Host Ö DCU
Bit D3 reserved Host Ö DCU
Bit D4 running Host Õ DCU
Bit D5 idle Host Õ DCU
Bit D6 locked Host Õ DCU
Bit D7 stopping Host Õ DCU
Bits D8 - D15 are reserved
Value - AGE Elapsed time since start of sequence Host Õ DCU
Value: - Integer Number of step (1..n) from sequence Host Õ DCU
Assumption: DCU software version 4.80 or higher
Example Host Ö DCU:
:DS:0:0:SR:1:1:
In the examples mentioned above the Host computer transmits a start command for the sequence
number 1 to a Substation.
Example Host Õ DCU:
*1:DR:0:0:SR:1:
Response telegramm:
#1:DR:0:16:SR:1:1:0,30:88:
- 1.6 05.07.05 F. Guthof

A File: Page 23
B of 40
3.18 SEQUENCE PARAMETER HOST Ù SUBSYSTEM
For complete control of the sequence via the Host, the Host can transmit sequence parameter to the
Substation.
Designation: String SP Sequence Parameters
Value: - AGE Timer Setpoint #1
- AGE Elapsed Time #1 Host Õ DCU
- AGE Timer Setpoint #2
- Real Controller Setpoint #1

Example Host Ö DCU:
:DS:0:0:SP: 1:0,45:0,60:0,14:0,32;0,45:0,60:0,14:0,32:800.0:200.0:0.0:0.0:0.0:0.0:
In the examples mentioned above the Host computer transmits a start command for the
sequence number 1 to a Substation.
Example Host Õ DCU:
*1:DR:0:0:SP:1:
Response telegramm:
#1:DR:0:16:SP: 1:0,45:0,60:0,14:0,32;800.0:200.0:0.0:0.0:0.0:0.0:
- 1.6 05.07.05 F. Guthof

A File: Page 24
B of 40
3.19 SEQUENCE STEPS HOST Õ SUBSYSTEM
For display origin tag of step from sequence via the Host, the Host can receive sequence steps.
Designation: String ST Sequence STeps
- String Sequence Tag, 10 characters
Number: - Byte Number of steps
Number: - Byte Phase number
Number of Strings - String Phase tag, 10 characters
Example:
*1:DR:0:0:ST:1:
Response telegramm:
#1:DR:0:16:ST:1:FVESS____:4:1:HEAT1_____:2:HEAT2_____:3:STERI_____:4:COOL1__
___:
In the examples mentioned above the Host computer transmits a start command for the sequence
number 1 to a Substation. In the string field for the phase 10 blanks "Space" must be transmit with the
command, because character ‘:’ could be in string.
- 1.6 05.07.05 F. Guthof

A File: Page 25
B of 40
3.20 RECIPE MODE HOST Ö SUBSYSTEM
Start and stop of recipes within a Substation is controlled via the designation RM. The following
parameters are transmitted:
Designation: - String RM "Recipe Mode"

Number: - Byte Number of recipe 1..4
Value: - Integer Mode of recipe
Bit D0 Stop (Value = 1)
Bit D1 Start (Value = 2)
Bits D2 -D15 are reserved
- String Blank string with 5 characters; reserved
Example:
:RM:3:2: :
In the example above the Host transmits a command that starts

the recipe no. 3.
- 1.6 05.07.05 F. Guthof

A File: Page 26
B of 40
4 COMMANDS
In order to achieve a defined data flow between Host and Substation several commands from host to
Substation are necessary. Each command of the host is responded by the Substation if the sending
conditions are given (2.9 Response telegramm of Substations). The Substation sends an
acknowledgment or error telegramm after the commands SU and DS and after the command DR the
Substation sends the process data or an error telegramm to the host. The acknowledgement telegamms
have the following structure:
- Start character and address

- Reflexion of received command
- Reflexion of received sequence
- current statusfield
- Check sum and end mark
Examples for acknowledgement telegramms are at the end of each command description.
The Substation error telegramms are described in chapter 5.
- 1.6 05.07.05 F. Guthof

A File: Page 27
B of 40
4.1 DCU INITIALIZATION HOST Ö SUBSYSTEM
The Substation can be initialized at any time, no matter what the status of the REM key and the
operating mode (Recipe process, sterilization) are.
Command: - String SU "SetUP"

Value: - String Listing of data groups transmitted from Substation to Host
after data request command of the Host. The
designations are separated by the delimiter "/".
Not all substations are able to understand all data groups,
for example, an EGAS allows PV only. Please refer to the
overview table in the appendix to determine which
subsystem understand which data group.
- PV
- PA Unwanted data groups must not be indicated.
- PS
- BC The order of data groups must be considered.
- CS
- CO
- CM
- DI
- DA
- DO
- DC
- MS
- UL
- SM
- Byte Reserved, must have the value 5

- Byte Reserved, must have the value 2
To delete a data group already choosen a completely new initialization command must be send
to the Substation.
Examples:
*1:SU:0:0:PV:5:2:1030@
*1:SU:0:0:PV/CS/CO/CM:5:2:1611@
Acknowledgement telegramm:
#1:SU:0:17:636@ (the information field PV/CO/... is not transmitted back!)
- 1.6 05.07.05 F. Guthof

A File: Page 28
B of 40
4.2 PROCESS DATA REQUEST HOST Ö SUBSYSTEM
This command allows the transmission of the data (as determined in the initialization) from the
Substation to the host. All data must have the same time basis.
Command: String: DR "Data Request"
Example:
*1:DR:0:0:569@
Response telegramm:
#1:DR:0:17:PV:1:187.5:2:150.0:...:CS:1:250.0:...:xxxx@
- 1.6 05.07.05 F. Guthof

A File: Page 29
B of 40
4.3 TRANSMISSION OF PROCESS DATA HOST Ö SUBSYSTEM
This command allows the data transmission from host to Substation ( if the Substation is in the Remote
mode). All process data with the specified transmission direction Host -> DCU / FIS can be sent to the
Substation herewith. To achieve this the information field must be completed with the required
designations of the data groups and the process values (cf. examples). If the definitions of the separate
data fields are not observed the Substation sends an error telegramm and thus denies the process data.
Additionally the Substation checks the status of the REM key and sens an error telegramm if the key is
not activated. Only an activated REM key allows the data setting by the Host Computer.
The adjustment of the process time and real time (designation BC) is an exception and can only be sent
to the Substation at any time like the initialization command.
The data setting with the command DS does not depend on the initialized data group. Even controller
setpoints can be determined by the Host, despite the fact that no sepoints but only process values
should be sent from the Substation to the Host (only PV initialized).
Command: - String DS "Data Set"

Designation, Depending on the type of application,
Number, the structure can differ
Value
Example:
*1:DS:0:0:CS:3:625.0:CM:3:1:PA:3:0.0:666.6:1:0:0.0:2859@
- Controller Setpoint No.3 on pH 7.5

- Controller Mode No.3 on Auto
- Alarm parameter PV No.3 Limits Low=0/High=8pH,Mode=Enable,2xReserve
*1:DS:0:0:BC:7:14,12,1988/16,34,12:1878@
- Setting of Date and Time
Acknowledgement telegramm:
#1:DS:0:17:619@
- 1.6 05.07.05 F. Guthof

A File: Page 30
B of 40
4.4 SYSTEM INFORMATION HOST Õ SUBSYSTEM
This command allows the data transmission from substation to host about specified information.
Command: - String SI "System Information"
Number: - Byte Control unit type

1: DCU
Value: - String Firmware version
4.80
Value: - String Configuration ID
48___B_H502_
Designation - String Type of setting
CS Calibration sensor
CT Calibration totalizer
CB Calibration balance
MR Measuring ranges
CL Controller settings (PID and SETP only)
Number: - Byte Number of setting CS, CT, CB channel of connected PV
Designation - String Content of setting in engineering units

CS(pH,pO2) <zero>_<slope>
CS(Redox) <buffer>
CS(Turbidity) <zero>
CT <mode>_<flow>
CB(Weight) <mode>_<tare>
CB(Flow) <mode>_<tare>
MR <min>_<max>
CL(PID2/3) <casc label>_<channel of casc>_
<min>_<max>_
<deadb>_<xp>_<ti>_<td>_<hystersestime>
CL(PID) <min>_<max>_<deadb>_<xp>_<ti>_<td>
CL(SETP) <min>_<max>
Example:
*1:SI:0:0:
Response telegramm:
#1:SI:1:4.80:48___B_H502_:CS:1:0.0 59.9:SQ:1:121.0 37.0 0.0 0.0 0.0 0.0 00:30 ....
- 1.6 05.07.05 F. Guthof

A File: Page 31
B of 40
5 SUBSTATION ERROR TELEGRAMMS HOST Õ SUBSYSTEM
In case of an error the Substation generates an error telegramm itself. Since different error causes may
occur, it is differentiated between logical errors, data errors and format errors. Each type of error has its
specific designation. The error telegramm has the following structure:
Command: - String CE "Communication Error"
Designation: - String LE Logical Error

FE Format Error
DE Data Error
Number: to LE - Byte Error code from error table

to FE - Byte Character counter
to DE - Byte Character counter
Value: to FE - String Complete structure of received host command from field

command up to error.
to DE - String like FE
List for logical errors:
Code Cause
1 Substation has not been initialized and the received data request command,
command DR, is not applicable
2 Inadmissible adjustment by host since Substation not in Remote mode.
3 Command faulty
4 Host status field faulty
5 Inadmissible adjustment of controller mode
6 Recipe can not be started
7 Sequence did not exist
8 Sequence can not be started
9 Unknown Command
Examples:
#2:CE:0:16:LE:2:915@
#2:CE:0:17:DE:7:CS:17:2:1391@ Channel 17 did not exist
- 1.6 05.07.05 F. Guthof

A File: Page 32
B of 40
Assignment of Interfaces
6 ASSIGNMENT OF THE DCU - / FIS – INTERFACES
6.1 PERIPHERAL INTERFACE CONNECTOR (RS-232C) DCU S/N > 4000
PERIPHERAL (RS232) SUBD, 9 pol., Female

Frontview Pin RS232 Explanation
1
2 RXD Receive data
9 5 3 TXD Transmit data
4 DTR Data Terminal Ready
5 DGND Ground
6 6
1 7
8 CTS Clear to Send
9
6.2 PERIPHERAL INTERFACE CONNECTOR (RS-232C) DCU S/N < 4000
PERIPHERAL (RS232) SUBD, 9 pol., Female

1
2
4 RXD Receive data
5
6 6
1 7 GND Ground
8
9
6.3 HOST INTERFACE CONNECTOR (RS-422)
X3 – HOST (RS422) SUBD, 9 pol., Female

1 RTS Request to send
2 DGND Ground
9 5 3 /DO Transmit data -
4 /RI Receive data -
5 RGND Ground
6 6
1 7 DGND Ground
8 DO Transmit data
9 RI Receive data
- 1.6 05.07.05 F. Guthof

A File: Page 33
B of 40
6.4 ETHERNET 10-BASE-T INTERFACE CONNECTOR (RJ-45)
X1920, 1910 – Ethernet RJ-45

Frontview Pin RJ-45 Explanation
1 TPRXA Twisted Pair Receiver Channel A
2 TPRXB Twisted Pair Receiver Channel B
3 TPTXA Twisted Pair Transmitter Channel A
4
5
6 TPTXB Twisted Pair Transmitter Channel B
7
8
PE PE Connected with case
- 1.6 05.07.05 F. Guthof

A File: Page 34
B of 40
6.5 ETHERNET SOFTWARE INTERFACE FOR PROGRAMMERS
6.5.1 DCU-SERVER ISO/OSI MODEL
Client-Server technology
Based on SOCKET-technology of Berkely
Using ISO/OSI-7-level model like following:
Level Application Data Structure

7. Application dcucomm-task Host-
Telegramm
6. Presentation
5. Session dcuserver-task Server- Server-Data
Header
4. Transport TCP TCP-Header TCP-Data

3. Network IP IP-Header IP-Data
Ethernet.-
2. Data Link ETHERNET IEEE 802.3 Header
1. Physical 10Base-T Ethernet-Data
6.5.2 SOCKET-PARAMETER
Type Setting Remark
Address Family AF_INET ARPA Internet address family
Socket Type SOCK_STREAM Stream socket, full duplex connect byte streams
with protocol TCP/IP
Socket I/O Blocking Mode Non Blocking Socket Read / write option for sockets
Port Number of Service 21333 (dcu-port) Identifikation of DCUSERVER service
Clients IP Access Any IP Defines which IP-addresse allowed to connect
Count of concurrently 1 Only one client its allowed to connect at one

clients time.
- 1.6 05.07.05 F. Guthof

A File: Page 35
B of 40
6.5.3 HOST TELEGRAMM FORMAT
SF 1 SF 2 SF 3 LENGTH TELEGRAM FORMAT
SF 1 State Field 1 4 Byte Future Option (must be in network byte order*)

LENGTH Length Of Data 4 Byte Length of data (must be in network byte order*)
TELEGRAM FORMAT
Data 1..256 Byte See chapter “2.6 Telegram Format”
* Use standard network C function “htonl() – Convert 32-bit values between host and network byte
order”.
6.5.3.1 C Example
char message[32] =
{
0, 0, 0, 0, /* state field 1 */
0, 0, 0, 0, /* state field 2 */
0, 0, 0, 0, /* state field 3 */
0, 0, 0, 0xE, /* lenght of data */
'*', /* data start ... */
'1',
':',
'D',
'R',
':',
'0',
':',
'0',
':',
'5',
'6',
'9',
'@' /* ... data end */
};
- 1.6 05.07.05 F. Guthof

A File: Page 36
B of 40
7 ASSIGNMENT OF THE DFC – INTERFACES
7.1 PRINTER INTERFACE CONNECTOR (RS-232C)
X4 – PERIPHERAL (RS232) SUBD, 9 pol., Female

1
2 RXD Receive data
4 DTR Data Terminal Ready
5 DGND Ground
6 6
1 7
8 CTS Clear to Send
9
7.2 HOST INTERFACE CONNECTOR (RS-422)
X3 – HOST (RS422) SUBD, 9 pol., Female

1 RTS Request to send
2 DGND Ground
9 5 3 /DO Transmit data -
4 /RI Receive data -
5 RGND Ground
6 6
1 7 DGND Ground
8 DO Transmit data
9 RI Receive data
- 1.6 05.07.05 F. Guthof

A File: Page 37
B of 40
DCU-SW DCU-SW DCU-SW DCU-SW

1.1 - 2.11 2.11 - 3.2 3.2 - 3.4 3.5 – 4.7
DCU1, FIS1 DCU1, DCU2, FIS1, DCU2, FIS2 DCU2, FIS2, DCU3
FIS2
Parameter of the Subsystem Group Revision HOST --> Subsystem HOST --> Subsystem HOST --> Subsystem HOST --> Subsystem
Subsystem --> HOST Subsystem --> HOST Subsystem --> HOST Subsystem --> HOST
Batch Control BC 0 X X X X
Batch Control extended with local/remote setting BC 1 X X X
Batch Control extended direction to Host BC 2 X
Process Values (PV) PV X X X X
Process Values Alarmparameters PA X X X X
Process Values Alarmstate PS 0 X X
Process Values Alarmstate extended PS 1 X X
Controller Setpoint CS X X X X X X X X
Controller Mode CM X X X X X X X X
Controller Output CO X X X X X X X X
Controller Parameter CR X X X
Digital Inputs State DI01..16 DI X X X X
Dig. Inp. Alarmparameter DA X X X X X X X X
Dig. Inp. Alarm Condition DC X X X X
Digital Output DO X X X X X X X X
DCU-Messages MS X X
User-Logging UL X X
Sequence Mode SM X X X X X X
Sequence Setpoints SS X X X
Recipe Mode RM X State X State X State
Setup Subsystem SU 0 X X X X
Setup Subsystem extended with SM SU 1 X X X X
Setup Subsystem extended with SM, DC, MS, UL SU 2 X X
Setup Subsystem extended with BC SU 3 X
State State 0 X X X X
State extended with Sequence 1..4 State 1 X X X
- 1.6 05.07.05 F. Guthof

A File: Page 38
B of 40
DCU-SW
4.8 – act.
DCU3
Parameter of the Subsystem Group Revision HOST --> Subsystem
Subsystem --> HOST
Batch Control BC 0 X
Batch Control extended with local/remote setting BC 1 X
Batch Control extended direction to Host BC 2 X
Process Values (PV) PV X
Process Values Alarmparameters PA X
Process Values Alarmstate PS 0
Process Values Alarmstate extended PS 1 X
Process Values Totalizer PT X
Controller Setpoint CS X X
Controller Mode CM X X
Controller Output CO X X
Controller Parameter CR X
Digital Inputs State DI01..16 DI X
Dig. Inp. Alarmparameter DA X X
Dig. Inp. Alarm Condition DC X X
Digital Output DO X X
DCU-Messages MS X
User-Logging UL X
Sequence Mode SM X X
Sequence Setpoints SS X
Sequence Request SR Mode X
Sequence Parameter SP X X
Sequence Steps ST X
Recipe Mode RM X State
Setup Subsystem SU 0 X
Setup Subsystem extended with SM SU 1 X
Setup Subsystem extended with SM, DC, MS, UL SU 2 X
Setup Subsystem extended with BC SU 3 X
System Information SI X
State State 0 X
State extended with Sequence 1..4 State 1 X
- 1.6 05.07.05 F. Guthof

A File: Page 39
B of 40
DFC2-SW DFC2-SW EGAS-SW

1.0 - 2.1 3.0 1.00-1.03
Biostat B, C Biostat B, C, D EGAS2, 4, 8
Micro-DCU
Parameter of the Subsystem Group Rev HOST --> Subsystem HOST --> Subsystem HOST --> Subsystem
Subsystem --> HOST Subsystem --> HOST Subsystem --> HOST
Batch Control BC 0
Batch Control extended with local/remote setting BC 1
Process Values (PV) PV X X X
Process Values Alarmparameters PA
Process Values Alarmstate PS 0
Process Values Alarmstate extended PS 1
Controller Setpoint CS X X X
Controller Mode CM X X X
Controller Output CO
Controller Parameter CR
Digital Inputs State DI01..16 DI
Dig. Inp. Alarmparameter DA
Dig. Inp. Alarm Condition DC
Digital Output DO
DCU-Messages MS
User-Logging UL
Sequence Mode SM
Sequence Setpoints SS
Recipe Mode RM
Setup Subsystem SU 0 X X X
Setup Subsystem extended with SM SU 1
Setup Subsystem ext. with SM, DC, MS, UL SU 2
State State 0 X X X
State extended with Sequence 1..4 State 1
- 1.6 05.07.05 F. Guthof

A File: Page 40
B of 40

Sartorius Manual Dcu-Host Interface 1 - 6

Uploaded by

Document Information

Original Description:

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

Sartorius Manual Dcu-Host Interface 1 - 6

Uploaded by

Copyright:

Available Formats

INTERFACE DESCRIPTION

DCU - DFC ' HOST

VERSION DATE NAME CHANGES

1.5 12.05.03 F. Guthof Ethernet interface

1.6 05.07.05 F. Guthof New Commands : SI, PT, SP, SR, ST

- 1.6 05.07.05 F. Guthof

3.19 SEQUENCE STEPS HOST Õ SUBSYSTEM ..................................................................... 25

- 1.6 05.07.05 F. Guthof

DCU-System (Biostat B-DCU, Biostat C-DCU ect.) DCU Hardware

The following interfaces can be choosen in the Substation:

- RS-232C at peripheral interface connector

- 1.6 05.07.05 F. Guthof

2 PREREQUISITS FOR DATA TRANSMISSION

2.1 TRANSMISSION CONTROL VIA HOST COMPUTER

DR requests for process data from the subsystem

All commands are described in chapter 4 in detail.

2.2 SUBSTATION INITIALIZATION

- 1.6 05.07.05 F. Guthof

2.3 BREAK-GENERATION VIA HOST SYSTEM (RS422, RS232 ONLY)

2.4 REMOTE MODE

2.5 RESERVED CONTROL CHARACTER

The following characters are required for data transmission control.

* - Start character Host telegramm

- 1.6 05.07.05 F. Guthof

2.6 TELEGRAMM FORMAT

SC ADR : COMMAND : SEQ : STAT : MESSAGE-FIELD : CS EM

SC Start character STAT Status of sender

* For ethernet connection it can be any number

Structure of message field:

DES : NO : VAL : NO : VAL : ... : DES : NO : VAL : ...

DES Designation (PV,CS...) NO Channel Number

2.7 Transmission formats for date and time

DAT = Day , Month , Year / Hour , Minute , Second

AGE = Hour , Minute

- 1.6 05.07.05 F. Guthof

2.7 TABLE NUMBERS

Process Display PVAL Table for process values

2.8 RANGE OF VALUES FOR DATA TRANSMISSION FIELDS

- Byte 0 ... 255

2.9 RESPONSE TELEGRAMMS OF SUBSTATIONS

1. Command telgramm begins with * and ends with @

- 1.6 05.07.05 F. Guthof

2.10 TMEOUT AND REPETITION

Refer to the following example for better understanding:

Host sends command *1:DR:0:0:569@ and receives error telegramm or no

- 1.6 05.07.05 F. Guthof

2.11 END OF DATA TRANSMISSION

2.12 DATA SECURITY

2.13 CHECK SUM

2.14 BLOCK TRANSMISSION

- 1.6 05.07.05 F. Guthof

3 TRANSMISSION VOLUME AND DEFINITION OF DATA FIELDS

3.1 STATUS DEFINITION DIRECTION: HOST Ù SUBSYSTEM

D0 Local / Remote 1: Remote

The sum of all bit values is transmitted as integer number (decimal)!

- 1.6 05.07.05 F. Guthof

3.2 OPERATING MODES HOST Ù SUBSYSTEM

Designation: - String BC "Batch Control"

Number: - Byte 1: Local/Remote Setting

3.3 PROCESS VALUES HOST Õ SUBSYSTEM

Designation: - String PV "Process Value"

3.4 ALARM PARAMETERS PROCESS VALUES HOST Ù SUBSYSTEM