Re: [Playerstage-users] ATRV Sr

[Toby C. <tco...@di...>]

Hi Doug/Nathan,
I thought Id add my two cents, Im currently the maintainer for the rflex
drivers which we successfully use and build on our b21r, however we have
replaced the ancient redhat distro with our own debian setup so that may
not help.
Im not sure wether the rflex driver has been used specifically on the
ATVR sr, but the range of rwi's rflex based robots it runs on has been
increasing over time and Im happy to look into any problems you run into
(bearing in mind I do not have access to ATVR's).  The rflex driver was
originally written for the ATVR Jr, Im not sure what the hardware
differneces between these are but hopefully it should work.

Toby


Brian Gerkey wrote:

> On Tue, 7 Sep 2004, Nathan M. Farrington wrote:
>
>> The following message is from Doug Few, who is trying to get Player 
>> to work
>> on an ATRV Sr.
>>
>> "The one problem I did have was compiling the latest version of player.
>> After I edited a few scripts to account for differences in iRobot's 
>> Mobility
>> software versions I wound up having difficulties with the fact that the
>> robot's did not have automake installed. I then shifted to my 
>> Mandrake 9.1
>> laptop (knowing it had automake) and had problems with my Python
>> installation. I have invested only a couple hours into trying to get 
>> things
>> installed but I had no idea I would run up against so much trouble. 
>> As for
>> the iRobot Machines... have you successfully compiled and installed the
>> player drivers on the robots? Should I retrograde player versions to
>> something that is more in line with the archaic operating system that 
>> is on
>> the ATRV Sr?"
>
>
> Assuming you're working from a distribution (I would recommend 1.5),
> you don't need automake in order to build Player, only to do development
> with it.  So the old machine, without automake, should work fine.
>
> Now, if you change any of the build configuration, then you might need
> automake (and maybe autoconf).  However, it doesn't seem like Doug 
> needs to
> do that.  There's a configure option to allow the user to specify where
> Mobility is installed, e.g.:
>   $ ./configure --with-mobility=<dir>
> The default, ${HOME}/../mobility/mobility-b-1.1.7-rh6.0, is overridden
> by whatever the user gives to configure.  This option should suffice,
> unless his version of Mobility uses a different file layout.
>
> Regarding Python problems, you can always pass --without-python to
> Player's configure, and then no Python-related things will be built.
>
> Finally, Player also includes an rflex driver, which does direct control
> of RFLEX robots, rather than going through Mobility.  I don't know
> whether the rflex driver has been tested on an ATRV; some robot-specific
> configuration information might be required.
>
>         brian.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Playerstage-users mailing list
> Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/playerstage-users
>