JUMO LOGOSCREEN nt Interface Description

Download

JUMO LOGOSCREEN nt

Paperless recorder

with TFT display, CompactFlash card

and USB interfaces

B 706581.2.0

Interface Description

V1.00/EN/00504688

Contents

1 Introduction 5

1.1 Preface .......................................................................................................... 5

1.2 Typographical conventions ......................................................................... 6

1.2.1 Warning signs ................................................................................................. 6

1.2.2 Note symbols ................................................................................................. 6

1.2.3 Number types ................................................................................................. 6

2 General information 7

2.1 Target group .................................................................................................. 7

2.2 Interfaces ...................................................................................................... 7

2.3 System prerequisites ................................................................................... 7

3 Connecting the interface 9

3.1 Connection position ..................................................................................... 9

3.2 RS232 .......................................................................................................... 11

3.3 Toggling 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

4 Modbus protocol description 15

4.1 Master-Slave principle ............................................................................... 15

4.2 Transmission mode (RTU) ......................................................................... 15

4.3 Timing of the 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 bit ..................................................................................................... 19

4.6.2 Read n words ............................................................................................... 20

4.6.3 Write one bit ................................................................................................. 21

4.6.4 Write one word ............................................................................................. 22

4.6.5 Write n words ............................................................................................... 23

4.7 Transmission format (integer, float, double and text values) ................. 24

Contents

4.8 Checksum (CRC16) .................................................................................... 27

4.9 Error messages .......................................................................................... 28

4.9.1 Modbus error codes ..................................................................................... 28

4.9.2 Error messages for invalid values ................................................................ 29

4.9.3 Error codes as integer return values ............................................................ 30

5 Serial protocol types 35

5.1 Modbus slave .............................................................................................. 35

5.2 Modbus master .......................................................................................... 38

5.3 Barcode ....................................................................................................... 39

6 Ethernet protocols 41

6.1 HTTP ............................................................................................................ 41

6.2 Browser connection ................................................................................... 41

6.3 Modbus TCP ............................................................................................... 42

6.4 Email (SMTP and POP3) ............................................................................. 44

7 Address tables 47

7.1 Data types and type of access .................................................................. 47

7.2 Modbus addresses of important device and process data .................... 47

8Index 65

1.1 Preface

1 Introduction

Please read this interface description before commissioning the interfaces of the device. Keep the interface description in a place accessible to all users at all times.

Please assist us in improving this Interface description.

Your comments are highly appreciated.

All information required to operate the interface is described in the supplied Interface description. Nevertheless, should problems be encountered during commissioning/start-up, please refrain from carrying out any inadmissible manipulations. This could jeopardize your warranty rights!

Please contact the nearest subsidiary or the head office.

When returning controller modules, assemblies or components, please observe the regulations according to DIN EN 61340-5-1 and DIN EN 61340-5-2 „Protection of electrostatic sensitive devices“. For transport, only use ESD packages.

Please note that we cannot accept any liability for damage caused by ESD.

ESD=Electro Static Discharge

1 Introduction

1.2 Typographical conventions

1.2.1 Warning signs

The symbols for Caution and Attention are used in this operating manual under the following conditions:

Caution This symbol is used when there may be danger to personnel if

the instructions are ignored or not followed correctly!

Attention This symbol is used when there may be damage to equipment

or data if the instructions are ignored or not followed correctly!

Attention This symbol is used where special care is required when

handling components liable to damage through electrostatic discharge.

1.2.2 Note symbols

Note This symbol is used when your special attention is drawn to a

abc

Footnote Footnotes are remarks that refer to specific points in the text.

1.2.3 Number types

0x0010 Hexadecimal

number

remark.

Footnotes consist of two parts: A marker in the text and the foot note text itself. The markers in the text are arranged as continuous superscript

numbers.

A hexadecimal number is identified by „0x“ preceding the actual number (here: 16 decimal).

2 General information

2.1 Target group

This operating manual is intended for user, who want to use the paperless recorder as a Modbus slave and read out data from a Modbus master (e.g. PLC).

2.2 Interfaces

ex-factory The paperless recorder is equipped with several interfaces as a standard:

• Serial interface RS232 or RS485

• Serial interface RS232 (barcode scanner)

• Ethernet 10/100 MBit/s

• 2 USB host and 2 USB device interfaces The serial and the ethernet interfaces serves for communication with a bus

system or PC. They can be used, for example, to read out the measured values and/or instrument and process data from the paperless recorder. In connection with the ethernet interface and a PC webbrowser, recorders can be monitored via the internet. Two RS232 interfaces are available. Both interfaces are to be considered as equal.

The USB interfaces are fitted on the front and the back and intended for the operation with the setup program or the PCA communication software (PCC) or for reading out data via the USB memory stick. Only use one USB host or USB device interface at a time. Instruments with stainless steel fronts are not equipped with USB interfaces on the front.

Extra code The paperless recorder is equipped with several interfaces as an option:

• PROFIBUS-DP interface

2.3 System prerequisites

The following items are required for interface operation:

• Connection line: for RS232 Interface cable RS232 (9/9-pin): TN 00367735 Interface cable RS232 (9/25-pin): TN 00367736 for ethernet, e.g. RJ 45 patch cable, CAT 5 or higher (cross over)

• Setup or evaluation program, e.g. Setup program: TN 00468991 PC evaluation software PCA3000: TN 00431882 PCA communication software PCC: TN 00431879 JUMO SVS3000 Visualization: Data Sheet

700755

• PC or notebook

2 General information

3.1 Connection position

USB host

for the data exchange

(measured data,

configuration data,

user lists) between paperless

recorder and PC

USB device

for communication with the setup program or PCC

Front view of the paperless recorder

3 Connecting the interface

Connection diagram

Use a USB interface either at the front or at the rear! Only use one host or device interface at a time.

USB host = Plug type A USB device = Plug type B mini

3 Connecting the interface

123

10 11

B12

B10

B11

B13

B14

B15

B16

out

12341234123

11.

10.

14.

(L+)

(L-)

15.

(1) (2)

(3) (4) (5)

(6)

Rear view of the paperless recorder

(1) RS232 interface for

barcode scanner (serial)

(2) PROFIBUS-DP interface

(optional)

(3) USB host interface

(serial)

(4) Ethernet interface

(serial)

(5) RS232/485 interface

(serial)

(6) USB device interface

(serial)

Connection diagram

RS232 (plugs (1) + (5)) RS485 (plug (5))

RS232/RS485

We recommend the use of a twisted connection cable with shielding! Only connect the signals specified above, otherwise errors will

occur!

3.2 RS232

(2) RxD (3) TxD (5) GND

RxD TxD

RTS CTS

GND

(2) (3)

(7) (8)

(5)

Paperless recorder

PC/notebook

(2) RxD (3) TxD

(5) GND

TxD RxD RTS CTS GND

(2) (3) (4) (5) (7)

Paperless recorder

PC/notebook

PC COM interface with 9pin Sub-D socket

3 Connecting the interface

The RS232 interface does not use the handshake lines (RTS, CTS). The RTS line (CTS on the paperless recorder) coming from the master (PC or notebook) is not taken into consideration. The response is immediately transmitted from the paperless recorder. The CTS line of the master (RTS on the paperless recorder) remains open.

If the used program evaluates the handshake lines, they must be bridged in the cable.

PC COM interface with 25-pin Sub-D socket

3.3 Toggling between RS232 and RS485

Toggling between RS232 and RS485 interface is carried out by means of the paperless recorder parameter

Configuration

or via the setup program

Edit

 Serial interface  RS232/RS485  Type

 Interface  RS232/RS485  General  Type

3 Connecting the interface

3.4 Configuration of the serial interfaces

Configuration on the paperless

✱ Select Configuration  Interface  RS232/RS485  General on the

paperless recorder. Now the parameters required to configure the interface are available.

recorder

Configuration via the setup

The Edit

➔ Serial interface  RS232/RS485 menu point is used for the

configuration by means of the setup software.

program

Parameters Value/Selection Description

Device address ➔ Device address 1...254 see Chapter 4.5 Device

address, Page 18.

Interface type ➔ Ty pe RS232,

RS485

Protocol ➔ Protocol Modbus slave,

Modbus master, Barcode

Baud rate ➔ Baud rate 9600 baud,

19200 baud, 38400 baud

Transmission mode (RTU)

Min. response time ➔ Min. response time 0 ... 500ms see Chapter 4.3 Timing of

➔ Data format 8 - 1 - no Parity,

8 -1 - odd Parity, 8 -1 - even Parity

Can only be edited for RS232/RS485.

See Chapter 3.3 Toggling between RS232 and RS485, Page 11.

see Chapter 5 Serial protocol types, Page 35

see Chapter 4.3 Timing of the communication, Page

16. see Chapter 4.2 Transmission mode (RTU), Page 15.

the communication, Page

16.

For communication via the RS232 interfaces, the device address has to be taken into account although it is not a bus interface.

The serial interfaces as well as the USB and Ethernet interface can be operated simultaneously. Only on the protocol level, some inhibits are present (e.g. only one setup may be written at a time).

3 Connecting the interface

3.5 Configuration of the Ethernet interface

Configuration on the paperless recorder

Configuration via the setup program

is carried out using the Configuration ➔ Interface ➔ Ethernet menu point.

is carried out using the Extras

➔ Ethernet interface menu point.

3.5.1 Parameters

DHCP DHCP (Dynamic Host Configuration Protocol) is used to ensure that the

paperless recorder is automatically assigned an IP address and further communication parameters by a DHCP server.

On DHCP is switched on, the paperless recorder obtains its

IP address by the DHCP server

The further communication parameters usually assigned to the paperless recorder by the DHCP server include, among others, the subnet mask, the standard gateway address and the so-called lease time.

After the lease time (period of use) has elapsed, the validity of the IP address expires. To ensure that the paperless recorder always has a valid IP address, after 50% of the lease time it transmits a query to the known DHCP server asking whether or not the address is still valid. If the DHCP server cannot be accessed, the paperless recorder repeats its query until 87.5% of the lease time has elapsed. Then the paperless recorder transmits its query not only to the DHCP server but also to the entire network. When the lease time has elapsed and the IP address is still not acknowledged, the paperless recorder declares the address as invalid and is no longer accessible via the net.

3 Connecting the interface

The DHCP server can change an assigned address. If, for

example, automatic data download with the PCA communication software is used, the address must be changed within the software.

The automatically assigned IP address query can be inquired in the Device

manager

IP address If automatic IP address assignment is not used ("DHCP = OFF"), the IP

address of the paperless recorder is set here.

Subnet mask If automatic IP address assignment is not used ("DHCP = OFF"), the subnet

mask is set here. The subnet mask is used to group devices (PC, paperless recorder, etc.) into

subnets. All devices, the IP address of which is linked with AND identical to the subnet mask, belong to one subnet and can communicate with each other.

If devices are to be accessed outside the subnet, communication must be carried out via a gateway (standard gateway).

 Device info  Ethernet info menu.

Standard Gateway

Port Modbus TCP

DNS Device name

DNS server Here the IP address of a DNS server installed in the network is set. The DNS

If automatic IP address assignment is not used ("DHCP = OFF"), the address of the standard gateway is set here.

The standard gateway is used for communication by devices which are not part in a subnet.

The port address must be set when the paperless recorder is accessed by a visualization software and the Modbus TCP protocol (Modbus tunneling: external frame Ethernet, internal frame Modbus) is used.

Changes to this parameter will become effective after the paperless recorder has been restarted.

The DNS device name is entered here. This ensures that the device can be accessed not only via its IP address but also via its name.

server is required to convert the name for Email transmittion via Ethernet.

Changes to this parameter will become effective after the paperless recorder has been restarted.

Transfer rate The transfer rate used by the paperless recorder to communicate with the

DHCP server and other PCs is configured here.

4.1 Master-Slave principle

Master

Slave 1 Slave 2 Slave n

Communication between a master (PC or notebook) and a slave (paperless recorder) using the Modbus/J-bus takes place according to the master-slave principle, in the form of data request/instruction - response.

The master controls the data exchange, the slaves only have a response function. They are identified by their device address.

The paperless recorder can be operated either as a Modbus slave, see Chapter 5.1 Modbus slave, Page 35, or as a Modbus master, see Chapter 5.2 Modbus master, Page 38.

4 Modbus protocol description

In a Modbus network, only one master function.

device can be assigned with the

4.2 Transmission mode (RTU)

The transmission mode used is the RTU mode (Remote Terminal Unit). The data is transmitted in the binary format (hexadecimal) with 8 or 16 bits for integer values and 32 bits for float values.

Data format The data format describes the structure of a byte transmitted.

Data word Parity bit Stop bit Number of bits

8 bits no 1 9 8 bits even 1 10 8 bits odd 1 10

The data format to be used can be set, see Chapter 3.4 Configuration of the serial interfaces, Page 12.

4 Modbus protocol description

Master

Slave

Data request

Response

Data request

4.3 Timing of the communication

Character transmission time

Example

Timing scheme A data request runs according to the following timing scheme:

Start and end of a data block are marked by transmission pauses. The character transmission time (time required to transmit one single character) depends on the baud rate and the data format used.

For a data format of 8 data bits, no parity bit and one stop bit, this is:

Character transmission time [ms] = 1000 * 9 bit ÷ baud rate

For the other data formats, this is:

Character transmission time [ms] = 1000 * 10 bit ÷ baud rate

Baud rate [baud] Data format [bit]

38400

19200

9600

10 0,260

9 0,234

10 0,521

9 0,469

10 1,042

9 0,938

character transmission

time [ms]

Internal waiting time of the paperless recorder prior to checking the data request and the internal processing time.

min.: 5 ms typical: 5 ... 45 ms max.: 60 ms or set "minimum response time"

4 Modbus protocol description

A minimum response time can be set in the controller under the menu point Configuration minimum waiting time before an answer is transmitted (0…500 ms). If a smaller value is set, then the response time may be longer than the preset value (internal processing takes longer), the controller answers as soon as internal processing is completed. The preset time of 0 msec means that the controller responds at the maximum possible speed.

The minimum response time, which can be set is required by the RS485 interface in the master, to be able to switch over the interface drivers from transmit to receive. This parameter is not required for the RS232 interface.

➔ Interface. This preset time is the

No data requests from the master are permitted during t1 and t2 , because the paperless recorder will either ignore the request or declare it to be invalid.

The master has to observe this waiting time before starting a new data request.

for RS232 min. 3.5 times the transmission time

for RS485 60ms

4.4 Structure of a Modbus telegram

Data structure All telegrams have the same structure:

Slave address Function code Data field Checksum

1 byte 1 byte x byte 2 byte

Each telegram contains four fields: Slave address device address of a specific paperless recorder

required for 1 character (the time depends on the baud rate)

CRC16

Function code function selection (read, write words) Data field Contains information (according to the function code):

• Word address/bit address

• Number of words/bits

•word/bit values

Checksum detection of transmission errors

4 Modbus protocol description

4.5 Device address

The device address of the paperless recorder can be set between 1 and 254 (decimal), see Chapter 3.4 Configuration of the serial interfaces, Page 12.

A maximum of 31 paperless recorders can be addressed via the RS 485 interface.

The device address 0 is reserved as the Modbus broadcast address. An instruction of the master to address 0 is carried out by all slaves, but no response is transmitted by them (because this would result in a data collision).

If only one paperless recorder is connected to the PC or notebook, it can also be addressed via device address 255 (even if a different device address is configured). The paperless recorder always responds to instructions using device address 255.

In the transmission protocol, the address is specified in the binary format (hexadecimal).

4.6 Function codes

Function overview

The functions described as follows can be used to read out the measured values and further device and process data from the paperless recorder.

Function number

0x01 or 0x02 Read n bit 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)

Function Limitation

Please refer to Chapter 4.9 Error messages, Page 28, if the paperless recorder does not react to these functions or emits an error code.

4.6.1 Read n bit

4 Modbus protocol description

This function is used to read n bits starting from a specific address.

Data request

Response

Example Reading a bit starting from bit address 0x0340 (this is word address 0x0034).

Slave

address

1 byte 1 byte 2 byte 2 byte 2 byte

Slave

address

1 byte 1 byte 1 byte x byte 2 byte

The response always comes in full bytes of 8 bits each. Non-requested bit values will be complemented with the 0 value.

For the addresses please refer to Chapter 7.2 Modbus addresses of important device and process data, Page 47.

Data request:

01 02 0340 0001 B85A

Response:

01 02 01 01 6048

Function

0x01 or 0x02

Function

0x01 or 0x02

Bit value

Address

first bit

Number of

byte read

Number

of bits

Bit

value(s)

Checksum

CRC16

Checksum

CRC16

4 Modbus protocol description

4.6.2 Read n words

This function is used to read n words starting from a specific address.

Data request

Response

Example Reading the first 3 analog inputs (these are the first 6 words starting from

Slave

address

1 byte 1 byte 2 byte 2 byte 2 byte

Slave

address

1 byte 1 byte 1 byte x byte 2 byte

Modbus address 0x1257). For the analog input address please refer to Chapter 7.2 Modbus addresses of

important device and process data, Page 47.

Data request:

01 03 1257 0006 7160

Response:

01 03 0C 1999 4348 4CCC 4348 2666 4396 8548

Function

0x03 or 0x04

Function

0x03 or 0x04

Measured

value 1

200,1

Address

first word

Number of

byte read

Measured

value 2

200,3

Number

words

Word

value(s)

Measured

value 3

Checksum

CRC16

Checksum

CRC16

300,3

4.6.3 Write one bit

In the write bit function, the data blocks for instruction and response are identical.

4 Modbus protocol description

Instruction

Response

Example Writing a bit starting from bit address 0x0340 (this is bit 0 of the word address

Slave

address

1 byte 1 byte 2 byte 2 byte 2 byte

Slave

address

1 byte 1 byte 2 byte 2 byte 2 byte

0x0034). For the addresses please refer to Chapter 7.2 Modbus addresses of important

device and process data, Page 47. Instruction:

01 05 0340 FF00 8DAA

Response (as instruction):

Function

0x05

Function

0x05

Bit address Bit value

xx00

xx = 00  Bit is set to 0 xx = FF  Bit is set to 1

Bit address Bit value Checksum

Checksum

CRC16

01 05 0340 FF00 8DAA

4 Modbus protocol description

4.6.4 Write one word

In the write word function, the data blocks for instruction and response are identical.

Instruction

Response

Example Set the variable "External Binary In 1" (Modbus address 0x1638) to 1.

Slave

address

1 byte 1 byte 2 byte 2 byte 2 byte

Slave

address

1 byte 1 byte 2 byte 2 byte 2 byte

For the addresses please refer to Chapter 7.2 Modbus addresses of important device and process data, Page 47.

Instruction:

01 06 1638 0001 CD8F

Response (as instruction):

01 06 1638 0001 CD8F

Function

0x06

Function

0x06

Word address Word value Checksum

CRC16

Word address Word value Checksum

CRC16

4.6.5 Write n words

4 Modbus protocol description

instruction

Response

Example Writing the word "Test" (ASCII coding: 0x54 0x65 0x73 0x74 0x00) to address

Slave

Address

1 byte 1 byte 2 byte 2 byte 1 byte x byte 2 byte

Slave

address

1 byte 1 byte 2 byte 2 byte 2 byte

0x148A ff to ensure that this text is entered in the event list of group 1: Instruction:

01 10 148A 0003 06 54 65 73 74 00 00 9BFA

Response:

01 10 148A 0003 A412

Function 0x10

Address

word

Function

0x10

first

Number

words

Address

first word

Number

words

Number of

words

Number

value(s)

Check

CRC16

Checksum

CRC16

sum

4 Modbus protocol description

4.7 Transmission format (integer, float, double and text values)

Integer values Integer values are transmitted via the Modbus in the following format:

The high byte first, followed by the low byte.

Example Request of the integer value of address 0x1017, if value "4" (word value

0x0004) is written under this address. Request: 01031017000130CE (CRC16 = CE30)

Response: 0103020004B987 (CRC16 = 87B9)

Float values In the case of float values, the Modbus operates with the IEEE-754 standard

format (32bits), the only difference being that byte 1 and 2 are changed over with byte 3 and 4.

Single-float format (32bit) as per IEEE 754standard

SEEEEEEE EMMMMMMM MMMMMMMM MMMMMMMM

Byte 1 Byte 2 Byte 3 Byte 4

S - sign bit E - exponent (two's complement) M - 23bits normalized mantissa

Modbus float format

Modbus address x Modbus address x+1

MMMMMMMM MMMMMMMM SEEEEEEE EMMMMMMM

Byte 3 Byte 4 Byte 1 Byte 2

Example Request of the float value of address 0x0035, if value "550.0" (0x44098000 in

IEEE-754 format) is written under this address. Request: 140300350002D6C0 (CRC16 = C0D6)

Response: 140304800044096434 (CRC16 = 3464) Once transmission from the device is completed, the bytes of the float value

need to be changed over accordingly. A large number of compilers (e.g. Microsoft Visual C++) file the float values in

the following order:

Float value

Address x Address x+1 Address x+2 Address x+3

MMMMMMMM MMMMMMMM EMMMMMMM SEEEEEEE

Byte 4Byte 3Byte 2Byte 1

Please find out the way float values are saved in your application. After the request from the paperless recorder, it might be necessary to change the bytes over in the interface program you are using.

4 Modbus protocol description

Double values The double values are also processed in the Modbus in the IEEE-754 standard

format (32bit). Unlike float values, bytes are not changed over for double values.

Doupble-float format (32bit) as per IEEE 754standard

SEEEEEEE EEEEMMMM MMMMMMMM MMMMMMMM

Byte 1 Byte 2 Byte 3 Byte 4

MMMMMMMM MMMMMMMM MMMMMMMM MMMMMMMM

Byte 5 Byte 6 Byte 7 Byte 8

S - sign bit E - exponent (two's complement) M - 52bits normalized mantissa

Modbus double format

Modbus address x Modbus address x+1

SEEEEEEE EEEEMMMM MMMMMMMM MMMMMMMM

Byte 1 Byte 2 Byte 3 Byte 4

Modbus address x+2 Modbus address x+3

MMMMMMMM MMMMMMMM MMMMMMMM MMMMMMMM

Byte 5 Byte 6 Byte 7 Byte 8

Example Request of the double value of address 0x0066, if value 1234567.89

(0x4132D687E3D70A3D in the IEEE-754 format) is written under this address. Request: 140300660004A6D3 (CRC16 = D3A6)

Response: 1403084132D687E3D70A3DE1C1 (CRC16 = C1E1)

Please find out the way double values are saved in your application. After the request from the paperless recorder, it might be necessary to change the bytes over in the program you are using.

4 Modbus protocol description

Strings (texts) Character strings are transmitted in the ASCII format.

To mark the end, the last character to be transmitted can be a "\0" (ASCII code 0x00). Characters after this mark are without significance.

Knowing that the transmission of texts takes place word by word (16 bits), 0x00 is additionally appended where an odd number of characters is used (incl. "\0").

The maximum length specified in the address tables (see “Address tables” on page 47. ff) for strings also includes the terminating "/0". This means, in the case of "char 11", the text can consist of max. 10 readable characters.

Example Text inquiry from address 0x1000, if the

character string "LS NT" (ASCII code: 0x4C, 0x53, 0x20, 0x4E, 0x54, 0x00) is entered under this address.

Request: 01031000000440C9 Response: 0103084C53204E540000AA0D96

Instead of "AA" in front of the CRC sum, there could be any value, because it is behind "/0" and will be ignored.

4.8 Checksum (CRC16)

4 Modbus protocol description

Calculation scheme

Example 1 Requesting the status of relay output 1.

The checksum (CRC16) serves to recognize transmission errors. If an error is identified during evaluation, the device concerned does not respond.

CRC = 0xFFFF

CRC = CRC XOR ByteOfMessage For (1 to 8)

CRC = SHR(CRC) if (flag shifted right = 1) then else CRC = CRC XOR 0xA001

while (not all ByteOfMessage processed);

The low byte of the check sum is the first to be transmitted!

Instruction: Read a word from the address 0x1631

01 03 1631 0001 D18D

Response (CRC = 0x8479):

01 03 02 0001 7984

Word 1

Word 1 = 1 indicates that relay 1 is active.

4 Modbus protocol description

4.9 Error messages

4.9.1 Modbus error codes

No response by the paperless recorder

Error codes If the data request of the master has been received by the paperless recorder

In the event of the following errors, the slave will not respond:

• Baud rate and/or data format of Master (PC or notebook) and Slave (paperless recorder) are not compatible.

• The device address of the paperless recorder does not comply with that contained in the protocol.

• The checksum (CRC16) is not correct.

• The instruction from the Master is incomplete or over-defined.

• The number of words to be read is zero.

In these cases the data request should be transmitted again once the timeout time (2s) has elapsed.

without transmission errors but could not be processed, the paperless recorder will respond with an error code.

The following error codes can be occur:

• 01 Invalid error code

• 02 Invalid address or number of words or bits to be read or written is too large

• 03 Value not within the admissible range

• 08 Value wirte-protected

Response in the event of an error

Example Data request:

Slave

address

1 byte 1 byte 1 byte 2 byte

0x80 is used to set the function code to its OR status, i.e. the MSB (most significant bit) is set to 1.

01 06 1257 0001 FCA2

Response:

01 86 08 43A6

Respons is error code 08 because address 0x1257 is write-protected.

Function

XX OR 80h

Error code Checksum

CRC16

4 Modbus protocol description

4.9.2 Error messages for invalid values

For measured values in the float format, the error number appears directly in the value, i.e. the error number is entered instead of the measured value.

Error code for float values

1.0 x 10

2.0 x 10

3.0 x 10

4.0 x 10

5.0 x 10

6.0 x 10

7.0 x 10

8.0 x 10

Example Data request:

01 03 1259 0002 1160

Response:

Error

Underrange

Overrange

No valid input value

Division by zero

Math error

Invalid terminal temperature of thermocouple

Invalid float value

Integrator or statistics destroyed

01 03 04 8E52 7DB4 51ED

The measured value 0x7DB48E52 (=3.0 x 10

) supplied by analog input 2

(Modbus address 0x1259) indicates that the input value is invalid.

4 Modbus protocol description

4.9.3 Error codes as integer return values

For some lengthy sequences (e.g. email transfer) an error code is entered at the end into an event field or the event list.

Error codes

Error code Description Error list: Program memory management

1 Program cannot be created

2 Program does not exist

3 Program cannot be deleted

4 Segment cannot be deleted

5 Checksum cannot be saved

6 Checksum cannot be read

7 Program cannot be copied

8 Segment cannot be copied

9 Program checksum error

10 Program pointer tab. checksum error

11 Program memory end

12 Segment does not exist

13 Repeat jump marks cannot be corrected

Error list: General inputs and outputs

14 Please acknowledge with ENTER

15 Invalid number of places

16 The entry contains invalid characters

17 Value not within the limits

18 Segment incorrectly programmed

19 Password error

Error list: Profibus job processing

20 Busy flag not reset by the master

21 Inadmissible job

22 Error on data acceptance

23 No cyclical data existing

24 Inadmissible structure length

25 Inadmissible header ID

4 Modbus protocol description

Error code Description Error list: Keyboard and program lock

26 Keyboard locked

27 Programming locked

28 Write error in the ser. EEprom (Calib)

29 Hardware error: MANUAL + AUTO locked

30 Edit is inadmissible when the program is active

31 Copy is inadmissible when the program is active

32 MANUAL is inadmissible during AUTO lead time

33 Segment change Image update required

34 No DB number, image update by PLC

35 No DB number for process values of PLC

36 Printer loaded or not operational

37 Set point value 1 was not programmed

38 Configure printer (config./interface)

39 Only possible, when the device is in MANUAL mode

40 Self-optimization already running

41 Tme axis elapsed or not programmed

42 Time axis cannot be copied

43 Time axis not existing

44 Program change is locked

45 MANUAL mode locked

46 Program start locked

Error list: Interface processing

47 Incorrect response length

48 Timeout error (no response)

49 Error reported in telegram protocol

50 Checksum error

51 Parity error

52 Framing error

53 Interface buffer full

54 Address error (e.g. address does not exist)

4 Modbus protocol description

Error code Description

55 Incorrect or unexpected command

Error list: Event processing

60 event could not be created

61 event setting failed

62 event clear failed

63 event wait failed

64 event close failed

65 event open failed

66 Sync error between group and data manager

Error list: message processing

70 Queue memory does not exist

71 Message queue cannot be opened

72 Message pool cannot be generated

73 Memory from message pool cannot be inquired

74 Message cannot be transmitted

Error list: Processing of MQX functions

80 Task creation failed

81 Hardware-Timer not created

Error list: Flash processing

90 Data flash write error

Error list: Other errors

100 Undefined error

101 Division by zero

102 RAM cannot be detected

103 RTC run-time overrun

104 ID does not exist

105 Index too large (overflow)

106 Invalid data

107 Invalid pointer

109 String without 0 characters

110 Timeout during initialization

4 Modbus protocol description

Error code Description

111 Value must not be written to

112 Log entry with error bits initiating debug mode

Error list: Email transfer via modem and Ethernet

120 Step error in the status automatic

121 Invalid response length

122 No CONNECT from the modem

123 FCS checksum incorrect

124 Unexpected value or response

125 Conf-Request not accepted

126 No Conf-Request from the other end

127 No Chap-Request from the other end

128 Response timeout

129 Unknown modem response

130 Unexpected OK by the modem

131 Unexpected CONNECT from the modem

132 Unknown frame received

133 Unexpected PROTOCOL by the modem

134 Unexpected COMPRESS from the modem

135 Invalid PPP package received

136 Unexpected BUSY from the modem

137 Unknown authentification protocol

138 Ignored LCP option

139 Unexpected DELAYED from the modem

140 Unexpected NODIALTONE

141 Unknown PPP protocol

142 Unknown PAP code

143 Ignored IPCP option

144 Ignored IPCP code

145 Unknown CHAP code

146 IP checksum incorrect

147 Unknown IP protocol

4 Modbus protocol description

Error code Description

148 Unknown ICMP type

149 Unknown LCP type

150 As a client DNS request received

151 Unknown DNS error

152 DNS response is divided

153 No IP received via DNS

154 Unknown Udp port

155 TCP checksum incorrect

156 TCP port incorrect

157 Unknown TCP-SYN option

158 Unused TCP port

159 Unknown POP3 response

160 Unknown SMTP response

161 Unknown DNS name

162 No MD5 requested from CHAP

163 Authentification error

164 Cancel from other end

165 Error when creating TCP socket

166 Error when binding TCP socket

167 Error on TCP connect

168 Error when transmitting TCP telegram

169 Error when closing TCP socket

170 Error on TCP listing

171 Reset on TCP accept

172 Error on TCP accept

173 SMTP server indicates syntax error

Error list: File system processing

200 Error when installing the partition manager

201 Error when installing the MFS file system

202 Error when deinstalling the partition manager

203 Error when deinstalling the MFS file system

5.1 Modbus slave

Modem

(Master)

ModemModem

(Master)

Telephone

Modbus

Slave Slave Slave

Slave

If the paperless recorder is configured as a slave, see Chapter 3.4 Configuration of the serial interfaces, Page 12, in the network it responds to Modbus requests of the master. The master controls the data exchange, the slaves only have a response function. They are identified by their device address. The master usually is a PC with a setup or visualization program installed. The master can inquire all instrument variables of the paperless recorder (see Chapter 7 Address tables, Page 47).

5 Serial protocol types

In a Modbus network, only one instrument may be assigned with the master function.

Modem operation

• A paperless recorder in the slave mode can be controlled by the master via a telephone connection using a modem, see above illustration.

• The paperless recorder can initialize a modem (also cyclically, if the modem is switched on after the instrument has been activated).

• The paperless recorder can use the Init string (entry per setup program in the "RS232/RS485: Modem" mask) to configure the modem so that an incoming call is automatically answered. Then a remote inquiry for the paperless recorder can be carried out by the master using Modbus commands or the recorder can send a signal (e.g. an alarm) or an email after the active dial-in.

• The paperless recorder (slave) can use a dial-in/hang-up string to alarm a PC (master) with the suitable Modbus master software (which recognizes incoming modem calls).

• The paperless recorder can use a dial-in/hang-up string to call an internet provider and send an email.

When the modem operation is active, the following parameters (by setup program only) can be edited:

5 Serial protocol types

Modem parameters

The following Init string is required for the operation as a Modbus slave via modem:

AT&FE0X3Q1&K0S0=1&D0&W0&Y0 AT&F = Load the current manufacturer profile

E0 = Switch off character echo X3 = Switch off fixed dial tone selection,

Q1 = Switch off command responses &K0 = Switch off data flow control S0=1 = Automatic pick-up after first ring &D0 = Ignore DTR signal &W0 = Save current configuration as profile 0 &Y0 = Use profile 0 after switch-on

Switch on busy tone selection

Internet dial-in

The dial-in and hang-up string are only required for one of the active modem alarms.

Email parameters

5 Serial protocol types

For the active internet dial-in for alarms by email, the instrument modem must be switched to a different mode using another INIT string.

Telephone number, user name and password must be entered according to the specifications of the selected internet provider. Once the internet dial-in has been completed, the modem is automatically reset to its initial state using the Init string entered under modem parameters.

5 Serial protocol types

Master

Modbus

Slave Slave Slave

5.2 Modbus master

If the paperless recorder is configured as a master, (see Chapter 3.4 Configuration of the serial interfaces, Page 12), it can send Modbus inquiries in the network to slaves (e.g. other paperless recorders). The requested values are written into external instrument variables of the paperless recorder:

• external analog values 1 to 24 in the analog selector

• external binary values 1 to 24 in the binary selector

• external texts 1 to 9 (e.g. to link batch texts in the instrument)

Modbus master

These parameters can be edited in the setpu program and on the paperless recorder.

5 Serial protocol types

Slave

Ascii Barcode Protocol

Barcode Scanner (Master)

For each target variable, it is possible to enter the instrument address and Modbus address used to request the value.

Each programmed inquiry can be deactivated by entering the instrument address 0 (if, for example, the "external analog value 2" is no longer to be written to by the Modbus master but by the Profibus).

Double writing of a target variable will lead to undefined states and must be avoided.

For analog and binary values, the entry of a "Number of measured values" or "Number of bits" larger than 1 allows reading consecutively several variables using one command. The following target variables are automatically assigned during saving.

Timeout defines the maximum time-out time used for each sent command to wait for

response before the next command is carried out.

Inquiry cycle defines the time interval used to read in variables.

5.3 Barcode

In the "Barcode mode" (see Chapter 3.4 Configuration of the serial interfaces, Page 12), the paperless recorder appears as a slave. It waits for the ASCII strings sent by the barcode scanner (master). This interface mode only requires the setting of the "Baud rate" and "Data format" configuration parameters, see Chapter 3.4 Configuration of the serial interfaces, Page 12, further parameters are not required here.

The paperless recorder can use these strings for the incremental control of a batch sequence (see operating manual of the paperless recorder).

5 Serial protocol types

The advantage of the Ethernet connection compared with a serial connection lies in the higher transmission rate the company-wide accessibility.

6.1 HTTP

In this case, the paperless recorder is configured as a slave and handles incoming requests as a server via port 80. These requests can come, for example, from a PC with setup software, PC evaluation software (PCA) or PCA communication software (PCC).

6.2 Browser connection

The paperless recorder can also be accessed by a browser using the HTTP protocol. The URL required for this purpose is the IP address of the paperless recorder.

6 Ethernet protocols

The HTML start page "index.htm" is accessed and can be used to branch to further HTML pages.

The start page "index.htm" and other HTML pages can be loaded into the paperless recorder using the setup program For this purpose, a memory space of 512 kB is available.

The online visualization as well as three HTML pages and three HTML batch pages are factory-saved as templates. In the HTML pages, special tags can be used to access device variables. Support is provided in a help window which can be used to select the device variable in the setup program and copy the corresponding HTML tag into the clipboard.

Edit  Web server  Web import.

6 Ethernet protocols

6.3 Modbus TCP

In this case, the paperless recorder is configured as a slave and handles incoming requests as a server via port 502. The port can also be changed, see Chapter 3.5 Configuration of the Ethernet interface, Page 13.

Modbus TCP is a standardized process, in which a Modbus telegram is packed into a TCP frame (tunnelled) and transmitted via Ethernet. The Modbus telegram (without CRC) is transmitted with an additional "MBAP header" of 6 or 7 byte. The seventh byte is identical to the first serial byte, but has a different designation.

Structure of a Modbus TCP telegram

MBAP header Modbus

2 byte Tran s-

action ID

Identical in

request and

response

2 byte

Protocol ID

Must be 0

for Modbus

2 byte

Length

Length of

question

and

response in

byte

from (incl.)

"Unit ID"

1 byte

Unit ID

Corresponds to

the controller

address. For

TCP must be

0xFF or 0

(0=broadcast)

Further bytes

as specified below,

however, without CRC

For comparison: a Modbus telegram, Page 17:

This protocol can be used, e.g. by a suitable process data visualization program to read and write values of the paperless recorder via a companywide Ethernet network. All device variables from the Modbus address tables (see Chapter 7 Address tables, Page 47) can be accessed.

Only one Modbus master (client) can access a paperless recorder via Modbus TCP at a time.

A connection opened by a client is cancelled by the paperless recorder after 30 seconds of inactivity.

If a Modbus TCP port is closed (by the paperless recorder or the other end), it can be reopened after 10 seconds.

the "normal" Modbus telegram, see Chapter 4.4 Structure of

Slave

address

1 byte

Function

code

1 byte

Data field

x byte

CRC16

2 byte

6 Ethernet protocols

Example: reading n words

00 01 00 00 00 06 FF 03 12 57 00 02

2 bytes

Transaction

Assignment of response to request (consecutive numbering)

For Modbus always 0x00

Reading the measured value from the first analog input (these are the first 2 words starting from Modbus address 0x1257).

See also the Modbus example in Chapter 4.6.2 Read n words, Page 20. Query:

MBAP header Modbus telegram

(without slave address and CRC)

2 bytes

Protocol ID

2 bytes

Length

Length of the request in bytes starting with (incl.) "Unit ID"; 6 bytes here (0x06)

1 byte

Unit ID

With TCP always 0xFF (except for broadcast)

1 byte

Function

code

Function code for "Reading n words"

2 bytes

Address of

first word

First word of analog inputs to be read

2 bytes

Number of

words

2 words should be read

Response:

MBAP header Modbus telegram

(without slave address and CRC)

00 01 00 00 00 07 FF 03 04 19 99 43 48

2 bytes

Transaction

Assignment of response to request (consecutive numbering)

2 bytes

Protocol ID

For Modbus always 0x00

2 bytes

Length

Length of the response in bytes starting with (incl.) "Unit ID"; 7 bytes here (0x07)

1 byte

Unit ID

With TCP always 0xFF (except for broadcast)

1 byte

Function

code

Function code for "Reading n words"

1 byte

Number of

bytes read

4 bytes were read

4 bytes

Data read

Measured value

200.1

6 Ethernet protocols

local subnet

additional subnets

Internet (worldwide)

PC IP=x.x.x.x

Proxy IP=x.x.x.x

SMTP server IP=x.x.x.x Port 25

DHCP server IP=x.x.x.x

DNS server IP=x.x.x.x

POP3 server IP=x.x.x.x Port 110

Setup PC IP=x.x.x.x

Gateway IP=x.x.x.x

Recorder IP=x.x.x.x

6.4 Email (SMTP and POP3)

The paperless recorder can transmit Emails (e.g. alarms). In this case, it is the master (client) and can access SMTP servers at the standard port (25) as well as POP3 servers at the standard port (110)

Typical networking in the company network

Function of the individual stations

Gateway: separates local sub-nets from each other and thus filters the packets. Not all packets are received in every sub-net. Packets from outside the local sub-net must be addressed to the gateway.

DHCP server: can automatically assign IP address, sub-net mask and gateway address to other stations when switching on. These parameters can also be entered manually, then a DHCP server is not required.

DNS server: converts symbolic names to IP addresses, e.g. question: "www.name.de" will generate the "www.name.de has IP=10.12.32.45" response.

POP3 server: serves to read out received Emails of a mail account. The POP3 mail account can be accessed after log-in entering user name and password. A successful log-in process often releases the transmission authorization of a connected SMTP server.

SMTP server: serves to transmit Emails. The authorization to transmit Emails via a mail account must be released in several networks by previously logging in at the corresponding POP3 server.

Proxy: serves as a gateway between the local company network and the worldwide internet. It is also used for the conversion of "local" IP addresses (used in the company network) to "once-only" IP addresses (used in the internet). The device software cannot address a proxy!

6 Ethernet protocols

Parameters for mail server and Email parameters

These parameters can only be edited via the setup program.

Edit  Ethernet Email parameters

A mail server within the company network (not the internet) must be entered here. This mail server should be able to also transmit Emails to the internet.

6 Ethernet protocols

Load own present

IP address

POP3

configured before

SMTP?

Request

DNS server

POP3 server

name from

Conditions

fulfilled for e-mail

transmission?

Make TCP connection

to POP3 server

with user name + password

Close TCP connection without reading e-mail

Request

DNS server

SMTP server name

from

Make TCP connection

to SMTP server

Format and send

e-mail text

Close TCP connection

Enter e-mail OK /

error code in event list

Ye s

Error

Repeat attempts with the

same mail every 15 min.

Ye s

Transmission of an Email via internet

Here, serveral steps depend on configured device parameters. An error code of the event entry (see Chapter 4.9.3 Error codes as integer return values, Page 30 (particularly the error codes 120 to 173)) can suggest an incorrectly set parameter. An incorrectly entered DNS server IP, for example, generates the error code 153 = "no IP received via DNS".

7.1 Data types and type of access

The Chapter 7.2 contain descriptions of all process values (variables) including their addresses, data type and type of access.

Meaning:

R Read only access

W Write access

R/W Read and write access

char xx Character string consisting of ASCII characters (8 bits) with the

length xx; xx = Length including the "\0" character string end character

2 characters are read and written in a word.

word Unsigned Integer 16 bit (1 word)

int Signed Integer 16 bit (1 word)

long Signed Integer 32 bit (2 words)

7 Address tables

float Float value (4 byte = 2 words) as per IEEE 754

bool Bool can be read and written as word,

its value range is 0 … 1

byte Byte (8 bit) can be read and written as word,

its value range is 0 … 255

Bit x Bit No. x (bit 0 is always the bit with the lowest value)

7.2 Modbus addresses of important device and process data

Address Access Data type Signal designation

0x0009 R char 12 Software version 0x0103 R word Status binary inputs/outputs 1...16 0x0104 R word Status binary inputs/outputs 17...24 0x0105 R word Status ext. binary inputs/outputs 1...16

(via PROFIBUS-DP also R/W)

0x0106 R word Status ext. binary inputs/outputs 17...24

(via PROFIBUS-DP also R/W)

Available as of firmware 187.04.xx: Status ext. binary inputs/outputs 17...32 (via PROFIBUS-DP also R/W)

See also address: 0x0128 and 0x0129 0x0107 R word Status Relay 1…7 0x0108 R word Math bool 1…16 0x0109 R word Math bool 17…18

0x010A R word Logic result 1…16

7 Address tables

0x010B R word Logic result 17…18 0x010C R word Limit value monitoring Status 1...9 0x010D R word Analog alarms 1 channel 1...16

0x010E R word Analog alarms 1 channel 17...18 0x010F R word Analog alarms 2 channel 1...16 0x0110 R word Analog alarms 2 channel 17...18 0x0111 R word External analog alarms 1 channel 1...16 0x0112 R word External analog alarms 1 channel 17...18

0x0113 R word External analog alarms 2 channel 1...16 0x0114 R word External analog alarms 2 channel 17...18

0x0115 R word Binary inputs/outputs alarm 1...16 0x0116 R word Binary inputs/outputs alarm 17...24 0x0117 R word External binary inputs alarm 1...16 0x0118 R word External binary inputs alarm 17...24

Available as of firmware 187.04.xx:

External analog alarms 1 channel 17...32

8 Index

ElectroStatic Discharge (ESD) 5 Email 35, 37, 44, 46 Email transfer via modem and Ethernet 33 Error 28 Ethernet 10, 13–14

Float values 24 Function overview 18

HTTP 41

Integer values 24 Interface type 12

Min. response time 12, 17 Modbus 15 Modbus broadcast address 18 Modbus double format 25

8 Index

Modbus error codes 28 Modbus float format 24 Modbus master 12 Modbus slave 12 Modbus TCP 42 Modbus telegram 17 Modem operation 35

Overrange 29

Parity bit 15 Plug assignment 11 POP3 44 Protocol 12

Read command 19–20 Relay outputs 27 Returning 5 RS232 10–11 RS485 10–11 RTU 12, 15

SMTP 34, 44 Stop bit 15 System prerequisites 7

Telegram 42 Timing scheme 16 Troubleshooting 28

Underrange 29

Write command 21–23

JUMO GmbH & Co. KG JUMO Instrument Co. Ltd. JUMO Process Control, Inc.

Street address: Moritz-Juchheim-Straße 1 36039 Fulda, Germany Delivery address: Mackenrodtstraße 14 36039 Fulda, Germany Postal address: 36035 Fulda, Germany Phone: +49 661 6003-0 Fax: +49 661 6003-607 Email: mail@jumo.net Internet: www.jumo.net

JUMO House Temple Bank, Riverway Harlow, Essex CM 20 2DY, UK Phone: +44 1279 63 55 33 Fax: +44 1279 62 50 29 Email: sales@jumo.co.uk Internet: www.jumo.co.uk

6733 Myers Road East Syracuse, NY 13057, USA Phone: +1 315 437 5866 Fax: +1 315 437 5860 Email: info.us@jumo.net Internet: www.jumousa.com

JUMO LOGOSCREEN nt Interface Description

Specifications and Main Features

Frequently Asked Questions

User Manual

1.1 Preface

1 Introduction

1.2 Typographical conventions

1.2.1 Warning signs

1.2.2 Note symbols

1.2.3 Number types

2 General information

2.1 Target group

2.2 Interfaces

2.3 System prerequisites

3.1 Connection position

3 Connecting the interface

3.2 RS232

3.3 Toggling between RS232 and RS485

3.4 Configuration of the serial interfaces

3.5 Configuration of the Ethernet interface

3.5.1 Parameters

4.1 Master-Slave principle

4 Modbus protocol description

4.2 Transmission mode (RTU)

4.3 Timing of the communication

4.4 Structure of a Modbus telegram

4.5 Device address

4.6 Function codes

4.6.1 Read n bit

4.6.2 Read n words

4.6.3 Write one bit

4.6.4 Write one word

4.6.5 Write n words

4.7 Transmission format (integer, float, double and text values)

4.8 Checksum (CRC16)

4.9 Error messages

4.9.1 Modbus error codes

4.9.2 Error messages for invalid values

4.9.3 Error codes as integer return values

5.1 Modbus slave

5 Serial protocol types

5.2 Modbus master

5.3 Barcode

6.1 HTTP

6.2 Browser connection

6 Ethernet protocols

6.3 Modbus TCP

6.4 Email (SMTP and POP3)

7.1 Data types and type of access

7 Address tables

7.2 Modbus addresses of important device and process data

8 Index