 | | Re: Revisions to RcxCC
|
|
(...) I am considering taking advantage of the -raw option on NQC or possibly the -remote option to further enable RcxCC in the absence of Spirit.ocx. Of course, most users of RcxCC will have spirit.ocx, but Scout users may not. I'm not planning on (...) (24 years ago, 5-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Exploration Mars Balloon Tires Part#
|
|
Hello Would anyone happen to know the LEGO Shop-At-Home part # for the Balloon Tires that come with the Exploration Mars expanion set ? Thanks Tim Goodwin (24 years ago, 5-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Revisions to RcxCC
|
|
hi John, Great idea, (for RCXcc is a very good application, even my children can write programs with it) I just had the same idea, but my time is limited. I've need some more ideas, here are some of mine ideas (and bugs), I wanted to implement: - (...) (24 years ago, 4-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Revisions to RcxCC
|
|
(...) You can probably use NQC to implement a lot of the other fancy features as well. The "-raw" option for NQC lets you send raw byte packets. You'd need to figure out the actual bytecodes from Lego's LASM document, but you wouldn't have to worry (...) (24 years ago, 4-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Revisions to RcxCC
|
|
(...) This is unclear. What I mean to say is that I'm revising RcxCC so that it will be able to run in the situation where you do not have the Spirit OCX installed on your system. Since NQC is all that is required to compile, download, and run a (...) (24 years ago, 4-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Revisions to RcxCC
|
|
I'm working on a revision to Mark Overmars' fantastic RcxCC program. I'm an experienced Delphi programmer so that's no problem. But I'm not all that experienced with NQC or the RCX generally. I've got a the latest version of NQC, a Cybermaster, an (...) (24 years ago, 3-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
(...) My guess is that SENSOR_1 in your receiving RCX is getting a 1 when your program starts. I imagine that OFF is the default state for OUT_B in your transmitter RCX, and that the receiver is seeing this before OUT_B is switched to FLOAT. This is (...) (24 years ago, 3-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
(...) Hi Dean, meanwhile I followed your suggestions and implemented a scheme that uses a pulse scheme like this: ______ ______ ______ __ ______ ______ ___...___ Start Bit3 Bit2 Bit1 Bit0 A bit value of 1 results in a long pulse, a bit value of 0 in (...) (24 years ago, 3-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Yet another Q: IR messages
|
|
(...) Hi Tobias I'm not very familiar with NQC events, but if you want to use a blocking function for receiving your message, use parts of the code i posted before. int local_message = 0; int global_message = 0; task main() { //do what you like (...) (24 years ago, 31-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Yet another Q: IR messages
|
|
If I am understanding what you want correclty (I have never used the RCX-code) only NQC then try this. Assume: RCX2 is sending message # 15 to RCX1. RCX1 is in a waiting state until it gets the message RCX code: . . . While (Message() != 15){ ++i; } (...) (24 years ago, 31-Mar-01, to lugnet.robotics.rcx.nqc)
|
