While I was testing PLAYER I also tried the stereo camera on min1 - it seems to work as I coulddisplay its stream via PLAYER/videoplayer on my laptop.
3 Fedora Core 3 setup
Nothing too special about the installation, I tried to install only the minimum requirementwithout the X server overhead for example to keep the image’s size small. The rights for theserial connection had to be set, the shutdown per rFLex interface enabled as Ben describes it inhis INSTALL of the robotmgr. I’m having problems with the yum update system so I installedmost specialised packages on my own because I couldn’t ﬁnd them with
yum search foo
. Thewireless card is managed by a special controller so its only necessary to include drivers for thenetwork interface, throughput is awfully slow though.When you boot the robot it will probably try to run the redhat hardware detection to ﬁnd newdevices, which is unreadable on the small screen of the robot. It will time out after 30 secondsand continue to boot.
The ﬁrewall can be modiﬁed with the Fedora tool
. I enabled somestandard ports like HTTP (needed for JADE), ssh and ports for PLAYER and JADE.
3.0.3 User setup
Apart from the root user I added only one further user: mobility. The password for root andmobility won’t be written here.
4.1 RobotMgr on Min1
I didn’t try RobotMgr on the ATRVs but I assume that some changes have to be made forit to work like on the Magellans. Like I described in my report the rFlex device uses its ownabstract units for distance and angle measurement which diﬀer on the ATRVs and the Magellans.PLAYER uses a variable to convert between those abstract values and the real values in mmand degree - and those variables diﬀer a lot between those two robot classes. This has to beconsidered when using RobotMgr on the ATRVs.3