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 / 1901
1900  |  1902
Subject: 
Re: lnp rcx hostaddress [and a summer legOS release?]
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Sun, 27 May 2001 15:39:22 GMT
Viewed: 
1404 times
  
Vittorio-
I've frequently wondered the same, but since I've never had reason to
use LNP I've never fixed it. If you'd like to submit a patch I'll gladly
apply it to the source tree.

In other news- I'm back, more or less. While this week will be pretty
hectic, I'll be spending parts of the next two weeks slowly going
through the legOS archives of the past 6 months and getting back on my
feet. I know lots of people have expressed interest in all variety of
contributions, including stuff related to a new networking protocol and
new and better documentation, and I'd like to get these people involved
as I get myself back into the swing of things.

I'd like to aim at a new release by the end of the summer (say, late
August.) I have no idea at the moment what would go into such a
release... I'll work on a list as I read through the archives, but I'd
think it would probably include new documentation, an API
cleanup/reorganization, and hopefully lots of LNP re-working to make it
more usable. If anyone else has suggestions- please! fire away. My legOS
needs are met; so I'm not exactly going to be a fount of ideas- I just
want to be a clearinghouse and organizer and perhaps coder for the work
and ideas of others.

Anyway, let me know if you think I'm nuts...
Luis

On 27 May 2001 11:16:02 +0000, Vittorio Zamparella wrote:
I have an important question:

WHY the rcx lnp address (and mask) is hardcoded in the library?

I inspected the source code for both the pc part and the rcx part.
The pc library is well formed and the init function allows you to set up the
address and mask.
Instead the rcx  lnp library (lnp.c) lacks of a real init function and the
internals rely on configuration symbols rather than variables. It is really
not clear the purpose of this choice.

The work needed to straighten the library is minimal: two more variables, an
init function (based on the pc-side library) and the change of to lines in
the logical-received function.
And I'm gonna do it because our project specifically needs to use multiple
rcx toghether.

Comments on this topics will be appreciated.

Ciao,
     Vittorio


--
Luis Villa
Duke University '01
http://tieguy.org/
"Liberace outlived Elvis, thereby suggesting to many there is no God, or if
  there is one, He lacks taste."
        -www.lileks.com



Message has 1 Reply:
  Re: lnp rcx hostaddress [and a summer legOS release?]
 
Hi I'm preparing for the same project Vittorio's working on, a high level library in C++ to send explicit commands to rcx from a pc and back. I hope if you gonna change the low level library you will mantain a certain compatibility so that I won't (...) (23 years ago, 28-May-01, to lugnet.robotics.rcx.legos)

Message is in Reply To:
  lnp rcx hostaddress
 
I have an important question: WHY the rcx lnp address (and mask) is hardcoded in the library? I inspected the source code for both the pc part and the rcx part. The pc library is well formed and the init function allows you to set up the address and (...) (23 years ago, 27-May-01, to lugnet.robotics.rcx.legos)

5 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