The original WeDo Resource Set introduced 1st-3rd-grade kids to the world of robotics. The one thing I did not like about it, is that the robot had to stay connected, by wire, to the computer. With the introduction of WeDo 2.0 Core Set, Bluetooth frees the robot from the computer. It is also more versatile with the use of tablets, as well as computers.
For those of you who might be considering LEGO's WeDo 2.0 Core Set, you will find that it is a good platform for Grades K-4 and a good introduction to robotics for the older students who are starting to explore the world of robotics. It is a natural lead into LEGO Mindstorms robotics.
So, the Brics~2~Bots engineers have been tinkering with the WeDo 2.0 set and have made some interesting discoveries.
If you haven’t seen the Smarthub yet, it does not have a display screen or speakers like the NXT or EV3 Controllers. However, it does have programming/coding blocks for both sound and display; the sound is played and the display is seen through your tablet/computer.
As you may or may not know, the Smarthub has only 2 Input/Outs for motors and/or sensors. So it really doesn’t matter which Input/Output you use.
When 2 motors are connected 1 Smarthub, both motors are programmed by the same motor block. Also, when 2 of the same sensors are connected, both sensors are programmed by the same sensor block and either one will respond.
Now, if 3 SmartHubs (the Max. is 3 and you can edit and label each by pressing the hub icon) are paired with/connected to one device (tablet/computer), one or simulataneous executed program strings will control all 3 Smarthubs at the smae time. Any sensor from any of the Smarthubs can receive input and all motors respond. So one tablet/computer can be paired with Smarthub A and Smarthub B at the same time running the same program string(s). This is a handy titbit when testing the effectiveness of a design model to another using the exact same program string - a side by side comparison, which we did when we compared a Pulley driven vehicle to a Differential Gearing driven vehicle.
In order to control two or more Smarthub models separately, you will need two or more devices (tablets/computers). Each model will be paired with one device and the program strings on that device will only affect the model paired with that device.
We wanted to know the relationship between the number (seconds) input for motors to actual motor rotations, so we did some tests:
How does the number (seconds) input relate to actual motor rotation with the motor using a Power of 1?
We built two cars, a pulley driven car and a gearing driven car.
Some useful info:
Pulley driven car - 1:1 ratio of Wedge Belt Wheel to Wedge Belt Wheel
0 seconds = .65 rotation
1 second = 1.75 rotations
Gearing driven car - 1:1 ration of 20 Bevel to 20 Double Bevel
0 seconds = .75 rotation
1 second = 2.25 rotations
( you would think that at 0 seconds it would not move at all!)
Note: When inputting the power of a motor, the maximum power is about 9-10, even though you can input a larger number.
Next, we did a test comparison on the performance of the same pulley driven car to the gearing car, comparing the distance traveled using two extreme Power settings of 1 and 9. The cars were tested for various durations (seconds) inputs. Our hypothesis was that the gearing driven car would perform better.
And the results are in….
As you can see from the data, the pulley driven car did not travel as far as the gearing driven car.
Our conclusion: The gearing driven car, based on the observations, performances better by going faster, further, and straighter than the pulley driven car. We believe the gearing has more clutch/grip so its performance is more accurate and consistent; whereas the pulley driven system might tend to slip, particular with wear the rubber band will stretch slightly resulting in slippage. Also, with the pulley driven system, one has to make sure the car/vehicle is balanced from side to side, otherwise it will have a tendency to drift to the weighted side of the vehicle. We also found that the tension of the rubber band has to be exact and after some use it loses its tension and will cause slippage; dierect connection to the motor or use of gearing is definitely better.
What else did we discover?
We do know we can have 2 motors connected to 1 Smarthub and they will both be controlled by a single Move this/That Way or Motor On For block, but you can control them individually. In the LEGO Education WeDo 2.0 Curriculum Pack it shows you how by using the Move this/That Way (which runs continuously until indicated to stop) block, but you can also use the Motor On For block. Click/Press the block until the Lablelling Panel of 6 squares appears above it. Each square has a color assigned to itfor each motor - up to 6 motors. Tap the Labelling Panel to change the color and assign that motor on the particular Smarthub.
This means that you can individually select up to 6 motors on the 3 Smarthubs paired with (connected) and programmed by one program string or parallel program strings from one device (tablet/computer). You can select which motors to control on which Smarthubs, but remember also an unselected motor block will control all motors at that point in the program. However, multiple sensors can not be "selected" (if a sensor on one Smarthub detects, then the reponse causes all Smarthubs to respond and this is where motor selection can be helpful to control wuich motors you want to respond. Sound and displays are through the device so it happens exactly where it is in the program string. Imagine, you can turn on and off any motor on any Smarthub in your project - Awesomeness!