search

flybeyond / atrias

Automatically exported from code.google.com/p/atrias
0 stars 0 forks source link

Make it easy to get software system up and running #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently, getting the software up and running across the nettop and desktop 
require quite a few steps, possibly in a certain order.

We need to make this a two-step process:

On nettop:
{{{
roslaunch atrias nettop.launch
}}}

On desktop:
{{{
roslaunch atrias desktop.launch
}}}

Original issue reported on code.google.com by yoos117@gmail.com on 24 Oct 2011 at 9:51

GoogleCodeExporter commented 9 years ago 
Almost there. Currently there is no way to automatically load the kernel 
modules, which we need to do often for rtai_controller. This is especially so 
because inserting kernel modules requires root privileges, and we'd rather not 
run ROS commands as root. If there was a way to reset the Medullas from the 
controller without reinserting that module, we could just stick rtai_controller 
and rt_shm into the startup modules list.

Eventually, we don't want any of this custom kernel modules stuff, but that's 
something for later.

Original comment by yoos117@gmail.com on 25 Oct 2011 at 4:09

GoogleCodeExporter commented 9 years ago 
Launching software components is now done with nettop.launch and 
desktop.launch, with the exception of manually loading the kernel modules. 
Unfortunately, there is no way to load kernel modules with roslaunch.

The function of the kernel modules will eventually be replaced with Orocos RTT: 
http://code.google.com/p/atrias/issues/detail?id=32

As such, this ticket will be closed.

Original comment by yoos117@gmail.com on 28 Oct 2011 at 3:17