From ahernandez at ikergune.com Sun Feb 1 20:17:18 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Sun, 1 Feb 2015 20:17:18 +0100 Subject: [Fiware-robotics] Feb 2nd Demo Message-ID: Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Sun Feb 1 20:47:50 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Sun, 1 Feb 2015 19:47:50 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: References: Message-ID: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia? ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 Mon Feb 2 09:21:57 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 2 Feb 2015 08:21:57 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 -------------- An embedded message was scrubbed... From: MANUEL ESCRICHE VICENTE Subject: Re: [Fiware-chapter-leaders] [Fiware-chapter-architects] Review Demo meeting - Monday from 10:30 onwards Date: Fri, 30 Jan 2015 15:33:47 +0000 Size: 92213 URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE_Robotics_Demo_20150202-v1.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 280006 bytes Desc: FIWARE_Robotics_Demo_20150202-v1.pptx URL: From davide.colombatto at telecomitalia.it Mon Feb 2 10:00:11 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Mon, 2 Feb 2015 09:00:11 +0000 Subject: [Fiware-robotics] Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com>, Message-ID: <069906BED271EB4A883BD9578DCDD354023EC5@TELMBB006RM001.telecomitalia.local> Hi Pier, Consider that hangout should support at most 10 connections for videocall (if I understand right from the website) and that the VNC client will be only one (so we have to use only hangout to show tha desktop sharing). I think that the following connections will be reserved: * 1 Pier and Gianmario * 1 Davide, Roberto and Fabio * 2 ET (one is used by the PC with the VNC client) I think there are 6 places remaining for others team. Davide ________________________________ Da: Garino Pierangelo Inviato: luned? 2 febbraio 2015 9.21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we?ll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia? ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Mon Feb 2 10:28:05 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Mon, 2 Feb 2015 10:28:05 +0100 Subject: [Fiware-robotics] Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn't we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn't have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 01D03ED2.EE6CB3E0]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: Etxe-Tar_Horizontal.png Type: image/png Size: 123862 bytes Desc: Etxe-Tar_Horizontal.png URL: From pierangelo.garino at telecomitalia.it Mon Feb 2 10:36:04 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 2 Feb 2015 09:36:04 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft's too. Concerning the two issues you mention, they are Stories so I'll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn't we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn't have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Mon Feb 2 10:46:44 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Mon, 2 Feb 2015 10:46:44 +0100 Subject: [Fiware-robotics] Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: Hey, Join.me is only available for Windows, so if we decide to go for that solution in the end, we will have to do it from another computer. This is not a big deal, so we will have it ready anyway. PS: Here is the Consoft logo... but you better make sure it is still the right one, I cleaned it after taking it from their website long time ago. De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft's too. Concerning the two issues you mention, they are Stories so I'll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn't we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn't have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 01D03ED5.88E43E00]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: consoft.png Type: image/png Size: 86106 bytes Desc: consoft.png URL: From fabio.dibenedetto at consoft.it Mon Feb 2 11:02:57 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Mon, 2 Feb 2015 10:02:57 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: <56964650a6294c52a62ae5b2da328128@EXCHMBX1.consoft.it> Thank you Angel I had already sent the logo, but I made a mistake and sent only to Pier Fabio Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: luned? 2 febbraio 2015 10:47 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Feb 2nd Demo Hey, Join.me is only available for Windows, so if we decide to go for that solution in the end, we will have to do it from another computer. This is not a big deal, so we will have it ready anyway. PS: Here is the Consoft logo... but you better make sure it is still the right one, I cleaned it after taking it from their website long time ago. De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft's too. Concerning the two issues you mention, they are Stories so I'll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn't we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn't have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 Feb 2 11:12:14 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 2 Feb 2015 10:12:14 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: Hi Angel, situation is as follows: - I have a webex setup ready, see link https://telecomitalia-sales.webex.com/mw0401lsp11/mywebex/default.do?service=1&siteurl=telecomitalia-sales-en&nomenu=true&main_url=%2Fmc0901lsp11%2Fe.do%3Fsiteurl%3Dtelecomitalia-sales-en%26AT%3DMI%26EventID%3D368108462%26UID%3D510560027%26Host%3DQUhTSwAAAAIJ0NLryL-wrmOjBdsq7udXrwgHj_mLNsH4I37DotuwORN--qveU5iFQLAg1-9BqW89wv8d7Dodvsqi03gknlWL0%26FrameSet%3D2%26MTID%3Dmc68d15bf4d4463271af67363ed0e8816 o I doubt you can take control of the screen, but please try it (we can phone to sync together) o However I can use it for slide sharing and for making the first part of presentation. Then I would leave the floor to you for the demo run - Hangout: o All email addresses, including yours, are not gmail ones, so they cannot be used!! o If the following item works, I would definitely drop this solutions, as it seems creating confusion - Can you set up a join.me connection on a windows machine and then use a VNC connection to the linux machine running the demo? o That would be the best option in my view, but it depend on if/how you can set it right now My strong suggestion was to take a record of the demo just in case everthing else fails. Could you do it? BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:47 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hey, Join.me is only available for Windows, so if we decide to go for that solution in the end, we will have to do it from another computer. This is not a big deal, so we will have it ready anyway. PS: Here is the Consoft logo... but you better make sure it is still the right one, I cleaned it after taking it from their website long time ago. De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft's too. Concerning the two issues you mention, they are Stories so I'll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn't we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn't have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Mon Feb 2 11:58:08 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Mon, 2 Feb 2015 11:58:08 +0100 Subject: [Fiware-robotics] Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: Guys, we need to get a hold from you ASAP. Davide, can you call I?igo? De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft's too. Concerning the two issues you mention, they are Stories so I'll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn't we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn't have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 01D03EDF.82B05E10]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 Feb 2 13:07:58 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 2 Feb 2015 12:07:58 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: References: <4ijolwf385flbhw9qcciuiie.1422820066357@email.android.com> Message-ID: Thank you all guys for your effort to show the demo! In fact sharing the screen has been the most critical issue to solve. At least we found that this webex connection, although not the best one, is working and is the only one I can set from my side. We'll study more in detail other solutions to have them ready next time. I suggest a wrap-up after the demo, to be done either tomorrow or Thursday morning during the Robotics call @ 10, what's vbest for you? Thanks again and talk to you soon again Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 11:58 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Guys, we need to get a hold from you ASAP. Davide, can you call I?igo? De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft's too. Concerning the two issues you mention, they are Stories so I'll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn't we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn't have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we'll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia(tm) ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Tue Feb 3 08:26:02 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Tue, 3 Feb 2015 08:26:02 +0100 Subject: [Fiware-robotics] Feb 2nd Demo Message-ID: Hi, today sounds good What time? Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:02/02/2015 01:07 PM (GMT+01:00) Para: Angel Hernandez ,Colombatto Davide ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Thank you all guys for your effort to show the demo! In fact sharing the screen has been the most critical issue to solve. At least we found that this webex connection, although not the best one, is working and is the only one I can set from my side. We?ll study more in detail other solutions to have them ready next time. I suggest a wrap-up after the demo, to be done either tomorrow or Thursday morning during the Robotics call @ 10, what?s vbest for you? Thanks again and talk to you soon again Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 11:58 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Guys, we need to get a hold from you ASAP. Davide, can you call I?igo? De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft?s too. Concerning the two issues you mention, they are Stories so I?ll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn?t we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn?t have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we?ll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia? ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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:_com_android_email_attachmentprovider_1_414_RAW at sec.galaxytab]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 Tue Feb 3 09:51:40 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 3 Feb 2015 08:51:40 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: References: Message-ID: <069906BED271EB4A883BD9578DCDD3540247D2@TELMBB006RM001.telecomitalia.local> Hi All, Today afternoon at 15.00 is good for you? Davide Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: marted? 3 febbraio 2015 08:26 A: Garino Pierangelo; Colombatto Davide; I?igo Gonzalez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Antonini Roberto Oggetto: RE: Feb 2nd Demo Hi, today sounds good What time? Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:02/02/2015 01:07 PM (GMT+01:00) Para: Angel Hernandez ,Colombatto Davide ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Thank you all guys for your effort to show the demo! In fact sharing the screen has been the most critical issue to solve. At least we found that this webex connection, although not the best one, is working and is the only one I can set from my side. We?ll study more in detail other solutions to have them ready next time. I suggest a wrap-up after the demo, to be done either tomorrow or Thursday morning during the Robotics call @ 10, what?s vbest for you? Thanks again and talk to you soon again Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 11:58 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Guys, we need to get a hold from you ASAP. Davide, can you call I?igo? De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft?s too. Concerning the two issues you mention, they are Stories so I?ll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn?t we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn?t have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we?ll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia? ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Tue Feb 3 10:20:01 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Tue, 3 Feb 2015 10:20:01 +0100 Subject: [Fiware-robotics] Feb 2nd Demo Message-ID: <0xfle8jqc989x77ps5tkoeyp.1422955182689@email.android.com> Yeap Enviado de Samsung Mobile -------- Mensaje original -------- De: Colombatto Davide Fecha:03/02/2015 09:51 AM (GMT+01:00) Para: Angel Hernandez ,Garino Pierangelo ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Hi All, Today afternoon at 15.00 is good for you? Davide Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: marted? 3 febbraio 2015 08:26 A: Garino Pierangelo; Colombatto Davide; I?igo Gonzalez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Antonini Roberto Oggetto: RE: Feb 2nd Demo Hi, today sounds good What time? Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:02/02/2015 01:07 PM (GMT+01:00) Para: Angel Hernandez ,Colombatto Davide ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Thank you all guys for your effort to show the demo! In fact sharing the screen has been the most critical issue to solve. At least we found that this webex connection, although not the best one, is working and is the only one I can set from my side. We?ll study more in detail other solutions to have them ready next time. I suggest a wrap-up after the demo, to be done either tomorrow or Thursday morning during the Robotics call @ 10, what?s vbest for you? Thanks again and talk to you soon again Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 11:58 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Guys, we need to get a hold from you ASAP. Davide, can you call I?igo? De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft?s too. Concerning the two issues you mention, they are Stories so I?ll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn?t we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn?t have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we?ll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia? ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 01D03F97.01012C10]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 Tue Feb 3 11:10:06 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 3 Feb 2015 10:10:06 +0000 Subject: [Fiware-robotics] R: Feb 2nd Demo In-Reply-To: <0xfle8jqc989x77ps5tkoeyp.1422955182689@email.android.com> References: <0xfle8jqc989x77ps5tkoeyp.1422955182689@email.android.com> Message-ID: <0b6e6960fbd84e75b27fe7a9f5478322@EXCHMBX1.consoft.it> Ok for me too, but on what platform? Phone or hangouts? Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: marted? 3 febbraio 2015 10:20 A: Colombatto Davide; Garino Pierangelo; I?igo Gonzalez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Feb 2nd Demo Yeap Enviado de Samsung Mobile -------- Mensaje original -------- De: Colombatto Davide Fecha:03/02/2015 09:51 AM (GMT+01:00) Para: Angel Hernandez ,Garino Pierangelo ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Hi All, Today afternoon at 15.00 is good for you? Davide Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: marted? 3 febbraio 2015 08:26 A: Garino Pierangelo; Colombatto Davide; I?igo Gonzalez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Antonini Roberto Oggetto: RE: Feb 2nd Demo Hi, today sounds good What time? Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:02/02/2015 01:07 PM (GMT+01:00) Para: Angel Hernandez ,Colombatto Davide ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Thank you all guys for your effort to show the demo! In fact sharing the screen has been the most critical issue to solve. At least we found that this webex connection, although not the best one, is working and is the only one I can set from my side. We?ll study more in detail other solutions to have them ready next time. I suggest a wrap-up after the demo, to be done either tomorrow or Thursday morning during the Robotics call @ 10, what?s vbest for you? Thanks again and talk to you soon again Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 11:58 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Guys, we need to get a hold from you ASAP. Davide, can you call I?igo? De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft?s too. Concerning the two issues you mention, they are Stories so I?ll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn?t we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn?t have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we?ll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia? ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Tue Feb 3 11:38:17 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Tue, 3 Feb 2015 11:38:17 +0100 Subject: [Fiware-robotics] Feb 2nd Demo In-Reply-To: <0b6e6960fbd84e75b27fe7a9f5478322@EXCHMBX1.consoft.it> References: <0xfle8jqc989x77ps5tkoeyp.1422955182689@email.android.com> <0b6e6960fbd84e75b27fe7a9f5478322@EXCHMBX1.consoft.it> Message-ID: Hangouts, please. De: fabio.dibenedetto at consoft.it [mailto:fabio.dibenedetto at consoft.it] Enviado el: martes, 3 de febrero de 2015 11:10 Para: Angel Hernandez; Colombatto Davide; Garino Pierangelo; I?igo Gonzalez; Jose Jaime Ariza CC: fiware-robotics at lists.fi-ware.org Asunto: R: Feb 2nd Demo Ok for me too, but on what platform? Phone or hangouts? Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: marted? 3 febbraio 2015 10:20 A: Colombatto Davide; Garino Pierangelo; I?igo Gonzalez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Feb 2nd Demo Yeap Enviado de Samsung Mobile -------- Mensaje original -------- De: Colombatto Davide Fecha:03/02/2015 09:51 AM (GMT+01:00) Para: Angel Hernandez ,Garino Pierangelo ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Hi All, Today afternoon at 15.00 is good for you? Davide Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: marted? 3 febbraio 2015 08:26 A: Garino Pierangelo; Colombatto Davide; I?igo Gonzalez; Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Antonini Roberto Oggetto: RE: Feb 2nd Demo Hi, today sounds good What time? Enviado de Samsung Mobile -------- Mensaje original -------- De: Garino Pierangelo Fecha:02/02/2015 01:07 PM (GMT+01:00) Para: Angel Hernandez ,Colombatto Davide ,I?igo Gonzalez ,Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org,Bollano Gianmario ,Antonini Roberto Asunto: R: Feb 2nd Demo Thank you all guys for your effort to show the demo! In fact sharing the screen has been the most critical issue to solve. At least we found that this webex connection, although not the best one, is working and is the only one I can set from my side. We?ll study more in detail other solutions to have them ready next time. I suggest a wrap-up after the demo, to be done either tomorrow or Thursday morning during the Robotics call @ 10, what?s vbest for you? Thanks again and talk to you soon again Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 11:58 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Guys, we need to get a hold from you ASAP. Davide, can you call I?igo? De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 10:36 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Hi Angel, Thanks, the logo what was I was looking for. I just need the Consoft?s too. Concerning the two issues you mention, they are Stories so I?ll add the corresponding Featureas but saying they are partially done. Can you check with Pepe or who is going to show the demo, if they can set up a join.me connection? The trouble of hangout for may 10 users is worrying me. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: luned? 2 febbraio 2015 10:28 A: Garino Pierangelo Cc: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Oggetto: RE: Feb 2nd Demo Hello Pier, Thanks for the slides they look pretty good. Just a couple of comments: - There are 2 features on jira that has also been closed, should they be added to the presentation? http://jira.fiware.org/browse/MIND-149 http://jira.fiware.org/browse/MIND-153 - Shouldn?t we add CONSOFT and Etxe-Tar Logos to the Architecture slides (4 and 5)? Or maybe none? I am attaching the ET logo, in case you didn?t have it. I will join myself at 11, and the rest of the team will get online by 11:30 Thank you! De: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Enviado el: lunes, 2 de febrero de 2015 9:22 Para: Angel Hernandez CC: fiware-robotics at lists.fi-ware.org; Colombatto Davide; Bollano Gianmario Asunto: R: Feb 2nd Demo Dear Angel and All, Here is an update to the slides accompanying the robotics demo today. Please have a look, especially to the architecture drawing, which is taken from the diagram provided by Davide. It will still be subject to modifications, according to the consolidation of the architecture we?ll do this month, but it should be enough clear for the presentation today. Additional information: the demo is scheduled at 12:00 (see attached mail), I have provided a backup communication channel in case we need to show the slides in a different way than hangout. Slides will be loaded on google drive, so that everybody will be able to access them independently. Please let me have your comments/updates on slides thanks. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: domenica 1 febbraio 2015 20:48 A: fiware-robotics at lists.fi-ware.org; Angel Hernandez Oggetto: [Fiware-robotics] R: Feb 2nd Demo Hi Angel, Yes I did it. Audio for all demos has to be powwownow while sharing is decided by providers and I defined hangout. However I'll provide a backup in case we don't succeed using it. Good idea would be recording a video upfront, in case of serious connection troubles. I plan to share slides before our timeslot which is scheduled at 12. Send you mails early in the morning tomorrow. BR Pier Inviato da smartphone Sony Xperia? ---- Angel Hernandez ha scritto ---- Pier, Have you been able to confirm the timeslot and call system for the demo tomorrow? 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 01D03FA5.E706A330]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From ahernandez at ikergune.com Thu Feb 5 09:22:28 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 5 Feb 2015 09:22:28 +0100 Subject: [Fiware-robotics] Live demo Brainstorming and network issues Message-ID: Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [cid:image001.png at 01D04125.428C22E0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2821 bytes Desc: image001.png URL: From roberto1.antonini at telecomitalia.it Thu Feb 5 10:03:19 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 5 Feb 2015 09:03:19 +0000 Subject: [Fiware-robotics] R: Live demo Brainstorming and network issues In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCDBD7F@TELMBB001BA020.telecomitalia.local> Hi Angel, for sure we are available to investigate issues we experienced on Monday. Besides, we'd like to go on and share with you some issues and doubts we have about FIROS - RCM interaction, indeed the next sprint we want to release the Service Space Features, that is the creation of a ROS container to host nodes related to a specific robot, and we have some doubts we wanted you to clarify. I would take my chance to face issues above via-hangout as you proposed, Let us know if you're available today and what time. Thanks, Roberto and Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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: 2821 bytes Desc: image001.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 Thu Feb 5 10:23:37 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 5 Feb 2015 09:23:37 +0000 Subject: [Fiware-robotics] R: Live demo Brainstorming and network issues In-Reply-To: References: Message-ID: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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: 2821 bytes Desc: image001.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 jjaime at ikergune.com Thu Feb 5 10:46:25 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 5 Feb 2015 10:46:25 +0100 Subject: [Fiware-robotics] R: Live demo Brainstorming and network issues References: Message-ID: Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn?t miss it, it?s just that I didn?t create yet (well, I didn?t share it?) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we?ll propose to the live demo group. For what concerns the demo issues I?m in favour to analyse them as well. We?ll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADIAAAAyCAYAAAAeP4ixAAAAAXNSR0IArs4c6QAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAqFSURBVGhD3VoJcJTlGX7/a6/s5mRDElBIUEICEYRqobUcg4ozIEchCdVKRRAzDKNxGKwXronYwSlUUBqUig46TiEy03oUiu1oW5liCRWUY42BJGKENMke2SO7/+5/9PljNs1mN9kkQMB+Mzth9/+O9/nf63nfD76iooL+HwafCISq6tMDAZcR85SecwOBAGc0Gj0mk8mTaI/heN4nEJttXwaRazpRx0Zi5FFGAyPx0bP1ZrP5tbKysmeGQ9BEZ8QFYrPtWHbHTM+Ts6dLNwm8zB0+RvTeh7FbsSw7MtEBw/U8BojNVjXvweXuNzY/Gzanj4AYKtF6iejFKqKnNhOJ4e9EYxiGAKTr23CJ2/c5UUBstiP6qRM9j1VsAIg0LHJ04iDWADBriT6tIdr/56svdDwJemnkq+xbbgpNzh6FqXDhiHerHQCTRDR39vcGCEmiSHInAqYXbnzHs2t29NLII81HTjz9yZla79LCydBCW5fcqUQhL9G7B65ZHBQFpKLCLdlsqc9vqAxP2/yMOLYoHx4CTbTCVyq3EH38r+8JEE3MiorVx222V0rqv/E+NnNGeLoih3I+/bfKnqq9dkFoksXNIxUVZYhPVGyz7ZlC1FQNw7rx2obRB5CI0Kp67gu9Xu8Pha51GAmAEL3TmfuufRhxgOzZsyezvp63Eklw/LAJIPRDBbJv377rvV6vRRAEueceLlcLuVw+Gj9+vLpp01YOgT2XePYHPCekMYoigpCexfeT5+vrT4iiGIyszcrKMqSlWXPB+QJLliz5urKyUsvXnSPGRy5caCpbPI8pGzNa1XIKGxTDmQwLLwEZ OfQxUZtrYLBeeumlUr/fX6koigUruoFIEvgOxo9uu42W/+wezmQWzKrKWxgcIisycYJAxqQkCsGe8ydMPCIGwy/W1p7sNA1rTs54g6D7Uygsndm1a9ci/NQNMgaIKoXSy9dQ9qw7Ma29S2hQFB/yyO2LBwZk69atGohdsiwn94YNn6N771tBJSWl0LlEwUDwkMIwB0mS7YDoZxXFiDc+TmXY2Xq98e60jKTqwqKiV89JX2mUT1JVGq0ostPlckWZfGzUYinMaFQQtIQCXWIg0yv4txxlIPE1s2PHjns7Ojp2AoSmiahhMBjo4YfL6e5Fi8nd7q7xe3wba2tPH4qz01/x26u5uQWTkpOlJ6wjMh9inZzRHwj8hhNk8AtGTEtLU5ubm7uXxg2/ikZRNOG7yBaLv3JUWdUniPvdbvdv8aY134oaYMqdmli4eDG1trZ+1NLuWtnc0HC+P0NtaLCfwvN7i6ZM+Uqv0z+rKsr1DGKPyvzPVCPrE1aICTyiW72w2dVQ9/Z4ILQ9pk6dRsUwJ4ej7ayzrWVVc1NTvyB6nnvyxImKwkmTM5NTUtZqvh8WwzG2cUlAVFXtzDBVVVVlTqdTA6GLB5znOFoETSAqKU6/41dNTU2NCV5QzGOn3/M83tqdluTkG0KRoqjHrCEDAQjieT4ETTzgcDi29QVCOyu/oIAm3zyVvF7PZ+cbCUxh8ANmeCF5wqS3YaI2hlERR6PHkIFo2yAylcInMgGiv1xzYdacOcfNSeb5rY62v4ii3T94GN+tYFT178gxWrWH3HMZgWDTMf0JpdPp6pEPflFcXDonJIrzYdufDRWEti4U6qjjQzonx/Es/DFqq0vSSH9CcRynWK3W8jVr1hz+T0vrOoNep7A8fX0pQPDivJbUNDdUcnlNqz+hkNEZvLUVNpvtowMHD7WHJUlFohtAJup717y8PNUfEOGd3cyke/IV0wiCAYPEuEzrtjhdTnNKSqoaDErgCEMfZy6eMYy 2jDWxHAetXEYfQYPuNEhddjgcTu9LPABadqymhhYsXKT6vYFczPvnUKFYDdnXIWplKrLchMxOCTP7QA9Cy/SP2PD0xYsX3+gvcjU2NiKHcAyv46dg77cHun/veSzpJ6JFy/m8vsuXEDWTgSbM69at+z1IYipC8cvgVzFhURPm889PIKM7iBf4+SCNz0OLMaYxMHDSQp4XQFHUGMJ0ST4CMIImwPr163eCLJrg3C9AMzFgGhsaqKbmKN05764CXmfY+fjjj6/DLQBaGgMfNxYU/FjQCfM6yxMguaw+gs26N4RmtnaBqYzUHJHDNBbw/nvv0ozpMyg/P395aelyM6LZSoCJNJz6RYSCyoQ6pMJssZgDHR1xS9ZL0kjv0wHmuS1bthhgZk8i/EY9Pn3qFFVX76NVq9fQwkVLFsA4dgPM/QDTb6kGU7RYM3NeFnT8XJej7Q8cL9zNsMzAMrugUT8ESjbSdAAB0aOqARNPOHbv3r1x1apVAkLvBvhM1Px3qqspIyODFv90Kd1z388XTr112o6g3/8ITDRGM0eOHOFXPPDADJMhaROi40yn0/GEzxvYn5ImLBgYRVFJaPPhZgTuGO66wmEBxIvfpNh0FsN27Xa74vF4fpmenm5sb29f11MzoZBIr+ysQr3uoqXLiumHt06/x+12TZEk+aAYDjeyxDoUVjHpiM2ZPO2WWRzDzGUZpsXtdDxkP31yV1FR0US1yy8T+khYZr99YhOdte6gQChSWIE/h6GROhCMiFYQzw34fBNPRVpToLi4eMPevXs5aOZ2gNG6xp3+pNXib725h7780s6g0AqNy8uzsCy/PtmSjEJO0YomCokwBYXOySRtbmlteR20v05bCxH0XTYV09mJ8RFs9rL9bNrv7D0aBj2FRR6KDC4lJaW7+O8NaNSoUUFEs7Xbtm1LwbMoh9E0UnP0qPaRqqurdagHJsuKmquEpRF4UU5JYmtdrsDp5mZ7pGvQub0UJJZPgn2ran sQNKHnmTFA4HyacH0KmNBJek0oLy+PEqb3epii1hn4R9en3+3B1XitZEbzIZCdna2ghOief1mjVjwpUlNTeRyqaUWE0PC0SxlKhk4nUKBD9pSUlKg9b6SvOBCz2TraZEl5U5Gkb/QF+tWiXYz0ZgaNCNq4TqfTozXlOw8QUUnxigOxWHhnOBTKhtQ35wRzMhqooWnQCLoWSIryE621I4VCX/Te44oDgTl5JhRO+jA9I31twB/AdTftHwqQXAyQ1Dt8Pj9yjhJzU3PFgWhCy6q8F6XuQzq97tEsfdYHzWLzoIOJYEx6EEzbCuq+va6urn7YNaIdWGe3f1I4qejtkSOzVsgkb2w+1fzUYLQCZdyRbDE/6nI660mRfh1v7bBoRDs44Pc95XS4iqwZI56kwkKT2+l8Dm/XmQhQfn7BAktyymu41We8no5Hzp2zf3tVgTQ0NDTl5lIJx7Gvj8zKKUf0mZuRYd3Z3h486PO1Xjh8+HAnAcI1BDN79uyk6/PG36rjuFKj0bCK4Vin29W+EiA+6Av4sGlEEwBgziKrL7puTO56QdCtNSdZqjje682wJp8am3eDG31dhFRFjz7zWPjTOPAs6kC3XuzwPgO/ONqf9oYViCYIsrHL7T7+NDrtbxlM7F16g3GmoqhFiqzkg3sY0UZysCzTKInB9/3+4IHW1ot/w5qE/1Vk2IFE3io67do9sfbZjsLJjL+pCK9aF99x7NgxD+h+QuF7auiqAekpBJxeoy7d9EWrWQY7/gt3e4Sf0F17lgAAAABJRU5ErkJggg==] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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 Thu Feb 5 10:47:19 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 5 Feb 2015 09:47:19 +0000 Subject: [Fiware-robotics] Live demo Brainstorming and network issues In-Reply-To: References: Message-ID: <069906BED271EB4A883BD9578DCDD3540255F1@TELMBB006RM001.telecomitalia.local> Hi Angel and All, We'd like to share with you (ET) our view of the use case for the Robotics GE. I also send you a txt which describes the schema, so we can talk of this in the next call in order to find a common view point by ET and TI. Please also consider that this is the complete/ideal view but not what we'll implement at the end of the major release. Particularly, at the end of the major release, there will not be the concept of "Cloud Computing" but only that of "Cloud Robotics", so the Master and the VM will be in the same machine. Let us know. BR, Davide ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 9.22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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: 2821 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Robotics GE_useCase.jpg Type: image/jpeg Size: 128634 bytes Desc: Robotics GE_useCase.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: useCase - main Interaction.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From roberto1.antonini at telecomitalia.it Thu Feb 5 10:58:50 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 5 Feb 2015 09:58:50 +0000 Subject: [Fiware-robotics] R: R: Live demo Brainstorming and network issues In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCDBE49@TELMBB001BA020.telecomitalia.local> Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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 jjaime at ikergune.com Thu Feb 5 11:10:03 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 5 Feb 2015 11:10:03 +0100 Subject: [Fiware-robotics] R: R: Live demo Brainstorming and network issues References: <246C286B275B1B46A255552CD236DA863BCDBE49@TELMBB001BA020.telecomitalia.local> Message-ID: Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn?t miss it, it?s just that I didn?t create yet (well, I didn?t share it?) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we?ll propose to the live demo group. For what concerns the demo issues I?m in favour to analyse them as well. We?ll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADIAAAAyCAYAAAAeP4ixAAAAAXNSR0IArs4c6QAAAAlwSFlzAAAOxAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAqFSURBVGhD3VoJcJTlGX7/a6/s5mRDElBIUEICEYRqobUcg4ozIEchCdVKRRAzDKNxGKwXronYwSlUUBqUig46TiEy03oUiu1oW5liCRWUY42BJGKENMke2SO7/+5/9PljNs1mN9kkQMB+Mzth9/+O9/nf63nfD76iooL+HwafCISq6tMDAZcR85SecwOBAGc0Gj0mk8mTaI/heN4nEJttXwaRazpRx0Zi5FFGAyPx0bP1ZrP5tbKysmeGQ9BEZ8QFYrPtWHbHTM+Ts6dLNwm8zB0+RvTeh7FbsSw7MtEBw/U8BojNVjXvweXuNzY/Gzanj4AYKtF6iejFKqKnNhOJ4e9EYxiGAKTr23CJ2/c5UUBstiP6qRM9j1VsAIg0LHJ04iDWADBriT6tIdr/56svdDwJemnkq+xbbgpNzh6FqXDhiHerHQCTRDR39vcGCEmiSHInAqYXbnzHs2t29NLII81HTjz9yZla79LCydBCW5fcqUQhL9G7B65ZHBQFpKLCLdlsqc9vqAxP2/yMOLYoHx4CTbTCVyq3EH38r+8JEE3MiorVx222V0rqv/E+NnNGeLoih3I+/bfKnqq9dkFoksXNIxUVZYhPVGyz7ZlC1FQNw7rx2obRB5CI0Kp67gu9Xu8Pha51GAmAEL3TmfuufRhxgOzZsyezvp63Eklw/LAJIPRDBbJv377rvV6vRRAEueceLlcLuVw+Gj9+vLpp01YOgT2XePYHPCekMYoigpCexfeT5+vrT4iiGIyszcrKMqSlWXPB+QJLliz5urKyUsvXnSPGRy5caCpbPI8pGzNa1XIKGxTDmQwLLwEZ OfQxUZtrYLBeeumlUr/fX6koigUruoFIEvgOxo9uu42W/+wezmQWzKrKWxgcIisycYJAxqQkCsGe8ydMPCIGwy/W1p7sNA1rTs54g6D7Uygsndm1a9ci/NQNMgaIKoXSy9dQ9qw7Ma29S2hQFB/yyO2LBwZk69atGohdsiwn94YNn6N771tBJSWl0LlEwUDwkMIwB0mS7YDoZxXFiDc+TmXY2Xq98e60jKTqwqKiV89JX2mUT1JVGq0ostPlckWZfGzUYinMaFQQtIQCXWIg0yv4txxlIPE1s2PHjns7Ojp2AoSmiahhMBjo4YfL6e5Fi8nd7q7xe3wba2tPH4qz01/x26u5uQWTkpOlJ6wjMh9inZzRHwj8hhNk8AtGTEtLU5ubm7uXxg2/ikZRNOG7yBaLv3JUWdUniPvdbvdv8aY134oaYMqdmli4eDG1trZ+1NLuWtnc0HC+P0NtaLCfwvN7i6ZM+Uqv0z+rKsr1DGKPyvzPVCPrE1aICTyiW72w2dVQ9/Z4ILQ9pk6dRsUwJ4ej7ayzrWVVc1NTvyB6nnvyxImKwkmTM5NTUtZqvh8WwzG2cUlAVFXtzDBVVVVlTqdTA6GLB5znOFoETSAqKU6/41dNTU2NCV5QzGOn3/M83tqdluTkG0KRoqjHrCEDAQjieT4ETTzgcDi29QVCOyu/oIAm3zyVvF7PZ+cbCUxh8ANmeCF5wqS3YaI2hlERR6PHkIFo2yAylcInMgGiv1xzYdacOcfNSeb5rY62v4ii3T94GN+tYFT178gxWrWH3HMZgWDTMf0JpdPp6pEPflFcXDonJIrzYdufDRWEti4U6qjjQzonx/Es/DFqq0vSSH9CcRynWK3W8jVr1hz+T0vrOoNep7A8fX0pQPDivJbUNDdUcnlNqz+hkNEZvLUVNpvtowMHD7WHJUlFohtAJup717y8PNUfEOGd3cyke/IV0wiCAYPEuEzrtjhdTnNKSqoaDErgCEMfZy6eMYy 2jDWxHAetXEYfQYPuNEhddjgcTu9LPABadqymhhYsXKT6vYFczPvnUKFYDdnXIWplKrLchMxOCTP7QA9Cy/SP2PD0x] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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 -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From roberto1.antonini at telecomitalia.it Thu Feb 5 11:23:42 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 5 Feb 2015 10:23:42 +0000 Subject: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCDBE49@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCDBE88@TELMBB001BA020.telecomitalia.local> Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [Descrizione: Immagine rimossa dal mittente. cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. [Descrizione: Immagine rimossa dal mittente. 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 -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 368 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 347 bytes Desc: image002.jpg URL: From gianmario.bollano at telecomitalia.it Thu Feb 5 12:42:50 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 5 Feb 2015 11:42:50 +0000 Subject: [Fiware-robotics] R: R: R: R: Live demo Brainstorming and network issues In-Reply-To: <246C286B275B1B46A255552CD236DA863BCDBE88@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCDBE49@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCDBE88@TELMBB001BA020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C207B59@telmba003ba020.telecomitalia.local> Sorry guys, we don't have anymore the Lab hotspot; I'm trying to connect through the TI proxy but I always get a message saying that the microphone is not working, and the I got a message saying "Impossible to start the Video Call for a network connection error". After that Hangout closes itself. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: gioved? 5 febbraio 2015 11:24 A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [Descrizione: Immagine rimossa dal mittente. cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. [Descrizione: Immagine rimossa dal mittente. 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 -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 368 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 347 bytes Desc: image002.jpg URL: From ahernandez at ikergune.com Thu Feb 5 13:08:41 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Thu, 5 Feb 2015 13:08:41 +0100 Subject: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Message-ID: Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [cid:image001.jpg at 01D04144.DD13AC60] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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:image002.jpg at 01D04144.DD13AC60]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 368 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 347 bytes Desc: image002.jpg URL: From thomas.bohnert at zhaw.ch Thu Feb 5 13:48:59 2015 From: thomas.bohnert at zhaw.ch (Thomas Michael Bohnert) Date: Thu, 05 Feb 2015 13:48:59 +0100 Subject: [Fiware-robotics] Live demo Brainstorming and network issues In-Reply-To: <989a9828543446a588ef1b181adc9660@SRV-MAIL-001.zhaw.ch> References: <989a9828543446a588ef1b181adc9660@SRV-MAIL-001.zhaw.ch> Message-ID: <54D366BB.5000804@zhaw.ch> Guys, ... don't misuse the term "cloud". Just running something on a VM is not cloud computing. That's virtualization. Go and look for the NIST Cloud Computing defintion to learn what's Cloud (and what's not). Best - Thomas On 02/05/2015 10:47 AM, Colombatto Davide wrote: > Hi Angel and All, > > We'd like to share with you (ET) our view of the use case for the > Robotics GE. > I also send you a txt which describes the schema, so we can talk of this > in the next call in order to find a common view point by ET and TI. > > Please also consider that this is the complete/ideal view but not what > we'll implement at the end of the major release. Particularly, at the > end of the major release, there will not be the concept of "Cloud > Computing" but only that of "Cloud Robotics", so the Master and the VM > will be in the same machine. > > Let us know. > > BR, > Davide > > > > ------------------------------------------------------------------------ > *Da:* fiware-robotics-bounces at lists.fi-ware.org > [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez > [ahernandez at ikergune.com] > *Inviato:* gioved? 5 febbraio 2015 9.22 > *A:* fiware-robotics at lists.fi-ware.org > *Oggetto:* [Fiware-robotics] Live demo Brainstorming and network issues > > Morning Pier, > > I am not sure if I missed it, but have you shared the brainstorming > document for the live demo e talked about? > > Please let me know if you need any help with that. > > Also, do you guys want to keep investigating the network issues we > experienced on Monday? > > Let us know if you want to do it over a hangouts session or so. > > Thank you, > > cid:image002.png at 01CFDBC7.CE9B41D0 > > > > *?ngel Hern?ndez*** > > Director de Proyectos I+D > > *M?vil:*+34 661 15 01 67 > > *IKERGUNE.*Grupo Etxe-Tar > > 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'ambienteRispetta l'ambiente. Non stampare questa mail se non > ? necessario.* > -- Thomas Michael Bohnert (TMB) Head of Service Engineering (ICCLab, SPLab) Zurich University of Applied Sciences eMail: thomas.bohnert at zhaw.ch mobile: +41791758136 web: www.cloudcomp.ch, tmb.nginet.de twitter: tmbohnert skype: tbohnert From davide.colombatto at telecomitalia.it Thu Feb 5 15:20:53 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 5 Feb 2015 14:20:53 +0000 Subject: [Fiware-robotics] Finish technical issues investigation 10:00 on friday In-Reply-To: References: Message-ID: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local> Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we?ve already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn?t miss it, it?s just that I didn?t create yet (well, I didn?t share it?) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we?ll propose to the live demo group. For what concerns the demo issues I?m in favour to analyse them as well. We?ll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [Descrizione: Immagine rimossa dal mittente. cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. [Descrizione: Immagine rimossa dal mittente. 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 -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 368 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 347 bytes Desc: image002.jpg URL: From roberto1.antonini at telecomitalia.it Thu Feb 5 16:25:05 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 5 Feb 2015 15:25:05 +0000 Subject: [Fiware-robotics] R: Finish technical issues investigation 10:00 on friday In-Reply-To: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [Descrizione: Immagine rimossa dal mittente. cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. [Descrizione: Immagine rimossa dal mittente. 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 -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 368 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 347 bytes Desc: image002.jpg URL: From davide.colombatto at telecomitalia.it Thu Feb 5 17:06:02 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 5 Feb 2015 16:06:02 +0000 Subject: [Fiware-robotics] Finish technical issues investigation 10:00 on friday In-Reply-To: <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD354025802@TELMBB006RM001.telecomitalia.local> Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that?s 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we?ve already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn?t miss it, it?s just that I didn?t create yet (well, I didn?t share it?) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we?ll propose to the live demo group. For what concerns the demo issues I?m in favour to analyse them as well. We?ll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [Descrizione: Immagine rimossa dal mittente. cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. [Descrizione: Immagine rimossa dal mittente. 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 -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 368 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 347 bytes Desc: image002.jpg URL: From igonzalez at ikergune.com Thu Feb 5 17:20:18 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 5 Feb 2015 17:20:18 +0100 Subject: [Fiware-robotics] Finish technical issues investigation 10:00 on friday References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025802@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that?s 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we?ve already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn?t miss it, it?s just that I didn?t create yet (well, I didn?t share it?) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we?ll propose to the live demo group. For what concerns the demo issues I?m in favour to analyse them as well. We?ll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/wAALCAAyADIBAREA/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEBAAA/APZqKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK/9k=] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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,/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/wAALCAAoABoBAREA/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEBAAA/APZqKKKKKKKKKKKKKKKKKKK//9k=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahernandez at ikergune.com Fri Feb 6 10:20:01 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Fri, 6 Feb 2015 10:20:01 +0100 Subject: [Fiware-robotics] Finish technical issues investigation 10:00 on friday In-Reply-To: References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025802@TELMBB006RM001.telecomitalia.local> Message-ID: Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and I?igo anyway. Have a good day. ?ngel De: I?igo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/wAALCAAyADIBAREA/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEBAAA/APZqKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK/9k=] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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,/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/wAALCAAoABoBAREA/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEBAAA/APZqKKKKKKKKKKKKKKKKKKK//9k=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- 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 Fri Feb 6 10:34:40 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 6 Feb 2015 09:34:40 +0000 Subject: [Fiware-robotics] R: Finish technical issues investigation 10:00 on friday In-Reply-To: References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025802@TELMBB006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD354025B5D@TELMBB006RM001.telecomitalia.local> Hi Angel and All, Yes, for what concerns "Technical issues investigation" yesterday we understood that the problem could be related to the network (too much distance between the two machine which cause timeout depending the route chosen by the IP packet) or some firewalls, so we'll do other tests on our side. Other point: Yesterday morning I sent you our view of a "use case" (schema and description) of the Robotics GE, I think that in the next call we can talk about that in order to clarify some points. Tell us when you will be ready to discuss of that schema or if you agree with that I sent you yesterday. BR, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 10:20 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and I?igo anyway. Have a good day. ?ngel De: I?igo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [Descrizione: Immagine rimossa dal mittente. cid:image002.png at 01CFDBC7.CE9B41D0] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. [Descrizione: Immagine rimossa dal mittente. 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 -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahernandez at ikergune.com Fri Feb 6 12:01:59 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Fri, 6 Feb 2015 12:01:59 +0100 Subject: [Fiware-robotics] Finish technical issues investigation 10:00 on friday In-Reply-To: <069906BED271EB4A883BD9578DCDD354025B5D@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025802@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025B5D@TELMBB006RM001.telecomitalia.local> Message-ID: Hello Davide, We wanted to talk about the live demo yesterday as well as the technical issues, but we didn't have enough time. The document you shared looks very good. It defines a good architecture and technical details for what we would need for a demo. What I feel we would be missing there is an overall description of what the whole demo idea is pursuing. For example something like what we just wrote on the document. In the end is just making a technical demo, appealing for the general public and future users of FIWARE, so the Teleoperation proposal you wrote is a very good start for the architecture definition of the Firefighting demo... or pretty much any demo we want to describe. Take a look at the document, and let us know what you think. Thanks! De: Colombatto Davide [mailto:davide.colombatto at telecomitalia.it] Enviado el: viernes, 6 de febrero de 2015 10:35 Para: Angel Hernandez; fiware-robotics at lists.fi-ware.org Asunto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel and All, Yes, for what concerns "Technical issues investigation" yesterday we understood that the problem could be related to the network (too much distance between the two machine which cause timeout depending the route chosen by the IP packet) or some firewalls, so we'll do other tests on our side. Other point: Yesterday morning I sent you our view of a "use case" (schema and description) of the Robotics GE, I think that in the next call we can talk about that in order to clarify some points. Tell us when you will be ready to discuss of that schema or if you agree with that I sent you yesterday. BR, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 10:20 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and I?igo anyway. Have a good day. ?ngel De: I?igo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, [data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/wAALCAAyADIBAREA/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEBAAA/APZqKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK/9k=] ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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,/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/wAALCAAoABoBAREA/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEBAAA/APZqKKKKKKKKKKKKKKKKKKK//9k=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From roberto1.antonini at telecomitalia.it Tue Feb 10 17:02:23 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Tue, 10 Feb 2015 16:02:23 +0000 Subject: [Fiware-robotics] R: Finish technical issues investigation 10:00 on friday References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025802@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025B5D@TELMBB006RM001.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCDF41E@TELMBB001BA020.telecomitalia.local> Hi Angel, you are right when you said that is missing the whole demo objective we want to pursue. In defining that, I would take into consideration the final users and that demo needs to be living. Being said that, here a list of point which summarizes our proposal: ? Starting with something ready to be used, so that we thought we can start from a "simple" Teleoperation and progressively add other capabilities ? Managing FIROS in order to connect CB and so enabling FIWARE apps to use robotics. Here we'd like ask you if you shared architecture proposal here attached (image with arch view and a brief description), where for each robot/clone is started a FIROS, in way a single FIROS could project its clone or robot to CB entity and update attributes according to ROS messages. If you agree we will put that schema and the description in the common WIKI page within Main Interaction section. ? Exploiting other GEs, such as KURENTO, in order to integrate their capabilities, in case of KURENTO RCM could start sort of web RTC streaming video client (wrapped by ROS node) as needed Hence, from what said above, the objective could be "making robotics effective and ready to use" to final users who want to use robots in their services. We guess the first step could be simply teleoperating a robot, following step could be adding a thermal camera (rosify it) and provide thermal image to user or application to detect thermal patterns such as candle flames. Besides, I would add path planning capability (AMCL and move base node properly configured) to send robot to a position in the map or to schedule predefined path to take thermal picture at a specific point ... As you can see we prefer a progressive approach, in order to elicit feedback after each step and maybe be in time to change something. BR Roberto and Davide. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 12:02 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello Davide, We wanted to talk about the live demo yesterday as well as the technical issues, but we didn't have enough time. The document you shared looks very good. It defines a good architecture and technical details for what we would need for a demo. What I feel we would be missing there is an overall description of what the whole demo idea is pursuing. For example something like what we just wrote on the document. In the end is just making a technical demo, appealing for the general public and future users of FIWARE, so the Teleoperation proposal you wrote is a very good start for the architecture definition of the Firefighting demo... or pretty much any demo we want to describe. Take a look at the document, and let us know what you think. Thanks! De: Colombatto Davide [mailto:davide.colombatto at telecomitalia.it] Enviado el: viernes, 6 de febrero de 2015 10:35 Para: Angel Hernandez; fiware-robotics at lists.fi-ware.org Asunto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel and All, Yes, for what concerns "Technical issues investigation" yesterday we understood that the problem could be related to the network (too much distance between the two machine which cause timeout depending the route chosen by the IP packet) or some firewalls, so we'll do other tests on our side. Other point: Yesterday morning I sent you our view of a "use case" (schema and description) of the Robotics GE, I think that in the next call we can talk about that in order to clarify some points. Tell us when you will be ready to discuss of that schema or if you agree with that I sent you yesterday. BR, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 10:20 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and I?igo anyway. Have a good day. ?ngel De: I?igo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: use_case.jpg Type: image/jpeg Size: 128634 bytes Desc: use_case.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Wiki Main Interaction.txt URL: From pierangelo.garino at telecomitalia.it Wed Feb 11 09:32:56 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 11 Feb 2015 08:32:56 +0000 Subject: [Fiware-robotics] R: Finish technical issues investigation 10:00 on friday In-Reply-To: <246C286B275B1B46A255552CD236DA863BCDF41E@TELMBB001BA020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD354025766@TELMBB006RM001.telecomitalia.local>, <246C286B275B1B46A255552CD236DA863BCDC030@TELMBB001BA020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025802@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354025B5D@TELMBB006RM001.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCDF41E@TELMBB001BA020.telecomitalia.local> Message-ID: Hi All, I see interesting proposals circulating and I do like the idea of showing a practical example that exploits robot(s) and the robotics GE. The idea is perfectly complementing a demo centered around the manufacturing field, in my opinion. But let me point out a couple of things we should consider. The purpose of live demo is to propose a use case as an example of GE adoption to the developers interested in using the robotics GE. Ideally, the demo should be easy to reproduced by the interested developer. This means that we should clearly explain, step by step, how to program/implement the example. I believe therefore that we cannot be too much demanding about the robot to be used. However, I also believe that a nice example, although not completely reproducible by others, is appealing. I would therefore be in favour of the incremental/progressive approach to the live demo scenario: start with one robot, simple teleoperation, add sensors/cameras, include more GEs, add 'mission', include more robots, etc... In summary, I would use the use case explained by Angel as comprehensive example for the live demo, but clearly stating that there are steps which will be implemented for sure by M13, while others might be implemented depending on the time/resources available, and maybe completed later. Sort of a basic configuration + enriching features; on the other hand we'll probably create Features explicitly for the live demo... This incremental approach would avoid committing ourselves to a scenario perhaps difficult to achieve, and to keep example simple enough for 'end users' of the live demo who could replicate it easily, even without the specific robot we're willing to use (btw, do we have one with the characteristics depicted?). What's your opinion? BR Pier Da: Antonini Roberto Inviato: marted? 10 febbraio 2015 17:02 A: Angel Hernandez (ahernandez at ikergune.com); fiware-robotics at lists.fi-ware.org Cc: Colombatto Davide; Garino Pierangelo; Bollano Gianmario Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, you are right when you said that is missing the whole demo objective we want to pursue. In defining that, I would take into consideration the final users and that demo needs to be living. Being said that, here a list of point which summarizes our proposal: ? Starting with something ready to be used, so that we thought we can start from a "simple" Teleoperation and progressively add other capabilities ? Managing FIROS in order to connect CB and so enabling FIWARE apps to use robotics. Here we'd like ask you if you shared architecture proposal here attached (image with arch view and a brief description), where for each robot/clone is started a FIROS, in way a single FIROS could project its clone or robot to CB entity and update attributes according to ROS messages. If you agree we will put that schema and the description in the common WIKI page within Main Interaction section. ? Exploiting other GEs, such as KURENTO, in order to integrate their capabilities, in case of KURENTO RCM could start sort of web RTC streaming video client (wrapped by ROS node) as needed Hence, from what said above, the objective could be "making robotics effective and ready to use" to final users who want to use robots in their services. We guess the first step could be simply teleoperating a robot, following step could be adding a thermal camera (rosify it) and provide thermal image to user or application to detect thermal patterns such as candle flames. Besides, I would add path planning capability (AMCL and move base node properly configured) to send robot to a position in the map or to schedule predefined path to take thermal picture at a specific point ... As you can see we prefer a progressive approach, in order to elicit feedback after each step and maybe be in time to change something. BR Roberto and Davide. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 12:02 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello Davide, We wanted to talk about the live demo yesterday as well as the technical issues, but we didn't have enough time. The document you shared looks very good. It defines a good architecture and technical details for what we would need for a demo. What I feel we would be missing there is an overall description of what the whole demo idea is pursuing. For example something like what we just wrote on the document. In the end is just making a technical demo, appealing for the general public and future users of FIWARE, so the Teleoperation proposal you wrote is a very good start for the architecture definition of the Firefighting demo... or pretty much any demo we want to describe. Take a look at the document, and let us know what you think. Thanks! De: Colombatto Davide [mailto:davide.colombatto at telecomitalia.it] Enviado el: viernes, 6 de febrero de 2015 10:35 Para: Angel Hernandez; fiware-robotics at lists.fi-ware.org Asunto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel and All, Yes, for what concerns "Technical issues investigation" yesterday we understood that the problem could be related to the network (too much distance between the two machine which cause timeout depending the route chosen by the IP packet) or some firewalls, so we'll do other tests on our side. Other point: Yesterday morning I sent you our view of a "use case" (schema and description) of the Robotics GE, I think that in the next call we can talk about that in order to clarify some points. Tell us when you will be ready to discuss of that schema or if you agree with that I sent you yesterday. BR, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 10:20 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and I?igo anyway. Have a good day. ?ngel De: I?igo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From roberto1.antonini at telecomitalia.it Wed Feb 11 12:27:39 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Wed, 11 Feb 2015 11:27:39 +0000 Subject: [Fiware-robotics] Live demo plan Message-ID: <246C286B275B1B46A255552CD236DA863BCDF998@TELMBB001BA020.telecomitalia.local> Hi guys, with Luis we agreed on a plan to integrate their stuff into robotics platform, so just to summarize (in bold the milestones): ? At client side: we should send to him the characteristics of the robots we want to use for the demo, here we have a turtlebot2 and a camera (Logitech c270) ready to be used, I would ask you if you have some robot to be used for the demo, if so tell Luis its characteristics ? Test: given robot characteristics above, Luis will provide us with some configuration we need to do to test end-to-end video streaming, for instance by using WebRTC Technology with Chrome browser at robot side. We can assess latencies and basic functionalities, such as adaptive bandwidth, of video streaming directly at server side (Chrome browser) ? Wrapper ROS Node: once tests above succeed, we start building a ROS node to wrap Chrome Browser Web RTC client to capture the camera video stream, in order to start the client with SL/SN REST API. ? UI: understand how to involve Web UI GE, in order to build web application to remotely teleoperate the robot, this GE is connected to: o IoT CB: to manage robot entities, i.e. by updating /cmd_vel attribute according to keyboard button pressing or joysticks moving o KURENTO: to view video streaming, with Chrome embedded player The times to accomplish tasks above could be (just a proposal): ? by the end of the week, for what concerns the client side milestone. ? By the end of the month, for what concerns the test of e2e video streaming. ? By the end of the next month (Release 4.2), we (as TI) can release Wrapper ROS node. In the meanwhile I would suggest that ET guys get in touch with Web UI GE guys, in order to understand how to involve them. Pier let us know if times proposed are compatible with deadline to release at least the first part for live demo. BR, Davide and Roberto ? UI: Da: Garino Pierangelo Inviato: mercoled? 11 febbraio 2015 09:33 A: Antonini Roberto; Angel Hernandez (ahernandez at ikergune.com) Cc: Colombatto Davide; Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi All, I see interesting proposals circulating and I do like the idea of showing a practical example that exploits robot(s) and the robotics GE. The idea is perfectly complementing a demo centered around the manufacturing field, in my opinion. But let me point out a couple of things we should consider. The purpose of live demo is to propose a use case as an example of GE adoption to the developers interested in using the robotics GE. Ideally, the demo should be easy to reproduced by the interested developer. This means that we should clearly explain, step by step, how to program/implement the example. I believe therefore that we cannot be too much demanding about the robot to be used. However, I also believe that a nice example, although not completely reproducible by others, is appealing. I would therefore be in favour of the incremental/progressive approach to the live demo scenario: start with one robot, simple teleoperation, add sensors/cameras, include more GEs, add 'mission', include more robots, etc... In summary, I would use the use case explained by Angel as comprehensive example for the live demo, but clearly stating that there are steps which will be implemented for sure by M13, while others might be implemented depending on the time/resources available, and maybe completed later. Sort of a basic configuration + enriching features; on the other hand we'll probably create Features explicitly for the live demo... This incremental approach would avoid committing ourselves to a scenario perhaps difficult to achieve, and to keep example simple enough for 'end users' of the live demo who could replicate it easily, even without the specific robot we're willing to use (btw, do we have one with the characteristics depicted?). What's your opinion? BR Pier Da: Antonini Roberto Inviato: marted? 10 febbraio 2015 17:02 A: Angel Hernandez (ahernandez at ikergune.com); fiware-robotics at lists.fi-ware.org Cc: Colombatto Davide; Garino Pierangelo; Bollano Gianmario Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, you are right when you said that is missing the whole demo objective we want to pursue. In defining that, I would take into consideration the final users and that demo needs to be living. Being said that, here a list of point which summarizes our proposal: ? Starting with something ready to be used, so that we thought we can start from a "simple" Teleoperation and progressively add other capabilities ? Managing FIROS in order to connect CB and so enabling FIWARE apps to use robotics. Here we'd like ask you if you shared architecture proposal here attached (image with arch view and a brief description), where for each robot/clone is started a FIROS, in way a single FIROS could project its clone or robot to CB entity and update attributes according to ROS messages. If you agree we will put that schema and the description in the common WIKI page within Main Interaction section. ? Exploiting other GEs, such as KURENTO, in order to integrate their capabilities, in case of KURENTO RCM could start sort of web RTC streaming video client (wrapped by ROS node) as needed Hence, from what said above, the objective could be "making robotics effective and ready to use" to final users who want to use robots in their services. We guess the first step could be simply teleoperating a robot, following step could be adding a thermal camera (rosify it) and provide thermal image to user or application to detect thermal patterns such as candle flames. Besides, I would add path planning capability (AMCL and move base node properly configured) to send robot to a position in the map or to schedule predefined path to take thermal picture at a specific point ... As you can see we prefer a progressive approach, in order to elicit feedback after each step and maybe be in time to change something. BR Roberto and Davide. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 12:02 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello Davide, We wanted to talk about the live demo yesterday as well as the technical issues, but we didn't have enough time. The document you shared looks very good. It defines a good architecture and technical details for what we would need for a demo. What I feel we would be missing there is an overall description of what the whole demo idea is pursuing. For example something like what we just wrote on the document. In the end is just making a technical demo, appealing for the general public and future users of FIWARE, so the Teleoperation proposal you wrote is a very good start for the architecture definition of the Firefighting demo... or pretty much any demo we want to describe. Take a look at the document, and let us know what you think. Thanks! De: Colombatto Davide [mailto:davide.colombatto at telecomitalia.it] Enviado el: viernes, 6 de febrero de 2015 10:35 Para: Angel Hernandez; fiware-robotics at lists.fi-ware.org Asunto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel and All, Yes, for what concerns "Technical issues investigation" yesterday we understood that the problem could be related to the network (too much distance between the two machine which cause timeout depending the route chosen by the IP packet) or some firewalls, so we'll do other tests on our side. Other point: Yesterday morning I sent you our view of a "use case" (schema and description) of the Robotics GE, I think that in the next call we can talk about that in order to clarify some points. Tell us when you will be ready to discuss of that schema or if you agree with that I sent you yesterday. BR, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 10:20 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and I?igo anyway. Have a good day. ?ngel De: I?igo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From roberto1.antonini at telecomitalia.it Wed Feb 11 13:54:09 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Wed, 11 Feb 2015 12:54:09 +0000 Subject: [Fiware-robotics] Robot characteristics Message-ID: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> Hi Luis As agreed, we start sending to you the characteristics of the robot we have here, that's a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available at http://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). Let us know if this's enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. Thank you. Davide and Roberto 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 Wed Feb 11 14:49:08 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 11 Feb 2015 13:49:08 +0000 Subject: [Fiware-robotics] R: Live demo plan In-Reply-To: <246C286B275B1B46A255552CD236DA863BCDF998@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCDF998@TELMBB001BA020.telecomitalia.local> Message-ID: Hi Roberto, Currently the first deadline we have to meet is releasing a description of the live demo, rather than its implementation. Therefore the timing you propose is more than acceptable in my view. I remind that the entire live demo should be ready and working by M13, i.e. at end of r4.4. It is however good to have this first step ready well in advance, so that we can concentrate on the further functionalities we're going to define for the live demo, by 'merging' the demo ideas so far proposed. So let's continue working in parallel on the details of the demo on one side as well as on the demo description that's required by the end of the week (Angel, we should refine this latter in the google docs, as we said this morning: can you provide the description of interactions with the GEs listed?) Thanks and BR Pier Da: Antonini Roberto Inviato: mercoled? 11 febbraio 2015 12:28 A: Garino Pierangelo; Angel Hernandez (ahernandez at ikergune.com) Cc: Colombatto Davide; Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo plan Hi guys, with Luis we agreed on a plan to integrate their stuff into robotics platform, so just to summarize (in bold the milestones): ? At client side: we should send to him the characteristics of the robots we want to use for the demo, here we have a turtlebot2 and a camera (Logitech c270) ready to be used, I would ask you if you have some robot to be used for the demo, if so tell Luis its characteristics ? Test: given robot characteristics above, Luis will provide us with some configuration we need to do to test end-to-end video streaming, for instance by using WebRTC Technology with Chrome browser at robot side. We can assess latencies and basic functionalities, such as adaptive bandwidth, of video streaming directly at server side (Chrome browser) ? Wrapper ROS Node: once tests above succeed, we start building a ROS node to wrap Chrome Browser Web RTC client to capture the camera video stream, in order to start the client with SL/SN REST API. ? UI: understand how to involve Web UI GE, in order to build web application to remotely teleoperate the robot, this GE is connected to: o IoT CB: to manage robot entities, i.e. by updating /cmd_vel attribute according to keyboard button pressing or joysticks moving o KURENTO: to view video streaming, with Chrome embedded player The times to accomplish tasks above could be (just a proposal): ? by the end of the week, for what concerns the client side milestone. ? By the end of the month, for what concerns the test of e2e video streaming. ? By the end of the next month (Release 4.2), we (as TI) can release Wrapper ROS node. In the meanwhile I would suggest that ET guys get in touch with Web UI GE guys, in order to understand how to involve them. Pier let us know if times proposed are compatible with deadline to release at least the first part for live demo. BR, Davide and Roberto ? UI: Da: Garino Pierangelo Inviato: mercoled? 11 febbraio 2015 09:33 A: Antonini Roberto; Angel Hernandez (ahernandez at ikergune.com) Cc: Colombatto Davide; Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi All, I see interesting proposals circulating and I do like the idea of showing a practical example that exploits robot(s) and the robotics GE. The idea is perfectly complementing a demo centered around the manufacturing field, in my opinion. But let me point out a couple of things we should consider. The purpose of live demo is to propose a use case as an example of GE adoption to the developers interested in using the robotics GE. Ideally, the demo should be easy to reproduced by the interested developer. This means that we should clearly explain, step by step, how to program/implement the example. I believe therefore that we cannot be too much demanding about the robot to be used. However, I also believe that a nice example, although not completely reproducible by others, is appealing. I would therefore be in favour of the incremental/progressive approach to the live demo scenario: start with one robot, simple teleoperation, add sensors/cameras, include more GEs, add 'mission', include more robots, etc... In summary, I would use the use case explained by Angel as comprehensive example for the live demo, but clearly stating that there are steps which will be implemented for sure by M13, while others might be implemented depending on the time/resources available, and maybe completed later. Sort of a basic configuration + enriching features; on the other hand we'll probably create Features explicitly for the live demo... This incremental approach would avoid committing ourselves to a scenario perhaps difficult to achieve, and to keep example simple enough for 'end users' of the live demo who could replicate it easily, even without the specific robot we're willing to use (btw, do we have one with the characteristics depicted?). What's your opinion? BR Pier Da: Antonini Roberto Inviato: marted? 10 febbraio 2015 17:02 A: Angel Hernandez (ahernandez at ikergune.com); fiware-robotics at lists.fi-ware.org Cc: Colombatto Davide; Garino Pierangelo; Bollano Gianmario Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, you are right when you said that is missing the whole demo objective we want to pursue. In defining that, I would take into consideration the final users and that demo needs to be living. Being said that, here a list of point which summarizes our proposal: ? Starting with something ready to be used, so that we thought we can start from a "simple" Teleoperation and progressively add other capabilities ? Managing FIROS in order to connect CB and so enabling FIWARE apps to use robotics. Here we'd like ask you if you shared architecture proposal here attached (image with arch view and a brief description), where for each robot/clone is started a FIROS, in way a single FIROS could project its clone or robot to CB entity and update attributes according to ROS messages. If you agree we will put that schema and the description in the common WIKI page within Main Interaction section. ? Exploiting other GEs, such as KURENTO, in order to integrate their capabilities, in case of KURENTO RCM could start sort of web RTC streaming video client (wrapped by ROS node) as needed Hence, from what said above, the objective could be "making robotics effective and ready to use" to final users who want to use robots in their services. We guess the first step could be simply teleoperating a robot, following step could be adding a thermal camera (rosify it) and provide thermal image to user or application to detect thermal patterns such as candle flames. Besides, I would add path planning capability (AMCL and move base node properly configured) to send robot to a position in the map or to schedule predefined path to take thermal picture at a specific point ... As you can see we prefer a progressive approach, in order to elicit feedback after each step and maybe be in time to change something. BR Roberto and Davide. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 12:02 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello Davide, We wanted to talk about the live demo yesterday as well as the technical issues, but we didn't have enough time. The document you shared looks very good. It defines a good architecture and technical details for what we would need for a demo. What I feel we would be missing there is an overall description of what the whole demo idea is pursuing. For example something like what we just wrote on the document. In the end is just making a technical demo, appealing for the general public and future users of FIWARE, so the Teleoperation proposal you wrote is a very good start for the architecture definition of the Firefighting demo... or pretty much any demo we want to describe. Take a look at the document, and let us know what you think. Thanks! De: Colombatto Davide [mailto:davide.colombatto at telecomitalia.it] Enviado el: viernes, 6 de febrero de 2015 10:35 Para: Angel Hernandez; fiware-robotics at lists.fi-ware.org Asunto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel and All, Yes, for what concerns "Technical issues investigation" yesterday we understood that the problem could be related to the network (too much distance between the two machine which cause timeout depending the route chosen by the IP packet) or some firewalls, so we'll do other tests on our side. Other point: Yesterday morning I sent you our view of a "use case" (schema and description) of the Robotics GE, I think that in the next call we can talk about that in order to clarify some points. Tell us when you will be ready to discuss of that schema or if you agree with that I sent you yesterday. BR, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerd? 6 febbraio 2015 10:20 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and I?igo anyway. Have a good day. ?ngel De: I?igo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, I?igo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: gioved? 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto 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? 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Angel Hernandez [ahernandez at ikergune.com] Inviato: gioved? 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R 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: gioved? 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R 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: gioved? 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: gioved? 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, ?ngel Hern?ndez Director de Proyectos I+D M?vil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar 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. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- 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 Thu Feb 12 16:29:21 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Thu, 12 Feb 2015 16:29:21 +0100 Subject: [Fiware-robotics] Robot characteristics In-Reply-To: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> Message-ID: Hi Roberto, basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. 1. Use the WebRTC Google stack. * This is the most mature WebRTC stack providing lots of advanced features * It's the stack used by Chrome * Can be compiled and used independently on the browser (with some work) * Only supports VP8 codec. Supporting H264 requires some complex integrations * Details of it can be found here: http://www.webrtc.org/ 2. Use the WebRTC Ericsson Stack * Less mature but also less heavy * Supports natively H.264, which is a more performant codec for your use case. * Details can be found here: http://www.openwebrtc.io/ Here, my choice would be option 1, but you may wish to perform a deeper analysis. For validating that you webcam works correctly with WebRTC, do the following: - Provide internet connectivity to the robot - Install chrome on it - Open this URL -- https://talky.io/ - Fill a string in the form (e.g. "aaa") and press the button. - Accept to share the webcam - The video should appear - Open another browser into another computer with Internet connectivity and a webcam - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) - Accept to share the webcam - You should have a video conference between the two browsers Best. ----------------------------------------------------------- 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 11/02/2015, a las 13:54, Antonini Roberto escribi?: > Hi Luis > As agreed, we start sending to you the characteristics of the robot we have here, that?s a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) > The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). > > Let us know if this?s enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. > Thank you. > Davide and Roberto > 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 roberto1.antonini at telecomitalia.it Tue Feb 17 16:12:18 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Tue, 17 Feb 2015 15:12:18 +0000 Subject: [Fiware-robotics] R: Robot characteristics In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> Hi Luis, thanks for having promptly answered my e-mail . Amongst the solutions you've proposed, it's not clear (at least to me) which of these are using KURENTO GE. I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. Anyway, just to better clarify what we meant to do: On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. BR Roberto and Davide Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 12 febbraio 2015 16:29 A: Antonini Roberto Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org Oggetto: Re: Robot characteristics Hi Roberto, basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. 1. Use the WebRTC Google stack. * This is the most mature WebRTC stack providing lots of advanced features * It's the stack used by Chrome * Can be compiled and used independently on the browser (with some work) * Only supports VP8 codec. Supporting H264 requires some complex integrations * Details of it can be found here: http://www.webrtc.org/ 2. Use the WebRTC Ericsson Stack * Less mature but also less heavy * Supports natively H.264, which is a more performant codec for your use case. * Details can be found here: http://www.openwebrtc.io/ Here, my choice would be option 1, but you may wish to perform a deeper analysis. For validating that you webcam works correctly with WebRTC, do the following: - Provide internet connectivity to the robot - Install chrome on it - Open this URL -- https://talky.io/ - Fill a string in the form (e.g. "aaa") and press the button. - Accept to share the webcam - The video should appear - Open another browser into another computer with Internet connectivity and a webcam - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) - Accept to share the webcam - You should have a video conference between the two browsers Best. ----------------------------------------------------------- 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 11/02/2015, a las 13:54, Antonini Roberto > escribi?: Hi Luis As agreed, we start sending to you the characteristics of the robot we have here, that's a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). Let us know if this's enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. Thank you. Davide and Roberto 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 luis.lopez at urjc.es Tue Feb 17 16:19:46 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Tue, 17 Feb 2015 16:19:46 +0100 Subject: [Fiware-robotics] Robot characteristics In-Reply-To: <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> Message-ID: <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> Hi Roberto, Please, take into consideration the following information for having an understanding on how to use Kurento: Kurento is: - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) Kurento is not: - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) Hence, in your architecture, you need two ingredients: - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols - A WebRTC server, for receiving the stream and "do things" with that stream. The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. I hope this clarifies the issues. Best. El 17/02/2015, a las 16:12, Antonini Roberto escribi?: > Hi Luis, > thanks for having promptly answered my e-mail . > Amongst the solutions you?ve proposed, it?s not clear (at least to me) which of these are using KURENTO GE. > I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. > > Anyway, just to better clarify what we meant to do: > On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? > Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. > > BR > Roberto and Davide > > Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] > Inviato: gioved? 12 febbraio 2015 16:29 > A: Antonini Roberto > Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org > Oggetto: Re: Robot characteristics > > Hi Roberto, > > basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. > > 1. Use the WebRTC Google stack. > * This is the most mature WebRTC stack providing lots of advanced features > * It's the stack used by Chrome > * Can be compiled and used independently on the browser (with some work) > * Only supports VP8 codec. Supporting H264 requires some complex integrations > * Details of it can be found here: http://www.webrtc.org/ > > 2. Use the WebRTC Ericsson Stack > * Less mature but also less heavy > * Supports natively H.264, which is a more performant codec for your use case. > * Details can be found here: http://www.openwebrtc.io/ > > Here, my choice would be option 1, but you may wish to perform a deeper analysis. > > > For validating that you webcam works correctly with WebRTC, do the following: > > - Provide internet connectivity to the robot > - Install chrome on it > - Open this URL > -- https://talky.io/ > - Fill a string in the form (e.g. "aaa") and press the button. > - Accept to share the webcam > - The video should appear > - Open another browser into another computer with Internet connectivity and a webcam > - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) > - Accept to share the webcam > - You should have a video conference between the two browsers > > Best. > > > ----------------------------------------------------------- > 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 11/02/2015, a las 13:54, Antonini Roberto escribi?: > > > Hi Luis > As agreed, we start sending to you the characteristics of the robot we have here, that?s a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) > The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). > > Let us know if this?s enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. > Thank you. > Davide and Roberto > 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 Tue Feb 17 16:47:37 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 17 Feb 2015 15:47:37 +0000 Subject: [Fiware-robotics] R: Robot characteristics In-Reply-To: <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> Hi Luis, I think the questions arisen from Roberto and Davide can be summarized as: - Assuming to use a chrome browser, do we need a specific "Kurento Client" code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. 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? 17 febbraio 2015 16:20 A: Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Roberto, Please, take into consideration the following information for having an understanding on how to use Kurento: Kurento is: - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) Kurento is not: - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) Hence, in your architecture, you need two ingredients: - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols - A WebRTC server, for receiving the stream and "do things" with that stream. The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. I hope this clarifies the issues. Best. El 17/02/2015, a las 16:12, Antonini Roberto > escribi?: Hi Luis, thanks for having promptly answered my e-mail . Amongst the solutions you've proposed, it's not clear (at least to me) which of these are using KURENTO GE. I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. Anyway, just to better clarify what we meant to do: On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. BR Roberto and Davide Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 12 febbraio 2015 16:29 A: Antonini Roberto Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org Oggetto: Re: Robot characteristics Hi Roberto, basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. 1. Use the WebRTC Google stack. * This is the most mature WebRTC stack providing lots of advanced features * It's the stack used by Chrome * Can be compiled and used independently on the browser (with some work) * Only supports VP8 codec. Supporting H264 requires some complex integrations * Details of it can be found here: http://www.webrtc.org/ 2. Use the WebRTC Ericsson Stack * Less mature but also less heavy * Supports natively H.264, which is a more performant codec for your use case. * Details can be found here: http://www.openwebrtc.io/ Here, my choice would be option 1, but you may wish to perform a deeper analysis. For validating that you webcam works correctly with WebRTC, do the following: - Provide internet connectivity to the robot - Install chrome on it - Open this URL -- https://talky.io/ - Fill a string in the form (e.g. "aaa") and press the button. - Accept to share the webcam - The video should appear - Open another browser into another computer with Internet connectivity and a webcam - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) - Accept to share the webcam - You should have a video conference between the two browsers Best. ----------------------------------------------------------- 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 11/02/2015, a las 13:54, Antonini Roberto > escribi?: Hi Luis As agreed, we start sending to you the characteristics of the robot we have here, that's a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). Let us know if this's enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. Thank you. Davide and Roberto 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 luis.lopez at urjc.es Tue Feb 17 19:04:59 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Tue, 17 Feb 2015 19:04:59 +0100 Subject: [Fiware-robotics] Robot characteristics In-Reply-To: <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> Message-ID: <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> Hi Answers inline El 17/02/2015, a las 16:47, Bollano Gianmario escribi?: > Hi Luis, > I think the questions arisen from Roberto and Davide can be summarized as: > - Assuming to use a chrome browser, do we need a specific ?Kurento Client? code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? The short answer is no. The long answer is that it depend on the architecture of your application. Probably, the simplest way for you to start working with kurento is following one of these tutorials: 1. Read first this and pay attention to the role of the application server (node or java based) http://www.kurento.org/docs/current/introducing_kurento.html After that, my opinion is that you should go to an architecture based on application server, so the browser does not speak directly with Kurento Media Server. You can find several tutorials of applications basing on such architecture. For example In java http://www.kurento.org/docs/current/tutorials/java/tutorial-1-helloworld.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-1-helloworld.html For making something more useful (e.g. making possible to robot to broadcast the video to a number of receivers), take a look to these tutorials: In java http://www.kurento.org/docs/current/tutorials/java/tutorial-3-one2many.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html > - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? Install one of the tutorials listed above and open them from the robot using a chrome browser. That should do the job. > > The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. If you were able to execute the simple peer-to-peer example I provided in a previous mail (basing on talky.io for example), then you won't have problems for interoperating with Kurento. > This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. Again, you can check this with the basic peer-to-peer example based on talky.io without requiring Kurento at all for it. Best. > > 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? 17 febbraio 2015 16:20 > A: Antonini Roberto > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Robot characteristics > > Hi Roberto, > Please, take into consideration the following information for having an understanding on how to use Kurento: > > Kurento is: > - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) > - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) > > Kurento is not: > - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) > > > Hence, in your architecture, you need two ingredients: > - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols > - A WebRTC server, for receiving the stream and "do things" with that stream. > > > The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. > > The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. > > I hope this clarifies the issues. > > Best. > > > El 17/02/2015, a las 16:12, Antonini Roberto escribi?: > > > Hi Luis, > thanks for having promptly answered my e-mail . > Amongst the solutions you?ve proposed, it?s not clear (at least to me) which of these are using KURENTO GE. > I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. > > Anyway, just to better clarify what we meant to do: > On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? > Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. > > BR > Roberto and Davide > > Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] > Inviato: gioved? 12 febbraio 2015 16:29 > A: Antonini Roberto > Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org > Oggetto: Re: Robot characteristics > > Hi Roberto, > > basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. > > 1. Use the WebRTC Google stack. > * This is the most mature WebRTC stack providing lots of advanced features > * It's the stack used by Chrome > * Can be compiled and used independently on the browser (with some work) > * Only supports VP8 codec. Supporting H264 requires some complex integrations > * Details of it can be found here: http://www.webrtc.org/ > > 2. Use the WebRTC Ericsson Stack > * Less mature but also less heavy > * Supports natively H.264, which is a more performant codec for your use case. > * Details can be found here: http://www.openwebrtc.io/ > > Here, my choice would be option 1, but you may wish to perform a deeper analysis. > > > For validating that you webcam works correctly with WebRTC, do the following: > > - Provide internet connectivity to the robot > - Install chrome on it > - Open this URL > -- https://talky.io/ > - Fill a string in the form (e.g. "aaa") and press the button. > - Accept to share the webcam > - The video should appear > - Open another browser into another computer with Internet connectivity and a webcam > - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) > - Accept to share the webcam > - You should have a video conference between the two browsers > > Best. > > > ----------------------------------------------------------- > 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 11/02/2015, a las 13:54, Antonini Roberto escribi?: > > > > Hi Luis > As agreed, we start sending to you the characteristics of the robot we have here, that?s a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) > The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). > > Let us know if this?s enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. > Thank you. > Davide and Roberto > 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 Feb 18 12:41:22 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 18 Feb 2015 11:41:22 +0000 Subject: [Fiware-robotics] R: Robot characteristics In-Reply-To: <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C20E5AA@telmba003ba020.telecomitalia.local> Hi Luis, I have found initially of documentation from the FIWARE pages and it was quite complex to understand where to get clear code and examples. Probably the catalog page it's not the simplest page to start with, because it provides lot - for me too many - links for Kurento server and Client at Kurento Github, at NPM, at Maven Central, Bower and Kurento FIWARE Forge Repository ... Really hard to understand which component may be needed and where to get them. Information at Kurento.org is definitely more helpful; without digging deep in the technical details, from the Tutorial it is clear there are three different "usage scenarios" , also represented in the picture in the introducing_kurento tutorial ("Kurento Api, Client and Protocol" section). In my understanding, these 3 scenario mapped to our environment becomes: 1. Robot equipped with Chrome + NodeJS + Bower + Kurento JS Client + Application Code. This allow to have Application server as localhost in the robot and to open the browser for transmitting video in the same environment. Having everything in the Robot allows to communicate directly with a Kurento media server. The Browser endpoint connects to Kurento server. 2. Robot with Chrome only, which connect to on external Linux App server with NodeJS + Bower + Kurento JS Client + Application Code (downloaded and launched in the Robot browser). 3. As 2, but working in Java EE App server and Java Kurento client instead of JS. I believe the scenario 3 beyond the purposes of the Robotics live demo because it requires larger development effort and Java EE knowledge, however the Robotics developers may better evaluate this issue. The scenario 1. is preferable but we have to check if the Robot has the requirements to host all the Application Server software. The scenario 2 move the Application server outside the Robot and is less resource consuming for the Robot, but it involves further issues concerning communication between Robot and the Application server. Robotics GE adopts ROS environment which already consider a Robot Entity composed of nodes communicating in their way, same of them placed externally to the Robot (in a service Space which runs also in an external server). Moreover, our demo also use an external application server to send and display Robots commands, which interact with Context broker on one side and calls Robotics management APIs, but the Robot ROS environment (between ROS nodes) is isolated (also for Robotics security reasons) and cannot communicate with that external server. This issue should be better investigated because it may be important also for the scenario 1. The talk.io test may be come handy to test if WebRTC support from Chrome is working fine in the Robot, but does not require Kurento. The next steps will need to use a configuration including a Kurento Client (thus using Kurento protocol) and we'll need an instance of Kurento Server. Do you think it would be possible in the next phase to use a FI-LAB instance of Kurento to make some test with a Kurento Client? The solution of installing a local Kurento Server wouldn't probably simplify the communication issues with the Robotics platform, and probably would have less impact for Robotics and Kurento GEs demo. For the same reason we are using an external instance of the Context Broker: one of purpose of the live demo is to show interoperability of different FIWARE GEs in the Cloud. We are still defining the Live demo, and at this stage it's not yet completely defined if and how exploiting the Kurento advanced features (beyond the basic video streaming supported by WebRTC). One idea might be working on some pattern or face detection when we use an Infrared camera. This solution would obviously imply the usage of Kurento equipped with some processing function among the ones already developed and already made available with Kurento (no need to have ad-hoc functions, but use of one of the Kurento processing components available). This is my general understanding and overview; all the other Robotics in the mailing list guys have deeper knowledge of the technical details and specifications of the Robotics Platforms GE components, they can arise more precise proposals or questions. Thank you, Gianmario Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: marted? 17 febbraio 2015 19:05 A: Bollano Gianmario Cc: Antonini Roberto; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Answers inline El 17/02/2015, a las 16:47, Bollano Gianmario > escribi?: Hi Luis, I think the questions arisen from Roberto and Davide can be summarized as: - Assuming to use a chrome browser, do we need a specific "Kurento Client" code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? The short answer is no. The long answer is that it depend on the architecture of your application. Probably, the simplest way for you to start working with kurento is following one of these tutorials: 1. Read first this and pay attention to the role of the application server (node or java based) http://www.kurento.org/docs/current/introducing_kurento.html After that, my opinion is that you should go to an architecture based on application server, so the browser does not speak directly with Kurento Media Server. You can find several tutorials of applications basing on such architecture. For example In java http://www.kurento.org/docs/current/tutorials/java/tutorial-1-helloworld.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-1-helloworld.html For making something more useful (e.g. making possible to robot to broadcast the video to a number of receivers), take a look to these tutorials: In java http://www.kurento.org/docs/current/tutorials/java/tutorial-3-one2many.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? Install one of the tutorials listed above and open them from the robot using a chrome browser. That should do the job. The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. If you were able to execute the simple peer-to-peer example I provided in a previous mail (basing on talky.io for example), then you won't have problems for interoperating with Kurento. This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. Again, you can check this with the basic peer-to-peer example based on talky.io without requiring Kurento at all for it. Best. 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? 17 febbraio 2015 16:20 A: Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Roberto, Please, take into consideration the following information for having an understanding on how to use Kurento: Kurento is: - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) Kurento is not: - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) Hence, in your architecture, you need two ingredients: - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols - A WebRTC server, for receiving the stream and "do things" with that stream. The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. I hope this clarifies the issues. Best. El 17/02/2015, a las 16:12, Antonini Roberto > escribi?: Hi Luis, thanks for having promptly answered my e-mail . Amongst the solutions you've proposed, it's not clear (at least to me) which of these are using KURENTO GE. I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. Anyway, just to better clarify what we meant to do: On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. BR Roberto and Davide Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 12 febbraio 2015 16:29 A: Antonini Roberto Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org Oggetto: Re: Robot characteristics Hi Roberto, basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. 1. Use the WebRTC Google stack. * This is the most mature WebRTC stack providing lots of advanced features * It's the stack used by Chrome * Can be compiled and used independently on the browser (with some work) * Only supports VP8 codec. Supporting H264 requires some complex integrations * Details of it can be found here: http://www.webrtc.org/ 2. Use the WebRTC Ericsson Stack * Less mature but also less heavy * Supports natively H.264, which is a more performant codec for your use case. * Details can be found here: http://www.openwebrtc.io/ Here, my choice would be option 1, but you may wish to perform a deeper analysis. For validating that you webcam works correctly with WebRTC, do the following: - Provide internet connectivity to the robot - Install chrome on it - Open this URL -- https://talky.io/ - Fill a string in the form (e.g. "aaa") and press the button. - Accept to share the webcam - The video should appear - Open another browser into another computer with Internet connectivity and a webcam - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) - Accept to share the webcam - You should have a video conference between the two browsers Best. ----------------------------------------------------------- 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 11/02/2015, a las 13:54, Antonini Roberto > escribi?: Hi Luis As agreed, we start sending to you the characteristics of the robot we have here, that's a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). Let us know if this's enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. Thank you. Davide and Roberto 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 luis.lopez at urjc.es Thu Feb 19 09:54:13 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Thu, 19 Feb 2015 09:54:13 +0100 Subject: [Fiware-robotics] Robot characteristics In-Reply-To: <7E649CBD84A947498203DAF8F098B1F62C20E5AA@telmba003ba020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E5AA@telmba003ba020.telecomitalia.local> Message-ID: Hi, Some comments inline El 18/02/2015, a las 12:41, Bollano Gianmario escribi?: > Hi Luis, > I have found initially of documentation from the FIWARE pages and it was quite complex to understand where to get clear code and examples. Probably the catalog page it?s not the simplest page to start with, because it provides lot ? for me too many - links for Kurento server and Client at Kurento Github, at NPM, at Maven Central, Bower and Kurento FIWARE Forge Repository ? Really hard to understand which component may be needed and where to get them. > > Information at Kurento.org is definitely more helpful; without digging deep in the technical details, from the Tutorial it is clear there are three different ?usage scenarios? , also represented in the picture in the introducing_kurento tutorial (?Kurento Api, Client and Protocol? section). > In my understanding, these 3 scenario mapped to our environment becomes: > > 1. Robot equipped with Chrome + NodeJS + Bower + Kurento JS Client + Application Code. This allow to have Application server as localhost in the robot and to open the browser for transmitting video in the same environment. Having everything in the Robot allows to communicate directly with a Kurento media server. The Browser endpoint connects to Kurento server. > 2. Robot with Chrome only, which connect to on external Linux App server with NodeJS + Bower + Kurento JS Client + Application Code (downloaded and launched in the Robot browser). > 3. As 2, but working in Java EE App server and Java Kurento client instead of JS. > > > I believe the scenario 3 beyond the purposes of the Robotics live demo because it requires larger development effort and Java EE knowledge, however the Robotics developers may better evaluate this issue. The scenario 1. is preferable but we have to check if the Robot has the requirements to host all the Application Server software. I think you should go to scenario 2 or 3 and use an Application Server external to the robot. You can base the Application Server on Java EE or in Node.js, but definitely you need that Application Server to be external to the robot. Otherwise, you limit too much the use cases you may be supporting. We can discuss about this slowly if you want, but putting the AS in the robot is not the best design decision and there are strong reasons for it: - You won't be able to put the robot behind a NAT easily and connect from external applications (browsers) to the Application Server. - You will be putting CPU overhead in the robot - You will make the application too sensitive to robot network access. IMHO, you should go to option 2 or 3 and put in a FIWARE Lab node both, the Kurento server and the application server. You have may examples on doing it in Kurento.org tutorials. It wont' hurt you and you'll benefit from lots of advantages. > The scenario 2 move the Application server outside the Robot and is less resource consuming for the Robot, but it involves further issues concerning communication between Robot and the Application server. You will just need to put the AS into a well known IP. > Robotics GE adopts ROS environment which already consider a Robot Entity composed of nodes communicating in their way, same of them placed externally to the Robot (in a service Space which runs also in an external server). Moreover, our demo also use an external application server to send and display Robots commands, which interact with Context broker on one side and calls Robotics management APIs, but the Robot ROS environment (between ROS nodes) is isolated (also for Robotics security reasons) and cannot communicate with that external server. This issue should be better investigated because it may be important also for the scenario 1. If you cannot communicate with the external world you won't be able to see any video. > > The talk.io test may be come handy to test if WebRTC support from Chrome is working fine in the Robot, but does not require Kurento. The next steps will need to use a configuration including a Kurento Client (thus using Kurento protocol) and we?ll need an instance of Kurento Server. Do you think it would be possible in the next phase to use a FI-LAB instance of Kurento to make some test with a Kurento Client? The solution of installing a local Kurento Server wouldn?t probably simplify the communication issues with the Robotics platform, and probably would have less impact for Robotics and Kurento GEs demo. For the same reason we are using an external instance of the Context Broker: one of purpose of the live demo is to show interoperability of different FIWARE GEs in the Cloud. We are having a lot of problems with the FIWARE Lab. You can launch a Kurento server there and it works sometimes ... but sometimes it doesn't. > > We are still defining the Live demo, and at this stage it?s not yet completely defined if and how exploiting the Kurento advanced features (beyond the basic video streaming supported by WebRTC). One idea might be working on some pattern or face detection when we use an Infrared camera. This solution would obviously imply the usage of Kurento equipped with some processing function among the ones already developed and already made available with Kurento (no need to have ad-hoc functions, but use of one of the Kurento processing components available). > > This is my general understanding and overview; all the other Robotics in the mailing list guys have deeper knowledge of the technical details and specifications of the Robotics Platforms GE components, they can arise more precise proposals or questions. > > Thank you, > Gianmario > > > Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] > Inviato: marted? 17 febbraio 2015 19:05 > A: Bollano Gianmario > Cc: Antonini Roberto; fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Robot characteristics > > Hi > > Answers inline > > El 17/02/2015, a las 16:47, Bollano Gianmario escribi?: > > > Hi Luis, > I think the questions arisen from Roberto and Davide can be summarized as: > - Assuming to use a chrome browser, do we need a specific ?Kurento Client? code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? > > The short answer is no. The long answer is that it depend on the architecture of your application. Probably, the simplest way for you to start working with kurento is following one of these tutorials: > > 1. Read first this and pay attention to the role of the application server (node or java based) > http://www.kurento.org/docs/current/introducing_kurento.html > > After that, my opinion is that you should go to an architecture based on application server, so the browser does not speak directly with Kurento Media Server. You can find several tutorials of applications basing on such architecture. For example > > In java > http://www.kurento.org/docs/current/tutorials/java/tutorial-1-helloworld.html > > In JavaScript (for Node.js) > http://www.kurento.org/docs/current/tutorials/node/tutorial-1-helloworld.html > > For making something more useful (e.g. making possible to robot to broadcast the video to a number of receivers), take a look to these tutorials: > > In java > http://www.kurento.org/docs/current/tutorials/java/tutorial-3-one2many.html > > In JavaScript (for Node.js) > http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html > > > - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? > > Install one of the tutorials listed above and open them from the robot using a chrome browser. That should do the job. > > > > The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. > > If you were able to execute the simple peer-to-peer example I provided in a previous mail (basing on talky.io for example), then you won't have problems for interoperating with Kurento. > > > This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. > > Again, you can check this with the basic peer-to-peer example based on talky.io without requiring Kurento at all for it. > > > Best. > > > > > 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? 17 febbraio 2015 16:20 > A: Antonini Roberto > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] Robot characteristics > > Hi Roberto, > Please, take into consideration the following information for having an understanding on how to use Kurento: > > Kurento is: > - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) > - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) > > Kurento is not: > - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) > > > Hence, in your architecture, you need two ingredients: > - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols > - A WebRTC server, for receiving the stream and "do things" with that stream. > > > The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. > > The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. > > I hope this clarifies the issues. > > Best. > > > El 17/02/2015, a las 16:12, Antonini Roberto escribi?: > > > > Hi Luis, > thanks for having promptly answered my e-mail . > Amongst the solutions you?ve proposed, it?s not clear (at least to me) which of these are using KURENTO GE. > I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. > > Anyway, just to better clarify what we meant to do: > On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? > Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. > > BR > Roberto and Davide > > Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] > Inviato: gioved? 12 febbraio 2015 16:29 > A: Antonini Roberto > Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org > Oggetto: Re: Robot characteristics > > Hi Roberto, > > basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. > > 1. Use the WebRTC Google stack. > * This is the most mature WebRTC stack providing lots of advanced features > * It's the stack used by Chrome > * Can be compiled and used independently on the browser (with some work) > * Only supports VP8 codec. Supporting H264 requires some complex integrations > * Details of it can be found here: http://www.webrtc.org/ > > 2. Use the WebRTC Ericsson Stack > * Less mature but also less heavy > * Supports natively H.264, which is a more performant codec for your use case. > * Details can be found here: http://www.openwebrtc.io/ > > Here, my choice would be option 1, but you may wish to perform a deeper analysis. > > > For validating that you webcam works correctly with WebRTC, do the following: > > - Provide internet connectivity to the robot > - Install chrome on it > - Open this URL > -- https://talky.io/ > - Fill a string in the form (e.g. "aaa") and press the button. > - Accept to share the webcam > - The video should appear > - Open another browser into another computer with Internet connectivity and a webcam > - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) > - Accept to share the webcam > - You should have a video conference between the two browsers > > Best. > > > ----------------------------------------------------------- > 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 11/02/2015, a las 13:54, Antonini Roberto escribi?: > > > > > Hi Luis > As agreed, we start sending to you the characteristics of the robot we have here, that?s a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) > The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). > > Let us know if this?s enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. > Thank you. > Davide and Roberto > 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 igonzalez at ikergune.com Thu Feb 19 09:56:21 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 19 Feb 2015 09:56:21 +0100 Subject: [Fiware-robotics] R: Robot characteristics References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E5AA@telmba003ba020.telecomitalia.local> Message-ID: Hi everyone, as we are talking about doing the live demo with Kurento we think its interesting and useful for us using it for image processing. We have deployed the versions 5.0.33 and 5.0.4 in fiware to test the tutorials that are available in https://github.com/Kurento/kurento-tutorial-js We have only been able to send video via Kurento, we cannot do any image processing (that we think that is a very interesting feature for robotics area), so we put here the problems we have found so Luis can help us or put us in touch with someone who could help us with them, or maybe we can talk via skype or hangout to be more efficient: * The bower files use adapter.js with kurento-alvar branch, but it doesn't exist, so we used master branch and in the html dependencies we have changed "bower_components/adapter.js/samples/web/js/adapter.js" with "bower_components/adapter.js/adapter.js" FIXED * The kurento-crowddetector show us an error: 'Error: Unexpected error while processing method: Factory not found {code: -32603, stack: (...), message: "Unexpected error while processing method: Factory not found"}' I supposed that is related with something that is not installed, I have researched but I didn't find anything about this. * The kurento-faceoverlay-generator doesn't add any overlay on the video and doesn't give us any error. * The kurento-chroma doesn't show anything, but also we don't understand how it works, it tooks the upper left corner to do something but we don't know what. * The kurento-background give us many errors: * Bower doesn't know where kurento-module-backgroundextractor.js is I have search it on internet and finally I have been able to extract it from a jar file I found in a maven repository. FIXED * After fixing that I have tried the demo but it gives me the same error as in the crowdetector (Factory not found) * It also gives me another error: 'TypeError: Cannot read property 'processSdpAnswer' of null {stack: (...), message: "Cannot read property 'processSdpAnswer' of null"}' And I don't know how to continue. I wanted to do some pull request fixing the html, bower and js issues I have found, but first of all I want to be sure that I can make the examples work. So any help would be great. Regards, I?igo On 18/02/15 12:41, Bollano Gianmario wrote: Hi Luis, I have found initially of documentation from the FIWARE pages and it was quite complex to understand where to get clear code and examples. Probably the catalog page it?s not the simplest page to start with, because it provides lot ? for me too many - links for Kurento server and Client at Kurento Github, at NPM, at Maven Central, Bower and Kurento FIWARE Forge Repository ? Really hard to understand which component may be needed and where to get them. Information at Kurento.org is definitely more helpful; without digging deep in the technical details, from the Tutorial it is clear there are three different ?usage scenarios? , also represented in the picture in the introducing_kurento tutorial (?Kurento Api, Client and Protocol? section). In my understanding, these 3 scenario mapped to our environment becomes: 1. Robot equipped with Chrome + NodeJS + Bower + Kurento JS Client + Application Code. This allow to have Application server as localhost in the robot and to open the browser for transmitting video in the same environment. Having everything in the Robot allows to communicate directly with a Kurento media server. The Browser endpoint connects to Kurento server. 2. Robot with Chrome only, which connect to on external Linux App server with NodeJS + Bower + Kurento JS Client + Application Code (downloaded and launched in the Robot browser). 3. As 2, but working in Java EE App server and Java Kurento client instead of JS. I believe the scenario 3 beyond the purposes of the Robotics live demo because it requires larger development effort and Java EE knowledge, however the Robotics developers may better evaluate this issue. The scenario 1. is preferable but we have to check if the Robot has the requirements to host all the Application Server software. The scenario 2 move the Application server outside the Robot and is less resource consuming for the Robot, but it involves further issues concerning communication between Robot and the Application server. Robotics GE adopts ROS environment which already consider a Robot Entity composed of nodes communicating in their way, same of them placed externally to the Robot (in a service Space which runs also in an external server). Moreover, our demo also use an external application server to send and display Robots commands, which interact with Context broker on one side and calls Robotics management APIs, but the Robot ROS environment (between ROS nodes) is isolated (also for Robotics security reasons) and cannot communicate with that external server. This issue should be better investigated because it may be important also for the scenario 1. The talk.io test may be come handy to test if WebRTC support from Chrome is working fine in the Robot, but does not require Kurento. The next steps will need to use a configuration including a Kurento Client (thus using Kurento protocol) and we?ll need an instance of Kurento Server. Do you think it would be possible in the next phase to use a FI-LAB instance of Kurento to make some test with a Kurento Client? The solution of installing a local Kurento Server wouldn?t probably simplify the communication issues with the Robotics platform, and probably would have less impact for Robotics and Kurento GEs demo. For the same reason we are using an external instance of the Context Broker: one of purpose of the live demo is to show interoperability of different FIWARE GEs in the Cloud. We are still defining the Live demo, and at this stage it?s not yet completely defined if and how exploiting the Kurento advanced features (beyond the basic video streaming supported by WebRTC). One idea might be working on some pattern or face detection when we use an Infrared camera. This solution would obviously imply the usage of Kurento equipped with some processing function among the ones already developed and already made available with Kurento (no need to have ad-hoc functions, but use of one of the Kurento processing components available). This is my general understanding and overview; all the other Robotics in the mailing list guys have deeper knowledge of the technical details and specifications of the Robotics Platforms GE components, they can arise more precise proposals or questions. Thank you, Gianmario Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: marted? 17 febbraio 2015 19:05 A: Bollano Gianmario Cc: Antonini Roberto; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Answers inline El 17/02/2015, a las 16:47, Bollano Gianmario > escribi?: Hi Luis, I think the questions arisen from Roberto and Davide can be summarized as: - Assuming to use a chrome browser, do we need a specific ?Kurento Client? code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? The short answer is no. The long answer is that it depend on the architecture of your application. Probably, the simplest way for you to start working with kurento is following one of these tutorials: 1. Read first this and pay attention to the role of the application server (node or java based) http://www.kurento.org/docs/current/introducing_kurento.html After that, my opinion is that you should go to an architecture based on application server, so the browser does not speak directly with Kurento Media Server. You can find several tutorials of applications basing on such architecture. For example In java http://www.kurento.org/docs/current/tutorials/java/tutorial-1-helloworld.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-1-helloworld.html For making something more useful (e.g. making possible to robot to broadcast the video to a number of receivers), take a look to these tutorials: In java http://www.kurento.org/docs/current/tutorials/java/tutorial-3-one2many.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? Install one of the tutorials listed above and open them from the robot using a chrome browser. That should do the job. The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. If you were able to execute the simple peer-to-peer example I provided in a previous mail (basing on talky.io for example), then you won't have problems for interoperating with Kurento. This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. Again, you can check this with the basic peer-to-peer example based on talky.io without requiring Kurento at all for it. Best. 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? 17 febbraio 2015 16:20 A: Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Roberto, Please, take into consideration the following information for having an understanding on how to use Kurento: Kurento is: - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) Kurento is not: - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) Hence, in your architecture, you need two ingredients: - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols - A WebRTC server, for receiving the stream and "do things" with that stream. The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. I hope this clarifies the issues. Best. El 17/02/2015, a las 16:12, Antonini Roberto > escribi?: Hi Luis, thanks for having promptly answered my e-mail . Amongst the solutions you?ve proposed, it?s not clear (at least to me) which of these are using KURENTO GE. I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. Anyway, just to better clarify what we meant to do: On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. BR Roberto and Davide Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 12 febbraio 2015 16:29 A: Antonini Roberto Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org Oggetto: Re: Robot characteristics Hi Roberto, basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. 1. Use the WebRTC Google stack. * This is the most mature WebRTC stack providing lots of advanced features * It's the stack used by Chrome * Can be compiled and used independently on the browser (with some work) * Only supports VP8 codec. Supporting H264 requires some complex integrations * Details of it can be found here: http://www.webrtc.org/ 2. Use the WebRTC Ericsson Stack * Less mature but also less heavy * Supports natively H.264, which is a more performant codec for your use case. * Details can be found here: http://www.openwebrtc.io/ Here, my choice would be option 1, but you may wish to perform a deeper analysis. For validating that you webcam works correctly with WebRTC, do the following: - Provide internet connectivity to the robot - Install chrome on it - Open this URL -- https://talky.io/ - Fill a string in the form (e.g. "aaa") and press the button. - Accept to share the webcam - The video should appear - Open another browser into another computer with Internet connectivity and a webcam - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) - Accept to share the webcam - You should have a video conference between the two browsers Best. ----------------------------------------------------------- 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 11/02/2015, a las 13:54, Antonini Roberto > escribi?: Hi Luis As agreed, we start sending to you the characteristics of the robot we have here, that?s a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). Let us know if this?s enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. Thank you. Davide and Roberto 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 luis.lopez at urjc.es Thu Feb 19 10:27:32 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Thu, 19 Feb 2015 10:27:32 +0100 Subject: [Fiware-robotics] Robot characteristics In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E5AA@telmba003ba020.telecomitalia.local> Message-ID: <80AAE603-4375-44AA-A0CC-8991833B65C4@urjc.es> Hi, Answers inline El 19/02/2015, a las 09:56, I?igo Gonzalez escribi?: > Hi everyone, > > as we are talking about doing the live demo with Kurento we think its interesting and useful for us using it for image processing. We have deployed the versions 5.0.33 and 5.0.4 in fiware to test the tutorials that are available in https://github.com/Kurento/kurento-tutorial-js You should upgrade to KMS v5.1.0, otherwise you wont' be able to install any module. > > We have only been able to send video via Kurento, we cannot do any image processing (that we think that is a very interesting feature for robotics area), so we put here the problems we have found so Luis can help us or put us in touch with someone who could help us with them, or maybe we can talk via skype or hangout to be more efficient: > The bower files use adapter.js with kurento-alvar branch, but it doesn't exist, so we used master branch and in the html dependencies we have changed "bower_components/adapter.js/samples/web/js/adapter.js" with "bower_components/adapter.js/adapter.js" FIXED This was caused by Google guys, who moved the adapter.js location in github unexpectedly. The fix is ready in our develop branch. > The kurento-crowddetector show us an error: 'Error: Unexpected error while processing method: Factory not found {code: -32603, stack: (...), message: "Unexpected error while processing method: Factory not found"}' I supposed that is related with something that is not installed, I have researched but I didn't find anything about this. You need to install the module. In FIWARE Lab it's not installed. You just need to execute (you need our ppa repo to be configured, of course) sudo apt-get install kms-crowddetector > The kurento-faceoverlay-generator doesn't add any overlay on the video and doesn't give us any error. We'd need to check the logs. Probably you are not specifying the location of the overlayed image appropriately. You need to specify it using an URL. Example: - file:///tmp/myimage.png - http://mysite.com/myimage.png > The kurento-chroma doesn't show anything, but also we don't understand how it works, it tooks the upper left corner to do something but we don't know what. You need to have a chroma (a background with a single color) and calibrate the filter for that color. > The kurento-background give us many errors: > Bower doesn't know where kurento-module-backgroundextractor.js is I have search it on internet and finally I have been able to extract it from a jar file I found in a maven repository. FIXED > After fixing that I have tried the demo but it gives me the same error as in the crowdetector (Factory not found) > It also gives me another error: 'TypeError: Cannot read property 'processSdpAnswer' of null {stack: (...), message: "Cannot read property 'processSdpAnswer' of null"}' And I don't know how to continue. This filter is experimental and very unstable. Please do not use it. > I wanted to do some pull request fixing the html, bower and js issues I have found, but first of all I want to be sure that I can make the examples work. So any help would be great. This is already fixed in development branch. > > Regards, > I?igo > > > On 18/02/15 12:41, Bollano Gianmario wrote: >> Hi Luis, >> I have found initially of documentation from the FIWARE pages and it was quite complex to understand where to get clear code and examples. Probably the catalog page it?s not the simplest page to start with, because it provides lot ? for me too many - links for Kurento server and Client at Kurento Github, at NPM, at Maven Central, Bower and Kurento FIWARE Forge Repository ? Really hard to understand which component may be needed and where to get them. >> >> Information at Kurento.org is definitely more helpful; without digging deep in the technical details, from the Tutorial it is clear there are three different ?usage scenarios? , also represented in the picture in the introducing_kurento tutorial (?Kurento Api, Client and Protocol? section). >> In my understanding, these 3 scenario mapped to our environment becomes: >> >> 1. Robot equipped with Chrome + NodeJS + Bower + Kurento JS Client + Application Code. This allow to have Application server as localhost in the robot and to open the browser for transmitting video in the same environment. Having everything in the Robot allows to communicate directly with a Kurento media server. The Browser endpoint connects to Kurento server. >> 2. Robot with Chrome only, which connect to on external Linux App server with NodeJS + Bower + Kurento JS Client + Application Code (downloaded and launched in the Robot browser). >> 3. As 2, but working in Java EE App server and Java Kurento client instead of JS. >> >> >> I believe the scenario 3 beyond the purposes of the Robotics live demo because it requires larger development effort and Java EE knowledge, however the Robotics developers may better evaluate this issue. The scenario 1. is preferable but we have to check if the Robot has the requirements to host all the Application Server software. >> The scenario 2 move the Application server outside the Robot and is less resource consuming for the Robot, but it involves further issues concerning communication between Robot and the Application server. Robotics GE adopts ROS environment which already consider a Robot Entity composed of nodes communicating in their way, same of them placed externally to the Robot (in a service Space which runs also in an external server). Moreover, our demo also use an external application server to send and display Robots commands, which interact with Context broker on one side and calls Robotics management APIs, but the Robot ROS environment (between ROS nodes) is isolated (also for Robotics security reasons) and cannot communicate with that external server. This issue should be better investigated because it may be important also for the scenario 1. >> >> The talk.io test may be come handy to test if WebRTC support from Chrome is working fine in the Robot, but does not require Kurento. The next steps will need to use a configuration including a Kurento Client (thus using Kurento protocol) and we?ll need an instance of Kurento Server. Do you think it would be possible in the next phase to use a FI-LAB instance of Kurento to make some test with a Kurento Client? The solution of installing a local Kurento Server wouldn?t probably simplify the communication issues with the Robotics platform, and probably would have less impact for Robotics and Kurento GEs demo. For the same reason we are using an external instance of the Context Broker: one of purpose of the live demo is to show interoperability of different FIWARE GEs in the Cloud. >> >> We are still defining the Live demo, and at this stage it?s not yet completely defined if and how exploiting the Kurento advanced features (beyond the basic video streaming supported by WebRTC). One idea might be working on some pattern or face detection when we use an Infrared camera. This solution would obviously imply the usage of Kurento equipped with some processing function among the ones already developed and already made available with Kurento (no need to have ad-hoc functions, but use of one of the Kurento processing components available). >> >> This is my general understanding and overview; all the other Robotics in the mailing list guys have deeper knowledge of the technical details and specifications of the Robotics Platforms GE components, they can arise more precise proposals or questions. >> >> Thank you, >> Gianmario >> >> >> Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] >> Inviato: marted? 17 febbraio 2015 19:05 >> A: Bollano Gianmario >> Cc: Antonini Roberto; fiware-robotics at lists.fi-ware.org >> Oggetto: Re: [Fiware-robotics] Robot characteristics >> >> Hi >> >> Answers inline >> >> El 17/02/2015, a las 16:47, Bollano Gianmario escribi?: >> >> >> Hi Luis, >> I think the questions arisen from Roberto and Davide can be summarized as: >> - Assuming to use a chrome browser, do we need a specific ?Kurento Client? code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? >> >> The short answer is no. The long answer is that it depend on the architecture of your application. Probably, the simplest way for you to start working with kurento is following one of these tutorials: >> >> 1. Read first this and pay attention to the role of the application server (node or java based) >> http://www.kurento.org/docs/current/introducing_kurento.html >> >> After that, my opinion is that you should go to an architecture based on application server, so the browser does not speak directly with Kurento Media Server. You can find several tutorials of applications basing on such architecture. For example >> >> In java >> http://www.kurento.org/docs/current/tutorials/java/tutorial-1-helloworld.html >> >> In JavaScript (for Node.js) >> http://www.kurento.org/docs/current/tutorials/node/tutorial-1-helloworld.html >> >> For making something more useful (e.g. making possible to robot to broadcast the video to a number of receivers), take a look to these tutorials: >> >> In java >> http://www.kurento.org/docs/current/tutorials/java/tutorial-3-one2many.html >> >> In JavaScript (for Node.js) >> http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html >> >> >> - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? >> >> Install one of the tutorials listed above and open them from the robot using a chrome browser. That should do the job. >> >> >> >> The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. >> >> If you were able to execute the simple peer-to-peer example I provided in a previous mail (basing on talky.io for example), then you won't have problems for interoperating with Kurento. >> >> >> This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. >> >> Again, you can check this with the basic peer-to-peer example based on talky.io without requiring Kurento at all for it. >> >> >> Best. >> >> >> >> >> 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? 17 febbraio 2015 16:20 >> A: Antonini Roberto >> Cc: fiware-robotics at lists.fi-ware.org >> Oggetto: Re: [Fiware-robotics] Robot characteristics >> >> Hi Roberto, >> Please, take into consideration the following information for having an understanding on how to use Kurento: >> >> Kurento is: >> - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) >> - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) >> >> Kurento is not: >> - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) >> >> >> Hence, in your architecture, you need two ingredients: >> - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols >> - A WebRTC server, for receiving the stream and "do things" with that stream. >> >> >> The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. >> >> The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. >> >> I hope this clarifies the issues. >> >> Best. >> >> >> El 17/02/2015, a las 16:12, Antonini Roberto escribi?: >> >> >> >> Hi Luis, >> thanks for having promptly answered my e-mail . >> Amongst the solutions you?ve proposed, it?s not clear (at least to me) which of these are using KURENTO GE. >> I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. >> >> Anyway, just to better clarify what we meant to do: >> On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? >> Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. >> >> BR >> Roberto and Davide >> >> Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] >> Inviato: gioved? 12 febbraio 2015 16:29 >> A: Antonini Roberto >> Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org >> Oggetto: Re: Robot characteristics >> >> Hi Roberto, >> >> basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. >> >> 1. Use the WebRTC Google stack. >> * This is the most mature WebRTC stack providing lots of advanced features >> * It's the stack used by Chrome >> * Can be compiled and used independently on the browser (with some work) >> * Only supports VP8 codec. Supporting H264 requires some complex integrations >> * Details of it can be found here: http://www.webrtc.org/ >> >> 2. Use the WebRTC Ericsson Stack >> * Less mature but also less heavy >> * Supports natively H.264, which is a more performant codec for your use case. >> * Details can be found here: http://www.openwebrtc.io/ >> >> Here, my choice would be option 1, but you may wish to perform a deeper analysis. >> >> >> For validating that you webcam works correctly with WebRTC, do the following: >> >> - Provide internet connectivity to the robot >> - Install chrome on it >> - Open this URL >> -- https://talky.io/ >> - Fill a string in the form (e.g. "aaa") and press the button. >> - Accept to share the webcam >> - The video should appear >> - Open another browser into another computer with Internet connectivity and a webcam >> - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) >> - Accept to share the webcam >> - You should have a video conference between the two browsers >> >> Best. >> >> >> ----------------------------------------------------------- >> 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 11/02/2015, a las 13:54, Antonini Roberto escribi?: >> >> >> >> >> Hi Luis >> As agreed, we start sending to you the characteristics of the robot we have here, that?s a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) >> The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). >> >> Let us know if this?s enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. >> Thank you. >> Davide and Roberto >> 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 Thu Feb 19 11:01:30 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 19 Feb 2015 10:01:30 +0000 Subject: [Fiware-robotics] R: Robot characteristics In-Reply-To: References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E5AA@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C20E92D@telmba003ba020.telecomitalia.local> Thank you Luis, having also hints about a preferable solutions for Kurento is useful because we are still in a definition phase for live demo. Just a note to clarify one of my assertion, obviously the robot is able communicate with external world, but we have to consider three independent channels for information exchange: ? one is carrying ROS messages and enable ROS services to exchange Commands and sensors data (this is based on ROS communication), and it operates through FIROS Robotics component and Context Broker GE; his is a sort of "Instructions plane". ? another is used for the Service Logic management (e.g. to create, delete ROS nodes and configure ROS service spaces), and operate with RCM Robotics component (able to communicate with FIROS); this is a sort of "Management Plane"; ? the last one is the communication of a media stream to a Kurento Client toward Kurento Media Server; this is a sort of "Media plane". All these three information channels should be able to send / receive information/data to one (at least) Web/Application servers but they are independent. Specifically, ROS communications between nodes in Robots and Servers (for commands and data) should be considered "isolated" and independent from a media stream channel toward the Application Server hosting Kurento client and to Kurento Server. This is not an issue for Kurento, but something we (Robotics Group) have to consider to define a consistent a functional architecture for the Robotics Live demo. We'll have to investigate if the Application Server used to host the demo application to Command and Manage Robots can be used also to host Kurento Client, if we decide to have the App server external to the Robot. Best, Gianmario Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 19 febbraio 2015 09:54 A: Bollano Gianmario Cc: Antonini Roberto; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi, Some comments inline El 18/02/2015, a las 12:41, Bollano Gianmario > escribi?: Hi Luis, I have found initially of documentation from the FIWARE pages and it was quite complex to understand where to get clear code and examples. Probably the catalog page it's not the simplest page to start with, because it provides lot - for me too many - links for Kurento server and Client at Kurento Github, at NPM, at Maven Central, Bower and Kurento FIWARE Forge Repository ... Really hard to understand which component may be needed and where to get them. Information at Kurento.org is definitely more helpful; without digging deep in the technical details, from the Tutorial it is clear there are three different "usage scenarios" , also represented in the picture in the introducing_kurento tutorial ("Kurento Api, Client and Protocol" section). In my understanding, these 3 scenario mapped to our environment becomes: 1. Robot equipped with Chrome + NodeJS + Bower + Kurento JS Client + Application Code. This allow to have Application server as localhost in the robot and to open the browser for transmitting video in the same environment. Having everything in the Robot allows to communicate directly with a Kurento media server. The Browser endpoint connects to Kurento server. 2. Robot with Chrome only, which connect to on external Linux App server with NodeJS + Bower + Kurento JS Client + Application Code (downloaded and launched in the Robot browser). 3. As 2, but working in Java EE App server and Java Kurento client instead of JS. I believe the scenario 3 beyond the purposes of the Robotics live demo because it requires larger development effort and Java EE knowledge, however the Robotics developers may better evaluate this issue. The scenario 1. is preferable but we have to check if the Robot has the requirements to host all the Application Server software. I think you should go to scenario 2 or 3 and use an Application Server external to the robot. You can base the Application Server on Java EE or in Node.js, but definitely you need that Application Server to be external to the robot. Otherwise, you limit too much the use cases you may be supporting. We can discuss about this slowly if you want, but putting the AS in the robot is not the best design decision and there are strong reasons for it: - You won't be able to put the robot behind a NAT easily and connect from external applications (browsers) to the Application Server. - You will be putting CPU overhead in the robot - You will make the application too sensitive to robot network access. IMHO, you should go to option 2 or 3 and put in a FIWARE Lab node both, the Kurento server and the application server. You have may examples on doing it in Kurento.org tutorials. It wont' hurt you and you'll benefit from lots of advantages. The scenario 2 move the Application server outside the Robot and is less resource consuming for the Robot, but it involves further issues concerning communication between Robot and the Application server. You will just need to put the AS into a well known IP. Robotics GE adopts ROS environment which already consider a Robot Entity composed of nodes communicating in their way, same of them placed externally to the Robot (in a service Space which runs also in an external server). Moreover, our demo also use an external application server to send and display Robots commands, which interact with Context broker on one side and calls Robotics management APIs, but the Robot ROS environment (between ROS nodes) is isolated (also for Robotics security reasons) and cannot communicate with that external server. This issue should be better investigated because it may be important also for the scenario 1. If you cannot communicate with the external world you won't be able to see any video. The talk.io test may be come handy to test if WebRTC support from Chrome is working fine in the Robot, but does not require Kurento. The next steps will need to use a configuration including a Kurento Client (thus using Kurento protocol) and we'll need an instance of Kurento Server. Do you think it would be possible in the next phase to use a FI-LAB instance of Kurento to make some test with a Kurento Client? The solution of installing a local Kurento Server wouldn't probably simplify the communication issues with the Robotics platform, and probably would have less impact for Robotics and Kurento GEs demo. For the same reason we are using an external instance of the Context Broker: one of purpose of the live demo is to show interoperability of different FIWARE GEs in the Cloud. We are having a lot of problems with the FIWARE Lab. You can launch a Kurento server there and it works sometimes ... but sometimes it doesn't. We are still defining the Live demo, and at this stage it's not yet completely defined if and how exploiting the Kurento advanced features (beyond the basic video streaming supported by WebRTC). One idea might be working on some pattern or face detection when we use an Infrared camera. This solution would obviously imply the usage of Kurento equipped with some processing function among the ones already developed and already made available with Kurento (no need to have ad-hoc functions, but use of one of the Kurento processing components available). This is my general understanding and overview; all the other Robotics in the mailing list guys have deeper knowledge of the technical details and specifications of the Robotics Platforms GE components, they can arise more precise proposals or questions. Thank you, Gianmario Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: marted? 17 febbraio 2015 19:05 A: Bollano Gianmario Cc: Antonini Roberto; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Answers inline El 17/02/2015, a las 16:47, Bollano Gianmario > escribi?: Hi Luis, I think the questions arisen from Roberto and Davide can be summarized as: - Assuming to use a chrome browser, do we need a specific "Kurento Client" code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? The short answer is no. The long answer is that it depend on the architecture of your application. Probably, the simplest way for you to start working with kurento is following one of these tutorials: 1. Read first this and pay attention to the role of the application server (node or java based) http://www.kurento.org/docs/current/introducing_kurento.html After that, my opinion is that you should go to an architecture based on application server, so the browser does not speak directly with Kurento Media Server. You can find several tutorials of applications basing on such architecture. For example In java http://www.kurento.org/docs/current/tutorials/java/tutorial-1-helloworld.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-1-helloworld.html For making something more useful (e.g. making possible to robot to broadcast the video to a number of receivers), take a look to these tutorials: In java http://www.kurento.org/docs/current/tutorials/java/tutorial-3-one2many.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? Install one of the tutorials listed above and open them from the robot using a chrome browser. That should do the job. The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. If you were able to execute the simple peer-to-peer example I provided in a previous mail (basing on talky.io for example), then you won't have problems for interoperating with Kurento. This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. Again, you can check this with the basic peer-to-peer example based on talky.io without requiring Kurento at all for it. Best. 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? 17 febbraio 2015 16:20 A: Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Roberto, Please, take into consideration the following information for having an understanding on how to use Kurento: Kurento is: - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) Kurento is not: - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) Hence, in your architecture, you need two ingredients: - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols - A WebRTC server, for receiving the stream and "do things" with that stream. The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. I hope this clarifies the issues. Best. El 17/02/2015, a las 16:12, Antonini Roberto > escribi?: Hi Luis, thanks for having promptly answered my e-mail . Amongst the solutions you've proposed, it's not clear (at least to me) which of these are using KURENTO GE. I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. Anyway, just to better clarify what we meant to do: On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. BR Roberto and Davide Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 12 febbraio 2015 16:29 A: Antonini Roberto Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org Oggetto: Re: Robot characteristics Hi Roberto, basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. 1. Use the WebRTC Google stack. * This is the most mature WebRTC stack providing lots of advanced features * It's the stack used by Chrome * Can be compiled and used independently on the browser (with some work) * Only supports VP8 codec. Supporting H264 requires some complex integrations * Details of it can be found here: http://www.webrtc.org/ 2. Use the WebRTC Ericsson Stack * Less mature but also less heavy * Supports natively H.264, which is a more performant codec for your use case. * Details can be found here: http://www.openwebrtc.io/ Here, my choice would be option 1, but you may wish to perform a deeper analysis. For validating that you webcam works correctly with WebRTC, do the following: - Provide internet connectivity to the robot - Install chrome on it - Open this URL -- https://talky.io/ - Fill a string in the form (e.g. "aaa") and press the button. - Accept to share the webcam - The video should appear - Open another browser into another computer with Internet connectivity and a webcam - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) - Accept to share the webcam - You should have a video conference between the two browsers Best. ----------------------------------------------------------- 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 11/02/2015, a las 13:54, Antonini Roberto > escribi?: Hi Luis As agreed, we start sending to you the characteristics of the robot we have here, that's a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). Let us know if this's enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. Thank you. Davide and Roberto 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 Thu Feb 19 11:06:38 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 19 Feb 2015 10:06:38 +0000 Subject: [Fiware-robotics] R: Robot characteristics In-Reply-To: <80AAE603-4375-44AA-A0CC-8991833B65C4@urjc.es> References: <246C286B275B1B46A255552CD236DA863BCDFA34@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA863BCE0AFA@TELMBB001BA020.telecomitalia.local> <907B077F-BF82-4D66-9283-44639F0F0946@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E083@telmba003ba020.telecomitalia.local> <3AA620B7-70E5-4517-8542-71B858AD5678@urjc.es> <7E649CBD84A947498203DAF8F098B1F62C20E5AA@telmba003ba020.telecomitalia.local> <80AAE603-4375-44AA-A0CC-8991833B65C4@urjc.es> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C20E942@telmba003ba020.telecomitalia.local> Thank you Inigo and Luis, this kind of test and feedback is useful and effective. Gianmario Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 19 febbraio 2015 10:28 A: I?igo Gonzalez Cc: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi, Answers inline El 19/02/2015, a las 09:56, I?igo Gonzalez > escribi?: Hi everyone, as we are talking about doing the live demo with Kurento we think its interesting and useful for us using it for image processing. We have deployed the versions 5.0.33 and 5.0.4 in fiware to test the tutorials that are available in https://github.com/Kurento/kurento-tutorial-js You should upgrade to KMS v5.1.0, otherwise you wont' be able to install any module. We have only been able to send video via Kurento, we cannot do any image processing (that we think that is a very interesting feature for robotics area), so we put here the problems we have found so Luis can help us or put us in touch with someone who could help us with them, or maybe we can talk via skype or hangout to be more efficient: * The bower files use adapter.js with kurento-alvar branch, but it doesn't exist, so we used master branch and in the html dependencies we have changed "bower_components/adapter.js/samples/web/js/adapter.js" with "bower_components/adapter.js/adapter.js" FIXED This was caused by Google guys, who moved the adapter.js location in github unexpectedly. The fix is ready in our develop branch. * The kurento-crowddetector show us an error: 'Error: Unexpected error while processing method: Factory not found {code: -32603, stack: (...), message: "Unexpected error while processing method: Factory not found"}' I supposed that is related with something that is not installed, I have researched but I didn't find anything about this. You need to install the module. In FIWARE Lab it's not installed. You just need to execute (you need our ppa repo to be configured, of course) sudo apt-get install kms-crowddetector * The kurento-faceoverlay-generator doesn't add any overlay on the video and doesn't give us any error. We'd need to check the logs. Probably you are not specifying the location of the overlayed image appropriately. You need to specify it using an URL. Example: - file:///tmp/myimage.png - http://mysite.com/myimage.png * The kurento-chroma doesn't show anything, but also we don't understand how it works, it tooks the upper left corner to do something but we don't know what. You need to have a chroma (a background with a single color) and calibrate the filter for that color. * The kurento-background give us many errors: * Bower doesn't know where kurento-module-backgroundextractor.js is I have search it on internet and finally I have been able to extract it from a jar file I found in a maven repository. FIXED * After fixing that I have tried the demo but it gives me the same error as in the crowdetector (Factory not found) * It also gives me another error: 'TypeError: Cannot read property 'processSdpAnswer' of null {stack: (...), message: "Cannot read property 'processSdpAnswer' of null"}' And I don't know how to continue. This filter is experimental and very unstable. Please do not use it. I wanted to do some pull request fixing the html, bower and js issues I have found, but first of all I want to be sure that I can make the examples work. So any help would be great. This is already fixed in development branch. Regards, I?igo On 18/02/15 12:41, Bollano Gianmario wrote: Hi Luis, I have found initially of documentation from the FIWARE pages and it was quite complex to understand where to get clear code and examples. Probably the catalog page it's not the simplest page to start with, because it provides lot - for me too many - links for Kurento server and Client at Kurento Github, at NPM, at Maven Central, Bower and Kurento FIWARE Forge Repository ... Really hard to understand which component may be needed and where to get them. Information at Kurento.org is definitely more helpful; without digging deep in the technical details, from the Tutorial it is clear there are three different "usage scenarios" , also represented in the picture in the introducing_kurento tutorial ("Kurento Api, Client and Protocol" section). In my understanding, these 3 scenario mapped to our environment becomes: 1. Robot equipped with Chrome + NodeJS + Bower + Kurento JS Client + Application Code. This allow to have Application server as localhost in the robot and to open the browser for transmitting video in the same environment. Having everything in the Robot allows to communicate directly with a Kurento media server. The Browser endpoint connects to Kurento server. 2. Robot with Chrome only, which connect to on external Linux App server with NodeJS + Bower + Kurento JS Client + Application Code (downloaded and launched in the Robot browser). 3. As 2, but working in Java EE App server and Java Kurento client instead of JS. I believe the scenario 3 beyond the purposes of the Robotics live demo because it requires larger development effort and Java EE knowledge, however the Robotics developers may better evaluate this issue. The scenario 1. is preferable but we have to check if the Robot has the requirements to host all the Application Server software. The scenario 2 move the Application server outside the Robot and is less resource consuming for the Robot, but it involves further issues concerning communication between Robot and the Application server. Robotics GE adopts ROS environment which already consider a Robot Entity composed of nodes communicating in their way, same of them placed externally to the Robot (in a service Space which runs also in an external server). Moreover, our demo also use an external application server to send and display Robots commands, which interact with Context broker on one side and calls Robotics management APIs, but the Robot ROS environment (between ROS nodes) is isolated (also for Robotics security reasons) and cannot communicate with that external server. This issue should be better investigated because it may be important also for the scenario 1. The talk.io test may be come handy to test if WebRTC support from Chrome is working fine in the Robot, but does not require Kurento. The next steps will need to use a configuration including a Kurento Client (thus using Kurento protocol) and we'll need an instance of Kurento Server. Do you think it would be possible in the next phase to use a FI-LAB instance of Kurento to make some test with a Kurento Client? The solution of installing a local Kurento Server wouldn't probably simplify the communication issues with the Robotics platform, and probably would have less impact for Robotics and Kurento GEs demo. For the same reason we are using an external instance of the Context Broker: one of purpose of the live demo is to show interoperability of different FIWARE GEs in the Cloud. We are still defining the Live demo, and at this stage it's not yet completely defined if and how exploiting the Kurento advanced features (beyond the basic video streaming supported by WebRTC). One idea might be working on some pattern or face detection when we use an Infrared camera. This solution would obviously imply the usage of Kurento equipped with some processing function among the ones already developed and already made available with Kurento (no need to have ad-hoc functions, but use of one of the Kurento processing components available). This is my general understanding and overview; all the other Robotics in the mailing list guys have deeper knowledge of the technical details and specifications of the Robotics Platforms GE components, they can arise more precise proposals or questions. Thank you, Gianmario Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: marted? 17 febbraio 2015 19:05 A: Bollano Gianmario Cc: Antonini Roberto; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Answers inline El 17/02/2015, a las 16:47, Bollano Gianmario > escribi?: Hi Luis, I think the questions arisen from Roberto and Davide can be summarized as: - Assuming to use a chrome browser, do we need a specific "Kurento Client" code (e.g. a JS library for Kurento APIs) to call a Kurento function and transmit a video streaming to the media server? The short answer is no. The long answer is that it depend on the architecture of your application. Probably, the simplest way for you to start working with kurento is following one of these tutorials: 1. Read first this and pay attention to the role of the application server (node or java based) http://www.kurento.org/docs/current/introducing_kurento.html After that, my opinion is that you should go to an architecture based on application server, so the browser does not speak directly with Kurento Media Server. You can find several tutorials of applications basing on such architecture. For example In java http://www.kurento.org/docs/current/tutorials/java/tutorial-1-helloworld.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-1-helloworld.html For making something more useful (e.g. making possible to robot to broadcast the video to a number of receivers), take a look to these tutorials: In java http://www.kurento.org/docs/current/tutorials/java/tutorial-3-one2many.html In JavaScript (for Node.js) http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html - Would it be possible to have a simple code snipped to try to transmit a video stream to Kurento and use it to check if it works immediately in our robot (equipped with chrome and linux)? Install one of the tutorials listed above and open them from the robot using a chrome browser. That should do the job. The point is not WebRTC, I think the different options for WebRTC clients are clear now, but instead identifying the simplest code (Kurento client library, snippet code, etc) required to make a quick test and transmit a video stream from a Robot to a real Kurento media server. If you were able to execute the simple peer-to-peer example I provided in a previous mail (basing on talky.io for example), then you won't have problems for interoperating with Kurento. This will help to see if the Robot environment is sufficiently compliant with WebRTC and Kurento requirements, and the robot have enough resources (CPU, memory) to allow a realtime transmission of a video stream from a webcam. Again, you can check this with the basic peer-to-peer example based on talky.io without requiring Kurento at all for it. Best. 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? 17 febbraio 2015 16:20 A: Antonini Roberto Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robot characteristics Hi Roberto, Please, take into consideration the following information for having an understanding on how to use Kurento: Kurento is: - A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc) - A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams) Kurento is not: - A WebRTC client (it cannot "open a webcam" and send the stream to a remote party) Hence, in your architecture, you need two ingredients: - A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols - A WebRTC server, for receiving the stream and "do things" with that stream. The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it. The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client. I hope this clarifies the issues. Best. El 17/02/2015, a las 16:12, Antonini Roberto > escribi?: Hi Luis, thanks for having promptly answered my e-mail . Amongst the solutions you've proposed, it's not clear (at least to me) which of these are using KURENTO GE. I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO. Anyway, just to better clarify what we meant to do: On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible? Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well. BR Roberto and Davide Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: gioved? 12 febbraio 2015 16:29 A: Antonini Roberto Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; I?igo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org Oggetto: Re: Robot characteristics Hi Roberto, basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options. 1. Use the WebRTC Google stack. * This is the most mature WebRTC stack providing lots of advanced features * It's the stack used by Chrome * Can be compiled and used independently on the browser (with some work) * Only supports VP8 codec. Supporting H264 requires some complex integrations * Details of it can be found here: http://www.webrtc.org/ 2. Use the WebRTC Ericsson Stack * Less mature but also less heavy * Supports natively H.264, which is a more performant codec for your use case. * Details can be found here: http://www.openwebrtc.io/ Here, my choice would be option 1, but you may wish to perform a deeper analysis. For validating that you webcam works correctly with WebRTC, do the following: - Provide internet connectivity to the robot - Install chrome on it - Open this URL -- https://talky.io/ - Fill a string in the form (e.g. "aaa") and press the button. - Accept to share the webcam - The video should appear - Open another browser into another computer with Internet connectivity and a webcam - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form) - Accept to share the webcam - You should have a video conference between the two browsers Best. ----------------------------------------------------------- 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 11/02/2015, a las 13:54, Antonini Roberto > escribi?: Hi Luis As agreed, we start sending to you the characteristics of the robot we have here, that's a turtlebot2 and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/)) The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270). Let us know if this's enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication. Thank you. Davide and Roberto 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: