ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

Configuring startup files (robot_upstart).

asked 2020-04-14 14:32:06 -0500

smarn gravatar image

Hello guys. We have just received a husky uvg at my lab and I am humbly trying to step out of the simulating world and set up the platform.

I would like to test some of the nodes I developed in simulation and make them run at start-up in the backround along with the standard startup husky nodes.

In the user manual, clearpath suggests to simply copy the custom launch file in the /etc/ros/kinetic/husky-core.d folder where the standard husky launch files are located (state publiser, localization etc)

While this works and the nodes do appear after boot (i checked it in my remote) it someshow doesn't feel like a robust technique. So after reading a little on the robot_upstart command and ubuntu's service and systemctl commands I believe that the best way to do what I want would be either to

  1. create a new system service containing all the custom launch files to be launched at system boot or
  2. create a new system service for each launch file.

I am closing towards the first. Should I proceed and do that or is there something that I have missintepreted that could cause a problem?

Thank you!

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2020-04-24 07:20:07 -0500

smarn gravatar image

Looks like it is sufficient to just copy any .launch file that is to be called during start-up in the /etc/ros/kinetic/ros.d directory (eventually in my case it is not husky-core.d but ros.d) so i'm closing this one.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2020-04-14 14:32:06 -0500

Seen: 233 times

Last updated: Apr 24 '20