 | | Re: datalog viewer in RcxCC
|
|
Dave Baum wrote in message ... (...) Probably? Didn't you make NQC? (^: I tried the above. I got an error: Error: Couldn't open file log.txt. Any ideas? Iain -- tokama (URL) UIN 5362826 AIM Linjerflyg h e n d r y j r AT o x f o r d DOT n e t (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 released
|
|
(...) I take that back. It's fixed now. (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 released
|
|
(...) Linux binaries now at (URL), in .tar.gz and binary RPM format. (I've got to fix some stuff in the spec file, and then I'll post the SRPM too -- gimme a couple of days.) (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: datalog viewer in RcxCC
|
|
(...) You can probably use NQC to read the values into a text file. Try: nqc -datalog >log.txt The -datalog option will grab the datalog as raw valus, -datalog_full will add the 'sources' into the listing. I'm not sure why RcxCC lists the wrong (...) (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: datalog viewer in RcxCC
|
|
Jeff Canar wrote in message <38aff0b1.63663228@l...et.com>... (...) <snip> I have had similar oddities using RcxCC for retrieving DataLog values. For example when I am pulling something in from Sensor 1, it may tell me this: Sensor 1: 35 Sensor 1: (...) (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
