 | | Re: Decoding the LEGO IR remote control
|
|
(...) Ah, so the infamous d2 opcode is finally fully explained. What the d2 opcode did was discovered a while back when the firmware was disassembled, but people could only guess as to why Lego put such an opcode into the RCX. It was never connected (...) (25 years ago, 18-Sep-99, to lugnet.robotics.rcx)
|
| |
| | Re: Tasks vs. program slots
|
|
Hello Dave, First, let me thank you for NQC ... you've made my RCX playing tremendously more rewarding. I've been wanting to use a Sharp IR receiver to demodulate the signal from a LEGO remote control, and then a PIC to decode the rx output for use (...) (25 years ago, 18-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Tasks vs. program slots
|
|
(...) Too bad! So, the next thing I wonder is if there's any way to get an RCX to _send_ these packets to another RCX... (25 years ago, 18-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC API
|
|
I've been using NQC a bit ... and when the NQC 2 Request was posted, I got to thinking ... What about making a standard API that is not changed (except for officially) and a 'macro library' that can be added to and downloaded off of a website or (...) (25 years ago, 18-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Decoding the LEGO IR remote control
|
|
Dennis, Dave Baum just posted the remote control codes ... they are below: - Nick - Dave Baum wrote: [snip] (...) (25 years ago, 18-Sep-99, to lugnet.robotics.rcx)
|
| |
| | Re: Tasks vs. program slots
|
|
(...) The remote control always sends the same sort of packet: d2 xx yy where xxyy is a sixteen bit bit-field indicating what features should be activated: xxyy 0001 Message 1 0002 Message 2 0004 Message 3 0008 Motor A Forward 0010 Motor B Forward (...) (25 years ago, 18-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Decoding the LEGO IR remote control
|
|
(...) Hello Kekoa - - I apologize for not being able to make myself clear. I want to use the LEGO #9738 to control robots that use something other that the RCX for a controller. I envision a Sharp GP1U581Y IR receiver driving a PIC. The PIC will (...) (25 years ago, 18-Sep-99, to lugnet.robotics.rcx)
|
| |
| | Re: Tasks vs. program slots
|
|
(...) This is why it might be nice to get the remote control reverse engineered -- we may discover a way. (25 years ago, 17-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Tasks vs. program slots
|
|
(...) RCX contains 5 programs. Each program can have up to 10 tasks and 8 subroutines. Only one program may run at any given time, multitasking is between tasks in the same program. There is no known programmatic way of transferring control from one (...) (25 years ago, 17-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Decoding the LEGO IR remote control
|
|
(...) Do you want to connect the PIC to the IR tower to receive signals from the Lego remote control, or do you want to build your own IR receiver, and attach the PIC to that? The encoding of the IR is pretty simple. The IR tower contains a circuit (...) (25 years ago, 17-Sep-99, to lugnet.robotics.rcx)
|
