A colleague just told me it would be sensible to comment the diagram I
posted, as it could be confusing otherwise. It's illustrating two ways of
interfacing the control subsystem (one or more SOMANET Nodes) with ROS:
1. The SOMANET User App written using rosxmos can communicate directly with
other nodes anywhere in the system using ROS communication techniques,
whether through Ethernet or Ethernet over EtherCAT (EoE).
2. The SOMANET User App written without rosxmos needs a conventional ROS
driver node to bridge communication, e.g. to EtherCAT CoE or some VoE based
protocol (similar to pr2_controllers).
Both are displayed in the same diagram to show that real-time control
commands, if required, still need to be sent in a different way, as ROS
messaging isn't really rt capable. Anyhow the idea is to get rid of rt
communication between the PC running ROS and the control subsystem, by
putting everything that requires real-time behavior down to the
sensor/actuator level and only have intelligence apps left on the PC (what
ROS is good for) that send higher level, non-timing-critical commands to the
distributed control nodes (like a path to move the end effector along).
Nik
-----Ursprüngliche Nachricht-----
Von:
ros-users-bounces@code.ros.org [
mailto:ros-users-bounces@code.ros.org]
Im Auftrag von Nikolai Ensslen
Gesendet: Dienstag, 12. Juni 2012 13:46
An:
ros-users@code.ros.org
Betreff: Re: [ros-users] is a native ROS device possible?
See this diagram for illustration:
http://www.synapticon.com/wp-content/uploads/2012/06/ROS-SOMANET-2.png
%20with%20ROS:%0A>%20%0A>%201.%20The%20SOMANET%20User%20App%20written%20using%20rosxmos%20can%20communicate%20directly%20with%0A>%20other%20nodes%20anywhere%20in%20the%20system%20using%20ROS%20communication%20techniques,%0A>%20whether%20through%20Ethernet%20or%20Ethernet%20over%20EtherCAT%20(EoE).%0A>%20%0A>%202.%20The%20SOMANET%20User%20App%20written%20without%20rosxmos%20needs%20a%20conventional%20ROS%0A>%20driver%20node%20to%20bridge%20communication,%20e.g.%20to%20EtherCAT%20CoE%20or%20some%20VoE%20based%0A>%20protocol%20(similar%20to%20pr2_controllers).%20%0A>%20%0A>%20Both%20are%20displayed%20in%20the%20same%20diagram%20to%20show%20that%20real-time%20control%0A>%20commands,%20if%20required,%20still%20need%20to%20be%20sent%20in%20a%20different%20way,%20as%20ROS%0A>%20messaging%20isn't%20really%20rt%20capable.%20Anyhow%20the%20idea%20is%20to%20get%20rid%20of%20rt%0A>%20communication%20between%20the%20PC%20running%20ROS%20and%20the%20control%20subsystem,%20by%0A>%20putting%20everything%20that%20requires%20real-time%20behavior%20down%20to%20the%0A>%20sensor/actuator%20level%20and%20only%20have%20intelligence%20apps%20left%20on%20the%20PC%20(what%0A>%20ROS%20is%20good%20for)%20that%20send%20higher%20level,%20non-timing-critical%20commands%20to%20the%0A>%20distributed%20control%20nodes%20(like%20a%20path%20to%20move%20the%20end%20effector%20along).%0A>%20%0A>%20Nik%0A>%20%0A>%20-----Urspr%C3%BCngliche%20Nachricht-----%0A>%20Von:%20ros-users-bounces@code.ros.org%20%5Bmailto:ros-users-bounces@code.ros.org%5D%0A>%20Im%20Auftrag%20von%20Nikolai%20Ensslen%0A>%20Gesendet:%20Dienstag,%2012.%20Juni%202012%2013:46%0A>%20An:%20ros-users@code.ros.org%0A>%20Betreff:%20Re:%20%5Bros-users%5D%20is%20a%20native%20ROS%20device%20possible?%0A>%20%0A>%20See%20this%20diagram%20for%20illustration:%0A>%20http://www.synapticon.com/wp-content/uploads/2012/06/ROS-SOMANET-2.png%0A>%20%0A>%20%0A>%20%0A>%20%0A>%20 "Reply to this message")
(text/plain)