Subject:
|
Re: best way to ignore sensors??
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sun, 12 Sep 2004 11:17:53 GMT
|
Viewed:
|
1070 times
|
| |
|
|
Mr S wrote:
> This sounds like you have a sensor monitor running
> continuously, and there is code in the monitor.
> Perhaps if you set up the sensor monitor to only
> modify a variable rather than cause the RCX to do
> things, then your other code could monitor the
> variable when and if it needs to, acting on the value
> of the variable in relation to your other monitor code
> etc.
>
> Cheers
>
>
>
This is what I interpreted it to mean. I would advise him to use a
language like NQC, or another code based programmer. The GUI at last
view does not containt much, if any support for variables at all.
It could be done in the GUI by having a very simple state machine - so
in one state, it is looping - and polling for the sensor, and then once
a condition is met, it goes into another loop. This could all be in a
bigger loop, so that when a codition was met, it could return back to
the first loop. This would require no variables - just a good idea of
what the conditions are, and using loops and polling instead of
tasks/interrupts.
Danny
http://orionrobots.co.uk
All about building robots with Inspiration - Education - Discussion -
Competition.
|
|
Message is in Reply To:
 | | Re: best way to ignore sensors??
|
| (...) This sounds like you have a sensor monitor running continuously, and there is code in the monitor. Perhaps if you set up the sensor monitor to only modify a variable rather than cause the RCX to do things, then your other code could monitor (...) (20 years ago, 3-Sep-04, to lugnet.robotics)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
