|
|
 | | Re: VB Upload Problem
|
| 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 (...) (24 years ago, 26-Jun-00, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: VB Upload Problem
|
| (...) 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 (...) (24 years ago, 24-Jun-00, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: VB Upload Problem
|
| 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 (...) (24 years ago, 24-Jun-00, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: VB Upload Problem
|
| (...) But I wasn't logging variables... and I never have... I was logging sensor values... and the values were certainly not things like 9, 0, 1, 3, ... (what showed up for values) but were more like 16, 23, 32... (which show up 70 or so values into (...) (24 years ago, 24-Jun-00, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: VB Upload Problem
|
| (...) Variables are 'type' 0, but there's a disagreement between NQC and VB about which var is in the log. I haven't heard of any problems with NQC in this respect, but I can test it out a bit and see. ... (...) At the bytecode level, the datalog is (...) (24 years ago, 24-Jun-00, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
|
