On Sun, Oct 16, 2011 at 2:20 PM, Maxim Taschew <
maxim@taschew.de> wrote:
> ROS Service Definition (common_msgs) for Camera Parameters
> (FPS,Whitebalance, etc).****
>
> Hi ROS Users,****
>
> I’m currently working on a ros driver for a camera.
> I could use the listed common_msgs image, camera_info, setCameraInfo to
> create my driver to some sort of - let’s say standard ;). So far so good.*
> ***
>
> However last week I came across the issues of parameterizing my camera in
> terms of FPS, Whitebalance, Gain, ROI and so on. Unfortunately there isn’t
> any suggestion about parameterizing made in the camera_driver part in ROS.
> ****
>
> And this leads to my question:****
>
> Wouldn’t it make sense to have a parameter service message for Cameras in
> the common_msg stack? This could include values like fps, roi, encoding and
> so on. This way the parameters of a camera could be set way more generic.
> For example with a parameterizing node, this could be used for any camera
> node that has this parameter service.****
>
> Of course every camera has different parameters which can be set or not.
> This problem could be solved with a camera_parameter_info message. This
> message may keep information about supported parameters for the device. For
> instance FPS (yes,no) and FPS min and max Values.****
>
> Here is a very “cheap” (sry, it’s Sunday!!) picture to give visual support.
> ****
>
> http://img830.imageshack.us/img830/8985/cameraparameter.jpg****
>
> ** **
>
> So what do you think about
>
Have you taken a look at how the existing drivers such as camera1394 use
dynamic_reconfigure? There was also discussion in the Fuerte Drivers SIG
about ways to extend dynamic_reconfigure that may be relevant. See the links
here:
http://www.ros.org/wiki/fuerte/Planning/Drivers#Proposed_new_features
- Eric
> ****
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
%20for%20Camera%0A%20Parameters%20(FPS,%20Whitebalance,%20etc).&References=CAOtrKvkcqvn7LqVMC0tsvuvnWmr6Khzy1ZQSHB22jTUr_hquOg@mail.gmail.com&In-Reply-To=CAOtrKvkcqvn7LqVMC0tsvuvnWmr6Khzy1ZQSHB22jTUr_hquOg@mail.gmail.com&CC=%22User%20discussions%22%20<ros-users@code.ros.org>,%20%22User%20discussions%22%20<ros-users@code.ros.org>&Body=2011-10-16%2011:42,%20skrev%20User%20discussions:%0A>%20On%20Sun,%20Oct%2016,%202011%20at%202:20%20PM,%20Maxim%20Taschew%20<maxim@taschew.de>%20wrote:%0A>%20%0A>%20>%20ROS%20Service%20Definition%20(common_msgs)%20for%20Camera%20Parameters%0A>%20>%20(FPS,Whitebalance,%20etc).****%0A>%20>%0A>%20>%20Hi%20ROS%20Users,****%0A>%20>%0A>%20>%20I%E2%80%99m%20currently%20working%20on%20a%20ros%20driver%20for%20a%20camera.%0A>%20>%20I%20could%20use%20the%20listed%20common_msgs%20image,%20camera_info,%20setCameraInfo%20to%0A>%20>%20create%20my%20driver%20to%20some%20sort%20of%20-%20let%E2%80%99s%20say%20standard%20;).%20So%20far%20so%20good.*%0A>%20>%20***%0A>%20>%0A>%20>%20However%20last%20week%20I%20came%20across%20the%20issues%20of%20parameterizing%20my%20camera%20in%0A>%20>%20terms%20of%20FPS,%20Whitebalance,%20Gain,%20ROI%20and%20so%20on.%20Unfortunately%20there%20isn%E2%80%99t%0A>%20>%20any%20suggestion%20about%20parameterizing%20made%20in%20the%20camera_driver%20part%20in%20ROS.%0A>%20>%20****%0A>%20>%0A>%20>%20And%20this%20leads%20to%20my%20question:****%0A>%20>%0A>%20>%20Wouldn%E2%80%99t%20it%20make%20sense%20to%20have%20a%20parameter%20service%20message%20for%20Cameras%20in%0A>%20>%20the%20common_msg%20stack?%20This%20could%20include%20values%20like%20fps,%20roi,%20encoding%20and%0A>%20>%20so%20on.%20This%20way%20the%20parameters%20of%20a%20camera%20could%20be%20set%20way%20more%20generic.%0A>%20>%20For%20example%20with%20a%20parameterizing%20node,%20this%20could%20be%20used%20for%20any%20camera%0A>%20>%20node%20that%20has%20this%20parameter%20service.****%0A>%20>%0A>%20>%20Of%20course%20every%20camera%20has%20different%20parameters%20which%20can%20be%20set%20or%20not.%0A>%20>%20This%20problem%20could%20be%20solved%20with%20a%20camera_parameter_info%20message.%20This%0A>%20>%20message%20may%20keep%20information%20about%20supported%20parameters%20for%20the%20device.%20%20For%0A>%20>%20instance%20FPS%20(yes,no)%20and%20FPS%20min%20and%20max%20Values.****%0A>%20>%0A>%20>%20Here%20is%20a%20very%20%E2%80%9Ccheap%E2%80%9D%20(sry,%20it%E2%80%99s%20Sunday!!)%20picture%20to%20give%20visual%20support.%0A>%20>%20****%0A>%20>%0A>%20>%20http://img830.imageshack.us/img830/8985/cameraparameter.jpg****%0A>%20>%0A>%20>%20**%20**%0A>%20>%0A>%20>%20So%20what%20do%20you%20think%20about%0A>%20>%0A>%20%0A>%20Have%20you%20taken%20a%20look%20at%20how%20the%20existing%20drivers%20such%20as%20camera1394%20use%0A>%20dynamic_reconfigure?%20There%20was%20also%20discussion%20in%20the%20Fuerte%20Drivers%20SIG%0A>%20about%20ways%20to%20extend%20dynamic_reconfigure%20that%20may%20be%20relevant.%20See%20the%20links%0A>%20here:%20http://www.ros.org/wiki/fuerte/Planning/Drivers#Proposed_new_features%0A>%20%0A>%20-%20Eric%0A>%20%0A>%20%0A>%20>%20****%0A>%20>%0A>%20>%20_______________________________________________%0A>%20>%20ros-users%20mailing%20list%0A>%20>%20ros-users@code.ros.org%0A>%20>%20https://code.ros.org/mailman/listinfo/ros-users%0A>%20>%0A>%20>%0A>%20 "Besvar denne besked")
(text/plain)