 | | Re: New NQC API for RCX-Spybot or RCX-RC communication
|
|
(...) I forgot to include a few #defines: #define SERIAL_PACKET_RC 0 // default #define SERIAL_PACKET_SPYBOT 0 #define SERIAL_COMM_RC 7 // 4800/76KHZ/25% #define SERIAL_COMM_SPYBOT 7 // was SERIAL_COMM_4800 + SERIAL_COMM_76KHZ The RC function, by (...) (20 years ago, 12-Jan-05, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | New NQC API for RCX-Spybot or RCX-RC communication
|
|
Recently I happened across the MindScript headers for the RCX in the SDK and saw some interesting macros for RCX communication. I decided to port them to NQC and possibly add them to the official built-in NQC API. I would be extremely grateful if (...) (20 years ago, 12-Jan-05, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: NQC API for the new Swan firmware
|
|
(...) I would in this case prefer the second - I actually use a "kMyNamedConstant" convention in my code, and find it very nice to have the API constants very easily seperable from my constants. (...) Again, personally I would prefer that, as it (...) (20 years ago, 11-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC API for the new Swan firmware
|
|
I am working feverishly on updates to NQC which will include extensions to the built-in API in support of Dick Swan's new firmware. My intent is to be consistent with the existing NQC API. However, there are some issues I am debating and I would (...) (20 years ago, 11-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 1.0 compatibility mode
|
|
(...) I know I got stung with it when I first installed the IDE, not having it woulda saved me a couple of posts to Lugnet :) ROSCO (20 years ago, 7-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 1.0 compatibility mode
|
|
(...) I think if they need NQC V1, they won't have this new IDE. If they have the new IDE, they won't have NQC V1.x (20 years ago, 7-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC 1.0 compatibility mode
|
|
Would anyone miss terribly the NQC 1.x compatibility mode if I were to remove it? At this point it seems like it is a very useless feature, but maybe someone out there is still using the 1.x API. What do you think? John Hansen (20 years ago, 6-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Swan Firmware
|
|
(...) The Swan firmware is Dick Swan's replacement firmware which is compatible with the standard LEGO firmware (firm0328.lgo). The Swan firmware is available at the link mentioned in this post: (URL) use swan.nqh (available in the zip file (...) (20 years ago, 4-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Swan Firmware
|
|
(...) what is the swan firmware? what have I missed? Thomas (20 years ago, 4-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: questions on events
|
|
(...) This is where you use the event fork(s) that you asked about in a different message. You nest these forks to determine which event has been triggered. (...) Robolab is just a LabVIEW program. Viewed in that context, it is an amazing bit of (...) (20 years ago, 3-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc)
|
