JUMO LOGOSCREEN nt User manual

nt
Paperless Recorder
with TFT display
and
CompactFlash card
B 70.6580.2.0
Interface Description
07.07/00472204

Contents
1 Introduction 5
1.1 Preface .......................................................................................................... 5
1.2 Typographical conventions ......................................................................... 6
1.2.1 Warning signs ................................................................................................. 6
1.2.2 Note signs ...................................................................................................... 6
1.2.3 Representation modes ................................................................................... 6
2 General 7
2.1 Areas of application ..................................................................................... 7
2.2 System requirements ................................................................................... 7
2.3 Identifying the interface ............................................................................... 7
3 Connecting the interface 9
3.1 Position of the connection .......................................................................... 9
3.2 RS232 .......................................................................................................... 11
3.3 Switching between RS232 and RS485 ..................................................... 11
3.4 Configuration of the serial interfaces ....................................................... 12
3.5 Configuration of the Ethernet interface ................................................... 13
3.5.1 Parameters ................................................................................................... 13

Contents
4 Modbus protocol description 15
4.1 Master-slave principle ............................................................................... 15
4.2 Transmission mode (RTU) ......................................................................... 15
4.3 Timing sequence for communication ....................................................... 16
4.4 Structure of a Modbus telegram ............................................................... 17
4.5 Device address ........................................................................................... 18
4.6 Function codes ........................................................................................... 18
4.6.1 Read n bits ................................................................................................... 19
4.6.2 Read n words ............................................................................................... 19
4.6.3 Write one bit ................................................................................................. 20
4.6.4 Write one word ............................................................................................. 21
4.6.5 Write n words ............................................................................................... 21
4.7 Transmission format (integer, float, double and text values) ................. 22
4.8 Checksum (CRC16) .................................................................................... 24
4.9 Error messages .......................................................................................... 25
4.9.1 Modbus error codes ..................................................................................... 25
4.9.2 Error messages for invalid values ................................................................ 26
4.9.3 JUMO error codes as integer return values ................................................. 27
5 Serial protocol types 33
5.1 Modbus slave .............................................................................................. 33
5.2 Modbus master .......................................................................................... 35
5.3 Bar code ...................................................................................................... 37
6 Ethernet protocols 38
6.1 HTTP ............................................................................................................ 38
6.2 Browser connection ................................................................................... 38
6.3 Modbus-TCP ............................................................................................... 39
6.4 E-mail (SMTP and POP3) ........................................................................... 40
7 Address tables 43
7.1 Modbus addresses for important device and process data .................. 43
8Index 53

5
1 Introduction
1.1 Preface
Please read this interface description before commissioning the interfaces for
the instrument. Keep the interface description in a place which is accessible to
all users at all times.
Please assist us to improve this interface description, where necessary.
Your comments will be appreciated.
Phone [phone]
Fax [phone]
All the necessary information for operating the interface is
contained in this interface description. However, if any difficulties
should still arise during start-up, please do not carry out any
unauthorized manipulations. You could endanger your rights under
the instrument warranty!
Please contact the nearest subsidiary or the head office in such a
case.
E
When returning modules, assemblies or components, the
regulations of EN 100 015 “Protection of electrostatically sensitive
components” must be observed. Use only the appropriate ESD
packaging for transport.
Please note that we cannot accept any liability for damage caused
by ESD.
ESD = electrostatic discharge

1 Introduction
6
1.2 Typographical conventions
1.2.1 Warning signs
The symbols for Danger and Caution are used in these operating instructions
under the following conditions:
1.2.2 Note signs
1.2.3 Representation modes
Danger This symbol is used when there may be danger to personnel if
the instructions are ignored or not followed correctly!
Caution This symbol is used when there may be damage to equipment
or data if the instructions are ignored or not followed correctly.
E
Caution This symbol is used where special care is required when
handling components liable to damage through electrostatic
discharge.
Note This symbol is used when your special attention is drawn to a
remark.
abc1Footnote Footnotes are remarks that refer to specific points in the text.
Footnotes consist of two parts:
A marker in the text, and the footnote text.
The markers in the text are arranged as continuous superscript
numbers.
0x0010 Hexadecimal
number A hexadecimal number is identified by being preceded by an “0x” (here: 16 decimal).

7
2 General
2.1 Areas of application
The paperless recorder has several interfaces:
- as standard: a TTL setup connector on the front panel, and on the back
(only for a Modbus slave)
- as standard: serial interface RS232 or RS485 (Modbus slave, Modbus
master, bar code)
for communication with the bus system or a PC. This can be used to read
out measurements or other device and process data from the paperless
recorder.
- as standard: Ethernet 10/100 Mbit/sec
for communication with the instrument via a network (setup, browser,
Modbus-TCP, e-mail alarm)
- optionally: serial interface RS232
for the connection of a bar code reader (Modbus slave, Modbus master, bar
code)
2.2 System requirements
The following items are required for operating the serial interface:
- Connecting cable:
for RS232 / RS485 e.g.
PC interface
with TTL/RS232 converter and adapter Part No. 70/00350260
PC interface
with USB/RS232 converter and adapter Part No. 70/00456352
for Ethernet interface, e.g.
RJ 45 patch cable, CAT 5 or better (crossover)
- setup or evaluation program, e.g.
setup program: Part No. 70/00468991
PC evaluation software PCA3000 Part No. 70/00431882
PCA communications software PCC Part No. 70/00431879
JUMO SVS-2000 visualization: data sheet 70.0753
- PC or notebook
2.3 Identifying the interface
The interface for RS232 or RS485 and the Ethernet interface are available in
every instrument.
The RS232 serial interface for connecting a bar code reader and the Profibus-
DP interface are options.

2 General
8
To see whether the instrument already has an additional option interface, use the
menu Device info !Hardware to check.

9
3.1 Position of the connection
Front panel
of the
paperless
recorder
Connection
diagram
Setup interface
Use either the setup interface on the front panel or the setup
interface on the back!
The connection on the front panel can only be made through the
setup interface with the connecting cable for “PC interface with
TTL/RS232 converter and adapter”, Part No. 70/00350260.
If the PC or notebook does not have a serial interface, then the
connecting cable “PC interface with USB/RS232 converter and
adapter”, is also required (Part No. 70/00456352).
The transmission parameters for the interface are fixed in the
instrument, and cannot be altered.
- baud rate = 9600 bps
- data format = 8 data bits, 1 stop bit, no parity
3 Connecting the interface

3 Connecting the interface
10
Rear view
of the
paperless
recorder
Connection
diagram
RS232/RS485
(1) RS232 interface for
bar code reader (option)
(4) Ethernet interface
(standard)
(2) Profibus-DP interface
(option)
(5) Setup interface
(standard)
(3) RS232/RS485 interface
(standard)
13
21 22 23 31 32 33 41 42 43 51 52 53 61 62 63 71 72 73
1234
10 11 12
123456
12
11
9
8
7
B12
B 9
B10
B11
B13
B14
B15
B16
B4
B1
B2
B3
B5
B6
B7
B8
+
+
+
UU
+
--
--
in out
U
Uout
U
Uin
33
44
11
22
123412341234123412341234
123412341234
PE
N
L1
(L+)
(L-)
4.
3.
2.
1.
11.
9.
10.
8.
7.
5.
6.
14.
(1) (2)
(5) (4) (3)
RS232 (connector (1) + (3)) RS485 (connector (3))
We recommend using a twisted-pair connecting cable
with shielding!
Only the signal lines shown above are to be connected, otherwise
errors will occur.

11
3 Connecting the interface
3.2 RS232
In the case of the RS232 interface, the handshake lines (RTS, CTS) are not
used. The RTS line from the master (PC or notebook), which is the CTS line for
the paperless recorder, will be ignored. The response is sent back immediately
by the paperless recorder. The CTS line of the master (RTS on the recorder)
remains open.
If the program that is used evaluates the handshake lines, then they must be
bridged in the cable.
PC COM
interface with
9-pin Sub-D
socket
PC COM
interface with
25-pin Sub-D
socket
3.3 Switching between RS232 and RS485
The changeover between the RS232 and RS485 interfaces is made through
the paperless recorder parameter
Configuration !Interfaces !Interface1 !General !Type
or, using the setup program
Edit !serial interface !RS232/RS485 !Type
(2) RxD
(3) TxD
(5) GND
RxD
TxD
RTS
CTS
GND
(2)
(3)
(7)
(8)
(5)
Paperless recorder PC or notebook
(2) RxD
(3) TxD
(5) GND
TxD
RxD
RTS
CTS
GND
(2)
(3)
(4)
(5)
(7)
Paperless recorder PC or notebook

3 Connecting the interface
12
3.4 Configuration of the serial interfaces
Configuration
on the
paperless
recorder
✱On the recorder, select Configuration !Interface !Interface 1/2
!General.
The parameters for the configuration of the interface will now be available.
Configuration
through setup
program
Configuration with the aid of the setup software is made through the menu
item Edit ➔Interface.
Parameter Value/Selection Description
Interface type ➔Type RS232,
RS485
Can only be edited for
interface 1.
See Chapter 3.3 Switching
between RS232 and
RS485, page 11
Protocol ➔Protocol Modbus slave,
Modbus master,
bar code
see Chapter 5 Serial
protocol types, page 33.
Baud rate ➔Baud rate 9600 bps,
19200 bps,
38400 bps
see Chapter 4.3 Timing
sequence for
communication, page 16.
Transmission mode
(RTU)
➔Data format 8-1-none,
8-1-odd,
8-1-even
see Chapter 4.2
Transmission mode (RTU),
page 15.
Device address ➔Device address 1 — 254 see Chapter 4.5 Device
address, page 18.
Min. response time ➔Min. response time 0— 500msec see Chapter 4.3 Timing
sequence for
communication, page 16.
For communication via the back panel RS232 interface and the
setup interface, the device address must be observed, even
though it is not a bus interface!
The configuration of the setup interface cannot be edited,
but is fixed to
- Modbus slave,
- 9600 bps,
- 8-1-none,
- device address 1
The three serial interfaces can be operated simultaneously. There
are merely some interlocks built in at the protocol level (e.g. only
one setup can be written at a time).

13
3 Connecting the interface
3.5 Configuration of the Ethernet interface
Configuration
on the
paperless
recorder
is carried out via the menu item Configuration ➔Interface ➔Ethernet.
Configuration
via setup
program
is carried out via the menu item Extras ➔Ethernet interface.
3.5.1 Parameters
DHCP DHCP (Dynamic Host Configuration Protocol) is used so that the paperless
recorder can automatically receive an IP address and other communication
parameters from a DHCP server.
The other communication parameters that the paperless recorder usually
receives from the DHCP server include the subnet mask, gateway address,
and the lease time.
When the lease time (user time) has expired, the IP address loses its validity. In
order that the paperless recorder may always have a valid IP address, it sends
a query to its DHCP server whether the address is still valid when 50 of the
lease time has expired. If the DHCP server is not available, the recorder
repeats the query until 87.5% of the lease time has expired. After that, the
recorder sends the query not only to the DHCP server, but to the entire
network. If the lease time expires without the IP address being confirmed, the
recorder declares the address as invalid and is no longer accessible in the
network.
On DHCP is switched on, the recorder receives its IP
address from the DHCP server

3 Connecting the interface
14
The automatically assigned IP address can be read in the menu Device
manager !Device info !Eth. Info.
Manual IP
address If automatic IP address assignment is not used (DHCP = OFF), then the IP address for the paperless recorder is set up here.
Subnet mask If automatic IP address assignment is not used (DHCP = OFF), then the subnet
mask is set up here.
The subnet mask is used to gather devices (PC, recorders etc.) together to
form subnets. All devices that have an IP address that is AND linked to the
subnet mask belong to one subnet and can communicate with one another.
If devices outside the subnet need to be accessed, then the communication
must be handled by a gateway (standard gateway).
Standard
gateway If automatic IP address assignment is not used (DHCP = OFF), then the IP address for the standard gateway is set up here.
The standard gateway is used for communication with devices that do not
belong to the subnet.
Port Modbus
TCP The port address must be set if the paperless recorder needs to be accessed by visualization software, and the Modbus TCP protocol (Modbus tunneling:
outer frame = Ethernet, inner frame = Modbus) is to be used.
DNS server This is used to set up the IP address for a DNS server that is installed in the
network. The DNS server is required to resolve the name for e-mail transfer via
Ethernet.
Transfer rate Here you can configure the transfer rate that is used for communication
between the paperless recorder and the DHCP server or other computers.
An assigned address can be altered by the DHCP server. For
example, if the PCA communications software is used for the
automatic collection of data, then the address must be altered
within the software.
Any change to this parameter will only becomes effective after the
recorder has been restarted!
Any change to this parameter will only become effective after the
recorder has been restarted!

15
4 Modbus protocol description
4.1 Master-slave principle
When using Modbus/Jbus, the communication between a master (PC or
notebook) and a slave device (paperless recorder), takes place according to
the master-slave principle, in the form of a data request/instruction - response.
The master controls the data exchange, the slaves only have a response
function. They are identified by their device addresses.
4.2 Transmission mode (RTU)
The transmission mode used is the RTU mode (Remote Terminal Unit). Data
are transmitted in binary format (hexadecimal) with 8 bits, as 16-bit integer
values, or as 32-bit float values.
Data format The data format describes the structure of a transmitted byte.
The paperless recorder can be operated either as a Modbus slave,
see Chapter 5.1 Modbus slave, page 33, or as a Modbus master,
see Chapter 5.2 Modbus master, page 35.
In a Modbus network, only one device is allowed to take on the
master function!
Master
Slave 1 Slave 2 Slave n
Data word Parity bit Stop bit Number of bits
8 bits none (no) 1 9
8 bits even 1 10
8 bits odd 1 10
The data format that is to be used can be selected, see Chapter
3.4 Configuration of the serial interfaces, page 12.

4 Modbus protocol description
16
4.3 Timing sequence for communication
Character
transmission
time
The start and end of a data block are marked by transmission pauses. The
character transmission time (the time taken to transmit one character)
depends on the baud rate and the data format that is used.
For a data format with 8 data bits, no parity bit and one stop bit, this is:
character transmission time [msec] = 1000 * 9 bits / (baud rate)
For the other data formats it is:
character transmission time [msec] = 1000 * 10 bits / (baud rate)
Example
Timing
sequence A data request runs according to the following timing sequence:
Baud rate [bps] Data format [bit] Character transmission
time [msec]
38400 10 0.260
9 0.234
19200 10 0.521
9 0.469
9600 10 1.042
9 0.938
t1Internal waiting time of the paperless recorder before checking the
data request, and the internal processing time.
min.: 5 msec
typical: 5 — 45 msec
max.: 60 msec, or the preset “minimum response time”

17
4 Modbus protocol description
While t1and t2are running, the master must not present any further data
requests, since the paperless recorder will either ignore them or declare them
to be invalid.
4.4 Structure of a Modbus telegram
Data structure All telegrams have the same structure:
Each telegram contains four fields:
Slave address the device address of a specific paperless recorder
Function code function selection (read/write a word)
Data field contains the information (depending on the function code):
- word address / bit address
- word number / bit number
- word value /bit values
Checksum detection of transmission errors
A minimum response time can be set in the controller, in the menu
item Configuration ➔Interface. This setting is the minimum waiting
time that must elapse before an answer is transmitted (0 — 500
msec). If a smaller value is set, then the response time may be
longer than the preset value (because the internal processing time
is longer), the controller will then answer as soon as the internal
processing is completed. A preset time of 0 msec means that the
controller answers with the maximum possible speed.
The minimum response time which can be set is required by the
RS485 interface in the master, in order to switch over the interface
driver from transmit to receive. This parameter is not required for
the RS232 interface.
t2This is the waiting time which the master has to observe before
initiating a new data request.
for RS232 at least 3.5 x the transmission time for
one character (this time depends on the
baud rate)
for RS485 60msec
Slave address Function code Data field Checksum
CRC16
1 byte 1 byte x byte(s) 2 bytes

4 Modbus protocol description
18
4.5 Device address
The device address for the paperless recorder can be set between 1 and 254
(decimal), see Chapter 3.4 Configuration of the serial interfaces, page 12.
4.6 Function codes
Function
summary The functions described below can be used to read out measurements and other device and process data from the paperless recorder.
A maximum of 31 paperless recorders can be addressed via the
RS485 interface.
Device address 0 is reserved as the Modbus broadcast address.
An instruction from the master for address 0 will be carried out by
all the slaves, but none of them will answer (because this would
lead to a data collision).
If only one recorder is connected to the PC or notebook, then it
can also be accessed through device address 255 (even if a
different address has been configured). The paperless recorder will
always respond to instructions for device address 255.
In the transmission protocol, the address is given in binary format
(hexadecimal).
Function
number Function Restriction
0x01 or 0x02 read n bits max. 256 bits (16 bytes)
0x03 or 0x04 read n words max. 127 words (254 bytes)
0x05 write one bit max. 1 bit
0x06 write one word max. 1 word (2 bytes)
0x10 write n words max. 127 words (254 bytes)
If the recorder does not respond to one of these functions, or reacts
by generating an error code, then please refer to Chapter 4.9 Error
messages, page 25.

19
4 Modbus protocol description
4.6.1 Read n bits
This function reads n bits, starting from a defined address.
Data request
Response
Example Read one bit, starting at address 0x0340 (word address 0x0034).
For addresses, see Chapter 7.1 Modbus addresses for important device and
process data, page 43.
Data request:
Response:
4.6.2 Read n words
This function reads n words, starting from a defined address.
Data request
Response
Example Read the first 3 analog inputs (i.e. the first 6 words starting at Modbus address
0x1257).
For the addresses of the analog inputs, see Chapter 7.1 Modbus addresses
for important device and process data, page 43.
Slave
address
Function
0x01 or 0x02
Address
first bit
Number
of bits
Checksum
CRC16
1 byte 1 byte 2 bytes 2 bytes 2 bytes
Slave
address
Function
0x01 or 0x02
Number
of bits read
bit
value(s)
Checksum
CRC16
1 byte 1 byte 1 byte x byte(s) 2 bytes
The response is always made in complete 8-bit bytes.
The byte values that are not required are filled with the value 0.
01 02 0340 0001 B85A
01 02 01 01 6048
bit value
Slave
address
Function
0x03 or 0x04
Address
of first word
Number
of words
Checksum
CRC16
1 byte 1 byte 2 byte 2 bytes 2 bytes
Slave
address
Function
0x03 or 0x04
Number
of bytes
read
Word
value(s)
Checksum
CRC16
1 byte 1 byte 1 byte x byte(s) 2 bytes

4 Modbus protocol description
20
Data request:
Response:
4.6.3 Write one bit
For the “Write one bit” function, the data blocks for instruction and
response are identical.
Instruction
Response
Example Write one bit, at bit address 0x0340 (i.e. bit 0 of the word address 0x0034).
For addresses, see Chapter 7.1 Modbus addresses for important device and
process data, page 43.
Instruction:
Response (as instruction):
01 03 1257 0006 7160
01 03 0C 1999 4348 4CCC 4348 2666 4396 8548
Measurement 1
200.1
Measurement 2
200.3
Measurement 3
300.3
Slave
address Function 0x05 Bit address Bit value xx00 Checksum CRC16
1 byte 1 byte 2 bytes 2 bytes 2 bytes
xx = 00 !bit
is set to 0
xx = FF !bit
is set to 1
Slave
address Function 0x05 Bit address Bit value Checksum CRC16
1 byte 1 byte 2 bytes 2 bytes 2 bytes
01 05 0340 FF00 8DAA
01 05 0340 FF00 8DAA