Endress+Hauser Modbus Liquistation CSF22 Instruction Manual

® MODBUS ist a registered Trademark of Modbus Organization, Inc.
© Copyright Dez. 2011
Liquistation CSF22
Modbus® Guideline
Valid from:
Software version 1.04.00
Document: E+H Liquistation CSF22 Modbus Guideline, Revision 2
Initial release 15-Dec-2011
Current release 31-May-2013
SD01212C/07/EN/01.13
71224018
Author:
Endress+Hauser
Gesellschaft für Mess- und Regeltechnik mbH+Co. KG
Dieselstr. 24
70839 Gerlingen
Deutschland

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
2 © Copyright Dez. 2011
Table of contents
1. Introduction............................................................................................................................................. 4
1.1. Scope ................................................................................................................................................... 4
1.2. Purpose................................................................................................................................................ 4
1.3. Who should use this document? ........................................................................................................... 4
1.4. Abbreviations and definitions................................................................................................................ 4
1.5. References............................................................................................................................................ 4
2. Device identification ................................................................................................................................ 5
2.1. Operation mode ................................................................................................................................... 5
2.1.1. ASCII ............................................................................................................................................ 5
2.1.2. RTU .............................................................................................................................................. 5
2.2. Register Addressing .............................................................................................................................. 6
3. Function description ................................................................................................................................ 7
3.1. Communication module 485................................................................................................................ 7
3.2. Modbus function codes ........................................................................................................................ 7
3.2.1. FC03 Read Holding Register .......................................................................................................... 8
3.2.2. FC04 Read Input Register .............................................................................................................. 8
3.2.3. FC08 Diagnostics (nur seriell)........................................................................................................ 8
3.2.4. FC16 Write Multiple Register ........................................................................................................ 9
3.2.5. FC23 Read/Write Multiple Register............................................................................................. 10
3.3. Modbus Exception Codes ................................................................................................................... 10
3.4. Performance....................................................................................................................................... 11
3.4.1. Power up .................................................................................................................................... 11
3.4.2. Non-volatile memory................................................................................................................... 11
3.4.3. Reaction delay ............................................................................................................................. 11
3.4.4. Modbus Response time................................................................................................................ 11
4. Installation & Wiring .............................................................................................................................. 13
5. Commissioning ...................................................................................................................................... 14
5.1. Local configuration of the device ........................................................................................................ 14
5.2. Configuration of the Modbus RS485 interface..................................................................................... 14
5.2.1. Settings ....................................................................................................................................... 14
5.2.2. Selecting Bus address and Identnumber ....................................................................................... 14
5.3. Communication control („Watchdog“) ............................................................................................... 15
5.4. Configuration of the process data for Modbus ..................................................................................... 15
5.4.1. AI Analog values (Device Modbus).......................................................................................... 16
5.4.2. DI Digital values (Device Modbus).......................................................................................... 16
5.4.1. AO Analog values (Modbus Device)........................................................................................ 17
5.4.2. DO Digital values (Modbus Device) ........................................................................................ 17
5.4.3. Overview of possible setpoint parameter ...................................................................................... 17
5.5. Process values .................................................................................................................................... 18
5.5.1. Units ...................................................................................................................................... 18
5.5.2. Status ..................................................................................................................................... 18
6. Diagnostics ............................................................................................................................................ 19
6.1. Status signal ....................................................................................................................................... 19
6.2. Diagnostic messages ........................................................................................................................... 20
6.2.1. Device related diagnostic ............................................................................................................. 20
6.3. Communication related errors ............................................................................................................ 21
6.3.1. Termination ................................................................................................................................ 21
6.3.2. Error counter............................................................................................................................... 21
7. Tables.................................................................................................................................................... 22
7.1. Data types .......................................................................................................................................... 22
7.1.1. Float (IEE-754)............................................................................................................................ 22
7.1.2. Integer ........................................................................................................................................ 22
7.1.3. String .......................................................................................................................................... 22
7.1.4. Date............................................................................................................................................ 22
7.1.5. Other data types .......................................................................................................................... 23
7.2. Unit codes and data sources................................................................................................................ 23

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 3
7.3. Parameter........................................................................................................................................... 23
7.3.1. Process values (Holding Register: FC 03, 16, 23) ......................................................................... 23
7.3.2. Configuration (Holding Register: FC 03, 16, 23) .......................................................................... 26
7.3.3. Process values (Input Register: FC 04) ......................................................................................... 26
7.3.4. Diagnose (Input Register: FC 04) ................................................................................................. 28
7.3.5. Identification (Input Register: FC 04) ........................................................................................... 29

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
4 © Copyright Dez. 2011
1. Introduction
1.1. Scope
The Endress+Hauser liquid sampler CSF22 complies with the Modbus protocol.
This document specifies all the device specific features and documents Modbus protocol implementation details.
The functionality of this field device is described sufficiently to allow the proper application in a process and the
complete support in Modbus capable host applications.
1.2. Purpose
This specification is designed to complement the operating instructions by providing a complete, unambiguous
description of this field device from a Modbus communication perspective.
1.3. Who should use this document?
The specification is designed to be a technical reference for Modbus capable host application developers, system
integrators and knowledgeable end users. It also provides functional specifications (e.g., commands, enumerations
and performance requirements) used during field device development, maintenance and testing. This document
assumes the reader to be familiar with Modbus protocol requirements and terminology.
1.4. Abbreviations and definitions
n. A.: Not applicable
NaN: Not a number (an IEEE-754 floating point value representing no number, 7F A0 00 00h)
ENP: Electronic nameplate
1.5. References
BA473C: Liquistation CSF22 Operating instructions (Commissioning).
BA477C: Liquistation CSF22 Operating instructions (Maintenance & diagnostics).
BA476C: Liquistation CSF22 Operating instructions (Operation & settings).
BA475C: Liquistation CSF22 Operating instructions (Calibration).
MB-APPL (Modbus application layer documentation): “Modbus Protocol Specification” and “Modbus Serial Line
Protocol and Implementation Guide”, free download at www.modbus-ida.org

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 5
2. Device identification
Manufacturer name: Endress+Hauser
Model name: Liquistation CSFxx
Device revision: 1
Physical layers supported: RS485
Physical device category: Transmitter, DC isolated bus device
The nameplate is located on the right side of the housing and indicates the model name, order codes, serial number
and software version. The device revision and Modbus address are shown in the setup menu.
Menu/Setup/General settings/Extended setup/Modbus
2.1. Operation mode
At any time one of the following fieldbus protocols can be active:
•Modbus RS485 (ASCII)
•Modbus RS485 (RTU)
2.1.1. ASCII
The data are transmitted as ASCII characters. They are readable for human.
Start
Address
Function
Data
LRC
End
1 character
2 characters
2 characters
N characters
2 characters
2 characters
= „:“
CRLF
Field
length
Info
Client
Server
Address
2 Byte
Identification of target device
Set by client
Copied from request
to response
LRC
2 Bytes
Modbus specification
Set by client
Set by server
2.1.2. RTU
The data are transmitted as binary code. They are compact.
Address
Function
Data
CRC16
1 character
1 character
N characters
2 characters
0 = Broadcast
247 = Unicast
Hint:
Between two Modbus telegrams must be a delay of mind. 3.5 characters.
Field
length
Info
Client
Server
Address
1 Byte
Identification of target device
Set by client
Copied from request
to response
CRC16
2 Bytes
Modbus specification
Set by client
Set by server

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
6 © Copyright Dez. 2011
2.2. Register Addressing
Register
Datatyp
Access
Address range*
Info
Discretes Inputs
Bit
Read only
1XXXX
Not used by device
Coils
Bit
Read / write
2XXXX
Not used by device
Input Register
16-Bit Word
Read only
3XXXX
These data can only be read from
the device
Holding Register
16-Bit Word
Read / write
4XXXX
These data can be read from the
device and changed by the
application.
* The register address is transferred as 16 bit word where the first register is addressed with the value 0. In this
document the register addresses are given the same way as they are used in the Modbus telegrams.
Hint:
In some Modbus application notes the register addresses are counted starting with 1. In this cases in the Modbus
telegram is transferred the address -1.

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 7
3. Function description
3.1. Communication module 485
The measuring device is an assembly of modules, which are connected to a backplane residing inside a casing. For
using Modbus communication a 485 module has to be present with appropriate licensing.
3.2. Modbus function codes
Liquistation supports the following Modbus function codes:
Function
code FCxx
Name Description
03 READ HOLDING REGISTER
Reading one or several register of the Modbus slave
1 to max. 125 successional register can be read (1 register = 2
bytes) with one telegram.
Usage:
This function code is used to read register with read/write
access.
04 READ INPUT REGISTER
Reading one or several register of the Modbus slave
1 to max. 125 successional register can be read (1 register = 2
bytes) with one telegram.
Usage:
This function code is used to read register with read access.
08 DIAGNOSTICS
This function code is used to check the communication
between Master and Slave.
The following sub function codes are supported:
• Sub-function 00 = Return Query Data (Loopback test)
•Sub-function 02 = Return Diagnostics Register
16 WRITE MULTIPLE REGISTERS
This function code is used to write several registers with a
single request. Up to 123 successional registers can be written.
All parameters addressed by the written registers need to be
writable, otherwise the query is answered with an exception
ILLEGAL DATA VALUE.
23 READ/WRITE
MULTIPLE REGISTERS
This function code is used to write several registers and read
several registers with one single Modbus transaction. Up to
118 successional registers can be read and written. The write
operation is executed before the read
Hint:
•Broadcast messages are possible only with function codes 06, 16 and 23.

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
8 © Copyright Dez. 2011
3.2.1. FC03 Read Holding Register
This function reads one or several holding registers. Up to 125 successional registers can be read.
Request
Function code
1 Byte
0x03
Starting Address
2 Bytes
0x0000 to 0xFFFF
Quantity of Registers
2 Bytes
1 to 125 (0x7D)
Response
Function code
1 Byte
0x03
Byte count
1 Bytes
2 * Quantity of registers
Holding register value
(2 * Quantity of registers) Bytes
2 to 250
Error
Error code
1 Byte
0x83
Exception code
1 Bytes
01 or 02 or 03 or 04
3.2.2. FC04 Read Input Register
This function code is used to read one or several input registers. Up to 125 successional registers can be read.
Request
Function code
1 Byte
0x04
Starting Address
2 Bytes
0x0000 to 0xFFFF
Quantity of Registers
2 Bytes
1 to 125 (0x7D)
Response
Function code
1 Byte
0x04
Byte count
1 Bytes
2 * Quantity of registers
Input register value
(2 * Quantity of registers) Bytes
2 to 250
Error
Error code
1 Byte
0x84
Exception code
1 Bytes
01 or 02 or 03 or 04
3.2.3. FC08 Diagnostics (nur seriell)
This function code is used to test the Modbus communication between the client (master) and the server (slave)
and to check for various error conditions within the server. Sending not supported sub-function codes cause an
ILLEGAL DATA VALUE response.
Function code
1 Byte
0x06
Sub-function
2 Bytes
Data
N x 2 Bytes
Response
Function code
1 Byte
1 Byte
Sub-function
2 Bytes
Data
N x 2 Bytes

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 9
Error
Error code
1 Byte
0x88
Exception code
1 Bytes
01 or 03 or 04
Sub function 0x00: Return Query Data (Loopback)
The data passed in the request data field is to be returned (looped back) in the response.
Example:
Request
Function code
0x08
Sub-function
0x00
Data
0x01 0x02 0x03 0x04
Response is identical to Request
Function code
0x08
Sub-function
0x00
Data
0x01 0x02 0x03 0x04
Sub function 0x02: Return diagnostic register
The content of the 16-bit Modbus diagnostics register is returned. The diagnostic register provides information
about the device status and the location of an error condition. Multiple bits may be set.
Parameter
Register
Bit
MB_FC08_DIAGNOSE
500
0
Reserviert = 0
1
Reserviert = 0
2
Reserviert = 0
3
Reserviert = 0
4
Reserviert = 0
5
Reserviert = 0
6
Reserviert = 0
7
Reserviert = 0
8
General device error is present, description category see bits
12…15
9..11
Reserviert = 0
12
Status signal F (Failure)
13
Status signal C (Function check)
14
Status signal M (Maintenance required)
15
Status signal S (Out of specification)
Hint:
The definition of the status signal is according NAMUR NE107. Further information is in the operation manual
BA477C: Liquistation CSF22 Operating instructions (Maintenance & diagnostics).
3.2.4. FC16 Write Multiple Register
This function code is used to write several registers with a single request. All parameters addressed by the written
registers need to be writable, otherwise the query is answered with an exception ILLEGAL DATA VALUE.
Request
Function code
1 Byte
0x10
Starting Address
2 Bytes
0x0000 to 0xFFFF
Quantity of Registers
2 Bytes
0x0001 to 0x007B
Byte Count
1 Byte
(2 * Quantity of registers) Bytes
Register Value
(2 * Quantity of registers) Bytes
value

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
10 © Copyright Dez. 2011
Response
Function code
1 Byte
0x10
Sub-function
2 Bytes
0x0000 to 0xFFFF
Quantity of Registers
2 Bytes
1 to 123 (0x7B)
Error
Error code
1 Byte
0x90
Exception code
1 Bytes
01 or 02 or 03 or 04
3.2.5. FC23 Read/Write Multiple Register
This function code is used to write several registers and read several registers with one single Modbus transaction.
The write operation is executed before the read.
Holding registers are addressed starting at zero. Therefore holding registers 1-16 are addressed in the PDU as 0-15.
The request specifies the starting address and number of holding registers to be read as well as the starting address,
number of holding registers, and the data to be written. The byte count specifies the number of bytes to follow in
the write data field.
The normal response contains the data from the group of registers that were read. The byte count field specifies the
quantity of bytes to follow in the read data field.
Request
Function code
1 Byte
0x17
Read starting address
2 Bytes
0x0000 to 0xFFFF
Quantity to read
2 Bytes
0x0001 to 0x007D
Write starting address
2 Bytes
0x0000 to 0xFFFF
Quantity to write
2 Bytes
0x0001 to 0x0079
Write byte count
1 Byte
2 x (Quantity to write)
Write register value
2 x (Quantity to write)
Response
Function code
1 Byte
1 Byte
Sub-function
2 Bytes
Data
N x 2 Bytes
Error
Error code
1 Byte
0x97
Exception code
1 Bytes
01 or 03 or 04
Hint:
This function code can be used to exchange all process variables with one single Modbus request.
3.3. Modbus Exception Codes
Erkennt der MODBUS Slave einen Fehler im Anforderungstelegramm des Masters, sendet er als Antwort dem
Master eine Fehlermeldung bestehend aus Slave-Adresse, Funktionscode, Fehlercode (Exception Code) und
Prüfsumme. Als Kennzeichnung, dass es sich um eine Fehlermeldung handelt, wird das Führungsbit des
zurückgesendeten Funktionscodes gesetzt. Die Fehlerursache wird über den Fehlercode (Exception Code) an den
Master übertragen.
Exception Code
Info
01
ILLEGAL_FUNCTION
Der vom Master gesendete Funktionscode wird vom Messgerät (Slave) nicht unterstützt.
02
ILLEGAL_DATA_ADDRESS

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 11
Das vom Master adressierte Register ist nicht belegt (d.h. es existiert nicht), oder die Länge
der abgefragten Daten ist zu groß.
03
ILLEGAL_DATA_VALUE
Der Master versucht in ein Register zu schreiben, welches nur einen Lesezugriff erlaubt.
Der Wert, der in dem Datenfeld erscheint, ist nicht zulässig: z.B. Bereichsgrenzen
überschritten oder falsches Datenformat.
04
SLAVE_DEVICE_FAILURE
Der Slave hat auf das Anforderungstelegramm des Masters nicht geantwortet bzw. bei der
Verarbeitung des Anforderungstelegramms ist ein Fehler aufgetreten.
3.4. Performance
3.4.1. Power up
On power up, the transmitter has to initialize itself, which takes up to 2 minutes. During this period, the device
will not respond to any Modbus communication.
As soon as the operation view appears on the display the Liquistation is ready to communicate via Modbus, no
matter if there are errors present or not.
3.4.2. Non-volatile memory
The device‘s configuration parameters are saved into a flash memory. It takes approximately 5 seconds after the
execution of the write command that the data will be saved. Data consistency is always ensured.
3.4.3. Reaction delay
The reaction delay is different depending on the direction of the data flow.
Modbus to Device
Received data is send without delay to the internal component processing this data. The internal components have
a fixed sampling rate of 3 Hz.
Device to Modbus
The reaction delay is defined as the time span between the moment a process value assumes a new value and this
value is replied to the Modbus client.
3.4.4. Modbus Response time
The device is limited to handle one Modbus transaction each 300 ms. Any first Modbus request is replied without
delay. The reply to a follow-up request is delayed for 300 ms after the last reply.

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
12 © Copyright Dez. 2011
If more than one Modbus client is present the performance of the Modbus network can be optimized by requesting
information from different Modbus clients in an orderly schedule. The following diagram shows an example for a
schedule consisting of one Modbus client and 4 Modbus servers.

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 13
4. Installation & Wiring
Please refer to this product documentation:
BA473C: Liquistation CSF22 Operating instructions (Commissioning).
Modbus M12 socket and pin assignment:
1P5V, 5 V power supply for external
terminating resistor
2A (GN), signal RxD/TxD-N
3P0V, reference potential for P5V
4B (RD), signal RxD/TxD-P
5n.c., not connected
* Shield
* = Thread

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
14 © Copyright Dez. 2011
5. Commissioning
5.1. Local configuration of the device
All settings can be done at the display of the device or remotely via the service interface.
For the service interface connect the Commubox FXA291 and use the software FieldCare.
Note:
For further information please refer to the following documentation:
BA473C: Liquistation CSF22 Operating instructions (Commissioning).
BA476C: Liquistation CSF22 Operating instructions (Operation & settings).
5.2. Configuration of the Modbus RS485 interface
5.2.1. Settings
Settings
Default settings
selection
Bus address
247
1 ... 247
Transmission mode
RTU
RTU, ASCII
Baud rate/bps
19200
1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200
Parity
even (1 Stopbit)
even (1 Stopbit), Uneven (1 Stopbit), non (2 Stopbits)
Path: Menu/Setup/General settings/Extended setup /Modbus/Settings:
5.2.2. Selecting Bus address and Identnumber
Liquistation CSF22 supports two options to set the Modbus Address:
1.
by Menu
Software-Addressing
2.
by Modbus
Software-Addressing
Step 1
Step 2
Step 3
Step 4

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 15
Step 5 Step 6 Step 7 Step 8
Valid Modbus addresses are in the range from 1 to 247.
Step
Description
Example
1
Enter Menue/Setup/General Settings
Press “Extended setup”
2
Press “Modbus”
3
Press “Settings”
4
Set Busaddress
Press “Bus address”
5
Enter and confirm Bus address “88”
6
Set Transmission Mode
Enter to select Transmission Mode
7
Set Baudrate
Enter to select Baudrate
8
Set Parity
Enter to select Parity
9
Save Settings
Press softkey “Save” to save the selected settings
Note:
The Modbus settings are switched active only after being saved.
5.3. Communication control („Watchdog“)
Does the device not receive a Modbus telegram within the configured time out, the diagnostic message S969 will
be set.
The time out can be set to values between “0” (deactivated) to 999 seconds.
Path: Menu/Setup/General settings/Extended setup /Modbus/Settings
5.4. Configuration of the process data for Modbus
Via Modbus communication the device can send several device variables or receive Modbus variables. The device
variables may be analog or digital values from the device or send to the device. The commissioning of the data for
the cyclic data exchange requires the steps selection of the device variable and selection of the data source. The
following number of device variables are available:
Abbre-
viation
Qty
Name
Description
Example
AI
16
Analog Input
Analog value from the device
Flow measured by binary input
or analog current input
DI
8
Digital Input
digital value from the device
Read limit switch
AO
4
Analog Output
Analog value into the device
Flow measured by external MID
DO
8
Digital Output
digital value into the device
Start sampling

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
16 © Copyright Dez. 2011
5.4.1. AI Analog values (Device

Modbus)
Path: Menu/Setup/Outputs/Modbus/AI 1 (Analog Input)
Function
Option
Description
Data source
Select data source
•any of the list
Default setting
•
none
Which data sources are in the list depends of the device
configuration.
Measured value
Select measured value
•depending of
source
Default setting
•
none
The available measured value depends of the data
The device variables are configured accordingly to the given example of configuring the device variable 0 (Analog
Input AI1) to the analog current input of the CSF22.
Step 1
Step 2
Step 3
Step 4
Step 5 Step 6 Step 7
Step
Description
Example
1
Select the device variable
Press “AI 1 (Analog Input)”
2
Select the source of data
Press “Source of data”
3
Press e.g. “Temperature S:1”
4
Select the measured value of this source of
data
Press “Measured value”
5
Press e.g. “Temperature”
6
Verify the assignment
Press “Modbus assignment view”
7
Check assignment of “AI 1 (Analog Input)”
5.4.2. DI Digital values (Device

Modbus)
Path: Menu/Setup/Outputs/Modbus/DI 1 (Digital Input)
Function
Option
Description
Data source
Select data source
•any of the list
Default setting
•none
Which data sources are in the list depends of the device
configuration.

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 17
5.4.1. AO Analog values (Modbus

Device)
The parameters transferred via Modbus to the device can be used and configured accordingly to the given example
of configuring the Limit switch 1 to the Analog Ouput 1 value (AO 1) of the control system. This means the Limit
switch 1 monitors the AO 1 value from Modbus and switches accordingly the configured limit value.
Step 1 Step 2 Step 3 Step 4
Step 5
Step 6
Step 7
Step
Description
Example
Select a Component which uses a selectable
data source as input. In this example we use a
Limit switch
Press “Limit switches”
1
Press “Limit switch 1”
2
Select the Source of data
Press “Source of data”
3
Press “Modbus”
4
Select the value of this Source of data
Press “Measured value”
5
Press “Modbus AO 01
6
Verify the assignment
Check assignment of “Controlled variable”
5.4.2. DO Digital values (Modbus

Device)
Digital values transferred via Modbus to the device can be used as trigger for an action in the device.
For example a sampling cycle can be triggered with a DO device variable. The configuration is similar to the use of
the AO (Analog Output variables).
5.4.3. Overview of possible setpoint parameter
Path: The selection of the device variables is done in the menu of the relevant function.
Path
Used Modbus function block
Menu/Setup/Additional functions/Limit switch/data source
Modbus AO x
Menu/Setup/Additional functions/Cleaning/Cleaning X/Start signal
Modbus DO x
Menu/Setup/General Settings/Hold Settings/External Hold
Modbus DO x
Menu/Setup/Logbooks/Data logbooks/Data source
Modbus AO x / DO x
Menu/Display/User definable screens/Data source
Modbus AO x / DO x

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
18 © Copyright Dez. 2011
Menu/Setup/Sampling Programs/Setup program/Advanced/Start condition
Modbus
Menu/Setup/Sampling Programs/Setup program/Advanced/Start signal
Modbus DO x
Menu/Setup/Sampling Programs/Setup program/Advanced/Stopp condition
Modbus
Menu/Setup/Sampling Programs/Setup program/Advanced/Stopp signal
Modbus DO x
Menu/…/Advanced/Setup subprogram/Sampling modus
Modbus
Menu/…/Advanced/ Setup subprogram/Sampling signal
Modbus DO x
Menu/…/Advanced/ Setup subprogram/Bottle change
Modbus DO x
Menu/…/Advanced/ Setup subprogram/Change signal
Modbus DO x
Menu/…/Advanced/ Setup subprogram/Sub program activation
Modbus
Menu/…/Advanced/ Setup subprogram/Activation signal
Modbus DO x
5.5. Process values
The process values start at register 40001 (Holding Register 0) or 30001 (Input Register 0). With the input register
you can access read-only process values. A write request is only possible to Holding Register.
Each process value is transmitted with unit and status. The status indicates the reliability of the process value.
5.5.1. Units
To each process value is a unit assigned. The unit depends of the process value and is not changeable. An
exception is the unit of the temperature. This can be changed with the Holding Register 1016.
5.5.2. Status
To each process value is a status assigned which indicates the reliability of the process value. The status can have
the following values:
HEX DEZ Quality Description
0 0 Good The value is usable.
1 1 Uncertain The value is possibly not accurate.
2 2 Bad The value is not usable.
3 3 Not assigend To the Modbus variable is no measurement value assigned.

Liquistation CSF22 MODBUS®-Guideline
Endress+Hauser
© Copyright Dez. 2011 19
6. Diagnostics
6.1. Status signal
The current status of the device is shown in the status signal. It can be read via Modbus and is indicated at the
display of the device. Either it corresponds to ‘no diagnostic condition detected’ or is one of the following
categories.
Diagnostic category Description
F Failure
The measurement value is not reliable. The reason is most
likely at this measurement point. A connected control system
should be operated manually.
C Function Check Maintenance work is executed at the device. Wait until end of
this work.
S Out of Specification
The measurement point operates out of the specification.
Measurement is still possible with less accuracy, higher
wearout or shorter live time of the material. The reason is in
the process environment of the measurement point.
M Maintenance required
Measurement functionality is given and all values are reliable.
A maintenance work is required to avoid failure or break
down.
The current status can be read with the Modbus diagnose function code #08 or directly as parameter.
Parameter
Register
Bit
MB_FC08_DIAGNOSE
500
0
Reserviert = 0
1
Reserviert = 0
2
Reserviert = 0
3
Reserviert = 0
4
Reserviert = 0
5
Reserviert = 0
6
Reserviert = 0
7
Reserviert = 0
8
General device error is present, description category see bits
12…15
9..11
Reserviert = 0
12
Status signal F (Failure)
13
Status signal C (Function check)
14
Status signal M (Maintenance required)
15
Status signal S (Out of specification)
The diagnostic category F, C, S, M can be edited for every diagnostic message.
Path for device related diagnostic messages:
Menu/Setup/General Settings/Extended Settings/Diagnostic settings/Diagnostic behavior

Liquiline CM44x Modbus Guideline V1.0
Endress+Hauser
20 © Copyright Dez. 2011
6.2. Diagnostic messages
The device features via Modbus register detailled informations to current diagnostic messages with the highest
priority and for the last fallen diagnostic message.
The diagnostic codes and the related remedy measures are described in the operation manual BA477C.
6.2.1. Device related diagnostic
Current active diagnostic message with the highes priority:
Parameter
Input
Register
Datatyp
Information
DEVICE_CURRENT_DIAG_MODUL
504
UNSIGNED16
Slot number of the module.
DEVICE_CURRENT_DIAG_PORT
505
UNSIGNED8
Connector on the module
DEVICE_CURRENT_DIAG_NE107_STATUS
506
UNSIGNED8
Bit 0: Failure (F)
Bit 1: Function Check (F)
Bit 2: Maintenance required(M)
Bit 3: Out of specification (S)
Bit 4-7: reserviert = 0
DEVICE_CURRENT_DIAG_CODE
507
UNSIGNED16
Diagnostic code (0..999)
DEVICE_CURRENT_DIAG_TIMESTAMP
508
UNSIGNED32
Timestamp (seconds since 1.1.1970)
DEVICE_NUMBER_ADDITIONAL_DIAG
510
UNSIGNED8
Number of further active diagnostic
messages with lower priority. A full list
of all messages is shown on the local
display.
Last fallen diagnostic message (the reason for the message is not given any more, therefor the diagnostic message is
withdrawn)
Parameter
Input
Register
Datentyp
Info
DEVICE_LAST_DIAG_MODUL
512
UNSIGNED8
See above
DEVICE_LAST_DIAG_PORT
513
UNSIGNED8
DEVICE_LAST_DIAG_NE107_STATUS
514
UNSIGNED8
DEVICE_LAST_DIAG_CODE
515
UNSIGNED16
DEVICE_LAST_DIAG_TIMESTAMP
516
UNSIGNED32