All, I'm going to throw this out there for discussion since I have struggled with it myself. Do we really need message types for simple analog values, such as humidity or pressure. Is it enough to just have an analog message (I believe there is one already) with an appropriate topic name. The main reason for my dilemma is that you can write some pretty generic nodes, say filtering for example, that can work on any analog value. If we create special messages for each type of analog value, then a generic node becomes more difficult. Thoughts? Shaun Edwards Senior Research Engineer Manufacturing System Department http://robotics.swri.org http://rosindustrial.swri.org/ http://ros.swri.org Southwest Research Institute 210-522-3277 -----Original Message----- From: ros-users-bounces@code.ros.org [mailto:ros-users-bounces@code.ros.org] On Behalf Of Stephan Wirth Sent: Tuesday, November 13, 2012 4:24 AM To: User discussions Subject: Re: [ros-users] sensor_msgs Low Cost/Android review On Sat, Nov 10, 2012 at 3:24 AM, Chad Rockey wrote: > Hi everyone, > > I'm proposing a few new messages for sensor_msgs. These messages are > intended to provide common, shareable data types for new low cost and > mobile sensing applications. +1! We defined similar Pressure/Humidity messages for our underwater robot due to the lack of standard messages. Stephan -- Stephan Wirth Systems, Robotics and Vision Group Department of Mathematics and Computer Science University of the Balearic Islands http://srv.uib.es _______________________________________________ ros-users mailing list ros-users@code.ros.org https://code.ros.org/mailman/listinfo/ros-users