10.07.2015 Views

Proline Promass 83E/F/O Modbus RS485 Operating Instructions

Proline Promass 83E/F/O Modbus RS485 Operating Instructions

Proline Promass 83E/F/O Modbus RS485 Operating Instructions

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Proline</strong> <strong>Promass</strong> 83 <strong>Modbus</strong> <strong>RS485</strong>OperationData typesThe following data types are supported by the measuring device:• FLOAT (floating-point numbers IEEE 754)Data length = 4 bytes (2 registers)Byte 3 Byte 2 Byte 1 Byte 0SEEEEEEE EMMMMMMM MMMMMMMM MMMMMMMMS = signE = exponentM = mantissa• INTEGERData length = 2 bytes (1 register)Byte 1 Byte 0Most significant byte(MSB)Least significant byte(LSB)• STRINGData length = depends on device parameter,e.g. illustration of a device parameter with a data length = 18 bytes (9 registers):Byte 17 Byte 16 … Byte 1 Byte 0Most significant byte(MSB)…Least significant byte(LSB)Byte transmission sequenceByte addressing, i.e. the transmission sequence of the bytes, is not specified in the <strong>Modbus</strong>specification. For this reason, it is important to coordinate the addressing method between themaster and slave during commissioning. This can be configured in the measuring device by meansof the "BYTE SEQUENCE" parameter (see "Description of Device Functions" manual).The bytes are transmitted depending on the option selected in the "BYTE SEQUENCE" parameter:FLOAT:SequenceSelection1st 2nd 3rd 4th1 – 0 – 3 – 2* Byte 1(MMMMMMMM)Byte 0(MMMMMMMM)Byte 3(SEEEEEEE)Byte 2(EMMMMMMM)0 – 1 – 2 – 3 Byte 0(MMMMMMMM)Byte 1(MMMMMMMM)Byte 2(EMMMMMMM)Byte 3(SEEEEEEE)2 – 3 – 0 – 1 Byte 2(EMMMMMMM)Byte 3(SEEEEEEE)Byte 0(MMMMMMM)Byte 1(MMMMMMM)3 – 2 – 1 – 0 Byte 3(SEEEEEEE)Byte 2(EMMMMMMM)Byte 1(MMMMMMMM)Byte 0(MMMMMMMM)* = Factory settingS = signE = exponentM = mantissaIssue/Rev. 0.2 (12/12) MN0M030 • Page 47

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!