|
 | | Re: Problem with IR
|
| (...) Can you post the output generated by NQC when you add -v to the command line? nqc -Susb -TRCX2 -v -d filename.nqc > output.txt Or you could just email it to me directly. John Hansen (19 years ago, 24-Nov-05, to lugnet.robotics.rcx)
| |
|  
ir
(score: 1.892)
|
|
| | Re: Yet another Q: IR messages
|
| Hi Tobias, this could look something like this for example : int global_message; // place to store and read messages for every task task main() { start Read_Messages; // start Receive_Message Task while(true) { switch (global_message) { case 1 : (...) (24 years ago, 29-Mar-01, to lugnet.robotics.rcx.nqc)
| |
|
ir
(score: 1.892)
|
|
| |
|
ir
(score: 1.892)
|
|
| | Re: Yet another Q: IR messages
|
| To send a message use the following: SendMessage(<variable> or <number>); The variable must be of integer type between 1 - 255 The number must be between 1 - 255 To read a message from the IR port do <variable> = Message(); This will put whatever (...) (24 years ago, 29-Mar-01, to lugnet.robotics.rcx.nqc)
| |
|
ir
(score: 1.892)
|
|
| | Re: communication PC <-IR-> RCX
|
| Hi Pavel, check out the program loader. Basically, you have to register your own port handler for incoming packets on the PC. You should also acknowledge them in some way, so the RCX knows what's going on. Maybe IR networking should become secure. (...) (25 years ago, 11-Nov-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.891)
|
|
| |
|
ir
(score: 1.891)
|
|
| |
|
ir
(score: 1.891)
|
|
| | Re: Decoding the LEGO IR remote control
|
| (...) [snip] (...) What makes this especially intrigueing is that the remote control box does not send messages with the same preamble as the RCX does. The RCX with take an RCX message and treat it as a message. The stuff from the remote is treated (...) (25 years ago, 17-Sep-99, to lugnet.robotics.rcx)
| |
|
ir
(score: 1.891)
|
|
| |
|
ir
(score: 1.891)
|
|
| | Re: Decoding the LEGO IR remote control
|
| (...) [snip] Thanks to all you have responded to my plea for help on this list and on others ... especially Dave Baum, Kekoa Proudfoot, Dennis Clark, and several others. But, I'm giving up ... can't seem to find a way to decode the remote's signals. (...) (25 years ago, 25-Sep-99, to lugnet.robotics.rcx)
| |
|
ir
(score: 1.891)
|
|
| |
|
ir
(score: 1.891)
|
|
| | communication PC <-IR-> RCX
|
| Does anybody have an example of a LegOS program that sends data back from the RCX to the PC? Is this possible also with SPIRIT.OCX poll/datalog protocol? Tnanks, Pavel. e-mail: petrovic@ifi.ntnu.no (25 years ago, 11-Nov-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.891)
|
|
| | Re: legOS IR comm and debugging tools
|
| (...) Lorenzo, i also just started with legOS and just thought about exactly the same issue. I'm wondering, if anyone has tried to run gdb in remote mode on the RCX. Imho, this would be the perfect solution... I've never ported gdb-remote to a new (...) (25 years ago, 23-Nov-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.891)
|
|
| | Re: legOS IR comm and debugging tools
|
| (...) Yes, do follow this vision. (...) See "info gdb", following the links Targets -> Remote -> Remote Serial. The protocol assumes a serial line, using +/- for acknowledge/nak, single character commands and hexadecimal addresses. There are several (...) (25 years ago, 23-Nov-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.891)
|
|
| | Re: Running IR in the background
|
| (...) Commentary below. (...) I must have missed this one the first time around. lnp_logical_write() will block, but it should only block the thread it's called from. Put your send-zero loop in a separate thread and I think you should be set. (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.891)
|
|
| | 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)
| |
|
ir
(score: 1.891)
|
|
| | Re: Sending ir packets
|
| Check the source code for NQC (in rcx/RCX_Link.cpp), or even use it as your underlying comms library. You may spot something Dave does that you don't.. Phil. (...) (23 years ago, 29-Sep-01, to lugnet.robotics.rcx)
| |
|
ir
(score: 1.891)
|
|
| | Re: Blocking The Lego Remote?
|
| Hi Stephen, you will not have success with this approach, because the LEGO firmware has no collision detection (especially no collision avoidance !) for their IR protocol. So if you're using more than 2 IR devices with LEGO firmware you will receive (...) (23 years ago, 27-Apr-01, to lugnet.robotics.rcx.nqc)
| |
|
ir
(score: 1.891)
|
|
| | tm-and-ir.c
|
| Is anyone else having problems with this? The receive and display part works fine but it won't send "Hello World" when I press the View button. The srec from the LegOS home page works fine but if I build it myself it doesn't. I've tried both the web (...) (25 years ago, 1-May-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.891)
|
|
| | 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)
| |
|
ir
(score: 1.891)
|
