|
|
 | | Re: host address
|
| (...) Do you have a patch? (...) I'm writing a compiler (automaton model of the robot to C). With dynamic addresses, it could manage an "addresses pool", and simply add a call to change the address when the program starts... On the other hand, if (...) (23 years ago, 30-Dec-01, to lugnet.robotics.rcx.legos)
| | | | | Re: host address
|
| Eric, see the thread started by Zhengrong Zhang on 11/5/01 about this. short: we can't find any compelling reason to hardcode the address. I'm not sure about Zhengrong, but I've modified my copy of LegOS to support "dynamic" addresses (i.e. can (...) (23 years ago, 30-Dec-01, to lugnet.robotics.rcx.legos)
| | | | | Re: How to make shared memory....not
|
| Hi Steve, (...) Yes. Actually, I am working on a robot that finds a path trough a maze. After solving the maze, a second program can run through the maze with the informations from the first program. (I will do this with shared mem). Both programs (...) (23 years ago, 28-Dec-01, to lugnet.robotics.rcx.legos)
| | | | | LNPD: communication between clients
|
| It seems that when a client of lnpd sends data to the IR tower, these are not sent to the other clients connected to the daemon. Unfortunately, I really need this feature... So I tried to call "deliver_packet(tx_buffer, tx_end-tx_buffer);" in (...) (23 years ago, 28-Dec-01, to lugnet.robotics.rcx.legos)
| | | | | Re: How to make shared memory....not
|
| (...) Yes, I'm sure I can. And I think it would be 'safer' that way. But Mike's idea about functions sounds interesting. I don't really have any idea about how I would use that in a real program, but it sure sounds interesting. Steve (23 years ago, 27-Dec-01, to lugnet.robotics.rcx.legos)
|
|
