github.com/UtilitechAS.amsreader-firmware
1
0
Fork 0
mirror of https://github.com/UtilitechAS/amsreader-firmware.git synced 2026-01-26 04:11:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge DIYglenn

Browse Source
This commit is contained in:
Gunnar Skjold
2019-02-14 07:48:46 +01:00
parent a954b838f3
commit 3cb433b27e
273 changed files with 84 additions and 11488 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8997
Debugging/Samples/Kamstrup/HAN 20171019 xibriz4.txt Normal file
View File

File diff suppressed because it is too large Load Diff

40
Debugging/Samples/Kamstrup/obisdata.md Normal file
View File

@@ -0,0 +1,40 @@
# One sample of each list on the Kamstrup ??? meter
For the data parts, I have found they follow a pattern where the first byte dictates the data type and size:
02 - one byte following
06 - long (4 bytes / 32 bits)
12 - int (2 bytes / 16 bit)
09 - string, first byte is length (could it be a byte array?)
0A - string, first byte is length
## List #1 (0x19)
No | Data | Explaination | Value
-- | ---- | ------------ | -----
x | E6 E7 00 0F 00 00 00 00 | Uknown |
0 | 09 0C 07 E1 0A 14 05 03 2B 1E FF 80 00 00 | Date and time | 2017-10-20 (fre) 03:43:30
1 | 02 19 | List ID | 25 (List 1)
2 | 0A 0E 4B 61 6D 73 74 72 75 70 5F 56 30 30 30 31 | OBIS List Version Identifier | Kamstrup_V0001
3 | 09 06 01 01 00 00 05 FF | OBIS for Meter ID | 1.1.0.0.5.255
4 | 0A 10 35 37 30 36 35 36 37 32 37 34 33 38 39 37 30 32 | Meter ID | 5706567274389702
5 | 09 06 01 01 60 01 01 FF | OBIS for Meter Type | 1.1.96.1.1.255
6 | 0A 12 36 38 34 31 31 32 31 42 4E 32 34 33 31 30 31 30 34 30 | Meter Type | 6841121BN243101040
7 | 09 06 01 01 01 07 00 FF | OBIS for Active Power + | 1.1.1.7.0.255
8 | 06 00 00 05 BC | Active Power + | 1468 W
9 | 09 06 01 01 02 07 00 FF | OBIS for Active Power - | 1.1.2.7.0.255
10 | 06 00 00 00 00 | Active Power - | 0 W
11 | 09 06 01 01 03 07 00 FF | OBIS for Reactive Power + | 1.1.3.7.0.255
12 | 06 00 00 00 00 | Reactive Power + | 0W
13 | 09 06 01 01 04 07 00 FF | OBIS for Reactive Power - | 1.1.4.7.0.255
14 | 06 00 00 01 CE | Reactive Power - | 462W
15 | 09 06 01 01 1F 07 00 FF | OBIS for L1 Current | 1.1.31.7.0.255
16 | 06 00 00 02 34 | L1 Current | 5.64 A
17 | 09 06 01 01 33 07 00 FF | OBIS for L2 Current | 1.1.51.7.0.255
18 | 06 00 00 00 CA | L2 Current | 2.02 A
19 | 09 06 01 01 47 07 00 FF | OBIS for L3 Current | 1.1.71.7.0.255
20 | 06 00 00 01 FF | L3 Current | 5.11 A
21 | 09 06 01 01 20 07 00 FF | OBIS for L1 Voltage | 1.1.32.7.0.255
22 | 12 00 E8 | L1 Voltage | 232 V
23 | 09 06 01 01 34 07 00 FF | OBIS for L2 Voltage | 1.1.52.7.0.255
24 | 12 00 E4 | L1 Voltage | 228 V
25 | 09 06 01 01 48 07 00 FF | OBIS for L3 Voltage | 1.1.72.7.0.255
26 | 12 00 E9 | L1 Voltage | 233 V

51
Debugging/Samples/Kamstrup/readme.md Normal file
View File

@@ -0,0 +1,51 @@
> NOTE: There has been a change in the Kamstrup firmware which removes the 09 preceeding the first timestamp. See the ~~strikthrough~~ in the table below
## Sample for Kamstrup
This sample shows a full data package, including start and stop bits.
Please check the [data breakdown](./obisdata.md) for a more detailed description of each OBIS code value.
A good portion of raw sample data is also available in [HAN 20171019 xibriz4.txt](./HAN%2020171019%20xibriz4.txt)
### SAMPLE Data:
> **[2017-10-20 04.43.32.368 - Received 229 (0xE5) bytes]**
> 7E A0 E3 2B 21 13 98 86 E6 E7 00 0F 00 00 00 00 09 0C 07 E1 0A 14 05 03 2B 1E FF 80 00 00 02 19 0A 0E 4B 61 6D 73 74 72 75 70 5F 56 30 30 30 31 09 06 01 01 00 00 05 FF 0A 10 35 37 30 36 35 36 37 32 37 34 33 38 39 37 30 32 09 06 01 01 60 01 01 FF 0A 12 36 38 34 31 31 32 31 42 4E 32 34 33 31 30 31 30 34 30 09 06 01 01 01 07 00 FF 06 00 00 05 BC 09 06 01 01 02
> 07 00 FF 06 00 00 00 00 09 06 01 01 03 07 00 FF 06 00 00 00 00 09 06 01
> 01 04 07 00 FF 06 00 00 01 CE 09 06 01 01 1F 07 00 FF 06 00 00 02 34 09
> 06 01 01 33 07 00 FF 06 00 00 00 CA 09 06 01 01 47 07 00 FF 06 00 00 01
> FF 09 06 01 01 20 07 00 FF 12 00 E8 09 06 01 01 34 07 00 FF 12 00 E4 09
> 06 01 01 48 07 00 FF 12 00 E9 A1 A5 7E
### Breakdown:
Data | Explaination
--------|-------------
7E | Frame Start flag
A | 4 bits, A = Frame Format Type 3 (0b1010)
0 E3 | 12 bits, Frame size: 0xE3 (227 bytes, excluding start/end flags)
2B | Destination Address (Address can be 1-4 bytes. Terminated by LSB=1)
21 | Source Address (Address can be 1-4 bytes. Terminated by LSB=1)
13 | Control Field
98 86 | 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?
00 00 00 00 | INVOKE_ID_AND_PRIORITY
~~09~~ | ~~String following (really, it's a date!)~~
0C | 12 bytes (length of the string)
07 E1 | 2017 (year)
0A | 10 (oct)
14 | 20 (date)
05 | friday
03 | 03 (hour)
2B | 43 (min)
1E | 30 (sec)
FF | (fff not specified)
80 | (deviation not specified?)
(...) | (...)
**End Data**|
A1 A5 | Frame check sequence (FCS) (Check sum calculated from full frame, excluding flags and FCS, according to RFC 1662)
7E | Frame End flag