[Fiware-robotics] R: R: R: R: Firos GIT

fabio.dibenedetto at consoft.it fabio.dibenedetto at consoft.it
Tue Jun 30 09:25:09 CEST 2015


No problem about that but it's only because I haven't follow much about what you were doing and I didn't know there was another web/application server in firos other than the one used for expose the API. Is it on another port than the one used for exposing your API, right? Is it an outbound port too? Don't know if it will be available for the demo so for now I will use without that
Thanks

-----Messaggio originale-----
Da: Iñigo Gonzalez [mailto:igonzalez at ikergune.com] 
Inviato: martedì 30 giugno 2015 08:55
A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org
Oggetto: Re: [Fiware-robotics] R: R: R: Firos GIT

Hi,

inside firos a nodejs server is also brought up to allow users to access some ROS capabilities that are not accessible via context broker and this tool is also compatible with more browsers than rosbridge.

Anyway you can disable it by deleting the entry "map_server_port" in your firos/config/config.json file.

Regards,
Iñigo

On 29/06/15 17:54, fabio.dibenedetto at consoft.it wrote:
> Sorry to disturb again but I commented the part relative to 
> move_base_msgs because I only need to launch firos for now to see if 
> the port exchange works on rcm side, but I have another issue
>
> sudo: npm: command not found
> Exception in thread Thread-4:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
>     self.run()
>   File "/usr/lib/python2.7/threading.py", line 763, in run
>     self.__target(*self.__args, **self.__kwargs)
>   File "/home/fabiog/catkin_ws/src/firos/scripts/include/mapServer.py", line 48, in _launchMapServer
>     subprocess.Popen(["node", mapserver_path + "mapserver.js", str(MAP_SERVER_PORT), str(ROSBRIDGE_PORT)])
>   File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
>     errread, errwrite)
>   File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
>     raise child_exception
> OSError: [Errno 2] No such file or directory
>
> Installing node.js is really mandatory? What is the mapserver for? Can I avoid to use this component or is required for firos? 
>
>
>
> -----Messaggio originale-----
> Da: Iñigo Gonzalez [mailto:igonzalez at ikergune.com]
> Inviato: lunedì 29 giugno 2015 16:12
> A: Antonini Roberto; fabio.dibenedetto at consoft.it; 
> fiware-robotics at lists.fi-ware.org
> Oggetto: Re: R: [Fiware-robotics] R: Firos GIT
>
> That's it
>
> On 29/06/15 16:11, Antonini Roberto wrote:
>> Hi Inigo,
>> As far as I understood your FIROS depends on move_base_msgs package in a dynamic way, isn't it?
>> So if I remove move_base entries in config/robot.json, everything will work correctly, right?
>>
>> Thk
>> R&FG
>>
>>
>> -----Messaggio originale-----
>> Da: fiware-robotics-bounces at lists.fi-ware.org
>> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Iñigo 
>> Gonzalez
>> Inviato: lunedì 29 giugno 2015 15:29
>> A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org
>> Oggetto: Re: [Fiware-robotics] R: Firos GIT
>>
>> Hi Fabio,
>>
>> the firos you have donwloaded is configured to work with the turtlebot, so what it does on startup is to read on the config.json the robot list and configure ros listeners and publishers.
>>
>> The problem seems to be that the machine where you are launching the firos instance hasn't the move_base handlers installed, maybe try to install the turtlebot¡s software and running it again.
>>
>> Regards,
>> Iñigo
>>
>> On 29/06/15 15:16, fabio.dibenedetto at consoft.it wrote:
>>> Hi guys,
>>> can I have a little help? I downloaded the new firos last week but 
>>> I'm trying only today to launch it for the first time. I'm having 
>>> some trouble (at the end of the mail what I received using rosrun 
>>> firos core.py). Have I missed anything? Looking quickly in the code 
>>> I've seen that I have to use -Pport to pass the port parameter: is 
>>> that right? But for now I haven't tried that way for now
>>>
>>> shell output:
>>>
>>> Initializing ROS node: firos
>>> Initialized
>>>
>>> Starting Firos setup...
>>> ---------------------------------
>>>
>>>
>>> Generating Message Description Files
>>>
>>> Generating message definition for robot2/cmd_height
>>>
>>> Succesfully generated
>>>
>>>
>>> Starting Firos...
>>> ---------------------------------
>>>
>>> Getting configuration data
>>> Generating topic handlers:
>>>   -robot2
>>>     -cmd_vel_mux/input/teleop
>>>     -cmd_serial
>>>     -move_base/goal
>>> Traceback (most recent call last):
>>>   File "/home/fabiog/catkin_ws/src/firos/scripts/core.py", line 87, in <module>
>>>     loadMsgHandlers(confManager.getRobots(True, True))
>>>   File "/home/fabiog/catkin_ws/src/firos/scripts/include/ros/topicHandler.py", line 75, in loadMsgHandlers
>>>     theclass = LibLoader.loadFromSystem(topic['msg'])
>>>   File "/home/fabiog/catkin_ws/src/firos/scripts/include/libLoader.py", line 57, in loadFromSystem
>>>     module = __import__(module_name, globals(), locals(),
>>> [module_name.split('.')[-1]])
>>> ImportError: No module named move_base_msgs.msg
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----Messaggio originale-----
>>> Da: fiware-robotics-bounces at lists.fi-ware.org
>>> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose 
>>> Jaime Ariza
>>> Inviato: venerdì 26 giugno 2015 11:58
>>> A: fiware-robotics at lists.fi-ware.org
>>> Oggetto: [Fiware-robotics] Firos GIT
>>>
>>> Hi,
>>>
>>> You can find FIROS in https://github.com/Ikergune/firos/
>>>
>>> BR,
>>> Pepe
>>>
>> _______________________________________________
>> Fiware-robotics mailing list
>> Fiware-robotics at lists.fi-ware.org
>> https://lists.fi-ware.org/listinfo/fiware-robotics
>>
>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
>>
>> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
>>
>>
> _______________________________________________
> Fiware-robotics mailing list
> Fiware-robotics at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-robotics
>




More information about the Fiware-robotics mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy