Subject:
|
Re: LNP problems detected
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Tue, 4 Apr 2000 17:26:26 GMT
|
Viewed:
|
2646 times
|
| |
|
|
Who is maintaining the LNP code right now? Not the stuff in the kernel,
but the desktop tools? It'd be great if we could wrap that up into a
package and put the source into CVS. That way, it might be easier for
someone like Manuel to hack in the solutions he is suggesting. Anyone?
Anyone?
-Luis
On Tue, 4 Apr 2000, Manuel Cabido Lopes wrote:
>
> A problem appeared when trying to sent the value 16. The LNP protocal makes
> the folowing string
>
> F0011000
>
> I couldnt receive in my computer the final caracter the 0. This can be a
> problem.
>
> Another problem, this one alowed by the protocol is the folowing:
>
> If some noise is received with the bits of the header the next caracter will
> be the size of the message. This causes the receiver to ignore many next
> caracter until reaching the end of the message and only them detecting the
> error with the checksum.
>
> Can I suggest another protocol
>
> HEADER SIZE CHKSUM BODY CHKSUM
>
> In this way only one byte would be lost.
>
> Thank you, happy yellow robots
>
>
-----------------------------------------------------------------------
"As an engineer, it's important to look yourself in the eye in the
mirror every morning, and remind yourself that 'marketing is
everything,' and engineering doesn't matter a tinker's damn."
-Keith Bostic
-----------------------------------------------------------------------
|
|
Message is in Reply To:
 | | LNP problems detected
|
| A problem appeared when trying to sent the value 16. The LNP protocal makes the folowing string F0011000 I couldnt receive in my computer the final caracter the 0. This can be a problem. Another problem, this one alowed by the protocol is the (...) (25 years ago, 4-Apr-00, to lugnet.robotics.rcx.legos)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
