Subject:
|
Re: Problems with datalog
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Sat, 26 Aug 2000 03:17:52 GMT
|
Viewed:
|
1864 times
|
| |
|
|
In article <Fzu6DD.7o0@lugnet.com>, "Michael Andersen"
<roboduck@pobox.com> wrote:
>
> Looking at your NQC program, you seem to be logging the IR message buffer
> directly, but that's not possible.
>
> A careful examination of the DataLogNext command in the beta SDK
> documentation
> shows that the command is quite limited and that you can only log
> (global)
> variables, timers, sensor values and the watch/clock. If you copy the
> message
> to a (global) variable and log that value, my guess is that it'll work.
Unless I bungled the code, NQC should handle this ok. Old versions of
NQC would always move from a restricted datalog source into a temp
variable. With the new firmware, there's the added complexity that the
temp can't be a local var, and I haven't optimized things yet, so NQC
will do the following:
move the message into a local var
move the local var into a global var
log the global var
free the global and local vars for later use
If I get a change I'll try to clean this up so it skips the local var
step....that was just a consequence of reusing the general purpose "move
restricted source into something that can be manipulated" code, in which
case a local var is almost always the right destination.
Dave
--
reply to: dbaum at enteract dot com
|
|
Message is in Reply To:
 | | Re: Problems with datalog
|
| (...) directly, but that's not possible. A careful examination of the DataLogNext command in the beta SDK documentation shows that the command is quite limited and that you can only log (global) variables, timers, sensor values and the watch/clock. (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
9 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
