|
|
 | | 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)
| | | | | Re: questions on events
|
| (...) Yeah, my fault. I said two things that do not have to follow. Yes, you can use one event monitor to watch more than one event... and yes, you can't nest event monitoring statements. I've not used an event watcher to monitor more than one event (...) (20 years ago, 3-Jan-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.nqc)
|
|
