Have segfaults each time I receive a notification from a sensor. Python 3 version of pygattlib as some problems with notifications and I WeDo 2.0 and a few other BLE devices I've been playing with can work Notifications with pygattlib since they were not very well documented and Unfortunately when starting sensor methods I found a problem: the wayīOOST was implemented requires notifications. Only a few control methods yet (LED color, motors timed) but give me time. I will document my progress at github BOOSTreveng
#LEGO WEDO 2.0 PREVENT FLOODING LIBRARY CODE#
Sensor is much more difficult, don't think I can get it without a code sample (for WeDo 2.0 I had some luck, there was an example at Microsoft site). In a few days I hope to have at least a basic method to control the motors. When/if I have something more decent will add a tutorial to ev3dev site like I did for WeDo 2.0. I will document my progress at my blog to don't pollute this issue any more. Given the fact that it is rather expensive compared to the usefulness that it provides, this is probably going to be pretty low in the priority list unless someone wants to make this his/her pet project. I have a feeling that this means that the motor is not very powerful.
The hub takes only 2 AA batteries, which means it operates at 3VDC.
#LEGO WEDO 2.0 PREVENT FLOODING LIBRARY BLUETOOTH#
It is advertised at BLE (Bluetooth Low Energy), but I saw some mentions that it might also work with Bluetooth 2.0. It also has what looks like the same motion (really distance) and tilt sensors as WeDo 1.0, just with the new style electrical connector. WeDo 2.0 has a new "medium" motor that has studs on top which is kind of nifty. Instead, it as a new, unique electrical connector. It is not compatible with Power Functions like it's WeDo predecessor (now being called WeDo 1.0). If you haven't seen the news, LEGO Education has released WeDo 2.0. I know someone will ask about this sooner or later (actually I'm kind of surprised no one has yet).
0 kommentar(er)
