 | | Problems with datalog —Ryan J. Schave
|
| | | I wrote a simple program that adds any messages received to the datalog. It also beeps after it logs each message so that I know it is working. The CreateDatalog() command doesn't seem to be working. It seems pretty simple. What am I missing? The (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | |
| | | | | Re: Problems with datalog —Dave Baum
|
| | | | (...) What version of the firmware are you using (what's the filename of the firmware file)? I think some versions of early 2.0 firmware didn't support creating the datalog from within a program. Also, what version of NQC are you using...I don't (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: Problems with datalog —Ryan J. Schave
|
| | | | (...) Dave, I'm using NQC 2.2 b1. The firmware filename is firm0328.lgo, the version that came with Vision Command. Ryan -- (URL) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: Problems with datalog —Michael Andersen
|
| | | | (...) directly, but that's not possible. A careful examination of the DataLogNext command in the beta SDK documentation shows that the command is quite limited and that you can only log (global) variables, timers, sensor values and the watch/clock. (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: Problems with datalog —Ryan J. Schave
|
| | | | | (...) It is possible. If the datalog is created from outside the program (i.e. RCXcc) then my program correctly logs the IR messages. The problem I'm having is that I cannot get the RCX to create the datalog from within the program. From Dave's (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | | |
| | | | | | | Re: Problems with datalog —Dean Husby
|
| | | | | | (...) Have you tried putting in a Wait command after creating the Datalog and before you start using it? It must take a few milliseconds to set up. Just my .001 cents after taxes... Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | | | |
| | | | | | | | Problems Solved(WAS Re: Problems with datalog) —Ryan J. Schave
|
| | | | | | (...) before (...) I just tried using the Wait() command for up to 5 seconds. Still didn't work. I remember reading that the Vision Command required the new firmware. I assumed that VC d/l'd the new firmware automatically. I didn't remember waiting (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | | | |
| | | | | | | | Re: Problems Solved(WAS Re: Problems with datalog) —Dean Husby
|
| | | | | | (...) Ya, VC must have gone to press before they asked us to help with the bugs... 0321 was really buggy. I'm glad you got it worked out. Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 26-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | | | |
| | | | | | Re: Problems with datalog —Dave Baum
|
| | | | (...) Unless I bungled the code, NQC should handle this ok. Old versions of NQC would always move from a restricted datalog source into a temp variable. With the new firmware, there's the added complexity that the temp can't be a local var, and I (...) (24 years ago, 26-Aug-00, to lugnet.robotics.rcx.nqc)
|
| | | | |
