Page 2 of 2

Re: PERL vs SHELL

Posted: Tue Oct 29, 2013 2:05 pm
by Jameson
Please take a look at the attached screenshot. This is shows the Dash Hex inspector (with the time highlighted in the Hex) and the date that it has parsed on the right.

31 33 31 30 32 39 30 33 31 33 34 35 30 37

This is parsed as 2013 October 29 Tuesday (3rd day of week) 13:45:07

Re: PERL vs SHELL

Posted: Tue Oct 29, 2013 2:16 pm
by riv
So those bytes stands for the day of week?
31 33 31 30 32 39 30 33 31 33 34 35 30 37
where
30 30 => [00] => Sunday
30 31 => [01] => Monday
....
30 36 => [06] => Saturday.

Correct?

Re: PERL vs SHELL

Posted: Tue Oct 29, 2013 2:18 pm
by Jameson
Yes, that is it exactly 8-)

Well actually, not exactly.

Sunday is 30 31
Monday is 30 32
Tuesday is 30 33
Wednesday is 30 34
Thursday is 30 35
Friday is 30 36
Saturday is 30 37

Re: PERL vs SHELL

Posted: Tue Oct 29, 2013 2:33 pm
by riv
got it, thanks.

strange, why it need 2 bytes to keep the day of week, plus why it is required at all, as it is calculated value..... not a question, just concern.

Re: PERL vs SHELL

Posted: Tue Oct 29, 2013 2:36 pm
by riv
result code "0x06" stands for success. any other code and encoding of those error codes?

Re: PERL vs SHELL

Posted: Tue Oct 29, 2013 7:54 pm
by Jameson
Yes, when you successfully send a setting and the meter responds with a "0x06", this means success or OK.

There are no other codes that I know of that the meter would send in the place of "0x06". The meter does not respond if something is wrong.