Subject:
|
Re: The datalog
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Wed, 4 Oct 2000 18:03:19 GMT
|
Reply-To:
|
tobias.moller@telia.ANTISPAMcom
|
Viewed:
|
2068 times
|
| |
|
|
BTW, what does the datalog *store*? Numbers? Events? Anything?
And what good is it for (besides the methods we've disscussed earlier)?
--Tobias
Dave Baum wrote:
>
> In article <39DA1F0C.E321A6EE@akasa.bc.ca>, Dean Husby
> <nntp@akasa.bc.ca> wrote:
>
> >
> > 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 like 4 or 123456 equal as a single entry?
>
> 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
> compiler error for constant overflow, or just be truncated to a 16 bit
> signed value (-7616).
>
> >
> > One last issue, with the RCX you can set up the IR port as a serial
> > protocol. 2400 baud etc... But I don't see any way of receiving this info
> > with another RCX. Is this for RCX -> PC only?
>
>
> I couldn't find any way to Rx either. It still could be useful in
> RCX-RCX communication, though, provided you use the default serial and
> packet settings. This allows you to create a custom RCX packet (using
> the normal RCX bytecodes), so you could remotely cause the other RCX to
> do just about anything. Send it a "motor on" packet to turn on motors,
> etc. More flexible than the basic "message" communication.
>
> Dave
>
> --
> reply to: dbaum at enteract dot com
|
|
Message has 2 Replies:
 | | 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
|
| (...) 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)
|
Message is in Reply To:
| | 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)
|
16 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
