Re: [Roboticsprimer-users] problems in intro

[Robotics P. u. h. l. <rob...@li...>]

Hi John,

> 7)I am assuming the Load proxy messages on the desktop means that some
> messaging
> got back from the gumstix. If I change the .cfg file on the gumstix I get
> different number of proxies. Does this seem reasonable to you?

Yes, this seems reasonable.

> 8) I have the same version 2.0.4 of player on my desktop and on the gumstix.
> However I am only running it on the gumstix. I assume you ask this to see if
> intro would link with the correct librarys. I am only running intro on
> desktop. If I need anything else please advise.

Yes, I was just making sure that you were linking against the correct libraries.

> 9)Some one suggested that I run player on the desktop and socat on desktop
> and gumstix to avoid the player comm problems. Do you have any experience
> with this?

I'm not familiar with socat. I'm pretty sure the problem is with the
intro code. One real easy way to test the comms, is to run player on
the gumstix, and then connect to the gumstix from your desktop using
playerv.

> 10)Do you know what
> warning : Unhandled message for driver device=16777343:6665:4:0 type=3
> subtype=2 len=1
>
> warning : Unhandled message for driver device=16777343:6665:4:0 type=3
> subtype=2 len=1
> means comming from player on the gumstix? Could this be the requests that it
> gets NACKed?

These messages mean that a device driver on the gumstix did not handle
a message. This is most likely not important, just a warning.

> 11) The segment fault in intro indicates to me something is BAD in intro. I
> assume that it would just terminate if it can't talk to player, or ignore
> it. Is this expected behaviour of intro? If so in what circumstances?

A segfault means that my intro code is bad. I'll have to look into it
once I get all my gumstix equipment back (hopefully sometime today).

> 12)Can you tell me which versions of player, gumstix-buildroot, Linux etc
> you have tested this with?

At the time we used Player CVS. This was a year ago, so there could be
some incompatibility issues now. Again, once I get my hardware back
I'll test everything out again, and track down the problem in the
intro code.

-nate