To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 1475
1474  |  1476
Subject: 
Re: LEGO remote and LNP (legOS 0.2.4)
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Mon, 23 Oct 2000 17:08:07 GMT
Viewed: 
1324 times
  
I'd actually really like to include Chris's patch in the official tree,
but I'm informed by folks with more clue about the networking stuff than
me that switching the parity bit would probably break some LNP stuff.
Would everyone be happier if I posted the patch on the site, along with
some description of how to apply it to stock 0.2.4 and rebuild? I think
that this seems like a reasonable compromise, unless someone has a better
suggestion...
Luis (who is very sorry that he hasn't written to Chris in some time)

On Mon, 23 Oct 2000, Jochen Hoenicke wrote:

Date: Mon, 23 Oct 2000 16:53:44 GMT
From: Jochen Hoenicke <Jochen.Hoenicke@Informatik.Uni-Oldenburg.DE>
To: lugnet.robotics.rcx.legos@lugnet.com
Subject: Re: LEGO remote and LNP (legOS 0.2.4)

On Oct 23, Rasmus Kjeldsen wrote:
Hi

I've just got the LEGO remote control (from the Ultimate Accessory Kit), and
of cause it dosen't work with legos. So I tried to see, if anyone had done
some kind of driver to it, but I couldn't find any, and began hacking in the
legOS kernel (kernel/lnp.c), to see, if I could alter the LNP driver to accept

messages from the remote. It nearly works, but strangly enough, a couble of
bytes is missing. I receive the following bytes for "message 1": (out of my
memory)

55 ff 00 2d d2 00 ff 2d d2

But if I use a program on my Linuxbox, which receives the signal from the ir-
tower, I get:

55 ff 00 2d d2 00 ff 01 fe 2d d2
So the question is: Why are the 01 fe bytes missing???

The remote control sends with parity odd, but the rcx is programmed to
no parity.  If the parity bit has the same value as a undriven line (I
think it is logical 1), the byte is received, but otherwise the byte
gets thrown away by the serial hardware.

The fix is of course to put the serial in odd parity mode.  There was
a patch by Chris Arquiza on this list some time ago (18. July) and I'm
using it (slightly modified) without problems.  For convenience I have
now put the patch I am using at:

  http://www.informatik.uni-oldenburg.de/~delwi/legOS/remote.diff

  Jochen



-----------------------------------------------------------------------

    "It's clear to us that Microsoft isn't the competition anymore.
                       They are our environment."
        WordPerfect manager, talking about Word

-----------------------------------------------------------------------



Message has 1 Reply:
  Re: LEGO remote and LNP (legOS 0.2.4)
 
Luis, I can do a quick HOWTO (though it'll only cover Linux) & post this patch. I think it'd be useful, anyway. It applies cleanly to 0.2.5 as well. Regards, ROSCO Luis Villa <liv@duke.edu> wrote in message news:Pine.GSO.4.10.1...uke.edu... (...) (...) (24 years ago, 6-Feb-01, to lugnet.robotics.rcx.legos)

Message is in Reply To:
  Re: LEGO remote and LNP (legOS 0.2.4)
 
(...) The remote control sends with parity odd, but the rcx is programmed to no parity. If the parity bit has the same value as a undriven line (I think it is logical 1), the byte is received, but otherwise the byte gets thrown away by the serial (...) (24 years ago, 23-Oct-00, to lugnet.robotics.rcx.legos)

11 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR