{"id":923,"date":"2016-06-26T20:38:53","date_gmt":"2016-06-26T19:38:53","guid":{"rendered":"http:\/\/ofalcao.pt\/blog\/?p=923"},"modified":"2016-06-26T20:38:53","modified_gmt":"2016-06-26T19:38:53","slug":"wedo-2-0-led-button-service","status":"publish","type":"post","link":"https:\/\/ofalcao.pt\/blog\/2016\/wedo-2-0-led-button-service","title":{"rendered":"WeDo 2.0 LED Button Service"},"content":{"rendered":"
This post is part 3 of 6 of \u00a0WeDo 2.0 - reverse engineering<\/a><\/div>

And we continue digging into the\u00a0 WeDo 2.0 Hub primary services, now with the “Nordic LED Button Service”<\/p>\n

\"WeDo<\/a><\/p>\n

[A0:E6:F8:1E:58:57][LE]> primary\r\n...\r\nattr handle: 0x000c, end grp handle: 0x002f uuid: 00001523-1212-efde-1523-785feabcd123\r\n...<\/pre>\n
So this Primary service uses handles from 0x000c to 0x002f. Let’s look deeper:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> characteristics 000c 002f\r\nhandle: 0x000d, char properties: 0x0a, char value handle: 0x000e, uuid: 00001524-1212-efde-1523-785feabcd123\r\nhandle: 0x0010, char properties: 0x12, char value handle: 0x0011, uuid: 00001526-1212-efde-1523-785feabcd123\r\nhandle: 0x0014, char properties: 0x10, char value handle: 0x0015, uuid: 00001527-1212-efde-1523-785feabcd123\r\nhandle: 0x0018, char properties: 0x12, char value handle: 0x0019, uuid: 00001528-1212-efde-1523-785feabcd123\r\nhandle: 0x001c, char properties: 0x12, char value handle: 0x001d, uuid: 00001529-1212-efde-1523-785feabcd123\r\nhandle: 0x0020, char properties: 0x12, char value handle: 0x0021, uuid: 0000152a-1212-efde-1523-785feabcd123\r\nhandle: 0x0024, char properties: 0x08, char value handle: 0x0025, uuid: 0000152b-1212-efde-1523-785feabcd123\r\nhandle: 0x0027, char properties: 0x0a, char value handle: 0x0028, uuid: 0000152c-1212-efde-1523-785feabcd123\r\nhandle: 0x002a, char properties: 0x02, char value handle: 0x002b, uuid: 0000152d-1212-efde-1523-785feabcd123\r\nhandle: 0x002d, char properties: 0x08, char value handle: 0x002e, uuid: 0000152e-1212-efde-1523-785feabcd123\r\n\r\n[A0:E6:F8:1E:58:57][LE]> char-desc 000c 002f\r\nhandle: 0x000c, uuid: 00002800-0000-1000-8000-00805f9b34fb\r\nhandle: 0x000d, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x000e, uuid: 00001524-1212-efde-1523-785feabcd123\r\nhandle: 0x000f, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0010, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0011, uuid: 00001526-1212-efde-1523-785feabcd123\r\nhandle: 0x0012, uuid: 00002902-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0013, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0014, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0015, uuid: 00001527-1212-efde-1523-785feabcd123\r\nhandle: 0x0016, uuid: 00002902-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0017, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0018, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0019, uuid: 00001528-1212-efde-1523-785feabcd123\r\nhandle: 0x001a, uuid: 00002902-0000-1000-8000-00805f9b34fb\r\nhandle: 0x001b, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x001c, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x001d, uuid: 00001529-1212-efde-1523-785feabcd123\r\nhandle: 0x001e, uuid: 00002902-0000-1000-8000-00805f9b34fb\r\nhandle: 0x001f, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0020, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0021, uuid: 0000152a-1212-efde-1523-785feabcd123\r\nhandle: 0x0022, uuid: 00002902-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0023, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0024, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0025, uuid: 0000152b-1212-efde-1523-785feabcd123\r\nhandle: 0x0026, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0027, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0028, uuid: 0000152c-1212-efde-1523-785feabcd123\r\nhandle: 0x0029, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x002a, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x002b, uuid: 0000152d-1212-efde-1523-785feabcd123\r\nhandle: 0x002c, uuid: 00002901-0000-1000-8000-00805f9b34fb\r\nhandle: 0x002d, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x002e, uuid: 0000152e-1212-efde-1523-785feabcd123\r\nhandle: 0x002f, uuid: 00002901-0000-1000-8000-00805f9b34fb<\/pre>\n
Lot of things here: 10 characteristics and 36 handles!<\/p>\n
The first handle (0x000c) just marks the begin of the service (UUID 2800).<\/p>\n
Then we see that there are 10 handles with UUID 2803 (Characteristic Declaration Attribute) and also 10 handles with UUID 2901 (Characteristic User Description) – these handles mark the begin of each characteristic and also defines its properties, so let’s read them all\u00a0 (char-read-hnd) and translate it:<\/p>\n
Name Char               0x000e  read+write\r\nButton Char             0x0011  notify+read\r\nPort Type Char          0x0015  notify\r\nLow Voltage alert       0x0019  notify+read\r\nHigh Current alert      0x001d  notify+read\r\nLow Signal alert        0x0021  notify+read\r\nTurn off device         0x0025  write\r\nVcc port control        0x0028  read+write\r\nBattery type Indicator  0x002b  read\r\nDisconnect Char         0x002e  write<\/pre>\n
Some characteristics also have an handle with UUID 2902 (Client Characteristic Configuration). That’s used for Notifications – the 5 characteristics that support this feature use this extra handle to activate or deactivate it.<\/p>\n
So let’s read the 7 handles that are readable:<\/p>\n
Name Char               75 30 30 30 31 = u0001\r\nButton Char             00\r\nLow Voltage alert       00\r\nHigh Current alert      00\r\nLow Signal alert        00\r\nVcc port control        01\r\nBattery type Indicator  00<\/pre>\n
So ‘Name char’ contains the friendly name of my Hub. And it is writable, so what happens if I change it?<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-write-cmd 0x000e 4d616a6f72\r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 0x00e\r\nCharacteristic value\/descriptor: 4d 61 6a 6f 72<\/pre>\n
Well it retains what I wrote.<\/p>\n
And if I now read the ‘Device Name’ it is no longer ‘u0001’:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-read-uuid 0x2A00\r\nhandle: 0x0003 \u00a0\u00a0 \u00a0 value: 4d 61 6a 6f 72<\/pre>\n
So now my Hub announces a new name:<\/p>\n
$ sudo hcitool -i hci0 lescan\r\nLE Scan ...\r\nA0:E6:F8:1E:58:57 (unknown)\r\nA0:E6:F8:1E:58:57 Major<\/pre>\n
\"Changing<\/a><\/p>\n
Cool, isn’t it?<\/p>\n
Now the ‘Button Char’ just reads zero. But if I press the Hub’s button while I read it:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-read-hnd 0011\r\nCharacteristic value\/descriptor: 01<\/pre>\n
it reads ‘1’.<\/p>\n
And what about ‘Port Type Char’? It’s not defined as readable (just ‘notify’) but I can try to read it anyway:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-read-hnd 0015\r\nCharacteristic value\/descriptor:<\/pre>\n
Hmm… null value.<\/p>\n
But I have nothing connected to the Hub. Let’s try it again with a motor at port 1:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-read-hnd 0015\r\nCharacteristic value\/descriptor: 01 01 00 01 01 00 00 00 01 00 00 00<\/pre>\n
And removing the motor again:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-read-hnd 0015\r\nCharacteristic value\/descriptor: 01 00<\/pre>\n
Interesting – it’s not null now.<\/p>\n
Let’s do the same again but on port 2:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-read-hnd 0015\r\nCharacteristic value\/descriptor: 02 01 01 01 01 00 00 00 01 00 00 00\r\n\r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 0015\r\nCharacteristic value\/descriptor: 02 00<\/pre>\n
So the first byte seems to identify the Port (’01’ or ’02’) and the second byte the action (’01’ might be ‘device plugged’ and ’00’ might be ‘device removed’). I have no explanation for the third byte and the other 8 bytes bytes seem to be some kind of identification of the motor.<\/p>\n
Now let’s connect a tilt sensor in port 1 (and nothing in port 2):<\/p>\n
01 01 00 22 00 00 00 10 00 00 00 10<\/pre>\n
and then move it to port 2:<\/p>\n
02 01 01 22 00 00 00 10 00 00 00 10<\/pre>\n
Now just a distance sensor in port 1:<\/p>\n
01 01 00 23 00 00 00 10 00 00 00 10<\/pre>\n
and move it to port 2:<\/p>\n
02 01 01 23 00 00 00 10 00 00 00 10<\/pre>\n
Now just the motor again in port 1 and then the tilt sensor in port 2 (two readings):<\/p>\n
01 01 00 01 01 00 00 00 01 00 00 00\r\n02 01 01 22 00 00 00 10 00 00 00 10<\/pre>\n
So ‘Port Type Char’ doesn’t describe the ports state, it just shows the last action detected at ports. I think that’s the reason it’s not defined as ‘notify + read’, it’s purpose is just to notify that a change ocurred on ports.<\/p>\n
Now we have 3 characteristics named “Alert”: Low Voltage Alert, High Current Alert and Low Signal Alert. Their names seem clear enough to understand their purpose and since all read zero everything seems to be OK. But let’s try to force an “High Current Alert” – make the motor run, block it and read the handle:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 00 \r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 00 \r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 00 \r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 00 \r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 01 \r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 01 \r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 01 \r\n[A0:E6:F8:1E:58:57][LE]> char-read-hnd 001d\r\nCharacteristic value\/descriptor: 00<\/pre>\n
When I block the motor with my hand, the Hub beeps and flashes the LED twice (in yellow). And sometimes the Alert reads ’01’.<\/p>\n
But instead of reading several times the handler, we can activate ‘Notifications’ by turning ON the ‘notification’ flag in the ‘Client Characteristic Configuration’ and then just wait for the Hub to send the notification when the High Current Alert changes it’s state:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-write-req 001e 0100 -listen\r\nCharacteristic value was written successfully\r\n[A0:E6:F8:1E:58:57][LE]> char-write-cmd 003d 01010164\r\nNotification handle = 0x001d value: 01 \r\nNotification handle = 0x001d value: 00<\/pre>\n
We used a different write command: ‘char-write-req’ instead of ‘char-write-cmd’ expects an answer from the device and ‘-listen’ keeps listening for future ‘answers’.<\/p>\n
Now the ‘Vcc port control’ name isn’t much clear about it’s purpose. It reads ‘1’ but it’s also writable… does it allows us to control power in the ports? No matter what I write to 0x003d it seems to retain only ‘0’ or ‘1’ and when I write ‘0’ to it while the motor is running it keeps running.<\/p>\n
‘Battery type indicator’ reads zero, I guess that it identifies the kind of battery being used. I’m using 2 AA alcaline batteries, will try again with the LiPo battery when I get it.<\/p>\n
And finally the 2 writable-only characteristics: ‘Disconnect Char’ and ‘Turn off device’. They also seem quite clear about their purpose:<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-write-cmd 002e 01\r\n[A0:E6:F8:1E:58:57][LE]> \r\n(gatttool:8257): GLib-WARNING **: Invalid file descriptor.\r\n\r\n[A0:E6:F8:1E:58:57][LE]> connect\r\nAttempting to connect to A0:E6:F8:1E:58:57\r\nConnection successful<\/pre>\n
Writing to ‘Disconnect Char’ makes the Hub disconnects but keeps it in discovery mode so I cpuld reconnect to it.<\/p>\n
[A0:E6:F8:1E:58:57][LE]> char-write-cmd 0025 01\r\n[A0:E6:F8:1E:58:57][LE]> \r\n(gatttool:8257): GLib-WARNING **: Invalid file descriptor.\r\n\r\n[A0:E6:F8:1E:58:57][LE]> connect\r\nAttempting to connect to A0:E6:F8:1E:58:57\r\n[A0:E6:F8:1E:58:57][LE]> \r\nError: connect error: Connection refused (111)<\/pre>\n
Writing to ‘Turn off device’ really turns it off.<\/p>\n
So that’s it for ‘Nordic LED button service’. What LED, you ask? Well, the Android App is from Nordic and they have some examples on the Net with this UUID so my explanation is that LEGO used part of their code for the ‘button’ part without changing the UUID so the App recognizes it this way.<\/p>\n
Next post: Motors and LED.<\/p>\n","protected":false},"excerpt":{"rendered":"
This post is part 3  of 6 of \u00a0WeDo 2.0 - reverse engineering<\/a><\/div>
And we continue digging into the\u00a0 WeDo 2.0 Hub primary services, now with the “Nordic LED Button Service” [A0:E6:F8:1E:58:57][LE]> primary … attr handle: 0x000c, end grp handle: 0x002f uuid: 00001523-1212-efde-1523-785feabcd123 … So this Primary service uses handles from 0x000c to 0x002f. Let’s look deeper: [A0:E6:F8:1E:58:57][LE]> characteristics 000c 002f handle: 0x000d, char properties: 0x0a, char value … Continuar a ler “WeDo 2.0 LED Button Service”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[1],"tags":[],"series":[269],"class_list":["post-923","post","type-post","status-publish","format-standard","hentry","category-sem-categoria","series-wedo-2-0-reverse-engineering"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p2Mhyv-eT","_links":{"self":[{"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/posts\/923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/comments?post=923"}],"version-history":[{"count":0,"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/posts\/923\/revisions"}],"wp:attachment":[{"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/media?parent=923"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/categories?post=923"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/tags?post=923"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/ofalcao.pt\/blog\/wp-json\/wp\/v2\/series?post=923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}