This sample shows a full data package, including start and stop bits. Please check the data breakdown for a more detailed description of each OBIS code value.
A good portion of raw sample data is also available in raw-raw-20170915.txt
[2017-09-12 23.18.43.731 - Received 41 (0x29) bytes]
7E A0 27 01 02 01 10 5A 87 E6 E7 00 0F 40 00 00 00 09 0C 07 E1 09 0C 02 17 12 2A FF 80 00 00 02 01 06 00 00 05 28 B8 0C 7E
| Data | Explaination |
|---|---|
| 7E | Frame Start flag |
| A | 4 bits, A = Frame Format Type 3 (0b1010) |
| 0 27 | 11 bits, Frame size: 0x27 (39 bytes, excluding start/end flags) |
| 01 | Destination Address (Address can be 1-4 bytes. Terminated by LSB=1) |
| 02 01 | Source Address (Address can be 1-4 bytes. Terminated by LSB=1) |
| 10 | Control Field |
| 5A 87 | Header check sequence (HCS) (Check sum calculated from the address bytes, according to RFC 1662) |
| Begin Data | LLC PDU Format (GB, 8.3 Fig 19) |
| E6 | Destination LSAP |
| E7 | Source LSAP |
| 00 | LLC Quality |
| 0F | Information, n*8 bits? |
| 40 00 00 00 | (UNCERTAIN) |
| 09 | ??String?? Kamstrup removed this, will it also disappear from Kaifa? |
| 0C | 12 bytes (length of the string) |
| 07 E1 | 2017 (year) |
| 09 | 09 (sep) |
| 0C | 12 (date) |
| 02 | tuesday |
| 17 | 23 (hour) |
| 12 | 18 (min) |
| 2A | 42 (sec) |
| FF | (fff not specified) |
| 80 | (deviation not specified?) |
| 00 00 | (clock_status?) This is the 12th (0x0C) byte of the string |
| 02 01 | (UNKNOWN) could this be another value, identified by 0x02? |
| 06 | Integer following: 1320 Watt |
| 00 | Byte 1 (MSB) |
| 00 | Byte 2 |
| 05 | Byte 3 |
| 28 | Byte 4 (LSB) |
| End Data | |
| B8 0C | Frame check sequence (FCS) (Check sum calculated from full frame, excluding flags and FCS, according to RFC 1662) |
| 7E | Frame End flag |