1,386
edits
Changes
Jump to navigation
Jump to search
<code>1) Header = 0x00FF2A</code>
<code>2) Packet Type = 0xD5</code>
<code>3) Packet Length = 0x0016</code>
<code>4) Unknown = 0x21</code>
<code>5) Meter ID #1 = F05FCB84</code>
<code>6) Meter ID #2 = F0FC4DB1</code>
<code>7) Unknown = 0xE288</code>
<code>8) Unknown = 0x0100</code>
<code>9) Unknown= 0x273205</code>
<code>10) Unknown = 0x00781930</code>
<code>11) Checksum = 0xCB72</code>
<code>12) Trailing byte = 0x00</code>
Landis+Gyr GridStream Protocol (view source)
Revision as of 16:00, 6 March 2021
, 16:00, 6 March 2021→0xD5 Meter Data
Commentary on the data fields above, they have been grouped based on sample analysis but this could be wrong. If you see a new pattern not noticed before you may be correct.
* Field 5 - Never observed a packet with this length and subtype that wasn't all FF's
* Field 6 - Have only seen this change when comparing data from different energy providers
* Field 7 - Appears to either be location identifier (Oncor) or duplicate meter ID (Coserv)
* Field 9 - Increments some amount with each transmission and rolls over at 0xFF
* Field 10 - Value in seconds since meter powered on, '''easy way to see last time the meter experienced a power outage.'''
* Field 15 - This value counts from near 0 to around 3FFF and rolls over, not sure what it is. Have not been able to correlate the counting value or speed vs time to any sort of power utilization.
{| class="wikitable"
====0xD5 Meter Data====
There appear to be multiple packet lengths and styles for the 0xD5 packet. There are some Some samples shown below showing.
{| class="wikitable"
|+0xD5 Captured packet
|00
|}
