2011/5/9 Tim Clephas <t [dot] t [dot] g [dot] clephas [..] ...>

> Hi,
>
> I have seen this before with some DNS problems. Just to be sure, can you
> ping from both devices to both devices using hostnames?
>
>
Thanks for this. I think it was the robot->host side who didn't succeed. Now
it "works" (I have very hudge latency, but I think it is a network problem).

> Tim
>
> On Mon, 2011-05-09 at 13:38 +0200, Willy Lambert wrote:
> > Hi,
> >
> > I experience difficulties whith these 2 use cases :
> > 1/ roslaunching several deployer on the same machine
> > 2/ roslaunching a deployer on a machine with a distant roscore and
> > working app
> >
> >
> > For 1/, the problem is that both deployer are launched from the same
> > directory ($ROS_HOME), so orocos.log and .tb_history are the same for
> > both deployers. Does anyone know a solution to avoid this ? In the
> > best case I would like each deployer be launched in my 2 different
> > packages.
> >
> > For 2/ I have deployed a working application (containing a deployer)
> > on the robot with a roscore. I have launched a deployer on my host
> > computer with the ROS_MASTER_URI of my robot. This application is
> > publishing into a port connecting to a rostopic. If I launch rxgraph I
> > see everything to be well connected.
> > If I use on the host :
> > ROS_MASTER_URI=http://beta:11311/ rostopic echo /Command/velocity
> > I see my command being send from my host to the robot
> >
> > If I use on the robot (at the same time) :
> > rostopic echo /Command/velocity
> > I don't see anything !
> >
> > Does someone has ever tried a distant
> >
> > If I launch the 2 applications on the same machine everything is
> > perfectly working (so it is not an app bug :p). The only thing I could
> > accuse in my app is that the suscribing could need something special
> > for distant work I forget (I have never play with this before).
> >
>
>
>

On May 9, 2011, at 07:56 , Tim Clephas wrote:

> Hi,
>
> I have seen this before with some DNS problems. Just to be sure, can you
> ping from both devices to both devices using hostnames?
>
> Tim
>
> On Mon, 2011-05-09 at 13:38 +0200, Willy Lambert wrote:
>> Hi,
>>
>> I experience difficulties whith these 2 use cases :
>> 1/ roslaunching several deployer on the same machine
>> 2/ roslaunching a deployer on a machine with a distant roscore and
>> working app
>>
>>
>> For 1/, the problem is that both deployer are launched from the same
>> directory ($ROS_HOME), so orocos.log and .tb_history are the same for
>> both deployers. Does anyone know a solution to avoid this ? In the
>> best case I would like each deployer be launched in my 2 different
>> packages.
>>
>> For 2/ I have deployed a working application (containing a deployer)
>> on the robot with a roscore. I have launched a deployer on my host
>> computer with the ROS_MASTER_URI of my robot. This application is
>> publishing into a port connecting to a rostopic. If I launch rxgraph I
>> see everything to be well connected.
>> If I use on the host :
>> ROS_MASTER_URI=http://beta:11311/ rostopic echo /Command/velocity
>> I see my command being send from my host to the robot
>>
>> If I use on the robot (at the same time) :
>> rostopic echo /Command/velocity
>> I don't see anything !
>>
>> Does someone has ever tried a distant
>>
>> If I launch the 2 applications on the same machine everything is
>> perfectly working (so it is not an app bug :p). The only thing I could
>> accuse in my app is that the suscribing could need something special
>> for distant work I forget (I have never play with this before).
>>

There is an ORO_LOGFILE environment variable that RTT v2 appears to pick up and use instead of 'orocos.log' (I've not used this, just noticed it the other day while making other mod's). Check rtt/Logger.cpp. Can't help with the .tb file though, but a patch to change that also would be useful I imagine.
S

2011/5/9 Tim Clephas <t [dot] t [dot] g [dot] clephas [..] ...>

> Hi,
>
> I have seen this before with some DNS problems. Just to be sure, can you
> ping from both devices to both devices using hostnames?
>

I am looking at this

I also have those errors sometimes, if it may help :

[ERROR] [1304942821.353304371]: accept() on socket [11] failed with error
[Too many open files]
[ERROR] [1304942821.353451738]: accept() on socket [11] failed with error
[Too many open files]
[ERROR] [1304942821.353584788]: accept() on socket [11] failed with error
[Too many open files]
[ERROR] [1304942821.354648833]: accept() on socket [11] failed with error
[Too many open files]
[ERROR] [1304942821.356428132]: accept() on socket [11] failed with error
[Too many open files]
[ERROR] [1304942821.357501326]: accept() on socket [11] failed with error
[Too many open files]

>
> Tim
>
> On Mon, 2011-05-09 at 13:38 +0200, Willy Lambert wrote:
> > Hi,
> >
> > I experience difficulties whith these 2 use cases :
> > 1/ roslaunching several deployer on the same machine
> > 2/ roslaunching a deployer on a machine with a distant roscore and
> > working app
> >
> >
> > For 1/, the problem is that both deployer are launched from the same
> > directory ($ROS_HOME), so orocos.log and .tb_history are the same for
> > both deployers. Does anyone know a solution to avoid this ? In the
> > best case I would like each deployer be launched in my 2 different
> > packages.
> >
> > For 2/ I have deployed a working application (containing a deployer)
> > on the robot with a roscore. I have launched a deployer on my host
> > computer with the ROS_MASTER_URI of my robot. This application is
> > publishing into a port connecting to a rostopic. If I launch rxgraph I
> > see everything to be well connected.
> > If I use on the host :
> > ROS_MASTER_URI=http://beta:11311/ rostopic echo /Command/velocity
> > I see my command being send from my host to the robot
> >
> > If I use on the robot (at the same time) :
> > rostopic echo /Command/velocity
> > I don't see anything !
> >
> > Does someone has ever tried a distant
> >
> > If I launch the 2 applications on the same machine everything is
> > perfectly working (so it is not an app bug :p). The only thing I could
> > accuse in my app is that the suscribing could need something special
> > for distant work I forget (I have never play with this before).
> >
>
>
>