| |
In lugnet.robotics.rcx.nqc, Dave Baum wrote:
> If you just want to transfer the datalog and put it in a text file you
> can use the nqc command:
>
> nqc -datalog
>
> This will upload the datalog and print it to stdout. Use your shell I/O
> redirection to put it in a file...
>
> nqc -datalog >my.log
>
> Normally only the data values are displayed, but if you also want to see
> what source the values came from use -datalog_full instead of -datalog.
>
> As with any nqc commands, use the -S option to specify a different
> serial port (or USB device).
>
> AFAIK, BricxCC has a nice interface for datalogs, so that's probably the
> best way to go if you just want to view the log, but if you want to
> script it, then the nqc command should work fine.
Of course. How silly of me to forget that NQC, the most influential piece of
RCX software ever written, has built-in support for the datalog. I use NQC for
the majority of my projects, and have found it to be the quickest way to develop
RCX programs. Thank you (many times over) Dave.
- Chris.
|
|
Message has 1 Reply:
 | | Re: write files
|
| (...) I'm glad that you (and others) have found NQC to be useful. Most people don't use NQC for anything beyond compiling and downloading programs, but it has lots of options for interacting with the RCX (such as -datalog, -run, and -raw). Type "nqc (...) (21 years ago, 3-Oct-03, to lugnet.robotics.rcx.nqc)
|
Message is in Reply To:
| | Re: write files
|
| (...) If you just want to transfer the datalog and put it in a text file you can use the nqc command: nqc -datalog This will upload the datalog and print it to stdout. Use your shell I/O redirection to put it in a file... nqc -datalog >my.log (...) (21 years ago, 1-Oct-03, to lugnet.robotics.rcx.nqc)
|
8 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
|
|
|
|
