 | | Re: legOS Network Protocol —Mike Moran
|
| | | (...) 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 (...) (26 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: legOS Network Protocol —Lou Sortman
|
| | | | | (...) 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 (...) (26 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | | Re: legOS Network Protocol —Mike Moran
|
| | | | | | (...) 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 (...) (26 years ago, 23-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | Re: legOS Network Protocol —Jacob S. Barrett
|
| | | | | (...) 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 (...) (26 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | | Re: legOS Network Protocol —Markus L. Noga
|
| | | | | | (...) 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 (...) (26 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | Re: legOS Network Protocol —Richard Franks
|
| | | | (...) 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 (...) (26 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | |
