|  | @@ -75,8 +75,8 @@ Once I connected to it, the green light stayed on permanently. Clearly, I was
 | 
	
		
			
				|  |  |  making progress. A lot of services were also discovered but I had no idea what
 | 
	
		
			
				|  |  |  those things were at that point.</p>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -<p>After a lot of poking around, I could check the general device information.  You
 | 
	
		
			
				|  |  | -could get hardware, software and firmware version. There&rsquo;s also the device
 | 
	
		
			
				|  |  | +<p>After a lot of poking around, I could check the general device information. You
 | 
	
		
			
				|  |  | +could get the hardware, software and firmware version. There&rsquo;s also the device
 | 
	
		
			
				|  |  |  serial number which was nowhere on the actual physical device.</p>
 | 
	
		
			
				|  |  |  <div class="highlight" style="background: #f8f8f8"><pre style="line-height: 125%"><span></span>[CHSLEEV_00]# select-attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017
 | 
	
		
			
				|  |  |  [CH BTScale_00:/service0010/char0017]# attribute-info
 | 
	
	
		
			
				|  | @@ -127,7 +127,7 @@ Attempting to read /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/de
 | 
	
		
			
				|  |  |  denied. I could however, notify on them. But that didn&rsquo;t yield anything as well.
 | 
	
		
			
				|  |  |  What I <em>could</em> read was Accel Enable, which was set to 00. I guess that means it
 | 
	
		
			
				|  |  |  was off. After writing 01 to Accel Enable, I found I could get values out of
 | 
	
		
			
				|  |  | -Accel X-Coordinate!</p>
 | 
	
		
			
				|  |  | +Accel X-Coordinate! Also, the green LED which was permanently on turned off.</p>
 | 
	
		
			
				|  |  |  <div class="highlight" style="background: #f8f8f8"><pre style="line-height: 125%"><span></span>[CHSLEEV_00]# select-attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024
 | 
	
		
			
				|  |  |  [CH BTScale_00:/service0023/char0024]# write 01
 | 
	
		
			
				|  |  |  Attempting to write /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024
 | 
	
	
		
			
				|  | @@ -153,12 +153,12 @@ Notify started
 | 
	
		
			
				|  |  |  Now, I just had to figure out how to convert the values into grams. It looked
 | 
	
		
			
				|  |  |  like the values were 32-bit integers sent as 4 bytes. In the above example it
 | 
	
		
			
				|  |  |  would be <code>0x0002a35b</code>, <code>0x0002a355</code>, <code>0x0002a359</code> or 172891, 172855, 172899. The
 | 
	
		
			
				|  |  | -values also decrease as you exert more effort on the scale. So assuming you have
 | 
	
		
			
				|  |  | -take the initial value as <em>tare</em>, you simply subtract any succeeding from that
 | 
	
		
			
				|  |  | -<em>tare</em> and you can have your &ldquo;weight&rdquo;.</p>
 | 
	
		
			
				|  |  | +values also decrease as you exert more effort on the scale. So assuming you take
 | 
	
		
			
				|  |  | +the initial value as <em>tare</em>, you simply subtract any succeeding value from that
 | 
	
		
			
				|  |  | +<em>tare</em> and you get the &ldquo;weight&rdquo;.</p>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -<p>The values I got didn&rsquo;t seem to be grams though. After weighing some things on
 | 
	
		
			
				|  |  | -an actual scale and comparing the values I got, I found I can just divide the
 | 
	
		
			
				|  |  | +<p>The values I got didn&rsquo;t seem to be in grams though. After weighing some things
 | 
	
		
			
				|  |  | +on an actual scale and comparing the values I got, I found I can just divide the
 | 
	
		
			
				|  |  |  values by 14 and get something in grams. That 14 is entirely a magic number
 | 
	
		
			
				|  |  |  though and I have no idea whether other Prep Pad&rsquo;s would have the same constant.</p>
 | 
	
		
			
				|  |  |  
 |