 | | Re: Tasks vs. program slots
|
|
(...) Yes, it appears to use the same packet level formatting. It does use a new bytecode (0xd2) that isn't seen elsewhere. This bytecode needs two bytes of data to follow. These three bytes of "payload" are encoded the usual way with a three byte (...) (25 years ago, 20-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Tasks vs. program slots
|
|
(...) Dave, It is basically just exactly what you describe. It usually takes about 200us or so to "see" the incoming 38KHz signal, common I suppose for an integrator to react to the signal getting through the band-pass filter, then a Schmidt trigger (...) (25 years ago, 20-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Code Repository
|
|
The advantage to using lego.gerf.org, is that with the faqomatic, you can upload any data (text, images, compiled source) into 'bags'. This allows anyone upload what ever they feel they need to compleat their idea. Of course, the all web interface (...) (25 years ago, 19-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Q:#include and RCXCC 3.0 beta help requested
|
|
There was a bug with #include for files using MSDOS line endings in NQC 1.0b1. I'm pretty sure RcxCC beta 3.0 used this version of NQC. The bug was fixed in NQC 1.0b2, which is available from (URL) for an include path, try setting the environment (...) (25 years ago, 19-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Q:#include and RCXCC 3.0 beta help requested
|
|
Hello. I have two questions about #include. I am using RCXcc Beta 3.0. 1. How do you specify the default include path. Is there an environment var? 2. When I use the full path (E:\lego\application...\file.nqh) I get an error that says there is no (...) (25 years ago, 19-Sep-99, to lugnet.robotics.rcx.nqc)
|
