Hi guys, with Luis we agreed on a plan to integrate their stuff into robotics platform, so just to summarize (in bold the milestones): · At client side: we should send to him the characteristics of the robots we want to use for the demo, here we have a turtlebot2 and a camera (Logitech c270) ready to be used, I would ask you if you have some robot to be used for the demo, if so tell Luis its characteristics · Test: given robot characteristics above, Luis will provide us with some configuration we need to do to test end-to-end video streaming, for instance by using WebRTC Technology with Chrome browser at robot side. We can assess latencies and basic functionalities, such as adaptive bandwidth, of video streaming directly at server side (Chrome browser) · Wrapper ROS Node: once tests above succeed, we start building a ROS node to wrap Chrome Browser Web RTC client to capture the camera video stream, in order to start the client with SL/SN REST API. · UI: understand how to involve Web UI GE, in order to build web application to remotely teleoperate the robot, this GE is connected to: o IoT CB: to manage robot entities, i.e. by updating /cmd_vel attribute according to keyboard button pressing or joysticks moving o KURENTO: to view video streaming, with Chrome embedded player The times to accomplish tasks above could be (just a proposal): · by the end of the week, for what concerns the client side milestone. · By the end of the month, for what concerns the test of e2e video streaming. · By the end of the next month (Release 4.2), we (as TI) can release Wrapper ROS node. In the meanwhile I would suggest that ET guys get in touch with Web UI GE guys, in order to understand how to involve them. Pier let us know if times proposed are compatible with deadline to release at least the first part for live demo. BR, Davide and Roberto · UI: Da: Garino Pierangelo Inviato: mercoledì 11 febbraio 2015 09:33 A: Antonini Roberto; Angel Hernandez (ahernandez at ikergune.com) Cc: Colombatto Davide; Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi All, I see interesting proposals circulating and I do like the idea of showing a practical example that exploits robot(s) and the robotics GE. The idea is perfectly complementing a demo centered around the manufacturing field, in my opinion. But let me point out a couple of things we should consider. The purpose of live demo is to propose a use case as an example of GE adoption to the developers interested in using the robotics GE. Ideally, the demo should be easy to reproduced by the interested developer. This means that we should clearly explain, step by step, how to program/implement the example. I believe therefore that we cannot be too much demanding about the robot to be used. However, I also believe that a nice example, although not completely reproducible by others, is appealing. I would therefore be in favour of the incremental/progressive approach to the live demo scenario: start with one robot, simple teleoperation, add sensors/cameras, include more GEs, add 'mission', include more robots, etc... In summary, I would use the use case explained by Angel as comprehensive example for the live demo, but clearly stating that there are steps which will be implemented for sure by M13, while others might be implemented depending on the time/resources available, and maybe completed later. Sort of a basic configuration + enriching features; on the other hand we'll probably create Features explicitly for the live demo... This incremental approach would avoid committing ourselves to a scenario perhaps difficult to achieve, and to keep example simple enough for 'end users' of the live demo who could replicate it easily, even without the specific robot we're willing to use (btw, do we have one with the characteristics depicted?). What's your opinion? BR Pier Da: Antonini Roberto Inviato: martedì 10 febbraio 2015 17:02 A: Angel Hernandez (ahernandez at ikergune.com); fiware-robotics at lists.fi-ware.org Cc: Colombatto Davide; Garino Pierangelo; Bollano Gianmario Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, you are right when you said that is missing the whole demo objective we want to pursue. In defining that, I would take into consideration the final users and that demo needs to be living. Being said that, here a list of point which summarizes our proposal: · Starting with something ready to be used, so that we thought we can start from a "simple" Teleoperation and progressively add other capabilities · Managing FIROS in order to connect CB and so enabling FIWARE apps to use robotics. Here we'd like ask you if you shared architecture proposal here attached (image with arch view and a brief description), where for each robot/clone is started a FIROS, in way a single FIROS could project its clone or robot to CB entity and update attributes according to ROS messages. If you agree we will put that schema and the description in the common WIKI page within Main Interaction section. · Exploiting other GEs, such as KURENTO, in order to integrate their capabilities, in case of KURENTO RCM could start sort of web RTC streaming video client (wrapped by ROS node) as needed Hence, from what said above, the objective could be "making robotics effective and ready to use" to final users who want to use robots in their services. We guess the first step could be simply teleoperating a robot, following step could be adding a thermal camera (rosify it) and provide thermal image to user or application to detect thermal patterns such as candle flames. Besides, I would add path planning capability (AMCL and move base node properly configured) to send robot to a position in the map or to schedule predefined path to take thermal picture at a specific point ... As you can see we prefer a progressive approach, in order to elicit feedback after each step and maybe be in time to change something. BR Roberto and Davide. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerdì 6 febbraio 2015 12:02 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello Davide, We wanted to talk about the live demo yesterday as well as the technical issues, but we didn't have enough time. The document you shared looks very good. It defines a good architecture and technical details for what we would need for a demo. What I feel we would be missing there is an overall description of what the whole demo idea is pursuing. For example something like what we just wrote on the document. In the end is just making a technical demo, appealing for the general public and future users of FIWARE, so the Teleoperation proposal you wrote is a very good start for the architecture definition of the Firefighting demo... or pretty much any demo we want to describe. Take a look at the document, and let us know what you think. Thanks! De: Colombatto Davide [mailto:davide.colombatto at telecomitalia.it] Enviado el: viernes, 6 de febrero de 2015 10:35 Para: Angel Hernandez; fiware-robotics at lists.fi-ware.org Asunto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel and All, Yes, for what concerns "Technical issues investigation" yesterday we understood that the problem could be related to the network (too much distance between the two machine which cause timeout depending the route chosen by the IP packet) or some firewalls, so we'll do other tests on our side. Other point: Yesterday morning I sent you our view of a "use case" (schema and description) of the Robotics GE, I think that in the next call we can talk about that in order to clarify some points. Tell us when you will be ready to discuss of that schema or if you agree with that I sent you yesterday. BR, Davide Da: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: venerdì 6 febbraio 2015 10:20 A: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, It's 10:20, so I guess we are not having the call we set yesterday. It's ok since this issue was clarified yesterday by Davide and Iñigo anyway. Have a good day. Ángel De: Iñigo Gonzalez Enviado el: jueves, 5 de febrero de 2015 17:20 Para: Colombatto Davide; Angel Hernandez CC: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Asunto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi, as Davide said we set the throttling to PT0S. On our environment we are not having those problems. In order to discard the network problem we suggest you: - Trying on a machine outside TI's network - Installing the context broker locally in your machine Regards, Iñigo On 05/02/15 17:06, Colombatto Davide wrote: Hi, We check and FIROS uses PT0S (not PTS10) so that isn't the problem. We also try to disable the firewall on our side but nothing is changed. The last thing (I think) is that there could be present a firewall on FILAB side (where is hosted the Orion we are trying) or in other parts of the network between Spain and our location. 1. Is it possible? 2. When you tried CB notifications on your side (without RCM), have you ever seen this kind of problem? However, I think we could start to work on next steps due to in next releases we both (ET and TI) will able to test the solution and maybe understand which is the problem. BR, D ________________________________ Da: Antonini Roberto Inviato: giovedì 5 febbraio 2015 16.25 A: Colombatto Davide; Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: R: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi guys, In the link https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions We found this interesting explanation about the ONCHANGE notification: The throttling element is used to specify a minimum inter-notification arrival time. So, setting throttling to 5 seconds as in the example above makes that a notification will not be sent if a previous notification was sent less than 5 seconds ago, no matter how many actual changes take place in that period. This is to not stress the notification receptor in case of having context producers that update attribute values too frequently. Actually, throttling is not an "exclusive" field for ONCHANGE subscriptions: from a theoretical point of view it can be used in ONTIMEINTERVAL subscriptions but, given that in that case you can precisely control the notification frequency it doesn't have any practical sense. It seems to me that you set PT10S on FIROS, that's 10 second, indeed if we try every 10 seconds the turtle is moved correctly. Let us know if we miss something and above all if this solve the problem, maybe you can decrease the number of seconds or unset the parameter if possible. Roberto Da: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Colombatto Davide Inviato: giovedì 5 febbraio 2015 15:21 A: Angel Hernandez Cc: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: Re: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hi Angel, can you check the webapp (http://130.206.127.115/demo1/) to enable me to do some test this afternoon? It seems that the FORWARD button passes through "http://soc-e.noip.me:10101/NGSI10/updateContext" that is not more available now. I think Roberto will not be available tomorrow morning but if it is a firewall problem I think it will automatically disappear for the next demo (we will use another machine and we also release you the RCM). Let me known for the web-app D ________________________________ Da: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org>] per conto di Angel Hernandez [ahernandez at ikergune.com<mailto:ahernandez at ikergune.com>] Inviato: giovedì 5 febbraio 2015 13.08 A: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: [Fiware-robotics] Finish technical issues investigation 10:00 on friday Hello guys, In order to finish the conversation we just had, what about meeting tomorrow at 10:00? De: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto Enviado el: jueves, 5 de febrero de 2015 11:24 Para: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Asunto: [Fiware-robotics] R: R: R: Live demo Brainstorming and network issues Ok, we've already set the stage. R Da: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: giovedì 5 febbraio 2015 11:10 A: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: Re: [Fiware-robotics] R: R: Live demo Brainstorming and network issues Hangouts is good for us. BR On 05/02/15 10:58, Antonini Roberto wrote: Ok, hear you later. Hangouts? R Da: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: giovedì 5 febbraio 2015 10:46 A: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: Re: [Fiware-robotics] R: Live demo Brainstorming and network issues Hi all, We'll be available at 12:30, we'll you be available at that time? We've been searching in contextBroker's log and found many connection time out related to TI's IP: E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[97] socketHttpConnect: connect(188.15.109.226, 10100): Connection timed out E:Monday 02 Feb 11:29:19 2015(715):contextBroker-/clientSocketHttp.cpp[258] sendHttpSocket: Unable to connect to HTTP server at 188.15.109.226:10100 BR, Pepe On 05/02/15 10:23, Garino Pierangelo wrote: Hi Angel and All, You didn't miss it, it's just that I didn't create yet (well, I didn't share it...) the doc link, here it is: https://docs.google.com/document/d/1lz7_vtnLCkLSNCVd_AlPrwlh8UzBV_ygUoxLNvgN9KM/edit?usp=sharing I have put few instructions, plus my simple ideas I shared in the last call we had. All the team is invited to contribute to this document with ideas/proposals: I really would like you use this as a place where opinions, proposals, ideas, can be freely shared (even very challenging solutions!). So use it as a working document, you can provide new text, pictures, etc and drop others; for this last point (dropping parts) since google docs is not very good at showing changes, it would be preferable marking unwanted parts as obsolete (e.g. with different color), so we can keep track more easily of what we have decided. All what contributed will be helpful to draw at the end a synthesis that we'll propose to the live demo group. For what concerns the demo issues I'm in favour to analyse them as well. We'll get in touch later in the I2ND call. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Angel Hernandez Inviato: giovedì 5 febbraio 2015 09:22 A: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: [Fiware-robotics] Live demo Brainstorming and network issues Morning Pier, I am not sure if I missed it, but have you shared the brainstorming document for the live demo e talked about? Please let me know if you need any help with that. Also, do you guys want to keep investigating the network issues we experienced on Monday? Let us know if you want to do it over a hangouts session or so. Thank you, Ángel Hernández Director de Proyectos I+D Móvil: +34 661 15 01 67 IKERGUNE. Grupo Etxe-Tar Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non è necessario. -- José Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- José Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150211/6ce8467b/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy