Protocol VIT5. Communications RS485. Version 1.0. Pg.Up ENTER. Pg.Up ENTER. Pg.Up ENTER. Pg.Up ENTER. Pg.Up ENTER. Pg.Up ENTER. Pg.Up ENTER. Pg.

Similar documents
Conto D2 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION

IF96017 MODBUS COMMUNICATION PROTOCOL

Conto D1 MODBUS COMMUNICATION PROTOCOL

CE4DMID01 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION

COMMUNICATION MODBUS PROTOCOL

COMMUNICATION MODBUS PROTOCOL

COMMUNICATION MODBUS PROTOCOL

CONTO IMP PROTOCOL COMMUNICATION CONTENTS 1.0 INTRODUCTION

COMMUNICATION MODBUS PROTOCOL

COMMUNICATION MODBUS PROTOCOL MF96001 / 021 NEMO 96HD

Sommario. COMMUNICATION PROTOCOL PR 150 Rev. A 31/01/2018 Pag 1 Multifunction Firmware NEMO 96 EA ModBus

JUMO ctron 04/08/16. Compact controller with timer and ramp function. B Interface Description Modbus /

JUMO Quantrol LC100/LC200/LC300

Modbus Protocol For FTS/FTM 3x&8x

DataVU 5 - Interface Manual Modbus

DataVU 5 - Interface Manual Modbus

Type Type Type Type Type B Interface Description /

B Interface description 12.01/

DMTME Multimeters. Communication protocol. Technical specification V1.2 ABB

Precision Digital Modbus Register Tables Serial Communication

TR600 with RS485 Appendix 1

CTT MODBUS-RTU COMMUNICATION PROTOCOL TEMPERATURE MONITOR DEVICE

GNM3D Series COMMUNICATION PROTOCOL. Version 1 Revision 0

SC2004MBS 20x4 Characters MODBUS RTU Slave LCD

Interface design document MODBUS Protocol. Ab s t r a c t Description of the MODBUS implementation for the Modbus I/O board

Rev 1.3, Air-Farm User Manual. CO2 / Temperature / Humidity Transmitter

TECH TIP. Tritex Modbus Protocol Specification

M2M/DMTME Instruments Communication protocol. Technical specification V.2.1 2CSG445011D0201

Optris CT/ CTlaser/ CTvideo communication interface

EM23-DIN COMMUNICATION PROTOCOL. Version 0 Revision 0

EM100 Series and ET100 Series

JUMO di 308. Digital Indicator. B Interface Description Modbus 12.07/

MODBUS Protocol. The ecode Encoders contain both single register (16 bit) and double register (32 bit) values.

R1M-GH THERMOCOUPLE & DC INPUT MODULE MODEL. Remote I/O R1M Series. (16 points)

TORRIX RS485. Technical Documentation. with MODBUS Protocol. Edition: Version: 3 Art. no.:

EM21 COMMUNICATION PROTOCOL. Version 1 Revision 0

Version Action Author Date

EM271 COMMUNICATION PROTOCOL. Version 0 Revision 0

Definition of PLR on the RS485-bus. Version 1.06

JUMO dtron 304/308/316 JUMO dtron 304/308/316 plast

EM270 COMMUNICATION PROTOCOL. Version 1 Revision 0

GE MDS, LLC. NETio Series. Protocol Communications Supplement. March 2013 Part No A01, Rev. C

Deutschmann Module Unigate. CL-Profibus DP. Modbus - Profibus DP Programmer s Manual

Type 70906X. Thyristor power units TYA 201, 202 and 203. Interface description for Types ,-62, and T92Z001K000. Typ /

DTU sensor data formats.

REVO CL Serial Communication Manual

QEL - DEDESCO 5935 Ottawa Street Richmond, Ontario, Canada, K0A 2Z0.

CAN / RS485. Product Description. Technical Reference Note. Interface Adapter. Special Features

EM300 Series. ET300 Series

MODBUS APPLICATION PROTOCOL SPECIFICATION V1.1b3 CONTENTS

SOFTWARE FUNCTIONAL REQUIREMENTS SPECIFICATION. Athena DeviceNet Interface Module Revision /26/2001

MODBUS APPLICATION PROTOCOL SPECIFICATION V1.1a CONTENTS

OPTRIS CT communication interface

EM210 COMMUNICATION PROTOCOL. Version 3 Revision 1

2. Terminal arrangement TEMPERATURE CONTROLLER KT2 COMMUNICATION INSTRUCTION MANUAL. (Fig. 2-1)

Deutschmann Module Unigate. CL-Profibus DP. Modbus - Profibus DP Programmer s Manual

I/O Module. Modbus Manual DMB Series.

Using the MODBUS Protocol with Athena Series C (1ZC, 16C, 18C, and 25C) Controllers

User Manual version 1.04 TLM8 COMMUNICATION PROTOCOLS

EM24-DIN PFA, PFB & X models

VERIS H8035 and H8036

Golander Peristaltic Pump MODBUS Communication Instruction

SPI Lasers UK Limited. Serial Command Reference for the PRISM Laser Platform

VISY-Command. Technical Documentation. with Modbus Protocol. Edition: Version: 1 Art. no.:

For more information Contact with details of the application.

EM210 COMMUNICATION PROTOCOL. Version 3 Revision 3

EM24-DIN COMMUNICATION PROTOCOL. Version 3 Revision 1

MODBUS APPLICATION PROTOCOL SPECIFICATION V1.1b3 CONTENTS

The RS-485 user manual for B800 series communication

Modbus Protocol For TGP03 / THP03

OPTRIS CT/CTL communication interface

SPM90 MODBUS PROTOCOL AND REGISTER LIST V1.0

Manual 09/11 MN Z-EN. NZM-XATS-C Automatic Transfer Switch-Controller Modbus Communication Protocol

JDICON 1000 JDICON B Interface Description 3.99/ Universal Process Controller. Universal Profile Controller

JUMO ecoline O-DO/NTU

Sample F4T 32-bit Modbus RTU Packet

I 2 C Application Note in Protocol B

Appendix) Specifications of Monitor & Control Rev. 4.0 July 13, 2016

INTELLIS. Modbus Direct Network Monitor

Sample F4T 32-bit Modbus RTU Packet

ENGLISH ENGLISH ENGLISH ENGLISH

Data Communication Protocol Host Computer to FAS-A

EMDX3 Multifunction meter Cat No ModbusTable LGR EN v1.01.xls

Input Channels: 4 differential or four single-ended. Address / Baud rate / range configurable by the user

Modbus ASCII Serial Device Driver Help 2009 Kepware Technologies

ENGLISH ENGLISH ENGLISH ENGLISH

T7 Modbus Communication User Guide

VPGate Manual PROFIBUS to serial

EM24-DIN COMMUNICATION PROTOCOL. Version 3 Revision 0

Communication Protocol Manual JOFRA ATC Copyright 2007 AMETEK Denmark A/S

4511 MODBUS RTU. Configuration Manual. Universal transmitter. No. 4114MCM100(1402)

Tongta Inverter TDS-F8

Modbus RTU/TCP Installation and Programming Guide PC3400 Particle Counter

Modbus on SenseAir S8

CD3000E-REVO E Serial Communication Manual

4511 MODBUS RTU. Configuration Manual. Universal transmitter. No. 4116MCM101(1445) For 4511 devices from ser. no:

4511 MODBUS RTU. Configuration Manual. Universal trip amplifier. No. 4131MCM100(1402)

S u p p l e m e n t TQS3 MODBUS. Description of product modification with MODBUS RTU. 31. March 2008 w w w. p a p o u c h.

SPM33. MODBUS Protocol and register List V1.5

IQ Home Modbus-RTU Master

Transcription:

4.6.5. 0. 0. V 0. I. 2.0. 0. C 0. I. 2.0. 0. C 0. I. 2.0. 0. C 4.6.5. 0. 0. V 4.6.5. 0. 0. V 0. I. 2.0. 0. C 4.6.5. 0. 0. V 4.6.5. 0. 0. V VIT5 0. I. 2.0. 0. C Version 1.0 RS485 4.6.5. 0. 0. V Communications Protocol

INDEX ISTRUMENTI MISURE ELETTRICHE SpA Via Travaglia 7 20094 CORSICO (MI) ITALY Phone 02 44 878.1 Fax 02 45 03 448 +39 02 45 86 76 63 E-mail imebox@tin.it 1 INTRODUCTION page 3 2. PACKAGE DESCRIPTION page 4 2.1 Parameters description 2.2 Data format 2.3 CRC computation description 2.4 Error handling 3. COMMANDS page 7 3.1 0x03 code 3.2 Used addresses and data meaning 3.3 Group 1 3.4 Group 2 3.5 Group 3 3.6 Group 4 3.7 Group 5 4. TIG DIAGRAM page 17 I.M.E. S.p.A. reserves the right to modify the technical characteristics without notice.

1. INTRODUCTION The used communications protocol is MODBUS / JBUS compatible. Message physical transmission parameters are: Baud rate : configurable 9600, 4800, 2400, 1200 Bit count : 8 Bit Stop : 1 Parity : none 3

2. PACKAGE DESCRIPTION The generic data package is composed in this way : Device number Functional code Data Control CRC There are two possible answers : Answer with data Device number Functional code Data Control CRC Answer by mistake Device number Functional code + 0x80 Mistake code Control CRC 2.1 Parameters description Device number: Network device identification number It must be the same for Control and Answer. Format : 1 byte from 0 to 0xff 0 shows a message for all the devices (broadcast) and does not require an answer. Functional Code: they are the control codes The used functional codes are: Format : 1 byte 0x03: reading from device 4

Data: They are: required WORDS addresses the answer data Control CRC: It is a WORD resulting from a calculation carried out on all the byte making up the package. 2.2 Data format The generic datum base unit is BYTE. The addresses are expressed on a WORD (2 BYTES) and they are always positive. The data are expressed on BYTE, WORD and long (two WORDS). In the event that required data item is a BYTE-type data item, it is anyway transmitted a WORD with MSB (Most Significant Byte) at 0 or anyway at a negligible value. The 2-WORD data are transmitted with the most significant WORD preceding the less significant WORD. Therefore, all the data are transmitted with an even number of bytes. The data with sign follow the conventions for the numbers with sign as twos complement (this is valid for WORD or for long). Example: 1000 = 0x 03 e8 or 0x 00 00 03 e8 (if long) -1000 = 0x f c 18 or 0x f f f f f c 18 (if long) 5

2.3 CRC computation description In the following example, you can find a procedure written in "C" computation of CRC. unsigned int calc_crc (char *ptbuf,unsigned int num) /* **************************************************************** * Description : it computes the CRC of a data buffer * Input : ptbuf = first byte buffer pointer * num = number of byte on which CRC must be computed * Output : // * Return : ** ***************************************************************/ { unsigned int crc16; unsigned int temp; unsigned char c, flag; crc16 = 0xffff; /* it initializes the CRC */ for (num; num>0; num--) { temp = (unsigned int) *ptbuf; /* it loads the byte in temp */ temp &= 0x00ff; /* it masks the MSB */ crc16 = crc16 ^ temp; /* crc16 in OR only with temp */ for (c=0; c<8; c++) { flag = crc16 & 0x01; /* it filters only the LSBit of crc16 */ crc16 = crc16 >> 1; /* it loses the Lsbit of crc16 */ if (flag!= 0) crc16 = crc16 ^ 0x0a001; /* crc16 in XOR with 0x0a001 */ } ptbuf++; /* it points at next byte */ } crc16 = (crc16 >> 8) (crc16 << 8); /* it interchanges LBS with MSB */ return (crc16); } /* calc_crc */ 2.4 Error handling If received message is invalid (CRC16 does not coincide), the queried device (slave) does not answer. If the message is right but it contains some irregularities (in the functional Code or in the Data) so that it cannot be acnowledged, the device answers with an error message. The error codes are defined afterwards. 6

3. COMMANDS 3.1 0x03 Code: reading of one or more consecutive WORDS Command format: MSB LSB MSB LSB MSB LSB Device number Code 1.st WORD address WORDS number CRC16 Answer format: MSB LSB MSB LSB Device number Code Number of BYTES WORDS 1... CRC16 The number of BYTES must be always equal to the number of WORDS (in the command) * 2 Answer - error format : MSB LSB Device number Code + 0x80 Error code CRC16 Error code: * 0x01 non-recognized functional code * 0x02 Wrong first WORD address * 0x03 Wrong data Example Request of 4 WORDS (8 BYTES) starting from address 0x301: MSB LSB MSB LSB MSB LSB Number of device Code 1 WORD address WORDS number CRC16 0x01 0x03 0x03 0x01 0x00 0x04 0x15 0x8d 7

In this case two variables have been required: one at 0x301 address and another at 0x302 address, as more clearly explained afterwards. Answer Variable in 0x301 : 0x00 00 d8 85 0x302 : 0x00 01 86 9f MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB N. BYTES WORD 1 WORD 2 WORD 3 WORD 4 CRC16 0x01 0x03 0x08 0x00 0x00 0xd8 0x85 0x00 0x01 0x86 0x9f 0x68 0xd9 8

3.2 Used addresses and date meaning Data can be required one by one for each address or grouped together. The grouping is made by logical sections or type of data. It is possible to require one or more data of the same group specifying the initial address as well as the required number of words. The BYTE-type data are transmitted to WORD with MSB at 0 or anyway at a negligible value. The highest number of WORDS which can be required is 8 or 16 BYTES. Group 1 : measurements (all the long-type data) Group 2 : meter identification + setup parameters (all the BYTE-type data) Group 3 : identification data for compatibility with communication protocol for already-existing meters Group 4 : setup parameters (all the long-type data) Group 5 : setup parameters (all the long-type data) In the following table you can find the possible addresses with the meaning of the variables these addresses are referred to. Address Description Type Group1 0x301 present measurement Long 0x302 highest measurement peak value Long 0x303 lowest measurement peak value Long 0x304 emperature value (if measurable) Long Group 2 0x300 device identification Byte 0x400 state of the meter Byte 0x401 measurement code Byte 0x402 type of thermocouple Byte 0x403 type of resistive sensor Byte 0x404 decimal point position Byte 0x405 type of alarm 1 Byte 0x406 type of alarm 2 Byte 0x407 input signals polarity Byte 9

Address Description Type Group 3 0x 0f not used 0x10 not used 0x11 not used 0x12 software version Byte 0x13 not used 0x14 not used 0x15 device identification Byte 0x16 not used Group 4 0x430 display full scale Long 0x431 display scale beginning Long 0x432 analog output full scale Long 0x433 analog output scale beginning Long Group 5 0x440 alarm 1 set point Long 0x441 alarm 2 set point Long 0x442 alarm 1 hysteresis Long 0x443 alarm 2 hysteresis Long 10

3.3 Group 1 Group 1 contains the measurements. According to the VIT-5 model, the measurements can be voltage/current (linearized with full scale values in the setup) or temperature. The rendered measurements are exactly the ones displayed. If, for instance, the present measurement is 63470 with the decimal point in third posi tion from the left (634.70), the rendered value is 63470 in long form. If we actually have a temperature measurement, for instance 0123.4 (the point is fixed in fourth position), the rendered value is 1234 in LONG form. The degrees are always expressed in tenths. 0x301 : current measurement 0x302 : highest acquired measurement 0x303 : lowest acquired measurement 0x304 : meter inner temperature measurement expressed in tenths of degrees Note : the temperature can be measured in the following cases meter in temperature with thermocouple meter in voltage with 60mV or 200mV full scale meter in current Example Request of 4 WORDS (8 BYTES) starting from address 0x303 : MSB LSB MSB LSB MSB LSB Device number Code 1.st WORD address WORDS number CRC16 0x01 0x03 0x03 0x03 0x00 0x04 0xb4 0x4d 11

In this case two variables have been required : one at 0x303 address and another at 0x304 address, both of them with2 WORDS. Answer Variable in 0x303 : 0x00 00 d8 85 0x304 : 0x00 01 86 9f MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB N. BYTES WORD 1 WORD 2 WORD 3 WORD 4 CRC16 0x01 0x03 0x08 0x00 0x00 0xd8 0x85 0x00 0x01 0x86 0x9f 0x39 0x19 3.4 Group 2 Group 2 contains the BYTE-type setup parameters. Each parameter is transferred using a WORD with MSB at 0 or at a negligible value. 0x300 : device identification 0x90 : meter configurated in voltage 0x91 : meter configurated in current 0x92 : meter in temperature with thermocouple 0x93 : meter in temperature with PT100/NI100 0x400 : state of the meter bit 1 = 1 - alarm 1 on bit 5 = 1 - alarm 2 on bit 6 = 1 - overrange measurement 0 - measurement within the limits 12

0x401 : measurement code 0 = 200V 1 = 20V 2 = 2V 3 = 200mV 4 = 60mV 5 = 200mA 6 = 20mA 7 = 4-20mA 8 = thermocouple 9 = PT100/NI100 0x402 : type of thermocouple 0 = J 1 = K 2 = T 3 = R 4 = S 0x403 : type of resistive sensor 0 = PT100 1 = NI100 0x404 : decimal point position useful to reconstruct the measurement in a correct way. The position is expressed by a number showing the digit after which the decimal point is placed. Values : 0.. 4 Value 0 shows the point position after the digit 1 starting from the left. The digits are numbered 1...5 Example: 3 means the point is after the 4 TH digit (1387.4) 0x405 : type of alarm 1 0 = di min. 1 = di max. 0x406 : type of alarm 2 0 = di min. 1 = di max. 13

0x407 : input signals polarity 0 = unidirectional 1 = bidirectional Example Request of 4 WORDS (8 BYTES) starting from address 0x401 : MSB LSB MSB LSB MSB LSB Device number Code 1.st WORD address WORDS number CRC16 0x01 0x03 0x04 0x01 0x00 0x04 0x14 0xf9 In this case 4 variables have been required : at address 0x401, 0x402, 0x403, 0x404 each of 1 BYTE Answer Variable in 0x401 : 0x00 08 0x402 : 0x00 01 0x403 : 0x00 00 0x404 : 0x00 03 MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB N. BYTES WORD 1 WORD 2 WORD 3 WORD 4 CRC16 0x01 0x03 0x08 0x00 0x08 0x00 0x01 0x00 0x00 0x00 0x03 0x61 0xd6 The variables are expressed on 1 BYTE with MSB, in this case null. The received values mean : Temperature - thermocouple measurement K-type thermocouple Third value is negligibe Fourth value shows that the decimal point is placed after the digit 4 14

3.5 Group 3 Group 3 contains some identifying data to keep the compatibility with other meters. 0x0f : not used (= 0) Format : 1 BYTE 0x10 : not used (= 0) Format : 1 BYTE 0x11 : not used (= 0) Format : 1 BYTE 0x12 : software version Format : 1 BYTE It is a binary number that identifies the software version * 10. Example : V3.2 is coded as 32 binary. 0x13 : not used (= 0) Format : 1 BYTE 0x14 : not used (= 0) Format : 1 BYTE 0x15 : meter identification Format : as address 0x300 0x16 : not used (= 0) Format : 1 BYTE 15

3.6 Group 4 Group 4 contains the full scale values loaded in the display and analog output setup. The format is the same described in group 1. 0x430 : display full scale 0x431 : display beginning of scale 0x432 : analog output full scale 0x433 : analog output beginning of scale 3.7 Group 5 Group 5 contains the set points and the hysteresis for each alarm. The format is the same described in group 1. 0x440 : set point for alarm 1 0x441 : set point for alarm 2 0x442 : hysteresis for alarm 1 0x443 : hysteresis for alarm 2 16

4.0 TIG DIAGRAM REQUEST MESSAGE NEXT REQUEST MESSAGGE MASTER BYTE1 BYTE2 BYTE n T1 RESPONSE MESSAGE SLAVE BYTE1 BYTE2 BYTE n T2 T3 Where: TIME DESCRIPTION Min & Max VALUES Timeout between characters. T1 If thistime exceedthe max. time allowed, Max = 20ms. the message is not considered by VIT5. SLAVE response time. Min = 25ms. T2 Min and Max time in which VIT5 Max = 300ms. replies to the MASTER request. T3 Time for a new message request Min = 20ms. from the MASTER. 17