|
|
 | | Re: The datalog
|
| (...) If only the RCX could read it's own data... Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 5-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | 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)
| | | | | Re: The datalog
|
| BTW, what does the datalog *store*? Numbers? Events? Anything? And what good is it for (besides the methods we've disscussed earlier)? --Tobias (...) (24 years ago, 4-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: The datalog
|
| (...) Each call to AddToDatalog() uses up one "point". Each point takes up 3 bytes of memory: a 1-byte code for the source of point (sensor, timer, etc), then a 2-byte value. 123456 is too big to fit into the log. This would either generate a (...) (24 years ago, 4-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: Scout poweroff time out?
|
| (...) thanks. Comments are always welcome....that's not saying that I'll implement everything that anyone suggests, but I certainly appreciate the feedback. NQC wouldn't have gotten this far without the suggestions of the user community. Dave (24 years ago, 4-Oct-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
|
