Re: [Playerstage-users] What are INTPROP, DBLPROP, STRPROP requests?

[Rich M. <jp...@gm...>]

See the Driver Properties[1] article on the wiki. 

Basically they're a way to get and set driver-specific configuration options
(properties), for example: baudrate, framerate, etc.  They're outside of the
scope of the interfaces since they're driver specific; i.e. a cheapo serial
IMU may not let you change its baudrate or datarate, but a nicer model
might.  It's up to the driver developer to decide which properties to create
& respond to. 

The property requests are all already implemented in the client libraries,
there are some examples on the wiki page above.  Several drivers already
implement property requests, hokuyo_aist[2] and kinect[3] come to mind if
you would like to see some examples.

Rich 

[1] http://playerstage.sourceforge.net/wiki/Driver_Properties
[2]
http://playerstage.sourceforge.net/doc/Player-svn/player/group__driver__hoku
yo__aist.html
[3]
http://playerstage.sourceforge.net/doc/Player-svn/player/group__driver__kine
ct.html

> -----Original Message-----
> From: Alexander Lam [mailto:lam...@us...]
> Sent: Thursday, June 16, 2011 7:17 PM
> To: pla...@li...
> Subject: [Playerstage-users] What are INTPROP, DBLPROP, STRPROP
> requests?
> 
> Hi all,
> 
> What is the purpose of PLAYER_GET_INTPROP_REQ, PLAYER_GET_DBLPROP, and
> friends? Are they to send requests around outside the scope of an
> interface? This is what it seems to me.
> 
> Is it appropriate to expose these in a client library which would be
> operating specific devices only, such as only operating a v4l2 device
> and a hokuyo device? Can these {INT, DBL, STR}PROP messages even leave
> the domain of the player server (if being used)?
> 
> Thanks,
> 
> Alexander Lam
> 16x62 Carnegie Mellon University Mobile Robotics Programming Laboratory