 | | Re: Two RCX with one IR-Tower
|
|
The 'usual' way to get status data is to poll the the RCX memory for status information, but you can't do that because of the number of RCX bricks; so how about getting each RCX to send a response message (or series of messages) to the PC encoding (...) (22 years ago, 24-Apr-02, to lugnet.robotics.rcx)
|
| |
| | Re: constructing a new network protocol for LegOS
|
|
heh.. wow.. seems theres alot of work going on on the LNP front these days. i too am working on a TCP like addition to the LNP's UDP protocol. This is nothing too fancy, but does add a sliding window feature which will make the connection between (...) (22 years ago, 24-Apr-02, to lugnet.robotics.rcx.legos)
|
| |
| | constructing a new network protocol for LegOS
|
|
Hi! We're a group from Aalborg University who are about to design and implement a new network protocol for LegOS. The protocol should be able to communicate via cables from the I/O ports and also via the IR port. It should be possible to address (...) (22 years ago, 24-Apr-02, to lugnet.robotics.rcx.legos)
|
| |
| | Interactive communication with the RCX
|
|
I have recently discussed with Kekoa an interesting issue that apparently received scarce attention in the past. I'm trying to have interactive communication between the computer and the RCX through IR connected to an USB port: sendind commands from (...) (22 years ago, 24-Apr-02, to lugnet.robotics.rcx)
|
| |
| | Re: Help request : LegOS 2.5, demo/c++.cpp make failure
|
|
(...) Yes, that ist normal. :) With gcc 3.0.3, you get these errors with the c++ demos. I haven't fiddled with it to get rid of those. But the legOS system itself builds fine, even smaller then with the older compiler version. You can do two things: (...) (22 years ago, 23-Apr-02, to lugnet.robotics.rcx.legos)
|
