
MULTICAL® 302
Kamstrup A/S · Technical Description · 5512-1334_F1_GB_12.2016
67
13
Data communication
13.1
MULTICAL
302 Data Protocol
Internal data communication in MULTICAL
302 is based on the Kamstrup Meter Protocol (KMP) which provides a fast
and flexible reading structure and also fulfils future requirements to data reliability.
The KMP protocol is used in all Kamstrup consumption meters launched from 2006 onwards. The protocol is used for
the optical eye.
The KMP protocol has been designed to handle point to point communication in a master/slave system (e.g. a bus
system) and is used for data reading of Kamstrup energy meters.
Software and parameter protection
The meter’s software is implemented in a Flash and cannot be changed, neither deliberately nor by mistake.
Legal parameters cannot be changed via data communication.
Software conformity
Software check sum, based on CRC16, is available via data communication and in the display.
Integrity and authenticity of data
All data parameters include type, measuring unit, scaling factor and CRC16 check sum.
Every produced meter includes a unique identification number.
Two different formats are used for communication between master and slave. Either a data frame format or an
application acknowledgement.
•
A request from master to slave is always sent in a data frame
•
The response from the slave can either be sent in a data frame or as an application acknowledgement
The data frame is based on the OSI model using the physical layer, the data link layer and the application layer.
Bytes in each field
1
1
1
0-?
2
1
Field designation
Start byte Destination
address
CID
Data
CRC
Stop byte
OSI – layer
Application layer
Data link layer
Physical layer
The protocol is based on half duplex serial asynchronous communication with the setup: 8 data bits, no parity and 2
stop bits. The data bit rate is 1200 or 2400 baud. CRC16 is used in both request and response.
Data is transferred byte for byte in a binary data format, in which the 8 data bits represent one byte of data.
Byte Stuffing is used to extend the value range.