| |
Dave Baum wrote:
> In article <39DB70E7.432D2DEA@telia.com>, tobias.moller@telia.com
> wrote:
>
> > BTW, what does the datalog *store*? Numbers? Events? Anything?
>
>
> numbers. It can only log timers, sensors, variables, and the system
> watch. When a value is logged, its source is also logged. For example,
> AddToDatalog(Timer(1)) adds the current value of Timer 1 to the log and
> also stores that this entry came from timer 1.
>
> If you log anything other than the above named sources (for example a
> constant), the value is first moved to a temporary variable, then the
> variable is logged.
>
> You can use it for data collection experiments, or to let a robot create
> a "transcript" of what it does. Not really useful in isolation, but it
> does provide a nice way for the RCX to collect a bunch of data for
> future analysis by a host computer.
>
> Dave
>
> --
> reply to: dbaum at enteract dot com
If only the RCX could read it's own data...
Dean
--
Coin-Op's For Sale!: http://www.akasa.bc.ca/tfm/coin-op.html
Dean's Lego Workshop: http://www.akasa.bc.ca/tfm/lego_wr.html
Vancouver Lego Club: http://www.akasa.bc.ca/vlc
|
|
Message is in Reply To:
 | | Re: The datalog
|
| (...) numbers. It can only log timers, sensors, variables, and the system watch. When a value is logged, its source is also logged. For example, AddToDatalog(Timer(1)) adds the current value of Timer 1 to the log and also stores that this entry came (...) (24 years ago, 5-Oct-00, to lugnet.robotics.rcx.nqc)
|
16 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
