 | | | | | |
In lugnet.robotics.rcx, Kevin Karplus wrote:
> The Scratch Programming laguage (http://scratch.mit.edu) now includes
> blocks for controlling WeDo motors.
>
> Kevin Karplus
Thanks. From the description I get the impression you can use 1 motor and 1
sensor at a time. Can anyone confirm this?
Jetro
| | | | | | | | | | | | | | |
So far as I can see from the Scratch interface, there is control of
one motor, but no sensors. (There are sensors via the ScratchBoard,
but not through the WeDo interface.)
I don't have the WeDo hardware, so have not investigated further.
Kevin Karplus
| | | | | | | | | | | | | | | | |
In lugnet.robotics.rcx, Kevin Karplus wrote:
> So far as I can see from the Scratch interface, there is control of
> one motor, but no sensors. (There are sensors via the ScratchBoard,
> but not through the WeDo interface.)
>
> I don't have the WeDo hardware, so have not investigated further.
>
> Kevin Karplus
I saw a "WeDo 2 Puppet" project on the Scratch website that specifically
mentions the use of the tilt senso so I suppose it must be possible to use
sensors as well.
"The scratch project uses the tilt sensor to decide when they spin"
Jetro
| | | | | | | | | | | | | | | | |
> I saw a "WeDo 2 Puppet" project on the Scratch website that specifically
> mentions the use of the tilt senso so I suppose it must be possible to use
> sensors as well.
>
> "The scratch project uses the tilt sensor to decide when they spin"
>
> Jetro
You are correct---there is a tilt sensor and a distance sensor value
available in the sensor value block. These get shown even if the
motor blocks are not being shown, so I don't know why I missed them before.
The values are 0 if no WeDo sensors are connected to the computer.
Kevin Karplus
| | | | | | |
