| |
In lugnet.robotics.rcx.legos, Frederick N. Brier writes:
> I am coming into the middle of this...
As am I - it looks interesting, but looks like it may have died. Hopefully not!
> Could a token passing mechanism be used to prevent the IR flooding?
> It would slow down transmission and would require a lost-token/token-
election process.
I had wondered about this.
My big suggestion is for us to come up with a software API for both the RCX
end and PC (or whatever) end. This would allow people to experiment with such
ideas & learn, rather than have a single set-in-stone black-box mechanism.
Of course, at some point a standard LNP should probably be defined.
If we could come up with such an API, I would probably write an initial LNP
that supports simple two point RCX<->RCX or RCX<->PC comms to get the ball
rolling again.
Thoughts?
> My thought was: It might be nice to have a process (application/device
> driver) on the PC that would read the protocol from the IR port and
> converted to TCP/IP sockets.
Basically a kinda TCP/IP etc. <-> LNP router. Cool - would allow RCX<->RCX
comms via e.g. the Internet! Again, if this matched the API people could use
this with their experimental LNP's as well.
Also, how about a "delay line", so you could simulate a real Mars rover with
the attendant comms delays to Mars!
Kevin.
|
|
Message is in Reply To:
 | | Re: LNP Repost
|
| I am coming into the middle of this (or at the end considering the posting dates), and am hoping I don't sound like a fool putting out these ideas (since I don't yet know how legOS works). Is the RCX# used as a sort of ethernet MAC address? If you (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
