 | | Re: NQC vs Spirit communication speed —John Hansen
|
| | | (...) I'm using AutoLink.Send for most things. Initially I was always closing the link at the end of each method (which mostly map to the Spirit OCX API). I've made that configurable and at present I'm running with it set to leave the link open. (...) (24 years ago, 11-May-01, to lugnet.robotics.rcx.nqc)
|
| | | |
| | | | | Re: NQC vs Spirit communication speed —Dave Baum
|
| | | | (...) Correct - dynamic timing is turned off when predictive is being used (which is the default). Predictive is relatively new, and I wasn't sure which code you started with (or how you ported/used it), so that's why I explained the dynamic timing. (...) (24 years ago, 11-May-01, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: NQC vs Spirit communication speed —John Hansen
|
| | | | (...) I made PredictReplyLength a member of the RCXLink class so it can return a different value for case 0x20 (it returns 20 if the Target is Cybermaster and 0 if it is Scout - since the Scout doesn't support that opcode). Of course, in Object (...) (24 years ago, 11-May-01, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: NQC vs Spirit communication speed —Dave Baum
|
| | | | (...) I knew Scout didn't support the opcode, but overlooked the Cybermaster case. I'll fix it for NQC as well. The return value for an unsupported opcode doesn't really matter since nothing is going to come back anyway, so predictive will fail no (...) (24 years ago, 12-May-01, to lugnet.robotics.rcx.nqc)
|
| | | | |
