Hi everyone, as we said yesterday here you have the documentation of FIROS specs to communicate with RCM. We think there is a misunderstanding about what we consider interface between FIROS and RCM. Just for the sake of clarification, when we talk about FIROS and RCM interfaces, we talk about the information that they need to share to collaborate, not just about the connectivity proccess. We know that FIROS and RCM are ROS nodes and they communicate using ROS. However, we not only need the definition of the communication channel. The data that RCM must provide to do a correct integration between FIROS and RCM is: * The name of the robots * Topics that RCM will provide * The message type of each topic * If we must subscribe to the topic or publish on it So we need to know how RCM provides this data. Attached is a document with the FIROS specifications. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20141211/103cde8d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: FIROSSpecs.pdf Type: application/pdf Size: 105050 bytes Desc: FIROSSpecs.pdf URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20141211/103cde8d/attachment.pdf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy