You could use a passthrough driver, play back the data on its recorded port, and then use passthrough to map this to 6665...

Otherwise you will probably need to modify the code, as the log could have multiple ports that were recorded you would need to provide a mapping from source port to destination. If you do this please submit a patch.

Toby

2009/5/20 Nick Steel <nicholas.steel05@imperial.ac.uk>

After having another stab at this I've worked out what the problem was!  My
log was recorded with a player server running on port 10005 but when I was
trying to play it back, player was running on the default port 6665.  So
playing it back with "player -p 10005" and "playerv -p 10005" worked just
fine. Although there must be a way to map the port 10005 data onto 6665 and
avoid having to run player and the clients on the port the data was recorded
from.  Perhaps you can do something like this in the config?

provides ["6665:laser:0" "log:0"]

Nick


Nick Steel wrote:
>
> I'm sorry to resurrect an old thread but this was never solved and I am
> having the exact same problem.  I ran player on a P3-AT to record a log
> file containing laser and position2d data with the attached recordlog.cfg
> file.  This produced a log which looked fine to me and I have included the
> first few lines in the attached mydata.log file.  I then tried to read the
> laser data back from the log file on my home computer using the following
> player .cfg file:
> driver
> (
>       name "readlog"
>       filename "mydata.log"
>       provides ["laser:0" "position2d:0" "log:0"]
>       speed 2.0
>       autoplay 1
>       autorewind 1
> )
>
> If I then run:
> $ playerv --laser
> I get:
> PlayerViewer 2.1.2
> Connecting to [localhost:6665]
> Available devices: localhost:6665
> log:0            readlog                                 unsupported
> laser:0          readlog                                 subscribed
> playerc error   : got NACK from request
> playerv : error in pv_dev_laser.c
>   libplayerc error: got NACK from request
>
> And a blank playerv window.
>
> If I do "playerprint laser" it doesn't output anything and appears to
> hang.  If i try my client c++ program (below) and debug it seems to wait
> forever at robot.read().  It appears like the readlog is not producing any
> data but I have set autoplay and autorewind and made sure it is playing in
> playervcr.  What am I doing wrong?  Could it be that I recorded the log
> file with player 2.1.1 and I am using version 2.1.2 to play it back and
> that they are incompatible?
>
> Thanks for any ideas.
> Nick
>  http://www.nabble.com/file/p23635563/mydata.log mydata.log
> http://www.nabble.com/file/p23635563/recordlog.cfg recordlog.cfg
> Client C++ snippet:
> PlayerClient robot("localhost");
> LaserProxy lp(&robot, 0);
> robot.Read();
>
>
> Brian Gerkey wrote:
>>
>> Request 1 to the laser interface is getting geometry (size and pose).
>> playerv tries to get this info at the beginning, but should proceed to
>> display data regardless.  Do you get data displayed after the error?
>> How about if you try 'playerprint laser'?
>>
>> It might help if you post the first couple of non-comment lines from
>> your .log.
>>
>>      brian.
>>
>> On Jul 12, 2008, at 3:58 AM, Jonathan Paxman wrote:
>>
>>> Hi,
>>>
>>> I'm having some trouble playing back laser data using readlog.  When I
>>> subscribe to the laser I get this error from playerv:
>>>
>>> "playerc error   : got NACK from request
>>> playerv : error in pv_dev_laser.c
>>>  libplayerc error: got NACK from request"
>>>
>>> and this from the player server:
>>>
>>> "accepted TCP client 0 on port 6665, fd 6
>>> no metadata
>>> warning : Unhandled message for driver device=16777343:6665:laser:0
>>> type=request subtype=1 len=0
>>>
>>> closing TCP connection to client 0 on port 6665"
>>>
>>> The data is from a Hokuyo TOP-URG (UTM) laser, and it views live in
>>> playerv without problems.  Player version is 2.2.0 from SVN.  The
>>> logfile itself looks fine, and the readlog .cfg is very simple:
>>> driver
>>> (
>>>  name "readlog"
>>>  filename "logs/laserdata2008_07_11_13_33_49.log"
>>>  provides ["laser:0"]
>>>  speed 1.0
>>> )
>>>
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>>
>>> Jon
>>>
>>> -------------------------------------------------------------------------
>>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>>> Studies have shown that voting for your favorite open source project,
>>> along with a healthy diet, reduces your potential for chronic lameness
>>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>>> _______________________________________________
>>> Playerstage-users mailing list
>>> Playerstage-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/playerstage-users
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Playerstage-users mailing list
>> Playerstage-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/playerstage-users
>>
>>
>
>

--
View this message in context: http://www.nabble.com/Laser-playback-using-readlog-%28SVN%29-tp18418410p23637244.html
Sent from the playerstage-users mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Playerstage-users mailing list
Playerstage-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/playerstage-users



--
This email is intended for the addressee only and may contain privileged and/or confidential information