OPERATIONS MANUAL

ba76148e05 05/2017

IQ SENSORNET
Fieldbus linking
LINKING THE IQ S ENSORNET TO A FIELDBUS
 Fieldbus linking

For the most recent version of the manual, please visit

www.ysi.com.

Contact YSI
1725 Brannum Lane
Yellow Springs, OH 45387 USA
Tel: +1 937-767-7241
800-765-4974
Email: [email protected]
Internet: www.ysi.com

Copyright © 2017 Xylem Inc.

2 ba76148e05 05/2017
Fieldbus linking Contents

IQ SENSORNET Fieldbus linking -

Contents

1 Linking the IQ SENSORNET to a fieldbus . . . . . . . . . . . . . 5

1.1 Interfaces of the IQ SENSORNET . . . . . . . . . . . . . . . . . . . . 5
1.2 Linking the IQ SENSORNET . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.1 Linking the IQ SENSORNET via the RS485
interface ............................. 5
1.2.2 Linking the IQ SENSORNET via the Ethernet interface
6

2 Installing the interface in the IQ SENSORNET . . . . . . . . . 7

2.1 Installing the RS485 interface . . . . . . . . . . . . . . . . . . . . . 7
2.2 Mounting the Phoenix connector . . . . . . . . . . . . . . . . . . . 9
2.3 Installing the Ethernet interface . . . . . . . . . . . . . . . . . . . 10
2.3.1 Communication via Ethernet . . . . . . . . . . . . . . . 11
2.3.2 Ethernet connection in case of indoor
installation . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.3 Ethernet connection in case of outdoor installation
(DIQ/S28X-E[F]) . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.4 Ethernet connection in case of outdoor installation
(MIQ/MC2, MIQ/MC3) . . . . . . . . . . . . . . . . . . . . 11

3 Configuring the IQ SENSORNET . . . . . . . . . . . . . . . . . . . 14

3.1 Configuring the IQ SENSORNET for Profibus . . . . . . . . . . 14
3.1.1 Setting the PROFIBUS address . . . . . . . . . . . . 14
3.1.2 GSD file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2 Configuring the IQ SENSORNET for Modbus RTU . . . . . . 16
3.2.1 Setting the Modbus interface parameters . . . . . 16
3.3 PROFIBUS / Modbus RTU checklist . . . . . . . . . . . . . . . 17
3.4 Configuring the IQ SENSORNET for Ethernet fieldbuses . 18
3.4.1 GSDML file for Profinet . . . . . . . . . . . . . . . . . . . 19
3.4.2 EDS file for Ethernet-IP . . . . . . . . . . . . . . . . . . . 19
3.5 Assigning the sensor numbers . . . . . . . . . . . . . . . . . . . . 19
3.5.1 Creating the assignment of sensor numbers . . 20
3.5.2 Changing the assignment of sensor numbers . . 20
3.5.3 Creating the identical assignment of sensor
numbers in several systems . . . . . . . . . . . . . . . 22

4 Communication with fieldbuses . . . . . . . . . . . . . . . . . . 23

4.1 Profibus DP(V0), Profinet . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1.1 Profinet module (query format) . . . . . . . . . . . . . 24
4.1.2 Profibus modules (query formats) . . . . . . . . . . . 24
4.1.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

ba76148e05 05/2017 3
Contents IQ SENSORNET Fieldbus linking

4.1.4 Data of a module . . . . . . . . . . . . . . . . . . . . . . . . 25

4.1.5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.2 Profibus DPV1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2.1 Modules (query formats) . . . . . . . . . . . . . . . . . . 27
4.2.2 Data query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.3 Data block of the sensors . . . . . . . . . . . . . . . . . 29
4.2.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.3 EtherNet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.1 Modules (query formats) . . . . . . . . . . . . . . . . . . 32
4.3.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.3 Data block of the sensors . . . . . . . . . . . . . . . . . 32
4.3.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.4 Profibus DP(V0) and EtherNet/IP
Query of individual sensors . . . . . . . . . . . . . . . . . . . . . . 36
4.4.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.4.2 Data block for sensor selection (output data of
the PLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.4.3 Data block of the sensors (input data of the
PLC) ............................. 38
4.4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.5 Communication with Modbus RTU, Modbus TCP . . . . . 40
4.5.1 Data transmission . . . . . . . . . . . . . . . . . . . . . . . 40
4.5.2 Query format . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.5.3 Data block of the sensors . . . . . . . . . . . . . . . . . 41
4.5.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5 Encoded data for fieldbus communication . . . . . . . . . 45

5.1 Data formats of the sensor datablock . . . . . . . . . . . . . . . 45
5.2 Sensor status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.3 Measured value status . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.4 Signaling the sensor status and measured value status in
the IQ SENSORNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.4.1 Display in the measured value display on the
terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.4.2 Measured value transmitted on fieldbus level . . 49
5.5 Sensor model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.6 Status info of sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.7 Measuring mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6 What to do if ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.1 PROFIBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.2 Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.3 Ethernet fieldbuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

7 Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.1 Ordering & Technical Support . . . . . . . . . . . . . . . . . . . . 59
7.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4 ba76148e05 05/2017
IQ SENSORNET Fieldbus linking Linking the IQ SENSORNET to a fieldbus

1 Linking the IQ SENSORNET to a fieldbus

1.1 Interfaces of the IQ SENSORNET
The IQ SENSORNET system provides interfaces for the following net-
works:

Fieldbus Interface type IQ SENSORNET components with interfaces

Modbus RTU RS485 YY-MOD YY = DIQ/S 28X,
MIQ/MC3
Profibus YY-PR DIQ/S 182, MIQ/MC2
Modbus TCP Ethernet DIQ/S 28X-EF ZZ = PR, MOD
MIQ/MC3(-ZZ)
Ethernet/IP MIQ/MC2(-ZZ)
Profinet Ethernet DIQ/S 28X-EF
MIQ/MC3(-ZZ)

1.2 Linking the IQ SENSORNET

1.2.1 Linking the IQ SENSORNET via the RS485 interface

Steps Profibus Modbus

1 Establish the physical connection section 2.1
2 Configure the interface of the section 3.1 section 3.2
IQ SENSORNET
3 Program the queries and access GSD file
authorization * section 3.1.2
section 4.1 section 4.5
section 4.2
section 4.4

4 Interpret the data of the section 5 ff

IQ SENSORNET
* Configure the order of the sensors in the IQ SENSORNET (see section
3.5)

ba76148e05 05/2017 5
Linking the IQ SENSORNET to a fieldbus IQ SENSORNET Fieldbus linking

1.2.2 Linking the IQ SENSORNET via the Ethernet interface

Steps Ethernet IP Profinet Modbus TCP

1 Establish the physical connection section 2.3
2 Configure the interface of the section 3.4
IQ SENSORNET
3 Program the queries and access section 4.1 section 4.5
authorization *
EDS file GSDML file
section 3.4.2 section 3.4.1
4 Interpret the data of the section 5 ff
IQ SENSORNET
* Configure the order of the sensors in the IQ SENSORNET (see section
3.5)

6
IQ SENSORNET Fieldbus linking Installing the interface in the IQ SENSORNET

2 Installing the interface in the

IQ SENSORNET
2.1 Installing the RS485 interface
Profibus and Modbus use the same interface (RS485) for data
exchange.

We especially recommend the "Aufbaurichtlinie PROFIBUS/FMS",

published by the PROFIBUS user organization PNO, (PNO order num-
ber 2.111) with many practical tips for installation that also apply to
Modbus systems
(http://www.profibus.com/download/installation-guide/).

Further instructions for the installation and operation of a Modbus net-

work are available on the Internet at www.modbus.org.

The PROFIBUS user organization e.V. (PNO) provides detailed infor-

mation on the subject of PROFIBUS on the Internet at
www.profibus.com.

Connecting the Profibus The Profibus / Modbus cable is connected to the IQ SENSORNET using
/ Modbus cable a 9-pin D-SUB connector on the top of the housing.

Suitable cables Fieldbus type Cables

Profibus PROFIBUS cable
Modbus Cable for RS485 (e.g. PROFIBUS cable)

Connectors to be used Manufacturer Type

Phoenix Contact GmbH & Co. VS-09-PROFB-SC
KG (Phoenix article no. 1654549, with
Flachsmarkt 8 screwed contacts,
32825 Blomberg available from YSI under the
Germany order no. 902 888Y)
http://www.phoenixcontact.com
VS-09-PROFB-SP
(Phoenix article no. 1654345, with
spring contacts)

To remove the blind plug, lift the safety bracket with a suitable screw
driver at both clamps on the left and right side (see Fig. 2-1).

ba76148e05 05/2017 7
Installing the interface in the IQ SENSORNET IQ SENSORNET Fieldbus linking

1
1 Safety bracket

OK

er !
Pow

Fig. 2-1 Removing the safety bracket (example: MIQ/MC2, MIQ/MC3)

CAUTION
If water gets into the enclosure of a module with internal power
supply, there is danger of an electric shock.
If water gets into the enclosure of an MIQ module, there is a risk
of short circuits.
To prevent the enclosures of the IQ SENSORNETfrom being pene-
trated by water the following must be observed:
 Follow the safety instructions of the IQ SENSORNET system op-
erating manual.
 Use connectors recommended by YSI only.
 When the connector is removed, the connection socket of the
IQ SENSORNET must be closed with the blind plug and secured
with the safety bracket.

8
IQ SENSORNET Fieldbus linking Installing the interface in the IQ SENSORNET

2.2 Mounting the Phoenix connector

MIQ/(MC)2 - MOD MIQ/(MC)2 - PR

MIQ/(MC)3 - MOD or PR

approx. 100 mm approx. 100 mm

DIQ/S 182 - MOD or PR DIQ/S 28X - MOD or PR

approx. 100 mm

M C S

DIQ/S 284 ESC OK

UNIVERSAL TRANSMITTER

USB

M C S
OK
appro
ESC

Fig. 2-2 IQ SENSORNET modules with Phoenix connector

ba76148e05 05/2017 9
Installing the interface in the IQ SENSORNET IQ SENSORNET Fieldbus linking

Phoenix connector IQ SENSORNET instrument

Wire Terminals Pin Potential at Function
(color*) instrument
connector
1 -
2 -
red 1B and 2B 3 B line Positive RxD/TxD according to RS 485 specifica-
tion
4 RTS Request To Send
5 GND BUS Reference potential for data wires and terminating
resistors
6 +5 V BUS Supply voltage for terminating resistors
7 -
green 1A and 2A 8 A line Negative RxD/TxD according to RS 485 specifica-
tion
9 -

* Wire colors when using a standard PROFIBUS cable.

Please observe the operating manual of the connector.

2.3 Installing the Ethernet interface

The IQ SENSORNET system can be linked to a LAN via the following
modules:
 MIQ/MC2, MIQ/MC3
 DIQ/S 28X-E[F]

Basic knowledge of network engineering is helpful when establishing a

local network.
Depending on the network configuration, several settings have to be
made on the individual network components.
Settings that concern network components from third-party manufac-
turers (such as the router) are only referred to in general here. Detailed
information in which menus the settings should be done are given in the
respective operating manual of your instrument.
If you have no network knowledge, please contact your network admin-
istrator.

10
IQ SENSORNET Fieldbus linking Installing the interface in the IQ SENSORNET

Profinet, Modbus TCP and Ethernet IP use the same inter-

face (Ethernet) and the same cable type (Ethernet) for data
exchange.

2.3.1 Communication via Ethernet

The IQ SENSORNET provides an interface for Fast Ethernet

(100 MBit/s).
If configured as a DHCP client, the IQ SENSORNET can automatically
get its IP settings from a DHCP server in the network.

2.3.2 Ethernet connection in case of indoor installation

The Ethernet cable is connected to the IQ SENSORNET via the RJ45

connector of the following modules:
 MIQ/MC2, MIQ/MC3
 DIQ/S 28X-E[F]

2.3.3 Ethernet connection in case of outdoor installation

(DIQ/S28X-E[F])

To ensure a safe Ethernet communication with outdoor installation, the

moisture protection (ADA/E) available as an accessory has to be
mounted. Installation instructions are given with the accessory.

2.3.4 Ethernet connection in case of outdoor installation

(MIQ/MC2, MIQ/MC3)

When plugged in, the RJ45 socket is not sufficiently protected against
moisture. With outdoor installation, the Ethernet cable must therefore
be clamped directly on the PCB of the MIQ/MC2 or MIQ/MC3 controller
to ensure a safe Ethernet communication. For this purpose there is a
4-pole LSA terminal strip and a shielding terminal on the main PCB. An
LSA punch down tool is required for the assembly.

Connecting the Ethernet

1 Open the MIQ module.
cable with the main PCB
2 Disconnect the flat flexible cable (pos. 1 in Fig. 2-4) from the
main PCB.

ba76148e05 05/2017 11
Installing the interface in the IQ SENSORNET IQ SENSORNET Fieldbus linking

MIQ/MC2 1

2
Fig. 2-3 Ethernet connection with RJ45 socket (MIQ/MC2)

MIQ/MC3 1

2
Fig. 2-4 Ethernet connection with RJ45 socket (MIQ/MC3)

3 Unscrew the RJ45 socket enclosure (pos. 2 in Fig. 2-4).

4 Screw a cable gland with sealing ring into the free duct. Then
loosen the cap nut of the cable gland.

12
IQ SENSORNET Fieldbus linking Installing the interface in the IQ SENSORNET

LSA terminal strip

X10 X9 X8 X7

Rx-

Rx+

Tx-

Tx+
SHIELD CLAMP

ENTHERNET CABLE

3
Fig. 2-5 Ethernet connection via terminal strip
(example: MIQ/MC2, MIQ/MC3 likewise)

5 Strip the Ethernet cable for approx. 2 cm and untwist the Rx+,
Rx-, Tx+ and Tx wires.
6 Carefully slash the cable shield (foil + netting) lengthwise and
put it backwards over the cable sheath (pos. 3 in Fig. 2-5).
7 Feed the Ethernet cable through the cable gland into the mod-
ule housing.
8 Where the cable shield was put backwards, press the Ethernet
cable into the shielding terminal (pos. 4 in Fig. 2-5). The shield-
ing terminal must contact the cable shield across a wide area.
9 Connect the Rx+, Rx-, Tx+ and Tx- wires to the LSA terminal
strip with the aid of an LSA punch down tool. Make sure that
the cable assignment agrees with the specification on the ter-
minal label under the terminal strip.
10 Fasten the cap nut of the screwed cable gland.
11 Close the module.

ba76148e05 05/2017 13
Configuring the IQ SENSORNET IQ SENSORNET Fieldbus linking

3 Configuring the IQ SENSORNET

3.1 Configuring the IQ SENSORNET for Profibus

3.1.1 Setting the PROFIBUS address

Opening the setting

1 Open the setting menu with <S>.
menu for Profibus
2 For MIQ/MC2, MIQ/MC3, DIQ/S28X-E[F]:
Press <> and <OK> to select and confirm the menu
item, Settings bus interfaces
3 Select and confirm the bus interface with <> and
<OK>.

Settings Setting Selection/Valu Explanation

es
Device address 1 ... 126 Instrument address of the
IQ SENSORNET in the Profibus

If the Profibus data connection is working, there are the fol-

lowing entries in the menu for Profibus settings:
* Online (data exc): Yes
* Baud rate: 19.2 kbit/s (no value when there is no connec-
tion)

4 Edit the settings.

To accept all settings, you have to highlight the Save and

quit menu item at the lower end of the setting table and to
confirm with <OK>. If you exit the setting table via <M>,
<ESC>/Quit or the Quit menu item, all changes are
ignored.

Checking the A functioning Profibus data connection is displayed in the menu for Pro-
connection (general) fibus settings (see above).

LEDs A functioning Profibus data connection is additionally displayed by two

(MIQ/MC2, MIQ/MC3) LEDs on the Profibus module.

14
IQ SENSORNET Fieldbus linking Configuring the IQ SENSORNET

MIQ/MC2

1 2
Fig. 3-1 LEDs on the Profibus module (MIQ/MC2)
1 lights up green: Data connection OK
2 lights up green: Voltage OK

MIQ/MC3

1 2
Fig. 3-2 LEDs on the Profibus module (MIQ/MC3)
1 lights up green: Data connection OK
2 lights up green: Voltage OK

ba76148e05 05/2017 15
Configuring the IQ SENSORNET IQ SENSORNET Fieldbus linking

3.1.2 GSD file

The GSD file contains all necessary information on the Profibus module
and is required by the configuration program of the Profibus master.
The current GSD file is provided on the Internet at www.YSI.com.

3.2 Configuring the IQ SENSORNET for Modbus RTU

3.2.1 Setting the Modbus interface parameters

Opening the setting

1 Open the setting menu with <S>.
menu for Modbus RTU
2 For MIQ/MC2, MIQ/MC3, DIQ/S28X-E[F]:
Press <> and <OK> to select and confirm the menu
item, Settings bus interfaces
3 Select and confirm the bus interface with <> and
<OK>.

Settings
Setting Selection/Valu Explanation
es
Device 1 ... 247 Instrument address of the
address IQ SENSORNET in the Modbus
RTU
Baud rate 1200 Baud rate
2400
4800
9600
19200
38400
57600
Parity None Parity
Even
None
Odd
(2 stop bits)
Even
(1 stop bit)
Odd
(1 stop bit)

4 Edit the settings.

16
IQ SENSORNET Fieldbus linking Configuring the IQ SENSORNET

To accept all settings, you have to highlight the Save and

quit menu item at the lower end of the setting table and to
confirm with <OK>. If you exit the setting table via <M>,
<ESC>/Quit or the Quit menu item, all changes are
ignored.

3.3 PROFIBUS / Modbus RTU checklist

The following checklist supports you when planning, projecting and
installing a PROFIBUS or Modbus RTU system with the
IQ SENSORNET. For smooth operation, you should be able to answer all
questions with "Yes".
 Is the [bus system] (bus segment) installed without branch lines?
 Was the correct cable used (e.g. PROFIBUS cable, see section
2.1)?
 Are the poles of the signal lines A line and B line correctly connected
at all bus connections?
 Is it guaranteed that there is no short-circuit between A line, B line
and cable shielding?
 Is the shielding installed free of interruptions?
 Are the guidelines for shielding and grounding being observed, and
doesn't any unallowed potential equalization current flow via the
shielding?
 Is the maximum cable length (per bus segment) observed for the
corresponding baud rate?
 Do all devices support the required baud rate?
 Only for Profibus:
With 12 Mbit/s transmission rate only: Are the bus plugs suitable for
this baud rate?
 Are exactly two terminators switched on at the ends of the [bus sys-
tem] (bus segment)?
 Are the terminators supplied with voltage so the following applies:
UB line - UA line > + 500 mV?
 Do all devices have individual bus addresses?
 After changing the bus address, have the devices been restarted
(switched off and on again)?
Note: The IQ SENSORNET does not have to be restarted.
 Do the addresses projected in the master correspond to the actual
addresses?
 Only for Profibus:
Are all addresses less than or equal to the parameter HSA and less

ba76148e05 05/2017 17
Configuring the IQ SENSORNET IQ SENSORNET Fieldbus linking

than 126 (HSA = Highest Station Address)?

 Only for Profibus:
Is the currently valid GSD being used? If you are in doubt, download
it from the Internet.
 Only for Profibus:
Have admissible bus parameters been set only? If you are in doubt
set them to default values.
 Is consistent access to a sensor data block by the bus master
ensured?
 After commissioning:
Do all devices signal error-free behavior?
(IQ SENSORNET: status "Online" in the measured value and status
display).
 Only for Profibus:
A functioning Profibus connection displays the following entries in
the menu for Profibus settings (<S>/Settings bus interfaces/Profi-
bus):
* Online (data exc): Yes
* Baud rate: 19.2 kbit/s (no value when there is no connection)
Only for MIQ/MC2 and MIQ/MC3:
A functioning data connection is additionally displayed by two LEDs
on the Profibus module (see section 3.1.1).

3.4 Configuring the IQ SENSORNET for Ethernet fieldbuses

Opening the settings

1 Open the setting menu with <S>.
menu
2 Press <> and <OK> to select and confirm the menu
item, System settingsTCP/IP settings

Setting Selection/ Explanation

Values
DHCP Yes The IQ SENSORNET is configured as a DHCP client.
If a DHCP server is in the network, the IQ SENSORNET
receives all other network settings from the DHCP server.
No The IQ SENSORNET is not configured as a DHCP client.
All other settings have to be done as required.
IP address Address Permanent IP address for the IQ SENSORNET in the LAN
(if DHCP No).

18
IQ SENSORNET Fieldbus linking Configuring the IQ SENSORNET

Setting Selection/ Explanation

Values
Subnet mask Address Subnet mask (if DHCP No).
The subnet mask depends on the network size (for small
networks: e.g. 255.255.255.0).
DNS server Address Entry for fieldbus not required.
For a connection with the Internet (if DHCP No), e.g.:
 IP address of the DNS server in the network
 Entry of IP address or e.g. 127.0.0.1
Standard gateway Address Entry for fieldbus not required.
For a connection with the Internet (if DHCP No), e.g.:
 IP address of the instrument establishing the access to
the Internet
 Entry of IP address or e.g. 127.0.0.1

3.4.1 GSDML file for Profinet

The GSDML file contains all necessary information on the Profinet

module and is required by the configuration program for the Profinet
master.

The current GSDML file is available on the Internet at www.YSI.com.

3.4.2 EDS file for Ethernet-IP

The EDS file contains information on the Ethernet-IP module. It is eval-

uated by some configuration programs.

The current EDS file is available on the Internet at www.YSI.com.

3.5 Assigning the sensor numbers

The basis for data transmission between the superordinate control sys-
tem (PLC) and the IQ SENSORNET is formed by the unique assignment
of a sensor to its sensor number (Sxx) in the IQ SENSORNET system.
During the initial commissioning, the sensor numbers are assigned by
the system in the order in which the sensors are recognized by the sys-
tem.

Preparation of the IQ SENSORNET for communication with a fieldbus

may require, e.g. the following:
 Creating an IQ SENSORNET system with specific assignment of sen-

ba76148e05 05/2017 19
Configuring the IQ SENSORNET IQ SENSORNET Fieldbus linking

sor numbers to sensors

 Creating several IQ SENSORNET systems with the identical assign-
ment of sensor numbers to sensors
 Changing the order of the sensors in an already installed system

3.5.1 Creating the assignment of sensor numbers

You want to install an IQ SENSORNET system and, at the same time, to

create a specific sequence of sensor number assignments to the sen-
sors.

1 Carry out a system start without any sensors (see system oper-
ating manual).
2 Connect the sensors to the system in the required order.
After connecting each sensor, wait until the sensor is recog-
nized by the system (see system operating manual, chapter
Installation).

3.5.2 Changing the assignment of sensor numbers

You want to change the assignment of sensor numbers to the sensors

in an already running IQ SENSORNET system.

Change sensor no. Prerequisite:

menu IQ SENSORNET system with controller software version
3.50 or higher.

1 Open the setting menu with <S>.

2 IQ SENSORNET System 2020 3G, System 2020 XT,
System 28X:
Using <> and <OK>, select and confirm the menu
item, System settings / Service / Change sensor no..
IQ SENSORNET System 182:
Using <> and <OK>, select and confirm the menu
item System / Change sensor no..
3 IQ SENSORNET System 2020 3G, System 2020 XT,
System 28X:
Using <> and <OK>, select and confirm the column
with the sensor numbers.

20
IQ SENSORNET Fieldbus linking Configuring the IQ SENSORNET

4 Select and confirm a sensor with <> and <OK>.

An entry field for the new sensor number pops up.

5 Enter and confirm a new sensor number for the sensor
selected with <> and <OK>.
All sensor numbers that were changed are given an asterisk
(*).
6 Change further sensor numbers as necessary.
7 Using <> and <OK>, select and confirm Save and
quit.
IQ SENSORNET System 2020 3G, System 2020 XT,
System 28X:
A safety query pops up.
IQ SENSORNET System 182:
The new sensor numbers are active.

Links and measured value recordings for all sensors

marked by an asterisk (*) are erased.

8 IQ SENSORNET System 2020 3G, System 2020 XT,

System 28X:
Confirm the safety query with Yes.

Disconnecting / You can also change the sensor numbers in the system by disconnect-
connecting all sensors ing all sensors, erasing any inactive datasets and then reconnecting all
of the IQ SENSORNET sensors in the correct order.

1 Unplug all sensors from the IQ SENSORNET.

When the inactive datasets are deleted, all settings for the
sensors are deleted as well.

2 Delete all inactive datasets in the list of sensors (see System

operating manual, chapter Deleting inactive datasets of sen-
sors).
3 Connect the sensors to the system in the required order.
After connecting a sensor, wait until the sensor is recognized
by the system (see system operating manual, chapter Installa-
tion).

ba76148e05 05/2017 21
Configuring the IQ SENSORNET IQ SENSORNET Fieldbus linking

3.5.3 Creating the identical assignment of sensor numbers in

several systems

You want to install several identical IQ SENSORNET systems and, at the

same time, to create the same sequence of sensor number assign-
ments to the sensors in all systems.
To do so, you can save the system configuration of a system configured
as a model via the USB interface or via a network connection and then
load it to other systems.

USB interface
1 Save the configuration from the model to a USB memory
device (see system operating manual of your system).
2 Connect the USB memory device with the configuration data to
the target system and load the configuration
(see system operating manual of your system).

Network connection
1 Save the configuration from the model to a PC via a network
connection (see system operating manual of your system).
2 Connect the PC to the target system via a network and load the
configuration.
 MIQ/MC2, MIQ/TC 2020 XT:
see operating manual IQ Software Pack CONNECT.
 MIQ/MC3, MIQ/TC 2020 3G, DIQ/S 28X-E[F]:
see system operating manual of your system (section
IQ WEB CONNECT).

22
IQ SENSORNET Fieldbus linking Communication with fieldbuses

4 Communication with fieldbuses

The IQ SENSORNET monitors the current state of each sensor operated
on the system. The sensor status documents sensor information (mea-
sured value status and status info of the sensor) and current processes
(e.g. calibration or cleaning).

The sensor status is superordinate to the measured value status.

The influence of the sensor status on the measured value is docu-
mented with the status descriptions.

For the measured value to be evaluated, e.g. by a superordinate con-

trol system such as PLC, the sensor status and measured value status
also have to be taken into account together with the measured value.
A measured value is suitable for further evaluation if both of the follow-
ing conditions are met:

1st Sensor status MEASURE

2nd Measured value VALID
status

Details on the communication options with a fieldbus are given in the

respective sections.

Fieldbus Query see

Profibus*, Profinet
DP(V0), Profinet several sensors section 4.1
one sensor section 4.4
DPV1 several sensors section 4.2
Modbus section 4.5
Ethernet/IP all sensors section 4.3
one sensor section 4.4

* Communication with a Profibus applies to the current GSD file

(version > 1.22). The current GSD file is provided on the Inter-
net at www.YSI.com.

The query of several sensors under Profibus is supported by

the Profibus controller from version 3.50
(for the following instruments: MIQ/MC2-PR, MIQ/2-PR,
MIQ/MC3-PR, DIQ/S 182, DIQ/S 28X-PR).

ba76148e05 05/2017 23
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.1 Profibus DP(V0), Profinet

4.1.1 Profinet module (query format)

The following module (query format) is available:

SensorData Data block per sensor: 16 bytes

You can simultaneously transmit the data of up to 20 sensors.

4.1.2 Profibus modules (query formats)

A Profibus or Profinet instrument can transmit up to 244 bytes of user

data with the Profibus DP(V0) protocol. The number of the sensors that
can be queried at the same time depends on the size of the data block
per sensor.

The following modules (query formats) are available:

SensorData Data block per sensor: 16 bytes

With this you can simultaneously transmit the data of up to 15 sensors
(15 * 16 bytes = 240 bytes).

SensorData compact Data block per sensor: 12 bytes

With this you can simultaneously transmit the data of up to 20 sensors
(20 * 12 bytes = 240 bytes).

As a rule, some sensor data are already known at the time

of the PLC programming and do not have to be evaluated.
These sensor data are not transmitted in the module Sen-
sorData compact:
 Sensor number
 Sensor model
 Measuring mode

4.1.3 Configuration

Query In the Profibus instrument configuration, a slot is assigned to each sen-

SensorData sor in the IQ SENSORNET. The number of the slot corresponds to the
SensorData compact sensor number in the IQ SENSORNET.
To query sensor data, assign a module (SensorData or SensorData
compact) to each slot (sensor) you want to query.

For consistent access with a Siemens PLC with program-

ming language STEP7, the following commands have to
be used:
– SFC14 (for reading)

24
IQ SENSORNET Fieldbus linking Communication with fieldbuses

4.1.4 Data of a module

SensorData: 16 bytes - from the IQ SENSORNET to the superordinate control system

(PLC)
SensorData compact 12 bytes - from the IQ SENSORNET to the superordinate control system
(only Profibus): (PLC)

Byte Information Module

Sensor- SensorData Data Bits
Data compact type
(only Profibus):
1 - Sensor number Int 8 7-0
2 1 Sensor status Int 8 7-0
3 - Sensor model Int 16 15-8
4 - 7-0
5 2 Status info Int 16 15-8
6 3 7-0
7 - Measuring mode Int 8 7-0
8 4 Status of main measured value Int 8 7-4
Status of secondary measured value 3-0
9 5 Main measured value (IEEE-754 Float 32 31-24
floating point, 32-bit)
10 6 23-16
11 7 16-8
12 8 7-0
13 9 Secondary measured value Float 32 31-24
(IEEE-754 floating point, 32-bit)
14 10 23-16
15 11 16-8
16 12 7-0

ba76148e05 05/2017 25
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.1.5 Example

Querying sensors 2 Corresponding to the sensor numbers (Sxx) in the IQ SENSORNET, the
and 5 slots have to be assigned gap-free to the last sensor to be queried.

Profibus Slots for sensors not required have to be assigned to the module empty
slot.

Profinet Slots for sensors not required may remain unoccupied.

Configuration
Slot Module
1 empty slot (only Profibus; leave unoccupied for Profinet)
2 SensorData
3 empty slot
4 empty slot
5 SensorData

Byte Sensor data (slot 2 = sensor 2)

SensorData SensorData Value Information Meaning of the value
compact
(only Profibus):
1 - 02h Sensor number 02h (Int 8) --> 2
Sensor number S02
2 1 02h Sensor status 02h (Int 8) --> MEASURE
see section 5.2
3 - 04h Sensor model 0401h (Int 16)
--> VisoTurb 700 IQ
4 - 01h Sensor model see section 5.5
5 2 00h Status info 0000h (Int 16)
--> no errors
6 3 00h Status info see section 5.6
7 - 00h Measuring 00h (Int 8) --> FNU Turb
mode see section 5.7
8 4 14h Measured value 14h (Int 8)
status Main measured value (bits 7-4):
1h --> VALID
Secondary measured value (bits 3-0):
4h --> MISSING
see section 5.3

26
IQ SENSORNET Fieldbus linking Communication with fieldbuses

Byte Sensor data (slot 2 = sensor 2)

SensorData SensorData Value Information Meaning of the value
compact
(only Profibus):
9 5 42h Main measured 429E46C2h (Float 32)
value --> 79,1382
10 6 9Eh Measured parameter and unit,
11 7 46h see byte 10 (measuring mode)

12 8 C2h
13 9 00h Secondary 00000000h (Float 32)
measured value --> 0
14 10 00h but measured value invalid (MISSING),
15 11 00h see byte 11 (measured value status)

16 12 00h

4.2 Profibus DPV1

4.2.1 Modules (query formats)

A Profibus instrument can transmit up to 244 bytes of user data per

query with the Profibus DPV1 protocol.
The number of the sensors that can be queried at the same time
depends on the size of the data block per sensor.
The following modules (query formats) are available.

SensorData Data block per sensor: 16 bytes

With this you can simultaneously transmit the data of up to 15 sensors
(15 * 16 bytes = 240 bytes).

SensorData compact Data block per sensor: 12 bytes

With this you can simultaneously transmit the data of up to 20 sensors
(20 * 12 bytes = 240 bytes).

As a rule, some sensor data are already known at the time

of the PLC programming and do not have to be evaluated.
These sensor data are not transmitted in the module Sen-
sorData compact:
 Sensor number
 Sensor model
 Measuring mode

ba76148e05 05/2017 27
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.2.2 Data query

The IQ SENSORNET provides the sensor data for read access only.
Write access is not possible.
The data to be queried with Profibus DPV1 are addressed via slot,
index and length data.

SensorData Each sensor in the IQ SENSORNET is assigned an index in slot 0 of the

PLC. Data required for the query:

Data query
Slot 0
Index Sensor number of the first sensor to be queried
Length Number of bytes to be queried

SensorData compact Each sensor in the IQ SENSORNET is assigned an index in slot 0 of the
PLC. Data required for the query:

Data query
Slot 0
Index 100 + sensor number of the first sensor to be queried
Length Number of bytes to be queried

28
IQ SENSORNET Fieldbus linking Communication with fieldbuses

4.2.3 Data block of the sensors

The data block contains the data of the sensors in the order of their reg-
istering to the IQ SENSORNET (Sxx number).

SensorData: 16 bytes - from the IQ SENSORNET to the superordinate control system

(PLC)
SensorData compact: 12 bytes - from the IQ SENSORNET to the superordinate control system
(PLC)

Byte Information Module

SensorData SensorData Data Bits
compact type
1 - Sensor number Int 8 7-0
2 1 Sensor status Int 8 7-0
3 - Sensor model Int 16 15-8
4 - 7-0
5 2 Status info Int 16 15-8
6 3 7-0
7 - Measuring mode Int 8 7-0
8 4 Status of main measured value Int 8 7-4
Status of secondary measured value 3-0
9 5 Main measured value (IEEE-754 Float 32 31-24
floating point, 32-bit)
10 6 23-16
11 7 16-8
12 8 7-0
13 9 Secondary measured value Float 32 31-24
(IEEE-754 floating point, 32-bit)
14 10 23-16
15 11 16-8
16 12 7-0

ba76148e05 05/2017 29
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.2.4 Example

Querying sensors 2 Examples of query formats

and 5

SensorData Data query

Slot 0
Index 2 (sensor number of the first sensor to be queried)
Length 64 bytes = 4 * 16 bytes

4 (number of consecutive sensors)

16 (bytes per sensor in the module SensorData)

SensorData compact Data query

Slot 0
Index 102 (= 100 + 2)
2 (sensor number of the first sensor to be queried)
Length 48 bytes ( = 4 * 12 bytes)

4 (number of consecutive sensors)

12 (bytes per sensor in the module SensorData com-
pact)

30
IQ SENSORNET Fieldbus linking Communication with fieldbuses

Byte Sensor data

number
Sensor

Sxx

SensorData SensorData Value Information Meaning of the value

compact
1 - 02h Sensor num- 02h (Int 8) --> 2
ber Sensor number S02
2 1 02h Sensor status 02h (Int 8) --> MEASURE
see section 5.2
3 - 04h Sensor model 0401h (Int 16)
--> VisoTurb 700 IQ
4 - 01h Sensor model see section 5.5
5 2 00h Status info 0000h (Int 16)
--> no errors
6 3 00h Status info see section 5.6
7 - 00h Measuring 00h (Int 8) --> FNU Turb
mode see section 5.7
8 4 14h Measured 14h (Int 8)
value status Main measured value (bits 7-4):
1h --> VALID
02

Secondary measured value (bits

3-0):
4h --> MISSING
see section 5.3
9 5 42h Main mea- 429E46C2h (Float 32)
sured value --> 79,1382
10 6 9Eh Measured parameter and unit,
11 7 46h see byte 10 (measuring mode)

12 8 C2h
13 9 00h Secondary 00000000h (Float 32) --> 0
measured but measured value invalid
14 10 00h value (MISSING),
15 11 00h see byte 11 (measured value sta-
tus)
16 12 00h
17-32 13-24 ... ... ...
03

33-48 25-36 ... ... ...

04

49-64 37-48 ... ... ...

05

ba76148e05 05/2017 31
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.3 EtherNet/IP

4.3.1 Modules (query formats)

The sensor data are transferred as data blocks of 16 bytes per each
sensor. The data of up to 30 sensors are transferred (30 * 16 bytes =
480 bytes).

You can also query the sensor data individually (see sec-
tion 4.4).

4.3.2 Configuration

Use the following configuration data:

Connection GetSensorDataAll

Use the following configuration data if you do not use the EDS file.

Output Assembly Instance ID = 254 (InputOnly) 0 bytes

Input Assembly Instance ID = 104 (SensorDataAll) 480
bytes

4.3.3 Data block of the sensors

The data block contains the data of the sensors corresponding to the
sensor number (Sxx number) in the IQ SENSORNET.

16 bytes - from the IQ SENSORNET to the superordinate control system

(PLC)

Byte Information Module

Data Bits
type
1 Sensor number Int 8 7-0
2 Sensor status Int 8 7-0
3 Sensor model Int 16 15-8
4 7-0

32
IQ SENSORNET Fieldbus linking Communication with fieldbuses

Byte Information Module

Data Bits
type
5 Status info Int 16 15-8
6 7-0
7 Measuring mode Int 8 7-0
8 Status of main measured value Int 8 7-4
Status of secondary measured value 3-0
9 Main measured value (IEEE-754 Float 32 31-24
floating point, 32-bit)
10 23-16
11 16-8
12 7-0
13 Secondary measured value Float 32 31-24
(IEEE-754 floating point, 32-bit)
14 23-16
15 16-8
16 7-0

ba76148e05 05/2017 33
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.3.4 Example

Configuration
Connection GetSensorDataAll

Byte Sensor data

number
Sensor

Sxx Value Information Meaning of the value

1 02h Sensor number 01h (Int 8) --> 1

Sensor number S01
2 02h Sensor status 02h (Int 8) --> MEASURE
see section 5.2
3 04h Sensor model 0401h (Int 16)
--> VisoTurb 700 IQ
4 01h Sensor model see section 5.5
5 00h Status info 0000h (Int 16)
--> no errors
6 00h Status info see section 5.6
7 00h Measuring 00h (Int 8) --> FNU Turb
mode see section 5.7
8 14h Measured 14h (Int 8)
value status Main measured value
(bits 7-4):
01

1h --> VALID
Secondary measured
value (bits 3-0):
4h --> MISSING
see section 5.3
9 42h Main mea- 429E46C2h (Float 32)
sured value --> 79,1382
10 9Eh Measured parameter and
11 46h unit,
see byte 10 (measuring
12 C2h mode)
13 00h Secondary 00000000h (Float 32)
measured --> 0
14 00h value but measured value
15 00h invalid (MISSING),
see byte 11 (measured
16 00h value status)
17- ... ... ...
02

32

34
IQ SENSORNET Fieldbus linking Communication with fieldbuses

Byte Sensor data

number
Sensor

Sxx
Value Information Meaning of the value

33- ... ... ...

03
48
49- ... ... ...

04
64
... ... ... ... ...
465
-
30

480

ba76148e05 05/2017 35
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.4 Profibus DP(V0) and EtherNet/IP

Query of individual sensors
The sensor number (Sxx) is the identification for a sensor. The sensor
number is always transmitted in the first byte of the output and input da-
ta. Thus the control system (PLC) can clearly query data of individual
sensors.

The data is transferred cyclically in two steps:

 Output data of the PLC:
The superordinate control system (PLC) sends a prompt to the
IQ SENSORNET to provide data of the sensor with a certain sensor
number.
 Input data of the PLC:
The IQ SENSORNET checks whether the prompted sensor number is
available and returns the data of the sensor with the relevant sensor
number to the superordinate control system (PLC).

Start

Output data in PLC:

Assign a sensor number (Sxx) to a sensor

Input data in PLC:

Data from IQ SensorNet

Is the sensor number no

identical in the output data
and input data ?

Process the data of the sensor

Query the data of another sensor no

with different sensor number?

Fig. 4-1 Data transmission in (Profibus, Ethernet/IP)

36
IQ SENSORNET Fieldbus linking Communication with fieldbuses

4.4.1 Configuration

Profibus DP(V0) Slot 1 (exclusively possible at slot 1)

Module SensorData select (only slot 1)

It is also possible to query several sensors simultaneously

(see section 4.1).

Data access must be consistent.

For consistent access with a Siemens PLC with program-
ming language STEP7, the following commands have to
be used:
– Write: DPWR_DAT (SFC15)
– Read: DPRD_DAT (SFC14)

Ethernet/IP Connection GetSensorData

Use the following configuration data if you do not use the EDS file.

Output Assembly Instance ID= 101 (SensorSelector) 1 bytes

Input Assembly Instance ID = 102 (SensorData) 16
bytes

If your PLC (e.g. Omron) only supports a granularity of 2 bytes (WORD)

for the definition of EtherNet/IP access, select the connection
GetSensorData2B for the query.

Connection GetSensorData2B

Use the following configuration data if you do not use the EDS file.

Output Assembly Instance ID = 103 2 bytes

(SensorSelector2B)
Input Assembly Instance ID = 102 (SensorData) 16 bytes

You can also query all sensor data simultaneously (see

section 4.3).

ba76148e05 05/2017 37
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.4.2 Data block for sensor selection (output data of the PLC)

1 byte - from the to the superordinate control system (PLC) to the

IQ SENSORNET.

Byte Information Data format

Data type Bits
1 Sensor number (Sxx) in the Int 8 7-0
IQ SENSORNET

4.4.3 Data block of the sensors (input data of the PLC)

16 bytes - from the IQ SENSORNET to the superordinate control system

(PLC)

Byte Information Data format

Data Bits
type
1 Sensor number Int 8 7-0
2 Sensor status Int 8 7-0
3 Sensor model Int 16 15-8
4 7-0
5 Status info Int 16 15-8
6 7-0
7 Measuring mode Int 8 7-0
8 Status of main measured value Int 8 7-4
Status of secondary measured value 3-0
9 Main measured value (IEEE-754 floating point, Float 32 31-24
32-bit)
10 23-16
11 16-8
12 7-0
13 Secondary measured value (IEEE-754 floating point, Float 32 31-24
32-bit)
14 23-16
15 16-8
16 7-0

38
IQ SENSORNET Fieldbus linking Communication with fieldbuses

4.4.4 Example

Querying sensor 02
Configuration
Byte Valu Information Meaning of the value
e
1 02h Sensor number 02h (Int 8) --> 2
(Sxx) in the Sensor number S02
IQ SENSORNET

Sensor data
Byte Value Information Meaning of the value
1 02h Sensor number 02h (Int 8) --> 2
Sensor number S02
2 02h Sensor status 02h (Int 8) --> MEASURE
see section 5.2
3 04h Sensor model 0401h (Int 16)
--> VisoTurb 700 IQ
4 01h Sensor model see section 5.5
5 00h Status info 0000h (Int 16)
--> no errors
6 00h Status info see section 5.6
7 00h Measuring mode 00h (Int 8) --> FNU Turb
see section 5.7
8 14h Measured value 14h (Int 8)
status Main measured value (bits 7-4):
1h --> VALID
Secondary measured value (bits 3-0):
4h --> MISSING; see section 5.3
9 42h Main measured 429E46C2h (Float 32)
value --> 79,1382
10 9Eh Measured parameter and unit,
11 46h see byte 10 (measuring mode)

12 C2h
13 00h Secondary mea- 00000000h (Float 32)
sured value --> 0
14 00h but measured value invalid (MISSING),
15 00h see byte 11 (measured value status)

16 00h

ba76148e05 05/2017 39
Communication with fieldbuses IQ SENSORNET Fieldbus linking

4.5 Communication with Modbus RTU, Modbus TCP

4.5.1 Data transmission

On each query of sensor data with the Modbus protocol, a block of con-
secutive registers is read.

Query and response Data transmission takes place via query and response telegrams. The
telegram form of the telegrams is determined by the Modbus RTU protocol.
The Modbus master transmits a query telegram with a Modbus com-
mand to the Modbus slave (here, the IQ SENSORNET). The Modbus
slave transmits a response telegram with the requested data or an error
message.

4.5.2 Query format

Supported The IQ SENSORNET provides the data block for read access only. Writ-
Modbus commands ing Modbus commands are not carried out.
The following commands are available:

Modbus commands Command code

Read Input Register 04h
Read Holding Register 03h

For a query of sensor data, determine the first register and the number
of registers to be read.

Determining the first The first register to be read depends on the sensor number (Sxx):
register to be read R = [(Sxx - 1) * 8] + 1.

Example: Determine the first register with data block for the sensor
S02:
R = [(2 - 1) * 8] + 1 = 9

The number of registers to be read for one sensor data block is 8 reg-
isters.
With one Modbus query, up to 125 registers (15 data blocks) can be
read.

40
IQ SENSORNET Fieldbus linking Communication with fieldbuses

4.5.3 Data block of the sensors

The data block contains the data of the sensors in the order of their reg-
istering to the IQ SENSORNET (Sxx number).

The data of a sensor are stored in 8 registers each.

Modbus Information Data format

Register Bits Data Bits
type
0001 1-8 Sensor number (S01) Int 8 7-0
0001 9-16 Sensor status Int 8 7-0
0002 1-16 Sensor model Int 16 15-0
0003 1-16 Status info Int 16 15-0
Sensor S01

0004 1-8 Measuring mode Int 8 7-0

0004 9-16 Measured value status Int 8 7-0
0005 1-16 Main measured value (IEEE-754 floating point, Float 32 31-16
32-bit)
0006 1-16 15-0
0007 1-16 Secondary measured value (IEEE-754 floating point, Float 32 31-16
32-bit)
0008 1-16 15-0
0009 1-8 Sensor number (S02) Int 8 7-0
0009 9-16 Sensor status Int 8 7-0
0010 1-16 Sensor model Int 16 15-0
0011 1-16 Status info Int 16 15-0
Sensor S02

0012 1-8 Measuring mode Int 8 7-0

0012 9-16 Measured value status Int 8 7-0
0013 1-16 Main measured value (IEEE-754 floating point, Float 32 31-16
32-bit)
0014 1-16 15-0
0015 1-16 Secondary measured value (IEEE-754 floating point, Float 32 31-16
32-bit)
0016 1-16 15-0
0017 1-8 Int 8 7-0
Sensor S03 ...

0018 9-16 Int 8 7-0

... ... ... ... ...

ba76148e05 05/2017 41
Communication with fieldbuses IQ SENSORNET Fieldbus linking

The counting method of the Modbus registers and Modbus

bits and the allocation of MSB and LSB is different from the
usual method of most programming languages.

Modbus Usually
Count start of the register 1 0
MSB* allocation of the register Bit 1 Bit 15
LSB* allocation of the register Bit 16 Bit 0

* MSB = Most significant bit, LSB = Least significant bit

4.5.4 Example

Querying sensor S02

Modbus query
Byte Value Information Meaning of the value
1 01h Modbus address of 01h --> 1
the IQ SENSORNET
2 04h Function 04h --> 4
Read Input Register
see section 4.5.2
3 00h Start address HI 0008h --> 8
Start with register 9
4 08h Start address LO (Modbus counting method)
5 00h Number of HI regis- 0008h --> 8
ters 8 registers
6 08h Number of LO regis-
ters
7 70h CRC (HI) Checksum (CRC)
8 0Eh CRC (LO)

Modbus response
Byte Value Information Meaning of the value
1 01h Modbus address of the 01h --> 1
IQ SENSORNET

42
IQ SENSORNET Fieldbus linking Communication with fieldbuses

Modbus response
Byte Value Information Meaning of the value
2 04h Function 04h --> 4
Read Input Register
3 10h Number of bytes 10h --> 16
16 bytes (8 registers)
4 02h Contents of register 9 02h (Int 8) --> 2
(HI) = sensor number Sensor number S02
5 02h Contents of register 9 02h (Int 8) --> MEASURE
(LO) = sensor status see section 5.2
6 04h Contents of register 10 0401h (Int 16)
(HI) = sensor model --> VisoTurb 700 IQ
see section 5.5
7 01h Contents of register 10
(LO) = sensor model
8 00h Contents of register 11 0000h (Int 16)
(HI) = status info --> no errors
see section 5.6
9 00h Contents of register 11
(LO) = status info
10 00h Contents of register 12 00h (Int 8) --> FNU Turb
(HI) = measuring see section 5.7
mode
11 14h Contents of register 12 14h (Int 8)
(LO) = measured Main measured value (bits
value status 7-4):
1h --> VALID
Secondary measured
value (bits 3-0):
4h --> MISSING
see section 5.3

ba76148e05 05/2017 43
Communication with fieldbuses IQ SENSORNET Fieldbus linking

Modbus response
Byte Value Information Meaning of the value
12 42h Contents of register 13
(HI) = main measured 429E46C2h (Float 32)
value --> 79,1382
Measured parameter and
13 9Eh Contents of register 13 unit,
(LO) = main measured see byte 10 (measuring
value mode)
14 46h Contents of register 14
(HI) = main measured
value
15 C2h Contents of register 14
(LO) = main measured
value
16 00h Contents of register 15
(HI) = secondary mea- 00000000h (Float 32)
sured value --> 0
but measured value invalid
17 00h Contents of register 15 (MISSING),
(LO) = secondary see byte 11 (measured
measured value value status)
18 00h Contents of register 16
(HI) = secondary mea-
sured value
19 00h Contents of register 16
(LO) = secondary
measured value
20 23h CRC (HI) Checksum (CRC)
21 5Eh CRC (LO)

44
IQ SENSORNET Fieldbus linking Encoded data for fieldbus communication

5 Encoded data for fieldbus

communication
5.1 Data formats of the sensor datablock
Measured values The data for the main and secondary measured values are transmitted
(Float 32) in the IEE-754 standard 32-bit floating point format.

Address Bit representation

MSB* LSB*
Offset 0h bits S E E E E E E E S = sign (bit 31)
31-24 E = exponent
(bits 30-23)
Offset 1h bits E M M M M M M M M = mantissa (bits 22-0)
23-16
Offset 2h bits 15-8 M M M M M M M M
Offset 3h bits 7-0 M M M M M M M M

* MSB = Most significant bit, LSB = Least significant bit

If not all of the bits of the exponent are 0, the value is calculated accord-
ing to:

V = −1S ⋅ 2 E −127 ⋅ (1 + M b 22 ⋅ 2 −1 + M b 21 ⋅ 2 −2 + M b 20 ⋅ 2 −3 + ... + M b 0 ⋅ 2 −23 )

If all of the bits of the exponent are 0, the value is calculated according
to:

V = −1S ⋅ 2 −126 ⋅ ( M b 22 ⋅ 2 −1 + M b 21 ⋅ 2 −2 + M b 20 ⋅ 2 −3 + ... + M b 0 ⋅ 2 −23 )

A value is 0 if all the bits of both the exponent as well as the mantissa
are 0.

Evaluation Meaning
Measured value 0 Check the measured value status
Measured value <> 1 The measured value is invalid (error)
status

ba76148e05 05/2017 45
Encoded data for fieldbus communication IQ SENSORNET Fieldbus linking

Apart from the byte order described in the bit representa-

tion, another order of the bytes is also possible.
Opposite to the order described, the two lower bytes have
been exchanged with the two upper bytes in this order (b4
b3 b2 b1 - b2 b1 b4 b3).

For fieldbus applications that can independently interpret

floating point numbers (or allow to select a data format for
certain registers), the byte order the data interpretation is
based on should be checked.

Sensor model The data for the sensor model and status info is transmitted as INT16,
Status info i.e. consists of 2 bytes. The assignment is carried out in Motorola for-
(INT16) mat (the higher value byte first).

Address Bit representation Information

MSB LSB
Offset 0h bits 15-8 High byte
Offset 1h bits 7-0 Low byte

Measured value status The data for the measured value status of the main and secondary
(Int8) measured values are encoded jointly into a single byte. Bits 7-4 encode
the status of the main measured value, bits 3-0 encode the status of the
secondary measured value.

Other data (INT8) All other data always consist of only a single byte (Int8).

46
IQ SENSORNET Fieldbus linking Encoded data for fieldbus communication

5.2 Sensor status

The sensor status applies to both the main and secondary measured
value of a sensor.

Code Status Meaning of the status

00h UNUSED_ID Sensor and sensor number are not available in the IQ SENSORNET
system.
The measured value status of the main and secondary measured
value is MISSING (4h) (see section 5.3 MEASURED VALUE STATUS).

The UNUSED_ID status also occurs when the fieldbus interface of the
IQ SENSORNET does not receive any data from the IQ SENSORNET
controller for more than 2 minutes. Possible cause: Communication
malfunction or controller failure. The data transmitted last remain fro-
zen for the two minutes delay time.
01h INACTIVE The sensor is currently inactive. The sensor number (ID) and respec-
tive setting dataset are available in the IQ SENSORNET system. The
sensor was removed from the IQ SENSORNET system or the commu-
nication does not work.
The measured value status of the main and secondary measured
value is MISSING (4h) (see section 5.3 MEASURED VALUE STATUS).
The measured value display on the terminal indicates Init or Error.
02h MEASURE The sensor is in measuring mode.
The measured value status can be VALID, OFL or INVALID.
The measured value display on the terminal indicates the valid mea-
sured value, OFL or "----" (invalid measured value).
For the measured value to be evaluated, e.g. by a superordinate con-
trol system, the sensor status and measured value status also have to
be taken into account together with the measured value (see also sec-
tion 5.3 MEASURED VALUE STATUS)
03h CALIBRATE The sensor is being calibrated. No measured value is available.
The measured value status of the main and secondary measured
value is MISSING (4h) (see section 5.3 MEASURED VALUE STATUS).
The measured value display on the terminal indicates Cal.
04h ERROR The sensor is in a serious error status.

ba76148e05 05/2017 47
Encoded data for fieldbus communication IQ SENSORNET Fieldbus linking

Code Status Meaning of the status

05h MAINTENANCE The sensor is in maintenance condition or a cleaning cycle (cleaning
including adjustment phase) is active.
The measured value display on the terminal shows a flashing mea-
sured value or Clean.
The measured value and measured value status are frozen while the
sensor is in the MAINTENANCE condition.
In the case of the measured value status VALID, the measured value
is frozen with the value at the start of the MAINTENANCE status.

5.3 Measured value status

The measured value status is available for both the main and second-
ary measured value of a sensor.

Code Status Meaning of the status

1h VALID The measured value is valid.
In the case of the sensor status MAINTENANCE, the measured
value is frozen on the value of the start of the MAINTENANCE sta-
tus.
The measured value display of the IQ SENSORNET shows a flashing
measured value or Clean.
2h OFL The measured value lies outside the selected measuring range.
The transmitted measured value is set to 0.
The measured value display of the IQ SENSORNET indicates OFL.
3h INVALID The measured value is invalid.
The transmitted measured value is set to 0.
The measured value display of the IQ SENSORNET indicates "----"
(invalid measured value).
4h MISSING The measured value cannot be determined or is not available.
The transmitted measured value is set to 0.
The measured value display of the IQ SENSORNET indicates Cal or
Error.

48
IQ SENSORNET Fieldbus linking Encoded data for fieldbus communication

5.4 Signaling the sensor status and measured value sta-

tus in the IQ SENSORNET

5.4.1 Display in the measured value display on the terminal

Measured value status

VALID OFL INVALID MISSING
MEASURE Measured value "OFL" "----" -
UNUSED_ID - - - No display
(No sensor
connected)
Sensor status

INACTIVE - - - "Init" or "Error"

CALIBRATE - - - "Cal"
ERROR - - "----" -
MAINTENANCE Measured value "OFL" "----" -
flashing flashing flashing
or "Clean"

- The combination of sensor status and measured value status is not possi-
ble
"..." Displayed text

5.4.2 Measured value transmitted on fieldbus level

Measured value status

VALID OFL INVALID MISSING
MEASURE Measured value
Sensor status

UNUSED_ID 0 (zero)
INACTIVE
CALIBRATE For the measured value 0 (zero) to be evaluated by a superordinate con-
ERROR trol system, the measured value always has to be taken into account
MAINTENANCE together with the sensor status and measured value status.

ba76148e05 05/2017 49
Encoded data for fieldbus communication IQ SENSORNET Fieldbus linking

5.5 Sensor model

The sensor model is the model name the sensor registers with on the
IQ SENSORNET.

Code Model
0101h SensoLyt700IQ
0201h TetraCon700IQ
0301h TriOxmatic700IQ
0302h TriOxmatic701IQ
0303h TriOxmatic702IQ
0304h SC FDO 700 (FDO700IQ)
0305h SC FDO 701 (FDO700IQ)
0401h VisoTurb700IQ
0402h ViSolid700IQ
0501h AmmoLyt700IQ
0503h AmmoLyt+ (AmmoLyt+700IQ)
0907h AmmoLyt+K (AmmoLyt+700IQ)
0601h NitraLyt700IQ
0602h NitraLyt+ (NitraLyt+700IQ)
0701h NitraVis700/1IQ
0702h NitraVis700/5IQ
0703h CarboVis700/5IQ
0704h SolidVis700IQ (UV/VIS sensors with TSS option)
0705h NitraVis700/5IQ (NiCaVis700IQ)
0706h CarboVis700/5IQ (NiCaVis700IQ)
0707h CarboVis700/1IQ
0801h MIQ/IC2, current input 1
0802h MIQ/IC2, current input 2
0901h VARiON A (VARiON700IQ)
0902h VARiON N (VARiON700IQ)
0905h VARiON A (VARiON+700IQ)
0906h VARiON N (VARiON+700IQ)

50
IQ SENSORNET Fieldbus linking Encoded data for fieldbus communication

Code Model
0907h VARiON K (VARiON+700IQ)
0A01h NitraVis701 IQ (+ NiCaVis701IQ NI)
0A02h NitraVis705 IQ (+ NiCaVis705IQ + NiCaVis705IQ NI)
0A03h CarboVis701 IQ (+ NiCaVis701IQ NI)
0A04h CarboVis705 IQ (+ NiCaVis705IQ + NiCaVis705IQ NI)
0A05h UV701 IQ SAC
0A06h UV705 IQ SAC
0A07h SolidVis701 IQ (UV/VIS sensors with TSS option)
0A08h SolidVis705 IQ (UV/VIS sensors with TSS option)
0A09h UV701 IQ NOx
0A0A UV705 IQ NOx
0A1Ah Virtual N sensor - NitraVis701IQ NI
0A1Bh Virtual N sensor - NitraVis705IQ NI
0A1Ch Virtual C sensor 1 - CarboVis701 IQ
0A1Dh Virtual C sensor 2 - CarboVis701 IQ
0A1Eh Virtual C sensor 3 - CarboVis701 IQ
0A1Fh Virtual C sensor 4 - CarboVis701 IQ
0A20h Virtual C sensor 1 - CarboVis705 IQ
0A21h Virtual C sensor 2 - CarboVis705 IQ
0A22h Virtual C sensor 3 - CarboVis705 IQ
0A23h Virtual C sensor 4 - CarboVis705 IQ
0B01h P 700 IQ
0C01h IFL 700 IQ
0C02h IFL 701 IQ

ba76148e05 05/2017 51
Encoded data for fieldbus communication IQ SENSORNET Fieldbus linking

5.6 Status info of sensors

Model Bit 0 Bit 1 Bit 2 Bit 3-31

SensoLyt700IQ Component SensCheck: pH electrode - -
hardware defective, glass broken
defective
TetraCon700IQ - - -
TriOxmatic700IQ SensReg: Electrolyte SensLeck: Mem- -
supply is depleted brane head damaged
TriOxmatic701IQ * -

TriOxmatic702IQ - -
SC FDO 700 Measurement interfered - -
SC FDO 701 Measurement interfered - -
VisoTurb700IQ SensCheck: Sensor con- SensCheck: Ultra- -
taminated sound cleaning sys-
ViSolid700IQ tem has failed -

AmmoLyt700IQ - - -
AmmoLyt+ - - -
AmmoLyt+K - - -
NitraLyt700IQ - - -
NitraLyt+ - - -
NitraVis700/xIQ - - -
CarboVis700/xIQ - - -
SolidVis700IQ - - -
NitraVis70xIQ Component hardware Optical measuring -
defective xxx range exceeded
CarboVis70xIQ -
SolidVis70xIQ -
UV70x IQ SAC
UV70x IQ NOx
MIQ/IC2 - - -

* The SensLeck function is not available with the sea water model
(-SW variant)

52
IQ SENSORNET Fieldbus linking Encoded data for fieldbus communication

continued

Model Bit 0 Bit 1 Bit 2 Bit 3-31

VARiON A Component - - -
hardware
VARiON N defective - - -
VARiON K - - -
IFL 700 IQ - - -
IFL 701 IQ - - -
P 700 IQ Container for xxx nearly Air bubbles in the -
empty! analyzer

Note
The status info must be evaluated for each bit individually.

ba76148e05 05/2017 53
Encoded data for fieldbus communication IQ SENSORNET Fieldbus linking

5.7 Measuring mode

Code
Model 00h 01h 02h 03h 04h 05h 06h 07h 08h
SensoLyt700IQ pH mV

TetraCon700IQ mS/cm SAL TDS S/m

TriOxmatic700IQ mg/l % O2
TriOxmatic701IQ O2
TriOxmatic702IQ
SC FDO 700 mg/l % O2
SC FDO 701 O2

VisoTurb700IQ FNU- NTU- TEF- mg/l ppm g/l TSS

Turb Turb Turb SiO2 SiO2

ViSolid700IQ g/l TSS % g/l TSS % g/l SiO2 % SiO2 g/l SiO2 % SiO2
(M11) TSS (M21) TSS (M11) (M11) (M21) (M21)
(M11) (M21)

AmmoLyt700IQ mg/l mg/l mV

AmmoLyt+ NH4-N NH4

AmmoLyt+K mg/l K mV

NitraLyt700IQ mg/l mg/l mV

NitraLyt+ NO3-N NO3

1 M1 = matrix type 1, M2 = matrix type 2

matrix types: see ViSolid 700 IQ sensor operating manual

54
 IQ SENSORNET Fieldbus linking Encoded data for fieldbus communication

Code
Model 00h 01h 02h 03h 04h 05h 06h 07h 08h
NitraVis700/xIQ mg/l mg/l mg/l
NitraVis70xIQ NO3-N NO3 NO3-N4

NitraVis70xIQ NI mg/l mg/l

NO2-N NO2

CarboVis700/xIQ mg/l mg/l mg/l mg/l mg/l Abs/m Abs/m mg/l UVT
CarboVis70xIQ CODto CODd TOC BOD DOC SACto SACds CSB4 2545
s

SolidVis700IQ (m)g/l
SolidVis70xIQ TSS 2

UV70x IQ SAC 1/m 1/m % mg/l mg/l mg/l mg/l mg/l

SAKgl SAKgs UVT CSBgl CSBgs TOC BSB DOC
254 Korrel Korrel Korrel Korrel Korrel

UV70x IQ NOx mg/l mg/l

NO3-N NO3
3
MIQ/IC2
VARiON A mg/l mg/l mV
NH4-N NH4

VARiON N mg/l mg/l mV

NO3-N NO3

VARiON K mg/l K mV

P 700 IQ mg/l mg/l

PO4-P PO4

IFL 70x IQ m

1
M1 = matrix type 1, M2 = matrix type 2
matrix types: see ViSolid 700 IQ sensor operating manual
2
The measurement unit depends on the settings of the main sensor
3
The measured parameter and measurement unit depend on the set-
tings of the display values (see MIQ/IC2 sensor operating manual).
4
Only xxxVis700/xIQ: Test measurement with standards
5
Only CarboVis70xIQ

ba76148e05 05/2017 55
What to do if ... IQ SENSORNET Fieldbus linking

6 What to do if ...

Here you will find causes and actions to take of errors con-
cerning the PROFIBUS and Modbus communication only.
General errors of the IQ SENSORNET system are dealt with
in the IQ SENSORNET system operating manual.

6.1 PROFIBUS

Data transmission Cause Remedy

between the bus master
and IQ SENSORNET is – Incorrect wiring – Check/change the connections
faulty (see section 2.1)
– Use checklist according to sec-
tion 3.3
– Incorrect setting of the – Check/change the setting of
address the address (see section 3.2.1)
– Incorrect protocol – Check the version of the GSD
file
– Adapt the protocol
– IQ SENSORNET defective – Return the IQ SENSORNET to
YSI

The PLC does not Cause Remedy

contain any plausible
input data – Input data and output data – When programming the PLC,
are not consistent define input data and output
data as consistent over the
entire data length
– The data interpretation of the – Observe the data alignment of
PLC is not correct the PLC data representation. If
necessary, exchange the
high-order and low-order bytes
word by word

56
IQ SENSORNET Fieldbus linking What to do if ...

6.2 Modbus RTU

Data transmission Cause Remedy

between the bus master
and IQ SENSORNET is – Incorrect wiring – Check/change the connections
faulty (see section 2.1)
– Use checklist according to sec-
tion 3.3
– Incorrect setting of address, – Check/change the settings
baud rate, parity (see section 3.2.1)
– Incorrect protocol – Adapt the protocol
– Controller of the – Return the controller to YSI
IQ SENSORNET defective

The PLC does not Cause Remedy

contain any plausible
input data – The data interpretation is not – Heed the data formats of the
correct IQ SENSORNET (see also sec-
tion 4.4.3).
– The data interpretation of the – Observe the data alignment of
PLC is not correct the PLC data representation. If
necessary, exchange the
high-order and low-order bytes
word by word

ba76148e05 05/2017 57
What to do if ... IQ SENSORNET Fieldbus linking

6.3 Ethernet fieldbuses

No network connection Cause Remedy

– Ethernet hardware defective, – Open the MIQ/MC2 or
e.g. MIQ/MC3 and check the red
– Ethernet cable defective Ethernet LED.

– Ethernet connection to – The red Ethernet LED is

MIQ/MC2, MIQ/MC3 or not illuminated (hardware
DIQ/S 28X-E[F] defective):
Use other hardware, e.g.:
– Switch or router to which Ethernet cable, Ethernet
the IQS is connected is connector on the router,
defective router
– The red Ethernet LED is
illuminated (hardware OK):
Check for other errors (see
below)
– Wrong setting in the – Correct the settings (e.g.
IQ SENSORNET (sys- DHCP yes, but no network
tem/TCP/IP settings menu) addresses displayed)
– Wrong setting in the – Correct the settings
router/switch
– Blocking by firewall – Contact your network adminis-
trator or a network specialist

The PLC does not Cause Remedy

contain any plausible
input data – Input data and output data – When programming the PLC,
are not consistent define input data and output
data as consistent over the
entire data length
– The data interpretation of the – Heed the data formats of the
PLC is not correct IQ SENSORNET (see also sec-
tion 4.4.3).
– Observe the data alignment of
the PLC data representation. If
necessary, exchange the
high-order and low-order bytes
word by word

58
Field bus linking Contact Information

7 Contact Information
7.1 Ordering & Technical Support

Telephone: (800) 897-4151

(937) 767-7241
Monday through Friday, 8:00 AM to 5:00 PM ET

Fax: (937) 767-1058

Email: [email protected]

Mail: YSI Incorporated

1725 Brannum Lane
Yellow Springs, OH 45387
USA

Internet: www.ysi.com

When placing an order please have the following information available:

YSI account number (if available) Name and Phone Number

Model number or brief description Billing and shipping address
Quantity Purchase Order or Credit Card

7.2 Service Information

YSI has authorized service centers throughout the United States and
Internationally. For the nearest service center information, please visit
www.ysi.com and click ‘Support’ or contact YSI Technical Support
directly at 800-897-4151.

When returning a product for service, include the Product Return form
with cleaning certification. The form must be completely filled out for an
YSI Service Center to accept the instrument for service. The Product
Return form may be downloaded at www.ysi.com and clicking on the
‘Support‘ tab.

ba76148e05 05/2017 59
Contact Information Field bus linking

60 ba76148e05 05/2017
Xylem |'zīləm|
1) The tissue in plants that brings water upward from the roots;
2) a leading global water technology company.

We're 12,500 people unified in a common purpose: creating innovative solutions

to meet our world's water needs. Developing new technologies that will improve
the way water is used, conserved, and re-used in the future is central to our work.
We move, treat, analyze, and return water to the environment, and we help people
use water efficiently, in their homes, buildings, factories and farms. In more than
150 countries, we have strong, long-standing relationships with customers who
know us for our powerful combination of leading product brands and applications
expertise, backed by a legacy of innovation.

For more information on how Xylem can help you, go to www.xyleminc.com

YSI
1725 Brannum Lane
Yellow Springs, OH 45387
Tel: +1 937-767-7241; 800-765-4974
Fax: +1 937-767-1058
Email: [email protected]
Web: www.ysi.com

©Xylem Inc