This can be done without a caster wheel as well:
Start out with a three wheeled vehicle, with two wheels in the front and one smaller wheel with less traction than the front wheels in the back. All wheels need to be fixed.
One of the front wheels is attached to the motor. This might need to have some gearing to get an appropriate speed.
The other front ...
Let's take a look. The first step to disassembling the motor is removing the small Philips screw on the bottom:
Now there are a pair of gray tabs in the back white section that we need to release. I found it easiest to cut them down with a knife. Once those are free, the white section slides backwards away from the motor. Try to do this gently, as there are ...
In WeDo 2.0 app "LEGO® Education WeDo 2.0" there is a complete project 12. Steer that is exactly about that
When it drives forward it goes in straight line, when it drives backward it then turns to one side.
There is full build instruction in the app.
I've also added distance sensor and made it fully autonomous - whenever it sees obstacle it goes back, ...
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 ...
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 just created a Node.js library that supports reading and writing to the Lego WeDo kit: https://www.npmjs.com/package/wedo-support
> npm install --save wedo-support
const WeDo = require('wedo-support');
const wd = new WeDo.WeDo();
// Activating the first motor full forward:
wd.motorA = 100;
// Activating the second motor half speed/...
It is possible to drive the WeDo from Python on a Mac, without a kext. I've only tested motors since I don't (yet) have the other sensors. You need to access the USB HID device directly. There are a couple of prerequisites to install:
cython-hidapi, which itself depends on
hidapi; homebrew can install that for you.
You'll likely want ...
I designed some WeDo 2.0 models that can drive and steer using just one motor.
This one uses a system of gears to alternately drive the left or right wheel of a differential drive robot, depending on the turning direction of the motor.
You can find the complete building and programming instructions here:
You can use WeDo with MIT Scratch 1.4 according to http://info.scratch.mit.edu/WeDo, and Scratch runs on Linux- and this thread https://lists.launchpad.net/scratch/msg00269.html indicates that the Linux Scratch does work with WeDo.
According to the WeDo 2.0 FAQ
Is this a new plug system?
Yes, this is the new LEGO Power Functions plug that has been optimized also to meet potential future needs.
What does that mean for the existing plug systems on other Power Function and MINDSTORMS products? Will they also be changed?
Yes, eventually we will convert to the new plug ...
I've just discover that the WEDO USB Hub just send to the motors 5V instead of 9V, so that's stopping me for doing a lot of stuff. Does anybody know how to add a separate source power and only send and read data from the USB Hub?
Here's what I found researching your issue:
It seems that the issue with Mac OS X's kernel claiming HID USB devices before libusb does is a known issue since OSX 10.5 (see here).
Libusb has no functionality to alter this behavior, so it would be up to the WeDoMore developers to use an alternative way to utilize USB on the Mac if they want to build in this ...