From pierangelo.garino at telecomitalia.it Wed Jul 1 10:16:54 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 1 Jul 2015 08:16:54 +0000 Subject: [Fiware-robotics] R: Demo Sprint 4.3.3 In-Reply-To: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> Message-ID: Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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 davide.colombatto at telecomitalia.it Wed Jul 1 10:43:00 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Wed, 1 Jul 2015 08:43:00 +0000 Subject: [Fiware-robotics] R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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 gianmario.bollano at telecomitalia.it Wed Jul 1 12:04:26 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 1 Jul 2015 10:04:26 +0000 Subject: [Fiware-robotics] R: Demo Sprint 4.3.3 In-Reply-To: <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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 igonzalez at ikergune.com Wed Jul 1 12:21:27 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Wed, 1 Jul 2015 12:21:27 +0200 Subject: [Fiware-robotics] R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> Message-ID: Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What?s important for the demo is to clearly explain what we?ll show, not to provide tech details for the implementation. Considering the short time available, I?d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren?t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I?d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway? - .. and we?ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity?s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I?d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI?s office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot?s movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide?s comments have to be rewritten Let we know, BR Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Wed Jul 1 14:35:52 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 1 Jul 2015 12:35:52 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> Hi all, according to the preferences in the poll we can have the call next Friday 3th from 2PM to 3PM. I?ll send you an invite. Gianmario Bollano Da: Bollano Gianmario Inviato: marted? 30 giugno 2015 17:10 A: '?lvaro Arranz'; Luis L?pez Fern?ndez Cc: Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and all, we propose a Doodle poll to select a timeslot for the call. The link is: http://doodle.com/fb6gx4wbbqupwkwu Please, select your preferred time. Gianmario Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: marted? 30 giugno 2015 16:55 A: Luis L?pez Fern?ndez Cc: Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi, sorry for the delay in the response, we are busy with the closing and planning phases of the sprint. Also I'm organising my travel to the Campus party event at Mexico. I'll work on providing a better feedback asap (I'll try to provide it today). Anyway, updating our widgets for accessing this one-to-many service will be easy, we can synchronise with the Kurento team for making the needed changes for selecting the master video stream, etc... This is only a thing of managing some new commands through the WebSocket connection and recreating the WebRTC connections. I don't forecast, as Luis, any problem on this side. We are also interested in join the call :). Best regards, ?lvaro On 30 June 2015 at 16:27, Luis L?pez Fern?ndez > wrote: Hi Gianmario, Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. Thanks. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 30/06/2015, a las 16:21, Bollano Gianmario > escribi?: Hi Luis, thank you for your support and your clarification. As a short summary, we also have tested a WebRTC client based on Webkit but haven?t yet found the optimal solution, then it would be useful to discuss further this issue. The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. Thank you, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez Inviato: marted? 30 giugno 2015 13:05 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo > escribi?: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we?d like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members?) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we?ll be able to ?complete the picture? and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Wed Jul 1 14:36:08 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 1 Jul 2015 12:36:08 +0000 Subject: [Fiware-robotics] Call for Robotics Live demo with Kurento and Wirecloud Message-ID: <7E649CBD84A947498203DAF8F098B1F642A78519@telmba003ba020.telecomitalia.local> Hi all, we'll have the call with hangout next Friday afternoon. In the meantime, please add notes/comments the shared online document for the Robotics Live demo details: https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit?pli=1#heading=h.wo297vomr0zs Kind regards, Gianmario 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: 3400 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 fabio.dibenedetto at consoft.it Wed Jul 1 14:40:16 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Wed, 1 Jul 2015 12:40:16 +0000 Subject: [Fiware-robotics] R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> Message-ID: <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From gianmario.bollano at telecomitalia.it Wed Jul 1 14:44:52 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 1 Jul 2015 12:44:52 +0000 Subject: [Fiware-robotics] R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A7855E@telmba003ba020.telecomitalia.local> Hi Inigo, what I've understood is that in the demo there's not yet a full interaction between RCM and FIROS, because FIROS has hardcoded the information to publish in the CB. Such communication is the FIROS interaction feature. Gianmario Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: mercoled? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From gianmario.bollano at telecomitalia.it Wed Jul 1 14:48:39 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 1 Jul 2015 12:48:39 +0000 Subject: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 In-Reply-To: <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you've found in your trials; if this works it would be better to use them , otherwise we'll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From igonzalez at ikergune.com Wed Jul 1 15:08:36 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Wed, 1 Jul 2015 15:08:36 +0200 Subject: [Fiware-robotics] R: R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> Message-ID: I think there is some misunderstanding here ;) , our problem was not related to FIROS, we brought up a robot using RCM but there was nothing in the context broker, we supposed that in your side was a firos instance (as RCM creates an VPN) isn't it? We didn't brought up any FIROS instance here when using RCM, so maybe that was the problem. The firos version you have should work as the one you were already using, the diference is the configuration way (this one is more user friendly, json configuration files) and that also has all the stuff we have talked in previous calls: * port configuration * RCM-FIROS communication The part that hasn't been tried is the communication with RCM. So if you have already been able to bring it up I encourage you to use the new version of FIROS, it will make the things easier for everyone. I think that what we can do by now is just bring up FIROS, and try FIROS + RCM to make the integration work for the live demo (not the mondays one). What do you think? Regards, I?igo On 01/07/15 14:42, fabio.dibenedetto at consoft.it wrote: Hi, I?m looking just now these mails; I haven?t understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don?t know if it was able to contact the CB. At the call you said that you haven?t seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn?t exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it?s ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What?s important for the demo is to clearly explain what we?ll show, not to provide tech details for the implementation. Considering the short time available, I?d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren?t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I?d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway? - .. and we?ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity?s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I?d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI?s office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot?s movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide?s comments have to be rewritten Let we know, BR Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Wed Jul 1 17:17:47 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Wed, 1 Jul 2015 15:17:47 +0000 Subject: [Fiware-robotics] R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3541B4E93BD@telmbc006ba020.telecomitalia.local> Hi I?igo and Gianmario, Below in red, some points/questions to I?igo related to FIROSv2 and the RCM Feature "FIROS Interaction". D Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: mercoled? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. Hence FIROSv2 works in the same way of FIROSv1 for what concern the hardcoded data (the only difference is that in FIROSv1 the data are put inside the code whereas in FIROSv2 they are in a config JSON file)? Consequently, this different behavior is not enough to show the RCM Feature "FIROS interaction" which is related to dynamically exchange these data btw RCM Driver and FIROS instead of keep them hardcoded. Does FIROSv2 already implement the data exchange with RCM Driver using the protocol we have specified in the OpenSpec Draft (Pub/Sub and service)? The CB entity is created/deletes when FIROSv2 is started/stopped or when it receives the notification from RCM Driver? Even if the response are positive, the integration and test phase (i.e. correct data exchange through RCM Driver) requires more than 2 days. The reason is that, for now, Fabio (for RCM Driver) and you (for FIROS) have worked in a standalone way to implement the interaction but it is not sure that the two components really "talk" together in synch way. For instance, some issues about FIROSv2 is that it is not aligned with the OpenSpec Draft we wrote. Examples: ? *.msg and *.srv files should be in a standalone ROS package "robotics_msgs" and not in the ROS package "firos" ? in FIROSv2 there is RCM_Event instead of Robot_Event ? In FIROSv2 there is FIROS_Info with "robot_name" instead of "instance_name" ? ... Said that, although we have closed the RCM Feature "FIROS interaction" in JIRA we cannot show it in the demo; for this reason I added additional workitems for the 4.4.1 related to Integration and Testing related to "FIROS interaction". Tomorrow we will try FIROSv2 but the demo on Monday will have hardcoded data as using FIROSv1. Is it correct? What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From igonzalez at ikergune.com Thu Jul 2 11:20:09 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 2 Jul 2015 11:20:09 +0200 Subject: [Fiware-robotics] R: R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E93BD@telmbc006ba020.telecomitalia.local> Message-ID: Hi again, I will take the blue color for my answers On 01/07/15 17:17, Colombatto Davide wrote: Hi I?igo and Gianmario, Below in red, some points/questions to I?igo related to FIROSv2 and the RCM Feature ?FIROS Interaction?. D Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: mercoled? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. Hence FIROSv2 works in the same way of FIROSv1 for what concern the hardcoded data (the only difference is that in FIROSv1 the data are put inside the code whereas in FIROSv2 they are in a config JSON file)? Consequently, this different behavior is not enough to show the RCM Feature ?FIROS interaction? which is related to dynamically exchange these data btw RCM Driver and FIROS instead of keep them hardcoded. Firosv2 handles the robots in the same way as Firosv1 does. The difference is what you have said, that the configuration is not hardcoded in the code, it is in configuration files: - robots.json: Creates its robots' subscription and publishing topics. It doesn't matter if the robot doesn't exist (Firosv1 hardcoded robot does the same) - whitelist.json: On firos startup or when the robot connection api (rest or topic) is used, searches for the robots that matches with this whitelist and connects to it. It also has the firos-RCM integration, but it hasn't been tested, so maybe is better not to use it by now. Does FIROSv2 already implement the data exchange with RCM Driver using the protocol we have specified in the OpenSpec Draft (Pub/Sub and service)? The CB entity is created/deletes when FIROSv2 is started/stopped or when it receives the notification from RCM Driver? Even if the response are positive, the integration and test phase (i.e. correct data exchange through RCM Driver) requires more than 2 days. The reason is that, for now, Fabio (for RCM Driver) and you (for FIROS) have worked in a standalone way to implement the interaction but it is not sure that the two components really ?talk? together in synch way. For instance, some issues about FIROSv2 is that it is not aligned with the OpenSpec Draft we wrote. Examples: ? *.msg and *.srv files should be in a standalone ROS package ?robotics_msgs? and not in the ROS package ?firos? ? in FIROSv2 there is RCM_Event instead of Robot_Event ? In FIROSv2 there is FIROS_Info with ?robot_name? instead of ?instance_name? ? ? Said that, although we have closed the RCM Feature ?FIROS interaction? in JIRA we cannot show it in the demo; for this reason I added additional workitems for the 4.4.1 related to Integration and Testing related to ?FIROS interaction?. As I said before, it is done. While we where doing that draft we were developing the functionalities. But this haven't been tested so I am agree with you, it is better not to show it in the demo. To test it, is there a way to emulate what RCM provides us when a robot is connected and when we ask for robot topics? Tomorrow we will try FIROSv2 but the demo on Monday will have hardcoded data as using FIROSv1. Is it correct? What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What?s important for the demo is to clearly explain what we?ll show, not to provide tech details for the implementation. Considering the short time available, I?d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren?t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I?d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway? - .. and we?ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity?s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I?d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI?s office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot?s movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide?s comments have to be rewritten Let we know, BR Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From igonzalez at ikergune.com Thu Jul 2 11:24:38 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 2 Jul 2015 11:24:38 +0200 Subject: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> Message-ID: Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you?ve found in your trials; if this works it would be better to use them , otherwise we?ll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I?m looking just now these mails; I haven?t understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don?t know if it was able to contact the CB. At the call you said that you haven?t seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn?t exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it?s ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What?s important for the demo is to clearly explain what we?ll show, not to provide tech details for the implementation. Considering the short time available, I?d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren?t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I?d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway? - .. and we?ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity?s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I?d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI?s office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot?s movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide?s comments have to be rewritten Let we know, BR Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabio.dibenedetto at consoft.it Thu Jul 2 12:00:09 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 2 Jul 2015 10:00:09 +0000 Subject: [Fiware-robotics] R: R: R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> Message-ID: <3834a20185a448f09225fd0dc435bcf1@EXCHMBX2.consoft.it> Hi, I have a question; I'm trying to using firos version 2 in the demo configuration, but I'm having trouble. The following is the robots.json file as I modified { "turtlebotTI":{ "topics": { "mobile_base/commands/velocity": { "msg": "geometry_msgs.msg.Twist", "type": "publisher" } } } } And here we have the part I use in config.json (where the address of the context broker is pointing to the instance that Davide created and we are using for our tests) "local": { "server": { "port": 10100 }, "contextbroker": { "address" : "130.206.114.100", "port" : 1026, "subscription": { "throttling": "PT0S", "subscription_length": "P1D", "subscription_refresh_delay": 0.5 } }, "log_level": "INFO", "interface": "eth0", "rosbridge_port": 9090 } On rcm log I see the error that firos put up during its execution after the start errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) and the robot doesn't move. Do I have to change something in the whitelist? Because to move the robot we use mobile_base/commands/velocity and in the previous version we only changed something in the core.py and in the js to point that Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 2 luglio 2015 11:25 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you've found in your trials; if this works it would be better to use them , otherwise we'll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From igonzalez at ikergune.com Thu Jul 2 12:15:50 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Thu, 2 Jul 2015 12:15:50 +0200 Subject: [Fiware-robotics] R: R: R: R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> <3834a20185a448f09225fd0dc435bcf1@EXCHMBX2.consoft.it> Message-ID: Hi fabio, I've just tried the configuration you have sent me and is working for me. Have you changed somwthing in other config file or commented some line in the jsons? Anyway here you have my configuration modified with what you have just send, the password is: robotics I hope this helps you. Regards, I?igo On 02/07/15 12:02, fabio.dibenedetto at consoft.it wrote: "local": { "server": { "port": 10100 }, "contextbroker": { "address" : "130.206.114.100", "port" : 1026, "subscription": { "throttling": "PT0S", "subscription_length": "P1D", "subscription_refresh_delay": 0.5 } }, "log_level": "INFO", "interface": "eth0", "rosbridge_port": 9090 } -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: firos_config.zip Type: application/zip Size: 1595 bytes Desc: firos_config.zip URL: From fabio.dibenedetto at consoft.it Thu Jul 2 12:34:23 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 2 Jul 2015 10:34:23 +0000 Subject: [Fiware-robotics] R: R: R: R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> <3834a20185a448f09225fd0dc435bcf1@EXCHMBX2.consoft.it> Message-ID: I see that the whitelist is different Thank you, I'll try Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 2 luglio 2015 12:16 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: R: Demo Sprint 4.3.3 Hi fabio, I've just tried the configuration you have sent me and is working for me. Have you changed somwthing in other config file or commented some line in the jsons? Anyway here you have my configuration modified with what you have just send, the password is: robotics I hope this helps you. Regards, I?igo On 02/07/15 12:02, fabio.dibenedetto at consoft.it wrote: "local": { "server": { "port": 10100 }, "contextbroker": { "address" : "130.206.114.100", "port" : 1026, "subscription": { "throttling": "PT0S", "subscription_length": "P1D", "subscription_refresh_delay": 0.5 } }, "log_level": "INFO", "interface": "eth0", "rosbridge_port": 9090 } -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Thu Jul 2 13:04:52 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 2 Jul 2015 11:04:52 +0000 Subject: [Fiware-robotics] R: R: R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3541B4EAE0B@telmbc006ba020.telecomitalia.local> Hi I?igo, I also made some modifications in the old web-app of first demo in order to also have forward, backward, left and right commands. As said in the call, I'm keeping it in my local machine (and not host in a public web server). I also continuing to launch chrome with the option -disable-web-security. I summarize the info you need: ? CB: 130.206.114.100 1026 ? CB entity name: turtlebotTI ? Topic (I think it is also the CB entity attribute): name mobile_base/commands/velocity ; msg geometry_msgs.msg.Twist Since we are using the standard turtlebot's ROS Driver we are not using namespace so in FIROS code the concatenation robot_name+"/"+topic_name is the issue. The topic should be mobile_base/commands/velocity and not turtlebotTI/mobile_base/commands/velocity I remind you that we already distinguish robots using Service Spaces and for this reason we don't need namespaces. Hence it is not correct to assume that the robot_name we give you (i.e. turtlebotTI) is to be used as a namespace. It should be used only for the CB-entity's name. Davide 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: gioved? 2 luglio 2015 11:25 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you've found in your trials; if this works it would be better to use them , otherwise we'll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From igonzalez at ikergune.com Thu Jul 2 13:10:41 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 2 Jul 2015 13:10:41 +0200 Subject: [Fiware-robotics] R: R: R: R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4EAE0B@telmbc006ba020.telecomitalia.local> Message-ID: Hi its great to know about the webapp you did, as there is no namespace my recomendation is to do this in the configuration: robotname: mobile_base robottoppic: commands/velocity In a future we will have to talk about the namespaces, since we need a name to create an entity in the context broker representing each robot, Maybe identify each service namespace with a name and firos consume it or something like that. But as I said that is not important now. Thank you for the data Davide. On 02/07/15 13:04, Colombatto Davide wrote: Hi I?igo, I also made some modifications in the old web-app of first demo in order to also have forward, backward, left and right commands. As said in the call, I?m keeping it in my local machine (and not host in a public web server). I also continuing to launch chrome with the option ?disable-web-security. I summarize the info you need: ? CB: 130.206.114.100 1026 ? CB entity name: turtlebotTI ? Topic (I think it is also the CB entity attribute): name mobile_base/commands/velocity ; msg geometry_msgs.msg.Twist Since we are using the standard turtlebot?s ROS Driver we are not using namespace so in FIROS code the concatenation robot_name+?/?+topic_name is the issue. The topic should be mobile_base/commands/velocity and not turtlebotTI/mobile_base/commands/velocity I remind you that we already distinguish robots using Service Spaces and for this reason we don?t need namespaces. Hence it is not correct to assume that the robot_name we give you (i.e. turtlebotTI) is to be used as a namespace. It should be used only for the CB-entity?s name. Davide 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: gioved? 2 luglio 2015 11:25 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you?ve found in your trials; if this works it would be better to use them , otherwise we?ll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I?m looking just now these mails; I haven?t understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don?t know if it was able to contact the CB. At the call you said that you haven?t seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn?t exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it?s ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What?s important for the demo is to clearly explain what we?ll show, not to provide tech details for the implementation. Considering the short time available, I?d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren?t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I?d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway? - .. and we?ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity?s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I?d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI?s office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot?s movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide?s comments have to be rewritten Let we know, BR Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Thu Jul 2 14:55:01 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 2 Jul 2015 12:55:01 +0000 Subject: [Fiware-robotics] R: R: R: R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4EAE0B@telmbc006ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3541B4EAF8E@telmbc006ba020.telecomitalia.local> Hi, actually this is an important argument because in the web-app we send data to the CB in the following way: CB.sendData() method ? 1st parameter: "turtlebotTI" -> intended as CB-entity's name ? 2nd parameter: 'ROBOT' ? 3th parameter: CB.createContent() method uses "mobile_base/commands/velocity" -> intended as CB-entity's attribute Said that, it is not totally correct to modify the FIROS's code as you recommend because the CB-entity's name have to be "turtlebotTI" (as we give you in the robots.json config file) and its attribute have to be "mobile/commands/velocity" To summarize, "turtlebotTI" (that we give you in the robots.json config file or through the ROS node RCM Driver) is: ? the name of the robot (by RCM view, thus when you install RCM on the robot you choose this name) ? the name of the Service Space (Robot Clone) automatically created at the robot connection ? the name of the CB-entity automatically created by FIROS o The CB-entity attribute should only be "mobile/commands/velocity" In FIROSv1 we modified only the following line: ROBOT1_TOPIC_PUB = rospy.Publisher(ROBOT1_NAME + "/" + ROBOT1_TOPIC, ROBOT1_TOPIC_CLASS, queue_size=10) Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 2 luglio 2015 13:11 A: Colombatto Davide; Bollano Gianmario; fabio.dibenedetto at consoft.it; Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: R: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi its great to know about the webapp you did, as there is no namespace my recomendation is to do this in the configuration: robotname: mobile_base robottoppic: commands/velocity In a future we will have to talk about the namespaces, since we need a name to create an entity in the context broker representing each robot, Maybe identify each service namespace with a name and firos consume it or something like that. But as I said that is not important now. Thank you for the data Davide. On 02/07/15 13:04, Colombatto Davide wrote: Hi I?igo, I also made some modifications in the old web-app of first demo in order to also have forward, backward, left and right commands. As said in the call, I'm keeping it in my local machine (and not host in a public web server). I also continuing to launch chrome with the option -disable-web-security. I summarize the info you need: ? CB: 130.206.114.100 1026 ? CB entity name: turtlebotTI ? Topic (I think it is also the CB entity attribute): name mobile_base/commands/velocity ; msg geometry_msgs.msg.Twist Since we are using the standard turtlebot's ROS Driver we are not using namespace so in FIROS code the concatenation robot_name+"/"+topic_name is the issue. The topic should be mobile_base/commands/velocity and not turtlebotTI/mobile_base/commands/velocity I remind you that we already distinguish robots using Service Spaces and for this reason we don't need namespaces. Hence it is not correct to assume that the robot_name we give you (i.e. turtlebotTI) is to be used as a namespace. It should be used only for the CB-entity's name. Davide 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: gioved? 2 luglio 2015 11:25 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you've found in your trials; if this works it would be better to use them , otherwise we'll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From fabio.dibenedetto at consoft.it Thu Jul 2 15:13:12 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 2 Jul 2015 13:13:12 +0000 Subject: [Fiware-robotics] R: R: R: R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4EAE0B@telmbc006ba020.telecomitalia.local> Message-ID: <8266297c8400486d9461694a8ac05fcc@EXCHMBX2.consoft.it> Hi, still have the same trouble as before: Expecting property name enclosed in double quotes: line 1 column 2 (char 1) The configuration is ok and the node starts, but this happens when we try to send something to the robot from the web app: it seems that something non-json has been received by firos (maybe from the context broker) and firos tries to translate as json. Are we sure that we are using the same version of context broker? We are using the same version of context broker that we used in the first demo, so if the new version of firos use a new one, maybe they have problem to communicate with each other. Also I take the liberty to modify your code to try to patch the problem of the namespace (and put a custom solution that works only for turtlebotTI so that you shouldn't have problem with all the other robots) Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 2 luglio 2015 13:11 A: Colombatto Davide; Bollano Gianmario; fabio.dibenedetto at consoft.it; Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: R: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi its great to know about the webapp you did, as there is no namespace my recomendation is to do this in the configuration: robotname: mobile_base robottoppic: commands/velocity In a future we will have to talk about the namespaces, since we need a name to create an entity in the context broker representing each robot, Maybe identify each service namespace with a name and firos consume it or something like that. But as I said that is not important now. Thank you for the data Davide. On 02/07/15 13:04, Colombatto Davide wrote: Hi I?igo, I also made some modifications in the old web-app of first demo in order to also have forward, backward, left and right commands. As said in the call, I'm keeping it in my local machine (and not host in a public web server). I also continuing to launch chrome with the option -disable-web-security. I summarize the info you need: ? CB: 130.206.114.100 1026 ? CB entity name: turtlebotTI ? Topic (I think it is also the CB entity attribute): name mobile_base/commands/velocity ; msg geometry_msgs.msg.Twist Since we are using the standard turtlebot's ROS Driver we are not using namespace so in FIROS code the concatenation robot_name+"/"+topic_name is the issue. The topic should be mobile_base/commands/velocity and not turtlebotTI/mobile_base/commands/velocity I remind you that we already distinguish robots using Service Spaces and for this reason we don't need namespaces. Hence it is not correct to assume that the robot_name we give you (i.e. turtlebotTI) is to be used as a namespace. It should be used only for the CB-entity's name. Davide 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: gioved? 2 luglio 2015 11:25 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you've found in your trials; if this works it would be better to use them , otherwise we'll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From igonzalez at ikergune.com Thu Jul 2 15:18:40 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 2 Jul 2015 15:18:40 +0200 Subject: [Fiware-robotics] R: R: R: R: R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4EAE0B@telmbc006ba020.telecomitalia.local> <8266297c8400486d9461694a8ac05fcc@EXCHMBX2.consoft.it> Message-ID: Ok, I thought the problem was on the startup of Firos. Can I know the structure you are sending to the CB, and which CB version are you using? Because in firosv1 we send the data in a way using a string with quotes, but the CB's last version doesn't allow to send that character so we had to change it. Maybe that's the problem On 02/07/15 15:13, fabio.dibenedetto at consoft.it wrote: Hi, still have the same trouble as before: Expecting property name enclosed in double quotes: line 1 column 2 (char 1) The configuration is ok and the node starts, but this happens when we try to send something to the robot from the web app: it seems that something non-json has been received by firos (maybe from the context broker) and firos tries to translate as json. Are we sure that we are using the same version of context broker? We are using the same version of context broker that we used in the first demo, so if the new version of firos use a new one, maybe they have problem to communicate with each other. Also I take the liberty to modify your code to try to patch the problem of the namespace (and put a custom solution that works only for turtlebotTI so that you shouldn?t have problem with all the other robots) Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 2 luglio 2015 13:11 A: Colombatto Davide; Bollano Gianmario; fabio.dibenedetto at consoft.it; Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: R: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi its great to know about the webapp you did, as there is no namespace my recomendation is to do this in the configuration: robotname: mobile_base robottoppic: commands/velocity In a future we will have to talk about the namespaces, since we need a name to create an entity in the context broker representing each robot, Maybe identify each service namespace with a name and firos consume it or something like that. But as I said that is not important now. Thank you for the data Davide. On 02/07/15 13:04, Colombatto Davide wrote: Hi I?igo, I also made some modifications in the old web-app of first demo in order to also have forward, backward, left and right commands. As said in the call, I?m keeping it in my local machine (and not host in a public web server). I also continuing to launch chrome with the option ?disable-web-security. I summarize the info you need: ? CB: 130.206.114.100 1026 ? CB entity name: turtlebotTI ? Topic (I think it is also the CB entity attribute): name mobile_base/commands/velocity ; msg geometry_msgs.msg.Twist Since we are using the standard turtlebot?s ROS Driver we are not using namespace so in FIROS code the concatenation robot_name+?/?+topic_name is the issue. The topic should be mobile_base/commands/velocity and not turtlebotTI/mobile_base/commands/velocity I remind you that we already distinguish robots using Service Spaces and for this reason we don?t need namespaces. Hence it is not correct to assume that the robot_name we give you (i.e. turtlebotTI) is to be used as a namespace. It should be used only for the CB-entity?s name. Davide 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: gioved? 2 luglio 2015 11:25 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you?ve found in your trials; if this works it would be better to use them , otherwise we?ll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I?m looking just now these mails; I haven?t understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don?t know if it was able to contact the CB. At the call you said that you haven?t seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn?t exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it?s ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What?s important for the demo is to clearly explain what we?ll show, not to provide tech details for the implementation. Considering the short time available, I?d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren?t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I?d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway? - .. and we?ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity?s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I?d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI?s office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot?s movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide?s comments have to be rewritten Let we know, BR Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabio.dibenedetto at consoft.it Thu Jul 2 15:34:27 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 2 Jul 2015 13:34:27 +0000 Subject: [Fiware-robotics] R: R: R: R: R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4EAE0B@telmbc006ba020.telecomitalia.local> <8266297c8400486d9461694a8ac05fcc@EXCHMBX2.consoft.it> Message-ID: <03a44e6ad4a04d29bdb47ff24a6179f7@EXCHMBX2.consoft.it> Yes, for sure is that: we are using the same infrastructure we used at the time of the first demo so the old CB (I don't know what version was but Davide suggests that could be 3.4 not the last for sure). The web_app is only an extension of your old one so if you have the new can we have it and use for our tests? What version of CB do you use? So we can stay updated and use the real same configuration Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 2 luglio 2015 15:19 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: R: R: Demo Sprint 4.3.3 Ok, I thought the problem was on the startup of Firos. Can I know the structure you are sending to the CB, and which CB version are you using? Because in firosv1 we send the data in a way using a string with quotes, but the CB's last version doesn't allow to send that character so we had to change it. Maybe that's the problem On 02/07/15 15:13, fabio.dibenedetto at consoft.it wrote: Hi, still have the same trouble as before: Expecting property name enclosed in double quotes: line 1 column 2 (char 1) The configuration is ok and the node starts, but this happens when we try to send something to the robot from the web app: it seems that something non-json has been received by firos (maybe from the context broker) and firos tries to translate as json. Are we sure that we are using the same version of context broker? We are using the same version of context broker that we used in the first demo, so if the new version of firos use a new one, maybe they have problem to communicate with each other. Also I take the liberty to modify your code to try to patch the problem of the namespace (and put a custom solution that works only for turtlebotTI so that you shouldn't have problem with all the other robots) Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 2 luglio 2015 13:11 A: Colombatto Davide; Bollano Gianmario; fabio.dibenedetto at consoft.it; Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: R: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi its great to know about the webapp you did, as there is no namespace my recomendation is to do this in the configuration: robotname: mobile_base robottoppic: commands/velocity In a future we will have to talk about the namespaces, since we need a name to create an entity in the context broker representing each robot, Maybe identify each service namespace with a name and firos consume it or something like that. But as I said that is not important now. Thank you for the data Davide. On 02/07/15 13:04, Colombatto Davide wrote: Hi I?igo, I also made some modifications in the old web-app of first demo in order to also have forward, backward, left and right commands. As said in the call, I'm keeping it in my local machine (and not host in a public web server). I also continuing to launch chrome with the option -disable-web-security. I summarize the info you need: ? CB: 130.206.114.100 1026 ? CB entity name: turtlebotTI ? Topic (I think it is also the CB entity attribute): name mobile_base/commands/velocity ; msg geometry_msgs.msg.Twist Since we are using the standard turtlebot's ROS Driver we are not using namespace so in FIROS code the concatenation robot_name+"/"+topic_name is the issue. The topic should be mobile_base/commands/velocity and not turtlebotTI/mobile_base/commands/velocity I remind you that we already distinguish robots using Service Spaces and for this reason we don't need namespaces. Hence it is not correct to assume that the robot_name we give you (i.e. turtlebotTI) is to be used as a namespace. It should be used only for the CB-entity's name. Davide 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: gioved? 2 luglio 2015 11:25 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi everyone, another thing. I am working on the interface we talk on the call, I need some data to work with it I know that some of that has been send in another mail, but it will be great to have it sumarized somewhere. the data I currently need is: context_broker's ip, and port the robots' namespaces: robot1, turtlebot..., or you aren't using any robot namespace? the topics we are going to work with: name, type, and if we publish or subscribe to it. By now I think this is enough to continue my work. Regards, I?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you've found in your trials; if this works it would be better to use them , otherwise we'll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From igonzalez at ikergune.com Thu Jul 2 16:14:14 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 2 Jul 2015 16:14:14 +0200 Subject: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> Message-ID: Hi, the problem you are facing is because in Firosv1, we used a character to identify some data, but in an update of the context broker that character wasn't allowed, that's the reason why I was asking you about your CB version. Also the webapp we have, uses the new character, so it would be incompatible whith your deployment. As we have reached this point, and we need to have all the demo stuff ready, we think that what we can do is 2 demos (the mixed idea Roberto said in the call). In TI side you can show how RCM works with Firosv1, and move it with your interface, so you will show the advances in RCM, working with the environment that you control and know quite well, and in our side we can show Firosv2 advances. Regards, i?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you?ve found in your trials; if this works it would be better to use them , otherwise we?ll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I?m looking just now these mails; I haven?t understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don?t know if it was able to contact the CB. At the call you said that you haven?t seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn?t exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it?s ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What?s important for the demo is to clearly explain what we?ll show, not to provide tech details for the implementation. Considering the short time available, I?d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren?t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I?d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway? - .. and we?ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity?s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I?d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI?s office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot?s movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide?s comments have to be rewritten Let we know, BR Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Jul 2 17:30:15 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 2 Jul 2015 15:30:15 +0000 Subject: [Fiware-robotics] R: R: R: R: Demo Sprint 4.3.3 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3541B4E505F@telmbc006ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A74405@telmba003ba020.telecomitalia.local> <499fff4e3f86433583e699582ec05e7a@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F642A7858B@telmba003ba020.telecomitalia.local> Message-ID: Hi Inigo, As far as I understood from Roberto, his idea of mixed demo was not like what you propose, and this latter in my opinion is not a good option for Monday's demo: Roberto's idea was to have a unique web app built on top of FIWARE, where controlling both robots, i.e. one at TI side and one at ET side. Hence FIROSv2 should have managed ports to connect CB and, I expected that you could provide the updated web app in time for integration/use in such demo. I also understood that Fabio/Davide needed from you a link to CB, the new web app and the new version of FIROSv2 in time (e.g. one week ago) to be sure they could set up the entire demo. This appeared to be partially happened, so at this time I believe that the most practical solution for the demo is to go back to the use of FIROSv1: this is anyway sending/receiving NGSI messages (thus demonstrating the Features developed) as well as showing the Features of RCM. The work on the inclusion of FIROSv2 will start right after the demo of Monday. On the other hand I don't think it can be said that the deployment is incompatible with the new version of FIROS: as far as I understand, the RCM development is following what is described in the draft specifications that were jointly produced so far and agreed. The communication with CB is in charge of FIROS, hence I expect that any modification on that side should be taken into account there, and propagated to the team if it has impacts on other parts (including the test set ups), to let all people know of possible changes to be applied, and to agree on spec updates if required. I am pretty sure this issue wouldn't happen if we had already the live demo account ready to host a common deployment of the components. I'll push again the guys on that side to provide it asap, so that we won't experience same troubles in the future. BR Pier 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: gioved? 2 luglio 2015 16:14 A: Bollano Gianmario; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Hi, the problem you are facing is because in Firosv1, we used a character to identify some data, but in an update of the context broker that character wasn't allowed, that's the reason why I was asking you about your CB version. Also the webapp we have, uses the new character, so it would be incompatible whith your deployment. As we have reached this point, and we need to have all the demo stuff ready, we think that what we can do is 2 demos (the mixed idea Roberto said in the call). In TI side you can show how RCM works with Firosv1, and move it with your interface, so you will show the advances in RCM, working with the environment that you control and know quite well, and in our side we can show Firosv2 advances. Regards, i?igo On 01/07/15 14:48, Bollano Gianmario wrote: Hi guys, it is definitely worth to go on and make a trial with last version of both RCM and FIROS, because they will solve some issues you've found in your trials; if this works it would be better to use them , otherwise we'll roll back to the last known working release for this demo. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: mercoled? 1 luglio 2015 14:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Demo Sprint 4.3.3 Hi, I'm looking just now these mails; I haven't understood that you were waiting any feedback from me about the launch of the new version of firos. The issue I had yesterday still at call time was after the change in configuration you suggested in the previous mail, but was only because I made a wrong deletion of the last option I had to remove. Fixed that the new firos manually launched was running, but only as a ros node, I don't know if it was able to contact the CB. At the call you said that you haven't seen the robot moving with the new version so I supposed that there was still problem with the communication with the context broker and waiting for some news from you. Sorry for the misunderstanding and if you solved those problems with the communication with the CB we can try with the new version. Meanwhile I was investigating the bug of high cpu consumption of rcm you mentioned in an old mail and I found that that happens when we launch a launcher that doesn't exist on the machine where we are trying to launch it; I think this morning I solved that but still trying if it's ok 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? 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, I?igo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What's important for the demo is to clearly explain what we'll show, not to provide tech details for the implementation. Considering the short time available, I'd propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren't last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I'd omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway... - .. and we'll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoled? 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity's name and attributes). Davide Da: Garino Pierangelo Inviato: mercoled? 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I'd like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI BR Pier Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide 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: From gianmario.bollano at telecomitalia.it Fri Jul 3 09:18:34 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Fri, 3 Jul 2015 07:18:34 +0000 Subject: [Fiware-robotics] I: [Fiware-i2nd] Preparing I2ND Slides for Sprint demo In-Reply-To: References: Message-ID: <7E649CBD84A947498203DAF8F098B1F642A7B522@telmba003ba020.telecomitalia.local> Dear all, I've seen lot of e-mail exchanged and great progress done for the next Monday demo. Please, let's not waste all our effort. Many people at the sprint demo will not be able to understand details in such a short time, but they'll remember one or two concepts. If we'll show two demos, they might remember: "here are two groups that weren't able to work jointly." Such a message does not fit with reality, but might have a disastrous effect nonetheless. Some GEs will be dropped by EC; let's not create such conditions for the Robotics GE. Instead, Let's prepare one demo, simple and working; and let's focus on preparing a shared good documentation. Davide has prepared and updated the slides for the demo sprint and put them in this shared presentation: https://docs.google.com/presentation/d/1F8M1YEkKkjrHulwuLUXaTYvFTT1edpXObSUx5XD7R98/edit?usp=sharing Please, let's try to jointly edit and enrich this presentation and the general one sent by Pier (link is in the email below). Thank you, Gianmario Da: fiware-i2nd-bounces at lists.fi-ware.org [mailto:fiware-i2nd-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 3 luglio 2015 08:28 A: fiware-i2nd at lists.fi-ware.org Oggetto: [Fiware-i2nd] Preparing I2ND Slides for Sprint demo Dear All, As anticipated in the call yesterday, I need to receive an updated set of slides (max 3) per GE, to present the progress of last Sprint during the Demo meeting on Monday. You find at link https://docs.google.com/presentation/d/1sd5CjFaWiQA9io2nOVa8c09tbRXMaR4Z7QovRRj5LfU/edit#slide=id.gb6186a633_2_155 the slides presented last month, I kindly ask GE owners of Netfloc, Kiara and OFNIC to update their three slides (What done in the Sprint, what done overall, workplan - please put if possible also references to Features) possibly by today. When doing your updates, please change the color of text, so that it's easy to find what has been updated. Note for Robotics GE Team: this GE will be shown during the demo, so I kindly ask the Team to prepare a set of slides providing the demo explanation, along with the three slides concerning the progress in the Sprint. Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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: -------------- 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 gianmario.bollano at telecomitalia.it Fri Jul 3 10:52:45 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Fri, 3 Jul 2015 08:52:45 +0000 Subject: [Fiware-robotics] Robotics pre-demo Message-ID: <7E649CBD84A947498203DAF8F098B1F642A7B666@telmba003ba020.telecomitalia.local> Hi, Davide and Fabio are setting up the Pre-demo with hangouts to do a test before the official presentation next Monday. The demo should start around 11.00 , Davide will send the invite via hangout. Gianmario 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: 2562 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 aarranz at fi.upm.es Fri Jul 3 13:42:54 2015 From: aarranz at fi.upm.es (=?UTF-8?Q?=C3=81lvaro_Arranz?=) Date: Fri, 3 Jul 2015 13:42:54 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> Message-ID: Hi all, I've added some details into the google docs. See you in a moment :) Best regards, ?lvaro On 1 July 2015 at 14:35, Bollano Gianmario < gianmario.bollano at telecomitalia.it> wrote: > Hi all, > > according to the preferences in the poll we can have the call next Friday > 3th from 2PM to 3PM. > > I?ll send you an invite. > > > > Gianmario Bollano > > > > *Da:* Bollano Gianmario > *Inviato:* marted? 30 giugno 2015 17:10 > *A:* '?lvaro Arranz'; Luis L?pez Fern?ndez > *Cc:* Garino Pierangelo; amagan at conwet.com; Javier Soriano; > fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org > *Oggetto:* R: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > > > Hi Luis and all, > > we propose a Doodle poll to select a timeslot for the call. > > The link is: > > http://doodle.com/fb6gx4wbbqupwkwu > > > > Please, > > select your preferred time. > > > > Gianmario > > > > *Da:* aarranz at conwet.com [mailto:aarranz at conwet.com] *Per conto di *?lvaro > Arranz > *Inviato:* marted? 30 giugno 2015 16:55 > *A:* Luis L?pez Fern?ndez > *Cc:* Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier > Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org > > *Oggetto:* Re: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > > > Hi, > > > > sorry for the delay in the response, we are busy with the closing and > planning phases of the sprint. Also I'm organising my travel to the Campus > party event at Mexico. > > > > I'll work on providing a better feedback asap (I'll try to provide it > today). Anyway, updating our widgets for accessing this one-to-many service > will be easy, we can synchronise with the Kurento team for making the > needed changes for selecting the master video stream, etc... This is only a > thing of managing some new commands through the WebSocket connection and > recreating the WebRTC connections. I don't forecast, as Luis, any problem > on this side. > > > > We are also interested in join the call :). > > > > Best regards, > > ?lvaro > > > > On 30 June 2015 at 16:27, Luis L?pez Fern?ndez wrote: > > Hi Gianmario, > > > > Modifying the Kurento demo for one-to-many to support several robots it's > quite trivial. We can do it for you if necessary. This is not an issue. > > > > The main problem I detect is at the WebRTC client embedded in the robot. > If this client is Chrome, then you may need human intervention for webcam > capture. There are hacks for this, but we need to analyze carefully your > requirements. Otherwise, the option is to compile the WebRTC Chrome stack > separately and write a C++ application at the robot controlling it. This > may require some more relevant efforts and this is the issue we need to > discuss. > > > > I'm available during most of this week for discussing. Just propose a slot > and we can try to arrange for a call. > > > > Thanks. > > > > ----------------------------------------------------------- > > Luis L?pez Fern?ndez > > Subdirector de Investigaci?n y Relaciones con la Empresa > > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > > Universidad Rey Juan Carlos > > http://www.etsit.urjc.es > > e-mail: luis.lopez at urjc.es > > Tf1: +34 914 888 747 > > Tf2: + 34 914 888 713 > > > > > > > El 30/06/2015, a las 16:21, Bollano Gianmario < > gianmario.bollano at telecomitalia.it> escribi?: > > > > Hi Luis, > > thank you for your support and your clarification. > > As a short summary, we also have tested a WebRTC client based on Webkit > but haven?t yet found the optimal solution, then it would be useful to > discuss further this issue. > > The team has done tests with the JS version for the Kurento Client with > NodeJS; our idea is to use a single App Server for the master Client and > all Viewer clients as in the One-To-Many Kurento tutorial ( > http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html > ). > > We have not yet found a solution when more Robots can act as master and > can transmit video (i.e. we have more than one Master). > > We are also waiting feedback from Wirecloud to understand how we may use > or adapt the Kurento widget. > > > > The guys of the Robotics team will go through your notes to check your > proposals and to define technical details if needed. > > > > Thank you, > > Gianmario > > > > > > *Da:* fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware- > robotics-bounces at lists.fi-ware.org] *Per conto di *Luis L?pez Fern?ndez > *Inviato:* marted? 30 giugno 2015 13:05 > *A:* Garino Pierangelo > *Cc:* amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; > fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es > *Oggetto:* Re: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > > > Hi Pier, > > > > I added several comments in your document answering your questions. In > general, I think that the general picture is OK from the perspective of > Kurento and I don't forecast any major problems. The only exception is in > relation to the WebRTC software to be embedded at the robot. In principle, > it seems that you are planning to use directly a Chrome browser instance. > This restricts a lot the type of features you may be capable of accessing > and this may require human intervention at the robot each time the webcam > is activated. I thing it should be worthy to discuss about this specific > item so that all of us are in the same page in relation to the consequences > of using directly a Chrome instance for that. > > > > Best regards. > > > > ----------------------------------------------------------- > > Luis L?pez Fern?ndez > > Subdirector de Investigaci?n y Relaciones con la Empresa > > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > > Universidad Rey Juan Carlos > > http://www.etsit.urjc.es > > e-mail: luis.lopez at urjc.es > > Tf1: +34 914 888 747 > > Tf2: + 34 914 888 713 > > > > > > El 23/06/2015, a las 12:22, Garino Pierangelo < > pierangelo.garino at telecomitalia.it> escribi?: > > > > Dear All, > > > > This message is intended to provide to Kurento and Wirecloud teams further > details about the robotics live demo we are working on, in order to make it > clearer what we?d like to achieve, and what should be implemented on their > side (particularly about wirecloud widgets and dashboard). > > > > We have prepared a shared document at the following link > https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# > which > refines the description of the live demo (later this doc will merge with > the workplan description we already shared in the past). > > > > The document is composed of three parts: > > - The first one (Strep 1: Managing interactively robots) is a > refinement of live demo deliverable section 4.4.3 > > - The second one (Design of step 1: Teleoperation as a Service > (TaaS)) is more or less the same contents of deliverable section 4.4.4 > > - *The third part* (Detailed description (script) of demo > implementation) *is the most important one*: we took as an example the > live demo script doc that Javier distributed through the live demo mailing > lists, which seemed to us a helpful way to provide a detailed description > of the demo, both for people who will watch it and for implementers of the > demo itself. > > > > *We kindly ask Luis, Javier, Alvaro (*well all team members?) to go > through the description of the demo and provide us a feedback, about > how/when this can be implemented (is it meaningful/feasible, etc?), giving > possibly answer to the questions/comments we have written there. With your > support in linking with Kurento media server and developing specific > widgets, we?ll be able to ?complete the picture? and proceed straight to > the assembly of all demo parts. > > > > Many thanks and BR > > > > Pier > > > > > > > > *Da:* fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware- > robotics-bounces at lists.fi-ware.org] *Per conto di *Colombatto Davide > *Inviato:* marted? 16 giugno 2015 12:34 > *A:* Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; > amagan at conwet.com; fdelavega at fi.upm.es > *Cc:* fiware-robotics at lists.fi-ware.org > *Oggetto:* [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > > > Hi Luis and Wirecloud guys, > > > > We have some doubts about the use of Kurento and Wirecloud widgets for > Kurento for the Robotics Live Demo. > > > > 1) For what concern *Kurento*, in our past tests we tried the > tutorial > http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where > it is said that it can be present only one WebRTC-Master and many > WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can > send the video and the others can receive the video). > > Starting from this point we think the slide2 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts > the Kurento One2Many architecture. > > Considering what mentioned above, if we want to use two different robots > (that act as WebRTC-Masters in order to send video) do we need to use two > different Kurento Application Servers (that act as Kurento-Clients) or a > single Kurento Application Server (that acts as Kurento-Client) is able to > manage multiple robots video transmission? > > > > 2) For what concern *Wirecloud widgets for Kurento*, starting from > the slide2 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do > the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the > Kurento One2Many architecture explained above in the point1? > > If it is correct, for the Robotics live demo will Wirecloud also host the > Kurento Application Servers (i.e. a single one or one for each robot that > act as WebRTC-Master in order to send video) within the Wirecloud > Application Server as depicted in the slide3 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 > ? > > > > Thank you, > > Davide > > 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.* > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahernandez at ikergune.com Fri Jul 3 13:48:52 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Fri, 3 Jul 2015 13:48:52 +0200 Subject: [Fiware-robotics] I: [Fiware-i2nd] Preparing I2ND Slides for Sprint demo In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642A7B522@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F642A7B522@telmba003ba020.telecomitalia.local> Message-ID: Hello all, I don't want to get lost in the details, but I agree on the fact that given the situation with the EC willing to drop some GEs, this demo is an important milestone for the whole Robotics Team. Therefore, I think all capabilities developed along the past months should be shown and shared among whoever shows up at the Demo meeting. In previous demos we've hided modules such as the map, multi-robot management and configuration, the initial joystick control or even the camera streaming just so we could extend those tasks and show a homogeneous development. As Gianmario just said, people will remember just one or two concepts, and honestly, I think this team could do better than just moving a robot forward. This is something we can discuss in the next call, but please, take this as an opportunity for the whole team to make the Robotics GE an interesting and rapidly growing GE. Regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Bollano Gianmario Enviado el: viernes, 3 de julio de 2015 9:19 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] I: [Fiware-i2nd] Preparing I2ND Slides for Sprint demo Dear all, I've seen lot of e-mail exchanged and great progress done for the next Monday demo. Please, let's not waste all our effort. Many people at the sprint demo will not be able to understand details in such a short time, but they'll remember one or two concepts. If we'll show two demos, they might remember: "here are two groups that weren't able to work jointly." Such a message does not fit with reality, but might have a disastrous effect nonetheless. Some GEs will be dropped by EC; let's not create such conditions for the Robotics GE. Instead, Let's prepare one demo, simple and working; and let's focus on preparing a shared good documentation. Davide has prepared and updated the slides for the demo sprint and put them in this shared presentation: https://docs.google.com/presentation/d/1F8M1YEkKkjrHulwuLUXaTYvFTT1edpXObSUx5XD7R98/edit?usp=sharing Please, let's try to jointly edit and enrich this presentation and the general one sent by Pier (link is in the email below). Thank you, Gianmario Da: fiware-i2nd-bounces at lists.fi-ware.org [mailto:fiware-i2nd-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 3 luglio 2015 08:28 A: fiware-i2nd at lists.fi-ware.org Oggetto: [Fiware-i2nd] Preparing I2ND Slides for Sprint demo Dear All, As anticipated in the call yesterday, I need to receive an updated set of slides (max 3) per GE, to present the progress of last Sprint during the Demo meeting on Monday. You find at link https://docs.google.com/presentation/d/1sd5CjFaWiQA9io2nOVa8c09tbRXMaR4Z7QovRRj5LfU/edit#slide=id.gb6186a633_2_155 the slides presented last month, I kindly ask GE owners of Netfloc, Kiara and OFNIC to update their three slides (What done in the Sprint, what done overall, workplan - please put if possible also references to Features) possibly by today. When doing your updates, please change the color of text, so that it's easy to find what has been updated. Note for Robotics GE Team: this GE will be shown during the demo, so I kindly ask the Team to prepare a set of slides providing the demo explanation, along with the three slides concerning the progress in the Sprint. Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01D0B595.2DE68120]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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 01D0B595.2DE68120]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 luis.lopez at urjc.es Fri Jul 3 14:10:54 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Fri, 3 Jul 2015 14:10:54 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> Message-ID: <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> I canot find the details of the call. Can anyone send them to me? ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 03/07/2015, a las 13:42, ?lvaro Arranz escribi?: > Hi all, > > I've added some details into the google docs. > > See you in a moment :) > > Best regards, > ?lvaro > > On 1 July 2015 at 14:35, Bollano Gianmario wrote: > Hi all, > > according to the preferences in the poll we can have the call next Friday 3th from 2PM to 3PM. > > I?ll send you an invite. > > > > Gianmario Bollano > > > > Da: Bollano Gianmario > Inviato: marted? 30 giugno 2015 17:10 > A: '?lvaro Arranz'; Luis L?pez Fern?ndez > Cc: Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org > Oggetto: R: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > > > Hi Luis and all, > > we propose a Doodle poll to select a timeslot for the call. > > The link is: > > http://doodle.com/fb6gx4wbbqupwkwu > > > > Please, > > select your preferred time. > > > > Gianmario > > > > Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz > Inviato: marted? 30 giugno 2015 16:55 > A: Luis L?pez Fern?ndez > Cc: Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org > > > Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > > > Hi, > > > > sorry for the delay in the response, we are busy with the closing and planning phases of the sprint. Also I'm organising my travel to the Campus party event at Mexico. > > > > I'll work on providing a better feedback asap (I'll try to provide it today). Anyway, updating our widgets for accessing this one-to-many service will be easy, we can synchronise with the Kurento team for making the needed changes for selecting the master video stream, etc... This is only a thing of managing some new commands through the WebSocket connection and recreating the WebRTC connections. I don't forecast, as Luis, any problem on this side. > > > > We are also interested in join the call :). > > > > Best regards, > > ?lvaro > > > > On 30 June 2015 at 16:27, Luis L?pez Fern?ndez wrote: > > Hi Gianmario, > > > > Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. > > > > The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. > > > > I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. > > > > Thanks. > > > > ----------------------------------------------------------- > > Luis L?pez Fern?ndez > > Subdirector de Investigaci?n y Relaciones con la Empresa > > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > > Universidad Rey Juan Carlos > > http://www.etsit.urjc.es > > e-mail: luis.lopez at urjc.es > > Tf1: +34 914 888 747 > > Tf2: + 34 914 888 713 > > > > > > > > El 30/06/2015, a las 16:21, Bollano Gianmario escribi?: > > > > Hi Luis, > > thank you for your support and your clarification. > > As a short summary, we also have tested a WebRTC client based on Webkit but haven?t yet found the optimal solution, then it would be useful to discuss further this issue. > > The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). > > We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). > > We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. > > > > The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. > > > > Thank you, > > Gianmario > > > > > > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez > Inviato: marted? 30 giugno 2015 13:05 > A: Garino Pierangelo > Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es > Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > > > Hi Pier, > > > > I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. > > > > Best regards. > > > > ----------------------------------------------------------- > > Luis L?pez Fern?ndez > > Subdirector de Investigaci?n y Relaciones con la Empresa > > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > > Universidad Rey Juan Carlos > > http://www.etsit.urjc.es > > e-mail: luis.lopez at urjc.es > > Tf1: +34 914 888 747 > > Tf2: + 34 914 888 713 > > > > > > > El 23/06/2015, a las 12:22, Garino Pierangelo escribi?: > > > > Dear All, > > > > This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we?d like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). > > > > We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). > > > > The document is composed of three parts: > > - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 > > - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 > > - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. > > > > We kindly ask Luis, Javier, Alvaro (well all team members?) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we?ll be able to ?complete the picture? and proceed straight to the assembly of all demo parts. > > > > Many thanks and BR > > > > Pier > > > > > > > > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide > Inviato: marted? 16 giugno 2015 12:34 > A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > > > Hi Luis and Wirecloud guys, > > > > We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. > > > > 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). > > Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. > > Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? > > > > 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? > > If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? > > > > Thank you, > > Davide > > 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. > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri Jul 3 14:11:21 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 3 Jul 2015 12:11:21 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> Message-ID: Hi Alvaro and Luis, We are using hangout, can you try to join this link https://plus.google.com/hangouts/_/gw3g3o72p5s26fwpiemztggwxqa or send me your username? BR Pier Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: venerd? 3 luglio 2015 13:43 A: Bollano Gianmario Cc: Luis L?pez Fern?ndez; Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi all, I've added some details into the google docs. See you in a moment :) Best regards, ?lvaro On 1 July 2015 at 14:35, Bollano Gianmario > wrote: Hi all, according to the preferences in the poll we can have the call next Friday 3th from 2PM to 3PM. I?ll send you an invite. Gianmario Bollano Da: Bollano Gianmario Inviato: marted? 30 giugno 2015 17:10 A: '?lvaro Arranz'; Luis L?pez Fern?ndez Cc: Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and all, we propose a Doodle poll to select a timeslot for the call. The link is: http://doodle.com/fb6gx4wbbqupwkwu Please, select your preferred time. Gianmario Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: marted? 30 giugno 2015 16:55 A: Luis L?pez Fern?ndez Cc: Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi, sorry for the delay in the response, we are busy with the closing and planning phases of the sprint. Also I'm organising my travel to the Campus party event at Mexico. I'll work on providing a better feedback asap (I'll try to provide it today). Anyway, updating our widgets for accessing this one-to-many service will be easy, we can synchronise with the Kurento team for making the needed changes for selecting the master video stream, etc... This is only a thing of managing some new commands through the WebSocket connection and recreating the WebRTC connections. I don't forecast, as Luis, any problem on this side. We are also interested in join the call :). Best regards, ?lvaro On 30 June 2015 at 16:27, Luis L?pez Fern?ndez > wrote: Hi Gianmario, Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. Thanks. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 30/06/2015, a las 16:21, Bollano Gianmario > escribi?: Hi Luis, thank you for your support and your clarification. As a short summary, we also have tested a WebRTC client based on Webkit but haven?t yet found the optimal solution, then it would be useful to discuss further this issue. The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. Thank you, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez Inviato: marted? 30 giugno 2015 13:05 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo > escribi?: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we?d like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members?) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we?ll be able to ?complete the picture? and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahernandez at ikergune.com Fri Jul 3 14:12:27 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Fri, 3 Jul 2015 14:12:27 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> Message-ID: https://plus.google.com/hangouts/_/gw3g3o72p5s26fwpiemztggwxqa De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Luis L?pez Fern?ndez Enviado el: viernes, 3 de julio de 2015 14:11 Para: ?lvaro Arranz CC: amagan at conwet.com; fiware-robotics at lists.fi-ware.org; Javier Soriano; fdelavega at fi.upm.es Asunto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud I canot find the details of the call. Can anyone send them to me? ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 03/07/2015, a las 13:42, ?lvaro Arranz > escribi?: Hi all, I've added some details into the google docs. See you in a moment :) Best regards, ?lvaro On 1 July 2015 at 14:35, Bollano Gianmario > wrote: Hi all, according to the preferences in the poll we can have the call next Friday 3th from 2PM to 3PM. I'll send you an invite. Gianmario Bollano Da: Bollano Gianmario Inviato: marted? 30 giugno 2015 17:10 A: '?lvaro Arranz'; Luis L?pez Fern?ndez Cc: Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and all, we propose a Doodle poll to select a timeslot for the call. The link is: http://doodle.com/fb6gx4wbbqupwkwu Please, select your preferred time. Gianmario Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: marted? 30 giugno 2015 16:55 A: Luis L?pez Fern?ndez Cc: Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi, sorry for the delay in the response, we are busy with the closing and planning phases of the sprint. Also I'm organising my travel to the Campus party event at Mexico. I'll work on providing a better feedback asap (I'll try to provide it today). Anyway, updating our widgets for accessing this one-to-many service will be easy, we can synchronise with the Kurento team for making the needed changes for selecting the master video stream, etc... This is only a thing of managing some new commands through the WebSocket connection and recreating the WebRTC connections. I don't forecast, as Luis, any problem on this side. We are also interested in join the call :). Best regards, ?lvaro On 30 June 2015 at 16:27, Luis L?pez Fern?ndez > wrote: Hi Gianmario, Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. Thanks. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 30/06/2015, a las 16:21, Bollano Gianmario > escribi?: Hi Luis, thank you for your support and your clarification. As a short summary, we also have tested a WebRTC client based on Webkit but haven't yet found the optimal solution, then it would be useful to discuss further this issue. The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. Thank you, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez Inviato: marted? 30 giugno 2015 13:05 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo > escribi?: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we'd like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members...) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we'll be able to 'complete the picture' and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ... of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aarranz at fi.upm.es Fri Jul 3 15:19:49 2015 From: aarranz at fi.upm.es (=?UTF-8?Q?=C3=81lvaro_Arranz?=) Date: Fri, 3 Jul 2015 15:19:49 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> Message-ID: Some screenshots of the joystick widget work: Best regards, ?lvaro On 3 July 2015 at 14:12, Angel Hernandez wrote: > https://plus.google.com/hangouts/_/gw3g3o72p5s26fwpiemztggwxqa > > > > *De:* fiware-robotics-bounces at lists.fi-ware.org [mailto: > fiware-robotics-bounces at lists.fi-ware.org] *En nombre de *Luis L?pez > Fern?ndez > *Enviado el:* viernes, 3 de julio de 2015 14:11 > *Para:* ?lvaro Arranz > *CC:* amagan at conwet.com; fiware-robotics at lists.fi-ware.org; Javier > Soriano; fdelavega at fi.upm.es > *Asunto:* Re: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > > > I canot find the details of the call. Can anyone send them to me? > > > > ----------------------------------------------------------- > > Luis L?pez Fern?ndez > > Subdirector de Investigaci?n y Relaciones con la Empresa > > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > > Universidad Rey Juan Carlos > > http://www.etsit.urjc.es > > e-mail: luis.lopez at urjc.es > > Tf1: +34 914 888 747 > > Tf2: + 34 914 888 713 > > > > > > > > El 03/07/2015, a las 13:42, ?lvaro Arranz escribi?: > > > > Hi all, > > > > I've added some details into the google docs. > > > > See you in a moment :) > > > > Best regards, > > ?lvaro > > > > On 1 July 2015 at 14:35, Bollano Gianmario < > gianmario.bollano at telecomitalia.it> wrote: > > Hi all, > > according to the preferences in the poll we can have the call next Friday > 3th from 2PM to 3PM. > > I?ll send you an invite. > > > > Gianmario Bollano > > > > *Da:* Bollano Gianmario > *Inviato:* marted? 30 giugno 2015 17:10 > *A:* '?lvaro Arranz'; Luis L?pez Fern?ndez > *Cc:* Garino Pierangelo; amagan at conwet.com; Javier Soriano; > fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org > *Oggetto:* R: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > > > Hi Luis and all, > > we propose a Doodle poll to select a timeslot for the call. > > The link is: > > http://doodle.com/fb6gx4wbbqupwkwu > > > > Please, > > select your preferred time. > > > > Gianmario > > > > *Da:* aarranz at conwet.com [mailto:aarranz at conwet.com] *Per conto di *?lvaro > Arranz > *Inviato:* marted? 30 giugno 2015 16:55 > *A:* Luis L?pez Fern?ndez > *Cc:* Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier > Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org > > > *Oggetto:* Re: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > > > > > Hi, > > > > sorry for the delay in the response, we are busy with the closing and > planning phases of the sprint. Also I'm organising my travel to the Campus > party event at Mexico. > > > > I'll work on providing a better feedback asap (I'll try to provide it > today). Anyway, updating our widgets for accessing this one-to-many service > will be easy, we can synchronise with the Kurento team for making the > needed changes for selecting the master video stream, etc... This is only a > thing of managing some new commands through the WebSocket connection and > recreating the WebRTC connections. I don't forecast, as Luis, any problem > on this side. > > > > We are also interested in join the call :). > > > > Best regards, > > ?lvaro > > > > On 30 June 2015 at 16:27, Luis L?pez Fern?ndez wrote: > > Hi Gianmario, > > > > Modifying the Kurento demo for one-to-many to support several robots it's > quite trivial. We can do it for you if necessary. This is not an issue. > > > > The main problem I detect is at the WebRTC client embedded in the robot. > If this client is Chrome, then you may need human intervention for webcam > capture. There are hacks for this, but we need to analyze carefully your > requirements. Otherwise, the option is to compile the WebRTC Chrome stack > separately and write a C++ application at the robot controlling it. This > may require some more relevant efforts and this is the issue we need to > discuss. > > > > I'm available during most of this week for discussing. Just propose a slot > and we can try to arrange for a call. > > > > Thanks. > > > > ----------------------------------------------------------- > > Luis L?pez Fern?ndez > > Subdirector de Investigaci?n y Relaciones con la Empresa > > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > > Universidad Rey Juan Carlos > > http://www.etsit.urjc.es > > e-mail: luis.lopez at urjc.es > > Tf1: +34 914 888 747 > > Tf2: + 34 914 888 713 > > > > > > El 30/06/2015, a las 16:21, Bollano Gianmario < > gianmario.bollano at telecomitalia.it> escribi?: > > > > Hi Luis, > > thank you for your support and your clarification. > > As a short summary, we also have tested a WebRTC client based on Webkit > but haven?t yet found the optimal solution, then it would be useful to > discuss further this issue. > > The team has done tests with the JS version for the Kurento Client with > NodeJS; our idea is to use a single App Server for the master Client and > all Viewer clients as in the One-To-Many Kurento tutorial ( > http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html > ). > > We have not yet found a solution when more Robots can act as master and > can transmit video (i.e. we have more than one Master). > > We are also waiting feedback from Wirecloud to understand how we may use > or adapt the Kurento widget. > > > > The guys of the Robotics team will go through your notes to check your > proposals and to define technical details if needed. > > > > Thank you, > > Gianmario > > > > > > *Da:* fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware- > robotics-bounces at lists.fi-ware.org] *Per conto di *Luis L?pez Fern?ndez > *Inviato:* marted? 30 giugno 2015 13:05 > *A:* Garino Pierangelo > *Cc:* amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; > fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es > *Oggetto:* Re: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > > > Hi Pier, > > > > I added several comments in your document answering your questions. In > general, I think that the general picture is OK from the perspective of > Kurento and I don't forecast any major problems. The only exception is in > relation to the WebRTC software to be embedded at the robot. In principle, > it seems that you are planning to use directly a Chrome browser instance. > This restricts a lot the type of features you may be capable of accessing > and this may require human intervention at the robot each time the webcam > is activated. I thing it should be worthy to discuss about this specific > item so that all of us are in the same page in relation to the consequences > of using directly a Chrome instance for that. > > > > Best regards. > > > > ----------------------------------------------------------- > > Luis L?pez Fern?ndez > > Subdirector de Investigaci?n y Relaciones con la Empresa > > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > > Universidad Rey Juan Carlos > > http://www.etsit.urjc.es > > e-mail: luis.lopez at urjc.es > > Tf1: +34 914 888 747 > > Tf2: + 34 914 888 713 > > > > > > El 23/06/2015, a las 12:22, Garino Pierangelo < > pierangelo.garino at telecomitalia.it> escribi?: > > > > Dear All, > > > > This message is intended to provide to Kurento and Wirecloud teams further > details about the robotics live demo we are working on, in order to make it > clearer what we?d like to achieve, and what should be implemented on their > side (particularly about wirecloud widgets and dashboard). > > > > We have prepared a shared document at the following link > https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# > which > refines the description of the live demo (later this doc will merge with > the workplan description we already shared in the past). > > > > The document is composed of three parts: > > - The first one (Strep 1: Managing interactively robots) is a > refinement of live demo deliverable section 4.4.3 > > - The second one (Design of step 1: Teleoperation as a Service > (TaaS)) is more or less the same contents of deliverable section 4.4.4 > > - *The third part* (Detailed description (script) of demo > implementation) *is the most important one*: we took as an example the > live demo script doc that Javier distributed through the live demo mailing > lists, which seemed to us a helpful way to provide a detailed description > of the demo, both for people who will watch it and for implementers of the > demo itself. > > > > *We kindly ask Luis, Javier, Alvaro (*well all team members?) to go > through the description of the demo and provide us a feedback, about > how/when this can be implemented (is it meaningful/feasible, etc?), giving > possibly answer to the questions/comments we have written there. With your > support in linking with Kurento media server and developing specific > widgets, we?ll be able to ?complete the picture? and proceed straight to > the assembly of all demo parts. > > > > Many thanks and BR > > > > Pier > > > > > > > > *Da:* fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware- > robotics-bounces at lists.fi-ware.org] *Per conto di *Colombatto Davide > *Inviato:* marted? 16 giugno 2015 12:34 > *A:* Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; > amagan at conwet.com; fdelavega at fi.upm.es > *Cc:* fiware-robotics at lists.fi-ware.org > *Oggetto:* [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > > > Hi Luis and Wirecloud guys, > > > > We have some doubts about the use of Kurento and Wirecloud widgets for > Kurento for the Robotics Live Demo. > > > > 1) For what concern *Kurento*, in our past tests we tried the > tutorial > http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where > it is said that it can be present only one WebRTC-Master and many > WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can > send the video and the others can receive the video). > > Starting from this point we think the slide2 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts > the Kurento One2Many architecture. > > Considering what mentioned above, if we want to use two different robots > (that act as WebRTC-Masters in order to send video) do we need to use two > different Kurento Application Servers (that act as Kurento-Clients) or a > single Kurento Application Server (that acts as Kurento-Client) is able to > manage multiple robots video transmission? > > > > 2) For what concern *Wirecloud widgets for Kurento*, starting from > the slide2 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do > the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the > Kurento One2Many architecture explained above in the point1? > > If it is correct, for the Robotics live demo will Wirecloud also host the > Kurento Application Servers (i.e. a single one or one for each robot that > act as WebRTC-Master in order to send video) within the Wirecloud > Application Server as depicted in the slide3 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 > ? > > > > Thank you, > > Davide > > 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.* > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Captura de pantalla 2015-07-03 a las 11.33.56.png Type: image/png Size: 129171 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Captura de pantalla 2015-07-03 a las 11.49.30.png Type: image/png Size: 142173 bytes Desc: not available URL: From davide.colombatto at telecomitalia.it Mon Jul 6 15:16:51 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Mon, 6 Jul 2015 13:16:51 +0000 Subject: [Fiware-robotics] Spring Planning 4.4.1 Message-ID: <069906BED271EB4A883BD9578DCDD3541E935B48@TELMBA006RM001.telecomitalia.local> Hi guys, have you completed the Sprint Planning 4.4.1 and can we close the JIRA issue MIN-366 (FIWARE.WorkItem.I2ND.Robotics.Agile.Sprint-441.Planning)? Thank you, Davide 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 pierangelo.garino at telecomitalia.it Tue Jul 7 16:56:15 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 7 Jul 2015 14:56:15 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> Message-ID: Dear Alvaro, I have some questions about the widgets and the robotics demo, after the call we had last week, your feedback will surely help me clarifying the related issues. - Is the ?Joystick? widget in the pictures above composed of the joystick itself, i.e. is the ?Spy wiring? a second widget? - When you propose to put together the camera view, the joystick and the robot buttons, do you mean to have the three of them in the same widget (see first picture below), or are they separate widgets superimposed? In the latter case, I believe that a better layout would be having them separate as layout (see second picture below). First picture: [cid:image002.png at 01D0B8D5.D26D55F0] Second picture: [cid:image004.png at 01D0B8D5.D26D55F0] Thanks in advance for your feedback. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di ?lvaro Arranz Inviato: venerd? 3 luglio 2015 15:20 A: Angel Hernandez Cc: amagan at conwet.com; Javier Soriano; fiware-robotics at lists.fi-ware.org; fdelavega at fi.upm.es; Luis L?pez Fern?ndez Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Some screenshots of the joystick widget work: [cid:image006.png at 01D0B8D5.D26D55F0] [cid:image012.png at 01D0B8D5.D26D55F0] Best regards, ?lvaro On 3 July 2015 at 14:12, Angel Hernandez > wrote: https://plus.google.com/hangouts/_/gw3g3o72p5s26fwpiemztggwxqa De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Luis L?pez Fern?ndez Enviado el: viernes, 3 de julio de 2015 14:11 Para: ?lvaro Arranz CC: amagan at conwet.com; fiware-robotics at lists.fi-ware.org; Javier Soriano; fdelavega at fi.upm.es Asunto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud I canot find the details of the call. Can anyone send them to me? ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 03/07/2015, a las 13:42, ?lvaro Arranz > escribi?: Hi all, I've added some details into the google docs. See you in a moment :) Best regards, ?lvaro On 1 July 2015 at 14:35, Bollano Gianmario > wrote: Hi all, according to the preferences in the poll we can have the call next Friday 3th from 2PM to 3PM. I?ll send you an invite. Gianmario Bollano Da: Bollano Gianmario Inviato: marted? 30 giugno 2015 17:10 A: '?lvaro Arranz'; Luis L?pez Fern?ndez Cc: Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and all, we propose a Doodle poll to select a timeslot for the call. The link is: http://doodle.com/fb6gx4wbbqupwkwu Please, select your preferred time. Gianmario Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: marted? 30 giugno 2015 16:55 A: Luis L?pez Fern?ndez Cc: Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi, sorry for the delay in the response, we are busy with the closing and planning phases of the sprint. Also I'm organising my travel to the Campus party event at Mexico. I'll work on providing a better feedback asap (I'll try to provide it today). Anyway, updating our widgets for accessing this one-to-many service will be easy, we can synchronise with the Kurento team for making the needed changes for selecting the master video stream, etc... This is only a thing of managing some new commands through the WebSocket connection and recreating the WebRTC connections. I don't forecast, as Luis, any problem on this side. We are also interested in join the call :). Best regards, ?lvaro On 30 June 2015 at 16:27, Luis L?pez Fern?ndez > wrote: Hi Gianmario, Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. Thanks. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 30/06/2015, a las 16:21, Bollano Gianmario > escribi?: Hi Luis, thank you for your support and your clarification. As a short summary, we also have tested a WebRTC client based on Webkit but haven?t yet found the optimal solution, then it would be useful to discuss further this issue. The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. Thank you, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez Inviato: marted? 30 giugno 2015 13:05 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo > escribi?: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we?d like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members?) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we?ll be able to ?complete the picture? and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 161806 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 158123 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 68500 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image012.png Type: image/png Size: 85361 bytes Desc: image012.png URL: From pierangelo.garino at telecomitalia.it Fri Jul 10 15:09:38 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 10 Jul 2015 13:09:38 +0000 Subject: [Fiware-robotics] Community account for Robotics live demo Message-ID: Dear All, We've got a community account for the live demo implementation! I'm going to add to it all the users who will work on it. The owner of the account is myself, however the Organization is named 'Robotics-live-demo cloud'. Please send me your account name in FIWARE Lab so that I can add them to the organization and let you access it. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- 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 fabio.dibenedetto at consoft.it Mon Jul 13 14:50:34 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Mon, 13 Jul 2015 12:50:34 +0000 Subject: [Fiware-robotics] R: Community account for Robotics live demo In-Reply-To: References: Message-ID: <8f92780fec8944daa1fc8e01e6909109@EXCHMBX2.consoft.it> I had an account, but it doesn't let me access it so I have just created a new one (this time I've been able to use my company mail): my account name is FabioDiBenedetto add me please Fabio Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 10 luglio 2015 15:10 A: fiware-robotics at lists.fi-ware.org Cc: Chulani, Ilknur (ilknur.chulani at atos.net) Oggetto: [Fiware-robotics] Community account for Robotics live demo Priorit?: Alta Dear All, We've got a community account for the live demo implementation! I'm going to add to it all the users who will work on it. The owner of the account is myself, however the Organization is named 'Robotics-live-demo cloud'. Please send me your account name in FIWARE Lab so that I can add them to the organization and let you access it. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Mon Jul 13 15:00:33 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 13 Jul 2015 13:00:33 +0000 Subject: [Fiware-robotics] R: Community account for Robotics live demo In-Reply-To: <8f92780fec8944daa1fc8e01e6909109@EXCHMBX2.consoft.it> References: <8f92780fec8944daa1fc8e01e6909109@EXCHMBX2.consoft.it> Message-ID: Hi Fbio, I have added you as a member of the Organization. You should have access to it. In case you have troubles please let me know. BR Pier Da: fabio.dibenedetto at consoft.it [mailto:fabio.dibenedetto at consoft.it] Inviato: luned? 13 luglio 2015 14:51 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Chulani, Ilknur (ilknur.chulani at atos.net) Oggetto: R: Community account for Robotics live demo I had an account, but it doesn't let me access it so I have just created a new one (this time I've been able to use my company mail): my account name is FabioDiBenedetto add me please Fabio Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 10 luglio 2015 15:10 A: fiware-robotics at lists.fi-ware.org Cc: Chulani, Ilknur (ilknur.chulani at atos.net) Oggetto: [Fiware-robotics] Community account for Robotics live demo Priorit?: Alta Dear All, We've got a community account for the live demo implementation! I'm going to add to it all the users who will work on it. The owner of the account is myself, however the Organization is named 'Robotics-live-demo cloud'. Please send me your account name in FIWARE Lab so that I can add them to the organization and let you access it. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From fabio.dibenedetto at consoft.it Mon Jul 13 18:15:13 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Mon, 13 Jul 2015 16:15:13 +0000 Subject: [Fiware-robotics] rcm driver firos interaction In-Reply-To: <8f92780fec8944daa1fc8e01e6909109@EXCHMBX2.consoft.it> References: <8f92780fec8944daa1fc8e01e6909109@EXCHMBX2.consoft.it> Message-ID: <5449e55f31aa4aa0930829c0b84c15b4@EXCHMBX2.consoft.it> Hi guys, I was doing some tests on rcm driver side to see if it sends and receives messages as we agreed on the openspec document. Looking at your code I've seen that you added some messages but they are internal in your package and not in robotics_msgs as I understood we have to use. I took the liberty to create this package as I understood the openspec and use that for rcm driver: I share this package as attach of this mail so that the 2 components can better cooperate. See if it is ok and please update firos to use that and not the internal messages in your package if not already do that As always the zip has a password ("robotics") -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: robotics_msgs.zip Type: application/x-zip-compressed Size: 2669 bytes Desc: robotics_msgs.zip URL: From gianmario.bollano at telecomitalia.it Tue Jul 14 10:15:28 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 14 Jul 2015 08:15:28 +0000 Subject: [Fiware-robotics] Links to shared docs Message-ID: <7E649CBD84A947498203DAF8F098B1F642A82836@telmba003ba020.telecomitalia.local> Robotics Call minutes: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo/edit?pli=1 Robotics Live demo detail: https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit?pli=1#heading=h.wo297vomr0zs ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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 gianmario.bollano at telecomitalia.it Tue Jul 14 12:26:10 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 14 Jul 2015 10:26:10 +0000 Subject: [Fiware-robotics] Robotics in FIWARE-LAB: public IP addresses Message-ID: <7E649CBD84A947498203DAF8F098B1F642A82968@telmba003ba020.telecomitalia.local> Dear Alvaro and others, we have successfully asked for the creation of an account for the Robotics Live Demo. We are now facing a major issue: it seems we can only have one public IP address. We would like to ask you an important question: using Wirecloud instance in FIWARE, can Widgets access to VMs hosted in FIWARE-LAB (through piping) using their private addresses? Or do we need a public IP address for each VM? For instance, we'll have one VM for Kurento, one VM for ContextBroker, one VM for Robotics, and widgets will access each of them: can we do this using their private IP addresses if we'll only have one public IP address for all Robotics environment? Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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 jjaime at ikergune.com Wed Jul 15 16:35:59 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Wed, 15 Jul 2015 16:35:59 +0200 Subject: [Fiware-robotics] R: Community account for Robotics live demo References: <8f92780fec8944daa1fc8e01e6909109@EXCHMBX2.consoft.it> Message-ID: Hi all, Pier, could you add the user "Ikergune A.I.E." (firos at ikergune.com) to the community. Thank you very much, Pepe. On 13/07/15 15:00, Garino Pierangelo wrote: Hi Fbio, I have added you as a member of the Organization. You should have access to it. In case you have troubles please let me know. BR Pier Da: fabio.dibenedetto at consoft.it [mailto:fabio.dibenedetto at consoft.it] Inviato: luned? 13 luglio 2015 14:51 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Chulani, Ilknur (ilknur.chulani at atos.net) Oggetto: R: Community account for Robotics live demo I had an account, but it doesn?t let me access it so I have just created a new one (this time I?ve been able to use my company mail): my account name is FabioDiBenedetto add me please Fabio Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 10 luglio 2015 15:10 A: fiware-robotics at lists.fi-ware.org Cc: Chulani, Ilknur (ilknur.chulani at atos.net) Oggetto: [Fiware-robotics] Community account for Robotics live demo Priorit?: Alta Dear All, We?ve got a community account for the live demo implementation! I?m going to add to it all the users who will work on it. The owner of the account is myself, however the Organization is named ?Robotics-live-demo cloud?. Please send me your account name in FIWARE Lab so that I can add them to the organization and let you access it. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From luis.lopez at urjc.es Wed Jul 15 12:23:50 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Wed, 15 Jul 2015 12:23:50 +0200 Subject: [Fiware-robotics] Robotics in FIWARE-LAB: public IP addresses In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642A82968@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F642A82968@telmba003ba020.telecomitalia.local> Message-ID: <4302951C-5D3A-419D-A1E0-148486243B9A@urjc.es> Kurento Media Server does not require a public IP address if you configure a STUN server for it. However, the Kurento Application server needs to be reachable from the external world (i.e. needs to accept HTTP requests coming from browsers). You can use the same IP for this application server and for the wirecloud one, but this may generate XSS problems and the browser, you'll need to check and to architect appropriately the applications for avoiding them. Best regards. El 14/07/2015, a las 12:26, Bollano Gianmario escribi?: > Dear Alvaro and others, > we have successfully asked for the creation of an account for the Robotics Live Demo. > We are now facing a major issue: it seems we can only have one public IP address. > > We would like to ask you an important question: using Wirecloud instance in FIWARE, can Widgets access to VMs hosted in FIWARE-LAB (through piping) using their private addresses? > Or do we need a public IP address for each VM? > > For instance, we?ll have one VM for Kurento, one VM for ContextBroker, one VM for Robotics, and widgets will access each of them: can we do this using their private IP addresses if we?ll only have one public IP address for all Robotics environment? > > Gianmario > > > ------------------------------------------------------------------------------------ > Telecom Italia > Gianmario Bollano > Innovation - Mobile Devices & Sim Applications > Via Reiss Romoli, n? 274 > Cap 10151 Torino > Phone 011 228 7103 > Cell Phone 3316015048 > > 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aarranz at fi.upm.es Wed Jul 15 14:43:46 2015 From: aarranz at fi.upm.es (=?UTF-8?Q?=C3=81lvaro_Arranz?=) Date: Wed, 15 Jul 2015 14:43:46 +0200 Subject: [Fiware-robotics] Robotics in FIWARE-LAB: public IP addresses In-Reply-To: <4302951C-5D3A-419D-A1E0-148486243B9A@urjc.es> References: <7E649CBD84A947498203DAF8F098B1F642A82968@telmba003ba020.telecomitalia.local> <4302951C-5D3A-419D-A1E0-148486243B9A@urjc.es> Message-ID: Hi Gianmario, the Wirecloud instance on FIWARE Lab is hosted by Red.es, so it cannot use, directly, the internal IPs provided in FIWARE Lab. However, we can deploy a VPN service if required, what region of FIWARE Lab are you using? Cross domain is not a problem for Wirecloud (as it provides a proxy), the only thing that cannot go through the proxy are the connections to the websockets created by the Kurento Application, but in that case is very easy to use the access control headers. Here we can have a problem if we are going to use the Mashup portal of FIWARE Lab, as it is running over HTTPS, so the ideal is to also use certificates on the websockets created by the Kurento Applicaition to avoid some security alerts from the browser. I think is feasible to ask for certificates and for domain names for the services we are going to make public for the demo... Anyway, this is not going to be a serious problem, as the demo can work without those domain names and certificates (the drawback is that the user will have to accept connecting with the kurento application server). Best regards, ?lvaro On 15 July 2015 at 12:23, Luis L?pez Fern?ndez wrote: > Kurento Media Server does not require a public IP address if you configure > a STUN server for it. > > However, the Kurento Application server needs to be reachable from the > external world (i.e. needs to accept HTTP requests coming from browsers). > You can use the same IP for this application server and for the wirecloud > one, but this may generate XSS problems and the browser, you'll need to > check and to architect appropriately the applications for avoiding them. > > Best regards. > > El 14/07/2015, a las 12:26, Bollano Gianmario < > gianmario.bollano at telecomitalia.it> escribi?: > > Dear Alvaro and others, > we have successfully asked for the creation of an account for the Robotics > Live Demo. > We are now facing a major issue: it seems we can only have one public IP > address. > > We would like to ask you an important question: using Wirecloud instance > in FIWARE, can Widgets access to VMs hosted in FIWARE-LAB (through piping) > using their private addresses? > Or do we need a public IP address for each VM? > > For instance, we?ll have one VM for Kurento, one VM for ContextBroker, > one VM for Robotics, and widgets will access each of them: can we do this > using their private IP addresses if we?ll only have one public IP address > for all Robotics environment? > > Gianmario > > > > ------------------------------------------------------------------------------------ > > *Telecom Italia*Gianmario Bollano > Innovation - Mobile Devices & Sim Applications > Via Reiss Romoli, n? 274 > Cap 10151 Torino > Phone 011 228 7103 > Cell Phone 3316015048 > > 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.* > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Wed Jul 15 16:08:15 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 15 Jul 2015 14:08:15 +0000 Subject: [Fiware-robotics] R: Robotics in FIWARE-LAB: public IP addresses In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F642A82968@telmba003ba020.telecomitalia.local> <4302951C-5D3A-419D-A1E0-148486243B9A@urjc.es> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A83253@telmba003ba020.telecomitalia.local> Thank you, Alvaro and Luis, your technical skills and the information you are providing us will be very helpful to understand which constraints and capabilities we need to negotiate for the setup of the Robotics-live-demo environment in FIWARE-LAB . We are using the node in Trento for FIWARE-Lab and have available a Robotics-live-demo project. Sadly, we have one Public IP address; we can maybe ask for a second one but hardly for a third one. I try to summarize your points below : 1) Wirecloud and FIWARE-LAB VMs must communicate through public addresses because are on different domains. 2) A VPN could solve the issue of communication Wirecloud FIWARE-LAB 3) Cross Domain for Wirecloud is solved thanks to a internal Proxy; 4) Wirecloud proxy cannot be used for Kurento websockets but in that case (and we use Mashup in FIWARE LAB) we can use certificates, or ask the user to accept manually connection to kurento 5) Kurento may work on a private address but a STUN server is required. These are a lot of important technical issues? I try to summarize some possible solutions (that we can discuss with someone at FIWARE-LAB in Trento). Please tell me if some of them are wrong or if you see others: Solution A): 3 Public IP addr. ====================== We use three Public IP addresses, one for Kurento VM, one for Robotics VM, one for Orion VM. Wirecloud must access all three of them. Robots must access Kurento and Robotics. Solution B): 2 Public IP addr. Needs PAT or Proxy. ====================================== In this compact case we could have one Public IP addr for Robotics+Orion on the same private subnet (and a router in it, but if we don?t have a VPN we also need a PAT function or proxy), another Public IP addr one is however required for Kurento. Solution C): 2 Public IP addr? Needs VPN. =========================== If we deploy a VPN we can avoid one Public IP. Also, the Robots already us a VPN to connect to Robotics, than the VPN might be on that VMs. Orion VM and especially Kurento VM will still need a public IP Addr. Orion and Robotics could be on the same Subnet (and one public IP addr), in that case Wirecloud communicate to Orion from the public IP? Solution D): 1 public IP addr? Needs STUN Server+PAT (+VPN?) ================================================ We can deploy a STUN server (and a NAT/PAT too?) to avoid using a public IP for Kurento, but we might need solutions to make Wirecloud working. Orion and Robotics can be reached thanks to a PAT/PROXY (or a VPN for Robotics and PAT for Orion and Kurento?) Here I see of solution with a mix of VPN/PAT/PROXY/STUN? Are these solution correct? Which of these solution do you think might be the easiest ? Do you see other solutions? Gianmario Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: mercoled? 15 luglio 2015 14:44 A: Luis L?pez Fern?ndez Cc: Bollano Gianmario; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: Re: Robotics in FIWARE-LAB: public IP addresses Hi Gianmario, the Wirecloud instance on FIWARE Lab is hosted by Red.es, so it cannot use, directly, the internal IPs provided in FIWARE Lab. However, we can deploy a VPN service if required, what region of FIWARE Lab are you using? Cross domain is not a problem for Wirecloud (as it provides a proxy), the only thing that cannot go through the proxy are the connections to the websockets created by the Kurento Application, but in that case is very easy to use the access control headers. Here we can have a problem if we are going to use the Mashup portal of FIWARE Lab, as it is running over HTTPS, so the ideal is to also use certificates on the websockets created by the Kurento Applicaition to avoid some security alerts from the browser. I think is feasible to ask for certificates and for domain names for the services we are going to make public for the demo... Anyway, this is not going to be a serious problem, as the demo can work without those domain names and certificates (the drawback is that the user will have to accept connecting with the kurento application server). Best regards, ?lvaro On 15 July 2015 at 12:23, Luis L?pez Fern?ndez > wrote: Kurento Media Server does not require a public IP address if you configure a STUN server for it. However, the Kurento Application server needs to be reachable from the external world (i.e. needs to accept HTTP requests coming from browsers). You can use the same IP for this application server and for the wirecloud one, but this may generate XSS problems and the browser, you'll need to check and to architect appropriately the applications for avoiding them. Best regards. El 14/07/2015, a las 12:26, Bollano Gianmario > escribi?: Dear Alvaro and others, we have successfully asked for the creation of an account for the Robotics Live Demo. We are now facing a major issue: it seems we can only have one public IP address. We would like to ask you an important question: using Wirecloud instance in FIWARE, can Widgets access to VMs hosted in FIWARE-LAB (through piping) using their private addresses? Or do we need a public IP address for each VM? For instance, we?ll have one VM for Kurento, one VM for ContextBroker, one VM for Robotics, and widgets will access each of them: can we do this using their private IP addresses if we?ll only have one public IP address for all Robotics environment? Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Jul 15 17:01:56 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 15 Jul 2015 15:01:56 +0000 Subject: [Fiware-robotics] R: R: Community account for Robotics live demo In-Reply-To: References: <8f92780fec8944daa1fc8e01e6909109@EXCHMBX2.consoft.it> Message-ID: Hi Pepe, Done! BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: mercoled? 15 luglio 2015 16:36 Cc: fiware-robotics at lists.fi-ware.org; "Chulani, Ilknur (ilknur.chulani at atos.net)" Oggetto: Re: [Fiware-robotics] R: Community account for Robotics live demo Hi all, Pier, could you add the user "Ikergune A.I.E." (firos at ikergune.com) to the community. Thank you very much, Pepe. On 13/07/15 15:00, Garino Pierangelo wrote: Hi Fbio, I have added you as a member of the Organization. You should have access to it. In case you have troubles please let me know. BR Pier Da: fabio.dibenedetto at consoft.it [mailto:fabio.dibenedetto at consoft.it] Inviato: luned? 13 luglio 2015 14:51 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Cc: Chulani, Ilknur (ilknur.chulani at atos.net) Oggetto: R: Community account for Robotics live demo I had an account, but it doesn't let me access it so I have just created a new one (this time I've been able to use my company mail): my account name is FabioDiBenedetto add me please Fabio Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 10 luglio 2015 15:10 A: fiware-robotics at lists.fi-ware.org Cc: Chulani, Ilknur (ilknur.chulani at atos.net) Oggetto: [Fiware-robotics] Community account for Robotics live demo Priorit?: Alta Dear All, We've got a community account for the live demo implementation! I'm going to add to it all the users who will work on it. The owner of the account is myself, however the Organization is named 'Robotics-live-demo cloud'. Please send me your account name in FIWARE Lab so that I can add them to the organization and let you access it. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Jul 15 17:09:27 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 15 Jul 2015 15:09:27 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> Message-ID: Hi Alvaro, Thanks for your answers. Besides the testing widget topic ;-) I believe your proposal about the dashboard sounds really good, maybe the other people in the team can send you further feedback. So let?s see it in the mockup as soon as it is available! BR Pier Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: mercoled? 15 luglio 2015 14:44 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fiware-robotics at lists.fi-ware.org; fdelavega at fi.upm.es; Luis L?pez Fern?ndez; Angel Hernandez Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, On 7 July 2015 at 16:56, Garino Pierangelo > wrote: Dear Alvaro, I have some questions about the widgets and the robotics demo, after the call we had last week, your feedback will surely help me clarifying the related issues. - Is the ?Joystick? widget in the pictures above composed of the joystick itself, i.e. is the ?Spy wiring? a second widget? The spy wiring widgets is a testing widget ;-). It's not going to be part of the demo :-). - When you propose to put together the camera view, the joystick and the robot buttons, do you mean to have the three of them in the same widget (see first picture below), or are they separate widgets superimposed? In the latter case, I believe that a better layout would be having them separate as layout (see second picture below). First picture: [cid:image001.png at 01D0BF21.001E0DE0] Second picture: [cid:image002.png at 01D0BF21.001E0DE0] I was thinking about providing a mockup version of the dashboard, but finally I din't find time. I will try to provide it next week from Mexico (jointly with the document about the interactions user/dashboard/cb). They are going to be separated widgets, although the can be placed overlapped, we can configure them as you wish, it's not a problem. Anyway, My idea is to provide a widget with the list of the robots (and probably an icon with the status of the robot: still, moving, ...) as I think that the idea to promote is that you can have N robots (in the first phase we have 2 real robots) and not two buttons. This list widget will connect to the context broker though a subscription, so if a robot is registered or remove this list will be updated (as well as the status icons of the robots). Regarding the joystick widget, my idea is to hide it until the user clicks on a "Take control" button. This button is the one I was thinking about to place inside the camera widget (and probably also in the robot list widget). Also, this button should be updated taking into account if the current user is anonymous (proposal | label: "Take control", label on hover: "Sign-up"), if the robot is already controlled by another user (proposal: button disabled, label: "Busy", tooltip: "Controlled by " ), and if currently the user is controlling the robot (proposal: label: "Release control"). If the user clicks the "Take control" button, the widget will try to get the lock over the robot and will show the joystick (I think that in this case the widget will be floating over the other widgets, but the user will be able to move it). If the user clicks on the "Release control" or closes the joystick widget, the dashboard will release the lock over the robot and will show again the "Take control" button. What do you think? Thanks in advance for your feedback. 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: image001.png Type: image/png Size: 161806 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 158123 bytes Desc: image002.png 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 aarranz at fi.upm.es Wed Jul 15 14:43:30 2015 From: aarranz at fi.upm.es (=?UTF-8?Q?=C3=81lvaro_Arranz?=) Date: Wed, 15 Jul 2015 14:43:30 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> Message-ID: Hi Pier, On 7 July 2015 at 16:56, Garino Pierangelo < pierangelo.garino at telecomitalia.it> wrote: > Dear Alvaro, > > > > I have some questions about the widgets and the robotics demo, after the > call we had last week, your feedback will surely help me clarifying the > related issues. > > > > - Is the ?Joystick? widget in the pictures above composed of the > joystick itself, i.e. is the ?Spy wiring? a second widget? > > The spy wiring widgets is a testing widget ;-). It's not going to be part of the demo :-). > - When you propose to put together the camera view, the joystick > and the robot buttons, do you mean to have the three of them in the same > widget (see first picture below), or are they separate widgets > superimposed? In the latter case, I believe that a better layout would be > having them separate as layout (see second picture below). > > > > First picture: > > > > Second picture: > > > I was thinking about providing a mockup version of the dashboard, but finally I din't find time. I will try to provide it next week from Mexico (jointly with the document about the interactions user/dashboard/cb). They are going to be separated widgets, although the can be placed overlapped, we can configure them as you wish, it's not a problem. Anyway, My idea is to provide a widget with the list of the robots (and probably an icon with the status of the robot: still, moving, ...) as I think that the idea to promote is that you can have N robots (in the first phase we have 2 real robots) and not two buttons. This list widget will connect to the context broker though a subscription, so if a robot is registered or remove this list will be updated (as well as the status icons of the robots). Regarding the joystick widget, my idea is to hide it until the user clicks on a "Take control" button. This button is the one I was thinking about to place inside the camera widget (and probably also in the robot list widget). Also, this button should be updated taking into account if the current user is anonymous (proposal | label: "Take control", label on hover: "Sign-up"), if the robot is already controlled by another user (proposal: button disabled, label: "Busy", tooltip: "Controlled by " ), and if currently the user is controlling the robot (proposal: label: "Release control"). If the user clicks the "Take control" button, the widget will try to get the lock over the robot and will show the joystick (I think that in this case the widget will be floating over the other widgets, but the user will be able to move it). If the user clicks on the "Release control" or closes the joystick widget, the dashboard will release the lock over the robot and will show again the "Take control" button. What do you think? > Thanks in advance for your feedback. > > > > BR > > Pier > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 158123 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 161806 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 68500 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image012.png Type: image/png Size: 85361 bytes Desc: not available URL: From gianmario.bollano at telecomitalia.it Thu Jul 16 12:25:08 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 16 Jul 2015 10:25:08 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A78511@telmba003ba020.telecomitalia.local> <2D5E8F00-21F4-4CEE-8756-FECED213BFA6@urjc.es> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A83B85@telmba003ba020.telecomitalia.local> Hi Alvaro, thank you for your description and proposal for the widget. I agree with your suggestions. Let me try to summarize your suggestions in a table. I also made some proposals (blue text). Phase Robot List Camera Box Robot Button Button Tooltip or Text box Joystick Start Display All Robots in plain text. Optionally, at start the first Robot is selected, thus this state is the same as next row. Use colour too (Robot status, same as button)? Empty Hidden Hidden Hidden User click a Robot in the list (not yet controlled) The Robot name text becomes bold (means: Video selected). Use colour too (Robot status, same as button)? Show Video from selected Robot Visible, with text "Take Control" and set a color meaning "Robot Available". Show "Not controlled" Hidden User click the Robot button to control it Robot name is still Bold. Use colour too (Robot status, same as button)? Show Video from selected Robot Visible, redirect to a login (if needed) then text change to "Release Control". Colour change meaning "Robot Controlled". Show "Controlled by " Visible User click the Robot button to release it Robot name is still Bold. Use colour too (Robot status, same as button)? Show Video from selected Robot Visible, text change again to "Take Control" and a color change to mean "Robot Available". Show "Not controlled" Hidden User click on another element in the list The selected Robot name text becomes bold (means: Video selected), the previously selected name become plain. Use colour too (Robot status, same as button)? Show Video from newly selected Robot Visible, text and colour depends on current Robot status. Show text depending on robot status Hidden ROBOT LIST and BUTTON COLOUR (Robot Status): Having clickable list or buttons is a choice of interface design but I like the idea of a list to better explain that robots can be N, not just two. My proposal is to apply (optionally) the colour meaning the Robot Status to the elements in the Robot List. This would allow a user to see the status of all robots at a glance, before clicking on them. KURENTO / VIDEO DISPLAY: In this setting, the action of clicking a list also activates the video from that robot and display the robot Button. This avoid having two (or more) camera widgets, and it?s good for me. I guess the simplest solution is having always streams enabled from the two robots, and simply switching between them on the one to display. This implies more traffic from Kurento Media Server (always receiving two streams) but seems more practical for the demo. Another solution might be having only one Robot controlled and transmitting a video at the same time, but I do not like such setting because it will not show the main capability of the platform, e.g. to manage and control multiple robots simultaneously. Moreover, in that case we need to change the video transmission endpoint every time we change the robot controlled. Other solutions, for instance controlling two robots but having only one video at any time, seem even more complex? Please let us know if these proposals are fine for you, if you have different insight or if you need further information from the team. Thank you in advance, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di ?lvaro Arranz Inviato: mercoled? 15 luglio 2015 14:44 A: Garino Pierangelo Cc: amagan at conwet.com; fiware-robotics at lists.fi-ware.org; Javier Soriano; Luis L?pez Fern?ndez; fdelavega at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, On 7 July 2015 at 16:56, Garino Pierangelo > wrote: Dear Alvaro, I have some questions about the widgets and the robotics demo, after the call we had last week, your feedback will surely help me clarifying the related issues. - Is the ?Joystick? widget in the pictures above composed of the joystick itself, i.e. is the ?Spy wiring? a second widget? The spy wiring widgets is a testing widget ;-). It's not going to be part of the demo :-). - When you propose to put together the camera view, the joystick and the robot buttons, do you mean to have the three of them in the same widget (see first picture below), or are they separate widgets superimposed? In the latter case, I believe that a better layout would be having them separate as layout (see second picture below). First picture: [cid:image001.png at 01D0BFB6.79DD3E40] Second picture: [cid:image002.png at 01D0BFB6.79DD3E40] I was thinking about providing a mockup version of the dashboard, but finally I din't find time. I will try to provide it next week from Mexico (jointly with the document about the interactions user/dashboard/cb). They are going to be separated widgets, although the can be placed overlapped, we can configure them as you wish, it's not a problem. Anyway, My idea is to provide a widget with the list of the robots (and probably an icon with the status of the robot: still, moving, ...) as I think that the idea to promote is that you can have N robots (in the first phase we have 2 real robots) and not two buttons. This list widget will connect to the context broker though a subscription, so if a robot is registered or remove this list will be updated (as well as the status icons of the robots). Regarding the joystick widget, my idea is to hide it until the user clicks on a "Take control" button. This button is the one I was thinking about to place inside the camera widget (and probably also in the robot list widget). Also, this button should be updated taking into account if the current user is anonymous (proposal | label: "Take control", label on hover: "Sign-up"), if the robot is already controlled by another user (proposal: button disabled, label: "Busy", tooltip: "Controlled by " ), and if currently the user is controlling the robot (proposal: label: "Release control"). If the user clicks the "Take control" button, the widget will try to get the lock over the robot and will show the joystick (I think that in this case the widget will be floating over the other widgets, but the user will be able to move it). If the user clicks on the "Release control" or closes the joystick widget, the dashboard will release the lock over the robot and will show again the "Take control" button. What do you think? Thanks in advance for your feedback. 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: image001.png Type: image/png Size: 161806 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 158123 bytes Desc: image002.png 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 pierangelo.garino at telecomitalia.it Tue Jul 21 09:57:00 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 21 Jul 2015 07:57:00 +0000 Subject: [Fiware-robotics] Robotics GE draft slides Message-ID: Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE I2ND - RoboticsGE-v1.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 1846991 bytes Desc: FIWARE I2ND - RoboticsGE-v1.pptx 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 Tue Jul 21 11:08:49 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Tue, 21 Jul 2015 11:08:49 +0200 Subject: [Fiware-robotics] Robotics GE draft slides In-Reply-To: References: Message-ID: De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 9:57 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01D0C3A5.9EC67210]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: -------------- next part -------------- A non-text attachment was scrubbed... Name: photo_2015-07-21_11-07-30.jpg Type: image/jpeg Size: 77914 bytes Desc: photo_2015-07-21_11-07-30.jpg URL: From pierangelo.garino at telecomitalia.it Tue Jul 21 11:21:27 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 21 Jul 2015 09:21:27 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides Message-ID: Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE I2ND - RoboticsGE-v2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 1850641 bytes Desc: FIWARE I2ND - RoboticsGE-v2.pptx 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 pierangelo.garino at telecomitalia.it Tue Jul 21 16:01:02 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 21 Jul 2015 14:01:02 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides Message-ID: Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE I2ND - RoboticsGE-v3.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 1850095 bytes Desc: FIWARE I2ND - RoboticsGE-v3.pptx 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 Wed Jul 22 12:45:12 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Wed, 22 Jul 2015 12:45:12 +0200 Subject: [Fiware-robotics] Robotics GE draft slides In-Reply-To: References: Message-ID: Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01D0C47B.7682F5E0]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 pierangelo.garino at telecomitalia.it Thu Jul 23 15:51:32 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 23 Jul 2015 13:51:32 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: References: Message-ID: HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE I2ND - RoboticsGE-v4.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 348607 bytes Desc: FIWARE I2ND - RoboticsGE-v4.pptx URL: From gianmario.bollano at telecomitalia.it Thu Jul 23 16:08:51 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 23 Jul 2015 14:08:51 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: References: Message-ID: <7E649CBD84A947498203DAF8F098B1F642A87908@telmba003ba020.telecomitalia.local> Pier, for the purpose of these slides - prove usefulness of Robotics in a straight way - I think these new changes are much more effective. I approve all of them; about comments, nothing to say: editing is fine for me because we need few words, and clear meaning. We do not need too many technical issues, because they would defeat the purpose... It might be also a good idea to have backup slides with initiatives, to link slide 3 to real "entities". Just one note: replace "GE-name" in the title of slide 3... Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From davide.colombatto at telecomitalia.it Thu Jul 23 16:12:05 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 23 Jul 2015 14:12:05 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: References: Message-ID: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> Hi, Only some points on slide2 from my side: > Programmable usage and distribution of algorithms between robots & platform (Service Logics) > Ok if "distribution" is to be intended as "the ability to start algorithms in a distributed way" and not as "the ability to deploy/install algorithms in a distributed way". I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots > Automatic management of events through programmable Service Spaces for multiple robots > Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Thu Jul 23 16:19:11 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 23 Jul 2015 14:19:11 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> Davide, so the first is assertion is OK; about the second, why "different" robots? i.e. can't we have also many equal robots (many robots of the same type)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: gioved? 23 luglio 2015 16:12 A: Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides Hi, Only some points on slide2 from my side: > Programmable usage and distribution of algorithms between robots & platform (Service Logics) > Ok if "distribution" is to be intended as "the ability to start algorithms in a distributed way" and not as "the ability to deploy/install algorithms in a distributed way". I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots > Automatic management of events through programmable Service Spaces for multiple robots > Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From davide.colombatto at telecomitalia.it Thu Jul 23 16:42:16 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 23 Jul 2015 14:42:16 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD354280F842A@TELMBB006RM001.telecomitalia.local> Hi, "different" is only to clarify that, using the automatic management of events, for each robot is created a dedicated Service Space. Robots are distinguished by their name (not by their type) and each dedicated Service Space is automatic named as the robot. Thus I confirm that we can have many equal robots (many robots of the same type), obviously all with different names. N.B. the "name" of a robot is that set during the RCM installation on the robot side. Davide Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:19 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Davide, so the first is assertion is OK; about the second, why "different" robots? i.e. can't we have also many equal robots (many robots of the same type)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: gioved? 23 luglio 2015 16:12 A: Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides Hi, Only some points on slide2 from my side: > Programmable usage and distribution of algorithms between robots & platform (Service Logics) > Ok if "distribution" is to be intended as "the ability to start algorithms in a distributed way" and not as "the ability to deploy/install algorithms in a distributed way". I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots > Automatic management of events through programmable Service Spaces for multiple robots > Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Thu Jul 23 16:46:55 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 23 Jul 2015 14:46:55 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: <069906BED271EB4A883BD9578DCDD354280F842A@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F842A@TELMBB006RM001.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A87991@telmba003ba020.telecomitalia.local> Hi Davide, then shouldn't be better to leave "multiple" (implying also equal type) or "any set of" or instead of "different" Robots? Gianmario Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:42 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, "different" is only to clarify that, using the automatic management of events, for each robot is created a dedicated Service Space. Robots are distinguished by their name (not by their type) and each dedicated Service Space is automatic named as the robot. Thus I confirm that we can have many equal robots (many robots of the same type), obviously all with different names. N.B. the "name" of a robot is that set during the RCM installation on the robot side. Davide Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:19 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Davide, so the first is assertion is OK; about the second, why "different" robots? i.e. can't we have also many equal robots (many robots of the same type)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: gioved? 23 luglio 2015 16:12 A: Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides Hi, Only some points on slide2 from my side: > Programmable usage and distribution of algorithms between robots & platform (Service Logics) > Ok if "distribution" is to be intended as "the ability to start algorithms in a distributed way" and not as "the ability to deploy/install algorithms in a distributed way". I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots > Automatic management of events through programmable Service Spaces for multiple robots > Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From davide.colombatto at telecomitalia.it Thu Jul 23 16:56:26 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 23 Jul 2015 14:56:26 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642A87991@telmba003ba020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F842A@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A87991@telmba003ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD354280F8497@TELMBB006RM001.telecomitalia.local> Hi, I don't know, the important thing is that passes the message that, using automatic management of events, for each connected robot is automatically created a specific Service Space which is totally dedicated to that specific robot (in fact the robot, the Service Space and the related CB-entity will have the same name). D Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:47 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi Davide, then shouldn't be better to leave "multiple" (implying also equal type) or "any set of" or instead of "different" Robots? Gianmario Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:42 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, "different" is only to clarify that, using the automatic management of events, for each robot is created a dedicated Service Space. Robots are distinguished by their name (not by their type) and each dedicated Service Space is automatic named as the robot. Thus I confirm that we can have many equal robots (many robots of the same type), obviously all with different names. N.B. the "name" of a robot is that set during the RCM installation on the robot side. Davide Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:19 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Davide, so the first is assertion is OK; about the second, why "different" robots? i.e. can't we have also many equal robots (many robots of the same type)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: gioved? 23 luglio 2015 16:12 A: Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides Hi, Only some points on slide2 from my side: > Programmable usage and distribution of algorithms between robots & platform (Service Logics) > Ok if "distribution" is to be intended as "the ability to start algorithms in a distributed way" and not as "the ability to deploy/install algorithms in a distributed way". I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots > Automatic management of events through programmable Service Spaces for multiple robots > Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Thu Jul 23 17:20:08 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 23 Jul 2015 15:20:08 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: <069906BED271EB4A883BD9578DCDD354280F8497@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F842A@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A87991@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F8497@TELMBB006RM001.telecomitalia.local> Message-ID: This bullet point is inside the item 'Platform management of multi-robots', so why don't we simplify it by removing 'multiple robots': > Automatic management of events through dedicated Service Spaces for different robots Pier Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:56 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, I don't know, the important thing is that passes the message that, using automatic management of events, for each connected robot is automatically created a specific Service Space which is totally dedicated to that specific robot (in fact the robot, the Service Space and the related CB-entity will have the same name). D Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:47 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi Davide, then shouldn't be better to leave "multiple" (implying also equal type) or "any set of" or instead of "different" Robots? Gianmario Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:42 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, "different" is only to clarify that, using the automatic management of events, for each robot is created a dedicated Service Space. Robots are distinguished by their name (not by their type) and each dedicated Service Space is automatic named as the robot. Thus I confirm that we can have many equal robots (many robots of the same type), obviously all with different names. N.B. the "name" of a robot is that set during the RCM installation on the robot side. Davide Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:19 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Davide, so the first is assertion is OK; about the second, why "different" robots? i.e. can't we have also many equal robots (many robots of the same type)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: gioved? 23 luglio 2015 16:12 A: Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides Hi, Only some points on slide2 from my side: > Programmable usage and distribution of algorithms between robots & platform (Service Logics) > Ok if "distribution" is to be intended as "the ability to start algorithms in a distributed way" and not as "the ability to deploy/install algorithms in a distributed way". I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots > Automatic management of events through programmable Service Spaces for multiple robots > Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don't we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any...) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don't think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That's why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the 'First published code in June 2015': what does it refer to? We don't have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later...). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we'll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From davide.colombatto at telecomitalia.it Thu Jul 23 17:40:55 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 23 Jul 2015 15:40:55 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: References: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F842A@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A87991@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F8497@TELMBB006RM001.telecomitalia.local>, Message-ID: <000f426f.0c862dbb52f0512d@telecomitalia.it> Ok for me. If you consider appropriate we could also add "Robot clone" to specify that the Service Space dedicated to a Robot is its "abstraction" in the ROS world (in the same way the CB entity dedicated to a Robot is its abstraction in the IoT world): Automatic management of events through dedicated Service Spaces (Robot clones) Davide ------ Messaggio originale------ Da: Garino Pierangelo Data: gio, 23 lug 2015 17:20 A: Colombatto Davide;Bollano Gianmario;Angel Hernandez;fiware-robotics at lists.fi-ware.org; Oggetto:R: Robotics GE draft slides This bullet point is inside the item ?Platform management of multi-robots?, so why don?t we simplify it by removing ?multiple robots?: ? Automatic management of events through dedicated Service Spaces for different robots Pier Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:56 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, I don?t know, the important thing is that passes the message that, using automatic management of events, for each connected robot is automatically created a specific Service Space which is totally dedicated to that specific robot (in fact the robot, the Service Space and the related CB-entity will have the same name). D Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:47 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi Davide, then shouldn?t be better to leave ?multiple? (implying also equal type) or ?any set of? or instead of ?different? Robots? Gianmario Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:42 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, ?different? is only to clarify that, using the automatic management of events, for each robot is created a dedicated Service Space. Robots are distinguished by their name (not by their type) and each dedicated Service Space is automatic named as the robot. Thus I confirm that we can have many equal robots (many robots of the same type), obviously all with different names. N.B. the ?name? of a robot is that set during the RCM installation on the robot side. Davide Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:19 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Davide, so the first is assertion is OK; about the second, why ?different? robots? i.e. can?t we have also many equal robots (many robots of the same type)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: gioved? 23 luglio 2015 16:12 A: Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides Hi, Only some points on slide2 from my side: ? Programmable usage and distribution of algorithms between robots & platform (Service Logics) ? Ok if ?distribution? is to be intended as ?the ability to start algorithms in a distributed way? and not as ?the ability to deploy/install algorithms in a distributed way?. I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots ? Automatic management of events through programmable Service Spaces for multiple robots ? Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don?t we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any?) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don?t think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That?s why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the ?First published code in June 2015?: what does it refer to? We don?t have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later?). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we?ll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Thu Jul 23 18:03:57 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 23 Jul 2015 16:03:57 +0000 Subject: [Fiware-robotics] R: Robotics GE draft slides In-Reply-To: <000f426f.0c862dbb52f0512d@telecomitalia.it> References: <069906BED271EB4A883BD9578DCDD354280F8390@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A8794C@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F842A@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A87991@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280F8497@TELMBB006RM001.telecomitalia.local>, <000f426f.0c862dbb52f0512d@telecomitalia.it> Message-ID: I would avoid that, because we should then clarify why a "Service Space" implies "Robot Clone". It might appear a sort of limitation, because "Service" and "Robot" remains distinct concepts in common understanding. Sent from TypeMail On Jul 23, 2015, at 5:40 PM, Colombatto Davide > wrote: Ok for me. If you consider appropriate we could also add "Robot clone" to specify that the Service Space dedicated to a Robot is its "abstraction" in the ROS world (in the same way the CB entity dedicated to a Robot is its abstraction in the IoT world): Automatic management of events through dedicated Service Spaces (Robot clones) Davide ------ Messaggio originale------ Da: Garino Pierangelo Data: gio, 23 lug 2015 17:20 A: Colombatto Davide;Bollano Gianmario;Angel Hernandez;fiware-robotics at lists.fi-ware.org; Oggetto:R: Robotics GE draft slides This bullet point is inside the item ?Platform management of multi-robots?, so why don?t we simplify it by removing ?multiple robots?: ? Automatic management of events through dedicated Service Spaces for different robots Pier Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:56 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, I don?t know, the important thing is that passes the message that, using automatic management of events, for each connected robot is automatically created a specific Service Space which is totally dedicated to that specific robot (in fact the robot, the Service Space and the related CB-entity will have the same name). D Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:47 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi Davide, then shouldn?t be better to leave ?multiple? (implying also equal type) or ?any set of? or instead of ?different? Robots? Gianmario Da: Colombatto Davide Inviato: gioved? 23 luglio 2015 16:42 A: Bollano Gianmario; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi, ?different? is only to clarify that, using the automatic management of events, for each robot is created a dedicated Service Space. Robots are distinguished by their name (not by their type) and each dedicated Service Space is automatic named as the robot. Thus I confirm that we can have many equal robots (many robots of the same type), obviously all with different names. N.B. the ?name? of a robot is that set during the RCM installation on the robot side. Davide Da: Bollano Gianmario Inviato: gioved? 23 luglio 2015 16:19 A: Colombatto Davide; Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Davide, so the first is assertion is OK; about the second, why ?different? robots? i.e. can?t we have also many equal robots (many robots of the same type)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: gioved? 23 luglio 2015 16:12 A: Garino Pierangelo; Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides Hi, Only some points on slide2 from my side: ? Programmable usage and distribution of algorithms between robots & platform (Service Logics) ? Ok if ?distribution? is to be intended as ?the ability to start algorithms in a distributed way? and not as ?the ability to deploy/install algorithms in a distributed way?. I remind that, for this major release, RCM will not able to install the ROS nodes/launchers but only to start them (i.e. they must be already installed in the machines: platform VMs, Robots), according to the service logics associated to the robots ? Automatic management of events through programmable Service Spaces for multiple robots ? Automatic management of events through dedicated Service Spaces for different robots Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: gioved? 23 luglio 2015 15:52 A: Angel Hernandez; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Robotics GE draft slides HI All, Here is an updated slideset for the Robotic GE, main modified parts are in green. I tried to gather suggestions I got, trying to be more incisive in the descriptions. I have also added a few comments, please have a look and express your opinion. Angel, concerning the point you raised in your mail (GE is core for all partners) I agree this is not only the situation of TI, it was just that I wanted to start placing a bullet point for this, to be updated hence absolutely fine to extend it to all of us (check it in this new version). I have also an additional proposal: whay don?t we put in a separate backup slide a list of current involvements by each group concerning the GE as core in the respective initiatives, i.e. more details on what reported by bullet points within third slide (field trials, experimental results, customer experiences)? This would give more info to those going to have a look at the slides (if any?) without disrupting the three slides scheme. As you might have seen, Manuel reminds us that we need to finalise the slides by today, so please send me your comments updates asap, thanks. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 22 luglio 2015 12:45 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: Robotics GE draft slides Hello Pier, I was refering to the initial publications of the functional code we uploaded on GitHub a while ago, Based on the conversatipon yesterday, I think we should show these kind of activities even without mentioning who has uploaded what or where. We are not gonna show the code or the GitHub, we just say the Robotics team has started uploading code. Also, I don?t think we should focalize on any partner and we should try to make all progress and achievements part of the common group we are. That?s why we are just showing numbers on the third slide, therefore, I think we should rewrite the last sentence you added: The GE is core inside the robotics experimental platform by TI It should be obvious that this development is core for all partners involved, so wither we change it to: The GE is core inside the robotics units of all partners Or we simply remove it, because it shows discordance. Best regards, ?ngel De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 21 de julio de 2015 16:01 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Robotics GE draft slides Hi All, Few more updates to the slide (in violet), please check them. I had a question I forgot to mention this morning: in slide 3 there is the item concerning the ?First published code in June 2015?: what does it refer to? We don?t have yet a public release of the Robotics GE, so in my opinion we should drop it. BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 11:21 A: fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics GE draft slides Hi All, Here are the updated slides after the call we had. Please update them (especially the red items), by using a different color (to ease my integration later?). Thanks and BR Pier Da: Garino Pierangelo Inviato: marted? 21 luglio 2015 09:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Robotics GE draft slides Dear All, You can find attached the draft integrated slides for the Robotics GE, we?ll use them as basis for discussion in the call right now. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Tue Jul 28 09:58:54 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 28 Jul 2015 07:58:54 +0000 Subject: [Fiware-robotics] Robotics call? Message-ID: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> Hi all, I'd skip the weekly Robotics call, if you don't have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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 jjaime at ikergune.com Tue Jul 28 10:08:38 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 28 Jul 2015 10:08:38 +0200 Subject: [Fiware-robotics] Robotics call? References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> Message-ID: Hi all, I'd skip this call too. BR, Pepe On 28/07/15 09:59, Bollano Gianmario wrote: Hi all, I?d skip the weekly Robotics call, if you don?t have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Tue Jul 28 10:19:32 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 28 Jul 2015 08:19:32 +0000 Subject: [Fiware-robotics] R: Robotics call? In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn't manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the "RCM-FIROS Interaction". Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I'd skip the weekly Robotics call, if you don't have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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 gianmario.bollano at telecomitalia.it Tue Jul 28 10:34:22 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 28 Jul 2015 08:34:22 +0000 Subject: [Fiware-robotics] R: Robotics call? In-Reply-To: <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F642A893C2@telmba003ba020.telecomitalia.local> Very well Davide, let me summarize the Action Points: AP0: @All : Complete the retrospectives, Davide will collect them AP1: @ET: Release an updated FIROS (by e-mail or with update on Github) with fixes suggested by Fabio to be compliant with Open Specs draft AP2: @ET: Provide the public IP address for the actual version of Orion-CB and for WebApp currently used to test the updated FIROS AP3: @TI: Test the interaction between RCM and updated FIROS, with the current version of Orion-CB and Webapp Gianmario Da: Colombatto Davide Inviato: marted? 28 luglio 2015 10:20 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Cc: fabio.dibenedetto at consoft.it Oggetto: R: Robotics call? Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn't manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the "RCM-FIROS Interaction". Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I'd skip the weekly Robotics call, if you don't have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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 igonzalez at ikergune.com Tue Jul 28 15:22:34 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Tue, 28 Jul 2015 15:22:34 +0200 Subject: [Fiware-robotics] R: Robotics call? References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A893C2@telmba003ba020.telecomitalia.local> Message-ID: Hi, In relation with the action points that are related to etxetar: AP1: We will work on it, we have to check what Fabio said. AP2: 1. The new version of FIROS is compatible with the new version of the contextborker, but it is also compatible with the old one, so you don't need the ip you are asking for. 2. To test FIROS new version it is not needed any web app, you can post data to the contextbroker (as it was done with the old version) the differene is that before inside each attributes value there was an object which strings were between simple quote and now we use '%27'. For example --> value: {'angular': 'x': 5, 'y': 6}. And now it will be --> value: {%27angular%27: %27x%27: 5, %27y%27: 6} Regards, I?igo On 28/07/15 10:34, Bollano Gianmario wrote: Very well Davide, let me summarize the Action Points: AP0: @All : Complete the retrospectives, Davide will collect them AP1: @ET: Release an updated FIROS (by e-mail or with update on Github) with fixes suggested by Fabio to be compliant with Open Specs draft AP2: @ET: Provide the public IP address for the actual version of Orion-CB and for WebApp currently used to test the updated FIROS AP3: @TI: Test the interaction between RCM and updated FIROS, with the current version of Orion-CB and Webapp Gianmario Da: Colombatto Davide Inviato: marted? 28 luglio 2015 10:20 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Cc: fabio.dibenedetto at consoft.it Oggetto: R: Robotics call? Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn?t manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the ?RCM-FIROS Interaction?. Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I?d skip the weekly Robotics call, if you don?t have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Tue Jul 28 16:45:38 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 28 Jul 2015 14:45:38 +0000 Subject: [Fiware-robotics] R: R: Robotics call? In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A893C2@telmba003ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD354280FB32F@TELMBB006RM001.telecomitalia.local> Hi Inigo, AP2 is related to your response in the attached email. Do you confirm that it is sufficient to replace in the old web-app the simple quotes into '%27' to allow the usage of FIROSv2 with any version of CB (old or new one)? In the attached email you said that you are already using a new version of web-app which uses the new character convention. Is it possible to send us the code of the new version of web-app (in the same way you sent us the old one)? If it is possible, I just remind you to protect the content with a password. Thank you, Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: marted? 28 luglio 2015 15:23 A: Bollano Gianmario; Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics call? Hi, In relation with the action points that are related to etxetar: AP1: We will work on it, we have to check what Fabio said. AP2: 1. The new version of FIROS is compatible with the new version of the contextborker, but it is also compatible with the old one, so you don't need the ip you are asking for. 2. To test FIROS new version it is not needed any web app, you can post data to the contextbroker (as it was done with the old version) the differene is that before inside each attributes value there was an object which strings were between simple quote and now we use '%27'. For example --> value: {'angular': 'x': 5, 'y': 6}. And now it will be --> value: {%27angular%27: %27x%27: 5, %27y%27: 6} Regards, I?igo On 28/07/15 10:34, Bollano Gianmario wrote: Very well Davide, let me summarize the Action Points: AP0: @All : Complete the retrospectives, Davide will collect them AP1: @ET: Release an updated FIROS (by e-mail or with update on Github) with fixes suggested by Fabio to be compliant with Open Specs draft AP2: @ET: Provide the public IP address for the actual version of Orion-CB and for WebApp currently used to test the updated FIROS AP3: @TI: Test the interaction between RCM and updated FIROS, with the current version of Orion-CB and Webapp Gianmario Da: Colombatto Davide Inviato: marted? 28 luglio 2015 10:20 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Cc: fabio.dibenedetto at consoft.it Oggetto: R: Robotics call? Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn't manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the "RCM-FIROS Interaction". Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I'd skip the weekly Robotics call, if you don't have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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 -------------- An embedded message was scrubbed... From: =?Windows-1252?Q?I=F1igo_Gonzalez?= Subject: Re: [Fiware-robotics] R: R: R: Demo Sprint 4.3.3 Date: Thu, 2 Jul 2015 14:14:14 +0000 Size: 63257 URL: From fabio.dibenedetto at consoft.it Tue Jul 28 17:22:15 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 28 Jul 2015 15:22:15 +0000 Subject: [Fiware-robotics] R: R: Robotics call? In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A893C2@telmba003ba020.telecomitalia.local> Message-ID: For what I remember after 3 days of try the last thing I received from firos last version using the old context broker we used was errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) If you say that even this message the context broker received what he had to, I trust you but I haven't seen the robot moving so for my point of view the test failed (and the demo couldn't be done in that way). Anyway soon or later we have to let rcmdriver and firos interact together, so if you can use the version of robotics_msgs I sent you some time ago instead the internal version of msg and service you used could be good also because I followed the specification. Furthermore I did a modification in firos to avoid the use of mandatory namespace you had: would be good if you can use something like that too. Fabio 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: marted? 28 luglio 2015 15:23 A: Bollano Gianmario; Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics call? Hi, In relation with the action points that are related to etxetar: AP1: We will work on it, we have to check what Fabio said. AP2: 1. The new version of FIROS is compatible with the new version of the contextborker, but it is also compatible with the old one, so you don't need the ip you are asking for. 2. To test FIROS new version it is not needed any web app, you can post data to the contextbroker (as it was done with the old version) the differene is that before inside each attributes value there was an object which strings were between simple quote and now we use '%27'. For example --> value: {'angular': 'x': 5, 'y': 6}. And now it will be --> value: {%27angular%27: %27x%27: 5, %27y%27: 6} Regards, I?igo On 28/07/15 10:34, Bollano Gianmario wrote: Very well Davide, let me summarize the Action Points: AP0: @All : Complete the retrospectives, Davide will collect them AP1: @ET: Release an updated FIROS (by e-mail or with update on Github) with fixes suggested by Fabio to be compliant with Open Specs draft AP2: @ET: Provide the public IP address for the actual version of Orion-CB and for WebApp currently used to test the updated FIROS AP3: @TI: Test the interaction between RCM and updated FIROS, with the current version of Orion-CB and Webapp Gianmario Da: Colombatto Davide Inviato: marted? 28 luglio 2015 10:20 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Cc: fabio.dibenedetto at consoft.it Oggetto: R: Robotics call? Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn't manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the "RCM-FIROS Interaction". Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I'd skip the weekly Robotics call, if you don't have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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: From igonzalez at ikergune.com Wed Jul 29 09:17:28 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Wed, 29 Jul 2015 09:17:28 +0200 Subject: [Fiware-robotics] R: R: Robotics call? References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A893C2@telmba003ba020.telecomitalia.local> Message-ID: Hi, I will explain what happens. In firos v1 we sent as an attribute's value the "data encoded in JSON". The reason was that if it was a pure JSON the context broker changes the numeric data to string. So we coded it in json changing the double quotes by simple quote. And FIROS when received that data it replaced the simple quote by double quote and decoded the json string. The new context broker version doesn't allow to add some characters to the value field, and one of them was simple quotes. So we decided to change the replacement character by %27. So now the value from the webapp must be sent with %27 instead of simple quote and as you can see here at line 68 https://github.com/Ikergune/firos/blob/master/scripts/include/constants.py FIROS will search for the SEPARATOR_CHAR (%27) replace it and decode the JSON, as you see in line 122 in https://github.com/Ikergune/firos/blob/master/scripts/include/pubsub/contextbroker/cbSubscriber.py As you were working with the old web-app (sending simple quote) and FIROS v2 (searching fo %27) there was no replacement, so the error you are receiving is right, as there wasn't any %27 there was no replacement to add double quotes, so it returns an error of "no double quotes found". As I said this was to add support for the new context broker, the old one supports simple quotes, %27 and many other things. In fact, when you were using our context broker for the first demo we were working on the integration with the new context broker version, and I also tried it with the old context broker and it worked. The funny thing was that you were also publishing data to that context broker instance, and I could move the robot using my web-app, but I also received Telecom Italia's data and that data returned the error Fabio said (as the separator characters were different.) As Davide said, just changing the simple quote for %27 should be enough. I will send you what I sent you before with the new separation character so you can test it. Also, maybe it will be a good idea that telecom italia open an issue on github for the changes Fabio proposed, so the GE can so more activity in other places in addition the mailing list. About the namespaces, maybe you don't need namespaces to identify a robot, but context broker needs (each robot is an entity, and is mandatory that each entity has a name). So as I said before this is something we will have to discuss later. Regards, I?igo On 28/07/15 17:24, fabio.dibenedetto at consoft.it wrote: For what I remember after 3 days of try the last thing I received from firos last version using the old context broker we used was errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) If you say that even this message the context broker received what he had to, I trust you but I haven?t seen the robot moving so for my point of view the test failed (and the demo couldn?t be done in that way). Anyway soon or later we have to let rcmdriver and firos interact together, so if you can use the version of robotics_msgs I sent you some time ago instead the internal version of msg and service you used could be good also because I followed the specification. Furthermore I did a modification in firos to avoid the use of mandatory namespace you had: would be good if you can use something like that too. Fabio 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: marted? 28 luglio 2015 15:23 A: Bollano Gianmario; Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics call? Hi, In relation with the action points that are related to etxetar: AP1: We will work on it, we have to check what Fabio said. AP2: 1. The new version of FIROS is compatible with the new version of the contextborker, but it is also compatible with the old one, so you don't need the ip you are asking for. 2. To test FIROS new version it is not needed any web app, you can post data to the contextbroker (as it was done with the old version) the differene is that before inside each attributes value there was an object which strings were between simple quote and now we use '%27'. For example --> value: {'angular': 'x': 5, 'y': 6}. And now it will be --> value: {%27angular%27: %27x%27: 5, %27y%27: 6} Regards, I?igo On 28/07/15 10:34, Bollano Gianmario wrote: Very well Davide, let me summarize the Action Points: AP0: @All : Complete the retrospectives, Davide will collect them AP1: @ET: Release an updated FIROS (by e-mail or with update on Github) with fixes suggested by Fabio to be compliant with Open Specs draft AP2: @ET: Provide the public IP address for the actual version of Orion-CB and for WebApp currently used to test the updated FIROS AP3: @TI: Test the interaction between RCM and updated FIROS, with the current version of Orion-CB and Webapp Gianmario Da: Colombatto Davide Inviato: marted? 28 luglio 2015 10:20 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Cc: fabio.dibenedetto at consoft.it Oggetto: R: Robotics call? Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn?t manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the ?RCM-FIROS Interaction?. Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I?d skip the weekly Robotics call, if you don?t have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabio.dibenedetto at consoft.it Wed Jul 29 10:40:28 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Wed, 29 Jul 2015 08:40:28 +0000 Subject: [Fiware-robotics] R: R: R: Robotics call? In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A893C2@telmba003ba020.telecomitalia.local> Message-ID: <662ec6ee7dbb4bbc8d4a798b7eba3435@EXCHMBX2.consoft.it> Thank you for the explanation, dealing with the context broker seems little tricky and I still don't understand the use of %27: doesn't the context broker use json? Anyway for what concern the namespace the problem is that you work on 2 worlds the ros one and the context broker one: you can force ros world use the namespace only because the context broker word need it In the topicHandler I changed this so that turtlebotTI can use the version without namespace if robotName == "turtlebotTI": ROBOT_TOPICS[robotName]["publisher"][topicName]["publisher"] = rospy.Publisher(topicName, theclass, queue_size=DEFAULT_QUEUE_SIZE) else: ROBOT_TOPICS[robotName]["publisher"][topicName]["publisher"] = rospy.Publisher(robotName + "/" + topicName, theclass, queue_size=DEFAULT_QUEUE_SIZE) I think the solution you did is correct if you want run more than one robot in a single roscore because you have to separate each robot context and so use different namespaces but using rcm in our solution means to have this problem already resolved because for every robot creates a different ros context in which work (each robot has its own service space and so ros core to dealing with): in this situation you need namespaces only in the context broker world Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: mercoled? 29 luglio 2015 09:17 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Robotics call? Hi, I will explain what happens. In firos v1 we sent as an attribute's value the "data encoded in JSON". The reason was that if it was a pure JSON the context broker changes the numeric data to string. So we coded it in json changing the double quotes by simple quote. And FIROS when received that data it replaced the simple quote by double quote and decoded the json string. The new context broker version doesn't allow to add some characters to the value field, and one of them was simple quotes. So we decided to change the replacement character by %27. So now the value from the webapp must be sent with %27 instead of simple quote and as you can see here at line 68 https://github.com/Ikergune/firos/blob/master/scripts/include/constants.py FIROS will search for the SEPARATOR_CHAR (%27) replace it and decode the JSON, as you see in line 122 in https://github.com/Ikergune/firos/blob/master/scripts/include/pubsub/contextbroker/cbSubscriber.py As you were working with the old web-app (sending simple quote) and FIROS v2 (searching fo %27) there was no replacement, so the error you are receiving is right, as there wasn't any %27 there was no replacement to add double quotes, so it returns an error of "no double quotes found". As I said this was to add support for the new context broker, the old one supports simple quotes, %27 and many other things. In fact, when you were using our context broker for the first demo we were working on the integration with the new context broker version, and I also tried it with the old context broker and it worked. The funny thing was that you were also publishing data to that context broker instance, and I could move the robot using my web-app, but I also received Telecom Italia's data and that data returned the error Fabio said (as the separator characters were different.) As Davide said, just changing the simple quote for %27 should be enough. I will send you what I sent you before with the new separation character so you can test it. Also, maybe it will be a good idea that telecom italia open an issue on github for the changes Fabio proposed, so the GE can so more activity in other places in addition the mailing list. About the namespaces, maybe you don't need namespaces to identify a robot, but context broker needs (each robot is an entity, and is mandatory that each entity has a name). So as I said before this is something we will have to discuss later. Regards, I?igo On 28/07/15 17:24, fabio.dibenedetto at consoft.it wrote: For what I remember after 3 days of try the last thing I received from firos last version using the old context broker we used was errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) If you say that even this message the context broker received what he had to, I trust you but I haven't seen the robot moving so for my point of view the test failed (and the demo couldn't be done in that way). Anyway soon or later we have to let rcmdriver and firos interact together, so if you can use the version of robotics_msgs I sent you some time ago instead the internal version of msg and service you used could be good also because I followed the specification. Furthermore I did a modification in firos to avoid the use of mandatory namespace you had: would be good if you can use something like that too. Fabio 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: marted? 28 luglio 2015 15:23 A: Bollano Gianmario; Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics call? Hi, In relation with the action points that are related to etxetar: AP1: We will work on it, we have to check what Fabio said. AP2: 1. The new version of FIROS is compatible with the new version of the contextborker, but it is also compatible with the old one, so you don't need the ip you are asking for. 2. To test FIROS new version it is not needed any web app, you can post data to the contextbroker (as it was done with the old version) the differene is that before inside each attributes value there was an object which strings were between simple quote and now we use '%27'. For example --> value: {'angular': 'x': 5, 'y': 6}. And now it will be --> value: {%27angular%27: %27x%27: 5, %27y%27: 6} Regards, I?igo On 28/07/15 10:34, Bollano Gianmario wrote: Very well Davide, let me summarize the Action Points: AP0: @All : Complete the retrospectives, Davide will collect them AP1: @ET: Release an updated FIROS (by e-mail or with update on Github) with fixes suggested by Fabio to be compliant with Open Specs draft AP2: @ET: Provide the public IP address for the actual version of Orion-CB and for WebApp currently used to test the updated FIROS AP3: @TI: Test the interaction between RCM and updated FIROS, with the current version of Orion-CB and Webapp Gianmario Da: Colombatto Davide Inviato: marted? 28 luglio 2015 10:20 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Cc: fabio.dibenedetto at consoft.it Oggetto: R: Robotics call? Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn't manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the "RCM-FIROS Interaction". Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I'd skip the weekly Robotics call, if you don't have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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: From igonzalez at ikergune.com Wed Jul 29 12:47:55 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Wed, 29 Jul 2015 12:47:55 +0200 Subject: [Fiware-robotics] R: R: R: Robotics call? References: <7E649CBD84A947498203DAF8F098B1F642A89342@telmba003ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354280FAFD5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642A893C2@telmba003ba020.telecomitalia.local> <662ec6ee7dbb4bbc8d4a798b7eba3435@EXCHMBX2.consoft.it> Message-ID: Hi again, here you have the testing webapp. The zip password is robot. Regards, I?igo On 29/07/15 10:41, fabio.dibenedetto at consoft.it wrote: Thank you for the explanation, dealing with the context broker seems little tricky and I still don?t understand the use of %27: doesn?t the context broker use json? Anyway for what concern the namespace the problem is that you work on 2 worlds the ros one and the context broker one: you can force ros world use the namespace only because the context broker word need it In the topicHandler I changed this so that turtlebotTI can use the version without namespace if robotName == "turtlebotTI": ROBOT_TOPICS[robotName]["publisher"][topicName]["publisher"] = rospy.Publisher(topicName, theclass, queue_size=DEFAULT_QUEUE_SIZE) else: ROBOT_TOPICS[robotName]["publisher"][topicName]["publisher"] = rospy.Publisher(robotName + "/" + topicName, theclass, queue_size=DEFAULT_QUEUE_SIZE) I think the solution you did is correct if you want run more than one robot in a single roscore because you have to separate each robot context and so use different namespaces but using rcm in our solution means to have this problem already resolved because for every robot creates a different ros context in which work (each robot has its own service space and so ros core to dealing with): in this situation you need namespaces only in the context broker world Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: mercoled? 29 luglio 2015 09:17 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Robotics call? Hi, I will explain what happens. In firos v1 we sent as an attribute's value the "data encoded in JSON". The reason was that if it was a pure JSON the context broker changes the numeric data to string. So we coded it in json changing the double quotes by simple quote. And FIROS when received that data it replaced the simple quote by double quote and decoded the json string. The new context broker version doesn't allow to add some characters to the value field, and one of them was simple quotes. So we decided to change the replacement character by %27. So now the value from the webapp must be sent with %27 instead of simple quote and as you can see here at line 68 https://github.com/Ikergune/firos/blob/master/scripts/include/constants.py FIROS will search for the SEPARATOR_CHAR (%27) replace it and decode the JSON, as you see in line 122 in https://github.com/Ikergune/firos/blob/master/scripts/include/pubsub/contextbroker/cbSubscriber.py As you were working with the old web-app (sending simple quote) and FIROS v2 (searching fo %27) there was no replacement, so the error you are receiving is right, as there wasn't any %27 there was no replacement to add double quotes, so it returns an error of "no double quotes found". As I said this was to add support for the new context broker, the old one supports simple quotes, %27 and many other things. In fact, when you were using our context broker for the first demo we were working on the integration with the new context broker version, and I also tried it with the old context broker and it worked. The funny thing was that you were also publishing data to that context broker instance, and I could move the robot using my web-app, but I also received Telecom Italia's data and that data returned the error Fabio said (as the separator characters were different.) As Davide said, just changing the simple quote for %27 should be enough. I will send you what I sent you before with the new separation character so you can test it. Also, maybe it will be a good idea that telecom italia open an issue on github for the changes Fabio proposed, so the GE can so more activity in other places in addition the mailing list. About the namespaces, maybe you don't need namespaces to identify a robot, but context broker needs (each robot is an entity, and is mandatory that each entity has a name). So as I said before this is something we will have to discuss later. Regards, I?igo On 28/07/15 17:24, fabio.dibenedetto at consoft.it wrote: For what I remember after 3 days of try the last thing I received from firos last version using the old context broker we used was errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) errorExpecting property name enclosed in double quotes: line 1 column 2 (char 1) Expecting property name enclosed in double quotes: line 1 column 2 (char 1) If you say that even this message the context broker received what he had to, I trust you but I haven?t seen the robot moving so for my point of view the test failed (and the demo couldn?t be done in that way). Anyway soon or later we have to let rcmdriver and firos interact together, so if you can use the version of robotics_msgs I sent you some time ago instead the internal version of msg and service you used could be good also because I followed the specification. Furthermore I did a modification in firos to avoid the use of mandatory namespace you had: would be good if you can use something like that too. Fabio 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: marted? 28 luglio 2015 15:23 A: Bollano Gianmario; Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics call? Hi, In relation with the action points that are related to etxetar: AP1: We will work on it, we have to check what Fabio said. AP2: 1. The new version of FIROS is compatible with the new version of the contextborker, but it is also compatible with the old one, so you don't need the ip you are asking for. 2. To test FIROS new version it is not needed any web app, you can post data to the contextbroker (as it was done with the old version) the differene is that before inside each attributes value there was an object which strings were between simple quote and now we use '%27'. For example --> value: {'angular': 'x': 5, 'y': 6}. And now it will be --> value: {%27angular%27: %27x%27: 5, %27y%27: 6} Regards, I?igo On 28/07/15 10:34, Bollano Gianmario wrote: Very well Davide, let me summarize the Action Points: AP0: @All : Complete the retrospectives, Davide will collect them AP1: @ET: Release an updated FIROS (by e-mail or with update on Github) with fixes suggested by Fabio to be compliant with Open Specs draft AP2: @ET: Provide the public IP address for the actual version of Orion-CB and for WebApp currently used to test the updated FIROS AP3: @TI: Test the interaction between RCM and updated FIROS, with the current version of Orion-CB and Webapp Gianmario Da: Colombatto Davide Inviato: marted? 28 luglio 2015 10:20 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Cc: fabio.dibenedetto at consoft.it Oggetto: R: Robotics call? Hi, I agree to skip the Robotics call today. I would simply remind two things: 1. @All: Complete the retrospectives so I will able to collect them 2. @ET: Some time ago Fabio sent you some feedbacks related to FIROSv2 in github (e.g. it was no completely compliant to the OpenSpec draft and maybe it didn?t manage the ROS Service exchange). We are waiting the new version of FIROS compliant with the OpenSpec draft (Fabio also sent you the package containing the correct ROS messages defined) in order to really test the ?RCM-FIROS Interaction?. Nowadays he tested this interaction using a mock ROS node which simulated FIROS interaction within the ROS environment (pub/sub and the service). Moreover, since FIROSv2 is implemented to talk with the new version of Orion-CB (FIROSv1 worked with the old one), we also need the public IP of the Orion-CB and the web-app you are using to test FIROSv2 Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 28 luglio 2015 09:59 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I?d skip the weekly Robotics call, if you don?t have objections or specific issues to discuss. Please, let me know if you want to discuss some specific issue and would prefer to have the Robotics call instead. ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]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: testapp.zip Type: application/zip Size: 125339 bytes Desc: testapp.zip URL: