ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Hi I m new here too.
So...if I understood (I did all the first Tutorials on the ROS Webpage) one should take ROS as a OS, which masters different nodes. So please let me understand better, the idea is: I create one node for one sensor, one node for the controller PID and one node for my motor DC. I let me to start a topic and sensor's node publishs on it. This is going later to be subscribed by the controller which makes some calculation and opens a new topic to feed the motor. The motor reads the right values subscribing to the second topic, which has the values coming form the controller.
I m right? Or I am completely wrong about the way of working of ROS?
I know...it takes time but it is really hard to understand, which is the correlation between ROS (form the tutorials) and a real robot/application
regards
2 | No.2 Revision |
Hi I m new here too.
So...if I understood (I did all the first Tutorials on the ROS Webpage) one should take ROS as a OS, which masters different nodes. So please let me understand better, the idea is: I create one node for one sensor, one node for the controller PID and one node for my motor DC. lets say I let me to start a topic and sensor's node publishs is going to publish on it. This is going later to be subscribed by the controller which makes some calculation and opens a new topic to feed for the motor. The motor reads the right values (for istance: speed) subscribing to the second topic, which has the values coming form the controller.
I m right? Or I am completely wrong about the way of working of ROS?
I know...it takes time but it is really hard to understand, which is the correlation between ROS (form the tutorials) and a real robot/application
regards