Thank you for helping to change that.WeDo 2.0 has been retired. WeDo2.0 is a fantastic tool, that has a very limited reach, because of little details like this. It’s a shame that this kind of closed source approach from LEGO (with the unusable SDK) is hampering STEAM education, unnecessarily. The trick was to separate the integer values to 32bit values and send it as a list.Īgain, thank you for your inspiring work on this. Using your finding on reversengineering the BT protocol and Rex’s hints on appinventor I was able to figure out how to comunicate with the hub and even expand on it a little, so I have sound working through MIT AI too. I just wanted to thank you for your work. Your blog is the best resource on how to play with WeDo2.0 from Linux/Raspberrypi. Even the android sw is limited to tablets only. But the stupid Windows/Mac software is holding it back. The potential of the LEGO WeDo for teaching is huge. I don’t understand how can it be that the only two usable resources how to combine wedo2.0 and appinventor is your blog and Rex Baker’s blog. I would like to move on to adding computer vision control, but this may require the full blown Android SDK + Lego SDK. Let me know if you have suggestions on how to improve or further the app. Thanks again for all of the critical inputs. The Lego WeDo2 app didn’t implement the Piezo control either, which makes me wonder if they also had a problem with the Android version of this control.Īnyway, all of this was based on your inputs, and I just implemented some code. I believe all of the inputs were correct, and I tried manually passing the values, but it still just left the Smart Hub with a continuous mono-tone buzz. I got almost all of the parts to work: motors + LED. So I published the finished app in Google Play:Īlso, I added a blog entry to document the code in case others want to try it as well: I couldn’t post the code to the MIT App Inventor gallery, since they don’t allow apps with ‘experimental’ extensions. I got the Lego WeDo2 car app to work based on your blog and the EV3Dev postings. it would also be nice to know the trick things, like determining the button state (pushed/unpushed), making tones with the piezo buzzer, color codes for the RGB LED (you already posted the one for “red” above) – (from your EV3Dev posting, I got most of the motor control codes) getting feedback from the proximity and tilt sensor So, I’m wondering if you’ve deciphered the rest of the control and data codes for the Smart Hub? Mainly, I’m looking for: Anyway, I could control the WeDo from RPi as well using the gatttool and the python libraries as well. Next, I was able to make do the same based upon your tutorial in the site using my BrickPi (RPi 3B…compiling the python GATTRequester was quite easy on that platform (not nearly the headaches you mentioned with the EV3 brick). Good.so I can check off controlling the motors from Android. I’ve followed your example from above, and built the same WeDo app in App Inventor…quite easy like you said. Thanks a lot for your blog on Lego and especially Lego WeDo2.0. Damn easy to create an BLE Android app! Autor Major Alvega Publicado em 8 de Setembro de 2016 Categorias Sem categoria Now that I finally started, I think I will use App Inventor some more times. So I tried another block, “call BluetoothLE.WriteIntValue”. WriteStringValue” but I couldn’t find a way to convert an hexadecimal string (“06040109”) to a proper string to send. Then I tried a block called “call BluetoothLE. So I had to go back to my notes and find the Service UUID and the Characteristic UUID: service_uuid = 00004f0e-1212-efde-1523-785feabcd123Ĭharacteristic_uuid = 00001565-1212-efde-1523-785feabcd123 Just needed to add the BLE extension to start working, getting a connection was easy but writing to the handle took a while since App Inventor BLE extension doesn’t use handles, just UUIDs. When using gatttool that’s done with just char-write-cmd 3d 06040109 I just wanted to connect to the WeDo 2.0 Smart Hub and change the color to RED. I’ve never used App Inventor before but I had already installed the Companion once in my Android Phone because I read something somewhere and found it quite similar to Snap! and Scratch (and also just because it is from MIT… I have a fetiche for MIT back from when I was at college and read Nicholas Negroponte articles on Wired). Rocha is trying to use MIT App Inventor to control the WeDo 2.0 Smart Hub RGB LED.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |