LEGO calls this communication protocol the "LEGO Wireless Protocol" (LWP). The documentation is publicly available at https://lego.github.io/lego-ble-wireless-protocol-docs/.
There is also a GitHub repository that provides the source of this website at https://github.com/LEGO/lego-ble-wireless-protocol-docs. Because of this, it seems reasonable to expect ...
Here's a YT vid on the disassembly, but the still picture shots with no commentary may not be what you need for a good walk-thru.
I don't have a Hub, but wish we all had a pic to make sure we're talking about the same piece.
Regardless, I'm gonna take a crazy shot at it. Let's Go!
We have two gray rectangles:
Big Gray Rectangle on the Left.
Small Gray ...
You can install the software using an alternative App Store such as APKPure. You can alternatively download and install the APK and OBB files directly from various online sources as demonstrated in this video. Once installed, this software seems to work for me on my Galaxy S4, and I assume it would also work on other Android devices. I can connect to and ...
Theoretically possible, but I think you'll find that the droid set contains quite a bit of lego elements that are rather rare, and hence difficult to find in your own collection or from other sources like bricklink.
But at least the electronics can be re-used from the 17101 set.
I myself bought the 75253 boost commander droid set.
You can build all three ...
While LEGO BOOST is compatible with the bricks from other sets, the motor, distance sensor, and Move Hub are not electrically compatible with current EV3 or PowerFunctions components. BOOST uses the same six pin connector as WeDo 2.0 from the Education line:
So, the bad news is that you can't easily use PF or EV3 motors with BOOST. However, LEGO plans to ...
Here's what the main board in the Move Hub looks like from the top:
The Move Hub includes the following hardware:
The two built in motors are fairly standard DC motors. They include optics in the early stage of the gearing for rotation counting.
There are two LB1836 motor drivers on the board. They are dual channel parts, so ...
As of the Powered Up app version 3.0, this is possible.
As of August 2018, this is not possible. However, TLG has stated that they plan to add more compatibility to the Powered Up system, and this will likely be available as a firmware update in the future:
Q. Will all different Powered Up components (Boost, WeDo, Train, etc)
be able to ...
M Motor (Powered Up/WeDo 2.0)
The M motor has a 2.2kΩ resistor between pins 5 and 6. Pin 6 is connected directly to pin 3.
I don't own any lights yet, but according to this post, they also use a 2.2kΩ resistor, but in this case it is between pins 5 and 3. This pulls ID 1 to ground. Here's the full circuit diagram:
The measured ...
I've tried attaching one of the Powered up motors from the batmobile set (76112) This motor looks identical to me as the WeDo motor (although brickset and bricklink don't list them as identical at the time of this writing)
I could not get it to work, all profiles of the fixed build models complain that the external motor is not attached. The free build ...
Boost and the other Powered Up components (the new City trains, the app-controlled batmobile, and WeDo 2.0) are controlled via Bluetooth. Any environment that can send bluetooth commands can be used to control these components.
There is a github page which documents some of the reverse-engineering that has been done and it links to several third-party Boost/...
Since June 2019, this is possible. See here:
Look right at the bottom of the article.
The latest version of the Powered Up app (2.2.0) as well as the latest
version of the Boost app include new firmware for the Boost hub. After
this update it is possible to ...
If you prefer C#, there a new lib on the block: SharpBrick.PoweredUp. While the Boost hub and motors are missing, the protocol is implemented. Your use case should be two minor contributions away.
Full Disclaimer: I maintain the library. I do not have Boost Hardware but the protocol officially supports Boost Hub. Just some enums and types are missing.
All you should have to do is connect pins 1 and 2 between the two motors. One motor will have all six wires connected and serve as the primary in order to give the hub something that it can properly identify. The second motor can simply piggyback off of the primary and share control voltages that are meant for the primary motor. Essentially, you can leave ...
As far as I can tell, recordings from the tablet are the only way to use custom sounds at the moment. I imagine that the UI for a feature like this was deemed too complex for an app designed for children under 12. However, this should be easy to add to the app in a future update if there is demand for it.
One obvious workaround for this is to play the ...
V1.4.4 on Apple App Store state “support for mobile phones”, and it does install fine on iPhones. Finally.
V1.4.3 on the Google Play store also lists "support for mobile phones" in the "What's New" section and can be installed on my Samsung S7.
This should be possible. On my Android device, the Boost files are located at Android/data/com.lego.boost.boost/files. There are subdirectories there for each model (Cat, Guitar, Vernie, etc).
The CreativeCanvas directory stores the generic programs that you have created via the canvas. These are divided into themes and activities. A single activity would ...
Looking at this site:
It is in German but I think this picture:
is the important one.
After these settings you have a global value in the white program block.
While the Boost components use a different connectivity, there is potentially another way you can extend your EV3 set with the capabilities of Boost by having both communicate via Bluetooth.
Unfortunately, there are no standard LEGO-provided tools to do so, but the systems are open-ended enough that some people are working on it. For example, here is a ...
This is not possible at the moment. This could be enabled in a future firmware update, but I'm honestly not sure how this would work. The Move Hub has 4 possible outputs. Mapping those to the pair of outputs normally controlled by the current remote seems like it would be somewhat clunky or non-intuitive.
You can try our just released WeDo 2.0 Framework that should suppot Boost partially (full support will be added soon). It is open source and free for education (written in C#). You can find it by this link: https://github.com/btframework/WeDo
There really isn't any easy way to do this at the moment. I would suggest buying plugs and making a simple port splitter, but I don't think there's currently any place to purchase the parts.
The best you can do involves (permanently) splicing the wires of the two motors together, using a single plug for both of them. With only the M motors this shouldn't ...
It depends on which app you want to use. My impression is that the Boost app can work with one Boost hub, one Boost motor and one Boost color/distance sensor.
If you use the PoweredUp app, you can use WeDo sensors and WeDo motors as well. But you always have to set the ports explicitely and remember that the external ports on the Boost hub are ports C and D. ...