comparison docs/protocol.txt @ 8:cf915ece9e48

Remove "week day" from the TIME response The week day item in the TIME response is useless. Drivewire 4 doesn't return it and since that is the most common Drivewire implementation, it makes sense to conform to that definition.
author William Astle <lost@l-w.ca>
date Sat, 16 Jul 2016 18:56:01 -0600
parents 2e382e1a173e
children 36c4cda4b6c4
comparison
equal deleted inserted replaced
7:2e382e1a173e 8:cf915ece9e48
117 1 month (1-12) 117 1 month (1-12)
118 2 day (1-31) 118 2 day (1-31)
119 3 hour (0-23) 119 3 hour (0-23)
120 4 minute (0-59) 120 4 minute (0-59)
121 5 second (0-60) 121 5 second (0-60)
122 6 day of week (0-6, 0 = Sunday)
123 122
124 This packet roughly corresponds to the return structure for the localtime() 123 This packet roughly corresponds to the return structure for the localtime()
125 function in C. Note that this request is part of the original Drivewire 3 124 function in C. Note that this request is part of the original Drivewire 3
126 specification. However, Drivewire 3 specifies only 0-59 for the seconds 125 specification. However, Drivewire 3 specifies only 0-59 for the seconds
127 value. LWWire allows the value 60 for the seconds value for the rare case 126 value. LWWire allows the value 60 for the seconds value for the rare case
128 where a leap second is in effect. This is unlikely to ever be a problem in 127 where a leap second is in effect. This is unlikely to ever be a problem in
129 real deployments since leap seconds can occur at most four times per year. 128 real deployments since leap seconds can occur at most twelve times per year.
129
130 The original Drivewire 3 ipmlementation returned a seventh octet which
131 encoded the day of the week with Sunday as 0. Since the most common
132 Drivewire implementation is the Drivewire 4 server which only sends the six
133 octets and the day of the week value is basically useless, this
134 specification conforms to the Drivewire 4 implementation.
130 135
131 136
132 46 PRINTFLUSH 137 46 PRINTFLUSH
133 138
134 This operation tells the server to flush its print buffer to its defined 139 This operation tells the server to flush its print buffer to its defined