Re: [Playerstage-users] Khepera driver debug: IR sensor readings

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Actually stage doesn't support any IR interface. So far I had to perform my
simulations with sonar interface that is approx. the same thing.
Toby, the libplayerc++ is so messed uuuuuuuuuuuuuup!!! I will try to figure
out how it works to debug the ir_device but.. don't you thik it would be
more simple to change the khepera driver in order to use a sonar interface
to read from the sensors instead of a buggy ir?
I know it's not so elegant but my deadlines are scary... ;)

Luca:)

On Nov 22, 2007 1:32 AM, Toby Collett <tco...@pl...> wrote:

> Yes I was suggesting some of the problem might be in the client proxy,
> which you could isolate by using stage (if it supports the ir interface). If
> it doesnt work in stage, then it is not an issue with the Khepera driver, if
> it does work in stage then it most likely and issue in the khepera driver,
>
>
> Toby
>
> On 22/11/2007, xbill (Luca,) <xb...@gm...> wrote:
> >
> > I don't understand properly your question.
> > I'm not working with Stage. I use a real Khepera II controlled by
> > Player.
> > Yeah, I've seen it's not a frequently used interface. What do you mean
> > by "client end of the connection"? Should I debug the IrProxy class?
> >
> > I'll go and see.
> >
> > The encoding problem was actually about the voltages_count.
> >
> > Stay tuned, thanks a lot!
> >
> > Luca;)
> >
> >
> >
> > On Nov 21, 2007 8:32 PM, Toby Collett < tco...@pl...>
> > wrote:
> >
> > > Hi,
> > > didnt see your subsequent post. Are their any IR models in stage, it
> > > is possible there is a bug in the client end of the IR connection, it is not
> > > a frequently used interface (infact apart from the rflex and khepera drivers
> > > I am not sure which others use it...)
> > >
> > > Toby
> > >
> > >
> > > On 22/11/2007, Toby Collett < tco...@pl...> wrote:
> > > >
> > > > Hi,
> > > > Thanks for all your work on this, have you tried to use the player
> > > > CVS version? the position_addr -> ir_addr change seem correct, it must have
> > > > been a copy+paste error, but I am not sure why it is not encoding correctly.
> > > > The only thing I can think of is to check in Khepera::UpdateData() that the
> > > > ranges_count and voltages_count is being set correctly...
> > > >
> > > > Toby
> > > >
> > > > On 22/11/2007, xbill (Luca,) < xb...@gm...> wrote:
> > > >
> > > > > Hello everybody,
> > > > > I keep on debugging the khepera class of Player 2.0.3 and I am
> > > > > stalled on a weird problem about IR sensor readings.
> > > > > I see that the values are correctly collected from Player and
> > > > > stored into a player_ir_data_t variable but they get lost when
> > > > > sent to the function
> > > > >   Publish(position_addr,NULL,PLAYER_MSGTYPE_DATA,
> > > > > PLAYER_IR_DATA_RANGES, (unsigned char *) &ir_data, sizeof(ir_data) ,NULL);
> > > > > so they don't get to the IrProxy->GetRange(i) method (that return
> > > > > zero values).
> > > > > I thought the problem was because of the position_addr so I
> > > > > changed it to ir_addr but I get a player error like
> > > > > warning : encoding failed on message from 22:0 with type 1:1
> > > > > Does anybody have an idea of what I could do to fix this?
> > > > >
> > > > > I will make the diff patch public as soon as possible, the fixes I
> > > > > have made so far are not stable yet...
> > > > >
> > > > > Thank you very much!
> > > > >
> > > > > Luca;)
> > > > >
> > > > >
> > > > > -------------------------------------------------------------------------
> > > > > This SF.net email is sponsored by: Microsoft
> > > > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > _______________________________________________
> > > > > Playerstage-users mailing list
> > > > > Pla...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/playerstage-users
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > This email is intended for the addressee only and may contain
> > > > privileged and/or confidential information
> > >
> > >
> > >
> > >
> > > --
> > > This email is intended for the addressee only and may contain
> > > privileged and/or confidential information
> > >
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > Playerstage-users mailing list
> > > Pla...@li...
> > > https://lists.sourceforge.net/lists/listinfo/playerstage-users
> > >
> > >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Playerstage-users mailing list
> > Pla...@li...
> > https://lists.sourceforge.net/lists/listinfo/playerstage-users
> >
> >
>
>
> --
> This email is intended for the addressee only and may contain privileged
> and/or confidential information
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Playerstage-users mailing list
> Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/playerstage-users
>
>