I've succeded to solve it.
The problem is in the .cfg file. 
You must specify which body contains the interface. So you must change the
"gz_id" field with:

model_name::interface_name

and so not only interface_name. 

I hope I helped you. If you have other problems or you haven't understood
me, please contact me.



BenW2 wrote:
> 
> So I have spent pretty much all day going through the code trying to
> understand whats going on to find the problem. 
> 
> It seems that on start up the seperate devices should have files created
> for them in /tmp/gazebo-USER-0/, but the only one that gets created is
> simulation and a few graphics references. I think it is
> gazebo/trunk/player/GazeboDriver.cc that creates an instance of each
> device based on what is defined in gazebo.cfg. I have tried printing debug
> statements to check that the devices are read in, and it seems that they
> are and are understood by gazebo. Commenting out the initialisation within
> the big switch case statement, causes the start up to fail because the
> device cannot be created. So obviously it thinks that it is creating these
> files correctly, but I cannot seem to identify why the files are not
> created. 
> 
> Can anyone with more knowledge of the code point me towards where in the
> code I can check this process?
> 
> Thanks
> 
> 
> 
> 
> Neostek wrote:
>> 
>> I didn't succeed to solve it. But, I've seen that many people have the
>> same problem but anyone has an answer.... I hope that someone can tell to
>> Nate about this problem because I'm trying to solve it about one week
>> ago.
>> If you succeed to solve it, please contact me. 
>> Thanks a lot!
>> 
>> 
>> BenW2 wrote:
>>> 
>>> Hi,
>>> 
>>> Unfortunately not. I have made a number of posts, but no-one seems
>>> interested in passing over any ideas. It would be great if you have any
>>> success with this problem, as its a major hold up on some of my work.
>>> 
>>> 
>>> 
>>> Neostek wrote:
>>>> 
>>>> I've a similar problem. 
>>>> I have the last section of your problem ("timed out for server reply").
>>>> Do you succeed to solve this problem?
>>>> Please, if you had solved this problem, contact me!!
>>>> Thanks a lot
>>>> 
>>>> 
>>>> BenW2 wrote:
>>>>> 
>>>>> So I have had a little more luck with a reinstall of gazebo.  Im still
>>>>> using player svn, and Gazebo 8255. The sequence i follow is 
>>>>> 
>>>>> 1 - player gazebo.cfg
>>>>> 2 - gazebo pioneer2at.world
>>>>> 3 - playerjoy
>>>>> 
>>>>> output from player is ...
>>>>> 
>>>>> invoking player_driver_init()...
>>>>> 
>>>>>  * Part of the Player/Stage Project [http://p
>>>>>  * Copyright 2000-2006 Richard Vaughan, Andre
>>>>> ig
>>>>>  * and contributors. Released under the GNU G
>>>>> success
>>>>>   Gazebo Plugin driver creating 1 device
>>>>>     6665.31.0 is  a simulation interface.
>>>>> opening /tmp/gazebo-ben-0
>>>>> opening /tmp/gazebo-ben-0/simulation.default 
>>>>> opening /tmp/gazebo-ben-0/simulation.default 
>>>>>   Gazebo Plugin driver creating 1 device
>>>>>     6665.4.0 is  a position2d interface.
>>>>>   Gazebo Plugin driver creating 1 device
>>>>>     6665.6.0 is  a laser interface.
>>>>>   Gazebo Plugin driver creating 1 device
>>>>>     6665.10.0 is  a fiducial interface.
>>>>> 
>>>>> gazebo...
>>>>> 
>>>>> /usr/local/share/gazebo/worlds/models/pioneer2at.model:18: namespace
>>>>> error : Namespace prefix controller on differential_position2d is not
>>>>> defined
>>>>> <controller:differential_position2d name="controller1">
>>>>>                                                       ^
>>>>> /usr/local/share/gazebo/worlds/models/pioneer2at.model:24: namespace
>>>>> error : Namespace prefix interface on position is not defined
>>>>>   <interface:position name="position_iface_0" />
>>>>>                                              ^
>>>>> [/home/ben/player_SVN/playerstage/code/gazebo/trunk/server/GazeboConfig.cc:103]
>>>>>   Gazebo Path[/usr/local/share/gazebo]
>>>>> [/home/ben/player_SVN/playerstage/code/gazebo/trunk/server/GazeboConfig.cc:115]
>>>>>   Ogre Path[/usr/local/lib/OGRE]
>>>>> Gazebo successfully initialized
>>>>> 
>>>>> 
>>>>> (could the namespace error be a clue? )
>>>>> 
>>>>> and finally playerjoy...
>>>>> 
>>>>> Connecting to Player at localhost:6665 - playerc warning   : warning :
>>>>> [Player v.3.0.0-rc2~svn] connected on [localhost:6665] with sock 3
>>>>> 
>>>>> playerc error   : timed out waiting for server reply to request
>>>>> player:0:request:3
>>>>> playerc error   : failed to get response
>>>>> terminate called after throwing an instance of 'PlayerCc::PlayerError'
>>>>> Aborted
>>>>> 
>>>>> listening on 6665
>>>>> Listening on ports: 6665 
>>>>> accepted TCP client 0 on port 6665, fd 7
>>>>> Error Subscribing to Gazebo Position2d Interf
>>>>> error opening device file /tmp/gazebo-ben-0/p
>>>>> file or directory
>>>>> 
>>>>> I have searched and searched the forums with no luck. For some reason
>>>>> I cant talk to gazebo through player but have no clue why, it works
>>>>> find with Stage 3.0. Any suggestions will be much appreciated.
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/libgazeboplugin-tp25149145p26798343.html
Sent from the playerstage-gazebo mailing list archive at Nabble.com.


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Playerstage-gazebo mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo

Reply via email to