User Tools

Site Tools


gs-iwds07

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
gs-iwds07 [2017/02/26 13:15]
wo_rasp created
gs-iwds07 [2017/10/31 10:11] (current)
inline fix typos
Line 78: Line 78:
  
 <​code>​ <​code>​
-1011010001110011000 ​0 1 010+1011 0100 0111 0011 0000 1 0 1 
 +uuuu uuuu uuuu uuuu uuuu b s ? i
 </​code>​ </​code>​
  
 Each (group) of numbers has a specific meaning: Each (group) of numbers has a specific meaning:
   * UnitCode: 0 till 19   * UnitCode: 0 till 19
-  * Battary: 20+  * Battery: 20
   * State: 21   * State: 21
-The meaning of Bits 22-24 is unknown.+  * Intrusion contact: 23 
 +The meaning of Bit 22 is unknown.
  
-  * The ''​Unit''​ is defined as a binary number +  * The ''​Unit''​ is defined as a binary number ​(order in above example: lsb...msb) 
-  * The ''​State''​ defines whether a sensor state is opened or closed+  * The ''​Battery''​ defines whether the battery is still fine (1) or not (0) 
 +  * The ''​State''​ defines whether a sensor state is opened ​(0) or closed ​(1) 
 +  * The ''​Intrusion''​ defines whether the sensor is mounted to its base (0) or not (1)
  
 So this code represents: So this code represents:
  
   * UnitCode: 52781   * UnitCode: 52781
-  * State: closed+  ​* Battery: ok 
 +  ​* State: ​open 
 +  * Intrusion: ok (properly mounted) 
 + 
 +When the intrusion contact is triggered, i.e. the device is taken from its platform mount, it sends a message where bits 20-23 are always 0111, regardless of contact state. So if you retrieve the information by simple bitmasking, you will get battery and state values which might be misleading. Furthermore if then the contact is opened or closed, it sends again the normal messages meaning the "​intrusion"​ condition is sent only once and probably needs to be saved.
gs-iwds07.1488114926.txt.gz · Last modified: 2017/02/26 13:15 by wo_rasp