Lego boost vs wedo code#
So it's easy to use previous code with just some minor changes.Įv3dev already works fine with Powered Up: current stretch snapshots include BlueZ and pybluez with gattlib. The good part: Powered Up uses same BLE services/characteristics as BOOST. The DUPLO trains will not be marketed as Powered Up.
New sets are also being release, like a Batman car with same smart hub as the trains (and 2x WeDo 2 motors) and new DUPLO trains. Same happens with the Color+Distance sensor.īOOST is also Powered Up but not marketed as such. The motor (a kind of Powered Up version of the Power Functions Medium Motor) works fine with BOOST and the new trains hub. It's more like a prototype but since it's firmware cannot be upgraded "over the air" so it will not work with recent devices like the motors and sensors that were released with BOOST.īut the motors and sensors released with WeDo2 are Powered Up. They also include a new train motor, essencially a Powered Up version of the Power Functions train motor.Īnd they also include a standalone controller, a basic BLE replacement of the Power Functions IR Command. The new LEGO trains sets include a smart hub with just 6xAAA batteries and two I/O ports, similar to the WeDo 2 Smart Hub. It appears to be the final brand name of "Power Functions 2". Reply to this email directly, view it on GitHub You are receiving this because you commented. Package) but at least it can be used from a linux computer.
It will not work on ev3dev (at least not together with the python-ev3dev Since it works with python 2, I'm going to duplicate this library for it. AlreadyĬreated an issue at pygattlib but by the history of their issues I'm afraid 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 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 boost vs wedo 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)
