Does anyone try SCRATCH WeDo function on Ubuntu 11.04?
I use 'lsusb' command to check motor and sensors devices, and it found.
But it can not work on SCRATCH.
It works fine on Windows XP.
I plugged motor and distance sensor to hub, then I plugged hub to PC USB port.
Inside the SCRATCH program, I can not control the motor.
And I can not read any value from distance sensor either.
The same process worked fine on Windows SCRATCH.
The latest installer, Scratch_184.108.40.206-0ubuntu5_i386.deb, doesn't have WeDoPlugin.
So you need get it from OLPC XO version.
http://web.media.mit.edu/~jmaloney/scra … atch-16.xo
You can extract Scratch-16.xo as a ZIP file.
Then try the following commands.
sudo cp WeDoPlugin-disabled /usr/lib/scratch/Plugins/WeDoPlugin
I've got a Wedo set and have install Scratch 1.4 on OpenSuse 12.2. I can't get the motors to work. They work on a Raspberry Pi but Scratch on the Pi was so unstable I decided to move to linux. My linux box sees the USB connection to motors and is duly reported by dmsg and lsusb commands. Scratch shows block but no motion. I installed the XO WedoPlugin as shown above but no go. I also tried the new Beta 2.0 web version of Scratch and no motors also. What should I try next?
scratch: /usr/bin/scratch /usr/lib/scratch /usr/bin/X11/scratch /usr/share/scratch /usr/share/man/man1/scratch.1.gz
CameraPlugin Mpeg3Plugin UnicodePlugin vm-sound-ALSA vm-sound-OSS WeDoPlugin MIDIPlugin ScratchPlugin vm-display-X11 vm-sound-null vm-sound-pulse
Thanks. It seems OK.
I'd like to make sure that your linux box is based on x86 architecture. Is it correct?
And could you get a tilt or a distance sensor value?
If your sensor is working, the cause might be low electric current of the USB port.
In this case, you should use self powered hub to provide much current.
Yes, I have a x86 architecture box. The sensors are not working but computer sees the Lego USB hub/device. I moved the RPi just to make sure Wedo was working, and it still is.
Here's a little output from dmesg:
USB Hub V1.00] on usb-0000:00:1d.2-1/input0
[181615.528070] hub 4-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
[181615.528079] usb 4-1: USB disconnect, device number 4
[181615.768044] usb 4-1: new low-speed USB device number 5 using uhci_hcd
[181615.936120] usb 4-1: New USB device found, idVendor=0694, idProduct=0003
[181615.936127] usb 4-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[181615.936131] usb 4-1: Product: LEGO USB Hub V1.00
[181615.956491] generic-usb 0003:0694:0003.0043: hiddev0,hidraw2: USB HID v1.10 Device [LEGO USB Hub V1.00] on usb-0000:00:1d.2-1/input0
[182585.456068] usb 4-1: USB disconnect, device number 5
[182602.700042] usb 4-2: new low-speed USB device number 6 using uhci_hcd
[182602.868994] usb 4-2: New USB device found, idVendor=0694, idProduct=0003
[182602.869001] usb 4-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[182602.869005] usb 4-2: Product: LEGO USB Hub V1.00
[182602.887207] generic-usb 0003:0694:0003.0044: hiddev0,hidraw2: USB HID v1.10 Device [LEGO USB Hub V1.00] on usb-0000:00:1d.2-2/input0
Umm, it's strange. I have no idea.
You might check and modify installWeDoRules.sh by the location of rules.d for your environment.
if [ -d /etc/udev/rules.d ] ; then
cp 45-lego-wedo.rules /etc/udev/rules.d
chmod 666 /etc/udev/rules.d/45-lego-wedo.rules
if [ -d /lib/udev/rules.d ] ; then
cp 45-lego-wedo.rules /lib/udev/rules.d
chmod 666 /lib/udev/rules.d/45-lego-wedo.rules
Last edited by abee (2013-02-26 06:29:17)