From gianmario.bollano at telecomitalia.it Tue Apr 14 15:11:53 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 14 Apr 2015 13:11:53 +0000 Subject: [Fiware-robotics] Robotics call Message-ID: <7E649CBD84A947498203DAF8F098B1F62C49F10C@telmba003ba020.telecomitalia.local> Dear all, I remind you of the Robotics Call today at 16.00. If you haven't different suggestions or needs, we can use Hangouts for the voice call as done in the past meetings. (Please apologize if you have received two copies of this notification). Best, Gianmario Bollano 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: 2626 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From ahernandez at ikergune.com Tue Apr 14 15:43:36 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Tue, 14 Apr 2015 15:43:36 +0200 Subject: [Fiware-robotics] Robotics call In-Reply-To: <7E649CBD84A947498203DAF8F098B1F62C49F10C@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F62C49F10C@telmba003ba020.telecomitalia.local> Message-ID: Hello all, We just moved to a new office and are having some issues with Internet speeds and disconnections. We will do our best to get online anyway. Angel Hernandez R&D Project Manager +34 661 150 167 -------- Original Message -------- From: Bollano Gianmario Sent: Tuesday, April 14, 2015 03:11 PM To: fiware-robotics at lists.fi-ware.org Subject: [Fiware-robotics] Robotics call Dear all, I remind you of the Robotics Call today at 16.00. If you haven?t different suggestions or needs, we can use Hangouts for the voice call as done in the past meetings. (Please apologize if you have received two copies of this notification). Best, Gianmario Bollano Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer] 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 Apr 14 15:51:44 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 14 Apr 2015 13:51:44 +0000 Subject: [Fiware-robotics] Accettata: Robotics call Message-ID: <069906BED271EB4A883BD9578DCDD3540CB07A1D@telmbc006ba020.telecomitalia.local> Hangout is ok. As the RCM's Feature "FIROSInteraction" is approaching, me and Roberto have slightly refined the old interaction btw the components RCM and FIROS. In particular our proposal adds a feedback (i.e. ROS message rcm_msgs/CB_Event on /cb_event topic) from FIROS to RCM Driver where FIROS publishes to RCM the event about the correctly creation/deletion of the entry in the CB. I attach the new interaction model in this email so ET guys can tell us if they agree with the proposal. 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: not available Type: text/calendar Size: 1870 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIROS_RCM_v3.0.pdf Type: application/pdf Size: 243730 bytes Desc: FIROS_RCM_v3.0.pdf 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 Apr 14 16:28:18 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 14 Apr 2015 14:28:18 +0000 Subject: [Fiware-robotics] R: Robotics call In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F62C49F10C@telmba003ba020.telecomitalia.local> Message-ID: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo/edit Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: marted? 14 aprile 2015 15:44 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Robotics call Hello all, We just moved to a new office and are having some issues with Internet speeds and disconnections. We will do our best to get online anyway. Angel Hernandez R&D Project Manager +34 661 150 167 -------- Original Message -------- From: Bollano Gianmario Sent: Tuesday, April 14, 2015 03:11 PM To: fiware-robotics at lists.fi-ware.org Subject: [Fiware-robotics] Robotics call Dear all, I remind you of the Robotics Call today at 16.00. If you haven?t different suggestions or needs, we can use Hangouts for the voice call as done in the past meetings. (Please apologize if you have received two copies of this notification). Best, Gianmario Bollano Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]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 Apr 14 17:30:39 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 14 Apr 2015 15:30:39 +0000 Subject: [Fiware-robotics] FIROS_RCM_v3.0 on Google Docs Message-ID: <069906BED271EB4A883BD9578DCDD3540CB07B17@telmbc006ba020.telecomitalia.local> Hi all, this is the link about the document we talked about in the call: https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit D Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From davide.colombatto at telecomitalia.it Tue Apr 14 18:04:58 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 14 Apr 2015 16:04:58 +0000 Subject: [Fiware-robotics] (no subject) Message-ID: <069906BED271EB4A883BD9578DCDD3540CB07BB7@telmbc006ba020.telecomitalia.local> Hi all, in the attached file there is depicted the solution that I tried with Kurento some time ago. The KMS on the FIWARE Lab is an instance started by the Kurento image available on the Lab and updated to the new version of Kurento (as they told to Inigo in an old email). Inigo, do you confirm that you tried the same solution but maintaining both KMS and KAS on your ET machines? For me, this solution works but not perfectly: the video/audio has not always a good quality and sometimes the KAS (on my machine) goes down. As I said I'm not able to use the Trento node because it don't give me a public IP. 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: Kurento.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 37125 bytes Desc: Kurento.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 igonzalez at ikergune.com Wed Apr 15 10:08:46 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Wed, 15 Apr 2015 10:08:46 +0200 Subject: [Fiware-robotics] (no subject) References: <069906BED271EB4A883BD9578DCDD3540CB07BB7@telmbc006ba020.telecomitalia.local> Message-ID: Hi, streaming video with kurento on fiware lab worked. But we also wanted to try the kurento's video processing capabilities to make smart robots (object recognition, crowd detection, plate reader...) And those examples didn't worked with the kurento's deployment in fiware lab. We have our own kurento deployed in our machines working with the kurento filters, and we have been working on an app that doesnt' need chrome to stream video tu KMS and use their filters. Regards, i?igo On 14/04/15 18:04, Colombatto Davide wrote: Hi all, in the attached file there is depicted the solution that I tried with Kurento some time ago. The KMS on the FIWARE Lab is an instance started by the Kurento image available on the Lab and updated to the new version of Kurento (as they told to Inigo in an old email). Inigo, do you confirm that you tried the same solution but maintaining both KMS and KAS on your ET machines? For me, this solution works but not perfectly: the video/audio has not always a good quality and sometimes the KAS (on my machine) goes down. As I said I'm not able to use the Trento node because it don't give me a public IP. Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Thu Apr 16 12:17:01 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 16 Apr 2015 10:17:01 +0000 Subject: [Fiware-robotics] CB-Proxy Message-ID: <069906BED271EB4A883BD9578DCDD3540CB09451@telmbc006ba020.telecomitalia.local> Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? 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 Thu Apr 16 16:39:38 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 16 Apr 2015 14:39:38 +0000 Subject: [Fiware-robotics] R: Live Demo phase 1 Message-ID: <7E649CBD84A947498203DAF8F098B1F62C49FE17@telmba003ba020.telecomitalia.local> Hi all, thank you Davide for the contributions (docs and slide) and Inigo for the explanation about the tests done with Kurento. Below are some interesting points arising from this discussion and the last Robotics call: 1. We have decided to use Google Docs to share information and speedup development. For what concern the FIROS-RCM communication. a. If you you agree I would suggest to use and update the proposal in the google doc FIROS_RCM_v3.0.docx prepared by Davide. b. We still have to define more in detail the format of the messages we would use in the first demo, specifically messages to control the robot movement: ? how many types of movement? ? which type of control needed? (it may depends on Robots type) ? Will we have controls also for the movement of the camera? c. We may need further messages, beside those already defined till now: ? RCM_Event for connection/disconnection of robots, ? FIROS_Info for message type and communication type supported by any Robot, ? CB_Event when instances are created or removed from CB For instance, a message might be required after RCM master launch FIROS, when FIROS is up and working. d. If we want to control more than one robot, let's say at least 2 robots (as in the requirements of the demo) , we still have to decide if we have ? one FIROS instance for all robots and how name unambiguously the robot names, ? or more FIROS instances (with different names), one for robot or maybe one for location if robots are in different sites 2. Kurento: Davide and Inigo have tried two different setup. We are free to define the best setup for the demo but there are some point we need to consider carefully: a. One of the WebRTC endpoint (for video transmission) is in the Robot, thus the simplest solution might be chrome in a Linux environment. Having KAS (with node.js) is maybe possible but it might require excessive resources for a Linux environment hosted on a robot. b. For the other WebRTC endpoint (where the Control demo GUI app resides) we do not need chrome but obviously we should have stream compatibility with the other Chrome (on the Robot) endpoint. That might imply format and throughput of video stream. c. The KAS (Kurento App Server) might be hosted in the same machine with the RCM_Master. This machine might need to receive commands from the Control Demo Gui App then it should have public address if we want the Control GUI to register dynamically as webRTC endpoint. d. The KMS ideally should be the one in FIWARE lab, because that's one of the keypoint of the live demo:give example of usage of GEs available be the FIWARE lab. If however we'll find trouble in using the kurento filters, we can stick to a local KMS. e. Do we need Kurento filters for the first Teleoperation demo? f. If we don't need any specific kurento filter, shouldn't we use a Kurento Video-transmission widget made available by Wirecloud instead? In that case maybe we would not need a local KAS (if the widget already connect to a public one) and hopefully we would be able to use Kurento in FIWARE lab. Were you able to make any test in this setup? 3. Robots: a. Will we have more than one robots, also of different types? b. Will we have some Robots in Italy and other in Spain, or all the robots will be in the same site? Best, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: mercoled? 15 aprile 2015 10:09 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] (no subject) Hi, streaming video with kurento on fiware lab worked. But we also wanted to try the kurento's video processing capabilities to make smart robots (object recognition, crowd detection, plate reader...) And those examples didn't worked with the kurento's deployment in fiware lab. We have our own kurento deployed in our machines working with the kurento filters, and we have been working on an app that doesnt' need chrome to stream video tu KMS and use their filters. Regards, i?igo On 14/04/15 18:04, Colombatto Davide wrote: Hi all, in the attached file there is depicted the solution that I tried with Kurento some time ago. The KMS on the FIWARE Lab is an instance started by the Kurento image available on the Lab and updated to the new version of Kurento (as they told to Inigo in an old email). Inigo, do you confirm that you tried the same solution but maintaining both KMS and KAS on your ET machines? For me, this solution works but not perfectly: the video/audio has not always a good quality and sometimes the KAS (on my machine) goes down. As I said I'm not able to use the Trento node because it don't give me a public IP. Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From igonzalez at ikergune.com Thu Apr 16 16:58:37 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Thu, 16 Apr 2015 16:58:37 +0200 Subject: [Fiware-robotics] CB-Proxy References: <069906BED271EB4A883BD9578DCDD3540CB09451@telmbc006ba020.telecomitalia.local> Message-ID: Hi Davide, I have to say that the proxy isn't available. As we said some time ago that proxy was a temporary solution to try firos with a control panel we had, and we are not using it anymore, so we deleted it. Anyway, as we have changed from office we haven't got our own Internet connection yet, so my PC cannot be accessed from outside the network, making me impossible to help you with this. All I can do is send you the html code of the demo. I have been thinking about possible solutions with our current environment (since the only reason of using the proxy was the CORS policy with the context broker): 1. Edit the javascript code I have sent you (app.js) change there the proxy's address with the one of the context broker (the one that you have configured in your firos instance) and launch chrome without the security flag so the CORS policy will be avoided. 2. Create a little server application that allows CORS and redirects all the requests to another url (the cb one). 3. Don't use the demo page, and use native code (java python, c++...) to make requests to the context broker. Also I have read the documentation you sent about firos and RCM integration, and we are agree with what it is said on it, but I want to add some changes: 1. We should add namespaces to the topics, in firos we already had a topic for robot connection and disconnection and the namespace was firos: /firos/connect, /firos/disconnect So we think is interesting that topics to which firos publishes to should be in the "firos" namespace and the ones of rcm in "rcm" namespace for example. This is a way to have the topics well organized. 2. The CB_Event object is defined as string instance_name, int16 entity_status. We think both must be instances or entities (same name), but not one instance and the other one entity. As in this case we are talking about the context broker, we think is better to call both entity. What do you think about these changes? Should I add them to the document? We have been developing in firos what is said in the document. The communication defined in the document is developed and working, and we have also created a service that emulates what RCM sends to firos to try the full proccess and it seems to work. And this process seems to have sense. Regards, I?igo On 16/04/15 12:16, Colombatto Davide wrote: Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: roboticsdemo.tar.gz Type: application/gzip Size: 129883 bytes Desc: roboticsdemo.tar.gz URL: From roberto1.antonini at telecomitalia.it Fri Apr 17 11:29:41 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Fri, 17 Apr 2015 09:29:41 +0000 Subject: [Fiware-robotics] R: R: Live Demo phase 1 In-Reply-To: <7E649CBD84A947498203DAF8F098B1F62C49FE17@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F62C49FE17@telmba003ba020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8643D339B0@TELMBB001BA020.telecomitalia.local> My answer online ... 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? 16 aprile 2015 16:40 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Live Demo phase 1 Hi all, thank you Davide for the contributions (docs and slide) and Inigo for the explanation about the tests done with Kurento. Below are some interesting points arising from this discussion and the last Robotics call: 1. We have decided to use Google Docs to share information and speedup development. For what concern the FIROS-RCM communication. a. If you you agree I would suggest to use and update the proposal in the google doc FIROS_RCM_v3.0.docx prepared by Davide. b. We still have to define more in detail the format of the messages we would use in the first demo, specifically messages to control the robot movement: ? how many types of movement? R: For the first phase, I would only consider differential drive robots ? which type of control needed? (it may depends on Robots type) R: ROS abstraction typically suggests geometry_msgs/Twist ROS type message to control robot movement as a standard de-facto, if different ROS message types were requested, an adaption is needed which reflects that message to CB entity attribute making use of Twist type, ET correct me if I'm wrong. ? Will we have controls also for the movement of the camera? R: For the very first phase, I wouldn't consider a PTZ camera, if desired then a ROS (or to be ROSified) PTZ command is needed, the last part of above consideration/answer could be applied also for this answer: you (ET) need to take into consideration a new message type to control PTZ camera. c. We may need further messages, beside those already defined till now: ? RCM_Event for connection/disconnection of robots, ? FIROS_Info for message type and communication type supported by any Robot, ? CB_Event when instances are created or removed from CB R: in my opinion, these message should suffice our needs, your (of ET) considerations are warmly welcomed. For instance, a message might be required after RCM master launch FIROS, when FIROS is up and working. d. If we want to control more than one robot, let's say at least 2 robots (as in the requirements of the demo) , we still have to decide if we have ? one FIROS instance for all robots and how name unambiguously the robot names, ? or more FIROS instances (with different names), one for robot or maybe one for location if robots are in different sites 2. Kurento: Davide and Inigo have tried two different setup. We are free to define the best setup for the demo but there are some point we need to consider carefully: a. One of the WebRTC endpoint (for video transmission) is in the Robot, thus the simplest solution might be chrome in a Linux environment. Having KAS (with node.js) is maybe possible but it might require excessive resources for a Linux environment hosted on a robot. b. For the other WebRTC endpoint (where the Control demo GUI app resides) we do not need chrome but obviously we should have stream compatibility with the other Chrome (on the Robot) endpoint. That might imply format and throughput of video stream. c. The KAS (Kurento App Server) might be hosted in the same machine with the RCM_Master. This machine might need to receive commands from the Control Demo Gui App then it should have public address if we want the Control GUI to register dynamically as webRTC endpoint. d. The KMS ideally should be the one in FIWARE lab, because that's one of the keypoint of the live demo:give example of usage of GEs available be the FIWARE lab. If however we'll find trouble in using the kurento filters, we can stick to a local KMS. e. Do we need Kurento filters for the first Teleoperation demo? f. If we don't need any specific kurento filter, shouldn't we use a Kurento Video-transmission widget made available by Wirecloud instead? In that case maybe we would not need a local KAS (if the widget already connect to a public one) and hopefully we would be able to use Kurento in FIWARE lab. Were you able to make any test in this setup? 3. Robots: a. Will we have more than one robots, also of different types? b. Will we have some Robots in Italy and other in Spain, or all the robots will be in the same site? Best, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: mercoled? 15 aprile 2015 10:09 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] (no subject) Hi, streaming video with kurento on fiware lab worked. But we also wanted to try the kurento's video processing capabilities to make smart robots (object recognition, crowd detection, plate reader...) And those examples didn't worked with the kurento's deployment in fiware lab. We have our own kurento deployed in our machines working with the kurento filters, and we have been working on an app that doesnt' need chrome to stream video tu KMS and use their filters. Regards, i?igo On 14/04/15 18:04, Colombatto Davide wrote: Hi all, in the attached file there is depicted the solution that I tried with Kurento some time ago. The KMS on the FIWARE Lab is an instance started by the Kurento image available on the Lab and updated to the new version of Kurento (as they told to Inigo in an old email). Inigo, do you confirm that you tried the same solution but maintaining both KMS and KAS on your ET machines? For me, this solution works but not perfectly: the video/audio has not always a good quality and sometimes the KAS (on my machine) goes down. As I said I'm not able to use the Trento node because it don't give me a public IP. Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Mon Apr 20 10:48:39 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Mon, 20 Apr 2015 08:48:39 +0000 Subject: [Fiware-robotics] I: CB-Proxy In-Reply-To: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> Message-ID: <069906BED271EB4A883BD9578DCDD3540CB0AB58@telmbc006ba020.telecomitalia.local> Hi Inigo, Sorry, but for unknown problems me and Roberto didn't receive your response below last week (Fabio received it and shows us your email). Related to your questions about FIROS-RMC Integration: 1. I don't understand what is the use of your topics /firos/connect and /firos/disconnect; should they replace the /cb_event or you only say to modify /cb_event in firos/cb_event? N.B. /cb_event (or firos/cb_event) should be the event which notifies the correct creation/deletion of the robot entity in the CB (performed by FIROS) 2. I agree to call both "entity" but I'd like to highlight that the following String must be the same in the lifecycle of a Robot Connection process: RCM -> FIROS instance_name of rcm_msgs/RCM_Event FIROS -> RCM robot_name of rcm_msgs/FIROS_Info FIROS -> RCM instance_name/entity_name of rcm_msgs/CB_Event All of them values have to be referred to the robot name (i.e. instance_name of rcm_msgs/RCM_Event). In particular the entity name in the CB should be the same received as instance_name of rcm_msgs/RCM_Event. Are you agree? After these clarifications, you can modify the documents of Google Docs. Thanks, Davide Da: fabio.dibenedetto at consoft.it [mailto:fabio.dibenedetto at consoft.it] Inviato: luned? 20 aprile 2015 09:08 A: Colombatto Davide Oggetto: I: CB-Proxy Di seguito la mail di cui ti parlavo: e' scritta a te e a fiware-robotics quindi sicuramente ce l'hai da qualche parte Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: gioved? 16 aprile 2015 16:59 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] CB-Proxy Hi Davide, I have to say that the proxy isn't available. As we said some time ago that proxy was a temporary solution to try firos with a control panel we had, and we are not using it anymore, so we deleted it. Anyway, as we have changed from office we haven't got our own Internet connection yet, so my PC cannot be accessed from outside the network, making me impossible to help you with this. All I can do is send you the html code of the demo. I have been thinking about possible solutions with our current environment (since the only reason of using the proxy was the CORS policy with the context broker): 1. Edit the javascript code I have sent you (app.js) change there the proxy's address with the one of the context broker (the one that you have configured in your firos instance) and launch chrome without the security flag so the CORS policy will be avoided. 2. Create a little server application that allows CORS and redirects all the requests to another url (the cb one). 3. Don't use the demo page, and use native code (java python, c++...) to make requests to the context broker. Also I have read the documentation you sent about firos and RCM integration, and we are agree with what it is said on it, but I want to add some changes: 1. We should add namespaces to the topics, in firos we already had a topic for robot connection and disconnection and the namespace was firos: /firos/connect, /firos/disconnect So we think is interesting that topics to which firos publishes to should be in the "firos" namespace and the ones of rcm in "rcm" namespace for example. This is a way to have the topics well organized. 2. The CB_Event object is defined as string instance_name, int16 entity_status. We think both must be instances or entities (same name), but not one instance and the other one entity. As in this case we are talking about the context broker, we think is better to call both entity. What do you think about these changes? Should I add them to the document? We have been developing in firos what is said in the document. The communication defined in the document is developed and working, and we have also created a service that emulates what RCM sends to firos to try the full proccess and it seems to work. And this process seems to have sense. Regards, I?igo On 16/04/15 12:16, Colombatto Davide wrote: Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? 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: From igonzalez at ikergune.com Mon Apr 20 14:05:53 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Mon, 20 Apr 2015 14:05:53 +0200 Subject: [Fiware-robotics] I: CB-Proxy References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB0AB58@telmbc006ba020.telecomitalia.local> Message-ID: Hi Davide, I answer you on your mail: On 20/04/15 10:48, Colombatto Davide wrote: Hi Inigo, Sorry, but for unknown problems me and Roberto didn?t receive your response below last week (Fabio received it and shows us your email). Related to your questions about FIROS-RMC Integration: 1. I don?t understand what is the use of your topics /firos/connect and /firos/disconnect; should they replace the /cb_event or you only say to modify /cb_event in firos/cb_event? N.B. /cb_event (or firos/cb_event) should be the event which notifies the correct creation/deletion of the robot entity in the CB (performed by FIROS) Those topics won't replace any of the ones you said. We did a little temporary watchdog to understand how robots work on ROS and those topics were done to notify firos about robot connection and disconnection. We have created the topics you said, and we also reused code of our previous topics to do the tasks you said. The modification I mean was to do a /firos/cb_event instead of /cb_event and calling both attributtes with entity 2. I agree to call both ?entity? but I?d like to highlight that the following String must be the same in the lifecycle of a Robot Connection process: RCM -> FIROS instance_name of rcm_msgs/RCM_Event FIROS -> RCM robot_name of rcm_msgs/FIROS_Info FIROS -> RCM instance_name/entity_name of rcm_msgs/CB_Event All of them values have to be referred to the robot name (i.e. instance_name of rcm_msgs/RCM_Event). In particular the entity name in the CB should be the same received as instance_name of rcm_msgs/RCM_Event. Are you agree? Ok After these clarifications, you can modify the documents of Google Docs. Thanks, Davide Regards, I?igo -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Mon Apr 20 16:36:32 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Mon, 20 Apr 2015 14:36:32 +0000 Subject: [Fiware-robotics] R: I: CB-Proxy In-Reply-To: References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB0AB58@telmbc006ba020.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD3540CB0AFE0@telmbc006ba020.telecomitalia.local> Hi I?igo, Ok, you can change the doc in Google Docs, finally I suppose you propose the following changes: ? rcm/robot_event (topic) ? rcm/firos_info (service) ? firos/cb_event (topic) What about the packages for ROS messages: do you agree to maintain a unique package for ROS messages shared btw RCM and FIROS? In the documents we called it "rcm_msgs"; do you prefer something like "robotics_msgs"? Thanks, Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: luned? 20 aprile 2015 14:06 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org; Garino Pierangelo Oggetto: Re: I: CB-Proxy Hi Davide, I answer you on your mail: On 20/04/15 10:48, Colombatto Davide wrote: Hi Inigo, Sorry, but for unknown problems me and Roberto didn't receive your response below last week (Fabio received it and shows us your email). Related to your questions about FIROS-RMC Integration: 1. I don't understand what is the use of your topics /firos/connect and /firos/disconnect; should they replace the /cb_event or you only say to modify /cb_event in firos/cb_event? N.B. /cb_event (or firos/cb_event) should be the event which notifies the correct creation/deletion of the robot entity in the CB (performed by FIROS) Those topics won't replace any of the ones you said. We did a little temporary watchdog to understand how robots work on ROS and those topics were done to notify firos about robot connection and disconnection. We have created the topics you said, and we also reused code of our previous topics to do the tasks you said. The modification I mean was to do a /firos/cb_event instead of /cb_event and calling both attributtes with entity 2. I agree to call both "entity" but I'd like to highlight that the following String must be the same in the lifecycle of a Robot Connection process: RCM -> FIROS instance_name of rcm_msgs/RCM_Event FIROS -> RCM robot_name of rcm_msgs/FIROS_Info FIROS -> RCM instance_name/entity_name of rcm_msgs/CB_Event All of them values have to be referred to the robot name (i.e. instance_name of rcm_msgs/RCM_Event). In particular the entity name in the CB should be the same received as instance_name of rcm_msgs/RCM_Event. Are you agree? Ok After these clarifications, you can modify the documents of Google Docs. Thanks, Davide Regards, I?igo 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 Apr 21 10:14:10 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 21 Apr 2015 10:14:10 +0200 Subject: [Fiware-robotics] Today's robotics call Message-ID: Hi everybody, I've not received the hangout invitation for todays robotics call. We're having some issues with the Internet connection, could you confirm me that you've sent it? BR -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From davide.colombatto at telecomitalia.it Tue Apr 21 10:24:31 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 21 Apr 2015 08:24:31 +0000 Subject: [Fiware-robotics] Today's robotics call In-Reply-To: References: Message-ID: <069906BED271EB4A883BD9578DCDD3540CB0B4BE@telmbc006ba020.telecomitalia.local> Hi, We have invited you and others but none is joining in the call Davide, Roberto and Fabio. ________________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] per conto di Jose Jaime Ariza [jjaime at ikergune.com] Inviato: marted? 21 aprile 2015 10.14 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Today's robotics call Hi everybody, I've not received the hangout invitation for todays robotics call. We're having some issues with the Internet connection, could you confirm me that you've sent it? 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. From gianmario.bollano at telecomitalia.it Tue Apr 21 10:27:27 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 21 Apr 2015 08:27:27 +0000 Subject: [Fiware-robotics] Errors in connection Message-ID: <7E649CBD84A947498203DAF8F098B1F62C4A193B@telmba003ba020.telecomitalia.local> Hi all, I apologize I'm still having troubles to connect with hangout from the office. I hoped to have solved these issues after the updates (firefox and Google plugins) but the connection still continue to close itself with error... ------------------------------------------------------------------------------------ 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 igonzalez at ikergune.com Tue Apr 21 14:02:22 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Tue, 21 Apr 2015 14:02:22 +0200 Subject: [Fiware-robotics] I: CB-Proxy References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB0AB58@telmbc006ba020.telecomitalia.local> Message-ID: Hi, as I said before, here you have the code with the url changed. Regards, I?igo On 20/04/15 14:05, I?igo Gonzalez wrote: Hi Davide, I answer you on your mail: On 20/04/15 10:48, Colombatto Davide wrote: Hi Inigo, Sorry, but for unknown problems me and Roberto didn?t receive your response below last week (Fabio received it and shows us your email). Related to your questions about FIROS-RMC Integration: 1. I don?t understand what is the use of your topics /firos/connect and /firos/disconnect; should they replace the /cb_event or you only say to modify /cb_event in firos/cb_event? N.B. /cb_event (or firos/cb_event) should be the event which notifies the correct creation/deletion of the robot entity in the CB (performed by FIROS) Those topics won't replace any of the ones you said. We did a little temporary watchdog to understand how robots work on ROS and those topics were done to notify firos about robot connection and disconnection. We have created the topics you said, and we also reused code of our previous topics to do the tasks you said. The modification I mean was to do a /firos/cb_event instead of /cb_event and calling both attributtes with entity 2. I agree to call both ?entity? but I?d like to highlight that the following String must be the same in the lifecycle of a Robot Connection process: RCM -> FIROS instance_name of rcm_msgs/RCM_Event FIROS -> RCM robot_name of rcm_msgs/FIROS_Info FIROS -> RCM instance_name/entity_name of rcm_msgs/CB_Event All of them values have to be referred to the robot name (i.e. instance_name of rcm_msgs/RCM_Event). In particular the entity name in the CB should be the same received as instance_name of rcm_msgs/RCM_Event. Are you agree? Ok After these clarifications, you can modify the documents of Google Docs. Thanks, Davide Regards, I?igo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: roboticsdemo.tar.gz Type: application/gzip Size: 129912 bytes Desc: roboticsdemo.tar.gz URL: From jjaime at ikergune.com Tue Apr 21 16:41:35 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 21 Apr 2015 16:41:35 +0200 Subject: [Fiware-robotics] Live demos work plan Message-ID: Hi all, As commented in today's call, here you can find the work plan draft: https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit# Please, make any changes you consider appropriate. BR, Pepe. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From gianmario.bollano at telecomitalia.it Wed Apr 22 11:34:07 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Wed, 22 Apr 2015 09:34:07 +0000 Subject: [Fiware-robotics] Using Zip with password for exchange attachments Message-ID: <7E649CBD84A947498203DAF8F098B1F62C4A2ABE@telmba003ba020.telecomitalia.local> Hi all, we are experiencing some failure of e-mail delivery with attachments containing scripts (JS/HTML,etc), and have recently missed some e-mails with attachments sent to Telecomitalia. This is probably due to a nasty update of the Antispam-Antivirus Mailer which now it seems to block an entire e-mail delivery, not only any suspicious attachments. To overcome this problem, I would suggest to send attachment : - Inside a ZIP file (or 7-ZIP) WITH a PASSWORD - As password we can use "robotics" or any other you'd suggest: this is only required to avoid the central antivirus opening and deleting the attachment. In this way, both attachment and e-mail should be delivered. We can also use dropbox if attachment will be significantly larger. Pier and me suggested this trick yesterday (as we wrote in the Robotics Minutes) but we had an involuntary muting in the session and then an echo effect, then I think it would be important to notify it again. 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 davide.colombatto at telecomitalia.it Wed Apr 22 14:42:19 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Wed, 22 Apr 2015 12:42:19 +0000 Subject: [Fiware-robotics] CB-Proxy In-Reply-To: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> Message-ID: <069906BED271EB4A883BD9578DCDD3540CB0BCA6@telmbc006ba020.telecomitalia.local> Hi Inigo, I have some troubles with the web-app code you sent me (that with the ip address of the CB and not of the old CB-Proxy). Below there are the steps I did: 1) Start chrome with the security flag disabled; the CB response is: 415 Unsupported Media Type
not supported content type: application/x-www-form-urlencoded
 2) In the etxetar.js - Add to the ajax request contentType:"application/json; charset=utf-8"; the response from CB is: 406 Not Acceptable
acceptable MIME types: 'application/xml, application/json'. Accept header in request: 'undefined'
 3) In the etxetar.js - Remove accepts:"application/json; charset=utf-8" (or changing it to accepts: {text: "application/json; charset=utf-8"}); the response of CB is: 400 Bad Request
JSON Parse Error: (1): expected object
 It seems it is related to encoding (charset). The Request sent by ajax is serialized as: 1. contextElements%5B0%5D%5Bid%5D=turtle1&contextElements%5B0%5D%5Btype%5D=ROBOT&contextElements%5B0%5D%5BisPattern%5D=false&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bname%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Btype%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bvalue%5D%5B%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bname%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Btype%5D=NotYet&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bvalue%5D=%7B'linear'%3A%7B'x'%3A0.5%2C'y'%3A0%2C'z'%3A0%7D%2C'angular'%3A%7B'x'%3A0%2C'y'%3A0%2C'z'%3A0%7D%2C'firosstamp'%3A1429705669659%7D&updateAction=APPEND Do you know how to resolve this problem in order to use that web-app (avoiding to implement the other two solutions you proposed) to do my test? Maybe the CB-Proxy you used in the past modify the requests before sending it to the CB.. I remember you that we (Telecom) don't receive attached files of scripts if they aren't in a zip file protected by password. Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: gioved? 16 aprile 2015 16:59 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] CB-Proxy Hi Davide, I have to say that the proxy isn't available. As we said some time ago that proxy was a temporary solution to try firos with a control panel we had, and we are not using it anymore, so we deleted it. Anyway, as we have changed from office we haven't got our own Internet connection yet, so my PC cannot be accessed from outside the network, making me impossible to help you with this. All I can do is send you the html code of the demo. I have been thinking about possible solutions with our current environment (since the only reason of using the proxy was the CORS policy with the context broker): 1. Edit the javascript code I have sent you (app.js) change there the proxy's address with the one of the context broker (the one that you have configured in your firos instance) and launch chrome without the security flag so the CORS policy will be avoided. 2. Create a little server application that allows CORS and redirects all the requests to another url (the cb one). 3. Don't use the demo page, and use native code (java python, c++...) to make requests to the context broker. Also I have read the documentation you sent about firos and RCM integration, and we are agree with what it is said on it, but I want to add some changes: 1. We should add namespaces to the topics, in firos we already had a topic for robot connection and disconnection and the namespace was firos: /firos/connect, /firos/disconnect So we think is interesting that topics to which firos publishes to should be in the "firos" namespace and the ones of rcm in "rcm" namespace for example. This is a way to have the topics well organized. 2. The CB_Event object is defined as string instance_name, int16 entity_status. We think both must be instances or entities (same name), but not one instance and the other one entity. As in this case we are talking about the context broker, we think is better to call both entity. What do you think about these changes? Should I add them to the document? We have been developing in firos what is said in the document. The communication defined in the document is developed and working, and we have also created a service that emulates what RCM sends to firos to try the full proccess and it seems to work. And this process seems to have sense. Regards, I?igo On 16/04/15 12:16, Colombatto Davide wrote: Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? 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 Thu Apr 23 18:22:38 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 23 Apr 2015 16:22:38 +0000 Subject: [Fiware-robotics] RCM - FIROS Interaction Message-ID: <069906BED271EB4A883BD9578DCDD3540CB0C9B5@telmbc006ba020.telecomitalia.local> Hi all, I have slightly modified the shared document at link https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit with the requests about the name convention talked about in the last days; I ask you to check if they are aligned with the ET requests. I also put an example of the configuration data ("json schema" exchanged from RCM_DRIVER to FIROS) that ET sent us some months ago; In the comments there are some doubts that we have about that example. Waiting for your feedbacks. 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 roberto1.antonini at telecomitalia.it Fri Apr 24 11:19:13 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Fri, 24 Apr 2015 09:19:13 +0000 Subject: [Fiware-robotics] R: Live demos work plan In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA8643D3530B@TELMBB001BA020.telecomitalia.local> Hi all, thanks for your work, I added some comments in the doc, the most of them ask you to made task description clearer perhaps with some examples in order to avoid future misunderstanding. BR Roberto -----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? 21 aprile 2015 16:42 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demos work plan Hi all, As commented in today's call, here you can find the work plan draft: https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit# Please, make any changes you consider appropriate. 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 jjaime at ikergune.com Fri Apr 24 16:15:42 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 24 Apr 2015 16:15:42 +0200 Subject: [Fiware-robotics] R: Live demos work plan References: <246C286B275B1B46A255552CD236DA8643D3530B@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, Thank you very much for your comments, Roberto. I've answered them. I've not made any modification, I think it's better to make them after Tuesday's call. BR, Pepe. On 24/04/15 11:18, Antonini Roberto wrote: > Hi all, > thanks for your work, I added some comments in the doc, the most of them ask you to made task description clearer perhaps with some examples in order to avoid future misunderstanding. > > BR > Roberto > > -----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? 21 aprile 2015 16:42 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Live demos work plan > > Hi all, > > As commented in today's call, here you can find the work plan draft: > https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit# > > Please, make any changes you consider appropriate. > > 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. > > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From igonzalez at ikergune.com Mon Apr 27 10:01:56 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Mon, 27 Apr 2015 10:01:56 +0200 Subject: [Fiware-robotics] CB-Proxy References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB0BCA6@telmbc006ba020.telecomitalia.local> Message-ID: Hi Davide, here you have a new etxetar.js file. I have done several trials and I hope this one works for you. Regards, I?igo On 22/04/15 14:41, Colombatto Davide wrote: Hi Inigo, I have some troubles with the web-app code you sent me (that with the ip address of the CB and not of the old CB-Proxy). Below there are the steps I did: 1) Start chrome with the security flag disabled; the CB response is: 415 Unsupported Media Type
not supported content type: application/x-www-form-urlencoded
 2) In the etxetar.js - Add to the ajax request contentType:"application/json; charset=utf-8"; the response from CB is: 406 Not Acceptable
acceptable MIME types: 'application/xml, application/json'. Accept header in request: 'undefined'
 3) In the etxetar.js - Remove accepts:"application/json; charset=utf-8" (or changing it to accepts: {text: "application/json; charset=utf-8"}); the response of CB is: 400 Bad Request
JSON Parse Error: (1): expected object
 It seems it is related to encoding (charset). The Request sent by ajax is serialized as: 1. contextElements%5B0%5D%5Bid%5D=turtle1&contextElements%5B0%5D%5Btype%5D=ROBOT&contextElements%5B0%5D%5BisPattern%5D=false&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bname%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Btype%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bvalue%5D%5B%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bname%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Btype%5D=NotYet&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bvalue%5D=%7B'linear'%3A%7B'x'%3A0.5%2C'y'%3A0%2C'z'%3A0%7D%2C'angular'%3A%7B'x'%3A0%2C'y'%3A0%2C'z'%3A0%7D%2C'firosstamp'%3A1429705669659%7D&updateAction=APPEND Do you know how to resolve this problem in order to use that web-app (avoiding to implement the other two solutions you proposed) to do my test? Maybe the CB-Proxy you used in the past modify the requests before sending it to the CB.. I remember you that we (Telecom) don't receive attached files of scripts if they aren't in a zip file protected by password. Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: gioved? 16 aprile 2015 16:59 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] CB-Proxy Hi Davide, I have to say that the proxy isn't available. As we said some time ago that proxy was a temporary solution to try firos with a control panel we had, and we are not using it anymore, so we deleted it. Anyway, as we have changed from office we haven't got our own Internet connection yet, so my PC cannot be accessed from outside the network, making me impossible to help you with this. All I can do is send you the html code of the demo. I have been thinking about possible solutions with our current environment (since the only reason of using the proxy was the CORS policy with the context broker): 1. Edit the javascript code I have sent you (app.js) change there the proxy's address with the one of the context broker (the one that you have configured in your firos instance) and launch chrome without the security flag so the CORS policy will be avoided. 2. Create a little server application that allows CORS and redirects all the requests to another url (the cb one). 3. Don't use the demo page, and use native code (java python, c++...) to make requests to the context broker. Also I have read the documentation you sent about firos and RCM integration, and we are agree with what it is said on it, but I want to add some changes: 1. We should add namespaces to the topics, in firos we already had a topic for robot connection and disconnection and the namespace was firos: /firos/connect, /firos/disconnect So we think is interesting that topics to which firos publishes to should be in the "firos" namespace and the ones of rcm in "rcm" namespace for example. This is a way to have the topics well organized. 2. The CB_Event object is defined as string instance_name, int16 entity_status. We think both must be instances or entities (same name), but not one instance and the other one entity. As in this case we are talking about the context broker, we think is better to call both entity. What do you think about these changes? Should I add them to the document? We have been developing in firos what is said in the document. The communication defined in the document is developed and working, and we have also created a service that emulates what RCM sends to firos to try the full proccess and it seems to work. And this process seems to have sense. Regards, I?igo On 16/04/15 12:16, Colombatto Davide wrote: Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: etxetar.js Type: application/javascript Size: 2161 bytes Desc: etxetar.js URL: From igonzalez at ikergune.com Mon Apr 27 10:05:49 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Mon, 27 Apr 2015 10:05:49 +0200 Subject: [Fiware-robotics] CB-Proxy References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB0BCA6@telmbc006ba020.telecomitalia.local> Message-ID: I send you the file compressed to avoid your mail server reject the file. The password is: etxetar Regards, I?igo On 27/04/15 10:01, I?igo Gonzalez wrote: Hi Davide, here you have a new etxetar.js file. I have done several trials and I hope this one works for you. Regards, I?igo On 22/04/15 14:41, Colombatto Davide wrote: Hi Inigo, I have some troubles with the web-app code you sent me (that with the ip address of the CB and not of the old CB-Proxy). Below there are the steps I did: 1) Start chrome with the security flag disabled; the CB response is: 415 Unsupported Media Type
not supported content type: application/x-www-form-urlencoded
 2) In the etxetar.js - Add to the ajax request contentType:"application/json; charset=utf-8"; the response from CB is: 406 Not Acceptable
acceptable MIME types: 'application/xml, application/json'. Accept header in request: 'undefined'
 3) In the etxetar.js - Remove accepts:"application/json; charset=utf-8" (or changing it to accepts: {text: "application/json; charset=utf-8"}); the response of CB is: 400 Bad Request
JSON Parse Error: (1): expected object
 It seems it is related to encoding (charset). The Request sent by ajax is serialized as: 1. contextElements%5B0%5D%5Bid%5D=turtle1&contextElements%5B0%5D%5Btype%5D=ROBOT&contextElements%5B0%5D%5BisPattern%5D=false&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bname%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Btype%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bvalue%5D%5B%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bname%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Btype%5D=NotYet&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bvalue%5D=%7B'linear'%3A%7B'x'%3A0.5%2C'y'%3A0%2C'z'%3A0%7D%2C'angular'%3A%7B'x'%3A0%2C'y'%3A0%2C'z'%3A0%7D%2C'firosstamp'%3A1429705669659%7D&updateAction=APPEND Do you know how to resolve this problem in order to use that web-app (avoiding to implement the other two solutions you proposed) to do my test? Maybe the CB-Proxy you used in the past modify the requests before sending it to the CB.. I remember you that we (Telecom) don't receive attached files of scripts if they aren't in a zip file protected by password. Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: gioved? 16 aprile 2015 16:59 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] CB-Proxy Hi Davide, I have to say that the proxy isn't available. As we said some time ago that proxy was a temporary solution to try firos with a control panel we had, and we are not using it anymore, so we deleted it. Anyway, as we have changed from office we haven't got our own Internet connection yet, so my PC cannot be accessed from outside the network, making me impossible to help you with this. All I can do is send you the html code of the demo. I have been thinking about possible solutions with our current environment (since the only reason of using the proxy was the CORS policy with the context broker): 1. Edit the javascript code I have sent you (app.js) change there the proxy's address with the one of the context broker (the one that you have configured in your firos instance) and launch chrome without the security flag so the CORS policy will be avoided. 2. Create a little server application that allows CORS and redirects all the requests to another url (the cb one). 3. Don't use the demo page, and use native code (java python, c++...) to make requests to the context broker. Also I have read the documentation you sent about firos and RCM integration, and we are agree with what it is said on it, but I want to add some changes: 1. We should add namespaces to the topics, in firos we already had a topic for robot connection and disconnection and the namespace was firos: /firos/connect, /firos/disconnect So we think is interesting that topics to which firos publishes to should be in the "firos" namespace and the ones of rcm in "rcm" namespace for example. This is a way to have the topics well organized. 2. The CB_Event object is defined as string instance_name, int16 entity_status. We think both must be instances or entities (same name), but not one instance and the other one entity. As in this case we are talking about the context broker, we think is better to call both entity. What do you think about these changes? Should I add them to the document? We have been developing in firos what is said in the document. The communication defined in the document is developed and working, and we have also created a service that emulates what RCM sends to firos to try the full proccess and it seems to work. And this process seems to have sense. Regards, I?igo On 16/04/15 12:16, Colombatto Davide wrote: Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: etxetar.js.zip Type: application/zip Size: 1137 bytes Desc: etxetar.js.zip URL: From gianmario.bollano at telecomitalia.it Mon Apr 27 10:17:03 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Mon, 27 Apr 2015 08:17:03 +0000 Subject: [Fiware-robotics] R: CB-Proxy In-Reply-To: References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB0BCA6@telmbc006ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C4A4B67@telmba003ba020.telecomitalia.local> Hi I?igo, I can confirm you I've received correctly the attachment: the password tricks works... Gianmario 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? 27 aprile 2015 10:06 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] CB-Proxy I send you the file compressed to avoid your mail server reject the file. The password is: etxetar Regards, I?igo On 27/04/15 10:01, I?igo Gonzalez wrote: Hi Davide, here you have a new etxetar.js file. I have done several trials and I hope this one works for you. Regards, I?igo On 22/04/15 14:41, Colombatto Davide wrote: Hi Inigo, I have some troubles with the web-app code you sent me (that with the ip address of the CB and not of the old CB-Proxy). Below there are the steps I did: 1) Start chrome with the security flag disabled; the CB response is: 415 Unsupported Media Type
not supported content type: application/x-www-form-urlencoded
 2) In the etxetar.js - Add to the ajax request contentType:"application/json; charset=utf-8"; the response from CB is: 406 Not Acceptable
acceptable MIME types: 'application/xml, application/json'. Accept header in request: 'undefined'
 3) In the etxetar.js - Remove accepts:"application/json; charset=utf-8" (or changing it to accepts: {text: "application/json; charset=utf-8"}); the response of CB is: 400 Bad Request
JSON Parse Error: (1): expected object
 It seems it is related to encoding (charset). The Request sent by ajax is serialized as: 1. contextElements%5B0%5D%5Bid%5D=turtle1&contextElements%5B0%5D%5Btype%5D=ROBOT&contextElements%5B0%5D%5BisPattern%5D=false&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bname%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Btype%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bvalue%5D%5B%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bname%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Btype%5D=NotYet&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bvalue%5D=%7B'linear'%3A%7B'x'%3A0.5%2C'y'%3A0%2C'z'%3A0%7D%2C'angular'%3A%7B'x'%3A0%2C'y'%3A0%2C'z'%3A0%7D%2C'firosstamp'%3A1429705669659%7D&updateAction=APPEND Do you know how to resolve this problem in order to use that web-app (avoiding to implement the other two solutions you proposed) to do my test? Maybe the CB-Proxy you used in the past modify the requests before sending it to the CB.. I remember you that we (Telecom) don't receive attached files of scripts if they aren't in a zip file protected by password. Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: gioved? 16 aprile 2015 16:59 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] CB-Proxy Hi Davide, I have to say that the proxy isn't available. As we said some time ago that proxy was a temporary solution to try firos with a control panel we had, and we are not using it anymore, so we deleted it. Anyway, as we have changed from office we haven't got our own Internet connection yet, so my PC cannot be accessed from outside the network, making me impossible to help you with this. All I can do is send you the html code of the demo. I have been thinking about possible solutions with our current environment (since the only reason of using the proxy was the CORS policy with the context broker): 1. Edit the javascript code I have sent you (app.js) change there the proxy's address with the one of the context broker (the one that you have configured in your firos instance) and launch chrome without the security flag so the CORS policy will be avoided. 2. Create a little server application that allows CORS and redirects all the requests to another url (the cb one). 3. Don't use the demo page, and use native code (java python, c++...) to make requests to the context broker. Also I have read the documentation you sent about firos and RCM integration, and we are agree with what it is said on it, but I want to add some changes: 1. We should add namespaces to the topics, in firos we already had a topic for robot connection and disconnection and the namespace was firos: /firos/connect, /firos/disconnect So we think is interesting that topics to which firos publishes to should be in the "firos" namespace and the ones of rcm in "rcm" namespace for example. This is a way to have the topics well organized. 2. The CB_Event object is defined as string instance_name, int16 entity_status. We think both must be instances or entities (same name), but not one instance and the other one entity. As in this case we are talking about the context broker, we think is better to call both entity. What do you think about these changes? Should I add them to the document? We have been developing in firos what is said in the document. The communication defined in the document is developed and working, and we have also created a service that emulates what RCM sends to firos to try the full proccess and it seems to work. And this process seems to have sense. Regards, I?igo On 16/04/15 12:16, Colombatto Davide wrote: Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? 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 Mon Apr 27 16:49:53 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Mon, 27 Apr 2015 14:49:53 +0000 Subject: [Fiware-robotics] CB-Proxy In-Reply-To: References: <9d0a95ab29ac4c1c9b5beeb02f3c2064@EXCHMBX1.consoft.it> <069906BED271EB4A883BD9578DCDD3540CB0BCA6@telmbc006ba020.telecomitalia.local> , Message-ID: <069906BED271EB4A883BD9578DCDD3540CB0E869@telmbc006ba020.telecomitalia.local> Hi Inigo, the new JavaScript seems to work correctly now; I 've done some tests and I don't see the delay of the first demo starting FIROS on my PC, so I think it is resolved. Did you have seen the modification in the document https://docs.google.com/document/d/1eWO5MYYkjJEo1xLLm2YsX_bhCnET5eX4dm4_cL9MFg0/edit ? In particular what concern the example json that you send us some months ago. Thank you, Davide ________________________________ Da: I?igo Gonzalez [igonzalez at ikergune.com] Inviato: luned? 27 aprile 2015 10.05 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: CB-Proxy I send you the file compressed to avoid your mail server reject the file. The password is: etxetar Regards, I?igo On 27/04/15 10:01, I?igo Gonzalez wrote: Hi Davide, here you have a new etxetar.js file. I have done several trials and I hope this one works for you. Regards, I?igo On 22/04/15 14:41, Colombatto Davide wrote: Hi Inigo, I have some troubles with the web-app code you sent me (that with the ip address of the CB and not of the old CB-Proxy). Below there are the steps I did: 1) Start chrome with the security flag disabled; the CB response is: 415 Unsupported Media Type
not supported content type: application/x-www-form-urlencoded
 2) In the etxetar.js - Add to the ajax request contentType:"application/json; charset=utf-8"; the response from CB is: 406 Not Acceptable
acceptable MIME types: 'application/xml, application/json'. Accept header in request: 'undefined'
 3) In the etxetar.js - Remove accepts:"application/json; charset=utf-8" (or changing it to accepts: {text: "application/json; charset=utf-8"}); the response of CB is: 400 Bad Request
JSON Parse Error: (1): expected object
 It seems it is related to encoding (charset). The Request sent by ajax is serialized as: 1. contextElements%5B0%5D%5Bid%5D=turtle1&contextElements%5B0%5D%5Btype%5D=ROBOT&contextElements%5B0%5D%5BisPattern%5D=false&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bname%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Btype%5D=COMMAND&contextElements%5B0%5D%5Battributes%5D%5B0%5D%5Bvalue%5D%5B%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bname%5D=cmd_vel&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Btype%5D=NotYet&contextElements%5B0%5D%5Battributes%5D%5B1%5D%5Bvalue%5D=%7B'linear'%3A%7B'x'%3A0.5%2C'y'%3A0%2C'z'%3A0%7D%2C'angular'%3A%7B'x'%3A0%2C'y'%3A0%2C'z'%3A0%7D%2C'firosstamp'%3A1429705669659%7D&updateAction=APPEND Do you know how to resolve this problem in order to use that web-app (avoiding to implement the other two solutions you proposed) to do my test? Maybe the CB-Proxy you used in the past modify the requests before sending it to the CB.. I remember you that we (Telecom) don't receive attached files of scripts if they aren't in a zip file protected by password. Thank you, Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di I?igo Gonzalez Inviato: gioved? 16 aprile 2015 16:59 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] CB-Proxy Hi Davide, I have to say that the proxy isn't available. As we said some time ago that proxy was a temporary solution to try firos with a control panel we had, and we are not using it anymore, so we deleted it. Anyway, as we have changed from office we haven't got our own Internet connection yet, so my PC cannot be accessed from outside the network, making me impossible to help you with this. All I can do is send you the html code of the demo. I have been thinking about possible solutions with our current environment (since the only reason of using the proxy was the CORS policy with the context broker): 1. Edit the javascript code I have sent you (app.js) change there the proxy's address with the one of the context broker (the one that you have configured in your firos instance) and launch chrome without the security flag so the CORS policy will be avoided. 2. Create a little server application that allows CORS and redirects all the requests to another url (the cb one). 3. Don't use the demo page, and use native code (java python, c++...) to make requests to the context broker. Also I have read the documentation you sent about firos and RCM integration, and we are agree with what it is said on it, but I want to add some changes: 1. We should add namespaces to the topics, in firos we already had a topic for robot connection and disconnection and the namespace was firos: /firos/connect, /firos/disconnect So we think is interesting that topics to which firos publishes to should be in the "firos" namespace and the ones of rcm in "rcm" namespace for example. This is a way to have the topics well organized. 2. The CB_Event object is defined as string instance_name, int16 entity_status. We think both must be instances or entities (same name), but not one instance and the other one entity. As in this case we are talking about the context broker, we think is better to call both entity. What do you think about these changes? Should I add them to the document? We have been developing in firos what is said in the document. The communication defined in the document is developed and working, and we have also created a service that emulates what RCM sends to firos to try the full proccess and it seems to work. And this process seems to have sense. Regards, I?igo On 16/04/15 12:16, Colombatto Davide wrote: Hi Inigo, I need to use the web-app of first Robotics LiveDemo (http://130.206.127.115/demo1/) where the FORWARD button requires to switch on the CB-Proxy on your PC. Can you tell me when I can use it? 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 Apr 28 10:00:43 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 28 Apr 2015 08:00:43 +0000 Subject: [Fiware-robotics] Robotics Call Message-ID: <7E649CBD84A947498203DAF8F098B1F62C4A7C9E@telmba003ba020.telecomitalia.local> Hi all, we can have the usual Robotics call with hangout at 10.00 I've added my account bgianm at gmail.com on my smartphone for the call. 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: 2514 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 Apr 28 10:03:02 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 28 Apr 2015 08:03:02 +0000 Subject: [Fiware-robotics] Robotics Call Message-ID: <7E649CBD84A947498203DAF8F098B1F62C4A7CD5@telmba003ba020.telecomitalia.local> Hi all, we can have the usual Robotics call with hangout at 10.00 ? I've added my account bgianm at gmail.com on my smartphone for the call. 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 Apr 28 17:33:33 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 28 Apr 2015 17:33:33 +0200 Subject: [Fiware-robotics] IdM and OpenVPN Message-ID: Hi all, I've made some research about external authentication in OpenVPN. It looks like it can be achieved by using the "auth-user-pass-verify" stanza and a script which returns 0 if the authentication is OK or 1 in other case. Here you have some references, including a LDAP-auth example: http://edoceo.com/howto/openvpn-auth-user-pass-verify http://openvpn.net/index.php/open-source/documentation/howto.html#auth https://openvpn.net/index.php/open-source/documentation/manuals/65-openvpn-20x-manpage.html ("--auth-user-pass-verify" setion). Do you think that could be implemented in the VPNs that RCM is using? BR, Pepe. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From roberto1.antonini at telecomitalia.it Wed Apr 29 09:09:49 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Wed, 29 Apr 2015 07:09:49 +0000 Subject: [Fiware-robotics] R: IdM and OpenVPN In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA8643D36C40@TELMBB001BA020.telecomitalia.local> Hi Pepe, thanks so much for sharing this information, if I understand well the configuration directives , at (VPN) server side (MASTER) we need to execute a script connecting to LDAP server to authenticate the client (Robot). Hence, each robot will be provided with user and password to be authenticated by LDAP server (IdM GE) connected at server side. Have you already had some experience with iDM GE Keyrock? Thanks, Roberto -----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? 28 aprile 2015 17:34 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] IdM and OpenVPN Hi all, I've made some research about external authentication in OpenVPN. It looks like it can be achieved by using the "auth-user-pass-verify" stanza and a script which returns 0 if the authentication is OK or 1 in other case. Here you have some references, including a LDAP-auth example: http://edoceo.com/howto/openvpn-auth-user-pass-verify http://openvpn.net/index.php/open-source/documentation/howto.html#auth https://openvpn.net/index.php/open-source/documentation/manuals/65-openvpn-20x-manpage.html ("--auth-user-pass-verify" setion). Do you think that could be implemented in the VPNs that RCM is using? 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 jjaime at ikergune.com Wed Apr 29 12:38:32 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Wed, 29 Apr 2015 12:38:32 +0200 Subject: [Fiware-robotics] R: IdM and OpenVPN References: <246C286B275B1B46A255552CD236DA8643D36C40@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, I don't have any experience with Keyrock but it uses Oauth v2, which a usual authentication protocol. Just in case you have some problem with Oauth or Keyrock, it looks that there are other authentication GE. BR, Pepe On 29/04/15 09:09, Antonini Roberto wrote: > Hi Pepe, > thanks so much for sharing this information, > if I understand well the configuration directives , at (VPN) server side (MASTER) we need to execute a script connecting to LDAP server to authenticate the client (Robot). > Hence, each robot will be provided with user and password to be authenticated by LDAP server (IdM GE) connected at server side. > > Have you already had some experience with iDM GE Keyrock? > > Thanks, > Roberto > > > -----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? 28 aprile 2015 17:34 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] IdM and OpenVPN > > Hi all, > > I've made some research about external authentication in OpenVPN. It looks like it can be achieved by using the "auth-user-pass-verify" > stanza and a script which returns 0 if the authentication is OK or 1 in other case. > > Here you have some references, including a LDAP-auth example: > http://edoceo.com/howto/openvpn-auth-user-pass-verify > http://openvpn.net/index.php/open-source/documentation/howto.html#auth > https://openvpn.net/index.php/open-source/documentation/manuals/65-openvpn-20x-manpage.html > ("--auth-user-pass-verify" setion). > > Do you think that could be implemented in the VPNs that RCM is using? > > 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. > > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From jjaime at ikergune.com Wed Apr 29 16:03:29 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Wed, 29 Apr 2015 16:03:29 +0200 Subject: [Fiware-robotics] Interesting topics Message-ID: Hi all, Just as commented in the last call, here you have some of the topics which contextBroker can manage and are interesting enough to be sent "outside ROS": Topic Message type cmd_vel geometry_msgs.msg.Twist cmd_vel_mux/input/teleop geometry_msgs.msg.Twist move_base/cancel actionlib_msgs.msg.GoalID move_base/goal move_base_msgs.msg.MoveBaseActionGoal move_base/result move_base_msgs.msg.MoveBaseActionResult BR, Pepe -- 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 Wed Apr 29 18:33:03 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Wed, 29 Apr 2015 18:33:03 +0200 Subject: [Fiware-robotics] R: Live demos work plan References: <246C286B275B1B46A255552CD236DA8643D3530B@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, As you can check in https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit#, I'm expanding the description of each task. Please let me know if you think that the detail level is the appropriate for the stage of the document, or any other comment you have. As far as I can remember, Roberto told in the last call that you (TI) could take in charge of expanding some of the tasks. In order to not to collide while editing the document, which one could you expand? BR, Pepe. On 24/04/15 16:16, Jose Jaime Ariza wrote: > Hi all, > > Thank you very much for your comments, Roberto. I've answered them. I've > not made any modification, I think it's better to make them after > Tuesday's call. > > BR, > Pepe. > > On 24/04/15 11:18, Antonini Roberto wrote: >> Hi all, >> thanks for your work, I added some comments in the doc, the most of them ask you to made task description clearer perhaps with some examples in order to avoid future misunderstanding. >> >> BR >> Roberto >> >> -----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? 21 aprile 2015 16:42 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] Live demos work plan >> >> Hi all, >> >> As commented in today's call, here you can find the work plan draft: >> https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit# >> >> Please, make any changes you consider appropriate. >> >> 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. >> >> > -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From roberto1.antonini at telecomitalia.it Wed Apr 29 18:39:50 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Wed, 29 Apr 2015 16:39:50 +0000 Subject: [Fiware-robotics] R: R: Live demos work plan In-Reply-To: References: <246C286B275B1B46A255552CD236DA8643D3530B@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8643D3708F@TELMBB001BA020.telecomitalia.local> For what concerns only T1, the ones related to RCM deployment and RCM-FIROS connectivity, hence T 1.3 and T 1.4. Is it ok? BR Roberto -----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: mercoled? 29 aprile 2015 18:33 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Live demos work plan Hi all, As you can check in https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit#, I'm expanding the description of each task. Please let me know if you think that the detail level is the appropriate for the stage of the document, or any other comment you have. As far as I can remember, Roberto told in the last call that you (TI) could take in charge of expanding some of the tasks. In order to not to collide while editing the document, which one could you expand? BR, Pepe. On 24/04/15 16:16, Jose Jaime Ariza wrote: > Hi all, > > Thank you very much for your comments, Roberto. I've answered them. > I've not made any modification, I think it's better to make them after > Tuesday's call. > > BR, > Pepe. > > On 24/04/15 11:18, Antonini Roberto wrote: >> Hi all, >> thanks for your work, I added some comments in the doc, the most of them ask you to made task description clearer perhaps with some examples in order to avoid future misunderstanding. >> >> BR >> Roberto >> >> -----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? 21 aprile 2015 16:42 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] Live demos work plan >> >> Hi all, >> >> As commented in today's call, here you can find the work plan draft: >> https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d >> 2cAarKIlLY/edit# >> >> Please, make any changes you consider appropriate. >> >> 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. >> >> > -- 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 Apr 30 09:18:21 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 30 Apr 2015 07:18:21 +0000 Subject: [Fiware-robotics] R: Interesting topics In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA8643D3795A@TELMBB001BA020.telecomitalia.local> Hi Pepe, starting from the list below, I have some doubt about how CB is working, I will try to better explain what I mean: to my know, CB allows external user to create entity and its attributes, for sake of simplicity I report the JSON object you have to post to do it: "contextElements": [ { "type": "Room", "isPattern": "false", "id": "Room1", "attributes": [ { "name": "temperature", "type": "float", "value": "23" }, { "name": "pressure", "type": "integer", "value": "720" } ] } ], "updateAction": "APPEND" I consider FIROS an external user from CB perspective, correct me if I'm wrong, so FIROS it's able to create, publish to CB (e.g. example above) and being notified when something change (i.e. the pressure of room named Room1). In order to project Robot Clone to CB, FIROS creates an entity, named as the Robot Clone, with attributes reporting the ROS messages in the format above, i.e.: "contextElements": [ { "type": "Robot", "isPattern": "false", "id": "Turtlebot", "attributes": [ { "name": "/cmd_vel", "type": "geometry_msgs/Twist", "value": "{linear : { x : 0, y : 0, z : 0 }, angular : { x : 0, y : 0, z : 0, w : 0} }" }, { "name": "/odom", "type": "nav_msgs/odometry", "value": "{ ... }" } ] } ], "updateAction": "APPEND" So CB accepts, let's say, JSON object to be configured, if I want to move the robot I have to update object above by simply changing some values in /cmd_vel attribute, i.e. : "contextElements": [ { "type": "Robot", "isPattern": "false", "id": "Turtlebot", "attributes": [ { "name": "/cmd_vel", "type": "geometry_msgs/Twist", "value": "{linear : { x : 0.3, y : 0, z : 0 }, angular : { x : 0, y : 0, z : 0, w : 0} }" }, ] } ], "updateAction": "APPEND" In this way the robot will be moved along x axis with a velocity of 30 cm/s. The /odom attribute instead notify me, as FIWARE user, with robot position estimate with a rate of 10 or 20 Hz, in this case FIROS subscribes /odom topic and publishes its value to CB in order to update the value for FIWARE user benefit. Starting from the examples above, could you please clarify to us which are the CB limitations? I suppose they are more related to something like /odom dynamic and particularly the value update frequency, in that case 10 or 20 Hz, is it correct? Thanks in advance, Roberto Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: mercoled? 29 aprile 2015 16:03 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Interesting topics Hi all, Just as commented in the last call, here you have some of the topics which contextBroker can manage and are interesting enough to be sent "outside ROS": Topic Message type cmd_vel geometry_msgs.msg.Twist cmd_vel_mux/input/teleop geometry_msgs.msg.Twist move_base/cancel actionlib_msgs.msg.GoalID move_base/goal move_base_msgs.msg.MoveBaseActionGoal move_base/result move_base_msgs.msg.MoveBaseActionResult BR, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group 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 Thu Apr 30 12:29:33 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 30 Apr 2015 12:29:33 +0200 Subject: [Fiware-robotics] R: R: Live demos work plan References: <246C286B275B1B46A255552CD236DA8643D3530B@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8643D3708F@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, Perfect, Roberto, thank you very much. About stage 2 and 3, do you have any estimation about which one could you expand? Since Kurento and Wirecloud are also involved in the live demo, I'm going to ask them about contributing to the document. BR, Pepe. On 29/04/15 18:39, Antonini Roberto wrote: > For what concerns only T1, the ones related to RCM deployment and RCM-FIROS connectivity, hence T 1.3 and T 1.4. > Is it ok? > BR > Roberto > > -----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: mercoled? 29 aprile 2015 18:33 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: Live demos work plan > > Hi all, > > As you can check in > https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit#, > I'm expanding the description of each task. Please let me know if you think that the detail level is the appropriate for the stage of the document, or any other comment you have. > > As far as I can remember, Roberto told in the last call that you (TI) could take in charge of expanding some of the tasks. In order to not to collide while editing the document, which one could you expand? > > BR, > Pepe. > > On 24/04/15 16:16, Jose Jaime Ariza wrote: >> Hi all, >> >> Thank you very much for your comments, Roberto. I've answered them. >> I've not made any modification, I think it's better to make them after >> Tuesday's call. >> >> BR, >> Pepe. >> >> On 24/04/15 11:18, Antonini Roberto wrote: >>> Hi all, >>> thanks for your work, I added some comments in the doc, the most of them ask you to made task description clearer perhaps with some examples in order to avoid future misunderstanding. >>> >>> BR >>> Roberto >>> >>> -----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? 21 aprile 2015 16:42 >>> A: fiware-robotics at lists.fi-ware.org >>> Oggetto: [Fiware-robotics] Live demos work plan >>> >>> Hi all, >>> >>> As commented in today's call, here you can find the work plan draft: >>> https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d >>> 2cAarKIlLY/edit# >>> >>> Please, make any changes you consider appropriate. >>> >>> 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. >>> >>> > > -- > 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 jjaime at ikergune.com Thu Apr 30 12:43:30 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 30 Apr 2015 12:43:30 +0200 Subject: [Fiware-robotics] R: Interesting topics References: <246C286B275B1B46A255552CD236DA8643D3795A@TELMBB001BA020.telecomitalia.local> Message-ID: Hi all, We've found some limitations in contextBroker: 1) As you can find in the wiki, the request maximum size is 1MB, which is not enough for some topics. 2) ContextBroker does not recycle TCP sockets, neither it accepts keep-alive http connections. So, the TCP sockets usage is really high, which results in weird network behavior or outages. This one can be avoided by limitting the update rate or the number of elements that must be updated. 3) We've some issues while sending binary-alike data to contextBroker (images and so). There are other issues in coding and minor differences between the several versions of contextBroker, but FIROS usually can handle them. BR, Pepe On 30/04/15 09:18, Antonini Roberto wrote: Hi Pepe, starting from the list below, I have some doubt about how CB is working, I will try to better explain what I mean: to my know, CB allows external user to create entity and its attributes, for sake of simplicity I report the JSON object you have to post to do it: "contextElements": [ { "type": "Room", "isPattern": "false", "id": "Room1", "attributes": [ { "name": "temperature", "type": "float", "value": "23" }, { "name": "pressure", "type": "integer", "value": "720" } ] } ], "updateAction": "APPEND" I consider FIROS an external user from CB perspective, correct me if I?m wrong, so FIROS it?s able to create, publish to CB (e.g. example above) and being notified when something change (i.e. the pressure of room named Room1). In order to project Robot Clone to CB, FIROS creates an entity, named as the Robot Clone, with attributes reporting the ROS messages in the format above, i.e.: "contextElements": [ { "type": "Robot", "isPattern": "false", "id": "Turtlebot", "attributes": [ { "name": "/cmd_vel", "type": "geometry_msgs/Twist", "value": "{linear : { x : 0, y : 0, z : 0 }, angular : { x : 0, y : 0, z : 0, w : 0} }" }, { "name": "/odom", "type": "nav_msgs/odometry", "value": "{ ... }" } ] } ], "updateAction": "APPEND" So CB accepts, let?s say, JSON object to be configured, if I want to move the robot I have to update object above by simply changing some values in /cmd_vel attribute, i.e. : "contextElements": [ { "type": "Robot", "isPattern": "false", "id": "Turtlebot", "attributes": [ { "name": "/cmd_vel", "type": "geometry_msgs/Twist", "value": "{linear : { x : 0.3, y : 0, z : 0 }, angular : { x : 0, y : 0, z : 0, w : 0} }" }, ] } ], "updateAction": "APPEND" In this way the robot will be moved along x axis with a velocity of 30 cm/s. The /odom attribute instead notify me, as FIWARE user, with robot position estimate with a rate of 10 or 20 Hz, in this case FIROS subscribes /odom topic and publishes its value to CB in order to update the value for FIWARE user benefit. Starting from the examples above, could you please clarify to us which are the CB limitations? I suppose they are more related to something like /odom dynamic and particularly the value update frequency, in that case 10 or 20 Hz, is it correct? Thanks in advance, Roberto Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: mercoled? 29 aprile 2015 16:03 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Interesting topics Hi all, Just as commented in the last call, here you have some of the topics which contextBroker can manage and are interesting enough to be sent "outside ROS": Topic Message type cmd_vel geometry_msgs.msg.Twist cmd_vel_mux/input/teleop geometry_msgs.msg.Twist move_base/cancel actionlib_msgs.msg.GoalID move_base/goal move_base_msgs.msg.MoveBaseActionGoal move_base/result move_base_msgs.msg.MoveBaseActionResult BR, Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group 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 Thu Apr 30 15:17:35 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 30 Apr 2015 15:17:35 +0200 Subject: [Fiware-robotics] Robotics Live Demo Work plan Message-ID: Hi Kurento and Wirecloud guys, We are developing a workplan for the robotics live demo: https://docs.google.com/document/d/1qYa9UQcx1kGgQF07MUvlfM0P9NK5j2u8d2cAarKIlLY/edit#heading=h.f7mi0tl88him Please, have a look and provide any comment you think necessary. We are expanding the descriptions of the tasks and adding its outcomes. Could you take in charge of those related with Kurento and Wirecloud. Thank you very much, Pepe. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From jjaime at ikergune.com Thu Apr 30 16:24:59 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 30 Apr 2015 16:24:59 +0200 Subject: [Fiware-robotics] Demo slides Message-ID: Hi all, I've created three slides exposing the status and progress of FIROS (https://docs.google.com/presentation/d/1SH91S1X0Izm_9BxZ3ZLj09t9Dj6HzydB_a8Z5kxHF5M/edit?usp=sharing), but I'm not totally sure about what to write regarding RCM. Could you (TI) complete them or give me some hint? Pier, let me know if you expected something different. BR, Pepe. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From gianmario.bollano at telecomitalia.it Thu Apr 30 16:55:56 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 30 Apr 2015 14:55:56 +0000 Subject: [Fiware-robotics] R: Demo slides In-Reply-To: References: Message-ID: <7E649CBD84A947498203DAF8F098B1F62C4B1DC3@telmbb003ba020.telecomitalia.local> Hi, Pepe/Jose, the structure of the slides is fine; only the Workplan looks to me - let me say - too much Coca Cola optimistic. I think all of us can agree that many aspects are still under investigation concerning CB and the FIROS-RCM communication (just to consider the last exchanged e-mails and the robotics call). This is not a bad point, it's just a proof of the effort to converge to a good shared specification. Then in the workplan slide I'd suggest to use more specific/focused/limited milestones, otherwise anything would appear as real as a Coca Cola advertising, and Christmas is not even close! Roberto, Davide and Fabio have knowledge of the practical work done this sprint then they will let you know if they prefer adding their contribution to the slides you've prepared, or preparing their slides to merge. This is just a technical issue and will not affect the result, because Pier will merge ET and TI slides, as well as all other contributions. Best, Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 30 aprile 2015 16:25 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Demo slides Hi all, I've created three slides exposing the status and progress of FIROS (https://docs.google.com/presentation/d/1SH91S1X0Izm_9BxZ3ZLj09t9Dj6HzydB_a8Z5kxHF5M/edit?usp=sharing), but I'm not totally sure about what to write regarding RCM. Could you (TI) complete them or give me some hint? Pier, let me know if you expected something different. 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 gianmario.bollano at telecomitalia.it Thu Apr 30 18:36:22 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 30 Apr 2015 16:36:22 +0000 Subject: [Fiware-robotics] R: R: Demo slides In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F62C4B1DC3@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F62C4B1ECF@telmbb003ba020.telecomitalia.local> Hi Pepe (Jose?), the milestones shouldn't be high-level in this presentation. In fact, they only are the milestones of this sprint (Pier has defined them Workplan detail). Your Workplan table say "YES, Achieved", but this is more precisely, "Yes, under specific conditions". Robotics specification is still in progress and we are still defining which, why and how many are these "specific conditions". "Specific conditions" refers for instance: - list of Topics / List of messages Types, their number, their format and notation - list of conditions for commands/data messages - such as: Update frequency , message size limit, binary content and all of these are not yet clearly identified and defined. IMHO, some generic Milestones are not yet Achieved (but they will be) because a more detailed Milestone is still in progress: e.g. Investigating conditions to fit to requirements for both Robotics ROS environment and the Context Broker. As a conclusion, obviously anyone of us is free to define his milestone as he think it's better to describe his work. Only keep in mind we will have one presentation for Robotics - not two - we should be aware not to say something and then something that sound very different in the same or next slide. Gianmario -----Messaggio originale----- Da: Jose Jaime Ariza [mailto:jjaime at ikergune.com] Inviato: gioved? 30 aprile 2015 17:15 A: Bollano Gianmario Oggetto: Re: [Fiware-robotics] R: Demo slides Hi all, As I have understood, we must include the whole Robotics GE workplan status in the third slide, so I've included those high-level milestones. The work plan is not as you say, Coca Cola optimistic. It's just the current status of FIROS. BR, Pepe. On 30/04/15 16:55, Bollano Gianmario wrote: > Hi, > Pepe/Jose, the structure of the slides is fine; only the Workplan looks to me - let me say - too much Coca Cola optimistic. > > I think all of us can agree that many aspects are still under investigation concerning CB and the FIROS-RCM communication (just to consider the last exchanged e-mails and the robotics call). > This is not a bad point, it's just a proof of the effort to converge to a good shared specification. > > Then in the workplan slide I'd suggest to use more specific/focused/limited milestones, otherwise anything would appear as real as a Coca Cola advertising, and Christmas is not even close! > > Roberto, Davide and Fabio have knowledge of the practical work done this sprint then they will let you know if they prefer adding their contribution to the slides you've prepared, or preparing their slides to merge. > This is just a technical issue and will not affect the result, because Pier will merge ET and TI slides, as well as all other contributions. > > Best, > Gianmario > > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fi-ware.org > [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 30 aprile 2015 16:25 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Demo slides > > Hi all, > > I've created three slides exposing the status and progress of FIROS > (https://docs.google.com/presentation/d/1SH91S1X0Izm_9BxZ3ZLj09t9Dj6Hz > ydB_a8Z5kxHF5M/edit?usp=sharing), but I'm not totally sure about what > to write regarding RCM. Could you > (TI) complete them or give me some hint? > > Pier, let me know if you expected something different. > > 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 Thu Apr 30 19:24:03 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 30 Apr 2015 19:24:03 +0200 Subject: [Fiware-robotics] R: R: Demo slides References: <7E649CBD84A947498203DAF8F098B1F62C4B1DC3@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F62C4B1ECF@telmbb003ba020.telecomitalia.local> Message-ID: Hi all, Since the mail sent to the list said "c) overall architectural aspects + workplan details." I understood that the overall was applying to the workplan. My fault. I've rebuild the FIROS workplan in order to only include the tasks related to this release. I still don't think we should include the "under specific conditions" phrase: FIROS is working following the current FIROS-RCM specifications. Also, the limiting elements are the network and the contextBroker, not an element from Robotics GE. BR, Pepe. On 30/04/15 18:36, Bollano Gianmario wrote: > Hi Pepe (Jose?), > the milestones shouldn't be high-level in this presentation. > In fact, they only are the milestones of this sprint (Pier has defined them Workplan detail). > > Your Workplan table say "YES, Achieved", but this is more precisely, "Yes, under specific conditions". > Robotics specification is still in progress and we are still defining which, why and how many are these "specific conditions". > "Specific conditions" refers for instance: > - list of Topics / List of messages Types, their number, their format and notation > - list of conditions for commands/data messages - such as: Update frequency , message size limit, binary content > and all of these are not yet clearly identified and defined. > > IMHO, some generic Milestones are not yet Achieved (but they will be) because a more detailed Milestone is still in progress: > e.g. Investigating conditions to fit to requirements for both Robotics ROS environment and the Context Broker. > > As a conclusion, obviously anyone of us is free to define his milestone as he think it's better to describe his work. > Only keep in mind we will have one presentation for Robotics - not two - we should be aware not to say something and then something that sound very different in the same or next slide. > > Gianmario > > -----Messaggio originale----- > Da: Jose Jaime Ariza [mailto:jjaime at ikergune.com] > Inviato: gioved? 30 aprile 2015 17:15 > A: Bollano Gianmario > Oggetto: Re: [Fiware-robotics] R: Demo slides > > Hi all, > > As I have understood, we must include the whole Robotics GE workplan status in the third slide, so I've included those high-level milestones. > > The work plan is not as you say, Coca Cola optimistic. It's just the current status of FIROS. > > BR, > Pepe. > > On 30/04/15 16:55, Bollano Gianmario wrote: >> Hi, >> Pepe/Jose, the structure of the slides is fine; only the Workplan looks to me - let me say - too much Coca Cola optimistic. >> >> I think all of us can agree that many aspects are still under investigation concerning CB and the FIROS-RCM communication (just to consider the last exchanged e-mails and the robotics call). >> This is not a bad point, it's just a proof of the effort to converge to a good shared specification. >> >> Then in the workplan slide I'd suggest to use more specific/focused/limited milestones, otherwise anything would appear as real as a Coca Cola advertising, and Christmas is not even close! >> >> Roberto, Davide and Fabio have knowledge of the practical work done this sprint then they will let you know if they prefer adding their contribution to the slides you've prepared, or preparing their slides to merge. >> This is just a technical issue and will not affect the result, because Pier will merge ET and TI slides, as well as all other contributions. >> >> Best, >> Gianmario >> >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fi-ware.org >> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose >> Jaime Ariza >> Inviato: gioved? 30 aprile 2015 16:25 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] Demo slides >> >> Hi all, >> >> I've created three slides exposing the status and progress of FIROS >> (https://docs.google.com/presentation/d/1SH91S1X0Izm_9BxZ3ZLj09t9Dj6Hz >> ydB_a8Z5kxHF5M/edit?usp=sharing), but I'm not totally sure about what >> to write regarding RCM. Could you >> (TI) complete them or give me some hint? >> >> Pier, let me know if you expected something different. >> >> 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 > > _______________________________________________ > 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