Emerson Process Management MLT 2, MLT 5, MLT 4, MLT 1, MLT 3 User Manual

...

Instruction Manual

90003752 1 1/2003

Instruction Manual

AK Protocol Communication Option for ML T 1, MLT 2, MLT 3, MLT 4, MLT 5 and CAT 200

Edition 11/2003

www.EmersonProcess.com

AK Protocol for ML T 1, 2, 3, 4, 5 & CAT 200 Instruction Manual

90003752

11/2003

ESSENTIAL INSTRUCTIONS

READ THIS P AGE BEFORE PROCEEDING!

Emerson Process Management (Rosemount Analytical) designs, manufactures and test s its products to meet many national and international standards. Because these instruments are sophisticated technical products, you MUST properly install, use, and maintain them to ensure they continue to operate within their normal specifications. The following instructions MUST be adhered to and integrated into your safety program when installing, using and maintaining Emerson Process Management (Rosemount Analytical) products. Failure to follow the proper instructions may cause any one of the following situations to occur: Loss of life; personal injury; property damage; damage to this instrument; and warranty invalidation.

• Read all instructions prior to installing, operating, and servicing the product.

• If you do not understand any of the instructions, contact your Emerson Process

Management (Rosemount Analytical) representative for clarification.

• Follow all warnings, cautions, and instructions marked on and supplied with the product.

• Inform and educate your personnel in the proper installation, operation, and

maintenance of the product.

• Install your equipment as specified in the Installation Instructions of the appropriate

Instruction Manual and per applicable local and national codes. Connect all products

to the proper electrical and pressure sources.

• T o ensure proper performance, use qualified personnel to install, operate, update, program, and maintain the product.

• When replacement parts are required, ensure that qualified people use replacement parts specified by Emerson Process Management (Rosemount Analytical). Unauthorized parts and procedures can affect the product’s performance, place the safe operation of your process at risk, and VOID YOUR W ARRANTY. Look-alike substitutions may result in fire, electrical hazards, or improper operation.

• Ensure that all equipment doors are closed and protective covers are in place, except when maintenance is being performed by qualified persons, to prevent electrical shock and personal injury.

The information contained in this document is subject to change without notice. Misprints reserved.

1st Edition 10/1998 2nd Edition 11/2001

Emerson Process Management GmbH & Co. OHG

Industriestrasse 1 D-63594 Hasselroth Germany T +49 (0) 6055 884-0 F +49 (0) 6055 884-209 Internet: www.EmersonProcess.com

Contents

V24/RS232/485 Interface – Basics 1 - 1

1 Introduction.................................................................................................1 - 1

2 Hardware....................................................................................................1 - 2

3 Protocol settings.........................................................................................1 - 3

3.1 Command telegram .............................................................................1 - 3

3.2 Response telegram..............................................................................1 - 4

3.3 Command telegram for RS485 BUS operating....................................1 - 5

3.4 Response telegram for RS485 BUS operating.....................................1 - 6

4 Specifications of data settings ....................................................................1 - 7

4.1 Head telegram (Header) ......................................................................1 - 7

4.2 Data block and error status byte..........................................................1 - 8

4.3 End of telegram....................................................................................1 - 9

4.4 Command and response telegram timing............................................1 - 10

4.5 Handling of malfunctions......................................................................1 - 10

5 Examples for potential responses to control or write commands resp.

to command telegrams with data (format) errors........................................1 - 11

6 Function sequence and error status after the receipt of the

"SRES" or "STBY" commands....................................................................1 - 19

II) V24/RS232/485 Interface – Single Analyzers and Systems 2 - 1

1 Basic Informations......................................................................................2 - 2

2 List of all Codes [Commands - Overview including page numbers]......2 - 5

2.1 Control commands...............................................................................2 - 5

2.2 Read commands..................................................................................2 - 6

2.3 Write commands..................................................................................2 - 7

3 Description of all Control Commands .........................................................2 - 8

4 Description of all Read Commands ............................................................2 - 39

5 Description of all Write Commands.............................................................2 - 85

Supplement

1 Overview about working AK commands in NGA devices ..........Supplement - 1

2 AK Service Commands..............................................................Supplement - 3

90003752(2) [AK-Commands] 11/01

90003752(1) [AK-Commands] 10/98

I) V24/RS232/485-Interface - Basics

Protocol settings of a serial interface

between a test bench control computer

and peripheral analyzers on exhaust test benches

1. Introduction

The serial interface is made for slow point to point connections (f ≤ 10 Hz). The communication between the test bench control computer (TBCC) and the peripheral analyzers works according to the master slave principle. That means that the peripheral analyzers will only answer with a response telegram to the command telegram of the TBCC. They will not send an own message.

You can distinguish two cases: (1) Analyzers in a function unit (system)

Some analyzers are combined to a logical unit. They are connected to the TBCC via an front-end computer. In that case the communication will not take place directly between the TBCC and the analyzers, but between the TBCC and the front-end computer. Each analyzer or the whole system unit will be identified by a defined channel number: K0 is the channel number for the whole defined system. ("Assembling command resp. assembling report") Kn (n=1, nmax) is the channel number for each analyzer. KV is the channel number for the front-end computer.

(2) Single analyzers

Each analyzer is connected directly to the TBCC. In that case the identification of each analyzer will be done by the hardware connections and not by a software control. That is why the two channel number bytes (Kn) could be deleted. But in spite of that the channel number is generally 0 (K0) to get a uniform protocol.

The data transfer will only be done by ASCII code to get an easy handling of the protocol with a terminal for simulation of the TBCC, the system unit and the analyzers. Therefore, no parity check will be done as data saving.

90003752(2) [AK-Commands] 11/01

1 - 1

2. Hardware

1. Baud rate: 1200, 2400, 4800, 9600, 19200

2. Length of signs: 1 start bit 7 or 8 data bits 1 or 2 stop bits

3. Parity: even/odd/none

4. Operating: full duplex, no echo

5. Handshake: Xon/Xoff

6. Plug: 9 pin sub d, socket

7. Pin assignment: RS 232 module

GND

Rxd TxD

Relay 1 contact NC/NO Relay 2 contact NC/NO

Relay 3 contact NC/NO Relay common node

GND

RS 485 module

GND

RxDRxD+ TxD+

TxD-

1 - 2

Relay 1 contact NC/NO Relay 2 contact NC/NO

Relay 3 contact NC/NO Relay common node

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

3. Protocol settings

The data and command transfer protocol has the following structure:

3.1. Command telegram

1. Byte STX

2. Byte DON'T CARE

3. Byte FUNCT. CODE 1

4. Byte FUNCT. CODE 2 HEAD

5. Byte FUNCT. CODE 3

6. Byte FUNCT. CODE 4

7. Byte BLANK

8. Byte "K" VARIABLE DATA

9. Byte NUMBER

(number with several

digits possible)

D A (other data T can also disappear, A depending on the function code)

n. Byte ETX END

90003752(2) [AK-Commands] 11/01

1 - 3

3.2. Response telegram

1. Byte STX

2. Byte DON'T CARE

3. Byte FUNCT. CODE 1

4. Byte FUNCT. CODE 2 HEAD

5. Byte FUNCT. CODE 3

6. Byte FUNCT. CODE 4

7. Byte BLANK

8. Byte ERROR STATUS

FIXED

DATA

D A VARIABLE DATA T (can also disappear, A depending on the function code)

n. Byte ETX END

1 - 4

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

3.3. Command telegram for RS485 BUS operating

1. Byte STX

2. Byte BUS ADDRESS

3. Byte FUNCT. CODE 1

4. Byte FUNCT. CODE 2 HEAD

5. Byte FUNCT. CODE 3

6. Byte FUNCT. CODE 4

7. Byte BLANK

8. Byte "K" VARIABLE DATA

9. Byte NUMBER

(Number with several

digits possible)

D A (other data T can also disappear, A depending on the function code)

n. Byte ETX END

90003752(2) [AK-Commands] 11/01

1 - 5

3.4. Response telegram for RS485 BUS operating

1. Byte STX

2. Byte BUS ADDRESS

3. Byte FUNCT. CODE 1

4. Byte FUNCT. CODE 2 HEAD

5. Byte FUNCT. CODE 3

6. Byte FUNCT. CODE 4

7. Byte BLANK

8. Byte ERROR STATUS

FIXED

DATA

D A VARIABLE DATA T (can also disappear, A depending on the function code)

n. Byte ETX END

1 - 6

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

4. Specifications of data settings

4.1. Head telegram (Header)

The begin of each transfer is a "STX" in the first byte. Each "STX" will start a new transfer. Previous transfers will be deleted, if they are not finished by "ETX". That means, only completed telegrams may be interpreted and answered.

You can take any content for the "DON'T CARE" byte, excluding control signs or signs reserved by the AK commands. For the RS485 BUS operating an address byte will be used instead of the "DON'T CARE" byte. The analyzers will only answer to this command if the bus address setup will concur with this byte.

In the command telegram a function code will be sent to the system unit or the analyzer with the four function bytes.

In the response telegram this function code will be sent back as an echo if the transfer is successful. The echo will be four question marks (????), if

• the command telegram has not minimum the number of bytes of the head telegram, the

channel number in the data part and the end telegram (number of bytes = 10; using a channel number with two digits = 11 bytes) or

• the function code has errors or is unknown.

The function code may not contain blanks. There are three groups of function codes: (1) Control commands

(2) Read commands (3) Write commands

90003752(2) [AK-Commands] 11/01

1 - 7

4.2. Data block and error status byte

The data presentation is variable. A fixed format will not be used. A blank or a <CR> with <LF> will be used as separating characters of data. The separation with <CR><LF> will only be done, if the following complete date will have more than 60 digits. Each data set will begin normally with a blank.

The data block of the command telegram has only variable data. These data depend on the function code. They can disappear for some function codes excluding the channel number. The channel number can have more than two bytes.

The data block of the response telegram is divided in fixed and variable data. The first digit of the fixed data is a blank followed by an error status byte. The error status number will be zero for an error free running analyzer or system unit. The error status number will be counted up from 1 to 9 with each change in the error status. The error status number will be zero again after the errors will be removed. Changing the status of the system will not change the error status number. The variable data depend on the function code. They can disappear for some function codes.

The long and variable floating point format or the E- Format are allowed to display the digits of numbers. You can find in each analyzer protocol which of these formats may be used. The decimal point can disappear for integers. The "+/-" sign may only be used for negative numbers. Digits without physical meaning have to be vanished.

You can distinguish the following cases if a date with an error exists for a reading: (1) The transfer of the date is not possible, e.g. an analyzer in a system is missing or it

cannot send a signal. → The date will be replaced by a "#".

(2) The date is only valid with restrictions, e.g. FID temperature too low.

→ The date will begin with a "#". Range overflow and range underflow will be displayed in the same way. "Valid" means that no criterions of plausibility will be considered. Example: You ask for a concentration value and the analyzer is in the "stand-by" mode. The date must not be marked with "#" as "valid with restrictions", if the analyzer would work normally in the operation mode.

1 - 8

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

If an analyzer or a system is not in the "REMOTE" status, the control and write commands have to report "OF" ("Offline") in the data set to the. In system units the channel number has to be reported, too.

If one analyzer is missing, a system unit has to send the channel number and "NA" ("Not Available") to the test bench control computer with control and write commands.

A response telegram is not possible, if the test bench control computer has a direct contact to the analyzers and one analyzer is missing or the whole system is missing. So the test bench control computer has to realize the missing of devices by "Time Out".

If the system or the analyzer is occupied by executing a function, the new start of a control command will lead to the response "BS" (Busy) in the data block of the response telegram. The running function will not be disturbed. Exception: The order was a software reset.

If the data or parameters transfer is not complete (i.e. not expected format) in the command telegram to the system or the analyzer, the test bench control computer will get a "SE" (Syntax Error) in the data block of the following response telegram.

If the system or the analyzers cannot work with the data or the parameters of the command telegram (data error, parameter error), the test bench control computer will get a "DF" (data error) in the data block of the following response telegram.

4.3. End of telegram

Each transfer will end with "ETX" in the last byte.

90003752(2) [AK-Commands] 11/01

1 - 9

4.4. Command and response telegram timing

For each command telegram of the TBCC the peripheral analyzer sends a response telegram. It is not allowed for the TBCC to send new command telegrams before this response telegram is received.

For most of the command telegrams this response might be sent after some milliseconds. But for some commands the response telegram might be started to sent 2-3 seconds after receiving the command telegram. The time starts the moment the peripheral analyzer receives the ETX character of the command telegram. It is not assured that the response telegram is sent without any delay between the single characters but it might be that there are up to 2-3 seconds in between.

4.5. Handling of malfunctions

For the case of a malfunction it might be that the ETX-character of the command telegram is not received by the peripheral analyzer. Then it will not evaluate the command telegram and so will not send a response telegram.

In this case it is in the responsibility of the TBCC not to run into an endless loop. It has to have a timeout of 4-5 seconds to react on this communication failure. The TBCC may repeat the last command telegram or doing some other exception handling.

1 - 10

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

5. Examples for potential responses to control or write commands resp. to command telegrams with data (format) errors:

1. Analyzer and/or system unit with several analyzers "Online"

and called analyzers are existing.

1. Byte STX

2. Byte

DON'T

CARE

3. Byte C

4. Byte O

5. Byte D

6. Byte E

7. Byte BLANK

8. Byte x Error status byte

evtl.

variable

...

Data n. Byte ETX

Error status byte: Value is zero: Device without error. Value is not zero: Device with one or more errors.

90003752(2) [AK-Commands] 11/01

1 - 11

2. Analyzer and/or system unit with several analyzers "Offline" and called analyzers are existing.

1. Byte STX

2. Byte

DON'T

CARE

3. Byte C

4. Byte O

5. Byte D

6. Byte E

7. Byte BLANK

8. Byte x Error status byte

9. Byte BLANK

10. Byte K

11. Byte n

12. Byte BLANK

13. Byte O

14. Byte F

evtl.

variable

...

Data n. Byte ETX

Error status byte: Value is zero: Device without error. Value is not zero: Device with one or more errors.

11. Byte: Channel number is zero: "The whole system unit offline".

Channel number is one to n: "Single analyzer offline".

1 - 12

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

3. Called system unit "online", called single analyzer not available.

If the test bench control computer will call the devices directly and the system unit or the analyzer are not available, you will not get any response telegram. So, the test bench control computer will have to realize the missing of the system or of the analyzer by "Time Out".

1. Byte STX

2. Byte

DON'T

CARE

3. Byte C

4. Byte O

5. Byte D

6. Byte E

7. Byte BLANK

8. Byte x Error status byte

9. Byte BLANK

10. Byte K

11. Byte n

12. Byte BLANK

13. Byte N

14. Byte A

15. Byte ETX

Error status byte: Value is zero: Device without error Value is not zero: Device with one or more errors

11. Byte: Channel number one to n: "Called device not available".

90003752(2) [AK-Commands] 11/01

1 - 13

4. Called system unit "offline", called single analyzer not available.

1. Byte STX

2. Byte

DON'T

CARE

3. Byte C

4. Byte O

5. Byte D

6. Byte E

7. Byte BLANK

8. Byte x Error status byte

9. Byte BLANK

10. Byte K

11. Byte 0

12. Byte BLANK

13. Byte O

14. Byte F

15. Byte BLANK

16. Byte K

17. Byte n

18. Byte BLANK

19. Byte N

20. Byte A

21. Byte ETX

1 - 14

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

Error status byte: Value is zero: Device without error. Value is not zero: Device with one or more errors.

11. Byte: Channel number zero: "System unit offline"

17. Byte: Channel number one to n: "Called device not available.

90003752(2) [AK-Commands] 11/01

1 - 15

5. Called unit or channel is busy with a running function.

1. Byte STX

2. Byte

DON'T

CARE

3. Byte C

4. Byte O

5. Byte D

6. Byte E

7. Byte BLANK

8. Byte x Error status byte

9. Byte BLANK

10. Byte K

11. Byte n

12. Byte BLANK

13. Byte B

14. Byte S

15. Byte ETX

Error status byte: Value is zero: Device without error. Value is not zero: Device with one or more errors.

11. Byte: Channel number is zero: "The whole unit is busy".

Channel number is one to n: "Single analyzer is busy".

1 - 16

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

6. The data are incomplete or the data do not have the expected format.

1. Byte STX

2. Byte

DON'T

CARE

3. Byte C

4. Byte O

5. Byte D

6. Byte E

7. Byte BLANK

8. Byte x Error status byte

9. Byte BLANK

10. Byte K

11. Byte n

12. Byte BLANK

13. Byte S

14. Byte E

15. Byte ETX

Error status byte: Value is zero: Device without error. Value is not zero: Device with one or more errors.

90003752(2) [AK-Commands] 11/01

1 - 17

7. The data or the parameters do not have the expected size.

1. Byte STX

2. Byte

DON'T

CARE

3. Byte C

4. Byte O

5. Byte D

6. Byte E

7. Byte BLANK

8. Byte x Error status byte

9. Byte BLANK

10. Byte K

11. Byte n

12. Byte BLANK

13. Byte D

14. Byte F

15. Byte ETX

Error status byte: Value is zero: Device without error. Value is not zero: Device with one or more errors.

1 - 18

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

6. Function sequence and error status after the receipt of the 'SRES' or 'STBY' commands

1. The test bench control computer is sending the control command SRES (Reset)

to the system unit or any single analyzer.

All running functions or procedures will be canceled. An initializing will start, that is analogous to the switching on of the system unit or the analyzer: CPU and memory check, regulating or controlling of required temperatures, igniting of the flame in a FID an so on. The operation mode of the system or analyzer is "stand-by" during the initializing, even if the device is not ready and error free. That means, the status STBY will be reported to the read command ASTZ. The test bench control computer can only realize with the read command ASTF (error status), if the device is ready for measurements. The device will be ready to measure, if the essential functions of the current measuring instruction will be error free.

Example: The status of the system unit or analyzer is SXYZ. The test bench control computer

sends SRES:

Test bench control computer sends SRES Kn → System or analyzer will response SRES x

The system unit or the analyzer will cancel the status SXYZ. It will run a CPU and memory check and it will control the temperatures. If the temperatures are out of the allowed setpoint range, the device will regulate it. The FID will control the flame and will try to ignite it, if necessary, and so on. The test bench control computer will read the operation mode and the error status:

Test bench control computer sends ASTZ Kn → System or analyzer will response ASTZ 0 SMAN STBY

Test bench control computer sends ASTZ Kn System or analyzer will response ASTZ x SMAN STBY

Test bench control computer sends ASTF Kn System or analyzer will response ASTF x n

The error status byte will be zero and the system or the analyzer will be ready to measure, if all temperatures are in the allowed setpoint range, if the FID flame is burning etc. If these parameters are not correct, the error status byte will be different from zero. The test bench control computer will read the operation mode and the error status as long as the system or the analyzer will be ready to measure. The test bench control computer will control the maximum time for this reading.

90003752(2) [AK-Commands] 11/01

1 - 19

2. The test bench control computer is sending the control command STBY (Standby) to the system unit or any single analyzer.

There are two different cases:

! If the system or the analyzer is resting, this mode will be finished. Then, it will be tried to

get the stand-by mode ready for an error free measurement. The system or the analyzer will regulate all temperatures to the required setpoints, that were down during the resting. The FID will control the flame burning and if necessary it will try to ignite the flame etc. The operation mode of the system or analyzer is "stand-by" during these checkups, even if the device is not ready and error free. That means, the status STBY will be reported to the read command ASTZ. The test bench control computer can only realize with the read command ASTF (error status), if the device is ready for measurements. The device will be ready to measure, if the essential functions of the current measuring instruction will be error free.

Example: The system or the analyzer is resting. No error is existing. The test bench control

computer will ask for the operation mode:

Test bench control computer sends ASTZ Kn → System or analyzer will response ASTZ 0 SREM SPAU

Test bench control computer sends STBY. System or analyzer shall accept the stand-by mode:

Test bench control computer sends STBY Kn → System or analyzer will response STBY 0

The system or analyzer is finishing the resting. Then, it will try to get the stand-by mode for an error free measurement. The system or analyzer will check the conditions: Are all temperatures in the setpoint range ? Is the FID flame burning ? etc. The test bench control computer will read the operation mode:

Status is error free:

Test bench control computer sends ASTZ Kn → System or analyzer will response ASTZ 0 SREM STBY

or status has still some errors:

Test bench control computer sends ASTZ Kn → System or analyzer will response ASTZ x SREM STBY

Test bench control computer sends ASTF Kn → System or analyzer will response ASTF x n

1 - 20

90003752(2) [AK-Commands] 10/01

I) V24/RS232/485-Interface - Basics

# The system or the analyzer is in the operation mode SXYZ. This mode will be finished.

Then, it will be tried to get the stand-by mode ready for an error free measurement. If there will be an error in the function SXYZ, the system or the analyzer will try to remove this error to get the stand-by mode ready for an error free measurement (i.e. FID flame is not burning, the FID will try to ignite). The operation mode of the system or analyzer is "stand-by" during these check-ups, even if the device is not ready and error free. That means, the status STBY will be reported to the read command ASTZ. The test bench control computer can only realize with the read command ASTF (error status), if the device is ready for measurements. The device will be ready to measure, if the essential functions of the current measuring instruction will be error free.

Example: The system or the analyzer is in the operation mode SXYZ. An error is existing with the

error number n, i.e. FID flame is not burning. The test bench control computer will ask for the error status:

Test bench control computer sends ASTF Kn → System or analyzer will response ASTF x n

Test bench control computer sends STBY. System or analyzer shall accept the stand-by mode and get ready for an error free measurement:

Test bench control computer sends STBY Kn → System or analyzer will response STBY x

The system or analyzer is finishing the operation mode SXYZ. Then, it will try to get the stand-by mode for an error free measurement. The system or analyzer will check the conditions and will try to remove the error, i.e. ignition of the FID flame. The test bench control computer will read the operation mode:

Error is removed (e.g. Flame was ignited):

Test bench control computer sends ASTZ Kn → System or analyzer will response ASTZ 0 SREM STBY

or Error is still existing (e.g. Flame has not been ignited):

Test bench control computer sends ASTZ Kn → System or analyzer will response ASTZ x SREM STBY

Test bench control computer sends ASTF Kn → System or analyzer will response ASTF x n

The error status byte will be zero and the system or the analyzer will be ready to measure, if the error is removed i.e. the FID flame is still burning. If these parameters are not correct, the error status byte will be different from zero. The test bench control computer will read the operation mode and the error status as long as the system or the analyzer will be ready to measure. The test bench control computer will control the maximum time for this reading.

90003752(2) [AK-Commands] 11/01

1 - 21

1 - 22

90003752(2) [AK-Commands] 10/01

II) V24/RS232/485 Interface - Single Analyzers and Systems

Specifications of the criterions and codes for the communication between

• the front-end computer (system computer) of an exhaust analyzer system and the test

bench control computer.

• each analyzer of an exhaust analyzer system and the test bench control computer.

• the front-end computer (system computer) of an exhaust analyzer system and their

single devices. The following measurement systems and equipments can also be such single devices.

• the front-end computer (system computer) of a fuel consumption analyzer and a test

bench control computer.

• the front-end computer (system computer) of an SHED measurement equipment and

the test bench control computer. (SHED: Sealed Housing for Evaporative Determination)

• the front-end computer (system computer) of a sampling system and the test bench

control computer.

The computer of an analyzer or of a system will be named as FU (Function Unit) and the test bench control computer will be abbreviated with TBCC.

90003752(1) [AK-Commands] 10/98

2 - 1

1. Basic Informations

You can distinguish three cases:

(1) Exhaust analyzer system:

Some analyzers are combined logically. That means, these analyzers are connected with the TBCC via an front-end computer (system computer). The communication does not take place directly between the TBCC and the analyzers, but it will take place via the frontend computer. The identification of each device resp. of the whole system will be done by a channel number. K0 means the whole configured analyzer system ("assembling command resp. assembling report"). Kn (n=1, nmax) means each physical available analyzer. KV means the corresponding front-end computer.

Some analyzers and the sampling devices or systems (e.g. CVS equipment, particle sampler, sampling system, etc.) are combined logically. That means, these analyzers are connected with the TBCC via an front-end computer (system computer). The communication does not take place directly between the TBCC and the devices or systems, but it will take place via the front-end computer. The identification of each device and system will be done by a channel number. The handling of the analyzers will be like described above. All the other devices or systems can only be called directly by the corresponding channel number. The front-end computer must know the mnemonics of these devices and systems. Furthermore, the front-end computer has to be able to send orders and read commands to the channels resp. to send responses to the TBCC.

(2) Single exhaust analyzers (single channel analyzers):

All analyzers are connected to the TBCC individually. So, an identification of the analyzers by the software would not be necessary, because the analyzers are identified by their hardware connections. But to get a homogeneous protocol, the channel number will be indicated with K0.

(3) Single exhaust analyzers (multi channel analyzers):

All analyzers are connected to the TBCC individually, but they measure more than a single component (e.g. CO and C02). The identification by the software is necessary, because it will call the single channels resp. components. That is why such a single analyzer will be treated like a system.

2 - 2

90003752(3) [AK-Commands] 11/03

II) V24/RS232/485 Interface - Single Analyzers and Systems

The codes determined in this manual are valid for the communication between

• the TBCC and the front-end computer of an exhaust analyzer system.

• the front-end computer of an exhaust analyzer system and the corresponding single

devices.

• the TBCC and the single exhaust analyzers connected directly to the TBCC.

• the TBCC and other exhaust measuring or analyzing devices or equipments connected

directly to the TBCC.

The floating point format is valid for the signal transfer.

The physical units are determined as follows:

• Exhaust values: ppm

• Temperatures: K

• Pressures: Pa

• Flow: l/min

The analyzer system or each analyzer can be set to the operation mode "MANUAL" selecting "REMOTE DISABLE" for the parameter "REMOTE EN-/DISABLE". This setup does not depend on the previous status of the system or analyzer.

If you select "REMOTE ENABLE", the mode "MANUAL" will retain for the moment, but the TBCC can call this operation mode with a control command. If the TBCC will setup the system/the analyzer to "REMOTE", the system/the analyzer will execute control commands from the TBCC. Precondition: The system/the analyzer is able to start the function selected.

In the mode "REMOTE DISABLE", the TBCC can only send read commands. It is only possible to read signals and status informations. If then the system or the analyzer is in the mode "MANUAL", it will ignore the control command from the TBCC. No change of the error status will be done in the response to the TBCC. Instead of that the response will display "MANUAL" as first date.

The same will be valid, if the parameter is "REMOTE ENABLE", but the TBCC did switch the system/the analyzer to the mode "MANUAL".

Otherwise, the operation mode can only be recognized by reading the status. This is also valid during a test is running.

90003752(1) [AK-Commands] 10/98

2 - 3

If it is possible in a system to put single channels together to lines, so the following definition will be valid:

A line is the summary of "1-x" analyzers to a logical group "y", that can be switched physically to a gas channel "z". Each device can only be assigned to one line at the same time. If you will try to assign a channel to another line and this channel is already assigned, the front-end computer will send as response "DF" (data error). The organization of each defined line will be done in the front-end computer (CODE KV Ln ...). The order must be sent to the front-end computer "KV". A line will be dissolved by the configuration without assignment of channels (CODE KV Ln) or by the reset order (SRES). All available gas inputs can be assigned to a defined line. So it is possible to assign different lines to different gas sampling points, e.g. in front of a catalyst, behind a catalyst. If the gas running time will change in such cases, you have to regard for it.

2 - 4

90003752(3) [AK-Commands] 11/03

+ 110 hidden pages