|
|
 | | Re: Reading Spybotic controller
|
| (...) I seem to remember in Mindscript, there is a way to disable the RC messages. I think it was something like "setRCDisable" I'm not sure if that is implemented in the latest verson of NQC. (and I'm not sure if that's the right command) But I (...) (20 years ago, 26-Jan-04, to lugnet.robotics.spybotics, lugnet.robotics)
| | | | | Reading Spybotic controller
|
| Hi, I've been trying some experiments with Spybotic communications using Bricxcc and NQC. I have been able to send and receive messages using 'SendSpybotMessage()' and 'RxMessage()' However, when I try to read the controller, I am only able to (...) (20 years ago, 24-Jan-04, to lugnet.robotics.spybotics, lugnet.robotics)
| | | | | Re: BricxCC release 3.3.7.7
|
| (...) Unfortunately, BricxCC is still not downloading the brickOS firmware correctly. I will look into this problem and try to fix it. In the mean time, you can use firmdl3 which works correctly. John Hansen (20 years ago, 23-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | BricxCC release 3.3.7.7
|
| I've released version 3.3.7.7 of BricxCC today. It adds a Spybot EEPROM tool window. It adds a new configurable watch tool window. It adds a new generic set source value tool window. It adds a hot key (F2) for the pbForth console. The position of (...) (20 years ago, 22-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | Re: BricxCC release 3.3.7.6
|
| Hi John, Thanks to your pre-built BrickOS tools, I have finally installed it on my Windows 2000 machine (I tried several times in the past... no luck !). The installation was really fast and easy, the only problem I got was that the default BrickOS (...) (20 years ago, 15-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | Re: NQC's future
|
| "Brian Davis" <brdavis@iusb.edu> wrote in message news:HrB87H.17p1@lugnet.com... (...) future one) for NQC (...) I think your question probably meant "can I use FastTimer in defining events because I want better resolution than is possible with (...) (20 years ago, 12-Jan-04, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | Re: BricxCC release 3.3.7.6
|
| (...) I will make this change. Thanks for the report! John Hansen (20 years ago, 12-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | Re: NQC's future
|
| (...) According to the LEGO documentation, only the normal (source 1) Timers can be used as an event source. The ‘sensors’ for which events can be generated are: · Physical sensors (Source 9, Range 0-2, Logical number 0-2) · System timers (Source 1, (...) (20 years ago, 12-Jan-04, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | Re: BricxCC release 3.3.7.6
|
| small suggestion: when you've a syntax error in NQC, it goes like this - error is reported - you correct the error - recompile the source - code is downloaded - error message disappears In my opinion, the last 2 actions should be the other way (...) (20 years ago, 11-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
| | | | | Re: NQC's future
|
| (...) Here's a suggestion/question: is it possible (either in the current incarnation or a future one) for NQC to use FastTimer() as a source for events? Timer() works, but not (it seems) FastTimer(). (20 years ago, 11-Jan-04, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
|
