Hi All, here are few notes I took during of today's call (please correct if I reported something wrong). - Discussion on proposal to use CoAP protocol for FIROS o Presentation of slides (particularly 11 and 12) by Fernando & Jose - Comment by Pier o Will FIROS have in the short term CoAP and in the long term NGSI interface? - Messages exchanged through the FIROS Interface o Pdf Document by Fernando & Jose § Position of the robot § PointStamped § Etc - Comment by Roberto: with this definition FIROS seems a sort of driver, rather than a bridge o In his opinion it should really become a bridge, and not only a driver, to make the connection to CB o It should also extend to other kind of data § This is what is assumed by ET too o Since ROS is based on pbsub paradigm, and CB does the same, FIROS should be able to translate from northbound to southbound keeping the paradigm o ROSBridge is an example of socket-based translation in ROS - Comment by Fernando: it is not valuable translate everything · There are CB limitations in size of messages · ROS doesn't have context information, which is required by CB - Roberto: there are kind of data that should be conveyed to CB, take example of roomba device (position, battery, etc) - Fernando: but batterly level is probably to ba managed by RCM - We agree that there was a misalignment: o Pier/Roberto considered the use of FIROS without RCM o Fernando/Jose with it We should answer the question 'What kind of information we want to publish on CB' - Comment by Pier: o In addition to FIROS interfacing, a further interface needs to be available in RCM for management of platform components lifecycle o This doesn't duplicate the connection through FIROS (i.e. no data conveyed to CB are passing through it), but it is complementary - Roberto: o The high availability of robots is to be managed by the RCM § e.g. watchdog system to check network connections - Pier: o Proposal of AP to describe the capabilities of the robotics components in a textual format (Word Document) o This will help clarify the functionality and interfacing expected, as well as list the possible unknowns to be addressed AP: Provide document to be exchanged by the end of the week containing: - A List of capabilities of FIROS and RCM: - A list of questions/comments/doubts which we should then address: o AP: ET to describe the part concerning FIROS o AP: TI to describe the part concerning RCM o Deadline: Fri 7th, then document is shared BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20141103/61182bd8/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20141103/61182bd8/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy