To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.nqcOpen lugnet.robotics.rcx.nqc in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / NQC / 1897
     
   
Subject: 
NQC Linux Support - USB and TCP
Newsgroups: 
lugnet.robotics.rcx.nqc
Date: 
Wed, 11 Mar 2009 01:45:38 GMT
Viewed: 
18539 times
  

For those interested, I have posted a patch to SourceForge for NQC at
http://sourceforge.net/tracker/index.php?func=detail&aid=2639763&group_id=68600&atid=521778 .
This patch includes several changes, most of which are related to Linux,
though portions may be of use to other platforms.

* Removed the dependency of <LegoUSB/legousbtower.h> when building with USB
support for Linux

* Set some properties so that they can be set from the "make" command line
instead of modifying the Makefile, facilitating easier package creation
(including DEFAULT_SERIAL_NAME and DEFAULT_USB_NAME).

* Now that the Lego USB tower driver is included in the kernel, the device
is typically either /dev/legousbtower0 or /dev/usb/legousbtower0. The code
files have been updated to reflect these names.

* If the NQC "-S" argument is in the format "usb[:<device>]" (e.g.
usb:/dev/lego0), the program will use /dev/lego0 as the USB device; if the
"-S" argument is simply "usb" then the program will check for the presence
of DEFAULT_USB_NAME, /dev/legousbtower0, or /dev/usb/legousbtower

* A "tcp" option has been added as an option to the "-S" argument,
performing communication over a TCP connection instead of a serial or USB IR
device. This facilitates the use of NQC with programs such as BrickEmu, an
RCX emulator (see http://hoenicke.ath.cx/rcx/brickemu.html ). The full
option format is "tcp[:<host>[:<port>]]" If port is not provided, the
program will default to the "magic" Lego port of 50637, and if the host is
not provided, the program will default to localhost.

I hope that some of this might be useful for a future release.  If there is
a future release, I would also like to propose that the source archive be
packaged more GNU-style, in that the root of the archive would only contain
a single folder named in the format $PACKAGE-$VERSION (e.g. nqc-3.1r7).  All
the source content would then be under this folder, easing some package
management tasks for certain distributions.


Thank you,
Matthew

   
         
     
Subject: 
Re: NQC Linux Support - USB and TCP
Newsgroups: 
lugnet.robotics.rcx.nqc
Date: 
Tue, 17 Mar 2009 02:19:37 GMT
Viewed: 
18922 times
  

In lugnet.robotics.rcx.nqc, Matthew Sheets wrote:
For those interested, I have posted a patch to SourceForge for NQC at
http://sourceforge.net/tracker/index.php?func=detail&aid=2639763&group_id=68600&atid=521778 .

Matthew,

Thanks for your patch for NQC.  I will look at adding this to the official
sourcecode and creating a new official release.

John Hansen

   
         
   
Subject: 
Re: NQC Linux Patches
Newsgroups: 
lugnet.robotics.rcx.nqc
Date: 
Fri, 7 Aug 2009 00:12:45 GMT
Viewed: 
27673 times
  

I have updated the earlier NQC patch and uploaded two additional patches.

Patch 1 - Update of the NQC USB and TCP Patch
http://sourceforge.net/tracker/?func=detail&aid=2639763&group_id=68600&atid=521778
* Updated for compatibility with gcc 4.4.x
* Removed the DESTDIR patch for the Makefile (moved to another patch)

Patch 2 - Support Makefile Variables DESTDIR and TOOLPREFIX
http://sourceforge.net/tracker/?func=detail&aid=2833299&group_id=68600&atid=521778
* Added support for the Makefile variables DESTDIR and TOOLPREFIX,
enhancing compatibility with distro packaging tools

Patch 3 - Enable Setting a Default Port Name in a Configuration File
http://sourceforge.net/tracker/?func=detail&aid=2833359&group_id=68600&atid=521778
* If no port is specified on the command line (the "-S" argument) and if
the environment variable RCX_PORT is not defined, NQC on Linux will then
check for a default device name in the following configuration files (in
order):
   1) ~/.rcx/device.conf
   2) /etc/rcx/device.conf
These configuration files are designed to be compatible with Bibo, as
patches have been created for Bibo to allow it to process port names that
are specified in the NQC format.  Due to limitations with environment
variables, there is a need to have an alternate means for specifying a
default port.


Thank you,
Matthew

--------------------------------------------
Matthew Sheets <mesheets@hotSPAMMERmail.com> wrote in message
news:KGBJK3.IBu@lugnet.com...
For those interested, I have posted a patch to SourceForge for NQC at
http://sourceforge.net/tracker/index.php?func=detail&aid=2639763&group_id=68600&atid=521778 .
This patch includes several changes, most of which are related to Linux,
though portions may be of use to other platforms.

* Removed the dependency of <LegoUSB/legousbtower.h> when building with USB
support for Linux

* Set some properties so that they can be set from the "make" command line
instead of modifying the Makefile, facilitating easier package creation
(including DEFAULT_SERIAL_NAME and DEFAULT_USB_NAME).

* Now that the Lego USB tower driver is included in the kernel, the device
is typically either /dev/legousbtower0 or /dev/usb/legousbtower0. The code
files have been updated to reflect these names.

* If the NQC "-S" argument is in the format "usb[:<device>]" (e.g.
usb:/dev/lego0), the program will use /dev/lego0 as the USB device; if the
"-S" argument is simply "usb" then the program will check for the presence
of DEFAULT_USB_NAME, /dev/legousbtower0, or /dev/usb/legousbtower

* A "tcp" option has been added as an option to the "-S" argument,
performing communication over a TCP connection instead of a serial or USB IR
device. This facilitates the use of NQC with programs such as BrickEmu, an
RCX emulator (see http://hoenicke.ath.cx/rcx/brickemu.html ). The full
option format is "tcp[:<host>[:<port>]]" If port is not provided, the
program will default to the "magic" Lego port of 50637, and if the host is
not provided, the program will default to localhost.

I hope that some of this might be useful for a future release.  If there is
a future release, I would also like to propose that the source archive be
packaged more GNU-style, in that the root of the archive would only contain
a single folder named in the format $PACKAGE-$VERSION (e.g. nqc-3.1r7).  All
the source content would then be under this folder, easing some package
management tasks for certain distributions.


Thank you,
Matthew

 

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