Did you allow the hub to install correctly - maybe double check you get an extra entry in the Device Manager ‘Human Interface Devices’ section when the hub is plugged in. eglesby - It works ok on Windows 7 for me under Chrome. Use the extension blocks to switch the motors on/off and to react to a change in distance or tilt values from the sensor. Then plug in a motor and either a distance/tilt sensor into the Wedo. 2) Create a new project, hold down the shift key and click on ‘More Blocks’ > add an extension > wedo 3) Install the plugin when prompted and then ‘accept’ the browser prompt to give Chrome permission to use the plugin.
cwk_jack_85 - 1) Make sure you are using Chrome, some other browser's don't work at present. It wouldn't be too difficult to modify the Wedo plugin to work with NXT if/when the plugin source/API is released.ĪlexZOnder - You don't need to buy any of the Lego Wedo software at all - you just need the Lego Wedo hardware kit (hub and sensors) and Scratch (which is free of course!). In the past I've written my own experimental software to talk with Wedo, NXT (via bluetooth serial), RCX and even Model B. in schools) to have a proper neat embedded plugin like the Wedo plugin. You can actually already do this in Scratch/Snap! via Python trickery but it would be much cleaner/easier for non-technical users (e.g. But the advantage of this route is that all the NXT sensors will then simply plug into the NXT directly and all the electronics will work as designed. From the Scratch point of view a NXT connected via a bluetooth serial link is effectively no different to a Wedo connected via a USB cable, you just need a different plugin that can handle the communication with the Lego unit correctly. These are the ones I know about: // ID_Values //38-39 Tilt //99-102 Servo //176-179 Distance //203-204 Lights //228-231 None (default) //238-240 Motor M A better way to support other Lego sensors would be to generate, for instance, a similar NXT plugin. The Wedo identifies which sensor is connected via reading a simple fixed resistor potential divider value, so for a home made sensor you would just need to let the software (Scratch) accept another unique value as valid (ie select a value not already used by Lego sensors and allow that to work as well).
However I would love Scratch to have a ‘home made sensor’ setting that allows a home-brew sensor to connect to Wedo - this is certainly possible. Purely because you would be constantly fighting the electronics inside the Wedo that auto-identifies the power function sensors/motors. The Wedo plugin probably would not be the best way to add extra (non power function) Lego sensors and actutaors.
0 kommentar(er)
