 | | 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)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) Yes, I'll try to do that when I have some time... (...) That's not too bad... heh heh. I'm just shocked at how little RAM there is for programing... Maybe the 'way' I program is memory intensive. I can see an art to programing the scout (...) (24 years ago, 3-Oct-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: The datalog
|
|
(...) After looking over the docs again, I'm fairly certain it can't be done (or at the very least isn't documented). If anyone finds out how to do it, let me know and I'll add support to NQC. Dave (24 years ago, 3-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) The SetSleepTime() and SleepNow() thing was just sloppiness on my part when reorganizing the NQC API file. Those opcodes are clearly documented in the Scout SDK. I don't think we have to hunt around for undocumented features - just verify that (...) (24 years ago, 3-Oct-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) What other features will work? The BatteryLevel() one? I think we need to have a look at the rcx2 commands and see what's working for the Scout. Also, what does the Scout API include with the program? I know in the RCX it turns all motor ports (...) (24 years ago, 2-Oct-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: The datalog
|
|
I heard it somwhere too, so I assumed it could be done, however, I haven't downloaded the new firmware, so I don't know. --Tobias (...) (24 years ago, 2-Oct-00, to lugnet.robotics.rcx.nqc)
|
