<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Plugwise protocol unleashed part 3: internal clock information</title>
	<atom:link href="http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/</link>
	<description>Blogging on various IT subjects</description>
	<lastBuildDate>Mon, 26 Dec 2011 09:18:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Marc Dirix</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-3282</link>
		<dc:creator>Marc Dirix</dc:creator>
		<pubDate>Wed, 10 Aug 2011 13:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-3282</guid>
		<description>Scratch that.

I&#039;ve found the the hourly logs no longer is in &quot;hours&quot; since date-X but now also is given in the same &quot;year-month-month_minutes&quot; format as in 0024.</description>
		<content:encoded><![CDATA[<p>Scratch that.</p>
<p>I&#8217;ve found the the hourly logs no longer is in &#8220;hours&#8221; since date-X but now also is given in the same &#8220;year-month-month_minutes&#8221; format as in 0024.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Dirix</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-3281</link>
		<dc:creator>Marc Dirix</dc:creator>
		<pubDate>Wed, 10 Aug 2011 13:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-3281</guid>
		<description>I&#039;m using 0016 on all plugs to synchronize the internal clock monthly. 
But somehowe changing the plug clock als changes the timebase for the hourly logs. 

Does anyone now how these relate? The windows tool doesn&#039;t seem to be bothered by it.
Should I only update the circleplus?

Best regards,

Marc Dirix</description>
		<content:encoded><![CDATA[<p>I&#8217;m using 0016 on all plugs to synchronize the internal clock monthly.<br />
But somehowe changing the plug clock als changes the timebase for the hourly logs. </p>
<p>Does anyone now how these relate? The windows tool doesn&#8217;t seem to be bothered by it.<br />
Should I only update the circleplus?</p>
<p>Best regards,</p>
<p>Marc Dirix</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Plugwise Protocol Analysis, Part 5 (Date/Time) &#171; roheve</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-3239</link>
		<dc:creator>Plugwise Protocol Analysis, Part 5 (Date/Time) &#171; roheve</dc:creator>
		<pubDate>Sun, 03 Jul 2011 21:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-3239</guid>
		<description>[...] and more details become clear in the plugwise protocol. In Plugwise Unleased Maarten made this post, that describes a timesync between the modules and the computer. There is also a second DateTime [...]</description>
		<content:encoded><![CDATA[<p>[...] and more details become clear in the plugwise protocol. In Plugwise Unleased Maarten made this post, that describes a timesync between the modules and the computer. There is also a second DateTime [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roelof</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-3181</link>
		<dc:creator>Roelof</dc:creator>
		<pubDate>Sun, 15 May 2011 19:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-3181</guid>
		<description>Oops, I messed up two responses while copy/pasting, but the timecode is still the same... Noticed it after submitting my comment.

SEND	003E 000D6F0000B1B64B

RECV	003F 0161 000D6F0000B1B64B 1203 02 07 01 45 7A

SEND	003E 000D6F0000B1B967

RECV	003F 0163 000D6F0000B1B967 1203 00 07 01 45 7A</description>
		<content:encoded><![CDATA[<p>Oops, I messed up two responses while copy/pasting, but the timecode is still the same&#8230; Noticed it after submitting my comment.</p>
<p>SEND	003E 000D6F0000B1B64B</p>
<p>RECV	003F 0161 000D6F0000B1B64B 1203 02 07 01 45 7A</p>
<p>SEND	003E 000D6F0000B1B967</p>
<p>RECV	003F 0163 000D6F0000B1B967 1203 00 07 01 45 7A</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roelof</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-3180</link>
		<dc:creator>Roelof</dc:creator>
		<pubDate>Sun, 15 May 2011 19:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-3180</guid>
		<description>My 0016 string is different (2 bytes added FFFF), probably because the firmware changed.

After initialisation, just after the 0016 command, I also see an 0029  command, followed by a 003A is a reply/ This 003A reply contains data that is similar to the clock-time data of the 3E reply. I an not sure however, there is also a difference.

SEND	0016 000D6F0000B1B64B 0B0552FB FFFFFFFF FFFF 12 03 02 07
RECV	0000 sequ 00D7 000D6F0000B1B64B
YOUR	0016 000D6F0000551C14 0A021501 FFFFFFFF      11 25 36 04

SEND	0029 000D6F0000B1B64B

RECV	003A sequ 000D6F0000B1B64B 02 03 18 07 15 05 11

SEND	003E 000D6F0000B1B64B
RECV	003F sequ 000D6F0000B1B967 12 03 00 07   01 45 7A
YOUR	003F sequ 000D6F0000552XXX 13 25 35 04   01 45 7A

Te time in my &#039;message&#039; is 20u03[CET]=18u03[UTC] = 12u03 (hex), DoW=7 (sunday)
The 01 45 7A trailer seems quite constant.

I am wondering what to do with the FFFFFFFF (and FFFF) part, where you mention it has to do wite the logbuffers.  
The logbuffer formula you mentioned elsewhere seems changed. (both offset and divider), for my firmware. Boundaries are not at 32 bytes anymore but at 8, and the offset is bigger now (not sure how big)</description>
		<content:encoded><![CDATA[<p>My 0016 string is different (2 bytes added FFFF), probably because the firmware changed.</p>
<p>After initialisation, just after the 0016 command, I also see an 0029  command, followed by a 003A is a reply/ This 003A reply contains data that is similar to the clock-time data of the 3E reply. I an not sure however, there is also a difference.</p>
<p>SEND	0016 000D6F0000B1B64B 0B0552FB FFFFFFFF FFFF 12 03 02 07<br />
RECV	0000 sequ 00D7 000D6F0000B1B64B<br />
YOUR	0016 000D6F0000551C14 0A021501 FFFFFFFF      11 25 36 04</p>
<p>SEND	0029 000D6F0000B1B64B</p>
<p>RECV	003A sequ 000D6F0000B1B64B 02 03 18 07 15 05 11</p>
<p>SEND	003E 000D6F0000B1B64B<br />
RECV	003F sequ 000D6F0000B1B967 12 03 00 07   01 45 7A<br />
YOUR	003F sequ 000D6F0000552XXX 13 25 35 04   01 45 7A</p>
<p>Te time in my &#8216;message&#8217; is 20u03[CET]=18u03[UTC] = 12u03 (hex), DoW=7 (sunday)<br />
The 01 45 7A trailer seems quite constant.</p>
<p>I am wondering what to do with the FFFFFFFF (and FFFF) part, where you mention it has to do wite the logbuffers.<br />
The logbuffer formula you mentioned elsewhere seems changed. (both offset and divider), for my firmware. Boundaries are not at 32 bytes anymore but at 8, and the offset is bigger now (not sure how big)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JMcL</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-1520</link>
		<dc:creator>JMcL</dc:creator>
		<pubDate>Tue, 10 Aug 2010 11:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-1520</guid>
		<description>Further to Deep&#039;s analysis of the send command/ack/response sequence, there&#039;s an additional useful response regarding the packet sequence number

When a command packet is sent to the stick, the first reponse from the stick is a line in the form:

PutFifoUnicast 33 : Handle 129 : 000D6F0000xxxxB3

The &#039;129&#039; in the line above is specific to the command sent. From what I&#039;ve implemented it&#039;s as follows:

PowerChange (code=0017) : 33
PowerInfo (code=0012) : 23
Calibration (code=0026) : 60

I presume other commands will also follow this pattern.

The handle returned is the value (in decimal) of the packet sequence Deep refers to and will be used on the subsequent ACK and data packets, so the conversation is now along the lines of (leaving out frame start/ends and inserting spaces for clarity - CCCC represents CRC):

SEND: 0017 000D6F0000xxxxB3 CCCC
RECV: PutFifoUnicast 33 : Handle 129 : 000D6F0000xxxxB3
RECV: 0000 0081 00C1 CCCC (note &#039;0081&#039; = 129)
RECV: 0000 0081 00D8 00D8000D6F0000xxxxB3 CCCC

I guess this could be useful to optimise access to plugs. Fire a command, get the handle, and then keep track of responses received, leaving you free to send other commands in the meantime (Note: I haven&#039;t tried this yet, it&#039;s purely speculation!!!)</description>
		<content:encoded><![CDATA[<p>Further to Deep&#8217;s analysis of the send command/ack/response sequence, there&#8217;s an additional useful response regarding the packet sequence number</p>
<p>When a command packet is sent to the stick, the first reponse from the stick is a line in the form:</p>
<p>PutFifoUnicast 33 : Handle 129 : 000D6F0000xxxxB3</p>
<p>The &#8217;129&#8242; in the line above is specific to the command sent. From what I&#8217;ve implemented it&#8217;s as follows:</p>
<p>PowerChange (code=0017) : 33<br />
PowerInfo (code=0012) : 23<br />
Calibration (code=0026) : 60</p>
<p>I presume other commands will also follow this pattern.</p>
<p>The handle returned is the value (in decimal) of the packet sequence Deep refers to and will be used on the subsequent ACK and data packets, so the conversation is now along the lines of (leaving out frame start/ends and inserting spaces for clarity &#8211; CCCC represents CRC):</p>
<p>SEND: 0017 000D6F0000xxxxB3 CCCC<br />
RECV: PutFifoUnicast 33 : Handle 129 : 000D6F0000xxxxB3<br />
RECV: 0000 0081 00C1 CCCC (note &#8217;0081&#8242; = 129)<br />
RECV: 0000 0081 00D8 00D8000D6F0000xxxxB3 CCCC</p>
<p>I guess this could be useful to optimise access to plugs. Fire a command, get the handle, and then keep track of responses received, leaving you free to send other commands in the meantime (Note: I haven&#8217;t tried this yet, it&#8217;s purely speculation!!!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: YogiBear75</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-302</link>
		<dc:creator>YogiBear75</dc:creator>
		<pubDate>Fri, 28 May 2010 09:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-302</guid>
		<description>Hi Maarten,

I would like to receive more information on the new protocol version :)
Can you perhaps e-mail me some code, so I can adjust my Perl scripts ?
I am using XPL-Perl with plugwise.pm and already made some adjustments.

Thnx,

Ronald</description>
		<content:encoded><![CDATA[<p>Hi Maarten,</p>
<p>I would like to receive more information on the new protocol version :)<br />
Can you perhaps e-mail me some code, so I can adjust my Perl scripts ?<br />
I am using XPL-Perl with plugwise.pm and already made some adjustments.</p>
<p>Thnx,</p>
<p>Ronald</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olli</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-285</link>
		<dc:creator>Olli</dc:creator>
		<pubDate>Tue, 18 May 2010 08:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-285</guid>
		<description>How do I PM to deep? I assume need to register with this website but where?</description>
		<content:encoded><![CDATA[<p>How do I PM to deep? I assume need to register with this website but where?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deep</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-263</link>
		<dc:creator>Deep</dc:creator>
		<pubDate>Wed, 05 May 2010 19:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-263</guid>
		<description>I have more interesting information about the PowerInfo request.

If you want this info, reply to me via PM</description>
		<content:encoded><![CDATA[<p>I have more interesting information about the PowerInfo request.</p>
<p>If you want this info, reply to me via PM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deep</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-3-internal-clock-information/comment-page-1/#comment-261</link>
		<dc:creator>Deep</dc:creator>
		<pubDate>Tue, 04 May 2010 18:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=149#comment-261</guid>
		<description>site formatting screws up lot of my detail in above. send me pm and I send correct datas without fukup reformat</description>
		<content:encoded><![CDATA[<p>site formatting screws up lot of my detail in above. send me pm and I send correct datas without fukup reformat</p>
]]></content:encoded>
	</item>
</channel>
</rss>

