 | | Re: C$ - Code Only
|
|
(...) I am admittedly biased toward BrickOS; however, I am wondering if you attempted to free some memory in BrickOS by disabling features that you didn't need? If you are only going to run one program (whether single threaded or multi), you can (...) (21 years ago, 7-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: C$ - Code Only
|
|
(...) I think most people seriously underestimated how hard building the robot would be. The funny thing is, all of rtlToronto's events have the same general premise: Build a robot that does something. Second, if you can make the robot do it well, (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx)
|
| |
| | Re: C$ - Code Only
|
|
(...) NQC compiles not quite C code into LEGO firmware opcodes. You download the .rcx result, and LEGO firmware interprets the program. This makes it slow. QuiteC and brickOS both use H8 native C compilers that spit out H8 assembly code directly. (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: C$ - Code Only
|
|
(...) Forgive a clueless question here, but is QuiteC different than NotQuiteC? If so where can I learn more about it? Thanks! The oldest mention of the term "QuiteC" I could find on LUGNET was only 3 weeks ago but MAYBE I'm searching wrong? see (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: C$ - Code Only
|
|
(...) Folks who read rtlToronto can skip this part. I added it because I'm cross posting to robotics.rcx. For those who don't know, rtlToronto had a contest with robots playing Connect Four. Creating a robot for this is double faceted. Getting (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx)
|
| |
| | Re: QuiteC IR interfacing to lego firmware IR
|
|
(...) It is my conclusion that QuiteC is not receiving back to back IR bytes fast enough, and that characters are lost. Kevin (21 years ago, 5-Feb-04, to lugnet.robotics.rcx)
|
| |
| | RE: QuiteC IR interfacing to lego firmware IR
|
|
(...) Not knowing EXACTLY what is going on with QuiteC, I can only offer some suggestions.... The 0x55 to 0x5D might just be IR warmup goofiness. As far as I know, the RCX really only looks for the FF 00 Not sure what happened to the F7 and 08, but (...) (21 years ago, 3-Feb-04, to lugnet.robotics.rcx)
|
| |
| | QuiteC IR interfacing to lego firmware IR
|
|
Hi, QuiteC's IR facilities are rudimentary. They send and receive single bytes. I need to be able to make it send and receive lego IR protocol messages for opcode 0xf7. I'm not having much luck. When I send a 0xf7 opcode with a message of 0x03 (...) (21 years ago, 3-Feb-04, to lugnet.robotics.rcx)
|
| |
| | Re: BricxCC release 3.3.7.7
|
|
(...) Upon further review, it would appear that (at least on my machine and one other that I have heard about) the new release of BricxCC (3.3.7.7) does, in fact, correctly download the brickOS firmware. My previous tests were using an old copy of (...) (21 years ago, 30-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: Problems with if-close with phantom.dll
|
|
(...) Hi!! are you italian??so am I :) (...) phantom.dll control ( a replacement of spirit.ocx) used in a visual c++ mfc application (...) I had already tried this.. it doesn't work.. I was wondering if there is a problem with the if function! thank (...) (21 years ago, 28-Jan-04, to lugnet.robotics.rcx)
|
