Re: [Playerstage-users] multiple blob finders bug?

[Ben G. <bp...@gr...>]

Hi Mike,

The player port for captureCamera isn't hardcoded. Unfortunately I chose a 
strange and unnecessary mechanism for altering it from the default value. In 
player 1.5 you can set the player port and camera index as options in the 
config file. e.g.

in config for player to be run on port 6664 use:
blobfinder:0
( 
  driver "cmvision"
  capture "camera" 
  port "6664"
  colorfile "/usr/local/share/player/config/colors.txt"
)

in config for player to be run on port 6665 use:
blobfinder:0
( 
  driver "cmvision"
  capture "camera" 
  colorfile "/usr/local/share/player/config/colors.txt"
)

This will crank up a blobfinder on ports 6664 and 6665 as you desire.

Brian has removed this oddness from the current CVS version. That version 
behaves as you had anticipated. Sorry for the confusion.

Regards,
Ben
 
On Friday 18 June 2004 13:56, umg...@cc... wrote:
> I think i found a small bug.  I have an instance of gazebo running and then
> I run two instances of player: one on port 6665 and the other on port 6664.
>  Both are using blob finders.  When I try and initialize a blob finder on a
> port other than 6665 I get this error.  If you go and look in
> captureCamera.cc, you will notice that port 6665 is hardcoded in the
> captureCamera constructor.  Is this a bug or am I only supposed to be
> allowed to run blobfinder on port 6665.  Thanks
>
>
> Here is the error.
>
> CMVision server initializing...player error :
> captureCamera.cc:captureCamera(): unable to locate suitable camera device
> player error : P2CMV.cc:Setup():
>     Vision init failed.
>
>
> -Mike Gauthier