 | | legOS Network Protocol
|
|
Markus, I have been away for the last week or so. What have I missed in the discussion on LNP? I would like to get cracking on this. I have 2 or 3 guys over here who want to get into this too. -Jake Jacob S. Barrett jsbarrett@acm.org (25 years ago, 28-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) I too may be interested in this, although probably only the higher level stuff ie I'm not too sure how good I'd be at interfacing with the IR. Anyway, I had a look around and I found some references on a protocol layered on top of IP called (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Sounds good. Does it provide a stream interface or datagrams only? My faulty memory suggests that it might be the latter. If the network implementation supports packet reassembly (packets larger than MTU), there may not be a need for a stream (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
This would almost have to be a UDP like protocol just because the RCX has such limited resources and the complexity of adding transmision control to the protocol would be nasty. I really hate news groups, I like having messages sent to me directly. (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) I am not in position right now, time-wise, to contribute to the LNP, but I am very interested, and may have time to contribute soon. In the mean time, I'd like to keep up with the project. I don't know if you realize, Jacob, but if you prefer (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
Jacob S. Barrett <jsbarrett@acm.org> wrote in message news:3716681C.D5C8C6...acm.org... (...) You can subscribe to this newsgroup as a mailing list. I would prefer to see it on this group (or less thing to subscribe to) or to have lugnet make a new (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
I figured that out... Thanks... I am subscribed via email now! Much nicer... I am just too lazy to remeber to go check news groups. -Jake (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) The interface is specifically datagram only. Dunno about packet reassembly; I doubt it as the philosophy is minimalism. The main advantage I see in it is the ability to change the degree of checking it does on your behalf to ensure packets (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) From what little I remember about the Lego protocol, here are some thoughts. *) On reception, some Lego packets may contain data which look like the beginning of a legOS native protocol frame. Most likely, the checksum would fail (once enough (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Yes this will be a datagram only protocol for the time being. The LNP will allow us to do things like debugging and remote control. I have also invisioned something like a "shell" running on the legOS that you could either "telnet" in to or (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Assuming packets without large internal gaps, we could employ a timeout to wait for a packet transmission of unknown protocol type to end. At 2400 bps with 8E1 (LEGO, isn't it?), one data byte has 11 bits, so a space of 1.5*11/2400 s should be (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Hmm.. with a little hacking you could certainly detect logic errors. The main problem I think would be writing alternative C-Functions for the H8 assembler, which makes up legOS itself. You'd also need to create a simulator engine for legOS to (...) (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) given (...) lego (...) [ stuff about lego/native collisions ] (...) of a (...) on (...) I was wondering, since people are considering using tags in the LNP frame to signify local to local messages, could we not also use this to "label" non (...) (25 years ago, 23-Apr-99, to lugnet.robotics.rcx.legos)
|
