|
|
 | | Re: The Datalog
|
| Sorry, Dean - now I got your point. There is indeed no way to read the contents of the datalog. What about storing the data (e.g. for path information, maps, etc.) into an ARRAY instead of the datalog? With RIS2.0 and the latest NQC version you have (...) (24 years ago, 10-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: The Datalog
|
| (...) Please don't get any of us wrong, the DataLog is a WONDERFUL feature. It makes for the greatest use of the brick as a data gatherer... The ONLY gripe any of us have is that the RCX it's self cannot read back the DataLog... If we could we could (...) (24 years ago, 9-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | The Datalog
|
| To my mind, the datalog is a good feature, since it helps with debugging or adjusting sensors. I found very useful for analyzing light sensor values, measured during movements (e.g. proximity detection). Another useful application was measuring the (...) (24 years ago, 9-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: The datalog
|
| (...) Series of measurements. I've used it to measure light sensor values while doing a 360 degree turn next to a candle (disappointing, the candle made hardly a dent), and to measure raw values for touch sensors while pushing them slowly, 1/100mm (...) (24 years ago, 5-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | 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)
| | | | | Re: The datalog
|
| (...) Dave, I have a question about the datalog. In the manual you state that the createdatalog function creates a datalog of x many points. How much is a point? Is that how many unique entries can be made or an overall 'byte' amount? Is a value (...) (24 years ago, 3-Oct-00, to lugnet.robotics.rcx.nqc)
|
|
