| |
You could always check how big your datalog is by uploading the first point of
the datalog in VB. The third element of the first point (point 0) is the size
of the datalog. Throw that in a databox and see what it gives you.
I would agree that VB probably isn't clearing the datalog. I always use NQC
for this. I created a scanner using a NQC program to create the datalog and
control the robot, and a VB program to get the datalog and turn it into
pixels. Of course all of this looped.
Nate
In lugnet.robotics, Dave Baum writes:
> In article <Fwo5xB.M16@lugnet.com>, "Ben Erwin" <ben@alum.mit.edu>
> wrote:
>
> > ok, so i'm getting a little closer to answering my own question, but i'm
> > still
> > stuck.
> >
> > if i write a new robolab program to take 10 points of light data and then
> > upload it with VB, those 10 points get put into slots 10-20 in the
> > datalog,
> > and points 1-10 in the datalog remain intact for some reason. Also,
> > these
> > light sensor values are labeled "variable 23" -- but i wouldn't put it
> > past
> > chris to have called the light sensor 'variable 23' in robolab for who
> > knows
> > what reason. i'll have to ask him.
>
>
> I think chris is putting some other info in the datalog. I poked at
> this briefly when using an early version of Robolab 2.0, but I don't
> recall the exact details. I think it comes from Robolab trying to use
> the datalog to record multiple channels of info, so it add in values
> describing how the datalog is used.
>
> I be the reason he logs a variable is that he really wants to put a
> constant into the log, but that isn't allowed, so you move the constant
> into a scratch variable, then log the var.
>
> > anyway, when i then go and download a data-taking program for light and
> > temp
> > data (the one posted the previous message) and then upload THAT with VB
> > or
> > NQC, that data is tacked on to the VERY END of the datalog, and looks
> > pretty
> > normal (with the addition of a .ClearTimer 0, which I had forgotten).
>
> My guess is that the VB call to SetDatalog isn't doing anything. Try
> running this brief NQC program - it should erase the datalog completely:
>
> task main()
> {
> CreateDatalog(0);
> }
>
> If the datalog symbols on the LCD are still lit/flashing, then for some
> mysterious reason your RCX won't erase its datalog.
>
> Then try your VB program. If the datalog doesn't exist (no LCD symbols
> lit/flashing, and an upload reveals no data), then the VB call is hosed.
> I took a brief look at your code and I think it should work, but I'm not
> much of a VB or Spirit.ocx expert.
>
> Dave
>
> --
> reply to: dbaum at enteract dot com
|
|
Message has 1 Reply:
Message is in Reply To:
11 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
|
|
|
|
