Subject:
|
Re: Minor bug in DCP sound sensor support
|
Newsgroups:
|
lugnet.robotics.rcx.robolab
|
Date:
|
Thu, 13 Jul 2000 15:39:43 GMT
|
Viewed:
|
5144 times
|
| |
|
|
Yeah, I noticed this in China at one of the first workshops there... and of
course I hadn't tested the demo beforehand, so I had to quickly rewrite it with
forks. This was back around
April 15. http://members.aol.com/sowtime444/China/demos.html :)
-Ben
In lugnet.robotics.rcx.robolab, Richard Hamilton writes:
> Robolab 2.0 and 2.01 programmer extras has a bug in the DCP sound sensor
> construct "Wait for increasing sound". This construct sets the sensor type to
> touch when it should set the sensor type to light. The other sound sensor
> constructs "Wait for decreasing sound", "Loop while sound is less than", "Loop
> while sound is greater than", and "Sound level sensor fork" all set the sensor
> type correctly. It is possible to avoid the "Wait for increasing sound"
> construct by one or more of the other sound sensor constructs.
>
> This bug has been reported to Lego Dacta Support.
|
|
Message is in Reply To:
 | | Minor bug in DCP sound sensor support
|
| Robolab 2.0 and 2.01 programmer extras has a bug in the DCP sound sensor construct "Wait for increasing sound". This construct sets the sensor type to touch when it should set the sensor type to light. The other sound sensor constructs "Wait for (...) (24 years ago, 5-Jul-00, to lugnet.robotics.rcx.robolab)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
