Subject:
|
Re: The Scout brick: smart or dumb? (was: Robotics Discovery Set)
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Tue, 7 Sep 1999 21:57:52 GMT
|
Viewed:
|
711 times
|
| |
|
|
That really helps a lot! Now I know what the Scout can do. I'm still not sure
if I'll buy one, but it certainly makes it more likely.
To sum up (for others) the Scout user will:
- select an initial type of movement: none, straight, zigzag, circle CW,
circle CCW, fwd/reverse continuous loop on A, fwd/reverse continuous loop on B,
fwd/reverse continuous loop on A and B, with 3 available speeds for each except
"nothing".
- select a reaction to the touch sensor: no reaction, reverse, avoid [1],
waitfor [2], and brake, with 3 available speeds for each except "no reaction"
[3]
- select a reaction to light: no reaction, reverse, seek light [4], seek dark
[5], waitfor [6], brake, with 3 available speeds for each except "no reaction"
[3].
- select an "effect": none, bug, alarm, random, geiger (as you described, I
won't bother repeating)
- Robert Munafo http://www.mrob.com/
LEGO: TC+++(8480) SW++ #+ S-- LS++ Hsp M+ A@ LM++ YB64m IC13
[1] presumably this means "reverse motor A if touch sensor 1 or reverse motor B
if sensor 2"
[2] presumably this means "stop until sensor released, then resume previous
type of motion"
[3] speed isn't applicable to "brake" but perhaps you mean that it controls how
long it waits until braking.
[4] presumably this means "stop motors if light is bright"
[5] presumably this means "stop motors if light is dark"
[6] presumably this means "stop motors until light returns to previous level"
In lugnet.robotics, Robert Eddings writes:
> [...] There are four MOTION actions but the "circle" command can be
> set to clockwise or counterclockwise. The "loop" command (runs motors
> A and B back and forth in different patterns) can be set to "loop A",
> "loop B", or "loop AB". Under the LIGHT actions, the "seek" command
> can be set to
> "seek light" or "seek dark". Also, all three actions can be set to do
> nothing so that adds to the list of commands in a way. Therefore within
> the 12 commands, it could be said that there are actually 19 commands.
> This makes the combinations so far of 8 x 5 x 6 = 240.
>
> Furthermore, the timing of all actions can be set universally to execute
> slow, medium or fast. So, not counting "off", that is 7 x 4 x 6 = 168 x
> 3 = 504. Add back in the 3 "off" commands and we are at 507, so far.
>
> Now, on top of all of this, there are 4 "special effects" that can be
> set that effect the whole system. So the 5 added options would be "no
> special effects", "bug mode" (bug sounds and at least two additional
> random behaviors), "alarm sounds" (different sounds for movement and
> sensors), "random movements" (at least two different movements in random
> order and timing), and "geiger counter" (different sounds for movement
> and sensors). So not counting the the "off" commands, that is 504 x (at
> least) 6 = 3024. This must be close to how TLG figures it.
> [...]
|
|
Message has 1 Reply:
Message is in Reply To:
10 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Robotics
|
|
|
|
|
|
