Landis+Gyr GridStream Protocol - Revision history

Hash: /* 00FF 2A 55 Meter Data */ Changed data tags based on discovery using IWR

2023-04-03T14:08:07Z

00FF 2A 55 Meter Data: Changed data tags based on discovery using IWR

← Older revision		Revision as of 14:08, 3 April 2023
Line 210:		Line 210:
	\|-		\|-
	! colspan="4" \|Not part of CRC calc		! colspan="4" \|Not part of CRC calc
	! colspan="11" \|Data		! colspan="9" \|Data Packet
	! colspan="2" \|		! colspan="3" \|Trailing 6 Bytes
			!
	\|-		\|-
	!Start of		!Start of
Line 460:		Line 461:
	\|-		\|-
	! colspan="4" \|Not part of CRC calc		! colspan="4" \|Not part of CRC calc
	! colspan="11" \|Data		! colspan="9" \|Data Packet
	! colspan="2" \|		! colspan="3" \|Trailing 6 Bytes
			!
	\|-		\|-
	!Start of		!Start of
Line 1,194:		Line 1,196:
	\|-		\|-
	! colspan="4" \|Not part of CRC calc		! colspan="4" \|Not part of CRC calc
	! colspan="14" \|~~Payload~~ (Oncor Meter)		! colspan="12" \|Data Packet (Oncor Meter)
	! colspan="2" \|		! colspan="3" \|Trailing 6 Bytes
			!
	\|-		\|-
	!Start of		!Start of

Hash: /* Type, Length and Sub Type */

2023-02-13T01:12:04Z

Type, Length and Sub Type

Show changes

Hash: /* Dallas */ Removed old data

2023-01-14T22:09:01Z

Dallas: Removed old data

@@ Line 1,334: / Line 1,334: @@
 '''''*Note: This file does not contain the trailing bytes shown in the captures above, it stops at the 16 bit Checksum.'''''
-==== Dallas ====
+====Dallas====
 [https://wiki.recessim.com/w/images/9/9b/Oncor_Capture_01-07-2023_30hrs.zip Oncor Capture 01-07-2023 30hrs (CONTAINS NEW PACKETS)]
 ====Austin====

Hash: /* Data captures */ Added new data captures

2023-01-14T22:03:29Z

Data captures: Added new data captures

← Older revision		Revision as of 22:03, 14 January 2023
Line 1,332:		Line 1,332:

	===Data captures===		===Data captures===
	'''''*Note: This file does not contain the trailing bytes shown in the captures above, it stops at the 16 bit Checksum.'''''		'''''*Note: This file does not contain the trailing bytes shown in the captures above, it stops at the 16 bit Checksum.'''''

	[https://wiki.recessim.com/w/images/d/d3/F03B9FFB.txt Oncor Meter - F03B9FFB - 48 hours capture]		==== Dallas ====
			[https://wiki.recessim.com/w/images/d/d3/F03B9FFB.txt Oncor Meter - F03B9FFB - 48 hours capture (OLD MISSING DATA)]

			[https://wiki.recessim.com/w/images/9/9b/Oncor_Capture_01-07-2023_30hrs.zip Oncor Capture 01-07-2023 30hrs (CONTAINS NEW PACKETS)]
	{\| class="wikitable"		{\| class="wikitable"
	\|+Data Requests from SmartMeterTexas (F03B9FFB)		\|+Data Requests from SmartMeterTexas (F03B9FFB)

Hash: /* Sync and Header */ Added GNURadio v4/v5 sync data

2023-01-14T15:34:45Z

Sync and Header: Added GNURadio v4/v5 sync data

← Older revision		Revision as of 15:34, 14 January 2023
Line 45:		Line 45:
	\|[11] '''11111111''' 1		\|[11] '''11111111''' 1
	\|}		\|}
	----Using GNU Radio it was found that shortening the Sync requirements a bit and incorporating part of the header leads to the cleanest data for further downstream processing. The modified sync ~~shown~~ in 8 bit chunks is shown below.		----Using GNU Radio it was found that shortening the Sync requirements a bit and incorporating part of the header leads to the cleanest data for further downstream processing. The modified sync in 8 bit chunks is shown below. These two sync's are both loaded into the '''PDU Align''' block and if either one is matched the full packet is passed downstream.
	{\| class="wikitable"		{\| class="wikitable"
	\|+Sync Word used with GNURadio		\|+Sync Word used with GNURadio for v4
	!0xAA		!0xAA
	!0xAA		!0xAA
			!0x00
			!0x5F
			!0xF
			\|-
			\|10101010
			\|10101010
			\|00000000
			\|01011111
			\|1111
			\|}
			{\| class="wikitable"
			\|+Sync Word used with GNURadio for v5
	!0xAA		!0xAA
	!0xAA		!0xAA
	!~~0xA0~~		!0x00
	!~~0x05~~		!0x7F
	!~~0xFF~~		!0x1F
	\|-		\|-
	\|10101010		\|10101010
	\|10101010		\|10101010
	\|~~10101010~~		\|00000000
	\|~~10101010~~		\|01111111
	\|~~10100000~~		\|11111
	~~\|00000101~~
	~~\|11111111~~
	\|}		\|}
	~~The final byte of the sync (0x2A) along with it's start and stop bits are discarded as part of the processing.~~
	----<br />		----<br />
	====Type, Length and Sub Type====		====Type, Length and Sub Type====

Hash: /* Sync and Header */ Removed 0x2A from the header since new packets were found as part of "New Discovery" YouTube video.

2023-01-14T15:08:41Z

Sync and Header: Removed 0x2A from the header since new packets were found as part of "New Discovery" YouTube video.

← Older revision		Revision as of 15:08, 14 January 2023
Line 28:		Line 28:
	\|1010		\|1010
	\|}		\|}
	----Of particular note is the difference between versions 1-4 and version 5. In version 5 there are two bits [11] that do not respect the start/stop bit checks of the prior versions. The older protocol expects a 0 start bit, ~~bit~~ data bits and a 1 stop bit. By violating two consecutive start bits the older versions of ~~Gridstream~~ ignore version 5 even if they have the same CRC Adder! This appears to be a way to add backwards compatibility to newer versions of ~~Gridstream~~.		----Of particular note is the difference between versions 1-4 and version 5. In version 5 there are two bits [11] that do not respect the start/stop bit checks of the prior versions. The older protocol expects a 0 start bit, 8 data bits and a 1 stop bit. By violating two consecutive start bits the older versions of GridStream ignore version 5 even if they have the same CRC Adder! This appears to be a way to add backwards compatibility to newer versions of GridStream.
	{\| class="wikitable"		{\| class="wikitable"
	\|+Header for Gridstream		\|+Header for Gridstream
	! colspan="3" \|Header v1 - v4		! colspan="2" \|Header v1 - v4
	! rowspan="3" \|		! rowspan="3" \|
	! colspan="3" \|Header v5		! colspan="2" \|Header v5
	\|-		\|-
	!0x00		!0x00
	!0xFF (10 bit)		!0xFF (10 bit)
	~~!0x2A~~
	!0x00		!0x00
	!0xFF (11 bit)		!0xFF (11 bit)
	~~!0x2A~~
	\|-		\|-
	\|0 '''00000000''' 1		\|0 '''00000000''' 1
	\|0 '''11111111''' 1		\|0 '''11111111''' 1
	~~\|0 '''00101010''' 1~~
	\|0 '''00000000''' 1		\|0 '''00000000''' 1
	\|[11] '''11111111''' 1		\|[11] '''11111111''' 1
	~~\|0 '''00101010''' 1~~
	\|}		\|}
	----Using GNU Radio it was found that shortening the Sync requirements a bit and incorporating part of the header leads to the cleanest data for further downstream processing. The modified sync shown in 8 bit chunks is shown below.		----Using GNU Radio it was found that shortening the Sync requirements a bit and incorporating part of the header leads to the cleanest data for further downstream processing. The modified sync shown in 8 bit chunks is shown below.
Line 1,364:		Line 1,360:
	This table lists Real-time data requests from [https://www.smartmetertexas.com/home SmartMeterTexas.com] which allows customers to request current meter readings. You will see 0xD5 packets in the data file closely linked to the times above. When the request is made on the website the meter generally responds within 10-15 seconds meaning the system can send a message to the mesh network, traverse across the meters and return fairly quickly.		This table lists Real-time data requests from [https://www.smartmetertexas.com/home SmartMeterTexas.com] which allows customers to request current meter readings. You will see 0xD5 packets in the data file closely linked to the times above. When the request is made on the website the meter generally responds within 10-15 seconds meaning the system can send a message to the mesh network, traverse across the meters and return fairly quickly.

	==== Austin ====		====Austin====
	[[:File:Austin energy.txt\|Austin energy (Two Meters)]]		[[:File:Austin energy.txt\|Austin energy (Two Meters)]]

Lemonjello: Add data capture for Austin Energy

2022-07-08T12:44:37Z

Add data capture for Austin Energy

← Older revision		Revision as of 12:44, 8 July 2022
Line 1,363:		Line 1,363:
	\|}		\|}
	This table lists Real-time data requests from [https://www.smartmetertexas.com/home SmartMeterTexas.com] which allows customers to request current meter readings. You will see 0xD5 packets in the data file closely linked to the times above. When the request is made on the website the meter generally responds within 10-15 seconds meaning the system can send a message to the mesh network, traverse across the meters and return fairly quickly.		This table lists Real-time data requests from [https://www.smartmetertexas.com/home SmartMeterTexas.com] which allows customers to request current meter readings. You will see 0xD5 packets in the data file closely linked to the times above. When the request is made on the website the meter generally responds within 10-15 seconds meaning the system can send a message to the mesh network, traverse across the meters and return fairly quickly.

			==== Austin ====
			[[:File:Austin energy.txt\|Austin energy (Two Meters)]]

			90C3717A is PV

			90C1FD1A is Net meter

	===GPS Tagged Wardrive Files===		===GPS Tagged Wardrive Files===
Line 1,373:		Line 1,380:
	===Capture files from various regions===		===Capture files from various regions===
	[https://wiki.recessim.com/w/images/7/76/RAW_Capture_NJ.txt.txt Raw capture from New Jersey]<br />[https://wiki.recessim.com/w/images/8/85/Seattle-WA-SCL.txt Raw capture for Seattle City Light (SCL) from Seattle, Washington, USA]		[https://wiki.recessim.com/w/images/7/76/RAW_Capture_NJ.txt.txt Raw capture from New Jersey]<br />[https://wiki.recessim.com/w/images/8/85/Seattle-WA-SCL.txt Raw capture for Seattle City Light (SCL) from Seattle, Washington, USA]

			<br />

Hash: /* Sync and Header */

2021-09-12T20:21:03Z

Sync and Header

← Older revision		Revision as of 20:21, 12 September 2021
Line 7:		Line 7:

	====Sync and Header====		====Sync and Header====
	----The ~~sync word that the~~ Landis+Gyr smart meters ~~send is~~ shown below~~, this~~ can be used in GNU Radio ~~or other tools~~ to ~~receive only~~ packets ~~transmitted by the meters~~. Note that at the start of the header we begin using start and stop bits. These must be stripped off of the rest of the data packet during processing.		----The Landis+Gyr Gridstream smart meters use a 52 bit sync shown below regardless of Gridstream version. This can be used in GNU Radio along with the header to uniquely identify packets. Note that at the start of the header we begin using start and stop bits. These must be stripped off of the rest of the data packet during processing.
	{\| class="wikitable"		{\| class="wikitable"
	\|+Sync ~~and Header~~		\|+Sync 52 bits long
	! colspan="6" \|Sync		! colspan="7" \|Sync
	~~! colspan="3" \|Header~~
	\|-		\|-
			!0xAA
	!0xAA		!0xAA
	!0xAA		!0xAA
Line 19:		Line 19:
	!0xAA		!0xAA
	!0xA		!0xA
	~~!0x00~~
	~~!0xFF~~
	~~!0x2A~~
	\|-		\|-
			\|10101010
	\|10101010		\|10101010
	\|10101010		\|10101010
Line 29:		Line 27:
	\|10101010		\|10101010
	\|1010		\|1010
			\|}
			----Of particular note is the difference between versions 1-4 and version 5. In version 5 there are two bits [11] that do not respect the start/stop bit checks of the prior versions. The older protocol expects a 0 start bit, bit data bits and a 1 stop bit. By violating two consecutive start bits the older versions of Gridstream ignore version 5 even if they have the same CRC Adder! This appears to be a way to add backwards compatibility to newer versions of Gridstream.
			{\| class="wikitable"
			\|+Header for Gridstream
			! colspan="3" \|Header v1 - v4
			! rowspan="3" \|
			! colspan="3" \|Header v5
			\|-
			!0x00
			!0xFF (10 bit)
			!0x2A
			!0x00
			!0xFF (11 bit)
			!0x2A
			\|-
	\|0 '''00000000''' 1		\|0 '''00000000''' 1
	\|0 '''11111111''' 1		\|0 '''11111111''' 1
			\|0 '''00101010''' 1
			\|0 '''00000000''' 1
			\|[11] '''11111111''' 1
	\|0 '''00101010''' 1		\|0 '''00101010''' 1
	\|}		\|}
	Using GNU Radio it was found that shortening the Sync requirements a bit and incorporating part of the header leads to the cleanest data for further downstream processing. The modified sync shown in 8 bit chunks is shown below.		----Using GNU Radio it was found that shortening the Sync requirements a bit and incorporating part of the header leads to the cleanest data for further downstream processing. The modified sync shown in 8 bit chunks is shown below.
	{\| class="wikitable"		{\| class="wikitable"
	\|+Sync Word used with GNURadio		\|+Sync Word used with GNURadio

Sdwilsh: /* Capture files from various regions */ Added a raw capture from Seattle City Light in Seattle, WA

2021-08-12T05:32:09Z

Capture files from various regions: Added a raw capture from Seattle City Light in Seattle, WA

← Older revision		Revision as of 05:32, 12 August 2021
Line 1,356:		Line 1,356:

	===Capture files from various regions===		===Capture files from various regions===
	[https://wiki.recessim.com/w/images/7/76/RAW_Capture_NJ.txt.txt Raw capture from New Jersey]<br />		[https://wiki.recessim.com/w/images/7/76/RAW_Capture_NJ.txt.txt Raw capture from New Jersey]<br />[https://wiki.recessim.com/w/images/8/85/Seattle-WA-SCL.txt Raw capture for Seattle City Light (SCL) from Seattle, Washington, USA]

Hash: /* 0xD5 Meter Data */

2021-07-06T01:34:12Z

0xD5 Meter Data

Show changes