 | | 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)
|
| |
| | datalog viewer in RcxCC
|
|
Wrote a program to log light levels every ten minutes and store those levels in the datalog. I wrote the program to use, and connected the sensor to, SENSOR_3. Everything works fine. My question is: Why does the datalog viewer in RcxCC report (...) (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | MacNQC 2.1 in beta test
|
|
MacNQC 2.1 b1 in public beta: (URL) are a number of minor improvements - most notably an update to the latest NQC compiler (2.1 r1). This adds Scout support among other things. Dave (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 released
|
|
(...) The MPW version of NQC 2.1 is out now. The GUI based one (MacNQC) will probably be in beta very soon - there are some other things I need to wrap up since version 2.1 is in threory going to be localizable for German (and other languages). Dave (...) (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 released
|
|
(...) _good_ stuff! thanks, DLC (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 released
|
|
(...) (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC 2.1 released
|
|
NQC 2.1 has been released - (URL) features (from 2.0) include the switch statement, fast firmware download, and preliminary Scout support. For more information, refer to the README - (URL) Baum (25 years ago, 20-Feb-00, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | Re: size of programs
|
|
If you have a palm pilot, you can get the info you want using BrickRemote. Mike Kory Dave Baum <dbaum@spambgoneenteract.com> wrote in message news:dbaum-532A81.01...net.com... (...) (25 years ago, 17-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: size of programs
|
|
(...) Good idea - also works well for MacNQC. I'll add it for the upcoming 2.1 release. Dave (25 years ago, 16-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: size of programs
|
|
Dave, How about doing the total and including it in the code listing? That way those of us that use RcxCC will be able to see it for more than a flash on the screen. (The download is only visable for a short time and then the window closes.) (...) (25 years ago, 15-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: size of programs
|
|
Not at all, that would be EXTREMELY handy. Something for this release? or later down the road? (...) (25 years ago, 15-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: size of programs
|
|
(...) As mentioned in another post you can add up the sizes of each task/sub in the listing. I know this is tedious. I was considering adding a diagnostic message after download that would show the total number of bytes downloaded. Anyone have (...) (25 years ago, 15-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: size of programs
|
|
If you use RcxCC, look at the code listing. At the bottom of each task you will find the address of the last OP code. Just total them up and you have the size. If you don't have RcxCC, just use the -L option to generate the code listing. --- DonC (...) (25 years ago, 14-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | size of programs
|
|
Hi Is there an easy way of calculating the exact size of a program in bytes (for NQC). I would like to know how much I've got available for the datalog when the program is downloaded. The "dots" in the download-process, do they signify anything, or (...) (25 years ago, 14-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
One other thing ... when I first made a simple program to demonstrate the problem, I used a lowercase d for my symbol and got this error: # Error: parse error File "rcx.nqh" ; line 118 # void SetDirection(const int o, const int d) { asm { 0xe1, (o) (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
Thanks for the quick response. "It's fixed in the next release, which is due in a week or so" qualifies for excellent support, IMHO. :) My workaround is a REXX exec rewritting a small header file on the fly before each compile. -- Mark Haye, haye (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Having trouble with -D option
|
|
Yes, I noticed that too, but I'm trying to program multiple RCXs with the same source, and the symbol is meant to represent the RCX's id, so it must have multiple values. Thanks anyway for the quick response. -- Mark Haye, haye (at) us (dot) ibm (...) (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: scout.nqh no longer necessary?
|
|
(...) Correct. Initially (2.1 b1) I put the Scout support in a separate include file because I wasn't ready to merge all of the changes together. As of b2, the compiler's built-in system include file includes RCX, Cybermaster, and Scout APIs. Dave (25 years ago, 12-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: scout.nqh no longer necessary?
|
|
(...) Yes, this is true as of 2.1.b2. (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | scout.nqh no longer necessary?
|
|
It looks like Scout programs no longer need `#include "scout.nqh"', and the file has been removed from the NQC beta distribution. Is that correct? I've been confusing someone new to NQC because I didn't realize this :( --Ben (25 years ago, 11-Feb-00, to lugnet.robotics.rcx.nqc)
|
