From pierangelo.garino at telecomitalia.it Thu Dec 4 09:50:56 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 4 Dec 2014 08:50:56 +0000 Subject: [Fiware-robotics] FIWARE Robotics Periodic confcall Message-ID: Hi All, I'm unable to join at 10 the call, but I'll be available from 10:30 onwards. I suggest however you start discussing the latest document, then I'll join. BR Pier Hi All, this is the periodic reminder for the Robotics Confcall. We'll stay within 1h of call. We'll use powwownow, numbers to dial can be found at link http://www.powwownow.com/International-DialIn-Numbers/ PIN 075102 BR Pier 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3258 bytes Desc: not available URL: -------------- 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: From ahernandez at ikergune.com Thu Dec 4 09:53:27 2014 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 4 Dec 2014 09:53:27 +0100 Subject: [Fiware-robotics] FIWARE Robotics Periodic confcall Message-ID: Sounds good.. We will be on hangouts as usual. Sent from: Lenovo K910 Garino Pierangelo wrote: Hi All, I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. I suggest however you start discussing the latest document, then I?ll join. BR Pier Hi All, this is the periodic reminder for the Robotics Confcall. We?ll stay within 1h of call. We?ll use powwownow, numbers to dial can be found at link http://www.powwownow.com/International-DialIn-Numbers/ PIN 075102 BR Pier 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. Non stampare questa mail se non ? necessario. From ahernandez at ikergune.com Thu Dec 4 09:57:35 2014 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 4 Dec 2014 09:57:35 +0100 Subject: [Fiware-robotics] FIWARE Robotics Periodic confcall Message-ID: Hello again. We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? 40 minutes should still be enough for today's call. Sent from: Lenovo K910 Angel Hernandez wrote: Sounds good.. We will be on hangouts as usual. Sent from: Lenovo K910 Garino Pierangelo wrote: Hi All, I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. I suggest however you start discussing the latest document, then I?ll join. BR Pier Hi All, this is the periodic reminder for the Robotics Confcall. We?ll stay within 1h of call. We?ll use powwownow, numbers to dial can be found at link http://www.powwownow.com/International-DialIn-Numbers/ PIN 075102 BR Pier 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. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From fherranz at ikergune.com Thu Dec 4 14:19:05 2014 From: fherranz at ikergune.com (Fernando Herranz) Date: Thu, 4 Dec 2014 14:19:05 +0100 Subject: [Fiware-robotics] FIWARE Robotics Periodic confcall References: Message-ID: Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > From roberto1.antonini at telecomitalia.it Thu Dec 4 15:37:24 2014 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 4 Dec 2014 14:37:24 +0000 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I'm wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can't attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I'm unable to join at 10 the call, but I'll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I'll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We'll stay within 1h of call. > > We'll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahernandez at ikergune.com Thu Dec 4 15:51:38 2014 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 4 Dec 2014 15:51:38 +0100 Subject: [Fiware-robotics] FIWARE Robotics Periodic confcall In-Reply-To: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> Message-ID: Hello all, Thank you for the call this morning, I think it went pretty well and has been quite productive :) As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). In order to do so, we should work together and more efficiently tomorrow and Monday, that's why Fernando has requested to have a quick call tomorrow. I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. Talk to you soon, ?ngel. De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] Enviado el: jueves, 4 de diciembre de 2014 15:37 Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I'm wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can't attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I'm unable to join at 10 the call, but I'll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I'll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We'll stay within 1h of call. > > We'll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri Dec 5 09:24:41 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 5 Dec 2014 08:24:41 +0000 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> Message-ID: Dear Angel and All, Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. I would ask Roberto if there's a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. On the other hand, maybe my definition of 'final' architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? Thanks BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 4 dicembre 2014 15:52 A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello all, Thank you for the call this morning, I think it went pretty well and has been quite productive :) As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). In order to do so, we should work together and more efficiently tomorrow and Monday, that's why Fernando has requested to have a quick call tomorrow. I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. Talk to you soon, ?ngel. De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] Enviado el: jueves, 4 de diciembre de 2014 15:37 Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I'm wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can't attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I'm unable to join at 10 the call, but I'll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I'll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We'll stay within 1h of call. > > We'll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From fherranz at ikergune.com Fri Dec 5 10:10:39 2014 From: fherranz at ikergune.com (Fernando Herranz) Date: Fri, 5 Dec 2014 10:10:39 +0100 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, attending to the description of the scenario that we have commented and in order to promote the collaboration between Telecom Italia and Etxe-tar, it's important to start structuring the demo. So, let's identify tasks! We must identify and describe tasks that correspond to our part of the demo. But, it would also be interesting that people from Telecom Italia identify tasks that Etxe-tar needs to accomplish to work with RCM and vice versa. This way we can quickly move forward. It is also interesting if we group tasks attending to their domain i.e. Fiware applications domain, Fiware GEs domains (context broker domain), robotics domain and physical robotics domain. Saying that, let me start identifying tasks: Etxe-tar Side Fiware Applications Domain * Write a MashUp application (python): * Connect to CB * Subscribe the position of the robot Fiware GEs Domain * Context broker * Set up Virtual machine with CB Robotics Domain * FIROS * Connect to CB * Subscribe CB * Subscribe ROS topics (these topics must be defined by Telecom Italia) * Publish on ROS topics (these topics must be defined by Telecom Italia) * Send data to CB Telecom Italia Side Robotics domain * Set up move base and amcl * Identify the topics that must publish in CB * Identify the topics that must subscribe CB * Describe the type of data of the topics Physical robotics domain * Setup turtlebot2 Please, keep adding task that you identify! Just a reminder. Please! since we are to discuss a big part of the demo by mail, try to be as clear as possible and think about the undesirability of your proposals!! Fernando On 04/12/14 15:37, Antonini Roberto wrote: Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Sat Dec 6 08:39:32 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Sat, 6 Dec 2014 07:39:32 +0000 Subject: [Fiware-robotics] R: Re: R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local>, Message-ID: Hi Fernando, Roberto will surely contribute to make sure the demo will be very consistent. The fact we discuss some part by mail cannot be an issue. Can you tell me what you mean by 'think about the undesirability of your proposal'? It sounds bad to me, hope it's only a translation issue. BR Pier Inviato da smartphone Sony Xperia? ---- Fernando Herranz ha scritto ---- Hi all, attending to the description of the scenario that we have commented and in order to promote the collaboration between Telecom Italia and Etxe-tar, it's important to start structuring the demo. So, let's identify tasks! We must identify and describe tasks that correspond to our part of the demo. But, it would also be interesting that people from Telecom Italia identify tasks that Etxe-tar needs to accomplish to work with RCM and vice versa. This way we can quickly move forward. It is also interesting if we group tasks attending to their domain i.e. Fiware applications domain, Fiware GEs domains (context broker domain), robotics domain and physical robotics domain. Saying that, let me start identifying tasks: Etxe-tar Side Fiware Applications Domain * Write a MashUp application (python): * Connect to CB * Subscribe the position of the robot Fiware GEs Domain * Context broker * Set up Virtual machine with CB Robotics Domain * FIROS * Connect to CB * Subscribe CB * Subscribe ROS topics (these topics must be defined by Telecom Italia) * Publish on ROS topics (these topics must be defined by Telecom Italia) * Send data to CB Telecom Italia Side Robotics domain * Set up move base and amcl * Identify the topics that must publish in CB * Identify the topics that must subscribe CB * Describe the type of data of the topics Physical robotics domain * Setup turtlebot2 Please, keep adding task that you identify! Just a reminder. Please! since we are to discuss a big part of the demo by mail, try to be as clear as possible and think about the undesirability of your proposals!! Fernando On 04/12/14 15:37, Antonini Roberto wrote: Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- An HTML attachment was scrubbed... URL: From fherranz at ikergune.com Sat Dec 6 19:59:13 2014 From: fherranz at ikergune.com (Fernando Herranz) Date: Sat, 6 Dec 2014 19:59:13 +0100 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local>, , Message-ID: Hi, Sorry, it was a typo. I meant to say to plesse be clear with the descriptions. Because sometimes it's difficult to understand concepts by email. Have a good weekend! ________________________________________ De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] Enviado el: s?bado, 06 de diciembre de 2014 8:39 Para: Antonini Roberto; Angel Hernandez; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert; Fernando Herranz CC: Gaspardone Marco; I?igo Gonzalez Asunto: R: Re: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi Fernando, Roberto will surely contribute to make sure the demo will be very consistent. The fact we discuss some part by mail cannot be an issue. Can you tell me what you mean by 'think about the undesirability of your proposal'? It sounds bad to me, hope it's only a translation issue. BR Pier Inviato da smartphone Sony Xperia? ---- Fernando Herranz ha scritto ---- Hi all, attending to the description of the scenario that we have commented and in order to promote the collaboration between Telecom Italia and Etxe-tar, it's important to start structuring the demo. So, let's identify tasks! We must identify and describe tasks that correspond to our part of the demo. But, it would also be interesting that people from Telecom Italia identify tasks that Etxe-tar needs to accomplish to work with RCM and vice versa. This way we can quickly move forward. It is also interesting if we group tasks attending to their domain i.e. Fiware applications domain, Fiware GEs domains (context broker domain), robotics domain and physical robotics domain. Saying that, let me start identifying tasks: Etxe-tar Side Fiware Applications Domain * Write a MashUp application (python): * Connect to CB * Subscribe the position of the robot Fiware GEs Domain * Context broker * Set up Virtual machine with CB Robotics Domain * FIROS * Connect to CB * Subscribe CB * Subscribe ROS topics (these topics must be defined by Telecom Italia) * Publish on ROS topics (these topics must be defined by Telecom Italia) * Send data to CB Telecom Italia Side Robotics domain * Set up move base and amcl * Identify the topics that must publish in CB * Identify the topics that must subscribe CB * Describe the type of data of the topics Physical robotics domain * Setup turtlebot2 Please, keep adding task that you identify! Just a reminder. Please! since we are to discuss a big part of the demo by mail, try to be as clear as possible and think about the undesirability of your proposals!! Fernando On 04/12/14 15:37, Antonini Roberto wrote: Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From fherranz at ikergune.com Tue Dec 9 09:28:18 2014 From: fherranz at ikergune.com (Fernando Herranz) Date: Tue, 9 Dec 2014 09:28:18 +0100 Subject: [Fiware-robotics] FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , Message-ID: Hello! I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! ________________________________________ De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] Enviado el: viernes, 05 de diciembre de 2014 9:24 Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Dear Angel and All, Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? Thanks BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 4 dicembre 2014 15:52 A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello all, Thank you for the call this morning, I think it went pretty well and has been quite productive ? As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. Talk to you soon, ?ngel. De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] Enviado el: jueves, 4 de diciembre de 2014 15:37 Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From pierangelo.garino at telecomitalia.it Tue Dec 9 09:46:03 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 9 Dec 2014 08:46:03 +0000 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , Message-ID: Hi Fernando, for me it's fine postponing (3pm is preferred), is it ok for the others too? BR Pier -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: marted? 9 dicembre 2014 09:28 A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello! I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! ________________________________________ De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] Enviado el: viernes, 05 de diciembre de 2014 9:24 Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Dear Angel and All, Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? Thanks BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 4 dicembre 2014 15:52 A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello all, Thank you for the call this morning, I think it went pretty well and has been quite productive ? As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. Talk to you soon, ?ngel. De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] Enviado el: jueves, 4 de diciembre de 2014 15:37 Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From roberto1.antonini at telecomitalia.it Tue Dec 9 11:26:20 2014 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Tue, 9 Dec 2014 10:26:20 +0000 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , Message-ID: <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> Hi all, for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. My best, R -----Messaggio originale----- Da: Garino Pierangelo Inviato: marted? 9 dicembre 2014 09:46 A: Fernando Herranz; Angel Hernandez; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi Fernando, for me it's fine postponing (3pm is preferred), is it ok for the others too? BR Pier -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: marted? 9 dicembre 2014 09:28 A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello! I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! ________________________________________ De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] Enviado el: viernes, 05 de diciembre de 2014 9:24 Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Dear Angel and All, Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? Thanks BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 4 dicembre 2014 15:52 A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello all, Thank you for the call this morning, I think it went pretty well and has been quite productive ? As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. Talk to you soon, ?ngel. De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] Enviado el: jueves, 4 de diciembre de 2014 15:37 Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics -------------- next part -------------- A non-text attachment was scrubbed... Name: RCM.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 66166 bytes Desc: RCM.pptx URL: From pierangelo.garino at telecomitalia.it Tue Dec 9 16:51:06 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 9 Dec 2014 15:51:06 +0000 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall In-Reply-To: <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> Message-ID: Dear All, Is the option proposed by Roberto for a call tomorrow morning feasible for you, i.e. Wednesday 10/12 at 10 CET? BR Pier -----Messaggio originale----- Da: Antonini Roberto Inviato: marted? 9 dicembre 2014 11:26 A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco; Colombatto Davide Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi all, for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. My best, R -----Messaggio originale----- Da: Garino Pierangelo Inviato: marted? 9 dicembre 2014 09:46 A: Fernando Herranz; Angel Hernandez; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi Fernando, for me it's fine postponing (3pm is preferred), is it ok for the others too? BR Pier -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: marted? 9 dicembre 2014 09:28 A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello! I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! ________________________________________ De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] Enviado el: viernes, 05 de diciembre de 2014 9:24 Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Dear Angel and All, Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? Thanks BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: gioved? 4 dicembre 2014 15:52 A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Cc: Gaspardone Marco Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello all, Thank you for the call this morning, I think it went pretty well and has been quite productive ? As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. Talk to you soon, ?ngel. De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] Enviado el: jueves, 4 de diciembre de 2014 15:37 Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert CC: Gaspardone Marco Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall Hi, Finally we are at end of the road ... The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) ? Robot pose The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. BR R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz Inviato: gioved? 4 dicembre 2014 14:19 A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall Hello, at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: Etxe-Tar part: Develop a naive mashup application in FIWARE that publish in the context broker a position (goal) to command a robot Detailed explanation of the robot instance in the context broker for Telecom Italia Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia Telecom Italia part: Set-up the simplest RCM architecture to command a robot (turtlebot or PR2 or another robot that you can control) Detailed explanation of the set-up process for Etxe-Tar Name and type of the topic that FIROS has to subscribe We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? Cheers On 04/12/14 09:57, Angel Hernandez wrote: > Hello again. > We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? > 40 minutes should still be enough for today's call. > > > Sent from: Lenovo K910 > > Angel Hernandez > wrote: > > > Sounds good.. We will be on hangouts as usual. > > > > Sent from: Lenovo K910 > > Garino Pierangelo > wrote: > > > Hi All, > I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. > I suggest however you start discussing the latest document, then I?ll join. > > BR > Pier > > > > Hi All, > > this is the periodic reminder for the Robotics Confcall. > > We?ll stay within 1h of call. > > We?ll use powwownow, numbers to dial can be found at link > http://www.powwownow.com/International-DialIn-Numbers/ > > PIN 075102 > > > BR > Pier > > > > 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. Non stampare questa mail se non ? necessario. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From fherranz at ikergune.com Tue Dec 9 16:54:38 2014 From: fherranz at ikergune.com (Fernando Herranz) Date: Tue, 9 Dec 2014 16:54:38 +0100 Subject: [Fiware-robotics] R: FIWARE Robotics Periodic confcall References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> Message-ID: It's ok for us! On 09/12/14 16:51, Garino Pierangelo wrote: > Dear All, > > Is the option proposed by Roberto for a call tomorrow morning feasible for you, i.e. Wednesday 10/12 at 10 CET? > > BR > Pier > > > -----Messaggio originale----- > Da: Antonini Roberto > Inviato: marted? 9 dicembre 2014 11:26 > A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco; Colombatto Davide > Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hi all, > for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. > If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. > > As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. > For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. > > My best, > R > > -----Messaggio originale----- > Da: Garino Pierangelo > Inviato: marted? 9 dicembre 2014 09:46 > A: Fernando Herranz; Angel Hernandez; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hi Fernando, > for me it's fine postponing (3pm is preferred), is it ok for the others too? > BR > Pier > > > -----Messaggio originale----- > Da: Fernando Herranz [mailto:fherranz at ikergune.com] > Inviato: marted? 9 dicembre 2014 09:28 > A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hello! > > I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! > > > ________________________________________ > De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] > Enviado el: viernes, 05 de diciembre de 2014 9:24 > Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > CC: Gaspardone Marco > Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Dear Angel and All, > > Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. > > I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. > > On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. > > Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. > > Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? > > Thanks > > BR > Pier > > > > > Da: Angel Hernandez [mailto:ahernandez at ikergune.com] > Inviato: gioved? 4 dicembre 2014 15:52 > A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hello all, > > Thank you for the call this morning, I think it went pretty well and has been quite productive ? > > As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). > > In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. > > I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. > > Talk to you soon, > ?ngel. > > > De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] > Enviado el: jueves, 4 de diciembre de 2014 15:37 > Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > CC: Gaspardone Marco > Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > > Hi, > > Finally we are at end of the road ... > > > > The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. > > The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: > > ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot > > ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) > > > > FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: > > ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) > > ? Robot pose > > > > The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. > > > > > > Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. > > For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. > > > > BR > > R > > > > > > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Fernando Herranz > Inviato: gioved? 4 dicembre 2014 14:19 > A: Angel Hernandez; Garino Pierangelo; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall > > > > Hello, > > > > at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: > > > > - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. > > > > - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. > > > > Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: > > Etxe-Tar part: > > Develop a naive mashup application in FIWARE that publish in the > > context broker a position (goal) to command a robot > > Detailed explanation of the robot instance in the context broker for Telecom Italia > > Detailed explanation of the translation of a simple message like a pose by FIROS for Telecom Italia > > Telecom Italia part: > > Set-up the simplest RCM architecture to command a robot > > (turtlebot or PR2 or another robot that you can control) > > Detailed explanation of the set-up process for Etxe-Tar > > Name and type of the topic that FIROS has to subscribe > > > > We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? > > > > Cheers > > > > > > > > On 04/12/14 09:57, Angel Hernandez wrote: > >> Hello again. >> We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? >> 40 minutes should still be enough for today's call. >> Sent from: Lenovo K910 >> Angel Hernandez > wrote: >> Sounds good.. We will be on hangouts as usual. >> Sent from: Lenovo K910 >> Garino Pierangelo > wrote: >> Hi All, >> I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. >> I suggest however you start discussing the latest document, then I?ll join. >> BR >> Pier >> Hi All, >> this is the periodic reminder for the Robotics Confcall. >> We?ll stay within 1h of call. >> We?ll use powwownow, numbers to dial can be found at link >> http://www.powwownow.com/International-DialIn-Numbers/ >> PIN 075102 >> BR >> Pier >> 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. Non stampare questa mail se non ? necessario. >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics > > > _______________________________________________ > > Fiware-robotics mailing list > > Fiware-robotics at lists.fi-ware.org > > https://lists.fi-ware.org/listinfo/fiware-robotics > > From pierangelo.garino at telecomitalia.it Tue Dec 9 17:05:27 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 9 Dec 2014 16:05:27 +0000 Subject: [Fiware-robotics] R: R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> Message-ID: Great, thanks Fernando. This time I'd like to use the videconference sharing tool whose details are in the attached mail (sorry it's in Italian only, if you have troubles to interpret it, just let me know). Please access via the Webscopia tool from this link http://conference.vaionline.telecomitalia.it/?ID=72730399 to connect through a browser, which appears the best option to use (however also the Microsoft Office Communicator option is usually fine, except for desktop sharing). Occasionally, Firefox doesn't allow to join, in such a case I suggest to use either chrome or IE. The number of connections activated is 5 (two used by us in Torino), I believe the other three should be enough for you, otherwise let me know and I'll try to add extra connections. Talk to you tomorrow! Pier Thanks and BR Pier -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: marted? 9 dicembre 2014 16:55 A: Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: Gaspardone Marco; Colombatto Davide; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: R: [Fiware-robotics] FIWARE Robotics Periodic confcall It's ok for us! On 09/12/14 16:51, Garino Pierangelo wrote: > Dear All, > > Is the option proposed by Roberto for a call tomorrow morning feasible for you, i.e. Wednesday 10/12 at 10 CET? > > BR > Pier > > > -----Messaggio originale----- > Da: Antonini Roberto > Inviato: marted? 9 dicembre 2014 11:26 > A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco; Colombatto Davide > Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hi all, > for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. > If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. > > As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. > For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. > > My best, > R > > -----Messaggio originale----- > Da: Garino Pierangelo > Inviato: marted? 9 dicembre 2014 09:46 > A: Fernando Herranz; Angel Hernandez; Antonini Roberto; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hi Fernando, > for me it's fine postponing (3pm is preferred), is it ok for the others too? > BR > Pier > > > -----Messaggio originale----- > Da: Fernando Herranz [mailto:fherranz at ikergune.com] > Inviato: marted? 9 dicembre 2014 09:28 > A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hello! > > I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! > > > ________________________________________ > De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] > Enviado el: viernes, 05 de diciembre de 2014 9:24 > Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > CC: Gaspardone Marco > Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Dear Angel and All, > > Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. > > I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. > > On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. > > Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. > > Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? > > Thanks > > BR > Pier > > > > > Da: Angel Hernandez [mailto:ahernandez at ikergune.com] > Inviato: gioved? 4 dicembre 2014 15:52 > A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hello all, > > Thank you for the call this morning, I think it went pretty well and > has been quite productive ? > > As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). > > In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. > > I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. > > Talk to you soon, > ?ngel. > > > De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] > Enviado el: jueves, 4 de diciembre de 2014 15:37 > Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > CC: Gaspardone Marco > Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > > Hi, > > Finally we are at end of the road ... > > > > The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. > > The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: > > ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot > > ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) > > > > FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: > > ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) > > ? Robot pose > > > > The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. > > > > > > Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. > > For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. > > > > BR > > R > > > > > > > > -----Messaggio originale----- > Da: > fiware-robotics-bounces at lists.fi-ware.org es at lists.fi-ware.org> > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di > Fernando Herranz > Inviato: gioved? 4 dicembre 2014 14:19 > A: Angel Hernandez; Garino Pierangelo; > fiware-robotics at lists.fi-ware.org .org>; Thomas Michael Bohnert > Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall > > > > Hello, > > > > at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: > > > > - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. > > > > - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. > > > > Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: > > Etxe-Tar part: > > Develop a naive mashup application in FIWARE that publish in > the > > context broker a position (goal) to command a robot > > Detailed explanation of the robot instance in the context > broker for Telecom Italia > > Detailed explanation of the translation of a simple message > like a pose by FIROS for Telecom Italia > > Telecom Italia part: > > Set-up the simplest RCM architecture to command a robot > > (turtlebot or PR2 or another robot that you can control) > > Detailed explanation of the set-up process for Etxe-Tar > > Name and type of the topic that FIROS has to subscribe > > > > We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? > > > > Cheers > > > > > > > > On 04/12/14 09:57, Angel Hernandez wrote: > >> Hello again. >> We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? >> 40 minutes should still be enough for today's call. >> Sent from: Lenovo K910 >> Angel Hernandez > wrote: >> Sounds good.. We will be on hangouts as usual. >> Sent from: Lenovo K910 >> Garino Pierangelo > wrote: >> Hi All, >> I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. >> I suggest however you start discussing the latest document, then I?ll join. >> BR >> Pier >> Hi All, >> this is the periodic reminder for the Robotics Confcall. >> We?ll stay within 1h of call. >> We?ll use powwownow, numbers to dial can be found at link >> http://www.powwownow.com/International-DialIn-Numbers/ >> PIN 075102 >> BR >> Pier >> 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. Non stampare questa mail se non ? necessario. >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org> e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org> e.org> https://lists.fi-ware.org/listinfo/fiware-robotics > > > _______________________________________________ > > Fiware-robotics mailing list > > Fiware-robotics at lists.fi-ware.org .org> > > https://lists.fi-ware.org/listinfo/fiware-robotics > > -------------- next part -------------- An embedded message was scrubbed... From: VAIONLINE Prenotazioni Subject: VAIONLINE - CONFERMA DI AVVENUTA MODIFICA PRENOTAZIONE N.730399- TELECOM ITALIA CONFIDENZIALE - Date: Tue, 9 Dec 2014 15:59:09 +0000 Size: 20254 URL: From pierangelo.garino at telecomitalia.it Wed Dec 10 12:15:03 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 10 Dec 2014 11:15:03 +0000 Subject: [Fiware-robotics] R: R: R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> Message-ID: Hi All, Here https://docs.google.com/document/d/1XpIUUFzZpKgf7tTd6YvFcgZNs6N4JpXW2CunI0GGcmo/edit?usp=sharing is the link to a short summary I took during the call, I have rearranged a bit the items to make them more homogeneous. Please refine the summary if you feel it necessary, just inform the others if you do it so that we know they are updated. Thanks and BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: marted? 9 dicembre 2014 17:05 A: Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: R: FIWARE Robotics Periodic confcall Great, thanks Fernando. This time I'd like to use the videconference sharing tool whose details are in the attached mail (sorry it's in Italian only, if you have troubles to interpret it, just let me know). Please access via the Webscopia tool from this link http://conference.vaionline.telecomitalia.it/?ID=72730399 to connect through a browser, which appears the best option to use (however also the Microsoft Office Communicator option is usually fine, except for desktop sharing). Occasionally, Firefox doesn't allow to join, in such a case I suggest to use either chrome or IE. The number of connections activated is 5 (two used by us in Torino), I believe the other three should be enough for you, otherwise let me know and I'll try to add extra connections. Talk to you tomorrow! Pier Thanks and BR Pier -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: marted? 9 dicembre 2014 16:55 A: Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: Gaspardone Marco; Colombatto Davide; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert Oggetto: Re: R: [Fiware-robotics] FIWARE Robotics Periodic confcall It's ok for us! On 09/12/14 16:51, Garino Pierangelo wrote: > Dear All, > > Is the option proposed by Roberto for a call tomorrow morning feasible for you, i.e. Wednesday 10/12 at 10 CET? > > BR > Pier > > > -----Messaggio originale----- > Da: Antonini Roberto > Inviato: marted? 9 dicembre 2014 11:26 > A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco; Colombatto Davide > Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hi all, > for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. > If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. > > As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. > For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. > > My best, > R > > -----Messaggio originale----- > Da: Garino Pierangelo > Inviato: marted? 9 dicembre 2014 09:46 > A: Fernando Herranz; Angel Hernandez; Antonini Roberto; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hi Fernando, > for me it's fine postponing (3pm is preferred), is it ok for the others too? > BR > Pier > > > -----Messaggio originale----- > Da: Fernando Herranz [mailto:fherranz at ikergune.com] > Inviato: marted? 9 dicembre 2014 09:28 > A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hello! > > I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! > > > ________________________________________ > De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] > Enviado el: viernes, 05 de diciembre de 2014 9:24 > Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > CC: Gaspardone Marco > Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Dear Angel and All, > > Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. > > I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. > > On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. > > Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. > > Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? > > Thanks > > BR > Pier > > > > > Da: Angel Hernandez [mailto:ahernandez at ikergune.com] > Inviato: gioved? 4 dicembre 2014 15:52 > A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Cc: Gaspardone Marco > Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall > > Hello all, > > Thank you for the call this morning, I think it went pretty well and > has been quite productive ? > > As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). > > In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. > > I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. > > Talk to you soon, > ?ngel. > > > De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] > Enviado el: jueves, 4 de diciembre de 2014 15:37 > Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > CC: Gaspardone Marco > Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > > Hi, > > Finally we are at end of the road ... > > > > The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. > > The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: > > ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot > > ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) > > > > FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: > > ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) > > ? Robot pose > > > > The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. > > > > > > Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. > > For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. > > > > BR > > R > > > > > > > > -----Messaggio originale----- > Da: > fiware-robotics-bounces at lists.fi-ware.org es at lists.fi-ware.org> > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di > Fernando Herranz > Inviato: gioved? 4 dicembre 2014 14:19 > A: Angel Hernandez; Garino Pierangelo; > fiware-robotics at lists.fi-ware.org .org>; Thomas Michael Bohnert > Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall > > > > Hello, > > > > at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: > > > > - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. > > > > - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. > > > > Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: > > Etxe-Tar part: > > Develop a naive mashup application in FIWARE that publish in > the > > context broker a position (goal) to command a robot > > Detailed explanation of the robot instance in the context > broker for Telecom Italia > > Detailed explanation of the translation of a simple message > like a pose by FIROS for Telecom Italia > > Telecom Italia part: > > Set-up the simplest RCM architecture to command a robot > > (turtlebot or PR2 or another robot that you can control) > > Detailed explanation of the set-up process for Etxe-Tar > > Name and type of the topic that FIROS has to subscribe > > > > We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? > > > > Cheers > > > > > > > > On 04/12/14 09:57, Angel Hernandez wrote: > >> Hello again. >> We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? >> 40 minutes should still be enough for today's call. >> Sent from: Lenovo K910 >> Angel Hernandez > wrote: >> Sounds good.. We will be on hangouts as usual. >> Sent from: Lenovo K910 >> Garino Pierangelo > wrote: >> Hi All, >> I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. >> I suggest however you start discussing the latest document, then I?ll join. >> BR >> Pier >> Hi All, >> this is the periodic reminder for the Robotics Confcall. >> We?ll stay within 1h of call. >> We?ll use powwownow, numbers to dial can be found at link >> http://www.powwownow.com/International-DialIn-Numbers/ >> PIN 075102 >> BR >> Pier >> 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. Non stampare questa mail se non ? necessario. >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org> e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org> e.org> https://lists.fi-ware.org/listinfo/fiware-robotics > > > _______________________________________________ > > Fiware-robotics mailing list > > Fiware-robotics at lists.fi-ware.org .org> > > https://lists.fi-ware.org/listinfo/fiware-robotics > > From igonzalez at ikergune.com Wed Dec 10 13:32:07 2014 From: igonzalez at ikergune.com (=?utf-8?B?ScOxaWdvIEdvbnphbGV6?=) Date: Wed, 10 Dec 2014 13:32:07 +0100 Subject: [Fiware-robotics] R: R: R: FIWARE Robotics Periodic confcall References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> Message-ID: Hi, we have created a document with Firos roadmap, you can find it here: https://docs.google.com/document/d/1HNHBiK74Oo6lJfBvNwHBum2CUVijrvTbDc6rJm3A1gs/edit?usp=sharing As we have been talking about Firos - RCM integration and some of the Action Points of the last call are related with it, we think it is interesting to share technical specification documents of the interfaces provided by both modules (southbound FIROS interface and northbound RCM interface). We are working on the FIROS interface specification document and we plan to send it to you tomorrow. It can help you to understand how we expect RCM communicates with FIROS but we also need information about RCM interface. It would be great that youy guys send us this information before next call. This way we can work on the integration of Firos with RCM and discuss about it on the call. Regards, I?igo El 10/12/14 a las 12:15, Garino Pierangelo escribi?: > Hi All, > > Here https://docs.google.com/document/d/1XpIUUFzZpKgf7tTd6YvFcgZNs6N4JpXW2CunI0GGcmo/edit?usp=sharing is the link to a short summary I took during the call, I have rearranged a bit the items to make them more homogeneous. > Please refine the summary if you feel it necessary, just inform the others if you do it so that we know they are updated. > > Thanks and BR > Pier > > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo > Inviato: marted? 9 dicembre 2014 17:05 > A: Fernando Herranz; Angel Hernandez; Jose Jaime Ariza > Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide > Oggetto: [Fiware-robotics] R: R: FIWARE Robotics Periodic confcall > > Great, thanks Fernando. > > This time I'd like to use the videconference sharing tool whose details are in the attached mail (sorry it's in Italian only, if you have troubles to interpret it, just let me know). > Please access via the Webscopia tool from this link http://conference.vaionline.telecomitalia.it/?ID=72730399 to connect through a browser, which appears the best option to use (however also the Microsoft Office Communicator option is usually fine, except for desktop sharing). Occasionally, Firefox doesn't allow to join, in such a case I suggest to use either chrome or IE. > > The number of connections activated is 5 (two used by us in Torino), I believe the other three should be enough for you, otherwise let me know and I'll try to add extra connections. > > Talk to you tomorrow! > Pier > > > > > Thanks and BR > Pier > > > > > -----Messaggio originale----- > Da: Fernando Herranz [mailto:fherranz at ikergune.com] > Inviato: marted? 9 dicembre 2014 16:55 > A: Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza > Cc: Gaspardone Marco; Colombatto Davide; Antonini Roberto; fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Oggetto: Re: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > It's ok for us! > > On 09/12/14 16:51, Garino Pierangelo wrote: >> Dear All, >> >> Is the option proposed by Roberto for a call tomorrow morning feasible for you, i.e. Wednesday 10/12 at 10 CET? >> >> BR >> Pier >> >> >> -----Messaggio originale----- >> Da: Antonini Roberto >> Inviato: marted? 9 dicembre 2014 11:26 >> A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco; Colombatto Davide >> Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hi all, >> for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. >> If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. >> >> As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. >> For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. >> >> My best, >> R >> >> -----Messaggio originale----- >> Da: Garino Pierangelo >> Inviato: marted? 9 dicembre 2014 09:46 >> A: Fernando Herranz; Angel Hernandez; Antonini Roberto; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hi Fernando, >> for me it's fine postponing (3pm is preferred), is it ok for the others too? >> BR >> Pier >> >> >> -----Messaggio originale----- >> Da: Fernando Herranz [mailto:fherranz at ikergune.com] >> Inviato: marted? 9 dicembre 2014 09:28 >> A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hello! >> >> I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! >> >> >> ________________________________________ >> De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] >> Enviado el: viernes, 05 de diciembre de 2014 9:24 >> Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> CC: Gaspardone Marco >> Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Dear Angel and All, >> >> Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. >> >> I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. >> >> On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. >> >> Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. > >> Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? >> >> Thanks >> >> BR >> Pier >> >> >> >> >> Da: Angel Hernandez [mailto:ahernandez at ikergune.com] >> Inviato: gioved? 4 dicembre 2014 15:52 >> A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hello all, >> >> Thank you for the call this morning, I think it went pretty well and >> has been quite productive ? >> >> As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). >> >> In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. >> >> I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. >> >> Talk to you soon, >> ?ngel. >> >> >> De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] >> Enviado el: jueves, 4 de diciembre de 2014 15:37 >> Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> CC: Gaspardone Marco >> Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> >> Hi, >> >> Finally we are at end of the road ... >> >> >> >> The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. >> >> The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: >> >> ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot >> >> ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) >> >> >> >> FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: >> >> ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) >> >> ? Robot pose >> >> >> >> The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. >> >> >> >> >> >> Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. >> >> For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. >> >> >> >> BR >> >> R >> >> >> >> >> >> >> >> -----Messaggio originale----- >> Da: >> fiware-robotics-bounces at lists.fi-ware.org> es at lists.fi-ware.org> >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> Fernando Herranz >> Inviato: gioved? 4 dicembre 2014 14:19 >> A: Angel Hernandez; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org> .org>; Thomas Michael Bohnert >> Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> >> >> Hello, >> >> >> >> at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: >> >> >> >> - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. >> >> >> >> - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. >> >> >> >> Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: >> >> Etxe-Tar part: >> >> Develop a naive mashup application in FIWARE that publish in >> the >> >> context broker a position (goal) to command a robot >> >> Detailed explanation of the robot instance in the context >> broker for Telecom Italia >> >> Detailed explanation of the translation of a simple message >> like a pose by FIROS for Telecom Italia >> >> Telecom Italia part: >> >> Set-up the simplest RCM architecture to command a robot >> >> (turtlebot or PR2 or another robot that you can control) >> >> Detailed explanation of the set-up process for Etxe-Tar >> >> Name and type of the topic that FIROS has to subscribe >> >> >> >> We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? >> >> >> >> Cheers >> >> >> >> >> >> >> >> On 04/12/14 09:57, Angel Hernandez wrote: >> >>> Hello again. >>> We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? >>> 40 minutes should still be enough for today's call. >>> Sent from: Lenovo K910 >>> Angel Hernandez > wrote: >>> Sounds good.. We will be on hangouts as usual. >>> Sent from: Lenovo K910 >>> Garino Pierangelo > wrote: >>> Hi All, >>> I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. >>> I suggest however you start discussing the latest document, then I?ll join. >>> BR >>> Pier >>> Hi All, >>> this is the periodic reminder for the Robotics Confcall. >>> We?ll stay within 1h of call. >>> We?ll use powwownow, numbers to dial can be found at link >>> http://www.powwownow.com/International-DialIn-Numbers/ >>> PIN 075102 >>> BR >>> Pier >>> 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. Non stampare questa mail se non ? necessario. >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org>> e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org>> e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> _______________________________________________ >> >> Fiware-robotics mailing list >> >> Fiware-robotics at lists.fi-ware.org> .org> >> >> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > From roberto1.antonini at telecomitalia.it Wed Dec 10 14:32:07 2014 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Wed, 10 Dec 2014 13:32:07 +0000 Subject: [Fiware-robotics] R: R: R: R: FIWARE Robotics Periodic confcall In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> Hi all, just for clarity's sake. In our view, as FIROS is a ROS node, the interaction between FIROS and RCM should be the same interaction that RCM has with the other ROS nodes. To be clearer, instead of manually issuing rosrun/roslaunch commands by a Linux Shell, these commands are issued by RCM. Furthermore RCM will be notified when a ROS node goes down (implemented by an own watchdog mechanism). In conclusion: FIROS-CB communication don't concern with RCM, hence it's independent from RCM logic. FIROS-ROS nodes communication follow the well-defined ROS mechanism (e.g. topics pub-sub). I hope we clarified your doubts, we wait for your feedbacks. BR, Davide & Roberto -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: mercoled? 10 dicembre 2014 13:32 A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: Re: [Fiware-robotics] R: R: R: FIWARE Robotics Periodic confcall Hi, we have created a document with Firos roadmap, you can find it here: https://docs.google.com/document/d/1HNHBiK74Oo6lJfBvNwHBum2CUVijrvTbDc6rJm3A1gs/edit?usp=sharing As we have been talking about Firos - RCM integration and some of the Action Points of the last call are related with it, we think it is interesting to share technical specification documents of the interfaces provided by both modules (southbound FIROS interface and northbound RCM interface). We are working on the FIROS interface specification document and we plan to send it to you tomorrow. It can help you to understand how we expect RCM communicates with FIROS but we also need information about RCM interface. It would be great that youy guys send us this information before next call. This way we can work on the integration of Firos with RCM and discuss about it on the call. Regards, I?igo El 10/12/14 a las 12:15, Garino Pierangelo escribi?: > Hi All, > > Here https://docs.google.com/document/d/1XpIUUFzZpKgf7tTd6YvFcgZNs6N4JpXW2CunI0GGcmo/edit?usp=sharing is the link to a short summary I took during the call, I have rearranged a bit the items to make them more homogeneous. > Please refine the summary if you feel it necessary, just inform the others if you do it so that we know they are updated. > > Thanks and BR > Pier > > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino > Pierangelo > Inviato: marted? 9 dicembre 2014 17:05 > A: Fernando Herranz; Angel Hernandez; Jose Jaime Ariza > Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide > Oggetto: [Fiware-robotics] R: R: FIWARE Robotics Periodic confcall > > Great, thanks Fernando. > > This time I'd like to use the videconference sharing tool whose details are in the attached mail (sorry it's in Italian only, if you have troubles to interpret it, just let me know). > Please access via the Webscopia tool from this link http://conference.vaionline.telecomitalia.it/?ID=72730399 to connect through a browser, which appears the best option to use (however also the Microsoft Office Communicator option is usually fine, except for desktop sharing). Occasionally, Firefox doesn't allow to join, in such a case I suggest to use either chrome or IE. > > The number of connections activated is 5 (two used by us in Torino), I believe the other three should be enough for you, otherwise let me know and I'll try to add extra connections. > > Talk to you tomorrow! > Pier > > > > > Thanks and BR > Pier > > > > > -----Messaggio originale----- > Da: Fernando Herranz [mailto:fherranz at ikergune.com] > Inviato: marted? 9 dicembre 2014 16:55 > A: Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza > Cc: Gaspardone Marco; Colombatto Davide; Antonini Roberto; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Oggetto: Re: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > It's ok for us! > > On 09/12/14 16:51, Garino Pierangelo wrote: >> Dear All, >> >> Is the option proposed by Roberto for a call tomorrow morning feasible for you, i.e. Wednesday 10/12 at 10 CET? >> >> BR >> Pier >> >> >> -----Messaggio originale----- >> Da: Antonini Roberto >> Inviato: marted? 9 dicembre 2014 11:26 >> A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco; Colombatto Davide >> Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hi all, >> for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. >> If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. >> >> As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. >> For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. >> >> My best, >> R >> >> -----Messaggio originale----- >> Da: Garino Pierangelo >> Inviato: marted? 9 dicembre 2014 09:46 >> A: Fernando Herranz; Angel Hernandez; Antonini Roberto; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hi Fernando, >> for me it's fine postponing (3pm is preferred), is it ok for the others too? >> BR >> Pier >> >> >> -----Messaggio originale----- >> Da: Fernando Herranz [mailto:fherranz at ikergune.com] >> Inviato: marted? 9 dicembre 2014 09:28 >> A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hello! >> >> I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! >> >> >> ________________________________________ >> De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] >> Enviado el: viernes, 05 de diciembre de 2014 9:24 >> Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> CC: Gaspardone Marco >> Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Dear Angel and All, >> >> Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. >> >> I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. >> >> On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. >> >> Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. > >> Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? >> >> Thanks >> >> BR >> Pier >> >> >> >> >> Da: Angel Hernandez [mailto:ahernandez at ikergune.com] >> Inviato: gioved? 4 dicembre 2014 15:52 >> A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hello all, >> >> Thank you for the call this morning, I think it went pretty well and >> has been quite productive ? >> >> As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). >> >> In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. >> >> I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. >> >> Talk to you soon, >> ?ngel. >> >> >> De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] >> Enviado el: jueves, 4 de diciembre de 2014 15:37 >> Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> CC: Gaspardone Marco >> Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> >> Hi, >> >> Finally we are at end of the road ... >> >> >> >> The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. >> >> The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: >> >> ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot >> >> ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) >> >> >> >> FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: >> >> ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) >> >> ? Robot pose >> >> >> >> The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. >> >> >> >> >> >> Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. >> >> For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. >> >> >> >> BR >> >> R >> >> >> >> >> >> >> >> -----Messaggio originale----- >> Da: >> fiware-robotics-bounces at lists.fi-ware.org> c >> es at lists.fi-ware.org> >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> Fernando Herranz >> Inviato: gioved? 4 dicembre 2014 14:19 >> A: Angel Hernandez; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org> e >> .org>; Thomas Michael Bohnert >> Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> >> >> Hello, >> >> >> >> at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: >> >> >> >> - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. >> >> >> >> - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. >> >> >> >> Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: >> >> Etxe-Tar part: >> >> Develop a naive mashup application in FIWARE that publish in >> the >> >> context broker a position (goal) to command a robot >> >> Detailed explanation of the robot instance in the context >> broker for Telecom Italia >> >> Detailed explanation of the translation of a simple message >> like a pose by FIROS for Telecom Italia >> >> Telecom Italia part: >> >> Set-up the simplest RCM architecture to command a robot >> >> (turtlebot or PR2 or another robot that you can control) >> >> Detailed explanation of the set-up process for Etxe-Tar >> >> Name and type of the topic that FIROS has to subscribe >> >> >> >> We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? >> >> >> >> Cheers >> >> >> >> >> >> >> >> On 04/12/14 09:57, Angel Hernandez wrote: >> >>> Hello again. >>> We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? >>> 40 minutes should still be enough for today's call. >>> Sent from: Lenovo K910 >>> Angel Hernandez > wrote: >>> Sounds good.. We will be on hangouts as usual. >>> Sent from: Lenovo K910 >>> Garino Pierangelo > wrote: >>> Hi All, >>> I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. >>> I suggest however you start discussing the latest document, then I?ll join. >>> BR >>> Pier >>> Hi All, >>> this is the periodic reminder for the Robotics Confcall. >>> We?ll stay within 1h of call. >>> We?ll use powwownow, numbers to dial can be found at link >>> http://www.powwownow.com/International-DialIn-Numbers/ >>> PIN 075102 >>> BR >>> Pier >>> 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. Non stampare questa mail se non ? necessario. >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org>> r e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org>> r e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> _______________________________________________ >> >> Fiware-robotics mailing list >> >> Fiware-robotics at lists.fi-ware.org> e >> .org> >> >> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From gianmario.bollano at telecomitalia.it Wed Dec 10 15:22:44 2014 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 10 Dec 2014 14:22:44 +0000 Subject: [Fiware-robotics] R: R: R: R: R: FIWARE Robotics Periodic confcall In-Reply-To: <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> Hi all, I have two notes concerning FIROS-RCM and the Tech Roadmaps. 1) Communication FIROS-RCM: I've attended to this morning call with Pier; after today discussion it seems to me there is no direct communication between RCM and FIROS, in the meaning that RCM starts FIROS as a ROS node, as explained by Roberto, and does not need to interface to it. However, FIROS is able to manage multiple robots identifying them by their names, as explained us by Fernando; similarly RCM manage robots through their names. This implies there are shared information between FIROS and RCM; Robot name at least, maybe more. Are these information shared using a ROS communication toward other node (for instance to ROS master / ROS core) ? 2) Technical Roadmap Concerning the technical Roadmap and Features/Epic, I've sent an e-mail with instructions this morning (to all I2ND people). The next step is to split the "Tech Roadmap" into Epics and Features, according to the Agile methodology. As an example, according to your tech Roadmaps, the straightforward Epics definition be: FIWARE.Epic.I2ND.ROBOTICS.FIROSContexbrokerCommunication FIWARE.Epic.I2ND.ROBOTICS.FIROSLanguageTranslation FIWARE.Epic.I2ND.ROBOTICS.FIROSRosCommunication FIWARE.Epic.I2ND.ROBOTICS.RCMPlatformCommands FIWARE.Epic.I2ND.ROBOTICS.RCMPlatformEvents FIWARE.Epic.I2ND.ROBOTICS.RCMRoboticsData FIWARE.Epic.I2ND.ROBOTICS.RCMEventMatching Each of these Epics should correspond to one or more Features. Each Feature is expected inside a Minor Release (current minor release 4.1 ends in Dec, the next one 4.2 will be on Jan-March 2015). All the Features belonging to an Epics should be finished before the current Major Release (i.e. Sep 2015) but obviously multiple Features of different Epics can be completed in the same Minor Release. Have a look at this link for Sprint and release numbering: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Best, Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: mercoled? 10 dicembre 2014 14:32 A: I?igo Gonzalez; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: R: R: R: FIWARE Robotics Periodic confcall Hi all, just for clarity's sake. In our view, as FIROS is a ROS node, the interaction between FIROS and RCM should be the same interaction that RCM has with the other ROS nodes. To be clearer, instead of manually issuing rosrun/roslaunch commands by a Linux Shell, these commands are issued by RCM. Furthermore RCM will be notified when a ROS node goes down (implemented by an own watchdog mechanism). In conclusion: FIROS-CB communication don't concern with RCM, hence it's independent from RCM logic. FIROS-ROS nodes communication follow the well-defined ROS mechanism (e.g. topics pub-sub). I hope we clarified your doubts, we wait for your feedbacks. BR, Davide & Roberto -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: mercoled? 10 dicembre 2014 13:32 A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: Re: [Fiware-robotics] R: R: R: FIWARE Robotics Periodic confcall Hi, we have created a document with Firos roadmap, you can find it here: https://docs.google.com/document/d/1HNHBiK74Oo6lJfBvNwHBum2CUVijrvTbDc6rJm3A1gs/edit?usp=sharing As we have been talking about Firos - RCM integration and some of the Action Points of the last call are related with it, we think it is interesting to share technical specification documents of the interfaces provided by both modules (southbound FIROS interface and northbound RCM interface). We are working on the FIROS interface specification document and we plan to send it to you tomorrow. It can help you to understand how we expect RCM communicates with FIROS but we also need information about RCM interface. It would be great that youy guys send us this information before next call. This way we can work on the integration of Firos with RCM and discuss about it on the call. Regards, I?igo El 10/12/14 a las 12:15, Garino Pierangelo escribi?: > Hi All, > > Here https://docs.google.com/document/d/1XpIUUFzZpKgf7tTd6YvFcgZNs6N4JpXW2CunI0GGcmo/edit?usp=sharing is the link to a short summary I took during the call, I have rearranged a bit the items to make them more homogeneous. > Please refine the summary if you feel it necessary, just inform the others if you do it so that we know they are updated. > > Thanks and BR > Pier > > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino > Pierangelo > Inviato: marted? 9 dicembre 2014 17:05 > A: Fernando Herranz; Angel Hernandez; Jose Jaime Ariza > Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide > Oggetto: [Fiware-robotics] R: R: FIWARE Robotics Periodic confcall > > Great, thanks Fernando. > > This time I'd like to use the videconference sharing tool whose details are in the attached mail (sorry it's in Italian only, if you have troubles to interpret it, just let me know). > Please access via the Webscopia tool from this link http://conference.vaionline.telecomitalia.it/?ID=72730399 to connect through a browser, which appears the best option to use (however also the Microsoft Office Communicator option is usually fine, except for desktop sharing). Occasionally, Firefox doesn't allow to join, in such a case I suggest to use either chrome or IE. > > The number of connections activated is 5 (two used by us in Torino), I believe the other three should be enough for you, otherwise let me know and I'll try to add extra connections. > > Talk to you tomorrow! > Pier > > > > > Thanks and BR > Pier > > > > > -----Messaggio originale----- > Da: Fernando Herranz [mailto:fherranz at ikergune.com] > Inviato: marted? 9 dicembre 2014 16:55 > A: Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza > Cc: Gaspardone Marco; Colombatto Davide; Antonini Roberto; > fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert > Oggetto: Re: R: [Fiware-robotics] FIWARE Robotics Periodic confcall > > It's ok for us! > > On 09/12/14 16:51, Garino Pierangelo wrote: >> Dear All, >> >> Is the option proposed by Roberto for a call tomorrow morning feasible for you, i.e. Wednesday 10/12 at 10 CET? >> >> BR >> Pier >> >> >> -----Messaggio originale----- >> Da: Antonini Roberto >> Inviato: marted? 9 dicembre 2014 11:26 >> A: Garino Pierangelo; Fernando Herranz; Angel Hernandez; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco; Colombatto Davide >> Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hi all, >> for me, it's not possible attending a PhC today afternoon, for an already scheduled meeting, unfortunately it's the end of the year and we need to draw some conclusions and plan next year activities. >> If you agree, we can hear us tomorrow morning (Wednesday 10/12) at 10. >> >> As the demo we are discussing is for next minor release (that's in three months), in my opinion, these days it could be useful finalizing our reference architecture. >> For this and for clarity's sake, I shared with you a set of slides to be discussed together (maybe tomorrow), where it's presented RCM at a certain level with a minimal roadmap to develop it, if you do the same, this will help us to be clearer and avoid misunderstandings in the future. >> >> My best, >> R >> >> -----Messaggio originale----- >> Da: Garino Pierangelo >> Inviato: marted? 9 dicembre 2014 09:46 >> A: Fernando Herranz; Angel Hernandez; Antonini Roberto; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hi Fernando, >> for me it's fine postponing (3pm is preferred), is it ok for the others too? >> BR >> Pier >> >> >> -----Messaggio originale----- >> Da: Fernando Herranz [mailto:fherranz at ikergune.com] >> Inviato: marted? 9 dicembre 2014 09:28 >> A: Garino Pierangelo; Angel Hernandez; Antonini Roberto; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hello! >> >> I'm travelling and I can't attend the call at 10.30. Can we move the call to 3pm or 4pm?? I'll be in Bilbao at that time! >> >> >> ________________________________________ >> De: Garino Pierangelo [pierangelo.garino at telecomitalia.it] >> Enviado el: viernes, 05 de diciembre de 2014 9:24 >> Para: Angel Hernandez; Antonini Roberto; Fernando Herranz; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> CC: Gaspardone Marco >> Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Dear Angel and All, >> >> Roberto anticipated to me that today is a very busy day for their team due to important meetings they cannot miss, and Monday is holidays hence it creates some trouble to meet the dates we planned in the call yesterday. >> >> I would ask Roberto if there?s a possibility to have a call on Tuesday, rather than Wednesday, so that we can still meet the goal. >> >> On the other hand, maybe my definition of ?final? architecture was a little bit stronger than what I really meant: for me the goal on Dec 9th must be an already good description of the robotics architecture, and how this integrates within FIWARE. This will help showing it to other chapters, as well as will enable us to describe the technical roadmap of the GE(s). However, there will be still time beyond that deadline to further refine the details, up to the release of the architecture deliverable. >> >> Meanwhile, I suggest we continue as much as we can to interact at least via mail, e.g. continuing with the description of the demo scenario you have proposed, and Roberto replied, to capture requirements that will help refining further the architecture. > >> Please can you all check if Tuesday morning, e.g. 10:30 or 11, is fine for a call? >> >> Thanks >> >> BR >> Pier >> >> >> >> >> Da: Angel Hernandez [mailto:ahernandez at ikergune.com] >> Inviato: gioved? 4 dicembre 2014 15:52 >> A: Antonini Roberto; Fernando Herranz; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> Cc: Gaspardone Marco >> Oggetto: RE: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> Hello all, >> >> Thank you for the call this morning, I think it went pretty well and >> has been quite productive ? >> >> As you know, we have committed ourselves to have the final architecture by December 9th (Next Tuesday). >> >> In order to do so, we should work together and more efficiently tomorrow and Monday, that?s why Fernando has requested to have a quick call tomorrow. >> >> I think we should really have at least one more call before the 9th. We are very flexible and could do some afterhours if that helps with your schedule. Please let us know if you can figure anything out. >> >> Talk to you soon, >> ?ngel. >> >> >> De: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] >> Enviado el: jueves, 4 de diciembre de 2014 15:37 >> Para: Fernando Herranz; Angel Hernandez; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org; Thomas Michael Bohnert >> CC: Gaspardone Marco >> Asunto: R: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> >> Hi, >> >> Finally we are at end of the road ... >> >> >> >> The first version of RCM with the minimum capabilities requested, will be ready for the next sprint, the right time for a demo. >> >> The robot we can use could be a turtlebot2, as the robot will be installed with RCM part, FIROS could be started either at server or robot side. Once the robot is setup it can enter to the platform and here RCM: >> >> ? Create a clone in the platform, as the clone is a ROS container, it could be distributed between server and robot >> >> ? Start all ROS nodes needed for service logic (FIROS + move base + AMCL), FIROS could be started wherever you want (see above) >> >> >> >> FIROS, once started or after being properly notified by specific ROS topic (please correct me if I?m wrong), create robot entity on CB and update it on ROS topic basis, namely: >> >> ? Robot (turtlebot) sensors, here we can communicate only battery level to upper level (http://docs.ros.org/api/kobuki_msgs/html/msg/SensorState.html) >> >> ? Robot pose >> >> >> >> The Mashup app, built on top of FIWARE, will command the robot ( entity ) with a specific attribute. >> >> >> >> >> >> Unfortunately, tomorrow we can?t attend PhC for others previously scheduled meetings. >> >> For the next week we can schedule Wednesday afternoon or late morning, if not we have the weekly scheduled PhC the day after. >> >> >> >> BR >> >> R >> >> >> >> >> >> >> >> -----Messaggio originale----- >> Da: >> fiware-robotics-bounces at lists.fi-ware.org> c >> es at lists.fi-ware.org> >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> Fernando Herranz >> Inviato: gioved? 4 dicembre 2014 14:19 >> A: Angel Hernandez; Garino Pierangelo; >> fiware-robotics at lists.fi-ware.org> e >> .org>; Thomas Michael Bohnert >> Oggetto: Re: [Fiware-robotics] FIWARE Robotics Periodic confcall >> >> >> >> Hello, >> >> >> >> at the end of the call we were having a very interesting conversation about RCM and FIROS. Here you can see a summary of the main topic that we were discussing: >> >> >> >> - Etxe-Tar: has a preliminary version of FIROS which can manage basic ROS types of data such as poses. >> >> >> >> - Telecom Italia: has a version of RCM which is capable of launching the ROS node move_base to control a robot. >> >> >> >> Since we have a preliminary version of both system, I think it is the proper time to perform a simple real use case of the collaboration of FIROS and RCM. From my point of view it can be very helpful for both parts. Telecom Italia would understand better how FIWARE and the context broker work. Etxe-tar would know in detail how RCM works and could improve FIROS with that information. The test that I propose is that a FIWARE application commands a robot by means of context broker, FIROS and RCM. Here you can find the task that we have identified to complete the test: >> >> Etxe-Tar part: >> >> Develop a naive mashup application in FIWARE that publish in >> the >> >> context broker a position (goal) to command a robot >> >> Detailed explanation of the robot instance in the context >> broker for Telecom Italia >> >> Detailed explanation of the translation of a simple message >> like a pose by FIROS for Telecom Italia >> >> Telecom Italia part: >> >> Set-up the simplest RCM architecture to command a robot >> >> (turtlebot or PR2 or another robot that you can control) >> >> Detailed explanation of the set-up process for Etxe-Tar >> >> Name and type of the topic that FIROS has to subscribe >> >> >> >> We think it would be very useful to keep discussing about it by having a call tomorrow morning. What about tomorrow (Friday 5th) at 10am? >> >> >> >> Cheers >> >> >> >> >> >> >> >> On 04/12/14 09:57, Angel Hernandez wrote: >> >>> Hello again. >>> We are in the middle of finishing other task. Would you mind if we start the call at 10:20 instead? >>> 40 minutes should still be enough for today's call. >>> Sent from: Lenovo K910 >>> Angel Hernandez > wrote: >>> Sounds good.. We will be on hangouts as usual. >>> Sent from: Lenovo K910 >>> Garino Pierangelo > wrote: >>> Hi All, >>> I?m unable to join at 10 the call, but I?ll be available from 10:30 onwards. >>> I suggest however you start discussing the latest document, then I?ll join. >>> BR >>> Pier >>> Hi All, >>> this is the periodic reminder for the Robotics Confcall. >>> We?ll stay within 1h of call. >>> We?ll use powwownow, numbers to dial can be found at link >>> http://www.powwownow.com/International-DialIn-Numbers/ >>> PIN 075102 >>> BR >>> Pier >>> 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. Non stampare questa mail se non ? necessario. >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org>> r e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org>> r e.org> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> _______________________________________________ >> >> Fiware-robotics mailing list >> >> Fiware-robotics at lists.fi-ware.org> e >> .org> >> >> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From igonzalez at ikergune.com Thu Dec 11 10:30:25 2014 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Thu, 11 Dec 2014 10:30:25 +0100 Subject: [Fiware-robotics] FIROS-RCM Specs References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> Message-ID: 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIROSSpecs.pdf Type: application/pdf Size: 105050 bytes Desc: FIROSSpecs.pdf URL: From roberto1.antonini at telecomitalia.it Thu Dec 11 18:05:10 2014 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 11 Dec 2014 17:05:10 +0000 Subject: [Fiware-robotics] R: FIROS-RCM Specs References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local> Hi all, just an additional information to what I wrote before. If I've understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don't you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is "robot is connected": it creates the entity o If the event is "robot is disconnected": it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn't connect ROS directly, it's in charge of manage ROS framework as a whole, so it's not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ... Without "FI" heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That's our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs 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 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: -------------- 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: From roberto1.antonini at telecomitalia.it Fri Dec 12 09:12:19 2014 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Fri, 12 Dec 2014 08:12:19 +0000 Subject: [Fiware-robotics] R: FIROS-RCM Specs In-Reply-To: <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCC8EC9@TELMBB001BA020.telecomitalia.local> Hi all, apologize for spam, let me refine the previous proposal and correct some typos I did. Once the ServiceServer is implemented in RCM Driver node, all you need to do is requesting json info by calling that server with this message server type: string robot_name --- string json_format The server could be ever named /rcm_driver/firos_info. As you should indicate the robot name in the request, the process, I proposed yesterday, slightly changes: ? FIROS and RCM Driver are started by RCM ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? When FIROS is notified (subscribe callback) o If the event is "robot is connected": it requests info to /rcm_driver/firos_info for specific robot and creates the entity o If the event is "robot is disconnected": it deletes the entity Apologize again, I swear this is the last mail on the proposal. :) Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 11 dicembre 2014 18:05 A: I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi all, just an additional information to what I wrote before. If I've understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don't you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is "robot is connected": it creates the entity o If the event is "robot is disconnected": it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn't connect ROS directly, it's in charge of manage ROS framework as a whole, so it's not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ... Without "FI" heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That's our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs 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 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Fri Dec 12 11:43:11 2014 From: ahernandez at ikergune.com (Angel Hernandez) Date: Fri, 12 Dec 2014 11:43:11 +0100 Subject: [Fiware-robotics] FIROS-RCM Specs Message-ID: Hello Roberto, Most of the team is running a demo and a talk about cloud robotics and FI/WARE at the DevFest in Bilbao. We will be answering your emails shortly. Sorry about the delay. Sent from: Lenovo K910 Antonini Roberto wrote: Hi all, apologize for spam, let me refine the previous proposal and correct some typos I did. Once the ServiceServer is implemented in RCM Driver node, all you need to do is requesting json info by calling that server with this message server type: string robot_name --- string json_format The server could be ever named /rcm_driver/firos_info. As you should indicate the robot name in the request, the process, I proposed yesterday, slightly changes: ? FIROS and RCM Driver are started by RCM ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? When FIROS is notified (subscribe callback) o If the event is ?robot is connected?: it requests info to /rcm_driver/firos_info for specific robot and creates the entity o If the event is ?robot is disconnected?: it deletes the entity Apologize again, I swear this is the last mail on the proposal. :) Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 11 dicembre 2014 18:05 A: I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi all, just an additional information to what I wrote before. If I?ve understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don?t you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is ?robot is connected?: it creates the entity o If the event is ?robot is disconnected?: it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn?t connect ROS directly, it?s in charge of manage ROS framework as a whole, so it?s not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ? Without ?FI? heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That?s our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs 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 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. [cid:image001.gif at 01D015EA.BB556210]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From fherranz at ikergune.com Fri Dec 12 12:50:53 2014 From: fherranz at ikergune.com (Fernando Herranz) Date: Fri, 12 Dec 2014 12:50:53 +0100 Subject: [Fiware-robotics] FIROS-RCM Specs In-Reply-To: <246C286B275B1B46A255552CD236DA863BCC8EC9@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCC8EC9@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, sorry for the delay but we are inthe middle of a demo. We agree with the way you plan to send the topics list to FIROS but we (Etxe-Tar) should study how to implement services in FIROS. We also have a doubt, your approach has a FIROS instance per ROS container, right? here is the question: could your architecture support a FIROS instance for all the ROS container? we are developing FIROS to attend all the robots in the cloud. We also think that would help FIWARE application developers because that way they only have to talk to a FIROS instance to control a cloud of robots. Cheers! ________________________________________ De: Antonini Roberto [roberto1.antonini at telecomitalia.it] Enviado el: viernes, 12 de diciembre de 2014 9:12 Para: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide Asunto: R: FIROS-RCM Specs Hi all, apologize for spam, let me refine the previous proposal and correct some typos I did. Once the ServiceServer is implemented in RCM Driver node, all you need to do is requesting json info by calling that server with this message server type: string robot_name --- string json_format The server could be ever named /rcm_driver/firos_info. As you should indicate the robot name in the request, the process, I proposed yesterday, slightly changes: ? FIROS and RCM Driver are started by RCM ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? When FIROS is notified (subscribe callback) o If the event is ?robot is connected?: it requests info to /rcm_driver/firos_info for specific robot and creates the entity o If the event is ?robot is disconnected?: it deletes the entity Apologize again, I swear this is the last mail on the proposal. ? Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 11 dicembre 2014 18:05 A: I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi all, just an additional information to what I wrote before. If I?ve understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don?t you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is ?robot is connected?: it creates the entity o If the event is ?robot is disconnected?: it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn?t connect ROS directly, it?s in charge of manage ROS framework as a whole, so it?s not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ? Without ?FI? heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That?s our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs 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 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. [cid:image001.gif at 01D015EA.BB556210]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. From roberto1.antonini at telecomitalia.it Mon Dec 15 14:13:42 2014 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Mon, 15 Dec 2014 13:13:42 +0000 Subject: [Fiware-robotics] R: FIROS-RCM Specs In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCC8EC9@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCCA05B@TELMBB001BA020.telecomitalia.local> Hi Fernando, In attached a new version of PDF, in which we try to collect all the proposals we made about FIROS and RCM interaction. A couple of question about FIROS: 1. For "to implement service in FIROS" you mean ROS services, don?t you? 2. Have you considered scalability issues for FIROS node? What do you mean when you say " ... FIROS instance to control a cloud of robots"? The Container concept try to meet the non-functional requirement named ?scalability?, by modularizing robot and above all making them stateful (SOA paradigm) . e.g. A robot could be placed on whatever virtual machine (IaaS), basing on maybe cloud metrics. You, at the very beginning, only considered FIROS on each robot (If I remember well), for this, we placed FIROS on each robot whether this was real and virtual (cloned), anyway as we said at the end of the document ?It?s not mandatory having a ROS container for each robot?. BR Roberto -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: venerd? 12 dicembre 2014 12:51 A: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: RE: FIROS-RCM Specs Hi all, sorry for the delay but we are inthe middle of a demo. We agree with the way you plan to send the topics list to FIROS but we (Etxe-Tar) should study how to implement services in FIROS. We also have a doubt, your approach has a FIROS instance per ROS container, right? here is the question: could your architecture support a FIROS instance for all the ROS container? we are developing FIROS to attend all the robots in the cloud. We also think that would help FIWARE application developers because that way they only have to talk to a FIROS instance to control a cloud of robots. Cheers! ________________________________________ De: Antonini Roberto [roberto1.antonini at telecomitalia.it] Enviado el: viernes, 12 de diciembre de 2014 9:12 Para: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide Asunto: R: FIROS-RCM Specs Hi all, apologize for spam, let me refine the previous proposal and correct some typos I did. Once the ServiceServer is implemented in RCM Driver node, all you need to do is requesting json info by calling that server with this message server type: string robot_name --- string json_format The server could be ever named /rcm_driver/firos_info. As you should indicate the robot name in the request, the process, I proposed yesterday, slightly changes: ? FIROS and RCM Driver are started by RCM ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? When FIROS is notified (subscribe callback) o If the event is ?robot is connected?: it requests info to /rcm_driver/firos_info for specific robot and creates the entity o If the event is ?robot is disconnected?: it deletes the entity Apologize again, I swear this is the last mail on the proposal. ? Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 11 dicembre 2014 18:05 A: I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi all, just an additional information to what I wrote before. If I?ve understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don?t you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is ?robot is connected?: it creates the entity o If the event is ?robot is disconnected?: it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn?t connect ROS directly, it?s in charge of manage ROS framework as a whole, so it?s not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ? Without ?FI? heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That?s our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs 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 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. [cid:image001.gif at 01D015EA.BB556210]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIROS_RCM_v2.0.pdf Type: application/pdf Size: 224065 bytes Desc: FIROS_RCM_v2.0.pdf URL: From fherranz at ikergune.com Thu Dec 18 17:10:33 2014 From: fherranz at ikergune.com (Fernando Herranz) Date: Thu, 18 Dec 2014 17:10:33 +0100 Subject: [Fiware-robotics] R: FIROS-RCM Specs References: <246C286B275B1B46A255552CD236DA863BCC547A@TELMBB001BA020.telecomitalia.local> , <246C286B275B1B46A255552CD236DA863BCC7653@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC7FDA@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C1F2A5B@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCC8CC8@TELMBB001BA020.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCC8EC9@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCCA05B@TELMBB001BA020.telecomitalia.local> Message-ID: Hello all, About Roberto's questions: 1. We mean ROS services 2. We don't think FIROS is going to have scalability problems since FIROS is a light process. By " ... FIROS instance to control a cloud of robots" we mean that FIROS is being designed with the goal that one instance of FIROS is able to control more than one robot at the same time. Cheers! On 15/12/14 14:13, Antonini Roberto wrote: Hi Fernando, In attached a new version of PDF, in which we try to collect all the proposals we made about FIROS and RCM interaction. A couple of question about FIROS: 1. For "to implement service in FIROS" you mean ROS services, don?t you? 2. Have you considered scalability issues for FIROS node? What do you mean when you say " ... FIROS instance to control a cloud of robots"? The Container concept try to meet the non-functional requirement named ?scalability?, by modularizing robot and above all making them stateful (SOA paradigm) . e.g. A robot could be placed on whatever virtual machine (IaaS), basing on maybe cloud metrics. You, at the very beginning, only considered FIROS on each robot (If I remember well), for this, we placed FIROS on each robot whether this was real and virtual (cloned), anyway as we said at the end of the document ?It?s not mandatory having a ROS container for each robot?. BR Roberto -----Messaggio originale----- Da: Fernando Herranz [mailto:fherranz at ikergune.com] Inviato: venerd? 12 dicembre 2014 12:51 A: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: RE: FIROS-RCM Specs Hi all, sorry for the delay but we are inthe middle of a demo. We agree with the way you plan to send the topics list to FIROS but we (Etxe-Tar) should study how to implement services in FIROS. We also have a doubt, your approach has a FIROS instance per ROS container, right? here is the question: could your architecture support a FIROS instance for all the ROS container? we are developing FIROS to attend all the robots in the cloud. We also think that would help FIWARE application developers because that way they only have to talk to a FIROS instance to control a cloud of robots. Cheers! ________________________________________ De: Antonini Roberto [roberto1.antonini at telecomitalia.it] Enviado el: viernes, 12 de diciembre de 2014 9:12 Para: Antonini Roberto; I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide Asunto: R: FIROS-RCM Specs Hi all, apologize for spam, let me refine the previous proposal and correct some typos I did. Once the ServiceServer is implemented in RCM Driver node, all you need to do is requesting json info by calling that server with this message server type: string robot_name --- string json_format The server could be ever named /rcm_driver/firos_info. As you should indicate the robot name in the request, the process, I proposed yesterday, slightly changes: ? FIROS and RCM Driver are started by RCM ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? When FIROS is notified (subscribe callback) o If the event is ?robot is connected?: it requests info to /rcm_driver/firos_info for specific robot and creates the entity o If the event is ?robot is disconnected?: it deletes the entity Apologize again, I swear this is the last mail on the proposal. ? Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 11 dicembre 2014 18:05 A: I?igo Gonzalez; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: [Fiware-robotics] R: FIROS-RCM Specs Hi all, just an additional information to what I wrote before. If I?ve understood well, you need ROS topics in the ROS container FIROS has been launched by RCM , don?t you? What we can do to meet your req, is creating a ServiceServer on RCM Driver node, who also informs you about ROS Topics in the ROS Container, this obviously requests FIROS to create a ServiceClient to request this information, the message srv could be formatted in this way --- string json_format Where json_format is the one you described in your doc. The server could be named /rcm_driver/firos_info So the process could be modified adding the bold entry : ? FIROS and RCM Driver are started by RCM ? FIROS requests info to /rcm_driver/firos_info ? FIROS subscribes /rcm_event topic ? Robot get connected/disconnected ? RCM is notified by specific event ? RCM driver publishes /rcm_event topic reporting that event ? FIROS is notified and o If the event is ?robot is connected?: it creates the entity o If the event is ?robot is disconnected?: it deletes the entity let us know if this could be good for you, in case I complete the doc I sent you before. Thanks, Roberto Da: Antonini Roberto Inviato: gioved? 11 dicembre 2014 15:33 A: 'I?igo Gonzalez'; Bollano Gianmario; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Gaspardone Marco Oggetto: R: FIROS-RCM Specs Hi all, thanks to you guys, for having shared the FIROS-RCM interaction spec, this give us yet another chance to merge our views in order to reach the final solution. In the attached PDF, we provide a possible solution to exchange info between FIROS and RCM and clarify the specific role of each component. to better clarify, just a couple of comments about your view: ? RCM doesn?t connect ROS directly, it?s in charge of manage ROS framework as a whole, so it?s not correct placing ROSCORE inside RCM ? Starting from comments above, each ROS container has a proper ROSCORE and RCM can start ROS nodes (FIROS, ALGs and Drivers) in it. In the doc we also provide two architectural views: ? The first one is focused around the GE description, the same you did ? The second one highlights the GE distribution, when having more instances (robot, vm and so on) I hope this finally clarifies everything and reaches to a common convergence point. For what concerns the GE name, I supposed it to be the general name not the name of a GEi, so for this reason I would propose something more general such as ? ROBCON ? CONROB ? NCRP (network connected robotic platform) ? ? Without ?FI? heading (or trailing) the name, because it seems to us too limitative for describing a general Robotics GE, it could be used to describe the implementation name. That?s our view. Thanks again, Hear you soon. Roberto and Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 11 dicembre 2014 10:30 A: Bollano Gianmario; Antonini Roberto; Garino Pierangelo; Fernando Herranz; Angel Hernandez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide Oggetto: FIROS-RCM Specs 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 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. [cid:image001.gif at 01D015EA.BB556210]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahernandez at ikergune.com Mon Dec 22 15:46:57 2014 From: ahernandez at ikergune.com (Angel Hernandez) Date: Mon, 22 Dec 2014 15:46:57 +0100 Subject: [Fiware-robotics] Robotics White paper Message-ID: Pier, I've just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Mon Dec 22 16:27:33 2014 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 22 Dec 2014 15:27:33 +0000 Subject: [Fiware-robotics] R: Robotics White paper In-Reply-To: References: Message-ID: Hi Angel (and All), that is a general comment for all chapters, in our case we don't contribute (yet) to current release of technical white paper, so I didn't create issues in JIRA concerning this task. Later we'll start working on the finalization of our internal document, which we'll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I've just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! 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: -------------- 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: From ahernandez at ikergune.com Mon Dec 22 16:28:20 2014 From: ahernandez at ikergune.com (Angel Hernandez) Date: Mon, 22 Dec 2014 16:28:20 +0100 Subject: [Fiware-robotics] Robotics White paper In-Reply-To: References: Message-ID: Yep! Thank you :) De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 22 de diciembre de 2014 16:28 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: R: Robotics White paper Hi Angel (and All), that is a general comment for all chapters, in our case we don't contribute (yet) to current release of technical white paper, so I didn't create issues in JIRA concerning this task. Later we'll start working on the finalization of our internal document, which we'll propose as contribution to the technical white paper for the robotics GE. Hope this answers your question. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 22 dicembre 2014 15:47 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics White paper Pier, I've just seen a comment here (http://jira.fi-ware.org/browse/MIND-90) about the white paper. I am not sure what the status of that is or if there is any action that we have missed on our side. Can you, please, clarify if there is anything that should be taken care of concerning this white paper? Thank you! 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. [cid:image001.gif at 01D01E04.4C5F7090]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: