From jjaime at ikergune.com Mon Jun 1 14:03:57 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Mon, 1 Jun 2015 14:03:57 +0200 Subject: [Fiware-robotics] Robotics GE porst management problem Message-ID: Hi Thomas and Giovanni, We are stuck on a problem with the port management in the Robotics GE and need some help from the architect. We've elaborated a document (as much agnostic as we could) explaining the problem and providing three proposals: https://docs.google.com/document/d/1ReZKrIxWN5gQLMPsUbmYMqvWiptuAj0AxGr138SAkzU/edit Thank you very much, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From jjaime at ikergune.com Tue Jun 2 10:12:17 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 2 Jun 2015 10:12:17 +0200 Subject: [Fiware-robotics] Robotics call Message-ID: Hi all, Are you ready for the call? We are waiting for you. BR -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From jjaime at ikergune.com Tue Jun 2 10:19:38 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 2 Jun 2015 10:19:38 +0200 Subject: [Fiware-robotics] Robotics call References: Message-ID: Hi all, We've just found that today is Festa della Repubblica in Italy, see you next Tuesday. BR, Pepe On 02/06/15 10:12, Jose Jaime Ariza wrote: > Hi all, > > Are you ready for the call? We are waiting for you. > > BR > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From toff at zhaw.ch Tue Jun 2 10:33:22 2015 From: toff at zhaw.ch (Toffetti Carughi Giovanni (toff)) Date: Tue, 2 Jun 2015 08:33:22 +0000 Subject: [Fiware-robotics] Robotics GE porst management problem References: Message-ID: Aupa Pepe, there's something I don't really understand. FIROS has to register to the CB once is up and running no? Isn't that the moment to communicate the port? Sorry for the stupid question, there's clearly something I am not seeing in the picture. We can have a chat about it on skype or hangouts if you want to. My google handle is: giovanni.toffetti at gmail.com You can find me by name on skype. Cheers, g ---- Giovanni Toffetti, Ph.D. toff at zhaw.ch InIT Cloud Computing Lab - ICCLab http://blog.zhaw.ch/icclab Institute of Applied Information Technology - InIT School of Engineering Zurich University of Applied Sciences - ZHAW Phone: +41 58 934 6964 On 01/06/2015 14:04, Jose Jaime Ariza wrote: > Hi Thomas and Giovanni, > > We are stuck on a problem with the port management in the Robotics GE > and need some help from the architect. > > We've elaborated a document (as much agnostic as we could) explaining > the problem and providing three proposals: > https://docs.google.com/document/d/1ReZKrIxWN5gQLMPsUbmYMqvWiptuAj0AxGr138SAkzU/edit > > Thank you very much, > Pepe > From pierangelo.garino at telecomitalia.it Tue Jun 2 11:06:04 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 2 Jun 2015 09:06:04 +0000 Subject: [Fiware-robotics] R: Re: Robotics call In-Reply-To: References: , Message-ID: Hi All, Sorry I was convinced I told everybody about national holiday in Italy today. Apparently I missed the i2nd and robotics people, apologies. Talk to you on Thursday. Pier Inviato da smartphone Sony Xperia? ---- Jose Jaime Ariza ha scritto ---- Hi all, We've just found that today is Festa della Repubblica in Italy, see you next Tuesday. BR, Pepe On 02/06/15 10:12, Jose Jaime Ariza wrote: > Hi all, > > Are you ready for the call? We are waiting for you. > > BR > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Tue Jun 2 12:30:44 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 2 Jun 2015 12:30:44 +0200 Subject: [Fiware-robotics] Robotics GE porst management problem References: Message-ID: Hi Giovanni, The problem is not when to communicate the port, but how to guess which port to communicate. Today is holiday in Italy so lets wait for tomorrow in order to schedule the call. BR, Pepe On 02/06/15 10:33, Toffetti Carughi Giovanni (toff) wrote: > Aupa Pepe, > > there's something I don't really understand. > > FIROS has to register to the CB once is up and running no? > Isn't that the moment to communicate the port? > > Sorry for the stupid question, there's clearly something I am not seeing > in the picture. > > We can have a chat about it on skype or hangouts if you want to. > My google handle is: giovanni.toffetti at gmail.com > You can find me by name on skype. > > Cheers, > > g > > ---- > Giovanni Toffetti, Ph.D. toff at zhaw.ch > InIT Cloud Computing Lab - ICCLab http://blog.zhaw.ch/icclab > Institute of Applied Information Technology - InIT > School of Engineering > Zurich University of Applied Sciences - ZHAW > Phone: +41 58 934 6964 > > On 01/06/2015 14:04, Jose Jaime Ariza wrote: >> Hi Thomas and Giovanni, >> >> We are stuck on a problem with the port management in the Robotics GE >> and need some help from the architect. >> >> We've elaborated a document (as much agnostic as we could) explaining >> the problem and providing three proposals: >> https://docs.google.com/document/d/1ReZKrIxWN5gQLMPsUbmYMqvWiptuAj0AxGr138SAkzU/edit >> >> Thank you very much, >> Pepe >> > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From toff at zhaw.ch Thu Jun 4 14:33:26 2015 From: toff at zhaw.ch (Toffetti Carughi Giovanni (toff)) Date: Thu, 4 Jun 2015 12:33:26 +0000 Subject: [Fiware-robotics] Link to hangout Message-ID: In case it doesn't let you open the event, here's the link to the hangout. Please let me know if it doesn't work for you. https://plus.google.com/hangouts/_/calendar/aXBhazVrYXBsMGwwZDJmZzRqdHM0ZDFtNm9AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ.a4prdhmok34jmrfa0cabk7c9uo?authuser=0 Regards, g -- ---- Giovanni Toffetti, Ph.D. toff at zhaw.ch InIT Cloud Computing Lab - ICCLab http://blog.zhaw.ch/icclab Institute of Applied Information Technology - InIT School of Engineering Zurich University of Applied Sciences - ZHAW Phone: +41 58 934 6964 From toff at zhaw.ch Thu Jun 4 15:03:45 2015 From: toff at zhaw.ch (Toffetti Carughi Giovanni (toff)) Date: Thu, 4 Jun 2015 13:03:45 +0000 Subject: [Fiware-robotics] Another hangout Message-ID: Let's try this one: https://plus.google.com/hangouts/_/calendar/Z2lvdmFubmkudG9mZmV0dGlAZ21haWwuY29t.jqq7h37772qt24797haknu6i3o -- ---- Giovanni Toffetti, Ph.D. toff at zhaw.ch InIT Cloud Computing Lab - ICCLab http://blog.zhaw.ch/icclab Institute of Applied Information Technology - InIT School of Engineering Zurich University of Applied Sciences - ZHAW Phone: +41 58 934 6964 From gianmario.bollano at telecomitalia.it Thu Jun 4 15:06:37 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 4 Jun 2015 13:06:37 +0000 Subject: [Fiware-robotics] R: Link to hangout In-Reply-To: References: Message-ID: <7E649CBD84A947498203DAF8F098B1F63BFEEFA3@telmbb003ba020.telecomitalia.local> Hi, the link does not work for me because I cannot use hangouts behind my company firewall, thus I'm using a different e-mail address with hangout on the smartphone: bgianm at gmail.com The link below likely expects a different address and tell I do not belong to the company expected. Could you please invite me at the address bgianm at gmail.com ? Thank you, Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Toffetti Carughi Giovanni (toff) Inviato: gioved? 4 giugno 2015 14:33 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Link to hangout In case it doesn't let you open the event, here's the link to the hangout. Please let me know if it doesn't work for you. https://plus.google.com/hangouts/_/calendar/aXBhazVrYXBsMGwwZDJmZzRqdHM0ZDFtNm9AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ.a4prdhmok34jmrfa0cabk7c9uo?authuser=0 Regards, g -- ---- Giovanni Toffetti, Ph.D. toff at zhaw.ch InIT Cloud Computing Lab - ICCLab http://blog.zhaw.ch/icclab Institute of Applied Information Technology - InIT School of Engineering Zurich University of Applied Sciences - ZHAW Phone: +41 58 934 6964 _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. From giovanni.toffetti at gmail.com Thu Jun 4 14:29:11 2015 From: giovanni.toffetti at gmail.com (giovanni.toffetti at gmail.com) Date: Thu, 04 Jun 2015 12:29:11 +0000 Subject: [Fiware-robotics] Invitation: Robotics architecture call @ Thu Jun 4, 2015 15:00 - 16:00 (Giovanni Toffetti [ZHAW]) Message-ID: <001a11361ceea6589c0517b0525f@google.com> You have been invited to the following event. Title: Robotics architecture call When: Thu Jun 4, 2015 15:00 - 16:00 Zurich Video call: Join video call Calendar: Giovanni Toffetti [ZHAW] Who: * Giovanni Toffetti - creator * toff at zhaw.ch * pierangelo.garino at telecomitalia.it * fiware-robotics at lists.fi-ware.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=YTRwcmRobW9rMzRqbXJmYTBjYWJrN2M5dW8gZml3YXJlLXJvYm90aWNzQGxpc3RzLmZpLXdhcmUub3Jn&tok=NTIjaXBhazVrYXBsMGwwZDJmZzRqdHM0ZDFtNm9AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWNhZTc0YzkzYjQ0NWNhZWUxNjQwNmYxODg1OTc1MzY3ZmRjNjJlOGY&ctz=Europe/Zurich&hl=en Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account fiware-robotics at lists.fi-ware.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1492 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1529 bytes Desc: not available URL: From davide.colombatto at telecomitalia.it Fri Jun 5 12:32:51 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 5 Jun 2015 10:32:51 +0000 Subject: [Fiware-robotics] Sprint Planning 4.3.3 Message-ID: <069906BED271EB4A883BD9578DCDD3540CB4A637@TELMBB006RM001.telecomitalia.local> Hi all, Do you have completed the planning of this Sprint (4.3.3) so we can close the common issue FIWARE.WorkItem.I2ND.Robotics.Agile.Sprint-433.Planning? Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Fri Jun 5 12:59:50 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 5 Jun 2015 12:59:50 +0200 Subject: [Fiware-robotics] Sprint Planning 4.3.3 References: <069906BED271EB4A883BD9578DCDD3540CB4A637@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, We have completed our part of the planning. Thank you very much, Pepe. On 05/06/15 12:32, Colombatto Davide wrote: Hi all, Do you have completed the planning of this Sprint (4.3.3) so we can close the common issue FIWARE.WorkItem.I2ND.Robotics.Agile.Sprint-433.Planning? Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- 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 Jun 5 18:41:08 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 5 Jun 2015 16:41:08 +0000 Subject: [Fiware-robotics] Multiple FIROS instances - Range of ports Message-ID: <069906BED271EB4A883BD9578DCDD3540CB4C9E3@TELMBB006RM001.telecomitalia.local> Hi ET guys, As a result of the call of yesterday with G. Toffetti we agreed the range of ports to open in the NAT/Firewall is in charge of the "FIWARE User" and so it can only be a requirement of the GE and not a task do at GE-level. Hence the proposal 1 and the proposal 3 of the link https://docs.google.com/document/d/1ReZKrIxWN5gQLMPsUbmYMqvWiptuAj0AxGr138SAkzU/edit should be enough to manage the range of ports related to multiple FIROS instances. Considering that, at the link above we have slightly extended the proposal 3. Let we know what do you think about it. BR Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Mon Jun 8 14:00:50 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Mon, 8 Jun 2015 14:00:50 +0200 Subject: [Fiware-robotics] Multiple FIROS instances - Range of ports References: <069906BED271EB4A883BD9578DCDD3540CB4C9E3@TELMBB006RM001.telecomitalia.local> Message-ID: Hi Davide, It looks perfect for us, just a comment: since we relay on the network configuration I won't perform context-broker ping. BR Pepe On 05/06/15 18:41, Colombatto Davide wrote: Hi ET guys, As a result of the call of yesterday with G. Toffetti we agreed the range of ports to open in the NAT/Firewall is in charge of the ?FIWARE User? and so it can only be a requirement of the GE and not a task do at GE-level. Hence the proposal 1 and the proposal 3 of the link https://docs.google.com/document/d/1ReZKrIxWN5gQLMPsUbmYMqvWiptuAj0AxGr138SAkzU/edit should be enough to manage the range of ports related to multiple FIROS instances. Considering that, at the link above we have slightly extended the proposal 3. Let we know what do you think about it. BR Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Tue Jun 9 10:00:40 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 9 Jun 2015 08:00:40 +0000 Subject: [Fiware-robotics] Robotics call Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE0AFA0@telmba003ba020.telecomitalia.local> Hi all, we have the have the Robotics call at 10.00 with hangout. Robotics Call Minutes: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2511 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Tue Jun 9 11:42:11 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 9 Jun 2015 11:42:11 +0200 Subject: [Fiware-robotics] R: Robotics-Kurento call minutes References: <7E649CBD84A947498203DAF8F098B1F63BFDA1AE@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D558F8@TELMBA001BA020.telecomitalia.local> Message-ID: Hi Luis, We are gathering VM requirements for the live demo. I've found that the StreamOriented blueprint creates a tiny VM, do you think it we'll be enough for us or you recommend different VM size or number of VMs? Thank you very much, Pepe On 27/05/15 09:42, Antonini Roberto wrote: Just a quick comment inline (in red), for what concerns the first issues. R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 26 maggio 2015 16:31 A: fiware-robotics at lists.fi-ware.org; luis.lopez at urjc.es Oggetto: [Fiware-robotics] Robotics-Kurento call minutes Hi all, please find a short summary of the Robotics-Kurento call. Robotics - Kurento call: ? We should define what are the requirements, e.g. for latency: are we ok with 1/2s latency in our application? Do we need to broadcast the video, or is it used by an operator only? If we use camera sight as a feedback to move the robot, then 1 or 2 seconds are enough, to operate for that latency I would have to slow down robot ? * For the demo purposes, probably the former is more relevant (we can show to many people the robots moving) I would set two different profiles: ? The operator, who needs fast feedback from the camera (less than 0.5s) ? The viewer(s), who accesses a streaming portal, where above video is usually recasted and codified in different formats The first is the easiest, but if you try to access it as if you were a viewer (second case) you would have scalability issues, I suppose. ? Both Kurento blueprints or images can be used on FIWARE Lab * Suggested to use last image available for Kurento in FIWARE LAB ? Quick instructions: * Open all UDP ports. * Check if Kurento works in a browser. * If it doesn?t work (NAT must allow realtime traffic) it may require to install a Turn server in FIWARE lab. In this case, ask further instructions to Luis. ? Different kind of applications available from Kurento repository. The FIWARE Lab image has already several application installed (based on Tomcat on Springboot) then it should be a better solution than blueprint, which doesn't have any application. Applications are open source, so they could be used to derive the required application for our demo ? Application server can be on same machine as KMS or not; in the latter case it is required to open port 8888. Ports for Application server are 80, 8080 etc (HTTP). ? 2 Wirecloud widgets available for Kurento: one used for IP camera stream (not useful if using webkit/chrome), the second is for meeting communication. Perhaps the robot demo could be based on the latter. It is however better to talk to Wirecloud guys about this. Luis, I also enclose below the link with the slide of the configuration of Robotics GE used in the tests with Kurento (I apologize, I sent the link to many people but I missed your e-mail): https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit?usp=sharing Best, Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From luis.lopez at urjc.es Tue Jun 9 12:50:50 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Tue, 9 Jun 2015 12:50:50 +0200 Subject: [Fiware-robotics] R: Robotics-Kurento call minutes In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F63BFDA1AE@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D558F8@TELMBA001BA020.telecomitalia.local> Message-ID: <0B616D87-C5D5-4B1B-97B2-CB6916E2C7E1@urjc.es> Hi, With a tiny you should be able to stream the flow between the robot and the controller. However, if you want to have several viewers or if you want to record the stream, you'll need to use a more powerful machine: the more CPU you add, the higher the scalability you'll reach ... 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 09/06/2015, a las 11:42, Jose Jaime Ariza escribi?: > Hi Luis, > > We are gathering VM requirements for the live demo. I've found that the StreamOriented blueprint creates a tiny VM, do you think it we'll be enough for us or you recommend different VM size or number of VMs? > > Thank you very much, > Pepe > > On 27/05/15 09:42, Antonini Roberto wrote: >> Just a quick comment inline (in red), for what concerns the first issues. >> R >> >> Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario >> Inviato: marted? 26 maggio 2015 16:31 >> A: fiware-robotics at lists.fi-ware.org; luis.lopez at urjc.es >> Oggetto: [Fiware-robotics] Robotics-Kurento call minutes >> >> Hi all, >> please find a short summary of the Robotics-Kurento call. >> >> Robotics - Kurento call: >> ? We should define what are the requirements, e.g. for latency: are we ok with 1/2s latency in our application? Do we need to broadcast the video, or is it used by an operator only? >> If we use camera sight as a feedback to move the robot, then 1 or 2 seconds are enough, to operate for that latency I would have to slow down robot ? >> For the demo purposes, probably the former is more relevant (we can show to many people the robots moving) >> I would set two different profiles: >> ? The operator, who needs fast feedback from the camera (less than 0.5s) >> ? The viewer(s), who accesses a streaming portal, where above video is usually recasted and codified in different formats >> The first is the easiest, but if you try to access it as if you were a viewer (second case) you would have scalability issues, I suppose. >> >> >> ? Both Kurento blueprints or images can be used on FIWARE Lab >> Suggested to use last image available for Kurento in FIWARE LAB >> ? Quick instructions: >> Open all UDP ports. >> Check if Kurento works in a browser. >> If it doesn?t work (NAT must allow realtime traffic) it may require to install a Turn server in FIWARE lab. In this case, ask further instructions to Luis. >> ? Different kind of applications available from Kurento repository. The FIWARE Lab image has already several application installed (based on Tomcat on Springboot) then it should be a better solution than blueprint, which doesn't have any application. Applications are open source, so they could be used to derive the required application for our demo >> ? Application server can be on same machine as KMS or not; in the latter case it is required to open port 8888. Ports for Application server are 80, 8080 etc (HTTP). >> ? 2 Wirecloud widgets available for Kurento: one used for IP camera stream (not useful if using webkit/chrome), the second is for meeting communication. Perhaps the robot demo could be based on the latter. It is however better to talk to Wirecloud guys about this. >> >> Luis, I also enclose below the link with the slide of the configuration of Robotics GE used in the tests with Kurento (I apologize, I sent the link to many people but I missed your e-mail): >> https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit?usp=sharing >> >> >> Best, >> Gianmario >> >> ------------------------------------------------------------------------------------ >> Telecom Italia >> Gianmario Bollano >> Innovation - Mobile Devices & Sim Applications >> Via Reiss Romoli, n? 274 >> Cap 10151 Torino >> Phone 011 228 7103 >> Cell Phone 3316015048 >> >> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. >> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. >> >> Rispetta l'ambiente. Non stampare questa mail se non ? necessario. >> > > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Tue Jun 9 15:33:51 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 9 Jun 2015 13:33:51 +0000 Subject: [Fiware-robotics] Architecture for Robotics Live demo Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE0D20D@telmba003ba020.telecomitalia.local> Hi All, I've prepared a quick draft of the architecture for the Robotics Live Demo, you can find it enclosed it to this e-mail. I've shown two Robots to consider the more generic case with more FIROS instances. In it you'll find also an hypothesis for VMs and their size (3 VM); others are obviously possible: if we ask less VMs, we can pick larger ones. I would ask you to upload the slide in a shared document and I encourage you to edit it, fix errors and add any missing detail. For instance, I've imagined to have a single Application Server and I've divided the Apps conceptually, but likely some of them are grouped, such as Configuration and Control of the Robots. Also, it's not yet fully clear how Wirecloud GE is connected and related to the App server. Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Robotics Live Demo.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 112156 bytes Desc: Robotics Live Demo.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From roberto1.antonini at telecomitalia.it Tue Jun 9 16:25:48 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Tue, 9 Jun 2015 14:25:48 +0000 Subject: [Fiware-robotics] R: Architecture for Robotics Live demo In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE0D20D@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE0D20D@telmba003ba020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8643D6BA1C@TELMBB001BA020.telecomitalia.local> Hi all, before modifying shared slides, I need to clarify the some points about the architecture of at least KURENTO and WIRECLOUD. ? For what concerns KURENTO it seemed that the components were the Kurent Application Server (KAS) and the Kurento Media Server (KMS), besides client to place at end part, so you place only KMS and therefore we should also place the KAS somewhere, Is it necessary? If so, where do we place it? ? The Application Server you place in the slide, if I understand well, it is the front end of Wirecloud GE, isn't it? If so I would preferably place it on CB VM (VM2 in the slide), otherwise we could have some troubles for what concerns the ports, for instance, the 80 port could be used by both AS and Robotics GE. BR Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 9 giugno 2015 15:34 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Architecture for Robotics Live demo Hi All, I've prepared a quick draft of the architecture for the Robotics Live Demo, you can find it enclosed it to this e-mail. I've shown two Robots to consider the more generic case with more FIROS instances. In it you'll find also an hypothesis for VMs and their size (3 VM); others are obviously possible: if we ask less VMs, we can pick larger ones. I would ask you to upload the slide in a shared document and I encourage you to edit it, fix errors and add any missing detail. For instance, I've imagined to have a single Application Server and I've divided the Apps conceptually, but likely some of them are grouped, such as Configuration and Control of the Robots. Also, it's not yet fully clear how Wirecloud GE is connected and related to the App server. Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Tue Jun 9 17:17:13 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 9 Jun 2015 15:17:13 +0000 Subject: [Fiware-robotics] R: Architecture for Robotics Live demo In-Reply-To: <246C286B275B1B46A255552CD236DA8643D6BA1C@TELMBB001BA020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE0D20D@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D6BA1C@TELMBB001BA020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE0D2FD@telmba003ba020.telecomitalia.local> Hi all, then I've imported the slides also in a Google Powerpoint; I had to change a little the formatting. The link is: https://docs.google.com/presentation/d/1hDmIlCJY3mrrc_Rs2YoF0g1pdhiHzNcEAaPbP3VMJG4/edit?usp=sharing Personally I prefer editing in Microsoft office to Google docs, but the purpose is having a shared document , so anyone can edit or add slides or part of it. Concerning the question below, yes, there are other options. I think in previous setup (and in the test Davide made) we used KAS as App server with NodeJS and the JS Kurento client; Louis explained that KAS is actually any application server, which hosts the Kurento client. We can have this "KAS" together with Kurento Media server, same VM, but we also need to host the code for the second WebRTC endpoint: I've called Video RX (while Video TX is executed in the Chrome/Webkint on Robot) to show video in the user browser/widget. I'm not sure if also this code will require the Kurento Client ; if it does, we could host anything in the same Application server , and that's the hypothesis in my slide. But again, we can have different solutions, such as two application server, one for the main Robot Control app/widget and one for Kurento. Concerning the second point, in fact it wasn't clear to me how to access Application server and RDAPI. Having the application server on VM2 is a solution, or maybe on VM3 or both on VM2 and VM3. I HAVE updated the shared doc and added a second slide for this hypothesis. Gianmario Da: Antonini Roberto Inviato: marted? 9 giugno 2015 16:26 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: Architecture for Robotics Live demo Hi all, before modifying shared slides, I need to clarify the some points about the architecture of at least KURENTO and WIRECLOUD. ? For what concerns KURENTO it seemed that the components were the Kurent Application Server (KAS) and the Kurento Media Server (KMS), besides client to place at end part, so you place only KMS and therefore we should also place the KAS somewhere, Is it necessary? If so, where do we place it? ? The Application Server you place in the slide, if I understand well, it is the front end of Wirecloud GE, isn't it? If so I would preferably place it on CB VM (VM2 in the slide), otherwise we could have some troubles for what concerns the ports, for instance, the 80 port could be used by both AS and Robotics GE. BR Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 9 giugno 2015 15:34 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Architecture for Robotics Live demo Hi All, I've prepared a quick draft of the architecture for the Robotics Live Demo, you can find it enclosed it to this e-mail. I've shown two Robots to consider the more generic case with more FIROS instances. In it you'll find also an hypothesis for VMs and their size (3 VM); others are obviously possible: if we ask less VMs, we can pick larger ones. I would ask you to upload the slide in a shared document and I encourage you to edit it, fix errors and add any missing detail. For instance, I've imagined to have a single Application Server and I've divided the Apps conceptually, but likely some of them are grouped, such as Configuration and Control of the Robots. Also, it's not yet fully clear how Wirecloud GE is connected and related to the App server. Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Tue Jun 9 17:53:35 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 9 Jun 2015 15:53:35 +0000 Subject: [Fiware-robotics] R: Architecture for Robotics Live demo In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE0D2FD@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE0D20D@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D6BA1C@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE0D2FD@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE0D337@telmba003ba020.telecomitalia.local> Hi all, I've updated again the shared slides: now there are three slides for three different Hypothesis according suggestion from Roberto. Hyp 1 is the initial with AS on VM1 (may have troubles for port 80), Hyp 2 and Hyp 3 consider an AS on VM2 only or on VM2 and VM3. Please check them and feel free to edit, correct, add whatever is missing. Link to the document is the same: https://docs.google.com/presentation/d/1hDmIlCJY3mrrc_Rs2YoF0g1pdhiHzNcEAaPbP3VMJG4/edit?usp=sharing Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 9 giugno 2015 17:17 A: Antonini Roberto; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Architecture for Robotics Live demo Hi all, then I've imported the slides also in a Google Powerpoint; I had to change a little the formatting. The link is: https://docs.google.com/presentation/d/1hDmIlCJY3mrrc_Rs2YoF0g1pdhiHzNcEAaPbP3VMJG4/edit?usp=sharing Personally I prefer editing in Microsoft office to Google docs, but the purpose is having a shared document , so anyone can edit or add slides or part of it. Concerning the question below, yes, there are other options. I think in previous setup (and in the test Davide made) we used KAS as App server with NodeJS and the JS Kurento client; Louis explained that KAS is actually any application server, which hosts the Kurento client. We can have this "KAS" together with Kurento Media server, same VM, but we also need to host the code for the second WebRTC endpoint: I've called Video RX (while Video TX is executed in the Chrome/Webkint on Robot) to show video in the user browser/widget. I'm not sure if also this code will require the Kurento Client ; if it does, we could host anything in the same Application server , and that's the hypothesis in my slide. But again, we can have different solutions, such as two application server, one for the main Robot Control app/widget and one for Kurento. Concerning the second point, in fact it wasn't clear to me how to access Application server and RDAPI. Having the application server on VM2 is a solution, or maybe on VM3 or both on VM2 and VM3. I HAVE updated the shared doc and added a second slide for this hypothesis. Gianmario Da: Antonini Roberto Inviato: marted? 9 giugno 2015 16:26 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: Architecture for Robotics Live demo Hi all, before modifying shared slides, I need to clarify the some points about the architecture of at least KURENTO and WIRECLOUD. ? For what concerns KURENTO it seemed that the components were the Kurent Application Server (KAS) and the Kurento Media Server (KMS), besides client to place at end part, so you place only KMS and therefore we should also place the KAS somewhere, Is it necessary? If so, where do we place it? ? The Application Server you place in the slide, if I understand well, it is the front end of Wirecloud GE, isn't it? If so I would preferably place it on CB VM (VM2 in the slide), otherwise we could have some troubles for what concerns the ports, for instance, the 80 port could be used by both AS and Robotics GE. BR Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 9 giugno 2015 15:34 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Architecture for Robotics Live demo Hi All, I've prepared a quick draft of the architecture for the Robotics Live Demo, you can find it enclosed it to this e-mail. I've shown two Robots to consider the more generic case with more FIROS instances. In it you'll find also an hypothesis for VMs and their size (3 VM); others are obviously possible: if we ask less VMs, we can pick larger ones. I would ask you to upload the slide in a shared document and I encourage you to edit it, fix errors and add any missing detail. For instance, I've imagined to have a single Application Server and I've divided the Apps conceptually, but likely some of them are grouped, such as Configuration and Control of the Robots. Also, it's not yet fully clear how Wirecloud GE is connected and related to the App server. Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From jjaime at ikergune.com Tue Jun 9 18:16:51 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 9 Jun 2015 18:16:51 +0200 Subject: [Fiware-robotics] R: Robotics-Kurento call minutes References: <7E649CBD84A947498203DAF8F098B1F63BFDA1AE@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D558F8@TELMBA001BA020.telecomitalia.local> <0B616D87-C5D5-4B1B-97B2-CB6916E2C7E1@urjc.es> Message-ID: Hi, I suppose that we're going to have several viewers in the live demo. Pier, could we know how many of them? If this data is unknown I'd prefer to assign a large instance to Kurento. Thank you very much, Pepe On 09/06/15 12:50, Luis L?pez Fern?ndez wrote: Hi, With a tiny you should be able to stream the flow between the robot and the controller. However, if you want to have several viewers or if you want to record the stream, you'll need to use a more powerful machine: the more CPU you add, the higher the scalability you'll reach ... 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 09/06/2015, a las 11:42, Jose Jaime Ariza > escribi?: Hi Luis, We are gathering VM requirements for the live demo. I've found that the StreamOriented blueprint creates a tiny VM, do you think it we'll be enough for us or you recommend different VM size or number of VMs? Thank you very much, Pepe On 27/05/15 09:42, Antonini Roberto wrote: Just a quick comment inline (in red), for what concerns the first issues. R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 26 maggio 2015 16:31 A: fiware-robotics at lists.fi-ware.org; luis.lopez at urjc.es Oggetto: [Fiware-robotics] Robotics-Kurento call minutes Hi all, please find a short summary of the Robotics-Kurento call. Robotics - Kurento call: ? We should define what are the requirements, e.g. for latency: are we ok with 1/2s latency in our application? Do we need to broadcast the video, or is it used by an operator only? If we use camera sight as a feedback to move the robot, then 1 or 2 seconds are enough, to operate for that latency I would have to slow down robot ? * For the demo purposes, probably the former is more relevant (we can show to many people the robots moving) I would set two different profiles: ? The operator, who needs fast feedback from the camera (less than 0.5s) ? The viewer(s), who accesses a streaming portal, where above video is usually recasted and codified in different formats The first is the easiest, but if you try to access it as if you were a viewer (second case) you would have scalability issues, I suppose. ? Both Kurento blueprints or images can be used on FIWARE Lab * Suggested to use last image available for Kurento in FIWARE LAB ? Quick instructions: * Open all UDP ports. * Check if Kurento works in a browser. * If it doesn?t work (NAT must allow realtime traffic) it may require to install a Turn server in FIWARE lab. In this case, ask further instructions to Luis. ? Different kind of applications available from Kurento repository. The FIWARE Lab image has already several application installed (based on Tomcat on Springboot) then it should be a better solution than blueprint, which doesn't have any application. Applications are open source, so they could be used to derive the required application for our demo ? Application server can be on same machine as KMS or not; in the latter case it is required to open port 8888. Ports for Application server are 80, 8080 etc (HTTP). ? 2 Wirecloud widgets available for Kurento: one used for IP camera stream (not useful if using webkit/chrome), the second is for meeting communication. Perhaps the robot demo could be based on the latter. It is however better to talk to Wirecloud guys about this. Luis, I also enclose below the link with the slide of the configuration of Robotics GE used in the tests with Kurento (I apologize, I sent the link to many people but I missed your e-mail): https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit?usp=sharing Best, Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Jun 10 08:32:56 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 10 Jun 2015 06:32:56 +0000 Subject: [Fiware-robotics] R: R: Robotics-Kurento call minutes In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F63BFDA1AE@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D558F8@TELMBA001BA020.telecomitalia.local> <0B616D87-C5D5-4B1B-97B2-CB6916E2C7E1@urjc.es> Message-ID: Hi Pepe and Luis, Well the number of viewers can be extremely variable: if we organize an small demo e.g. for a meeting, there can be 5-7 viewers. But if we organize e.g. a webinar, then we might have many more viewers (20? 50?). Luis, is there a direct relationship between the number of viewers and the requirements in terms of processing power? If yes, what could be the 'formula' (or just a rule of thumb) we could use? Thanks Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: marted? 9 giugno 2015 18:17 A: Luis L?pez Fern?ndez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics-Kurento call minutes Hi, I suppose that we're going to have several viewers in the live demo. Pier, could we know how many of them? If this data is unknown I'd prefer to assign a large instance to Kurento. Thank you very much, Pepe On 09/06/15 12:50, Luis L?pez Fern?ndez wrote: Hi, With a tiny you should be able to stream the flow between the robot and the controller. However, if you want to have several viewers or if you want to record the stream, you'll need to use a more powerful machine: the more CPU you add, the higher the scalability you'll reach ... 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 09/06/2015, a las 11:42, Jose Jaime Ariza > escribi?: Hi Luis, We are gathering VM requirements for the live demo. I've found that the StreamOriented blueprint creates a tiny VM, do you think it we'll be enough for us or you recommend different VM size or number of VMs? Thank you very much, Pepe On 27/05/15 09:42, Antonini Roberto wrote: Just a quick comment inline (in red), for what concerns the first issues. R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 26 maggio 2015 16:31 A: fiware-robotics at lists.fi-ware.org; luis.lopez at urjc.es Oggetto: [Fiware-robotics] Robotics-Kurento call minutes Hi all, please find a short summary of the Robotics-Kurento call. Robotics - Kurento call: ? We should define what are the requirements, e.g. for latency: are we ok with 1/2s latency in our application? Do we need to broadcast the video, or is it used by an operator only? If we use camera sight as a feedback to move the robot, then 1 or 2 seconds are enough, to operate for that latency I would have to slow down robot ... * For the demo purposes, probably the former is more relevant (we can show to many people the robots moving) I would set two different profiles: ? The operator, who needs fast feedback from the camera (less than 0.5s) ? The viewer(s), who accesses a streaming portal, where above video is usually recasted and codified in different formats The first is the easiest, but if you try to access it as if you were a viewer (second case) you would have scalability issues, I suppose. ? Both Kurento blueprints or images can be used on FIWARE Lab * Suggested to use last image available for Kurento in FIWARE LAB ? Quick instructions: * Open all UDP ports. * Check if Kurento works in a browser. * If it doesn't work (NAT must allow realtime traffic) it may require to install a Turn server in FIWARE lab. In this case, ask further instructions to Luis. ? Different kind of applications available from Kurento repository. The FIWARE Lab image has already several application installed (based on Tomcat on Springboot) then it should be a better solution than blueprint, which doesn't have any application. Applications are open source, so they could be used to derive the required application for our demo ? Application server can be on same machine as KMS or not; in the latter case it is required to open port 8888. Ports for Application server are 80, 8080 etc (HTTP). ? 2 Wirecloud widgets available for Kurento: one used for IP camera stream (not useful if using webkit/chrome), the second is for meeting communication. Perhaps the robot demo could be based on the latter. It is however better to talk to Wirecloud guys about this. Luis, I also enclose below the link with the slide of the configuration of Robotics GE used in the tests with Kurento (I apologize, I sent the link to many people but I missed your e-mail): https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit?usp=sharing Best, Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- 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 Wed Jun 10 10:01:52 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Wed, 10 Jun 2015 10:01:52 +0200 Subject: [Fiware-robotics] R: Robotics-Kurento call minutes In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F63BFDA1AE@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D558F8@TELMBA001BA020.telecomitalia.local> <0B616D87-C5D5-4B1B-97B2-CB6916E2C7E1@urjc.es> Message-ID: Hi, We don't have benchmarks for this, the only rule I can provide you is that the higher the CPU power the higher the number of viewers. In our informal benchmarks we see that with a single CPU it's difficult to have much more than 10 viewers. With 2 CPUs its reasonable to reach 30 or 40. Best. Luis. El 10/06/2015, a las 08:32, Garino Pierangelo escribi?: > Hi Pepe and Luis, > > Well the number of viewers can be extremely variable: if we organize an small demo e.g. for a meeting, there can be 5-7 viewers. But if we organize e.g. a webinar, then we might have many more viewers (20? 50?). > > Luis, is there a direct relationship between the number of viewers and the requirements in terms of processing power? If yes, what could be the ?formula? (or just a rule of thumb) we could use? > > Thanks > Pier > > > > > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza > Inviato: marted? 9 giugno 2015 18:17 > A: Luis L?pez Fern?ndez > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: Robotics-Kurento call minutes > > Hi, > > I suppose that we're going to have several viewers in the live demo. Pier, could we know how many of them? If this data is unknown I'd prefer to assign a large instance to Kurento. > > Thank you very much, > Pepe > > On 09/06/15 12:50, Luis L?pez Fern?ndez wrote: > Hi, > With a tiny you should be able to stream the flow between the robot and the controller. However, if you want to have several viewers or if you want to record the stream, you'll need to use a more powerful machine: the more CPU you add, the higher the scalability you'll reach ... > > 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 09/06/2015, a las 11:42, Jose Jaime Ariza escribi?: > > > Hi Luis, > > We are gathering VM requirements for the live demo. I've found that the StreamOriented blueprint creates a tiny VM, do you think it we'll be enough for us or you recommend different VM size or number of VMs? > > Thank you very much, > Pepe > > On 27/05/15 09:42, Antonini Roberto wrote: > Just a quick comment inline (in red), for what concerns the first issues. > R > > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario > Inviato: marted? 26 maggio 2015 16:31 > A: fiware-robotics at lists.fi-ware.org; luis.lopez at urjc.es > Oggetto: [Fiware-robotics] Robotics-Kurento call minutes > > Hi all, > please find a short summary of the Robotics-Kurento call. > > Robotics - Kurento call: > ? We should define what are the requirements, e.g. for latency: are we ok with 1/2s latency in our application? Do we need to broadcast the video, or is it used by an operator only? > If we use camera sight as a feedback to move the robot, then 1 or 2 seconds are enough, to operate for that latency I would have to slow down robot ? > For the demo purposes, probably the former is more relevant (we can show to many people the robots moving) > I would set two different profiles: > ? The operator, who needs fast feedback from the camera (less than 0.5s) > ? The viewer(s), who accesses a streaming portal, where above video is usually recasted and codified in different formats > The first is the easiest, but if you try to access it as if you were a viewer (second case) you would have scalability issues, I suppose. > > > ? Both Kurento blueprints or images can be used on FIWARE Lab > Suggested to use last image available for Kurento in FIWARE LAB > ? Quick instructions: > Open all UDP ports. > Check if Kurento works in a browser. > If it doesn?t work (NAT must allow realtime traffic) it may require to install a Turn server in FIWARE lab. In this case, ask further instructions to Luis. > ? Different kind of applications available from Kurento repository. The FIWARE Lab image has already several application installed (based on Tomcat on Springboot) then it should be a better solution than blueprint, which doesn't have any application. Applications are open source, so they could be used to derive the required application for our demo > ? Application server can be on same machine as KMS or not; in the latter case it is required to open port 8888. Ports for Application server are 80, 8080 etc (HTTP). > ? 2 Wirecloud widgets available for Kurento: one used for IP camera stream (not useful if using webkit/chrome), the second is for meeting communication. Perhaps the robot demo could be based on the latter. It is however better to talk to Wirecloud guys about this. > > Luis, I also enclose below the link with the slide of the configuration of Robotics GE used in the tests with Kurento (I apologize, I sent the link to many people but I missed your e-mail): > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit?usp=sharing > > > Best, > Gianmario > > ------------------------------------------------------------------------------------ > Telecom Italia > Gianmario Bollano > Innovation - Mobile Devices & Sim Applications > Via Reiss Romoli, n? 274 > Cap 10151 Torino > Phone 011 228 7103 > Cell Phone 3316015048 > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. > This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. > > Rispetta l'ambiente. Non stampare questa mail se non ? necessario. > > > > > -- > 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 pierangelo.garino at telecomitalia.it Wed Jun 10 10:12:09 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 10 Jun 2015 08:12:09 +0000 Subject: [Fiware-robotics] R: R: Robotics-Kurento call minutes In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F63BFDA1AE@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D558F8@TELMBA001BA020.telecomitalia.local> <0B616D87-C5D5-4B1B-97B2-CB6916E2C7E1@urjc.es> Message-ID: Hi Luis, That's already a very helpful feedback, thanks. We can thus define the kind of VM we'd require. BR Pier Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: mercoled? 10 giugno 2015 10:02 A: Garino Pierangelo Cc: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics-Kurento call minutes Hi, We don't have benchmarks for this, the only rule I can provide you is that the higher the CPU power the higher the number of viewers. In our informal benchmarks we see that with a single CPU it's difficult to have much more than 10 viewers. With 2 CPUs its reasonable to reach 30 or 40. Best. Luis. El 10/06/2015, a las 08:32, Garino Pierangelo > escribi?: Hi Pepe and Luis, Well the number of viewers can be extremely variable: if we organize an small demo e.g. for a meeting, there can be 5-7 viewers. But if we organize e.g. a webinar, then we might have many more viewers (20? 50?). Luis, is there a direct relationship between the number of viewers and the requirements in terms of processing power? If yes, what could be the 'formula' (or just a rule of thumb) we could use? Thanks Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: marted? 9 giugno 2015 18:17 A: Luis L?pez Fern?ndez Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Robotics-Kurento call minutes Hi, I suppose that we're going to have several viewers in the live demo. Pier, could we know how many of them? If this data is unknown I'd prefer to assign a large instance to Kurento. Thank you very much, Pepe On 09/06/15 12:50, Luis L?pez Fern?ndez wrote: Hi, With a tiny you should be able to stream the flow between the robot and the controller. However, if you want to have several viewers or if you want to record the stream, you'll need to use a more powerful machine: the more CPU you add, the higher the scalability you'll reach ... 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 09/06/2015, a las 11:42, Jose Jaime Ariza > escribi?: Hi Luis, We are gathering VM requirements for the live demo. I've found that the StreamOriented blueprint creates a tiny VM, do you think it we'll be enough for us or you recommend different VM size or number of VMs? Thank you very much, Pepe On 27/05/15 09:42, Antonini Roberto wrote: Just a quick comment inline (in red), for what concerns the first issues. R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 26 maggio 2015 16:31 A: fiware-robotics at lists.fi-ware.org; luis.lopez at urjc.es Oggetto: [Fiware-robotics] Robotics-Kurento call minutes Hi all, please find a short summary of the Robotics-Kurento call. Robotics - Kurento call: * We should define what are the requirements, e.g. for latency: are we ok with 1/2s latency in our application? Do we need to broadcast the video, or is it used by an operator only? If we use camera sight as a feedback to move the robot, then 1 or 2 seconds are enough, to operate for that latency I would have to slow down robot ... * For the demo purposes, probably the former is more relevant (we can show to many people the robots moving) I would set two different profiles: * The operator, who needs fast feedback from the camera (less than 0.5s) * The viewer(s), who accesses a streaming portal, where above video is usually recasted and codified in different formats The first is the easiest, but if you try to access it as if you were a viewer (second case) you would have scalability issues, I suppose. * Both Kurento blueprints or images can be used on FIWARE Lab * Suggested to use last image available for Kurento in FIWARE LAB * Quick instructions: * Open all UDP ports. * Check if Kurento works in a browser. * If it doesn't work (NAT must allow realtime traffic) it may require to install a Turn server in FIWARE lab. In this case, ask further instructions to Luis. * Different kind of applications available from Kurento repository. The FIWARE Lab image has already several application installed (based on Tomcat on Springboot) then it should be a better solution than blueprint, which doesn't have any application. Applications are open source, so they could be used to derive the required application for our demo * Application server can be on same machine as KMS or not; in the latter case it is required to open port 8888. Ports for Application server are 80, 8080 etc (HTTP). * 2 Wirecloud widgets available for Kurento: one used for IP camera stream (not useful if using webkit/chrome), the second is for meeting communication. Perhaps the robot demo could be based on the latter. It is however better to talk to Wirecloud guys about this. Luis, I also enclose below the link with the slide of the configuration of Robotics GE used in the tests with Kurento (I apologize, I sent the link to many people but I missed your e-mail): https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit?usp=sharing Best, Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- 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 gianmario.bollano at telecomitalia.it Wed Jun 10 16:07:51 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 10 Jun 2015 14:07:51 +0000 Subject: [Fiware-robotics] Proposal for Robotics live demo architecture. Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE0F68D@telmba003ba020.telecomitalia.local> Hi all, I've updated the shared slides for the Robotics live demo architecture according to the last information from Luis. I've also added a short note at the bottom of each slide. There are 3 Hypothesis but I think we can restrict to one, so please give me your feedback about them: which one should we focus on? Please give a preference so that we can chose one main hypothesis to focus on: we should have one proposal, if we want to discuss details with other groups. I put my vote on Hypothesis 2, Kurento alone, App server in the same VM as Context Broker. Also please add any missing information, and feel free to edit for errors, notes or changes. The slides are here: https://docs.google.com/presentation/d/1hDmIlCJY3mrrc_Rs2YoF0g1pdhiHzNcEAaPbP3VMJG4/edit?usp=sharing ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From roberto1.antonini at telecomitalia.it Thu Jun 11 11:35:30 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 11 Jun 2015 09:35:30 +0000 Subject: [Fiware-robotics] R: Proposal for Robotics live demo architecture. In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE0F68D@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE0F68D@telmba003ba020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8643D7059E@TELMBB001BA020.telecomitalia.local> I add some graphics to understand/share where the Kurento Application Server has been placed, if so. Please correct me if I'm wrong. BR Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: mercoled? 10 giugno 2015 16:08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Proposal for Robotics live demo architecture. Hi all, I've updated the shared slides for the Robotics live demo architecture according to the last information from Luis. I've also added a short note at the bottom of each slide. There are 3 Hypothesis but I think we can restrict to one, so please give me your feedback about them: which one should we focus on? Please give a preference so that we can chose one main hypothesis to focus on: we should have one proposal, if we want to discuss details with other groups. I put my vote on Hypothesis 2, Kurento alone, App server in the same VM as Context Broker. Also please add any missing information, and feel free to edit for errors, notes or changes. The slides are here: https://docs.google.com/presentation/d/1hDmIlCJY3mrrc_Rs2YoF0g1pdhiHzNcEAaPbP3VMJG4/edit?usp=sharing ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Thu Jun 11 12:00:43 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 11 Jun 2015 10:00:43 +0000 Subject: [Fiware-robotics] R: Proposal for Robotics live demo architecture. In-Reply-To: <246C286B275B1B46A255552CD236DA8643D7059E@TELMBB001BA020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE0F68D@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D7059E@TELMBB001BA020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE0FD06@telmba003ba020.telecomitalia.local> Hi Roberto, all, I see your text, it's fine for me. In Hyp2 the idea is that we use one App server to host both Kurento and Wirecloud App, but we could have two different Application server instead, though I do not know if it might be useful or unneeded. So I guess it's fine to show Kurento App server in Hyp 3 (because it is dedicated to Kurento only), while I do not know if we have to assume that in Hyp 2 Kurento App server is distincted by Wirecloud/Robotics Widget App server. What are your insight about these hypothesis? After discussing it we could also also forward the question to Wirecloud or Kurento if we don't have a clear solution for this issue. Gianmario Da: Antonini Roberto Inviato: gioved? 11 giugno 2015 11:36 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: Proposal for Robotics live demo architecture. I add some graphics to understand/share where the Kurento Application Server has been placed, if so. Please correct me if I'm wrong. BR Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: mercoled? 10 giugno 2015 16:08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Proposal for Robotics live demo architecture. Hi all, I've updated the shared slides for the Robotics live demo architecture according to the last information from Luis. I've also added a short note at the bottom of each slide. There are 3 Hypothesis but I think we can restrict to one, so please give me your feedback about them: which one should we focus on? Please give a preference so that we can chose one main hypothesis to focus on: we should have one proposal, if we want to discuss details with other groups. I put my vote on Hypothesis 2, Kurento alone, App server in the same VM as Context Broker. Also please add any missing information, and feel free to edit for errors, notes or changes. The slides are here: https://docs.google.com/presentation/d/1hDmIlCJY3mrrc_Rs2YoF0g1pdhiHzNcEAaPbP3VMJG4/edit?usp=sharing ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Thu Jun 11 16:42:16 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 11 Jun 2015 14:42:16 +0000 Subject: [Fiware-robotics] R: Proposal for Robotics live demo architecture. In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE0FD06@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE0F68D@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D7059E@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE0FD06@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE0FEFA@telmba003ba020.telecomitalia.local> Hi all, I'm browsing at the wirecloud tutorials: https://edu.fiware.org/course/view.php?id=53 It seems to me we may not need to host wirecloud on a VM if we use the public instance and have one or more widgets available on the WStore (public or restricted to Robotics group). In this case the Wirecloud GE should already provide the App Server capabilities. >From the documentation on Github seems that Wirecloud may use an internal web server (for evaluation/test purposes) or be run in an Apache web server. If Wirecloud instance in FILAB use also a Django internal or is run in an Apache web server, and this happen also for the Kurento widget (i.e. Wirecloud also host the Kurento app server), we can avoid having an App server because in that case anything is provided by Wirecloud instance and the Robotics demo dose is hosted inside additional widgets (Robotics and Kurento widgets). In that case the Robotics Webpage application might be provided as a mashup at likely at a public address of the type : https://mashup.lab.fiware.org/... However, if we cannot use the public Wirecloud instance or if the App server used by Wirecloud is not able to acts as the Kurento App Server, we may still need to have dedicated App Server as in Hyp 2 and Hyp 3. If you have better knowledge about these aspects, please share this information, because it affects how many VMs we will need and their size. My question, to redirect at Wirecloud team if we don't have an answer are: - Can we use the public instance of Wirecloud in FIWARE-LAB for the Robotics Live Demo? - Will we be able to use a Robotics Widget (with Kurento streaming embedded in the mashup) that connects to Wirecloud, without the need of having a dedicated Application/Web server (i.e. can we host all the Robotics Widget code and also the Kurento App server)? Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: gioved? 11 giugno 2015 12:01 A: Antonini Roberto; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Proposal for Robotics live demo architecture. Hi Roberto, all, I see your text, it's fine for me. In Hyp2 the idea is that we use one App server to host both Kurento and Wirecloud App, but we could have two different Application server instead, though I do not know if it might be useful or unneeded. So I guess it's fine to show Kurento App server in Hyp 3 (because it is dedicated to Kurento only), while I do not know if we have to assume that in Hyp 2 Kurento App server is distincted by Wirecloud/Robotics Widget App server. What are your insight about these hypothesis? After discussing it we could also also forward the question to Wirecloud or Kurento if we don't have a clear solution for this issue. Gianmario Da: Antonini Roberto Inviato: gioved? 11 giugno 2015 11:36 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: Proposal for Robotics live demo architecture. I add some graphics to understand/share where the Kurento Application Server has been placed, if so. Please correct me if I'm wrong. BR Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: mercoled? 10 giugno 2015 16:08 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Proposal for Robotics live demo architecture. Hi all, I've updated the shared slides for the Robotics live demo architecture according to the last information from Luis. I've also added a short note at the bottom of each slide. There are 3 Hypothesis but I think we can restrict to one, so please give me your feedback about them: which one should we focus on? Please give a preference so that we can chose one main hypothesis to focus on: we should have one proposal, if we want to discuss details with other groups. I put my vote on Hypothesis 2, Kurento alone, App server in the same VM as Context Broker. Also please add any missing information, and feel free to edit for errors, notes or changes. The slides are here: https://docs.google.com/presentation/d/1hDmIlCJY3mrrc_Rs2YoF0g1pdhiHzNcEAaPbP3VMJG4/edit?usp=sharing ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From davide.colombatto at telecomitalia.it Thu Jun 11 17:59:38 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 11 Jun 2015 15:59:38 +0000 Subject: [Fiware-robotics] FIROS ports management problem Message-ID: <069906BED271EB4A883BD9578DCDD3540CB51346@TELMBB006RM001.telecomitalia.local> Hi ET guys, I've updated the OpenSpec Draft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#) for what concern "FIROS ports management problem". Do you agree to delete all the red text in pages 5/6/7 maintaining only the green text? You can edit the document if something is not correct. Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Fri Jun 12 11:59:37 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 12 Jun 2015 11:59:37 +0200 Subject: [Fiware-robotics] FIROS ports management problem References: <069906BED271EB4A883BD9578DCDD3540CB51346@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, We've made minor changes in the text and deleted the bullet about contextbroker-ping. The text looks fine, we can delete the re text in pages 5/6/7 and maintain the green text. Thank you very much. Pepe p.s.: sorry for the spam, Davide :) On 11/06/15 17:59, Colombatto Davide wrote: Hi ET guys, I?ve updated the OpenSpec Draft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#) for what concern ?FIROS ports management problem?. Do you agree to delete all the red text in pages 5/6/7 maintaining only the green text? You can edit the document if something is not correct. Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [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 roberto1.antonini at telecomitalia.it Fri Jun 12 20:03:09 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Fri, 12 Jun 2015 18:03:09 +0000 Subject: [Fiware-robotics] Next phC In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE0FD06@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE0F68D@telmba003ba020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D7059E@TELMBB001BA020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE0FD06@telmba003ba020.telecomitalia.local> Message-ID: Hi all I'm not gong to attend the next call on thursday for a business trip. Have a nice week end. Roberto Inviato da smartphone Sony Xperia? Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Jun 16 09:48:02 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 16 Jun 2015 07:48:02 +0000 Subject: [Fiware-robotics] Robotics weekly call Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE12A9C@telmba003ba020.telecomitalia.local> We will have the weekly Robotics call with hangout. Robotics call minutes: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo Best, Gianmario Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2523 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Jun 16 12:00:45 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 16 Jun 2015 10:00:45 +0000 Subject: [Fiware-robotics] Wirecloud and Kurento people Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE12B7F@telmba003ba020.telecomitalia.local> I've found these people to send the messages to discuss our proposal for Robotics Live Demo: please let me know if you know other people to be involved. Wirecloud: aarranz at fi.upm.es ; amagan at conwet.com ; fdelavega at fi.upm.es ; jsoriano at fi.upm.es Kurento: Only Luis? luis.lopez at urjc.es Best, Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Tue Jun 16 12:17:53 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 16 Jun 2015 12:17:53 +0200 Subject: [Fiware-robotics] Wirecloud and Kurento people References: <7E649CBD84A947498203DAF8F098B1F63FE12B7F@telmba003ba020.telecomitalia.local> Message-ID: Hi, Those are the same contacts I have. BR On 16/06/15 12:00, Bollano Gianmario wrote: I?ve found these people to send the messages to discuss our proposal for Robotics Live Demo: please let me know if you know other people to be involved. Wirecloud: aarranz at fi.upm.es ; amagan at conwet.com ; fdelavega at fi.upm.es ; jsoriano at fi.upm.es Kurento: Only Luis? luis.lopez at urjc.es Best, Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Tue Jun 16 12:34:20 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 16 Jun 2015 10:34:20 +0000 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Message-ID: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ... of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Jun 16 12:38:29 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 16 Jun 2015 10:38:29 +0000 Subject: [Fiware-robotics] Proposal of Q to Kurento and Wirecloud Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE12BEA@telmba003ba020.telecomitalia.local> Dear all, we are defining further details for the Robotics Live demo. Robotics Live demos consist of transmitting video from robots camera, controlling the robots with a Joystick from a Web interface, displaying robot status, their positioning, and their video stream. We are defining the architecture for the Robotics demo have few questions and hypothesis we need to check with you: 1. To use widgets to control Robots and displaying video from robots, can we use the public instance of Wirecloud in FIWARE LAB [our Hypothesis] or do we need to instantiate a dedicated Wirecloud instance (reserved only for Robotics demo in a specific VM)? 2. Will we be able to run different widgets in the same Wirecloud instance for different functions [our Hypothesis], e.g. to control the robot with a Joystick interface, to Initialize Robots configuration (that means writing few information using APIs to configure Robot environment), to display Robot positioning and data? 3. If we have 2 robots to transmitting Video streams, will we need two Application servers (one per stream), or just one [our Hypothesis]? Can we use the same Application server for video TX and RX endpoints [our Hypothesis]? 4. If we want to use a Kurento Widget in Wirecloud, can we assume that the Application server (to host Kurento client) is the same one embedded in Wirecloud [our Hypothesis] or do we need an external Application server? To manage two video streams transmitted by two robots, do we need two widgets? Can these widget use the same Application server? Best, Gianmmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From luis.lopez at urjc.es Tue Jun 16 14:15:26 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Tue, 16 Jun 2015 14:15:26 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, In relation to question 1), which is the only one for which I can provide a precise answer: Tutorial 3 is just, as its name indicates, a tutorial, not an application devoted for being used in production. As such, it has a lot of limitations, including the fact that only one master (robot in our case) can be present at any time in the application. Having said this, it shouldn't be too complex to create an application extending tutorial 3 for enabling multiple robots to be broadcasted. We may assume the creation of such an application if you want. However, we would require a short specification of requirements for doing so. For example, a viewer may require to see both robots at the same time? viewers need to register somehow? how we guarantee that master stream comes from a robot? through an authentication mechanism? based on passwords? This types of questions would need to be answered before creating such an application. Best regards. Luis. El 16/06/2015, a las 12:34, Colombatto Davide escribi?: > Hi Luis and Wirecloud guys, > > We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. > > 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). > Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. > Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? > > 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? > If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? > > Thank you, > Davide > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. > This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. > > Rispetta l'ambiente. Non stampare questa mail se non ? necessario. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Tue Jun 16 15:47:45 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 16 Jun 2015 13:47:45 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> Message-ID: Hi Luis and All, Concerning the specification of requirements, the basic operations expected by the robotics demo Step 1 are those reported in the live demo deliverable at section 4.4.3.1 Step1: Managing interactively robots We do agree however that a more refined version is necessary to explain in detail what actions, first of all from a user's (and viewer's as this is a demo) perspective, are to be performed. Perhaps a description similar to the live demo script used in FIWARE I might be helpful. Let's work on this point and come with a refined description of the demo story in a couple of days max. I'll provide asap a link to a shared doc to perform this action. BR Pier 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? 16 giugno 2015 14:15 A: Colombatto Davide Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi, In relation to question 1), which is the only one for which I can provide a precise answer: Tutorial 3 is just, as its name indicates, a tutorial, not an application devoted for being used in production. As such, it has a lot of limitations, including the fact that only one master (robot in our case) can be present at any time in the application. Having said this, it shouldn't be too complex to create an application extending tutorial 3 for enabling multiple robots to be broadcasted. We may assume the creation of such an application if you want. However, we would require a short specification of requirements for doing so. For example, a viewer may require to see both robots at the same time? viewers need to register somehow? how we guarantee that master stream comes from a robot? through an authentication mechanism? based on passwords? This types of questions would need to be answered before creating such an application. Best regards. Luis. El 16/06/2015, a las 12:34, Colombatto Davide > escribi?: Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ... of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjaime at ikergune.com Tue Jun 16 17:21:46 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 16 Jun 2015 17:21:46 +0200 Subject: [Fiware-robotics] Proposal of Q to Kurento and Wirecloud References: <7E649CBD84A947498203DAF8F098B1F63FE12BEA@telmba003ba020.telecomitalia.local> Message-ID: Hi, I think they're ok. I'd just change "demo have few questions" by "demo and have a few questions". BR, Pepe. On 16/06/15 12:38, Bollano Gianmario wrote: Dear all, we are defining further details for the Robotics Live demo. Robotics Live demos consist of transmitting video from robots camera, controlling the robots with a Joystick from a Web interface, displaying robot status, their positioning, and their video stream. We are defining the architecture for the Robotics demo have few questions and hypothesis we need to check with you: 1. To use widgets to control Robots and displaying video from robots, can we use the public instance of Wirecloud in FIWARE LAB [our Hypothesis] or do we need to instantiate a dedicated Wirecloud instance (reserved only for Robotics demo in a specific VM)? 2. Will we be able to run different widgets in the same Wirecloud instance for different functions [our Hypothesis], e.g. to control the robot with a Joystick interface, to Initialize Robots configuration (that means writing few information using APIs to configure Robot environment), to display Robot positioning and data? 3. If we have 2 robots to transmitting Video streams, will we need two Application servers (one per stream), or just one [our Hypothesis]? Can we use the same Application server for video TX and RX endpoints [our Hypothesis]? 4. If we want to use a Kurento Widget in Wirecloud, can we assume that the Application server (to host Kurento client) is the same one embedded in Wirecloud [our Hypothesis] or do we need an external Application server? To manage two video streams transmitted by two robots, do we need two widgets? Can these widget use the same Application server? Best, Gianmmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjaime at ikergune.com Tue Jun 16 17:30:29 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 16 Jun 2015 17:30:29 +0200 Subject: [Fiware-robotics] End-of-sprint demo Message-ID: Hi, In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? BR, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From gianmario.bollano at telecomitalia.it Tue Jun 16 17:36:01 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 16 Jun 2015 15:36:01 +0000 Subject: [Fiware-robotics] R: Proposal of Q to Kurento and Wirecloud In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F63FE12BEA@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE12DB0@telmba003ba020.telecomitalia.local> We've had an answer from Luis to the e-mail from Davide concerning the set of questions for Kurento (which were part of the questions below). Luis asked further question and details about the demo. After that Pier has sent an e-mail to Luis and all the Robotics group to suggest working on a document to better describe step by step what we want to show in the Live demo. We are working now on this new document and will share a version of it by tomorrow; according to the suggestion from Pier, we can first refine this document and then we will be able to forward our questions to Wirecloud and Kurento, providing them with a more detailed description of what we want to show and we'll need for the Live demo. Best, Gianmario 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: marted? 16 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Proposal of Q to Kurento and Wirecloud Hi, I think they're ok. I'd just change "demo have few questions" by "demo and have a few questions". BR, Pepe. On 16/06/15 12:38, Bollano Gianmario wrote: Dear all, we are defining further details for the Robotics Live demo. Robotics Live demos consist of transmitting video from robots camera, controlling the robots with a Joystick from a Web interface, displaying robot status, their positioning, and their video stream. We are defining the architecture for the Robotics demo have few questions and hypothesis we need to check with you: 1. To use widgets to control Robots and displaying video from robots, can we use the public instance of Wirecloud in FIWARE LAB [our Hypothesis] or do we need to instantiate a dedicated Wirecloud instance (reserved only for Robotics demo in a specific VM)? 2. Will we be able to run different widgets in the same Wirecloud instance for different functions [our Hypothesis], e.g. to control the robot with a Joystick interface, to Initialize Robots configuration (that means writing few information using APIs to configure Robot environment), to display Robot positioning and data? 3. If we have 2 robots to transmitting Video streams, will we need two Application servers (one per stream), or just one [our Hypothesis]? Can we use the same Application server for video TX and RX endpoints [our Hypothesis]? 4. If we want to use a Kurento Widget in Wirecloud, can we assume that the Application server (to host Kurento client) is the same one embedded in Wirecloud [our Hypothesis] or do we need an external Application server? To manage two video streams transmitted by two robots, do we need two widgets? Can these widget use the same Application server? Best, Gianmmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Wed Jun 17 12:34:52 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 17 Jun 2015 10:34:52 +0000 Subject: [Fiware-robotics] R: R: Proposal of Q to Kurento and Wirecloud In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE12DB0@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE12BEA@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE12DB0@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE1336A@telmba003ba020.telecomitalia.local> Dear all, Pier has prepared a shared document based on the section of the Live demo deliverable and takng as example a previous document prepared for the Live demo for Wirecloud. The idea is to use this shared document to better define and describe the Live demo. Pier, Davide and me have already added some contribution to it; we need to work on it and use it as a description of what we would like to show in the live demo. This will be also shared to Wirecloud and Kurento people to better define with them what we practically need for the Robotics demo. Please, read and edit the document to add all the information relevant and useful to describe the demo, what we will / would need to show. This always will help us to find what should be changed and to define more focused question . The shared document is here: https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit?pli=1# Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 16 giugno 2015 17:36 A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Proposal of Q to Kurento and Wirecloud We've had an answer from Luis to the e-mail from Davide concerning the set of questions for Kurento (which were part of the questions below). Luis asked further question and details about the demo. After that Pier has sent an e-mail to Luis and all the Robotics group to suggest working on a document to better describe step by step what we want to show in the Live demo. We are working now on this new document and will share a version of it by tomorrow; according to the suggestion from Pier, we can first refine this document and then we will be able to forward our questions to Wirecloud and Kurento, providing them with a more detailed description of what we want to show and we'll need for the Live demo. Best, Gianmario 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: marted? 16 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Proposal of Q to Kurento and Wirecloud Hi, I think they're ok. I'd just change "demo have few questions" by "demo and have a few questions". BR, Pepe. On 16/06/15 12:38, Bollano Gianmario wrote: Dear all, we are defining further details for the Robotics Live demo. Robotics Live demos consist of transmitting video from robots camera, controlling the robots with a Joystick from a Web interface, displaying robot status, their positioning, and their video stream. We are defining the architecture for the Robotics demo have few questions and hypothesis we need to check with you: 1. To use widgets to control Robots and displaying video from robots, can we use the public instance of Wirecloud in FIWARE LAB [our Hypothesis] or do we need to instantiate a dedicated Wirecloud instance (reserved only for Robotics demo in a specific VM)? 2. Will we be able to run different widgets in the same Wirecloud instance for different functions [our Hypothesis], e.g. to control the robot with a Joystick interface, to Initialize Robots configuration (that means writing few information using APIs to configure Robot environment), to display Robot positioning and data? 3. If we have 2 robots to transmitting Video streams, will we need two Application servers (one per stream), or just one [our Hypothesis]? Can we use the same Application server for video TX and RX endpoints [our Hypothesis]? 4. If we want to use a Kurento Widget in Wirecloud, can we assume that the Application server (to host Kurento client) is the same one embedded in Wirecloud [our Hypothesis] or do we need an external Application server? To manage two video streams transmitted by two robots, do we need two widgets? Can these widget use the same Application server? Best, Gianmmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Wed Jun 17 13:53:12 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 17 Jun 2015 11:53:12 +0000 Subject: [Fiware-robotics] R: R: R: Proposal of Q to Kurento and Wirecloud In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE1336A@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE12BEA@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE12DB0@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE1336A@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE133E7@telmba003ba020.telecomitalia.local> I've added some notes in the document but after sending the e-mail, my browser (firefox) froze and then crashed. I've just notices that all the notes I have added have been lost - all of them - none of them appears now in the shared document. I'm joining another call now; I will edit again the document later or tomorrow. Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: mercoled? 17 giugno 2015 12:35 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Proposal of Q to Kurento and Wirecloud Dear all, Pier has prepared a shared document based on the section of the Live demo deliverable and takng as example a previous document prepared for the Live demo for Wirecloud. The idea is to use this shared document to better define and describe the Live demo. Pier, Davide and me have already added some contribution to it; we need to work on it and use it as a description of what we would like to show in the live demo. This will be also shared to Wirecloud and Kurento people to better define with them what we practically need for the Robotics demo. Please, read and edit the document to add all the information relevant and useful to describe the demo, what we will / would need to show. This always will help us to find what should be changed and to define more focused question . The shared document is here: https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit?pli=1# Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 16 giugno 2015 17:36 A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Proposal of Q to Kurento and Wirecloud We've had an answer from Luis to the e-mail from Davide concerning the set of questions for Kurento (which were part of the questions below). Luis asked further question and details about the demo. After that Pier has sent an e-mail to Luis and all the Robotics group to suggest working on a document to better describe step by step what we want to show in the Live demo. We are working now on this new document and will share a version of it by tomorrow; according to the suggestion from Pier, we can first refine this document and then we will be able to forward our questions to Wirecloud and Kurento, providing them with a more detailed description of what we want to show and we'll need for the Live demo. Best, Gianmario 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: marted? 16 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Proposal of Q to Kurento and Wirecloud Hi, I think they're ok. I'd just change "demo have few questions" by "demo and have a few questions". BR, Pepe. On 16/06/15 12:38, Bollano Gianmario wrote: Dear all, we are defining further details for the Robotics Live demo. Robotics Live demos consist of transmitting video from robots camera, controlling the robots with a Joystick from a Web interface, displaying robot status, their positioning, and their video stream. We are defining the architecture for the Robotics demo have few questions and hypothesis we need to check with you: 1. To use widgets to control Robots and displaying video from robots, can we use the public instance of Wirecloud in FIWARE LAB [our Hypothesis] or do we need to instantiate a dedicated Wirecloud instance (reserved only for Robotics demo in a specific VM)? 2. Will we be able to run different widgets in the same Wirecloud instance for different functions [our Hypothesis], e.g. to control the robot with a Joystick interface, to Initialize Robots configuration (that means writing few information using APIs to configure Robot environment), to display Robot positioning and data? 3. If we have 2 robots to transmitting Video streams, will we need two Application servers (one per stream), or just one [our Hypothesis]? Can we use the same Application server for video TX and RX endpoints [our Hypothesis]? 4. If we want to use a Kurento Widget in Wirecloud, can we assume that the Application server (to host Kurento client) is the same one embedded in Wirecloud [our Hypothesis] or do we need an external Application server? To manage two video streams transmitted by two robots, do we need two widgets? Can these widget use the same Application server? Best, Gianmmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- 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 Wed Jun 17 18:03:00 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Wed, 17 Jun 2015 16:03:00 +0000 Subject: [Fiware-robotics] I: End-of-sprint demo In-Reply-To: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> Hi Pepe and all, Q. What do you intend with the "dynamic addition and removal of robots"? Do you mean the dynamic addition and removal of the CB entity when the RCM_DRIVER notifies to FIROS the robot connection and disconnection? N.B. if it is correct, RCM_DRIVER will be completed at the end of this month, so we don't think that RCM_DRIVER-FIROS Interaction will be correctly tested for the begin of July in order to show them in a demo. For the begin of July RCM will be able to manage the following use case: --- HYPOTHESIS --- - Use a turtlebot where the turtlebot's PC with a WiFi /LTE-Internet-key where the PM_AGENT is already installed - A turtlebot is already manual provisioned in the Robotics Data with a specific service logic which is related to: - launch the ROS node "firos core.py PORT" on Server side (i.e. RCM_Master) Q. Does your new FIROS accept the PORT parameter for CBAPI and FCGAPI? Can you send us the new FIROS (and how do you expect the PORT parameter) in order to put it on the RCM_Master? - launch the ROS launcher "turtlebot_bringup minimal.launch" on Robot side Q. In order to use these turtlebot's ROS DRIVER we have modified the old FIROS hardcoded topic "turtle1/cmd_vel" (for turtlesim) in "mobile_base/commands/velocity" (for tutlebot) - The turtlebot's PC is off (or it is on and the WiFi/LTE connection is disabled). Does the new FIROS already use this topic? --- USE CASE --- - Robot CONNECTION: when the turtlebot's PC is switched on (or the WiFi/LTE connection is enabled) the PM_AGENT (on the Robot side) automatically connects to the PM_MASTER (on the Server side) - PM_MASTER (on the Server side) automatically creates the Service Space (Robot Clone) and starts inside it the service logic associated with the robot during its manual provisioning (depicted above) - When FIROS is started it directly creates the CB entity (in the future FIROS have to wait the notification from RCM_DRIVER about robot connection and have to notify to RCM_DRIVER the correct CB entity creation) - A web-app (e.g. an improved version of that used in the demo1) could: - poll the CB in order to populate a listbox of the connected robots (if a robot is connected the CB entity is present, otherwise the CB entity is not present) - the user can select a connected robot (we will show only a robot) and teleoperates it exploiting the CB (as demo1, maybe with other directions in addiction to FORWARD) - two buttons/divs to show additional information directly retrieved from the Robotics GE through the following RDAPI (request/response are exposed in https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit# ): -- Read platform (provisioned Robots): returns the list of the manual provisioned Robots in the Robotics GE and information about their connection status (this information could be shown before and after the robot connection) -- Read service space: returns the list of ROS nodes and ROS launchers which are currently running on the Service Space --- CONSIDERATION --- Robot DISCONNECTION: when the turtlebot's PC is switched off (or the WiFi/LTE connection is disabled) the PM_MASTER (on the Server side) and PM_AGENT (on the Robot side) are able to automatically clean the Service Space (Robot Clone) which was automatically created during the Robot CONNECTION. As said above, since RCM_DRIVER-FIROS Interaction will be NOT correctly tested, for this demo FIROS will be stopped (with SIGINT signal) without is being notified before (in the future FIROS have to wait the notification from RCM_DRIVER about robot disconnection and have to notify to RCM_DRIVER the correct CB entity deletion). Considering that, we don't know if it is advisable to show the robot disconnection phase, due to the CB entity could be not really deleted.. maybe FIROS could delete the CB entity cathing its termination phase (trapping SIGINT signal)? --- IMPORTANT --- Now we are using a TI VM which acts as RCM_Master and OpenVPN-Server and a TI turtlebot's PC acts as OpenVPN-Client. Since the common FIWARE Lab account is not yet ready we could prepare for ET an OpenVPN certificate in order to allow an ET turtlebot's PC acting as OpenVPN-Client of our OpenVPN-Server for your connection/disconnection tests. We can give to ET the OpenVPN certificate on Monday, meanwhile you can install the OpenVPN Client on you turtlebot's PC. We will also send you the package to install the PM_AGENT on your turtlebot's PC. What do you think about this kind of demo? BR, TI, Consoft -----Messaggio originale----- 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: marted? 16 giugno 2015 17:30 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] End-of-sprint demo Hi, In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? BR, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. From pierangelo.garino at telecomitalia.it Thu Jun 18 17:02:09 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 18 Jun 2015 15:02:09 +0000 Subject: [Fiware-robotics] R: R: R: Proposal of Q to Kurento and Wirecloud In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE1336A@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F63FE12BEA@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE12DB0@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE1336A@telmba003ba020.telecomitalia.local> Message-ID: Dear All, I have restructured a bit the shared document, as there were a number of comments and 'suggestions' that, in my view, are mixing together the appearance of the demo and its implementation details. For this reason, column 3 of every row is now structured with two main items: - Presentation (What is shown) o This contains the description to the viewers of the demo, i.e. the 'outline of the story' - Implementation Details (What's behind it) o This part explains what is going on in the overall demo implementation: what's dne by each GE, the way they interact, the effects on the presentation part I expect that these two parts will enable us to better describe what and how the demo works. I kindly ask you all to check and update the steps by adding the parts not yet complete, or updating those already available. I did it for a couple of rows already. Time by time we should start resolving the comments, so as to make the document cleaner. I suggest that at given points we also consolidate the 'suggestions', upon a common agreement on what is accepted, what not and what still requires more details. The ultimate purpose of this exercise is to end up with a description we can share with the Wirecloud and Kurento guys, to let them understand perfectly what we want to achieve, moreover asking them a support to optimize some step, which might be modified and/or improved according to their suggestions. Thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: mercoled? 17 giugno 2015 12:35 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Proposal of Q to Kurento and Wirecloud Dear all, Pier has prepared a shared document based on the section of the Live demo deliverable and takng as example a previous document prepared for the Live demo for Wirecloud. The idea is to use this shared document to better define and describe the Live demo. Pier, Davide and me have already added some contribution to it; we need to work on it and use it as a description of what we would like to show in the live demo. This will be also shared to Wirecloud and Kurento people to better define with them what we practically need for the Robotics demo. Please, read and edit the document to add all the information relevant and useful to describe the demo, what we will / would need to show. This always will help us to find what should be changed and to define more focused question . The shared document is here: https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit?pli=1# Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 16 giugno 2015 17:36 A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Proposal of Q to Kurento and Wirecloud We've had an answer from Luis to the e-mail from Davide concerning the set of questions for Kurento (which were part of the questions below). Luis asked further question and details about the demo. After that Pier has sent an e-mail to Luis and all the Robotics group to suggest working on a document to better describe step by step what we want to show in the Live demo. We are working now on this new document and will share a version of it by tomorrow; according to the suggestion from Pier, we can first refine this document and then we will be able to forward our questions to Wirecloud and Kurento, providing them with a more detailed description of what we want to show and we'll need for the Live demo. Best, Gianmario 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: marted? 16 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Proposal of Q to Kurento and Wirecloud Hi, I think they're ok. I'd just change "demo have few questions" by "demo and have a few questions". BR, Pepe. On 16/06/15 12:38, Bollano Gianmario wrote: Dear all, we are defining further details for the Robotics Live demo. Robotics Live demos consist of transmitting video from robots camera, controlling the robots with a Joystick from a Web interface, displaying robot status, their positioning, and their video stream. We are defining the architecture for the Robotics demo have few questions and hypothesis we need to check with you: 1. To use widgets to control Robots and displaying video from robots, can we use the public instance of Wirecloud in FIWARE LAB [our Hypothesis] or do we need to instantiate a dedicated Wirecloud instance (reserved only for Robotics demo in a specific VM)? 2. Will we be able to run different widgets in the same Wirecloud instance for different functions [our Hypothesis], e.g. to control the robot with a Joystick interface, to Initialize Robots configuration (that means writing few information using APIs to configure Robot environment), to display Robot positioning and data? 3. If we have 2 robots to transmitting Video streams, will we need two Application servers (one per stream), or just one [our Hypothesis]? Can we use the same Application server for video TX and RX endpoints [our Hypothesis]? 4. If we want to use a Kurento Widget in Wirecloud, can we assume that the Application server (to host Kurento client) is the same one embedded in Wirecloud [our Hypothesis] or do we need an external Application server? To manage two video streams transmitted by two robots, do we need two widgets? Can these widget use the same Application server? Best, Gianmmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- 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 Jun 19 10:44:07 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 19 Jun 2015 08:44:07 +0000 Subject: [Fiware-robotics] R: End-of-sprint demo In-Reply-To: <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> Hi Pepe and all, We are waiting some feedbacks about the proposal below for the next demo and the answers to the questions related to the new version of FIROS (we also needs the new version on FIROS in order to deploy it on our VM). I'm sending you (to Pepe and I?igo, in a private email) the OpenVPN certificate (and instructions) to install in your tutlebot in order to use our VM which is acting as OpenVPN-Server. Today (at most Monday) Fabio will send to the fiware-robotics list the package to install the PM_AGENT on your turtlebot's PC. BR, Davide -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: mercoled? 17 giugno 2015 18:03 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] I: End-of-sprint demo Hi Pepe and all, Q. What do you intend with the "dynamic addition and removal of robots"? Do you mean the dynamic addition and removal of the CB entity when the RCM_DRIVER notifies to FIROS the robot connection and disconnection? N.B. if it is correct, RCM_DRIVER will be completed at the end of this month, so we don't think that RCM_DRIVER-FIROS Interaction will be correctly tested for the begin of July in order to show them in a demo. For the begin of July RCM will be able to manage the following use case: --- HYPOTHESIS --- - Use a turtlebot where the turtlebot's PC with a WiFi /LTE-Internet-key where the PM_AGENT is already installed - A turtlebot is already manual provisioned in the Robotics Data with a specific service logic which is related to: - launch the ROS node "firos core.py PORT" on Server side (i.e. RCM_Master) Q. Does your new FIROS accept the PORT parameter for CBAPI and FCGAPI? Can you send us the new FIROS (and how do you expect the PORT parameter) in order to put it on the RCM_Master? - launch the ROS launcher "turtlebot_bringup minimal.launch" on Robot side Q. In order to use these turtlebot's ROS DRIVER we have modified the old FIROS hardcoded topic "turtle1/cmd_vel" (for turtlesim) in "mobile_base/commands/velocity" (for tutlebot) - The turtlebot's PC is off (or it is on and the WiFi/LTE connection is disabled). Does the new FIROS already use this topic? --- USE CASE --- - Robot CONNECTION: when the turtlebot's PC is switched on (or the WiFi/LTE connection is enabled) the PM_AGENT (on the Robot side) automatically connects to the PM_MASTER (on the Server side) - PM_MASTER (on the Server side) automatically creates the Service Space (Robot Clone) and starts inside it the service logic associated with the robot during its manual provisioning (depicted above) - When FIROS is started it directly creates the CB entity (in the future FIROS have to wait the notification from RCM_DRIVER about robot connection and have to notify to RCM_DRIVER the correct CB entity creation) - A web-app (e.g. an improved version of that used in the demo1) could: - poll the CB in order to populate a listbox of the connected robots (if a robot is connected the CB entity is present, otherwise the CB entity is not present) - the user can select a connected robot (we will show only a robot) and teleoperates it exploiting the CB (as demo1, maybe with other directions in addiction to FORWARD) - two buttons/divs to show additional information directly retrieved from the Robotics GE through the following RDAPI (request/response are exposed in https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit# ): -- Read platform (provisioned Robots): returns the list of the manual provisioned Robots in the Robotics GE and information about their connection status (this information could be shown before and after the robot connection) -- Read service space: returns the list of ROS nodes and ROS launchers which are currently running on the Service Space --- CONSIDERATION --- Robot DISCONNECTION: when the turtlebot's PC is switched off (or the WiFi/LTE connection is disabled) the PM_MASTER (on the Server side) and PM_AGENT (on the Robot side) are able to automatically clean the Service Space (Robot Clone) which was automatically created during the Robot CONNECTION. As said above, since RCM_DRIVER-FIROS Interaction will be NOT correctly tested, for this demo FIROS will be stopped (with SIGINT signal) without is being notified before (in the future FIROS have to wait the notification from RCM_DRIVER about robot disconnection and have to notify to RCM_DRIVER the correct CB entity deletion). Considering that, we don't know if it is advisable to show the robot disconnection phase, due to the CB entity could be not really deleted.. maybe FIROS could delete the CB entity cathing its termination phase (trapping SIGINT signal)? --- IMPORTANT --- Now we are using a TI VM which acts as RCM_Master and OpenVPN-Server and a TI turtlebot's PC acts as OpenVPN-Client. Since the common FIWARE Lab account is not yet ready we could prepare for ET an OpenVPN certificate in order to allow an ET turtlebot's PC acting as OpenVPN-Client of our OpenVPN-Server for your connection/disconnection tests. We can give to ET the OpenVPN certificate on Monday, meanwhile you can install the OpenVPN Client on you turtlebot's PC. We will also send you the package to install the PM_AGENT on your turtlebot's PC. What do you think about this kind of demo? BR, TI, Consoft -----Messaggio originale----- 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: marted? 16 giugno 2015 17:30 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] End-of-sprint demo Hi, In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? BR, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From jjaime at ikergune.com Fri Jun 19 11:44:33 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 19 Jun 2015 11:44:33 +0200 Subject: [Fiware-robotics] R: End-of-sprint demo References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, We agree on what you propose but, in order to demostrate the autodiscovery and filtering capabilities of FIROS, we are going to implement a mini-watchdog. Please confirm us if the robot will addressed to 10.82.99.0/24 or a narrower address range. We are working on providing you access to FIROS. BR, Pepe P.S.: sorry for double-mailing, Davide. On 19/06/15 10:44, Colombatto Davide wrote: > Hi Pepe and all, > > We are waiting some feedbacks about the proposal below for the next demo and the answers to the questions related to the new version of FIROS (we also needs the new version on FIROS in order to deploy it on our VM). > > I'm sending you (to Pepe and I?igo, in a private email) the OpenVPN certificate (and instructions) to install in your tutlebot in order to use our VM which is acting as OpenVPN-Server. > Today (at most Monday) Fabio will send to the fiware-robotics list the package to install the PM_AGENT on your turtlebot's PC. > > BR, > Davide > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide > Inviato: mercoled? 17 giugno 2015 18:03 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] I: End-of-sprint demo > > Hi Pepe and all, > > Q. What do you intend with the "dynamic addition and removal of robots"? Do you mean the dynamic addition and removal of the CB entity when the RCM_DRIVER notifies to FIROS the robot connection and disconnection? > N.B. if it is correct, RCM_DRIVER will be completed at the end of this month, so we don't think that RCM_DRIVER-FIROS Interaction will be correctly tested for the begin of July in order to show them in a demo. > > For the begin of July RCM will be able to manage the following use case: > --- HYPOTHESIS --- > - Use a turtlebot where the turtlebot's PC with a WiFi /LTE-Internet-key where the PM_AGENT is already installed > - A turtlebot is already manual provisioned in the Robotics Data with a specific service logic which is related to: > - launch the ROS node "firos core.py PORT" on Server side (i.e. RCM_Master) > Q. Does your new FIROS accept the PORT parameter for CBAPI and FCGAPI? Can you send us the new FIROS (and how do you expect the PORT parameter) in order to put it on the RCM_Master? > - launch the ROS launcher "turtlebot_bringup minimal.launch" on Robot side > Q. In order to use these turtlebot's ROS DRIVER we have modified the old FIROS hardcoded topic "turtle1/cmd_vel" (for turtlesim) in "mobile_base/commands/velocity" (for tutlebot) > - The turtlebot's PC is off (or it is on and the WiFi/LTE connection is disabled). Does the new FIROS already use this topic? > > --- USE CASE --- > - Robot CONNECTION: when the turtlebot's PC is switched on (or the WiFi/LTE connection is enabled) the PM_AGENT (on the Robot side) automatically connects to the PM_MASTER (on the Server side) > - PM_MASTER (on the Server side) automatically creates the Service Space (Robot Clone) and starts inside it the service logic associated with the robot during its manual provisioning (depicted above) > - When FIROS is started it directly creates the CB entity (in the future FIROS have to wait the notification from RCM_DRIVER about robot connection and have to notify to RCM_DRIVER the correct CB entity creation) > - A web-app (e.g. an improved version of that used in the demo1) could: > - poll the CB in order to populate a listbox of the connected robots (if a robot is connected the CB entity is present, otherwise the CB entity is not present) > - the user can select a connected robot (we will show only a robot) and teleoperates it exploiting the CB (as demo1, maybe with other directions in addiction to FORWARD) > - two buttons/divs to show additional information directly retrieved from the Robotics GE through the following RDAPI (request/response are exposed in https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit# ): > -- Read platform (provisioned Robots): returns the list of the manual provisioned Robots in the Robotics GE and information about their connection status (this information could be shown before and after the robot connection) > -- Read service space: returns the list of ROS nodes and ROS launchers which are currently running on the Service Space > > --- CONSIDERATION --- > Robot DISCONNECTION: when the turtlebot's PC is switched off (or the WiFi/LTE connection is disabled) the PM_MASTER (on the Server side) and PM_AGENT (on the Robot side) are able to automatically clean the Service Space (Robot Clone) which was automatically created during the Robot CONNECTION. > As said above, since RCM_DRIVER-FIROS Interaction will be NOT correctly tested, for this demo FIROS will be stopped (with SIGINT signal) without is being notified before (in the future FIROS have to wait the notification from RCM_DRIVER about robot disconnection and have to notify to RCM_DRIVER the correct CB entity deletion). Considering that, we don't know if it is advisable to show the robot disconnection phase, due to the CB entity could be not really deleted.. maybe FIROS could delete the CB entity cathing its termination phase (trapping SIGINT signal)? > > --- IMPORTANT --- > Now we are using a TI VM which acts as RCM_Master and OpenVPN-Server and a TI turtlebot's PC acts as OpenVPN-Client. > Since the common FIWARE Lab account is not yet ready we could prepare for ET an OpenVPN certificate in order to allow an ET turtlebot's PC acting as OpenVPN-Client of our OpenVPN-Server for your connection/disconnection tests. > We can give to ET the OpenVPN certificate on Monday, meanwhile you can install the OpenVPN Client on you turtlebot's PC. > We will also send you the package to install the PM_AGENT on your turtlebot's PC. > > > What do you think about this kind of demo? > > BR, > TI, Consoft > > > -----Messaggio originale----- > 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: marted? 16 giugno 2015 17:30 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] End-of-sprint demo > > Hi, > > In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. > > For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? > > BR, > Pepe > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From davide.colombatto at telecomitalia.it Fri Jun 19 12:31:37 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 19 Jun 2015 10:31:37 +0000 Subject: [Fiware-robotics] R: R: End-of-sprint demo In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> Hi, Can you explain what do you mean with "autodiscovery and filtering capabilities of FIROS" and mini-watchdog? I would just remind that: - Each FIROS instance is started/stopped by RCM passing it the port to use for CBAPI and FCFGAPI within the range of free ports (i.e. 10100-1010x). For this demo we will use only one Robot, so the used port will be the first one of the range. Since the FIROS instance will be started on Server Side (i.e. RCM_Master) you will also have the public IP to access it on FCFGAPI (in the same way the CB use CBAPI for the notifications). - FIROS creates/removes the CB entity as a result of a Robot connection/disconnection, so you can use the CB to know if the FIROS is up/down (i.e. the robot is connected/disconnected). We confirm that the configuration of our OpenVPN Server (i.e. RCM_Master) assigns addresses within the address range 10.82.99.0/24. TI -----Messaggio originale----- Da: Jose Jaime Ariza [mailto:jjaime at ikergune.com] Inviato: venerd? 19 giugno 2015 11:44 A: Colombatto Davide Oggetto: Re: R: End-of-sprint demo Hi, We agree on what you propose but, in order to demostrate the autodiscovery and filtering capabilities of FIROS, we are going to implement a mini-watchdog. Please confirm us if the robot will addressed to 10.82.99.0/24 or a narrower address range. We are working on providing you access to FIROS. BR, Pepe On 19/06/15 10:44, Colombatto Davide wrote: > Hi Pepe and all, > > We are waiting some feedbacks about the proposal below for the next demo and the answers to the questions related to the new version of FIROS (we also needs the new version on FIROS in order to deploy it on our VM). > > I'm sending you (to Pepe and I?igo, in a private email) the OpenVPN certificate (and instructions) to install in your tutlebot in order to use our VM which is acting as OpenVPN-Server. > Today (at most Monday) Fabio will send to the fiware-robotics list the package to install the PM_AGENT on your turtlebot's PC. > > BR, > Davide > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di > Colombatto Davide > Inviato: mercoled? 17 giugno 2015 18:03 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] I: End-of-sprint demo > > Hi Pepe and all, > > Q. What do you intend with the "dynamic addition and removal of robots"? Do you mean the dynamic addition and removal of the CB entity when the RCM_DRIVER notifies to FIROS the robot connection and disconnection? > N.B. if it is correct, RCM_DRIVER will be completed at the end of this month, so we don't think that RCM_DRIVER-FIROS Interaction will be correctly tested for the begin of July in order to show them in a demo. > > For the begin of July RCM will be able to manage the following use case: > --- HYPOTHESIS --- > - Use a turtlebot where the turtlebot's PC with a WiFi > /LTE-Internet-key where the PM_AGENT is already installed > - A turtlebot is already manual provisioned in the Robotics Data with a specific service logic which is related to: > - launch the ROS node "firos core.py PORT" on Server side (i.e. RCM_Master) > Q. Does your new FIROS accept the PORT parameter for CBAPI and FCGAPI? Can you send us the new FIROS (and how do you expect the PORT parameter) in order to put it on the RCM_Master? > - launch the ROS launcher "turtlebot_bringup minimal.launch" on Robot side > Q. In order to use these turtlebot's ROS DRIVER we > have modified the old FIROS hardcoded topic "turtle1/cmd_vel" (for > turtlesim) in "mobile_base/commands/velocity" (for tutlebot) > - The turtlebot's PC is off (or it is on and the WiFi/LTE connection is disabled). Does the new FIROS already use this topic? > > --- USE CASE --- > - Robot CONNECTION: when the turtlebot's PC is switched on (or the > WiFi/LTE connection is enabled) the PM_AGENT (on the Robot side) > automatically connects to the PM_MASTER (on the Server side) > - PM_MASTER (on the Server side) automatically creates the Service Space (Robot Clone) and starts inside it the service logic associated with the robot during its manual provisioning (depicted above) > - When FIROS is started it directly creates the CB entity (in > the future FIROS have to wait the notification from RCM_DRIVER about > robot connection and have to notify to RCM_DRIVER the correct CB > entity creation) > - A web-app (e.g. an improved version of that used in the demo1) could: > - poll the CB in order to populate a listbox of the connected robots (if a robot is connected the CB entity is present, otherwise the CB entity is not present) > - the user can select a connected robot (we will show only a robot) and teleoperates it exploiting the CB (as demo1, maybe with other directions in addiction to FORWARD) > - two buttons/divs to show additional information directly retrieved from the Robotics GE through the following RDAPI (request/response are exposed in https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit# ): > -- Read platform (provisioned Robots): returns the list of the manual provisioned Robots in the Robotics GE and information about their connection status (this information could be shown before and after the robot connection) > -- Read service space: returns the list of ROS nodes and ROS > launchers which are currently running on the Service Space > > --- CONSIDERATION --- > Robot DISCONNECTION: when the turtlebot's PC is switched off (or the WiFi/LTE connection is disabled) the PM_MASTER (on the Server side) and PM_AGENT (on the Robot side) are able to automatically clean the Service Space (Robot Clone) which was automatically created during the Robot CONNECTION. > As said above, since RCM_DRIVER-FIROS Interaction will be NOT correctly tested, for this demo FIROS will be stopped (with SIGINT signal) without is being notified before (in the future FIROS have to wait the notification from RCM_DRIVER about robot disconnection and have to notify to RCM_DRIVER the correct CB entity deletion). Considering that, we don't know if it is advisable to show the robot disconnection phase, due to the CB entity could be not really deleted.. maybe FIROS could delete the CB entity cathing its termination phase (trapping SIGINT signal)? > > --- IMPORTANT --- > Now we are using a TI VM which acts as RCM_Master and OpenVPN-Server and a TI turtlebot's PC acts as OpenVPN-Client. > Since the common FIWARE Lab account is not yet ready we could prepare for ET an OpenVPN certificate in order to allow an ET turtlebot's PC acting as OpenVPN-Client of our OpenVPN-Server for your connection/disconnection tests. > We can give to ET the OpenVPN certificate on Monday, meanwhile you can install the OpenVPN Client on you turtlebot's PC. > We will also send you the package to install the PM_AGENT on your turtlebot's PC. > > > What do you think about this kind of demo? > > BR, > TI, Consoft > > > -----Messaggio originale----- > 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: marted? 16 giugno 2015 17:30 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] End-of-sprint demo > > Hi, > > In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. > > For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? > > BR, > Pepe > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From jjaime at ikergune.com Fri Jun 19 12:57:09 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 19 Jun 2015 12:57:09 +0200 Subject: [Fiware-robotics] R: R: End-of-sprint demo References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, Once FIROS has been launch, we'd command it via FCFGAPI to run autodiscovery and autodiscover the robot. We won't rely on static configurations. The mini-watchdog will look for FIROS IP and port in RDAPI. If RDPI won't be available for the demo we'd do some some "address and port guessing". BR, Pepe On 19/06/15 12:31, Colombatto Davide wrote: > Hi, > > Can you explain what do you mean with "autodiscovery and filtering capabilities of FIROS" and mini-watchdog? > I would just remind that: > - Each FIROS instance is started/stopped by RCM passing it the port to use for CBAPI and FCFGAPI within the range of free ports (i.e. 10100-1010x). For this demo we will use only one Robot, so the used port will be the first one of the range. Since the FIROS instance will be started on Server Side (i.e. RCM_Master) you will also have the public IP to access it on FCFGAPI (in the same way the CB use CBAPI for the notifications). > - FIROS creates/removes the CB entity as a result of a Robot connection/disconnection, so you can use the CB to know if the FIROS is up/down (i.e. the robot is connected/disconnected). > > We confirm that the configuration of our OpenVPN Server (i.e. RCM_Master) assigns addresses within the address range 10.82.99.0/24. > > TI > > > -----Messaggio originale----- > Da: Jose Jaime Ariza [mailto:jjaime at ikergune.com] > Inviato: venerd? 19 giugno 2015 11:44 > A: Colombatto Davide > Oggetto: Re: R: End-of-sprint demo > > Hi, > > We agree on what you propose but, in order to demostrate the autodiscovery and filtering capabilities of FIROS, we are going to implement a mini-watchdog. Please confirm us if the robot will addressed to 10.82.99.0/24 or a narrower address range. > > We are working on providing you access to FIROS. > > BR, > Pepe > > On 19/06/15 10:44, Colombatto Davide wrote: >> Hi Pepe and all, >> >> We are waiting some feedbacks about the proposal below for the next demo and the answers to the questions related to the new version of FIROS (we also needs the new version on FIROS in order to deploy it on our VM). >> >> I'm sending you (to Pepe and I?igo, in a private email) the OpenVPN certificate (and instructions) to install in your tutlebot in order to use our VM which is acting as OpenVPN-Server. >> Today (at most Monday) Fabio will send to the fiware-robotics list the package to install the PM_AGENT on your turtlebot's PC. >> >> BR, >> Davide >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> Colombatto Davide >> Inviato: mercoled? 17 giugno 2015 18:03 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] I: End-of-sprint demo >> >> Hi Pepe and all, >> >> Q. What do you intend with the "dynamic addition and removal of robots"? Do you mean the dynamic addition and removal of the CB entity when the RCM_DRIVER notifies to FIROS the robot connection and disconnection? >> N.B. if it is correct, RCM_DRIVER will be completed at the end of this month, so we don't think that RCM_DRIVER-FIROS Interaction will be correctly tested for the begin of July in order to show them in a demo. >> >> For the begin of July RCM will be able to manage the following use case: >> --- HYPOTHESIS --- >> - Use a turtlebot where the turtlebot's PC with a WiFi >> /LTE-Internet-key where the PM_AGENT is already installed >> - A turtlebot is already manual provisioned in the Robotics Data with a specific service logic which is related to: >> - launch the ROS node "firos core.py PORT" on Server side (i.e. RCM_Master) >> Q. Does your new FIROS accept the PORT parameter for CBAPI and FCGAPI? Can you send us the new FIROS (and how do you expect the PORT parameter) in order to put it on the RCM_Master? >> - launch the ROS launcher "turtlebot_bringup minimal.launch" on Robot side >> Q. In order to use these turtlebot's ROS DRIVER we >> have modified the old FIROS hardcoded topic "turtle1/cmd_vel" (for >> turtlesim) in "mobile_base/commands/velocity" (for tutlebot) >> - The turtlebot's PC is off (or it is on and the WiFi/LTE connection is disabled). Does the new FIROS already use this topic? >> >> --- USE CASE --- >> - Robot CONNECTION: when the turtlebot's PC is switched on (or the >> WiFi/LTE connection is enabled) the PM_AGENT (on the Robot side) >> automatically connects to the PM_MASTER (on the Server side) >> - PM_MASTER (on the Server side) automatically creates the Service Space (Robot Clone) and starts inside it the service logic associated with the robot during its manual provisioning (depicted above) >> - When FIROS is started it directly creates the CB entity (in >> the future FIROS have to wait the notification from RCM_DRIVER about >> robot connection and have to notify to RCM_DRIVER the correct CB >> entity creation) >> - A web-app (e.g. an improved version of that used in the demo1) could: >> - poll the CB in order to populate a listbox of the connected robots (if a robot is connected the CB entity is present, otherwise the CB entity is not present) >> - the user can select a connected robot (we will show only a robot) and teleoperates it exploiting the CB (as demo1, maybe with other directions in addiction to FORWARD) >> - two buttons/divs to show additional information directly retrieved from the Robotics GE through the following RDAPI (request/response are exposed in https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit# ): >> -- Read platform (provisioned Robots): returns the list of the manual provisioned Robots in the Robotics GE and information about their connection status (this information could be shown before and after the robot connection) >> -- Read service space: returns the list of ROS nodes and ROS >> launchers which are currently running on the Service Space >> >> --- CONSIDERATION --- >> Robot DISCONNECTION: when the turtlebot's PC is switched off (or the WiFi/LTE connection is disabled) the PM_MASTER (on the Server side) and PM_AGENT (on the Robot side) are able to automatically clean the Service Space (Robot Clone) which was automatically created during the Robot CONNECTION. >> As said above, since RCM_DRIVER-FIROS Interaction will be NOT correctly tested, for this demo FIROS will be stopped (with SIGINT signal) without is being notified before (in the future FIROS have to wait the notification from RCM_DRIVER about robot disconnection and have to notify to RCM_DRIVER the correct CB entity deletion). Considering that, we don't know if it is advisable to show the robot disconnection phase, due to the CB entity could be not really deleted.. maybe FIROS could delete the CB entity cathing its termination phase (trapping SIGINT signal)? >> >> --- IMPORTANT --- >> Now we are using a TI VM which acts as RCM_Master and OpenVPN-Server and a TI turtlebot's PC acts as OpenVPN-Client. >> Since the common FIWARE Lab account is not yet ready we could prepare for ET an OpenVPN certificate in order to allow an ET turtlebot's PC acting as OpenVPN-Client of our OpenVPN-Server for your connection/disconnection tests. >> We can give to ET the OpenVPN certificate on Monday, meanwhile you can install the OpenVPN Client on you turtlebot's PC. >> We will also send you the package to install the PM_AGENT on your turtlebot's PC. >> >> >> What do you think about this kind of demo? >> >> BR, >> TI, Consoft >> >> >> -----Messaggio originale----- >> 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: marted? 16 giugno 2015 17:30 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] End-of-sprint demo >> >> Hi, >> >> In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. >> >> For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? >> >> BR, >> Pepe >> >> -- >> Jos? Jaime Ariza >> R&D Engineer >> +34 696604288 >> Ikergune, Etxe-Tar group >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> 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. >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From davide.colombatto at telecomitalia.it Fri Jun 19 14:44:38 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 19 Jun 2015 12:44:38 +0000 Subject: [Fiware-robotics] R: R: R: End-of-sprint demo In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> Hi, current static configuration about the used port by FIROS (i.e. 10100 or another of the range) is related to the fact that the old version of FIROS was not parametric. When we will have the new version of FIROS, RCM will be able to start FIROS passing it the port to use (chosen within the range of free ports) and FIROS should behave as we agreed in OpenSpec Draft. A question for you: when a FIROS instance is started it subscribes itself to the CB informing which is the "public IP and PORT" (i.e. CBAPI) that the CB should use to notify it. Considering that CBAPI uses the same public IP and PORT of FCFGAPI, cannot you be able to obtain these information directly through the CB? However, with the new version of FIROS, the port used to start FIROS will be also stored by RCM in the Robotics Config Data and, if it is really necessary, we can give you this information with the RDAPI Service Space N.B. RDAPI related to "Read platform (provisioned Robots)" and "Read Service Space" are already implemented for this demo. Davide -----Messaggio originale----- 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: venerd? 19 giugno 2015 12:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: End-of-sprint demo Hi, Once FIROS has been launch, we'd command it via FCFGAPI to run autodiscovery and autodiscover the robot. We won't rely on static configurations. The mini-watchdog will look for FIROS IP and port in RDAPI. If RDPI won't be available for the demo we'd do some some "address and port guessing". BR, Pepe On 19/06/15 12:31, Colombatto Davide wrote: > Hi, > > Can you explain what do you mean with "autodiscovery and filtering capabilities of FIROS" and mini-watchdog? > I would just remind that: > - Each FIROS instance is started/stopped by RCM passing it the port to use for CBAPI and FCFGAPI within the range of free ports (i.e. 10100-1010x). For this demo we will use only one Robot, so the used port will be the first one of the range. Since the FIROS instance will be started on Server Side (i.e. RCM_Master) you will also have the public IP to access it on FCFGAPI (in the same way the CB use CBAPI for the notifications). > - FIROS creates/removes the CB entity as a result of a Robot connection/disconnection, so you can use the CB to know if the FIROS is up/down (i.e. the robot is connected/disconnected). > > We confirm that the configuration of our OpenVPN Server (i.e. RCM_Master) assigns addresses within the address range 10.82.99.0/24. > > TI > > > -----Messaggio originale----- > Da: Jose Jaime Ariza [mailto:jjaime at ikergune.com] > Inviato: venerd? 19 giugno 2015 11:44 > A: Colombatto Davide > Oggetto: Re: R: End-of-sprint demo > > Hi, > > We agree on what you propose but, in order to demostrate the autodiscovery and filtering capabilities of FIROS, we are going to implement a mini-watchdog. Please confirm us if the robot will addressed to 10.82.99.0/24 or a narrower address range. > > We are working on providing you access to FIROS. > > BR, > Pepe > > On 19/06/15 10:44, Colombatto Davide wrote: >> Hi Pepe and all, >> >> We are waiting some feedbacks about the proposal below for the next demo and the answers to the questions related to the new version of FIROS (we also needs the new version on FIROS in order to deploy it on our VM). >> >> I'm sending you (to Pepe and I?igo, in a private email) the OpenVPN certificate (and instructions) to install in your tutlebot in order to use our VM which is acting as OpenVPN-Server. >> Today (at most Monday) Fabio will send to the fiware-robotics list the package to install the PM_AGENT on your turtlebot's PC. >> >> BR, >> Davide >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> Colombatto Davide >> Inviato: mercoled? 17 giugno 2015 18:03 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] I: End-of-sprint demo >> >> Hi Pepe and all, >> >> Q. What do you intend with the "dynamic addition and removal of robots"? Do you mean the dynamic addition and removal of the CB entity when the RCM_DRIVER notifies to FIROS the robot connection and disconnection? >> N.B. if it is correct, RCM_DRIVER will be completed at the end of this month, so we don't think that RCM_DRIVER-FIROS Interaction will be correctly tested for the begin of July in order to show them in a demo. >> >> For the begin of July RCM will be able to manage the following use case: >> --- HYPOTHESIS --- >> - Use a turtlebot where the turtlebot's PC with a WiFi >> /LTE-Internet-key where the PM_AGENT is already installed >> - A turtlebot is already manual provisioned in the Robotics Data with a specific service logic which is related to: >> - launch the ROS node "firos core.py PORT" on Server side (i.e. RCM_Master) >> Q. Does your new FIROS accept the PORT parameter for CBAPI and FCGAPI? Can you send us the new FIROS (and how do you expect the PORT parameter) in order to put it on the RCM_Master? >> - launch the ROS launcher "turtlebot_bringup minimal.launch" on Robot side >> Q. In order to use these turtlebot's ROS DRIVER we >> have modified the old FIROS hardcoded topic "turtle1/cmd_vel" (for >> turtlesim) in "mobile_base/commands/velocity" (for tutlebot) >> - The turtlebot's PC is off (or it is on and the WiFi/LTE connection is disabled). Does the new FIROS already use this topic? >> >> --- USE CASE --- >> - Robot CONNECTION: when the turtlebot's PC is switched on (or the >> WiFi/LTE connection is enabled) the PM_AGENT (on the Robot side) >> automatically connects to the PM_MASTER (on the Server side) >> - PM_MASTER (on the Server side) automatically creates the Service Space (Robot Clone) and starts inside it the service logic associated with the robot during its manual provisioning (depicted above) >> - When FIROS is started it directly creates the CB entity (in >> the future FIROS have to wait the notification from RCM_DRIVER about >> robot connection and have to notify to RCM_DRIVER the correct CB >> entity creation) >> - A web-app (e.g. an improved version of that used in the demo1) could: >> - poll the CB in order to populate a listbox of the connected robots (if a robot is connected the CB entity is present, otherwise the CB entity is not present) >> - the user can select a connected robot (we will show only a robot) and teleoperates it exploiting the CB (as demo1, maybe with other directions in addiction to FORWARD) >> - two buttons/divs to show additional information directly retrieved from the Robotics GE through the following RDAPI (request/response are exposed in https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit# ): >> -- Read platform (provisioned Robots): returns the list of the manual provisioned Robots in the Robotics GE and information about their connection status (this information could be shown before and after the robot connection) >> -- Read service space: returns the list of ROS nodes and ROS >> launchers which are currently running on the Service Space >> >> --- CONSIDERATION --- >> Robot DISCONNECTION: when the turtlebot's PC is switched off (or the WiFi/LTE connection is disabled) the PM_MASTER (on the Server side) and PM_AGENT (on the Robot side) are able to automatically clean the Service Space (Robot Clone) which was automatically created during the Robot CONNECTION. >> As said above, since RCM_DRIVER-FIROS Interaction will be NOT correctly tested, for this demo FIROS will be stopped (with SIGINT signal) without is being notified before (in the future FIROS have to wait the notification from RCM_DRIVER about robot disconnection and have to notify to RCM_DRIVER the correct CB entity deletion). Considering that, we don't know if it is advisable to show the robot disconnection phase, due to the CB entity could be not really deleted.. maybe FIROS could delete the CB entity cathing its termination phase (trapping SIGINT signal)? >> >> --- IMPORTANT --- >> Now we are using a TI VM which acts as RCM_Master and OpenVPN-Server and a TI turtlebot's PC acts as OpenVPN-Client. >> Since the common FIWARE Lab account is not yet ready we could prepare for ET an OpenVPN certificate in order to allow an ET turtlebot's PC acting as OpenVPN-Client of our OpenVPN-Server for your connection/disconnection tests. >> We can give to ET the OpenVPN certificate on Monday, meanwhile you can install the OpenVPN Client on you turtlebot's PC. >> We will also send you the package to install the PM_AGENT on your turtlebot's PC. >> >> >> What do you think about this kind of demo? >> >> BR, >> TI, Consoft >> >> >> -----Messaggio originale----- >> 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: marted? 16 giugno 2015 17:30 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] End-of-sprint demo >> >> Hi, >> >> In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. >> >> For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? >> >> BR, >> Pepe >> >> -- >> Jos? Jaime Ariza >> R&D Engineer >> +34 696604288 >> Ikergune, Etxe-Tar group >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> 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. >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From fabio.dibenedetto at consoft.it Fri Jun 19 18:20:39 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Fri, 19 Jun 2015 16:20:39 +0000 Subject: [Fiware-robotics] rcm_platform v2 In-Reply-To: <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> Message-ID: <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> Hi guys, here is the new version of rcm_platform. To install it copy the zip on your turtlebot - scp rcm_platform.zip turtlebot at ip_address:. and unzip it (you can do it where you want because this is the installer and it will put all the files where are needed) - unzip rcm_platform.zip Once extracted the package you will have a folder named rcm_platform_pkg; go into it and launch install.sh - cd rcm_platform_pkg - ./install.sh This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. I'd ask you to answer n or no when the script ask to say if your instance is the master. There has to be only one master and is on the TI machine where is the VPN server. Then you have to give a name to your platform node: please, use "turtlebotET" because we already have manually provisioned it. It is provisioned with a custom service logic named "fiware_demo2" which starts a service space (with the same name of the robot), a firos instance on server side and the turtlebot ros driver on the robot side. The firos instance is the old one until we can deploy the new one. Your platform node should a robot, so when asked answer y yes or press only enter (the installer put the default answer between [] so if you push enter that value will be used). The default address of the master is calculated using the tun0 interface so you have the vpn configuration already done to do this installation. The final step of the installation put rcm as daemon in your ubuntu machine and start the compilation of rcmp workspace. At the end you can decide if already run the rcm node or if you want wait and start it manually later (sudo service rcmpd start) I hope this is clear but if I missed something ask me Last thing: I've redone the zip to add the password "robotics" Have a nice week end -------------- next part -------------- A non-text attachment was scrubbed... Name: rcm_platform.zip Type: application/x-zip-compressed Size: 55915 bytes Desc: rcm_platform.zip URL: From jjaime at ikergune.com Mon Jun 22 12:33:32 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Mon, 22 Jun 2015 12:33:32 +0200 Subject: [Fiware-robotics] R: rcm_platform v2 References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB5BB7F@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, I've made some tests with a virtual machine. The installation went smoothly (I'd add "chmod +x *.sh" to the guidelines you sent) and it looks like the rcmpd is working, but I cannot get information from the RCM master (RDAPI). The installation script is tellimng me that the RCM Master is in 10.82.99.1 and I've tried 130.206.114.100 also. We had to change the IP of our CB, the new one is 130.206.122.27 but we'd prefer to use yours. Thank you very much, Pepe On 19/06/15 18:46, Colombatto Davide wrote: > Hi, > > only a clarification about the sentence "The firos instance is the old one until we can deploy the new one"; as we said in the new demo proposal the old FIROS code is modified as following: > - the topic is modified from the turtlesim one ("turtle1/cmd_vel") to the turtlebot one ("mobile_base/commands/velocity") > - the current CB instance used is that at 130.206.114.100:1026; we created this our CB instance (on Spain2 node) because your old one didn't work (when it will be up again we can reuse it if you want). > > Using this configuration we have done many tests, also using your old web-app of the first demo (i.e. using chrome disabling the security option to avoid cross-domain issues and publishing to the CB instance at 130.206.114.100:1026), and it seems to work good (e.g. no latency btw the web-app's FORWARD command and the turtlebot's movement). > > BR, > Davide > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: venerd? 19 giugno 2015 18:21 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] rcm_platform v2 > > Hi guys, > here is the new version of rcm_platform. > To install it copy the zip on your turtlebot > - scp rcm_platform.zip turtlebot at ip_address:. > and unzip it (you can do it where you want because this is the installer and it will put all the files where are needed) > - unzip rcm_platform.zip > Once extracted the package you will have a folder named rcm_platform_pkg; go into it and launch install.sh > - cd rcm_platform_pkg > - ./install.sh > > This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. > I'd ask you to answer n or no when the script ask to say if your instance is the master. There has to be only one master and is on the TI machine where is the VPN server. Then you have to give a name to your platform node: please, use "turtlebotET" because we already have manually provisioned it. It is provisioned with a custom service logic named "fiware_demo2" which starts a service space (with the same name of the robot), a firos instance on server side and the turtlebot ros driver on the robot side. The firos instance is the old one until we can deploy the new one. Your platform node should a robot, so when asked answer y yes or press only enter (the installer put the default answer between [] so if you push enter that value will be used). The default address of the master is calculated using the tun0 interface so you have the vpn configuration already done to do this installation. The final step of the installation put rcm as daemon in your ubuntu machine and start the compilatio > n of rcmp workspace. At the end you can decide if already run the rcm node or if you want wait and start it manually later (sudo service rcmpd start) > > I hope this is clear but if I missed something ask me > > Last thing: I've redone the zip to add the password "robotics" > > Have a nice week end > > > > 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. > > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From jjaime at ikergune.com Mon Jun 22 12:50:48 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Mon, 22 Jun 2015 12:50:48 +0200 Subject: [Fiware-robotics] R: R: R: End-of-sprint demo References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, You must tell CB the destination of the notification each time a subscription is created, so FIROS must know its public IP before creating any subscription to CB, so we can't retrieve FIROS public IP via CB. BR, Pepe On 19/06/15 14:44, Colombatto Davide wrote: > Hi, > > current static configuration about the used port by FIROS (i.e. 10100 or another of the range) is related to the fact that the old version of FIROS was not parametric. > When we will have the new version of FIROS, RCM will be able to start FIROS passing it the port to use (chosen within the range of free ports) and FIROS should behave as we agreed in OpenSpec Draft. > > A question for you: when a FIROS instance is started it subscribes itself to the CB informing which is the "public IP and PORT" (i.e. CBAPI) that the CB should use to notify it. Considering that CBAPI uses the same public IP and PORT of FCFGAPI, cannot you be able to obtain these information directly through the CB? > > However, with the new version of FIROS, the port used to start FIROS will be also stored by RCM in the Robotics Config Data and, if it is really necessary, we can give you this information with the RDAPI Service Space > N.B. RDAPI related to "Read platform (provisioned Robots)" and "Read Service Space" are already implemented for this demo. > > Davide > > > -----Messaggio originale----- > 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: venerd? 19 giugno 2015 12:57 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: R: End-of-sprint demo > > Hi, > > Once FIROS has been launch, we'd command it via FCFGAPI to run autodiscovery and autodiscover the robot. We won't rely on static configurations. The mini-watchdog will look for FIROS IP and port in RDAPI. If RDPI won't be available for the demo we'd do some some "address and port guessing". > > BR, > Pepe > > On 19/06/15 12:31, Colombatto Davide wrote: >> Hi, >> >> Can you explain what do you mean with "autodiscovery and filtering capabilities of FIROS" and mini-watchdog? >> I would just remind that: >> - Each FIROS instance is started/stopped by RCM passing it the port to use for CBAPI and FCFGAPI within the range of free ports (i.e. 10100-1010x). For this demo we will use only one Robot, so the used port will be the first one of the range. Since the FIROS instance will be started on Server Side (i.e. RCM_Master) you will also have the public IP to access it on FCFGAPI (in the same way the CB use CBAPI for the notifications). >> - FIROS creates/removes the CB entity as a result of a Robot connection/disconnection, so you can use the CB to know if the FIROS is up/down (i.e. the robot is connected/disconnected). >> >> We confirm that the configuration of our OpenVPN Server (i.e. RCM_Master) assigns addresses within the address range 10.82.99.0/24. >> >> TI >> >> >> -----Messaggio originale----- >> Da: Jose Jaime Ariza [mailto:jjaime at ikergune.com] >> Inviato: venerd? 19 giugno 2015 11:44 >> A: Colombatto Davide >> Oggetto: Re: R: End-of-sprint demo >> >> Hi, >> >> We agree on what you propose but, in order to demostrate the autodiscovery and filtering capabilities of FIROS, we are going to implement a mini-watchdog. Please confirm us if the robot will addressed to 10.82.99.0/24 or a narrower address range. >> >> We are working on providing you access to FIROS. >> >> BR, >> Pepe >> >> On 19/06/15 10:44, Colombatto Davide wrote: >>> Hi Pepe and all, >>> >>> We are waiting some feedbacks about the proposal below for the next demo and the answers to the questions related to the new version of FIROS (we also needs the new version on FIROS in order to deploy it on our VM). >>> >>> I'm sending you (to Pepe and I?igo, in a private email) the OpenVPN certificate (and instructions) to install in your tutlebot in order to use our VM which is acting as OpenVPN-Server. >>> Today (at most Monday) Fabio will send to the fiware-robotics list the package to install the PM_AGENT on your turtlebot's PC. >>> >>> BR, >>> Davide >>> >>> >>> -----Messaggio originale----- >>> Da: fiware-robotics-bounces at lists.fi-ware.org >>> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >>> Colombatto Davide >>> Inviato: mercoled? 17 giugno 2015 18:03 >>> A: fiware-robotics at lists.fi-ware.org >>> Oggetto: [Fiware-robotics] I: End-of-sprint demo >>> >>> Hi Pepe and all, >>> >>> Q. What do you intend with the "dynamic addition and removal of robots"? Do you mean the dynamic addition and removal of the CB entity when the RCM_DRIVER notifies to FIROS the robot connection and disconnection? >>> N.B. if it is correct, RCM_DRIVER will be completed at the end of this month, so we don't think that RCM_DRIVER-FIROS Interaction will be correctly tested for the begin of July in order to show them in a demo. >>> >>> For the begin of July RCM will be able to manage the following use case: >>> --- HYPOTHESIS --- >>> - Use a turtlebot where the turtlebot's PC with a WiFi >>> /LTE-Internet-key where the PM_AGENT is already installed >>> - A turtlebot is already manual provisioned in the Robotics Data with a specific service logic which is related to: >>> - launch the ROS node "firos core.py PORT" on Server side (i.e. RCM_Master) >>> Q. Does your new FIROS accept the PORT parameter for CBAPI and FCGAPI? Can you send us the new FIROS (and how do you expect the PORT parameter) in order to put it on the RCM_Master? >>> - launch the ROS launcher "turtlebot_bringup minimal.launch" on Robot side >>> Q. In order to use these turtlebot's ROS DRIVER we >>> have modified the old FIROS hardcoded topic "turtle1/cmd_vel" (for >>> turtlesim) in "mobile_base/commands/velocity" (for tutlebot) >>> - The turtlebot's PC is off (or it is on and the WiFi/LTE connection is disabled). Does the new FIROS already use this topic? >>> >>> --- USE CASE --- >>> - Robot CONNECTION: when the turtlebot's PC is switched on (or the >>> WiFi/LTE connection is enabled) the PM_AGENT (on the Robot side) >>> automatically connects to the PM_MASTER (on the Server side) >>> - PM_MASTER (on the Server side) automatically creates the Service Space (Robot Clone) and starts inside it the service logic associated with the robot during its manual provisioning (depicted above) >>> - When FIROS is started it directly creates the CB entity (in >>> the future FIROS have to wait the notification from RCM_DRIVER about >>> robot connection and have to notify to RCM_DRIVER the correct CB >>> entity creation) >>> - A web-app (e.g. an improved version of that used in the demo1) could: >>> - poll the CB in order to populate a listbox of the connected robots (if a robot is connected the CB entity is present, otherwise the CB entity is not present) >>> - the user can select a connected robot (we will show only a robot) and teleoperates it exploiting the CB (as demo1, maybe with other directions in addiction to FORWARD) >>> - two buttons/divs to show additional information directly retrieved from the Robotics GE through the following RDAPI (request/response are exposed in https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit# ): >>> -- Read platform (provisioned Robots): returns the list of the manual provisioned Robots in the Robotics GE and information about their connection status (this information could be shown before and after the robot connection) >>> -- Read service space: returns the list of ROS nodes and ROS >>> launchers which are currently running on the Service Space >>> >>> --- CONSIDERATION --- >>> Robot DISCONNECTION: when the turtlebot's PC is switched off (or the WiFi/LTE connection is disabled) the PM_MASTER (on the Server side) and PM_AGENT (on the Robot side) are able to automatically clean the Service Space (Robot Clone) which was automatically created during the Robot CONNECTION. >>> As said above, since RCM_DRIVER-FIROS Interaction will be NOT correctly tested, for this demo FIROS will be stopped (with SIGINT signal) without is being notified before (in the future FIROS have to wait the notification from RCM_DRIVER about robot disconnection and have to notify to RCM_DRIVER the correct CB entity deletion). Considering that, we don't know if it is advisable to show the robot disconnection phase, due to the CB entity could be not really deleted.. maybe FIROS could delete the CB entity cathing its termination phase (trapping SIGINT signal)? >>> >>> --- IMPORTANT --- >>> Now we are using a TI VM which acts as RCM_Master and OpenVPN-Server and a TI turtlebot's PC acts as OpenVPN-Client. >>> Since the common FIWARE Lab account is not yet ready we could prepare for ET an OpenVPN certificate in order to allow an ET turtlebot's PC acting as OpenVPN-Client of our OpenVPN-Server for your connection/disconnection tests. >>> We can give to ET the OpenVPN certificate on Monday, meanwhile you can install the OpenVPN Client on you turtlebot's PC. >>> We will also send you the package to install the PM_AGENT on your turtlebot's PC. >>> >>> >>> What do you think about this kind of demo? >>> >>> BR, >>> TI, Consoft >>> >>> >>> -----Messaggio originale----- >>> 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: marted? 16 giugno 2015 17:30 >>> A: fiware-robotics at lists.fi-ware.org >>> Oggetto: [Fiware-robotics] End-of-sprint demo >>> >>> Hi, >>> >>> In the last end-of-sprint demo we performed, we show basic FIROS and RCM functionalities. >>> >>> For this new demo we should show new functionalities. In FIROS side we can show whitelist control and the dynamic addition and removal of robots. What new functionalities related with RCM could we show? >>> >>> BR, >>> Pepe >>> >>> -- >>> Jos? Jaime Ariza >>> R&D Engineer >>> +34 696604288 >>> Ikergune, Etxe-Tar group >>> >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org >>> https://lists.fi-ware.org/listinfo/fiware-robotics >>> >>> 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. >>> >>> _______________________________________________ >>> Fiware-robotics mailing list >>> Fiware-robotics at lists.fi-ware.org >>> https://lists.fi-ware.org/listinfo/fiware-robotics >>> >> -- >> Jos? Jaime Ariza >> R&D Engineer >> +34 696604288 >> Ikergune, Etxe-Tar group >> >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From davide.colombatto at telecomitalia.it Mon Jun 22 12:53:11 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Mon, 22 Jun 2015 10:53:11 +0000 Subject: [Fiware-robotics] R: R: rcm_platform v2 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB5BB7F@TELMBB006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD35416F70801@telmbc006ba020.telecomitalia.local> Hi Pepe, 130.206.114.100 is the IP of the CB only whereas the RCM_MASTER is a TI-VM. You can (and we can also show in the demo) the information retrieved directly by the Robotics Data Mgmt (look at https://forge.fiware.org/plugins/mediawiki/wiki/fiwarei2nd/index.php/FIWARE.ArchitectureDescription.I2ND.Robotics#Architecture). In particular you can use the RDAPI depicted in OpenSpecDraft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#), changing "MASTER_WAN_public_IP" in "jolcrab-platform.ddns.net", related to: - Read platform (provisioned Robots) - Your robot will be shown as "pi_name":"turtlebotET" - "connected":true: the Robot's PM_AGENT is connected to the PM_MASTER - "paired":true: the Robot is paired with a Server (i.e. always the Master for this Major Release) - Read service space passing as GET parameter ss_name=turtlebotET - Conventionally the Service Space automatically created for a connected robot has the same name of the robot - Obviously you can use this API only if the robot is currently connected (i.e. the Service Space in created) After the PM_AGENT is installed on your turtlebot's PC you have only to switch on/off the turtlebot'PC (or just to switch on/off the WiFi connection) and the correct service logic (FIROS on Server side and turtlebot's DRIVER on Robot side) should be started by the PM_MASTER. Please, also consider that the actual RCM implementation requires about 1 minute to recognize (i.e. to be sure to correctly identify) a Robot connection/disconnection and to do the relative tasks (i.e. creating/deleting the Service Space). Let we know, D -----Messaggio originale----- 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: luned? 22 giugno 2015 12:34 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: rcm_platform v2 Hi, I've made some tests with a virtual machine. The installation went smoothly (I'd add "chmod +x *.sh" to the guidelines you sent) and it looks like the rcmpd is working, but I cannot get information from the RCM master (RDAPI). The installation script is tellimng me that the RCM Master is in 10.82.99.1 and I've tried 130.206.114.100 also. We had to change the IP of our CB, the new one is 130.206.122.27 but we'd prefer to use yours. Thank you very much, Pepe On 19/06/15 18:46, Colombatto Davide wrote: > Hi, > > only a clarification about the sentence "The firos instance is the old one until we can deploy the new one"; as we said in the new demo proposal the old FIROS code is modified as following: > - the topic is modified from the turtlesim one ("turtle1/cmd_vel") to > the turtlebot one ("mobile_base/commands/velocity") > - the current CB instance used is that at 130.206.114.100:1026; we created this our CB instance (on Spain2 node) because your old one didn't work (when it will be up again we can reuse it if you want). > > Using this configuration we have done many tests, also using your old web-app of the first demo (i.e. using chrome disabling the security option to avoid cross-domain issues and publishing to the CB instance at 130.206.114.100:1026), and it seems to work good (e.g. no latency btw the web-app's FORWARD command and the turtlebot's movement). > > BR, > Davide > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di > fabio.dibenedetto at consoft.it > Inviato: venerd? 19 giugno 2015 18:21 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] rcm_platform v2 > > Hi guys, > here is the new version of rcm_platform. > To install it copy the zip on your turtlebot > - scp rcm_platform.zip turtlebot at ip_address:. > and unzip it (you can do it where you want because this is the > installer and it will put all the files where are needed) > - unzip rcm_platform.zip > Once extracted the package you will have a folder named > rcm_platform_pkg; go into it and launch install.sh > - cd rcm_platform_pkg > - ./install.sh > > This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. > I'd ask you to answer n or no when the script ask to say if your > instance is the master. There has to be only one master and is on the > TI machine where is the VPN server. Then you have to give a name to > your platform node: please, use "turtlebotET" because we already have > manually provisioned it. It is provisioned with a custom service logic > named "fiware_demo2" which starts a service space (with the same name > of the robot), a firos instance on server side and the turtlebot ros > driver on the robot side. The firos instance is the old one until we > can deploy the new one. Your platform node should a robot, so when > asked answer y yes or press only enter (the installer put the default > answer between [] so if you push enter that value will be used). The > default address of the master is calculated using the tun0 interface > so you have the vpn configuration already done to do this > installation. The final step of the installation put rcm as daemon in > your ubuntu machine and start the compilatio n of rcmp workspace. At > the end you can decide if already run the rcm node or if you want wait > and start it manually later (sudo service rcmpd start) > > I hope this is clear but if I missed something ask me > > Last thing: I've redone the zip to add the password "robotics" > > Have a nice week end > > > > 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. > > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From jjaime at ikergune.com Mon Jun 22 17:09:35 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Mon, 22 Jun 2015 17:09:35 +0200 Subject: [Fiware-robotics] R: R: rcm_platform v2 References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB5BB7F@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F70801@telmbc006ba020.telecomitalia.local> Message-ID: Thank you very much Davide. I've found one bug (I believe it is a bug) in the installer: /usr/local/bin/rcmp_launcher hasn't got +x persmissions. I had to add it manually. After starting rcmpd the robot appears as connected and paired but, a minute or two after that, "python /usr/local/bin/rcmp_launcher" starts eating 99.9% of a CPU core. The machine where I'm performing the test doesn't have FIROS or any other ROS node running. I'll try in the real turtlebot and let you know. BR, Pepe On 22/06/15 12:53, Colombatto Davide wrote: > Hi Pepe, > > 130.206.114.100 is the IP of the CB only whereas the RCM_MASTER is a TI-VM. > > You can (and we can also show in the demo) the information retrieved directly by the Robotics Data Mgmt (look at https://forge.fiware.org/plugins/mediawiki/wiki/fiwarei2nd/index.php/FIWARE.ArchitectureDescription.I2ND.Robotics#Architecture). > In particular you can use the RDAPI depicted in OpenSpecDraft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#), changing "MASTER_WAN_public_IP" in "jolcrab-platform.ddns.net", related to: > - Read platform (provisioned Robots) > - Your robot will be shown as "pi_name":"turtlebotET" > - "connected":true: the Robot's PM_AGENT is connected to the PM_MASTER > - "paired":true: the Robot is paired with a Server (i.e. always the Master for this Major Release) > - Read service space passing as GET parameter ss_name=turtlebotET > - Conventionally the Service Space automatically created for a connected robot has the same name of the robot > - Obviously you can use this API only if the robot is currently connected (i.e. the Service Space in created) > > After the PM_AGENT is installed on your turtlebot's PC you have only to switch on/off the turtlebot'PC (or just to switch on/off the WiFi connection) and the correct service logic (FIROS on Server side and turtlebot's DRIVER on Robot side) should be started by the PM_MASTER. > Please, also consider that the actual RCM implementation requires about 1 minute to recognize (i.e. to be sure to correctly identify) a Robot connection/disconnection and to do the relative tasks (i.e. creating/deleting the Service Space). > > Let we know, > D > > > -----Messaggio originale----- > 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: luned? 22 giugno 2015 12:34 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: rcm_platform v2 > > Hi, > > I've made some tests with a virtual machine. The installation went smoothly (I'd add "chmod +x *.sh" to the guidelines you sent) and it looks like the rcmpd is working, but I cannot get information from the RCM master (RDAPI). The installation script is tellimng me that the RCM Master is in 10.82.99.1 and I've tried 130.206.114.100 also. > > We had to change the IP of our CB, the new one is 130.206.122.27 but we'd prefer to use yours. > > Thank you very much, > Pepe > > On 19/06/15 18:46, Colombatto Davide wrote: >> Hi, >> >> only a clarification about the sentence "The firos instance is the old one until we can deploy the new one"; as we said in the new demo proposal the old FIROS code is modified as following: >> - the topic is modified from the turtlesim one ("turtle1/cmd_vel") to >> the turtlebot one ("mobile_base/commands/velocity") >> - the current CB instance used is that at 130.206.114.100:1026; we created this our CB instance (on Spain2 node) because your old one didn't work (when it will be up again we can reuse it if you want). >> >> Using this configuration we have done many tests, also using your old web-app of the first demo (i.e. using chrome disabling the security option to avoid cross-domain issues and publishing to the CB instance at 130.206.114.100:1026), and it seems to work good (e.g. no latency btw the web-app's FORWARD command and the turtlebot's movement). >> >> BR, >> Davide >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> fabio.dibenedetto at consoft.it >> Inviato: venerd? 19 giugno 2015 18:21 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] rcm_platform v2 >> >> Hi guys, >> here is the new version of rcm_platform. >> To install it copy the zip on your turtlebot >> - scp rcm_platform.zip turtlebot at ip_address:. >> and unzip it (you can do it where you want because this is the >> installer and it will put all the files where are needed) >> - unzip rcm_platform.zip >> Once extracted the package you will have a folder named >> rcm_platform_pkg; go into it and launch install.sh >> - cd rcm_platform_pkg >> - ./install.sh >> >> This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. >> I'd ask you to answer n or no when the script ask to say if your >> instance is the master. There has to be only one master and is on the >> TI machine where is the VPN server. Then you have to give a name to >> your platform node: please, use "turtlebotET" because we already have >> manually provisioned it. It is provisioned with a custom service logic >> named "fiware_demo2" which starts a service space (with the same name >> of the robot), a firos instance on server side and the turtlebot ros >> driver on the robot side. The firos instance is the old one until we >> can deploy the new one. Your platform node should a robot, so when >> asked answer y yes or press only enter (the installer put the default >> answer between [] so if you push enter that value will be used). The >> default address of the master is calculated using the tun0 interface >> so you have the vpn configuration already done to do this >> installation. The final step of the installation put rcm as daemon in >> your ubuntu machine and start the compilatio n of rcmp workspace. At >> the end you can decide if already run the rcm node or if you want wait >> and start it manually later (sudo service rcmpd start) >> >> I hope this is clear but if I missed something ask me >> >> Last thing: I've redone the zip to add the password "robotics" >> >> Have a nice week end >> >> >> >> 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. >> >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From davide.colombatto at telecomitalia.it Mon Jun 22 17:44:49 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Mon, 22 Jun 2015 15:44:49 +0000 Subject: [Fiware-robotics] R: R: R: rcm_platform v2 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB5BB7F@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F70801@telmbc006ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD35416F73AC0@telmbc006ba020.telecomitalia.local> Hi Pepe, For the "+x persmissions" issues (related to "/usr/local/bin/rcmp_launcher" and "*.sh") maybe are related to the password applied to forward you the zipped-installation package. The service logic related to the "turtlebotET" instance is: - on the Server side (i.e. Master) it is started FIROS (as the version except that the CB IP), so you won't see the FIROS-core.py process on the Robot side - on the Robot side (i.e. your machine) they are started the ROS driver to allow the robot teleoperation through the ROS launcher "turtlebot_bringup minimal.launch". N.B. If RCM doesn't succeed to start (within the created Service Space) even just one of the node/launcher related to the service logic, it stops all of them and also deletes the Service Space. For this reason it is better that your machine is a real turtlebot's PC (better if connected to the Kobuki to have some feedbacks), in order to have already installed the ROS driver started by "turtlebot_bringup minimal.launch" (and obviously the ROS launcher itself). Let we know if with a real turtlebot it works. Thank you, D -----Messaggio originale----- 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: luned? 22 giugno 2015 17:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: rcm_platform v2 Thank you very much Davide. I've found one bug (I believe it is a bug) in the installer: /usr/local/bin/rcmp_launcher hasn't got +x persmissions. I had to add it manually. After starting rcmpd the robot appears as connected and paired but, a minute or two after that, "python /usr/local/bin/rcmp_launcher" starts eating 99.9% of a CPU core. The machine where I'm performing the test doesn't have FIROS or any other ROS node running. I'll try in the real turtlebot and let you know. BR, Pepe On 22/06/15 12:53, Colombatto Davide wrote: > Hi Pepe, > > 130.206.114.100 is the IP of the CB only whereas the RCM_MASTER is a TI-VM. > > You can (and we can also show in the demo) the information retrieved directly by the Robotics Data Mgmt (look at https://forge.fiware.org/plugins/mediawiki/wiki/fiwarei2nd/index.php/FIWARE.ArchitectureDescription.I2ND.Robotics#Architecture). > In particular you can use the RDAPI depicted in OpenSpecDraft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#), changing "MASTER_WAN_public_IP" in "jolcrab-platform.ddns.net", related to: > - Read platform (provisioned Robots) > - Your robot will be shown as "pi_name":"turtlebotET" > - "connected":true: the Robot's PM_AGENT is connected to the PM_MASTER > - "paired":true: the Robot is paired with a Server (i.e. always the > Master for this Major Release) > - Read service space passing as GET parameter ss_name=turtlebotET > - Conventionally the Service Space automatically created for a connected robot has the same name of the robot > - Obviously you can use this API only if the robot is currently > connected (i.e. the Service Space in created) > > After the PM_AGENT is installed on your turtlebot's PC you have only to switch on/off the turtlebot'PC (or just to switch on/off the WiFi connection) and the correct service logic (FIROS on Server side and turtlebot's DRIVER on Robot side) should be started by the PM_MASTER. > Please, also consider that the actual RCM implementation requires about 1 minute to recognize (i.e. to be sure to correctly identify) a Robot connection/disconnection and to do the relative tasks (i.e. creating/deleting the Service Space). > > Let we know, > D > > > -----Messaggio originale----- > 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: luned? 22 giugno 2015 12:34 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: rcm_platform v2 > > Hi, > > I've made some tests with a virtual machine. The installation went smoothly (I'd add "chmod +x *.sh" to the guidelines you sent) and it looks like the rcmpd is working, but I cannot get information from the RCM master (RDAPI). The installation script is tellimng me that the RCM Master is in 10.82.99.1 and I've tried 130.206.114.100 also. > > We had to change the IP of our CB, the new one is 130.206.122.27 but we'd prefer to use yours. > > Thank you very much, > Pepe > > On 19/06/15 18:46, Colombatto Davide wrote: >> Hi, >> >> only a clarification about the sentence "The firos instance is the old one until we can deploy the new one"; as we said in the new demo proposal the old FIROS code is modified as following: >> - the topic is modified from the turtlesim one ("turtle1/cmd_vel") to >> the turtlebot one ("mobile_base/commands/velocity") >> - the current CB instance used is that at 130.206.114.100:1026; we created this our CB instance (on Spain2 node) because your old one didn't work (when it will be up again we can reuse it if you want). >> >> Using this configuration we have done many tests, also using your old web-app of the first demo (i.e. using chrome disabling the security option to avoid cross-domain issues and publishing to the CB instance at 130.206.114.100:1026), and it seems to work good (e.g. no latency btw the web-app's FORWARD command and the turtlebot's movement). >> >> BR, >> Davide >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> fabio.dibenedetto at consoft.it >> Inviato: venerd? 19 giugno 2015 18:21 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] rcm_platform v2 >> >> Hi guys, >> here is the new version of rcm_platform. >> To install it copy the zip on your turtlebot >> - scp rcm_platform.zip turtlebot at ip_address:. >> and unzip it (you can do it where you want because this is the >> installer and it will put all the files where are needed) >> - unzip rcm_platform.zip >> Once extracted the package you will have a folder named >> rcm_platform_pkg; go into it and launch install.sh >> - cd rcm_platform_pkg >> - ./install.sh >> >> This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. >> I'd ask you to answer n or no when the script ask to say if your >> instance is the master. There has to be only one master and is on the >> TI machine where is the VPN server. Then you have to give a name to >> your platform node: please, use "turtlebotET" because we already have >> manually provisioned it. It is provisioned with a custom service >> logic named "fiware_demo2" which starts a service space (with the >> same name of the robot), a firos instance on server side and the >> turtlebot ros driver on the robot side. The firos instance is the old >> one until we can deploy the new one. Your platform node should a >> robot, so when asked answer y yes or press only enter (the installer >> put the default answer between [] so if you push enter that value >> will be used). The default address of the master is calculated using >> the tun0 interface so you have the vpn configuration already done to >> do this installation. The final step of the installation put rcm as >> daemon in your ubuntu machine and start the compilatio n of rcmp >> workspace. At the end you can decide if already run the rcm node or >> if you want wait and start it manually later (sudo service rcmpd >> start) >> >> I hope this is clear but if I missed something ask me >> >> Last thing: I've redone the zip to add the password "robotics" >> >> Have a nice week end >> >> >> >> 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. >> >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From fabio.dibenedetto at consoft.it Mon Jun 22 18:27:53 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Mon, 22 Jun 2015 16:27:53 +0000 Subject: [Fiware-robotics] R: R: R: rcm_platform v2 In-Reply-To: <069906BED271EB4A883BD9578DCDD35416F73AC0@telmbc006ba020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB5BB7F@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F70801@telmbc006ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F73AC0@telmbc006ba020.telecomitalia.local> Message-ID: The permission problem is only because I had to unzip the package on Windows and rezip it on that OS: in this process I lost all the permission I had set (so all the executable files). Sorry about that -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: luned? 22 giugno 2015 17:45 A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: R: rcm_platform v2 Hi Pepe, For the "+x persmissions" issues (related to "/usr/local/bin/rcmp_launcher" and "*.sh") maybe are related to the password applied to forward you the zipped-installation package. The service logic related to the "turtlebotET" instance is: - on the Server side (i.e. Master) it is started FIROS (as the version except that the CB IP), so you won't see the FIROS-core.py process on the Robot side - on the Robot side (i.e. your machine) they are started the ROS driver to allow the robot teleoperation through the ROS launcher "turtlebot_bringup minimal.launch". N.B. If RCM doesn't succeed to start (within the created Service Space) even just one of the node/launcher related to the service logic, it stops all of them and also deletes the Service Space. For this reason it is better that your machine is a real turtlebot's PC (better if connected to the Kobuki to have some feedbacks), in order to have already installed the ROS driver started by "turtlebot_bringup minimal.launch" (and obviously the ROS launcher itself). Let we know if with a real turtlebot it works. Thank you, D -----Messaggio originale----- 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: luned? 22 giugno 2015 17:10 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: rcm_platform v2 Thank you very much Davide. I've found one bug (I believe it is a bug) in the installer: /usr/local/bin/rcmp_launcher hasn't got +x persmissions. I had to add it manually. After starting rcmpd the robot appears as connected and paired but, a minute or two after that, "python /usr/local/bin/rcmp_launcher" starts eating 99.9% of a CPU core. The machine where I'm performing the test doesn't have FIROS or any other ROS node running. I'll try in the real turtlebot and let you know. BR, Pepe On 22/06/15 12:53, Colombatto Davide wrote: > Hi Pepe, > > 130.206.114.100 is the IP of the CB only whereas the RCM_MASTER is a TI-VM. > > You can (and we can also show in the demo) the information retrieved directly by the Robotics Data Mgmt (look at https://forge.fiware.org/plugins/mediawiki/wiki/fiwarei2nd/index.php/FIWARE.ArchitectureDescription.I2ND.Robotics#Architecture). > In particular you can use the RDAPI depicted in OpenSpecDraft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#), changing "MASTER_WAN_public_IP" in "jolcrab-platform.ddns.net", related to: > - Read platform (provisioned Robots) > - Your robot will be shown as "pi_name":"turtlebotET" > - "connected":true: the Robot's PM_AGENT is connected to the PM_MASTER > - "paired":true: the Robot is paired with a Server (i.e. always the > Master for this Major Release) > - Read service space passing as GET parameter ss_name=turtlebotET > - Conventionally the Service Space automatically created for a connected robot has the same name of the robot > - Obviously you can use this API only if the robot is currently > connected (i.e. the Service Space in created) > > After the PM_AGENT is installed on your turtlebot's PC you have only to switch on/off the turtlebot'PC (or just to switch on/off the WiFi connection) and the correct service logic (FIROS on Server side and turtlebot's DRIVER on Robot side) should be started by the PM_MASTER. > Please, also consider that the actual RCM implementation requires about 1 minute to recognize (i.e. to be sure to correctly identify) a Robot connection/disconnection and to do the relative tasks (i.e. creating/deleting the Service Space). > > Let we know, > D > > > -----Messaggio originale----- > 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: luned? 22 giugno 2015 12:34 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: rcm_platform v2 > > Hi, > > I've made some tests with a virtual machine. The installation went smoothly (I'd add "chmod +x *.sh" to the guidelines you sent) and it looks like the rcmpd is working, but I cannot get information from the RCM master (RDAPI). The installation script is tellimng me that the RCM Master is in 10.82.99.1 and I've tried 130.206.114.100 also. > > We had to change the IP of our CB, the new one is 130.206.122.27 but we'd prefer to use yours. > > Thank you very much, > Pepe > > On 19/06/15 18:46, Colombatto Davide wrote: >> Hi, >> >> only a clarification about the sentence "The firos instance is the old one until we can deploy the new one"; as we said in the new demo proposal the old FIROS code is modified as following: >> - the topic is modified from the turtlesim one ("turtle1/cmd_vel") to >> the turtlebot one ("mobile_base/commands/velocity") >> - the current CB instance used is that at 130.206.114.100:1026; we created this our CB instance (on Spain2 node) because your old one didn't work (when it will be up again we can reuse it if you want). >> >> Using this configuration we have done many tests, also using your old web-app of the first demo (i.e. using chrome disabling the security option to avoid cross-domain issues and publishing to the CB instance at 130.206.114.100:1026), and it seems to work good (e.g. no latency btw the web-app's FORWARD command and the turtlebot's movement). >> >> BR, >> Davide >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >> fabio.dibenedetto at consoft.it >> Inviato: venerd? 19 giugno 2015 18:21 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] rcm_platform v2 >> >> Hi guys, >> here is the new version of rcm_platform. >> To install it copy the zip on your turtlebot >> - scp rcm_platform.zip turtlebot at ip_address:. >> and unzip it (you can do it where you want because this is the >> installer and it will put all the files where are needed) >> - unzip rcm_platform.zip >> Once extracted the package you will have a folder named >> rcm_platform_pkg; go into it and launch install.sh >> - cd rcm_platform_pkg >> - ./install.sh >> >> This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. >> I'd ask you to answer n or no when the script ask to say if your >> instance is the master. There has to be only one master and is on the >> TI machine where is the VPN server. Then you have to give a name to >> your platform node: please, use "turtlebotET" because we already have >> manually provisioned it. It is provisioned with a custom service >> logic named "fiware_demo2" which starts a service space (with the >> same name of the robot), a firos instance on server side and the >> turtlebot ros driver on the robot side. The firos instance is the old >> one until we can deploy the new one. Your platform node should a >> robot, so when asked answer y yes or press only enter (the installer >> put the default answer between [] so if you push enter that value >> will be used). The default address of the master is calculated using >> the tun0 interface so you have the vpn configuration already done to >> do this installation. The final step of the installation put rcm as >> daemon in your ubuntu machine and start the compilatio n of rcmp >> workspace. At the end you can decide if already run the rcm node or >> if you want wait and start it manually later (sudo service rcmpd >> start) >> >> I hope this is clear but if I missed something ask me >> >> Last thing: I've redone the zip to add the password "robotics" >> >> Have a nice week end >> >> >> >> 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. >> >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From pierangelo.garino at telecomitalia.it Tue Jun 23 10:09:39 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 23 Jun 2015 08:09:39 +0000 Subject: [Fiware-robotics] Minutes link Message-ID: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo/edit ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Tue Jun 23 12:22:43 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 23 Jun 2015 10:22:43 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> Message-ID: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we'd like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members...) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we'll be able to 'complete the picture' and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ... of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]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 jjaime at ikergune.com Tue Jun 23 13:39:05 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 23 Jun 2015 13:39:05 +0200 Subject: [Fiware-robotics] R: R: R: rcm_platform v2 References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB5BB7F@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F70801@telmbc006ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F73AC0@telmbc006ba020.telecomitalia.local> Message-ID: Hi all, I've made some tests in a real turtlebot and everything looks fine. I've tried to get information from your contextbroker but I've not find anything, I'm searching entities with type ROBOT. BR, Pepe On 22/06/15 18:29, fabio.dibenedetto at consoft.it wrote: > The permission problem is only because I had to unzip the package on Windows and rezip it on that OS: in this process I lost all the permission I had set (so all the executable files). Sorry about that > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide > Inviato: luned? 22 giugno 2015 17:45 > A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: R: R: rcm_platform v2 > > Hi Pepe, > > For the "+x persmissions" issues (related to "/usr/local/bin/rcmp_launcher" and "*.sh") maybe are related to the password applied to forward you the zipped-installation package. > > The service logic related to the "turtlebotET" instance is: > - on the Server side (i.e. Master) it is started FIROS (as the version except that the CB IP), so you won't see the FIROS-core.py process on the Robot side > - on the Robot side (i.e. your machine) they are started the ROS driver to allow the robot teleoperation through the ROS launcher "turtlebot_bringup minimal.launch". > > N.B. If RCM doesn't succeed to start (within the created Service Space) even just one of the node/launcher related to the service logic, it stops all of them and also deletes the Service Space. > For this reason it is better that your machine is a real turtlebot's PC (better if connected to the Kobuki to have some feedbacks), in order to have already installed the ROS driver started by "turtlebot_bringup minimal.launch" (and obviously the ROS launcher itself). > > Let we know if with a real turtlebot it works. > > Thank you, > D > > -----Messaggio originale----- > 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: luned? 22 giugno 2015 17:10 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: R: rcm_platform v2 > > Thank you very much Davide. > > I've found one bug (I believe it is a bug) in the installer: > /usr/local/bin/rcmp_launcher hasn't got +x persmissions. I had to add it manually. > > After starting rcmpd the robot appears as connected and paired but, a minute or two after that, "python /usr/local/bin/rcmp_launcher" starts eating 99.9% of a CPU core. The machine where I'm performing the test doesn't have FIROS or any other ROS node running. I'll try in the real turtlebot and let you know. > > BR, > Pepe > > On 22/06/15 12:53, Colombatto Davide wrote: >> Hi Pepe, >> >> 130.206.114.100 is the IP of the CB only whereas the RCM_MASTER is a TI-VM. >> >> You can (and we can also show in the demo) the information retrieved directly by the Robotics Data Mgmt (look at https://forge.fiware.org/plugins/mediawiki/wiki/fiwarei2nd/index.php/FIWARE.ArchitectureDescription.I2ND.Robotics#Architecture). >> In particular you can use the RDAPI depicted in OpenSpecDraft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#), changing "MASTER_WAN_public_IP" in "jolcrab-platform.ddns.net", related to: >> - Read platform (provisioned Robots) >> - Your robot will be shown as "pi_name":"turtlebotET" >> - "connected":true: the Robot's PM_AGENT is connected to the PM_MASTER >> - "paired":true: the Robot is paired with a Server (i.e. always the >> Master for this Major Release) >> - Read service space passing as GET parameter ss_name=turtlebotET >> - Conventionally the Service Space automatically created for a connected robot has the same name of the robot >> - Obviously you can use this API only if the robot is currently >> connected (i.e. the Service Space in created) >> >> After the PM_AGENT is installed on your turtlebot's PC you have only to switch on/off the turtlebot'PC (or just to switch on/off the WiFi connection) and the correct service logic (FIROS on Server side and turtlebot's DRIVER on Robot side) should be started by the PM_MASTER. >> Please, also consider that the actual RCM implementation requires about 1 minute to recognize (i.e. to be sure to correctly identify) a Robot connection/disconnection and to do the relative tasks (i.e. creating/deleting the Service Space). >> >> Let we know, >> D >> >> >> -----Messaggio originale----- >> 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: luned? 22 giugno 2015 12:34 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: Re: [Fiware-robotics] R: rcm_platform v2 >> >> Hi, >> >> I've made some tests with a virtual machine. The installation went smoothly (I'd add "chmod +x *.sh" to the guidelines you sent) and it looks like the rcmpd is working, but I cannot get information from the RCM master (RDAPI). The installation script is tellimng me that the RCM Master is in 10.82.99.1 and I've tried 130.206.114.100 also. >> >> We had to change the IP of our CB, the new one is 130.206.122.27 but we'd prefer to use yours. >> >> Thank you very much, >> Pepe >> >> On 19/06/15 18:46, Colombatto Davide wrote: >>> Hi, >>> >>> only a clarification about the sentence "The firos instance is the old one until we can deploy the new one"; as we said in the new demo proposal the old FIROS code is modified as following: >>> - the topic is modified from the turtlesim one ("turtle1/cmd_vel") to >>> the turtlebot one ("mobile_base/commands/velocity") >>> - the current CB instance used is that at 130.206.114.100:1026; we created this our CB instance (on Spain2 node) because your old one didn't work (when it will be up again we can reuse it if you want). >>> >>> Using this configuration we have done many tests, also using your old web-app of the first demo (i.e. using chrome disabling the security option to avoid cross-domain issues and publishing to the CB instance at 130.206.114.100:1026), and it seems to work good (e.g. no latency btw the web-app's FORWARD command and the turtlebot's movement). >>> >>> BR, >>> Davide >>> >>> >>> -----Messaggio originale----- >>> Da: fiware-robotics-bounces at lists.fi-ware.org >>> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >>> fabio.dibenedetto at consoft.it >>> Inviato: venerd? 19 giugno 2015 18:21 >>> A: fiware-robotics at lists.fi-ware.org >>> Oggetto: [Fiware-robotics] rcm_platform v2 >>> >>> Hi guys, >>> here is the new version of rcm_platform. >>> To install it copy the zip on your turtlebot >>> - scp rcm_platform.zip turtlebot at ip_address:. >>> and unzip it (you can do it where you want because this is the >>> installer and it will put all the files where are needed) >>> - unzip rcm_platform.zip >>> Once extracted the package you will have a folder named >>> rcm_platform_pkg; go into it and launch install.sh >>> - cd rcm_platform_pkg >>> - ./install.sh >>> >>> This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. >>> I'd ask you to answer n or no when the script ask to say if your >>> instance is the master. There has to be only one master and is on the >>> TI machine where is the VPN server. Then you have to give a name to >>> your platform node: please, use "turtlebotET" because we already have >>> manually provisioned it. It is provisioned with a custom service >>> logic named "fiware_demo2" which starts a service space (with the >>> same name of the robot), a firos instance on server side and the >>> turtlebot ros driver on the robot side. The firos instance is the old >>> one until we can deploy the new one. Your platform node should a >>> robot, so when asked answer y yes or press only enter (the installer >>> put the default answer between [] so if you push enter that value >>> will be used). The default address of the master is calculated using >>> the tun0 interface so you have the vpn configuration already done to >>> do this installation. The final step of the installation put rcm as >>> daemon in your ubuntu machine and start the compilatio n of rcmp >>> workspace. At the end you can decide if already run the rcm node or >>> if you want wait and start it manually later (sudo service rcmpd >>> start) >>> >>> I hope this is clear but if I missed something ask me >>> >>> Last thing: I've redone the zip to add the password "robotics" >>> >>> Have a nice week end >>> >>> >>> >>> 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. >>> >>> >> -- >> Jos? Jaime Ariza >> R&D Engineer >> +34 696604288 >> Ikergune, Etxe-Tar group >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From davide.colombatto at telecomitalia.it Tue Jun 23 14:38:40 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 23 Jun 2015 12:38:40 +0000 Subject: [Fiware-robotics] R: R: R: R: rcm_platform v2 In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB57F71@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5A766@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B510@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B710@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD3540CB5B87B@TELMBB006RM001.telecomitalia.local> <8b0bfaf78c01444f8728cdd4696af466@EXCHMBX2.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB5BB7F@TELMBB006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F70801@telmbc006ba020.telecomitalia.local> <069906BED271EB4A883BD9578DCDD35416F73AC0@telmbc006ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD35416F7628C@telmbc006ba020.telecomitalia.local> Hi Pepe, I don't know about information inside the CB but the FIROS version associated to your service logic is the same of the old version of FIROS except for the CB address (130.206.114.100) and the TOPIC published in ROS ("mobile_base/commands/velocity") in order to command the turtlebot; said that, the FIROS should name the CB entity as "turtle1" with the attribute "cmd_vel" as in the first demo. Have you tried to use the web-app we used in the first demo? (I have tried it and it works, after having changed the var CB_URL in the app.js) N.B. Please, remember the FIROS is running after you see that the RDAPI "Read platform" answers both connected and paired are "true". After the Service Space is created you can also see the information related to the Service Space, using the RDAPI "Read Service Space" (passing the GET-param ss_name=tutlebotET). Since we haven't work with the CB-API, if you prefer we can use a your instance of the CB so you could have more control on it. BR, Davide -----Messaggio originale----- 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: marted? 23 giugno 2015 13:39 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: rcm_platform v2 Hi all, I've made some tests in a real turtlebot and everything looks fine. I've tried to get information from your contextbroker but I've not find anything, I'm searching entities with type ROBOT. BR, Pepe On 22/06/15 18:29, fabio.dibenedetto at consoft.it wrote: > The permission problem is only because I had to unzip the package on > Windows and rezip it on that OS: in this process I lost all the > permission I had set (so all the executable files). Sorry about that > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di > Colombatto Davide > Inviato: luned? 22 giugno 2015 17:45 > A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: R: R: rcm_platform v2 > > Hi Pepe, > > For the "+x persmissions" issues (related to "/usr/local/bin/rcmp_launcher" and "*.sh") maybe are related to the password applied to forward you the zipped-installation package. > > The service logic related to the "turtlebotET" instance is: > - on the Server side (i.e. Master) it is started FIROS (as the version > except that the CB IP), so you won't see the FIROS-core.py process on > the Robot side > - on the Robot side (i.e. your machine) they are started the ROS driver to allow the robot teleoperation through the ROS launcher "turtlebot_bringup minimal.launch". > > N.B. If RCM doesn't succeed to start (within the created Service Space) even just one of the node/launcher related to the service logic, it stops all of them and also deletes the Service Space. > For this reason it is better that your machine is a real turtlebot's PC (better if connected to the Kobuki to have some feedbacks), in order to have already installed the ROS driver started by "turtlebot_bringup minimal.launch" (and obviously the ROS launcher itself). > > Let we know if with a real turtlebot it works. > > Thank you, > D > > -----Messaggio originale----- > 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: luned? 22 giugno 2015 17:10 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: R: rcm_platform v2 > > Thank you very much Davide. > > I've found one bug (I believe it is a bug) in the installer: > /usr/local/bin/rcmp_launcher hasn't got +x persmissions. I had to add it manually. > > After starting rcmpd the robot appears as connected and paired but, a minute or two after that, "python /usr/local/bin/rcmp_launcher" starts eating 99.9% of a CPU core. The machine where I'm performing the test doesn't have FIROS or any other ROS node running. I'll try in the real turtlebot and let you know. > > BR, > Pepe > > On 22/06/15 12:53, Colombatto Davide wrote: >> Hi Pepe, >> >> 130.206.114.100 is the IP of the CB only whereas the RCM_MASTER is a TI-VM. >> >> You can (and we can also show in the demo) the information retrieved directly by the Robotics Data Mgmt (look at https://forge.fiware.org/plugins/mediawiki/wiki/fiwarei2nd/index.php/FIWARE.ArchitectureDescription.I2ND.Robotics#Architecture). >> In particular you can use the RDAPI depicted in OpenSpecDraft (https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit#), changing "MASTER_WAN_public_IP" in "jolcrab-platform.ddns.net", related to: >> - Read platform (provisioned Robots) >> - Your robot will be shown as "pi_name":"turtlebotET" >> - "connected":true: the Robot's PM_AGENT is connected to the PM_MASTER >> - "paired":true: the Robot is paired with a Server (i.e. always the >> Master for this Major Release) >> - Read service space passing as GET parameter ss_name=turtlebotET >> - Conventionally the Service Space automatically created for a connected robot has the same name of the robot >> - Obviously you can use this API only if the robot is currently >> connected (i.e. the Service Space in created) >> >> After the PM_AGENT is installed on your turtlebot's PC you have only to switch on/off the turtlebot'PC (or just to switch on/off the WiFi connection) and the correct service logic (FIROS on Server side and turtlebot's DRIVER on Robot side) should be started by the PM_MASTER. >> Please, also consider that the actual RCM implementation requires about 1 minute to recognize (i.e. to be sure to correctly identify) a Robot connection/disconnection and to do the relative tasks (i.e. creating/deleting the Service Space). >> >> Let we know, >> D >> >> >> -----Messaggio originale----- >> 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: luned? 22 giugno 2015 12:34 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: Re: [Fiware-robotics] R: rcm_platform v2 >> >> Hi, >> >> I've made some tests with a virtual machine. The installation went smoothly (I'd add "chmod +x *.sh" to the guidelines you sent) and it looks like the rcmpd is working, but I cannot get information from the RCM master (RDAPI). The installation script is tellimng me that the RCM Master is in 10.82.99.1 and I've tried 130.206.114.100 also. >> >> We had to change the IP of our CB, the new one is 130.206.122.27 but we'd prefer to use yours. >> >> Thank you very much, >> Pepe >> >> On 19/06/15 18:46, Colombatto Davide wrote: >>> Hi, >>> >>> only a clarification about the sentence "The firos instance is the old one until we can deploy the new one"; as we said in the new demo proposal the old FIROS code is modified as following: >>> - the topic is modified from the turtlesim one ("turtle1/cmd_vel") >>> to the turtlebot one ("mobile_base/commands/velocity") >>> - the current CB instance used is that at 130.206.114.100:1026; we created this our CB instance (on Spain2 node) because your old one didn't work (when it will be up again we can reuse it if you want). >>> >>> Using this configuration we have done many tests, also using your old web-app of the first demo (i.e. using chrome disabling the security option to avoid cross-domain issues and publishing to the CB instance at 130.206.114.100:1026), and it seems to work good (e.g. no latency btw the web-app's FORWARD command and the turtlebot's movement). >>> >>> BR, >>> Davide >>> >>> >>> -----Messaggio originale----- >>> Da: fiware-robotics-bounces at lists.fi-ware.org >>> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di >>> fabio.dibenedetto at consoft.it >>> Inviato: venerd? 19 giugno 2015 18:21 >>> A: fiware-robotics at lists.fi-ware.org >>> Oggetto: [Fiware-robotics] rcm_platform v2 >>> >>> Hi guys, >>> here is the new version of rcm_platform. >>> To install it copy the zip on your turtlebot >>> - scp rcm_platform.zip turtlebot at ip_address:. >>> and unzip it (you can do it where you want because this is the >>> installer and it will put all the files where are needed) >>> - unzip rcm_platform.zip >>> Once extracted the package you will have a folder named >>> rcm_platform_pkg; go into it and launch install.sh >>> - cd rcm_platform_pkg >>> - ./install.sh >>> >>> This command starts the installation and configuration of your rcm platform node: it starts creating a ros workspace used by rcm and then installs 2 python packages in your ubuntu distribution. Then starts installing rcmplatform: many of these operations need root permission so during the installation will be asked the credentials. At the end of the installation the configuration step starts: follow the instruction on your shell. >>> I'd ask you to answer n or no when the script ask to say if your >>> instance is the master. There has to be only one master and is on >>> the TI machine where is the VPN server. Then you have to give a name >>> to your platform node: please, use "turtlebotET" because we already >>> have manually provisioned it. It is provisioned with a custom >>> service logic named "fiware_demo2" which starts a service space >>> (with the same name of the robot), a firos instance on server side >>> and the turtlebot ros driver on the robot side. The firos instance >>> is the old one until we can deploy the new one. Your platform node >>> should a robot, so when asked answer y yes or press only enter (the >>> installer put the default answer between [] so if you push enter >>> that value will be used). The default address of the master is >>> calculated using the tun0 interface so you have the vpn >>> configuration already done to do this installation. The final step >>> of the installation put rcm as daemon in your ubuntu machine and >>> start the compilatio n of rcmp workspace. At the end you can decide >>> if already run the rcm node or if you want wait and start it >>> manually later (sudo service rcmpd >>> start) >>> >>> I hope this is clear but if I missed something ask me >>> >>> Last thing: I've redone the zip to add the password "robotics" >>> >>> Have a nice week end >>> >>> >>> >>> 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. >>> >>> >> -- >> Jos? Jaime Ariza >> R&D Engineer >> +34 696604288 >> Ikergune, Etxe-Tar group >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> > > -- > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From roberto1.antonini at telecomitalia.it Thu Jun 25 12:12:27 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 25 Jun 2015 10:12:27 +0000 Subject: [Fiware-robotics] Sprint 4.3.3 Retrospective Message-ID: <246C286B275B1B46A255552CD236DA8643D77264@TELMBB001BA020.telecomitalia.local> Hi all, as emerged in the last call, I would kindly ask Pepe (ET) and Fabio (CONSOFT) to provide your retrospective by tomorrow (26th Friday) in the following JIRA issues: * MIND-358 ET * MIND-359 CONSOFT There you can find the usual template to ease retrospective insertion. Let me please know, as soon as you insert it. Thanks, 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 jjaime at ikergune.com Fri Jun 26 10:46:55 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 26 Jun 2015 10:46:55 +0200 Subject: [Fiware-robotics] Sprint 4.3.3 Retrospective References: <246C286B275B1B46A255552CD236DA8643D77264@TELMBB001BA020.telecomitalia.local> Message-ID: Hi, We've just added our retrospective. BR On 25/06/15 12:12, Antonini Roberto wrote: Hi all, as emerged in the last call, I would kindly ask Pepe (ET) and Fabio (CONSOFT) to provide your retrospective by tomorrow (26th Friday) in the following JIRA issues: ? MIND-358 ET ? MIND-359 CONSOFT There you can find the usual template to ease retrospective insertion. Let me please know, as soon as you insert it. Thanks, 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. [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 jjaime at ikergune.com Fri Jun 26 11:57:50 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 26 Jun 2015 11:57:50 +0200 Subject: [Fiware-robotics] Firos GIT Message-ID: Hi, You can find FIROS in https://github.com/Ikergune/firos/ BR, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From fabio.dibenedetto at consoft.it Fri Jun 26 14:09:58 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Fri, 26 Jun 2015 12:09:58 +0000 Subject: [Fiware-robotics] R: Sprint 4.3.3 Retrospective In-Reply-To: <246C286B275B1B46A255552CD236DA8643D77264@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA8643D77264@TELMBB001BA020.telecomitalia.local> Message-ID: Hi, I've just added my retrospective and closed the workitem Fabio Da: Antonini Roberto [mailto:roberto1.antonini at telecomitalia.it] Inviato: gioved? 25 giugno 2015 12:12 A: fiware-robotics at lists.fi-ware.org; fabio.dibenedetto at consoft.it; Jose Jaime Ariza Cc: Garino Pierangelo Oggetto: Sprint 4.3.3 Retrospective Priorit?: Alta Hi all, as emerged in the last call, I would kindly ask Pepe (ET) and Fabio (CONSOFT) to provide your retrospective by tomorrow (26th Friday) in the following JIRA issues: ? MIND-358 ET ? MIND-359 CONSOFT There you can find the usual template to ease retrospective insertion. Let me please know, as soon as you insert it. Thanks, 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: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From fabio.dibenedetto at consoft.it Mon Jun 29 15:14:56 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Mon, 29 Jun 2015 13:14:56 +0000 Subject: [Fiware-robotics] R: Firos GIT In-Reply-To: References: Message-ID: Hi guys, can I have a little help? I downloaded the new firos last week but I'm trying only today to launch it for the first time. I'm having some trouble (at the end of the mail what I received using rosrun firos core.py). Have I missed anything? Looking quickly in the code I've seen that I have to use -Pport to pass the port parameter: is that right? But for now I haven't tried that way for now shell output: Initializing ROS node: firos Initialized Starting Firos setup... --------------------------------- Generating Message Description Files Generating message definition for robot2/cmd_height Succesfully generated Starting Firos... --------------------------------- Getting configuration data Generating topic handlers: -robot2 -cmd_vel_mux/input/teleop -cmd_serial -move_base/goal Traceback (most recent call last): File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in loadMsgHandlers(confManager.getRobots(True, True)) File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers theclass = LibLoader.loadFromSystem(topic['msg']) File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem module = __import__(module_name, globals(), locals(), [module_name.split('.')[-1]]) ImportError: No module named move_base_msgs.msg -----Messaggio originale----- 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: venerd? 26 giugno 2015 11:58 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Firos GIT Hi, You can find FIROS in https://github.com/Ikergune/firos/ BR, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics From igonzalez at ikergune.com Mon Jun 29 15:29:06 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Mon, 29 Jun 2015 15:29:06 +0200 Subject: [Fiware-robotics] R: Firos GIT References: Message-ID: Hi Fabio, the firos you have donwloaded is configured to work with the turtlebot, so what it does on startup is to read on the config.json the robot list and configure ros listeners and publishers. The problem seems to be that the machine where you are launching the firos instance hasn't the move_base handlers installed, maybe try to install the turtlebot?s software and running it again. Regards, I?igo On 29/06/15 15:16, fabio.dibenedetto at consoft.it wrote: > Hi guys, > can I have a little help? I downloaded the new firos last week but I'm trying only today to launch it for the first time. I'm having some trouble (at the end of the mail what I received using rosrun firos core.py). Have I missed anything? Looking quickly in the code I've seen that I have to use -Pport to pass the port parameter: is that right? But for now I haven't tried that way for now > > shell output: > > Initializing ROS node: firos > Initialized > > Starting Firos setup... > --------------------------------- > > > Generating Message Description Files > > Generating message definition for robot2/cmd_height > > Succesfully generated > > > Starting Firos... > --------------------------------- > > Getting configuration data > Generating topic handlers: > -robot2 > -cmd_vel_mux/input/teleop > -cmd_serial > -move_base/goal > Traceback (most recent call last): > File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in > loadMsgHandlers(confManager.getRobots(True, True)) > File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers > theclass = LibLoader.loadFromSystem(topic['msg']) > File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem > module = __import__(module_name, globals(), locals(), [module_name.split('.')[-1]]) > ImportError: No module named move_base_msgs.msg > > > > > > > > -----Messaggio originale----- > 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: venerd? 26 giugno 2015 11:58 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Firos GIT > > Hi, > > You can find FIROS in https://github.com/Ikergune/firos/ > > BR, > Pepe > From roberto1.antonini at telecomitalia.it Mon Jun 29 16:11:27 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Mon, 29 Jun 2015 14:11:27 +0000 Subject: [Fiware-robotics] R: R: Firos GIT In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA8643D79562@TELMBB001BA020.telecomitalia.local> Hi Inigo, As far as I understood your FIROS depends on move_base_msgs package in a dynamic way, isn't it? So if I remove move_base entries in config/robot.json, everything will work correctly, right? Thk R&FG -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: luned? 29 giugno 2015 15:29 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Firos GIT Hi Fabio, the firos you have donwloaded is configured to work with the turtlebot, so what it does on startup is to read on the config.json the robot list and configure ros listeners and publishers. The problem seems to be that the machine where you are launching the firos instance hasn't the move_base handlers installed, maybe try to install the turtlebot?s software and running it again. Regards, I?igo On 29/06/15 15:16, fabio.dibenedetto at consoft.it wrote: > Hi guys, > can I have a little help? I downloaded the new firos last week but I'm > trying only today to launch it for the first time. I'm having some > trouble (at the end of the mail what I received using rosrun firos > core.py). Have I missed anything? Looking quickly in the code I've > seen that I have to use -Pport to pass the port parameter: is that > right? But for now I haven't tried that way for now > > shell output: > > Initializing ROS node: firos > Initialized > > Starting Firos setup... > --------------------------------- > > > Generating Message Description Files > > Generating message definition for robot2/cmd_height > > Succesfully generated > > > Starting Firos... > --------------------------------- > > Getting configuration data > Generating topic handlers: > -robot2 > -cmd_vel_mux/input/teleop > -cmd_serial > -move_base/goal > Traceback (most recent call last): > File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in > loadMsgHandlers(confManager.getRobots(True, True)) > File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers > theclass = LibLoader.loadFromSystem(topic['msg']) > File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem > module = __import__(module_name, globals(), locals(), > [module_name.split('.')[-1]]) > ImportError: No module named move_base_msgs.msg > > > > > > > > -----Messaggio originale----- > 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: venerd? 26 giugno 2015 11:58 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Firos GIT > > Hi, > > You can find FIROS in https://github.com/Ikergune/firos/ > > BR, > Pepe > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. From igonzalez at ikergune.com Mon Jun 29 16:11:42 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Mon, 29 Jun 2015 16:11:42 +0200 Subject: [Fiware-robotics] R: R: Firos GIT References: <246C286B275B1B46A255552CD236DA8643D79562@TELMBB001BA020.telecomitalia.local> Message-ID: That's it On 29/06/15 16:11, Antonini Roberto wrote: > Hi Inigo, > As far as I understood your FIROS depends on move_base_msgs package in a dynamic way, isn't it? > So if I remove move_base entries in config/robot.json, everything will work correctly, right? > > Thk > R&FG > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez > Inviato: luned? 29 giugno 2015 15:29 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: Firos GIT > > Hi Fabio, > > the firos you have donwloaded is configured to work with the turtlebot, so what it does on startup is to read on the config.json the robot list and configure ros listeners and publishers. > > The problem seems to be that the machine where you are launching the firos instance hasn't the move_base handlers installed, maybe try to install the turtlebot?s software and running it again. > > Regards, > I?igo > > On 29/06/15 15:16, fabio.dibenedetto at consoft.it wrote: >> Hi guys, >> can I have a little help? I downloaded the new firos last week but I'm >> trying only today to launch it for the first time. I'm having some >> trouble (at the end of the mail what I received using rosrun firos >> core.py). Have I missed anything? Looking quickly in the code I've >> seen that I have to use -Pport to pass the port parameter: is that >> right? But for now I haven't tried that way for now >> >> shell output: >> >> Initializing ROS node: firos >> Initialized >> >> Starting Firos setup... >> --------------------------------- >> >> >> Generating Message Description Files >> >> Generating message definition for robot2/cmd_height >> >> Succesfully generated >> >> >> Starting Firos... >> --------------------------------- >> >> Getting configuration data >> Generating topic handlers: >> -robot2 >> -cmd_vel_mux/input/teleop >> -cmd_serial >> -move_base/goal >> Traceback (most recent call last): >> File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in >> loadMsgHandlers(confManager.getRobots(True, True)) >> File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers >> theclass = LibLoader.loadFromSystem(topic['msg']) >> File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem >> module = __import__(module_name, globals(), locals(), >> [module_name.split('.')[-1]]) >> ImportError: No module named move_base_msgs.msg >> >> >> >> >> >> >> >> -----Messaggio originale----- >> 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: venerd? 26 giugno 2015 11:58 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] Firos GIT >> >> Hi, >> >> You can find FIROS in https://github.com/Ikergune/firos/ >> >> BR, >> Pepe >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > > 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. > > From fabio.dibenedetto at consoft.it Mon Jun 29 17:53:23 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Mon, 29 Jun 2015 15:53:23 +0000 Subject: [Fiware-robotics] R: R: R: Firos GIT In-Reply-To: References: <246C286B275B1B46A255552CD236DA8643D79562@TELMBB001BA020.telecomitalia.local> Message-ID: <6fb08ab493da4b2aa7039a0202a82594@EXCHMBX2.consoft.it> Sorry to disturb again but I commented the part relative to move_base_msgs because I only need to launch firos for now to see if the port exchange works on rcm side, but I have another issue sudo: npm: command not found Exception in thread Thread-4: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/home/fabiog/catkin_ws/src/firos/scripts/include/mapServer.py", line 48, in _launchMapServer subprocess.Popen(["node", mapserver_path + "mapserver.js", str(MAP_SERVER_PORT), str(ROSBRIDGE_PORT)]) File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory Installing node.js is really mandatory? What is the mapserver for? Can I avoid to use this component or is required for firos? -----Messaggio originale----- Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: luned? 29 giugno 2015 16:12 A: Antonini Roberto; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: R: [Fiware-robotics] R: Firos GIT That's it On 29/06/15 16:11, Antonini Roberto wrote: > Hi Inigo, > As far as I understood your FIROS depends on move_base_msgs package in a dynamic way, isn't it? > So if I remove move_base entries in config/robot.json, everything will work correctly, right? > > Thk > R&FG > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo > Gonzalez > Inviato: luned? 29 giugno 2015 15:29 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: Firos GIT > > Hi Fabio, > > the firos you have donwloaded is configured to work with the turtlebot, so what it does on startup is to read on the config.json the robot list and configure ros listeners and publishers. > > The problem seems to be that the machine where you are launching the firos instance hasn't the move_base handlers installed, maybe try to install the turtlebot?s software and running it again. > > Regards, > I?igo > > On 29/06/15 15:16, fabio.dibenedetto at consoft.it wrote: >> Hi guys, >> can I have a little help? I downloaded the new firos last week but >> I'm trying only today to launch it for the first time. I'm having >> some trouble (at the end of the mail what I received using rosrun >> firos core.py). Have I missed anything? Looking quickly in the code >> I've seen that I have to use -Pport to pass the port parameter: is >> that right? But for now I haven't tried that way for now >> >> shell output: >> >> Initializing ROS node: firos >> Initialized >> >> Starting Firos setup... >> --------------------------------- >> >> >> Generating Message Description Files >> >> Generating message definition for robot2/cmd_height >> >> Succesfully generated >> >> >> Starting Firos... >> --------------------------------- >> >> Getting configuration data >> Generating topic handlers: >> -robot2 >> -cmd_vel_mux/input/teleop >> -cmd_serial >> -move_base/goal >> Traceback (most recent call last): >> File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in >> loadMsgHandlers(confManager.getRobots(True, True)) >> File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers >> theclass = LibLoader.loadFromSystem(topic['msg']) >> File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem >> module = __import__(module_name, globals(), locals(), >> [module_name.split('.')[-1]]) >> ImportError: No module named move_base_msgs.msg >> >> >> >> >> >> >> >> -----Messaggio originale----- >> 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: venerd? 26 giugno 2015 11:58 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] Firos GIT >> >> Hi, >> >> You can find FIROS in https://github.com/Ikergune/firos/ >> >> BR, >> Pepe >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > > 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. > > From igonzalez at ikergune.com Tue Jun 30 08:55:09 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Tue, 30 Jun 2015 08:55:09 +0200 Subject: [Fiware-robotics] R: R: R: Firos GIT References: <246C286B275B1B46A255552CD236DA8643D79562@TELMBB001BA020.telecomitalia.local> <6fb08ab493da4b2aa7039a0202a82594@EXCHMBX2.consoft.it> Message-ID: Hi, inside firos a nodejs server is also brought up to allow users to access some ROS capabilities that are not accessible via context broker and this tool is also compatible with more browsers than rosbridge. Anyway you can disable it by deleting the entry "map_server_port" in your firos/config/config.json file. Regards, I?igo On 29/06/15 17:54, fabio.dibenedetto at consoft.it wrote: > Sorry to disturb again but I commented the part relative to move_base_msgs because I only need to launch firos for now to see if the port exchange works on rcm side, but I have another issue > > sudo: npm: command not found > Exception in thread Thread-4: > Traceback (most recent call last): > File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner > self.run() > File "/usr/lib/python2.7/threading.py", line 763, in run > self.__target(*self.__args, **self.__kwargs) > File "/home/fabiog/catkin_ws/src/firos/scripts/include/mapServer.py", line 48, in _launchMapServer > subprocess.Popen(["node", mapserver_path + "mapserver.js", str(MAP_SERVER_PORT), str(ROSBRIDGE_PORT)]) > File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ > errread, errwrite) > File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child > raise child_exception > OSError: [Errno 2] No such file or directory > > Installing node.js is really mandatory? What is the mapserver for? Can I avoid to use this component or is required for firos? > > > > -----Messaggio originale----- > Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] > Inviato: luned? 29 giugno 2015 16:12 > A: Antonini Roberto; fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: Re: R: [Fiware-robotics] R: Firos GIT > > That's it > > On 29/06/15 16:11, Antonini Roberto wrote: >> Hi Inigo, >> As far as I understood your FIROS depends on move_base_msgs package in a dynamic way, isn't it? >> So if I remove move_base entries in config/robot.json, everything will work correctly, right? >> >> Thk >> R&FG >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo >> Gonzalez >> Inviato: luned? 29 giugno 2015 15:29 >> A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org >> Oggetto: Re: [Fiware-robotics] R: Firos GIT >> >> Hi Fabio, >> >> the firos you have donwloaded is configured to work with the turtlebot, so what it does on startup is to read on the config.json the robot list and configure ros listeners and publishers. >> >> The problem seems to be that the machine where you are launching the firos instance hasn't the move_base handlers installed, maybe try to install the turtlebot?s software and running it again. >> >> Regards, >> I?igo >> >> On 29/06/15 15:16, fabio.dibenedetto at consoft.it wrote: >>> Hi guys, >>> can I have a little help? I downloaded the new firos last week but >>> I'm trying only today to launch it for the first time. I'm having >>> some trouble (at the end of the mail what I received using rosrun >>> firos core.py). Have I missed anything? Looking quickly in the code >>> I've seen that I have to use -Pport to pass the port parameter: is >>> that right? But for now I haven't tried that way for now >>> >>> shell output: >>> >>> Initializing ROS node: firos >>> Initialized >>> >>> Starting Firos setup... >>> --------------------------------- >>> >>> >>> Generating Message Description Files >>> >>> Generating message definition for robot2/cmd_height >>> >>> Succesfully generated >>> >>> >>> Starting Firos... >>> --------------------------------- >>> >>> Getting configuration data >>> Generating topic handlers: >>> -robot2 >>> -cmd_vel_mux/input/teleop >>> -cmd_serial >>> -move_base/goal >>> Traceback (most recent call last): >>> File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in >>> loadMsgHandlers(confManager.getRobots(True, True)) >>> File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers >>> theclass = LibLoader.loadFromSystem(topic['msg']) >>> File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem >>> module = __import__(module_name, globals(), locals(), >>> [module_name.split('.')[-1]]) >>> ImportError: No module named move_base_msgs.msg >>> >>> >>> >>> >>> >>> >>> >>> -----Messaggio originale----- >>> 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: venerd? 26 giugno 2015 11:58 >>> A: fiware-robotics at lists.fi-ware.org >>> Oggetto: [Fiware-robotics] Firos GIT >>> >>> Hi, >>> >>> You can find FIROS in https://github.com/Ikergune/firos/ >>> >>> BR, >>> Pepe >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> 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. >> >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > From fabio.dibenedetto at consoft.it Tue Jun 30 09:25:09 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 30 Jun 2015 07:25:09 +0000 Subject: [Fiware-robotics] R: R: R: R: Firos GIT In-Reply-To: References: <246C286B275B1B46A255552CD236DA8643D79562@TELMBB001BA020.telecomitalia.local> <6fb08ab493da4b2aa7039a0202a82594@EXCHMBX2.consoft.it> Message-ID: <3b689ef55a3e433ab93b16ca8781d1f0@EXCHMBX2.consoft.it> No problem about that but it's only because I haven't follow much about what you were doing and I didn't know there was another web/application server in firos other than the one used for expose the API. Is it on another port than the one used for exposing your API, right? Is it an outbound port too? Don't know if it will be available for the demo so for now I will use without that Thanks -----Messaggio originale----- Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: marted? 30 giugno 2015 08:55 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: R: Firos GIT Hi, inside firos a nodejs server is also brought up to allow users to access some ROS capabilities that are not accessible via context broker and this tool is also compatible with more browsers than rosbridge. Anyway you can disable it by deleting the entry "map_server_port" in your firos/config/config.json file. Regards, I?igo On 29/06/15 17:54, fabio.dibenedetto at consoft.it wrote: > Sorry to disturb again but I commented the part relative to > move_base_msgs because I only need to launch firos for now to see if > the port exchange works on rcm side, but I have another issue > > sudo: npm: command not found > Exception in thread Thread-4: > Traceback (most recent call last): > File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner > self.run() > File "/usr/lib/python2.7/threading.py", line 763, in run > self.__target(*self.__args, **self.__kwargs) > File "/home/fabiog/catkin_ws/src/firos/scripts/include/mapServer.py", line 48, in _launchMapServer > subprocess.Popen(["node", mapserver_path + "mapserver.js", str(MAP_SERVER_PORT), str(ROSBRIDGE_PORT)]) > File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ > errread, errwrite) > File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child > raise child_exception > OSError: [Errno 2] No such file or directory > > Installing node.js is really mandatory? What is the mapserver for? Can I avoid to use this component or is required for firos? > > > > -----Messaggio originale----- > Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] > Inviato: luned? 29 giugno 2015 16:12 > A: Antonini Roberto; fabio.dibenedetto at consoft.it; > fiware-robotics at lists.fi-ware.org > Oggetto: Re: R: [Fiware-robotics] R: Firos GIT > > That's it > > On 29/06/15 16:11, Antonini Roberto wrote: >> Hi Inigo, >> As far as I understood your FIROS depends on move_base_msgs package in a dynamic way, isn't it? >> So if I remove move_base entries in config/robot.json, everything will work correctly, right? >> >> Thk >> R&FG >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo >> Gonzalez >> Inviato: luned? 29 giugno 2015 15:29 >> A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org >> Oggetto: Re: [Fiware-robotics] R: Firos GIT >> >> Hi Fabio, >> >> the firos you have donwloaded is configured to work with the turtlebot, so what it does on startup is to read on the config.json the robot list and configure ros listeners and publishers. >> >> The problem seems to be that the machine where you are launching the firos instance hasn't the move_base handlers installed, maybe try to install the turtlebot?s software and running it again. >> >> Regards, >> I?igo >> >> On 29/06/15 15:16, fabio.dibenedetto at consoft.it wrote: >>> Hi guys, >>> can I have a little help? I downloaded the new firos last week but >>> I'm trying only today to launch it for the first time. I'm having >>> some trouble (at the end of the mail what I received using rosrun >>> firos core.py). Have I missed anything? Looking quickly in the code >>> I've seen that I have to use -Pport to pass the port parameter: is >>> that right? But for now I haven't tried that way for now >>> >>> shell output: >>> >>> Initializing ROS node: firos >>> Initialized >>> >>> Starting Firos setup... >>> --------------------------------- >>> >>> >>> Generating Message Description Files >>> >>> Generating message definition for robot2/cmd_height >>> >>> Succesfully generated >>> >>> >>> Starting Firos... >>> --------------------------------- >>> >>> Getting configuration data >>> Generating topic handlers: >>> -robot2 >>> -cmd_vel_mux/input/teleop >>> -cmd_serial >>> -move_base/goal >>> Traceback (most recent call last): >>> File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in >>> loadMsgHandlers(confManager.getRobots(True, True)) >>> File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers >>> theclass = LibLoader.loadFromSystem(topic['msg']) >>> File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem >>> module = __import__(module_name, globals(), locals(), >>> [module_name.split('.')[-1]]) >>> ImportError: No module named move_base_msgs.msg >>> >>> >>> >>> >>> >>> >>> >>> -----Messaggio originale----- >>> 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: venerd? 26 giugno 2015 11:58 >>> A: fiware-robotics at lists.fi-ware.org >>> Oggetto: [Fiware-robotics] Firos GIT >>> >>> Hi, >>> >>> You can find FIROS in https://github.com/Ikergune/firos/ >>> >>> BR, >>> Pepe >>> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-robotics >> >> 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. >> >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-robotics > From gianmario.bollano at telecomitalia.it Tue Jun 30 09:45:55 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 30 Jun 2015 07:45:55 +0000 Subject: [Fiware-robotics] Weekly Robotics call Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE242AC@telmbb003ba020.telecomitalia.local> You are invited at the Weekly Robotics call with hangout. We will discuss important issue for the Sprint Demo and to take decision quickly. Robotics call minutes: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo Best, Gianmario Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2616 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Tue Jun 30 09:49:38 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 30 Jun 2015 07:49:38 +0000 Subject: [Fiware-robotics] Shortening Robotics Call - Proposal Message-ID: Dear All, In a few minutes we'll have the periodic robotics call, and by taking into account the retrospective received from the Robotics team (about too long PhCs) I propose that we focus on a pre-defined number of items on which an agreement is to be found in the call, while the details can be managed via mail and/or shared documents. Moreover, I propose we define the hard deadline for the call, i.e. one hour time, after which the call is closed. My proposal of items is the following: - Where is the sprint demo showed (ET side, TI side, mixed one?) - As a consequence of previous item, status of implementation of demo setup - How to progress in contacts with Wirecloud and Kurento people (currently lack of contacts...) - Pre-demo show (on Friday?) - Setting of demo facilities (hangout? Webex?) Do you have further items to put under discussion today? BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From luis.lopez at urjc.es Tue Jun 30 13:04:49 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Tue, 30 Jun 2015 13:04:49 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> Message-ID: Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo escribi?: > Dear All, > > This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we?d like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). > > We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). > > The document is composed of three parts: > - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 > - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 > - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. > > We kindly ask Luis, Javier, Alvaro (well all team members?) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we?ll be able to ?complete the picture? and proceed straight to the assembly of all demo parts. > > Many thanks and BR > > Pier > > > > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide > Inviato: marted? 16 giugno 2015 12:34 > A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > Hi Luis and Wirecloud guys, > > We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. > > 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). > Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. > Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? > > 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? > If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? > > Thank you, > Davide > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. > This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. > > Rispetta l'ambiente. Non stampare questa mail se non ? necessario. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Tue Jun 30 16:21:32 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 30 Jun 2015 14:21:32 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> Hi Luis, thank you for your support and your clarification. As a short summary, we also have tested a WebRTC client based on Webkit but haven't yet found the optimal solution, then it would be useful to discuss further this issue. The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. Thank you, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez Inviato: marted? 30 giugno 2015 13:05 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo > escribi?: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we'd like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members...) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we'll be able to 'complete the picture' and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ... of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From luis.lopez at urjc.es Tue Jun 30 16:27:01 2015 From: luis.lopez at urjc.es (=?iso-8859-1?Q?Luis_L=F3pez_Fern=E1ndez?=) Date: Tue, 30 Jun 2015 16:27:01 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> Message-ID: Hi Gianmario, Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. Thanks. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 30/06/2015, a las 16:21, Bollano Gianmario escribi?: > Hi Luis, > thank you for your support and your clarification. > As a short summary, we also have tested a WebRTC client based on Webkit but haven?t yet found the optimal solution, then it would be useful to discuss further this issue. > The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). > We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). > We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. > > The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. > > Thank you, > Gianmario > > > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez > Inviato: marted? 30 giugno 2015 13:05 > A: Garino Pierangelo > Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es > Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > Hi Pier, > > I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. > > Best regards. > > ----------------------------------------------------------- > Luis L?pez Fern?ndez > Subdirector de Investigaci?n y Relaciones con la Empresa > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > Universidad Rey Juan Carlos > http://www.etsit.urjc.es > e-mail: luis.lopez at urjc.es > Tf1: +34 914 888 747 > Tf2: + 34 914 888 713 > > > > > > > El 23/06/2015, a las 12:22, Garino Pierangelo escribi?: > > > Dear All, > > This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we?d like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). > > We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). > > The document is composed of three parts: > - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 > - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 > - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. > > We kindly ask Luis, Javier, Alvaro (well all team members?) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we?ll be able to ?complete the picture? and proceed straight to the assembly of all demo parts. > > Many thanks and BR > > Pier > > > > Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide > Inviato: marted? 16 giugno 2015 12:34 > A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es > Cc: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > Hi Luis and Wirecloud guys, > > We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. > > 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). > Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. > Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? > > 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? > If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? > > Thank you, > Davide > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. > This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. > > Rispetta l'ambiente. Non stampare questa mail se non ? necessario. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Tue Jun 30 16:48:10 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 30 Jun 2015 14:48:10 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE2556A@telmbb003ba020.telecomitalia.local> Thank you Luis, we will check your notes and propose you as soon as possible a date to arrange a call. Gianmario Da: Luis L?pez Fern?ndez [mailto:luis.lopez at urjc.es] Inviato: marted? 30 giugno 2015 16:27 A: Bollano Gianmario Cc: Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Gianmario, Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. Thanks. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 30/06/2015, a las 16:21, Bollano Gianmario > escribi?: Hi Luis, thank you for your support and your clarification. As a short summary, we also have tested a WebRTC client based on Webkit but haven't yet found the optimal solution, then it would be useful to discuss further this issue. The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. Thank you, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez Inviato: marted? 30 giugno 2015 13:05 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo > escribi?: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we'd like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members...) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we'll be able to 'complete the picture' and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ... of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aarranz at fi.upm.es Tue Jun 30 16:54:32 2015 From: aarranz at fi.upm.es (=?UTF-8?Q?=C3=81lvaro_Arranz?=) Date: Tue, 30 Jun 2015 16:54:32 +0200 Subject: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> Message-ID: Hi, sorry for the delay in the response, we are busy with the closing and planning phases of the sprint. Also I'm organising my travel to the Campus party event at Mexico. I'll work on providing a better feedback asap (I'll try to provide it today). Anyway, updating our widgets for accessing this one-to-many service will be easy, we can synchronise with the Kurento team for making the needed changes for selecting the master video stream, etc... This is only a thing of managing some new commands through the WebSocket connection and recreating the WebRTC connections. I don't forecast, as Luis, any problem on this side. We are also interested in join the call :). Best regards, ?lvaro On 30 June 2015 at 16:27, Luis L?pez Fern?ndez wrote: > Hi Gianmario, > > Modifying the Kurento demo for one-to-many to support several robots it's > quite trivial. We can do it for you if necessary. This is not an issue. > > The main problem I detect is at the WebRTC client embedded in the robot. > If this client is Chrome, then you may need human intervention for webcam > capture. There are hacks for this, but we need to analyze carefully your > requirements. Otherwise, the option is to compile the WebRTC Chrome stack > separately and write a C++ application at the robot controlling it. This > may require some more relevant efforts and this is the issue we need to > discuss. > > I'm available during most of this week for discussing. Just propose a slot > and we can try to arrange for a call. > > Thanks. > > ----------------------------------------------------------- > Luis L?pez Fern?ndez > Subdirector de Investigaci?n y Relaciones con la Empresa > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > Universidad Rey Juan Carlos > http://www.etsit.urjc.es > e-mail: luis.lopez at urjc.es > Tf1: +34 914 888 747 > Tf2: + 34 914 888 713 > > > > > > > El 30/06/2015, a las 16:21, Bollano Gianmario < > gianmario.bollano at telecomitalia.it> escribi?: > > Hi Luis, > thank you for your support and your clarification. > As a short summary, we also have tested a WebRTC client based on Webkit > but haven?t yet found the optimal solution, then it would be useful to > discuss further this issue. > The team has done tests with the JS version for the Kurento Client with > NodeJS; our idea is to use a single App Server for the master Client and > all Viewer clients as in the One-To-Many Kurento tutorial ( > http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html > ). > We have not yet found a solution when more Robots can act as master and > can transmit video (i.e. we have more than one Master). > We are also waiting feedback from Wirecloud to understand how we may use > or adapt the Kurento widget. > > The guys of the Robotics team will go through your notes to check your > proposals and to define technical details if needed. > > Thank you, > Gianmario > > > *Da:* fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware- > robotics-bounces at lists.fi-ware.org] *Per conto di *Luis L?pez Fern?ndez > *Inviato:* marted? 30 giugno 2015 13:05 > *A:* Garino Pierangelo > *Cc:* amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; > fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es > *Oggetto:* Re: [Fiware-robotics] Robotics GE live demo - Kurento and > Wirecloud > > Hi Pier, > > I added several comments in your document answering your questions. In > general, I think that the general picture is OK from the perspective of > Kurento and I don't forecast any major problems. The only exception is in > relation to the WebRTC software to be embedded at the robot. In principle, > it seems that you are planning to use directly a Chrome browser instance. > This restricts a lot the type of features you may be capable of accessing > and this may require human intervention at the robot each time the webcam > is activated. I thing it should be worthy to discuss about this specific > item so that all of us are in the same page in relation to the consequences > of using directly a Chrome instance for that. > > Best regards. > > ----------------------------------------------------------- > Luis L?pez Fern?ndez > Subdirector de Investigaci?n y Relaciones con la Empresa > Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n > Universidad Rey Juan Carlos > http://www.etsit.urjc.es > e-mail: luis.lopez at urjc.es > Tf1: +34 914 888 747 > Tf2: + 34 914 888 713 > > > > > > > El 23/06/2015, a las 12:22, Garino Pierangelo < > pierangelo.garino at telecomitalia.it> escribi?: > > > Dear All, > > This message is intended to provide to Kurento and Wirecloud teams further > details about the robotics live demo we are working on, in order to make it > clearer what we?d like to achieve, and what should be implemented on their > side (particularly about wirecloud widgets and dashboard). > > We have prepared a shared document at the following link > https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# > > which refines the description of the live demo (later this doc will > merge with the workplan description we already shared in the past). > > The document is composed of three parts: > - The first one (Strep 1: Managing interactively robots) is a > refinement of live demo deliverable section 4.4.3 > - The second one (Design of step 1: Teleoperation as a Service > (TaaS)) is more or less the same contents of deliverable section 4.4.4 > - *The third part* (Detailed description (script) of demo > implementation) *is the most important one*: we took as an example the > live demo script doc that Javier distributed through the live demo mailing > lists, which seemed to us a helpful way to provide a detailed description > of the demo, both for people who will watch it and for implementers of the > demo itself. > > *We kindly ask Luis, Javier, Alvaro (*well all team members?) to go > through the description of the demo and provide us a feedback, about > how/when this can be implemented (is it meaningful/feasible, etc?), giving > possibly answer to the questions/comments we have written there. With your > support in linking with Kurento media server and developing specific > widgets, we?ll be able to ?complete the picture? and proceed straight to > the assembly of all demo parts. > > Many thanks and BR > > Pier > > > > *Da:* fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware- > robotics-bounces at lists.fi-ware.org] *Per conto di *Colombatto Davide > *Inviato:* marted? 16 giugno 2015 12:34 > *A:* Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; > amagan at conwet.com; fdelavega at fi.upm.es > *Cc:* fiware-robotics at lists.fi-ware.org > *Oggetto:* [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud > > Hi Luis and Wirecloud guys, > > We have some doubts about the use of Kurento and Wirecloud widgets for > Kurento for the Robotics Live Demo. > > 1) For what concern *Kurento*, in our past tests we tried the > tutorial > http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html > where it is said that it can be present only one WebRTC-Master and many > WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can > send the video and the others can receive the video). > Starting from this point we think the slide2 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 > depicts the Kurento One2Many architecture. > Considering what mentioned above, if we want to use two different robots > (that act as WebRTC-Masters in order to send video) do we need to use two > different Kurento Application Servers (that act as Kurento-Clients) or a > single Kurento Application Server (that acts as Kurento-Client) is able to > manage multiple robots video transmission? > > 2) For what concern *Wirecloud widgets for Kurento*, starting from > the slide2 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 > do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of > the Kurento One2Many architecture explained above in the point1? > If it is correct, for the Robotics live demo will Wirecloud also host the > Kurento Application Servers (i.e. a single one or one for each robot that > act as WebRTC-Master in order to send video) within the Wirecloud > Application Server as depicted in the slide3 at the link > https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 > ? > > Thank you, > Davide > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle > persone indicate. La diffusione, copia o qualsiasi altra azione derivante > dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora > abbiate ricevuto questo documento per errore siete cortesemente pregati di > darne immediata comunicazione al mittente e di provvedere alla sua > distruzione, Grazie. > > *This e-mail and any attachments is confidential and may contain > privileged information intended for the addressee(s) only. Dissemination, > copying, printing or use by anybody else is unauthorised. If you are not > the intended recipient, please delete this message and any attachments and > advise the sender by return e-mail, Thanks.* > *Rispetta l'ambiente. Non stampare questa mail se non ? > necessario.* > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianmario.bollano at telecomitalia.it Tue Jun 30 17:09:42 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 30 Jun 2015 15:09:42 +0000 Subject: [Fiware-robotics] R: Robotics GE live demo - Kurento and Wirecloud In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540CB56EF5@TELMBB006RM001.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F63FE244EC@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE255BB@telmbb003ba020.telecomitalia.local> Hi Luis and all, we propose a Doodle poll to select a timeslot for the call. The link is: http://doodle.com/fb6gx4wbbqupwkwu Please, select your preferred time. Gianmario Da: aarranz at conwet.com [mailto:aarranz at conwet.com] Per conto di ?lvaro Arranz Inviato: marted? 30 giugno 2015 16:55 A: Luis L?pez Fern?ndez Cc: Bollano Gianmario; Garino Pierangelo; amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi, sorry for the delay in the response, we are busy with the closing and planning phases of the sprint. Also I'm organising my travel to the Campus party event at Mexico. I'll work on providing a better feedback asap (I'll try to provide it today). Anyway, updating our widgets for accessing this one-to-many service will be easy, we can synchronise with the Kurento team for making the needed changes for selecting the master video stream, etc... This is only a thing of managing some new commands through the WebSocket connection and recreating the WebRTC connections. I don't forecast, as Luis, any problem on this side. We are also interested in join the call :). Best regards, ?lvaro On 30 June 2015 at 16:27, Luis L?pez Fern?ndez > wrote: Hi Gianmario, Modifying the Kurento demo for one-to-many to support several robots it's quite trivial. We can do it for you if necessary. This is not an issue. The main problem I detect is at the WebRTC client embedded in the robot. If this client is Chrome, then you may need human intervention for webcam capture. There are hacks for this, but we need to analyze carefully your requirements. Otherwise, the option is to compile the WebRTC Chrome stack separately and write a C++ application at the robot controlling it. This may require some more relevant efforts and this is the issue we need to discuss. I'm available during most of this week for discussing. Just propose a slot and we can try to arrange for a call. Thanks. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 30/06/2015, a las 16:21, Bollano Gianmario > escribi?: Hi Luis, thank you for your support and your clarification. As a short summary, we also have tested a WebRTC client based on Webkit but haven?t yet found the optimal solution, then it would be useful to discuss further this issue. The team has done tests with the JS version for the Kurento Client with NodeJS; our idea is to use a single App Server for the master Client and all Viewer clients as in the One-To-Many Kurento tutorial (http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html ). We have not yet found a solution when more Robots can act as master and can transmit video (i.e. we have more than one Master). We are also waiting feedback from Wirecloud to understand how we may use or adapt the Kurento widget. The guys of the Robotics team will go through your notes to check your proposals and to define technical details if needed. Thank you, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis L?pez Fern?ndez Inviato: marted? 30 giugno 2015 13:05 A: Garino Pierangelo Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, I added several comments in your document answering your questions. In general, I think that the general picture is OK from the perspective of Kurento and I don't forecast any major problems. The only exception is in relation to the WebRTC software to be embedded at the robot. In principle, it seems that you are planning to use directly a Chrome browser instance. This restricts a lot the type of features you may be capable of accessing and this may require human intervention at the robot each time the webcam is activated. I thing it should be worthy to discuss about this specific item so that all of us are in the same page in relation to the consequences of using directly a Chrome instance for that. Best regards. ----------------------------------------------------------- Luis L?pez Fern?ndez Subdirector de Investigaci?n y Relaciones con la Empresa Escuela T?cnica Superior de Ingenieros de Telecomunicaci?n Universidad Rey Juan Carlos http://www.etsit.urjc.es e-mail: luis.lopez at urjc.es Tf1: +34 914 888 747 Tf2: + 34 914 888 713 El 23/06/2015, a las 12:22, Garino Pierangelo > escribi?: Dear All, This message is intended to provide to Kurento and Wirecloud teams further details about the robotics live demo we are working on, in order to make it clearer what we?d like to achieve, and what should be implemented on their side (particularly about wirecloud widgets and dashboard). We have prepared a shared document at the following link https://docs.google.com/document/d/1a_8dBsoO-E7kaUr6fl3tXgv3Ojt4PMnsSvJwTutyxsg/edit# which refines the description of the live demo (later this doc will merge with the workplan description we already shared in the past). The document is composed of three parts: - The first one (Strep 1: Managing interactively robots) is a refinement of live demo deliverable section 4.4.3 - The second one (Design of step 1: Teleoperation as a Service (TaaS)) is more or less the same contents of deliverable section 4.4.4 - The third part (Detailed description (script) of demo implementation) is the most important one: we took as an example the live demo script doc that Javier distributed through the live demo mailing lists, which seemed to us a helpful way to provide a detailed description of the demo, both for people who will watch it and for implementers of the demo itself. We kindly ask Luis, Javier, Alvaro (well all team members?) to go through the description of the demo and provide us a feedback, about how/when this can be implemented (is it meaningful/feasible, etc?), giving possibly answer to the questions/comments we have written there. With your support in linking with Kurento media server and developing specific widgets, we?ll be able to ?complete the picture? and proceed straight to the assembly of all demo parts. Many thanks and BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: marted? 16 giugno 2015 12:34 A: Luis L?pez Fern?ndez; Javier Soriano; aarranz at fi.upm.es; amagan at conwet.com; fdelavega at fi.upm.es Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ? of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Tue Jun 30 17:22:02 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 30 Jun 2015 15:22:02 +0000 Subject: [Fiware-robotics] Demo Sprint 4.3.3 Message-ID: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: * Use hangout * Use FIROS vers1 * In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server * Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) * Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes * RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement * Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: * hidden slides have to be rewritten/completed * (if required) slide's comments have to be rewritten Let we know, BR Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE_Robotics_Demo_201507-v1.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 428700 bytes Desc: FIWARE_Robotics_Demo_201507-v1.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Jun 30 17:35:38 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 30 Jun 2015 15:35:38 +0000 Subject: [Fiware-robotics] R: Demo Sprint 4.3.3 In-Reply-To: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD35416F8A2D0@TELMBB006RM001.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F63FE25629@telmbb003ba020.telecomitalia.local> Hi, fine for me. If we can show something also with an updated FIROS it would be even better, otherwise we will do in a next demo. Also please remember to pick a timeslot in the doodle for the Call with Kurento and Wirecloud, we'll have support for Kurento and Wirecloud Widgets development and that will be really helpful. Gianmario Da: Colombatto Davide Inviato: marted? 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI's office like that shown this morning. Some additional points: ? Use hangout ? Use FIROS vers1 ? In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server ? Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) ? Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes ? RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot's movement ? Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: ? hidden slides have to be rewritten/completed ? (if required) slide's comments have to be rewritten Let we know, BR Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: