 | | Re: communication brick <-> PC
|
|
(...) My current thoughts are to add "listen" support to rcxlib/RCX_Link, but not add anything else to the nqc tool itself. This would facilitate writing a small wrapper program around rcxlib/RCX_Link that could send/receive messages without (...) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: communication brick <-> PC
|
|
(...) It can be used, but the problem is that the tower shuts off fairly quickly if it doesn't hear anything from the computer. So the listening program would need to be sending keep-alive messages periodically. I think that Dave will put something (...) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | communication brick <-> PC
|
|
Hi there ! I've got a question concerning ir communication with the brick ... After having done some low-level debugging to make a self-written programm communicate with my brick using the IR tower, I'd like to make my programm control the brick. (...) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.x event processing
|
|
(...) I don't have any changes in mind for the monitor/catch construct, although I'll listen to suggestions if people have any. There was a brief discussion about this a while back: (URL) that point I was already pushing a procedural approach - (...) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC 2.x event processing
|
|
Dave, I'm curious if the system of events and event-trapping in NQC 2.x will remain about the same as it is now. I played around with it this last week, and had little success (it worked once or twice, I *think*), but what struck me was how much I (...) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
|
