Manager launch file missing offset.yaml file about rh-p12-rn HOT 6 CLOSED

If the file does not exist, offset is used as 0 by default.
In case of RH-P12-RN, it is not necessary to set offset.

from rh-p12-rn.

The manager launch file asks for offset.yaml file. I can't even start the launch file. So does that mean I can just get rid of that line...?
I don't even know which parameter to set 0. Can you elaborate more, please?

from rh-p12-rn.

In the launch file

<param name="offset_file_path"         value="$(find rh_p12_rn_manager)/config/offset.yaml"/>

In the rh_p12_rn_manager.cpp file

...
  nh.param<std::string>("offset_file_path", g_offset_file, "");
...
  // load offset
  if (g_offset_file != "")
  controller->loadOffset(g_offset_file);
...

If the file does not exist, g_offset_file will be "" (default value).
So, controller does not load offset file.
The offset_file_path parameter of the launch file is the code to use when the file exists.
If the file doesn't exist, no problem.

from rh-p12-rn.

However when I run the launch file I get this error

Am I doing something wrong?

from rh-p12-rn.

Looking at the robotis_controller file, I guess "Failed to load offset.yaml" is just a default ROS_WARN error when yaml file doesn't exist.

The next problem is what can I do with "creating timer thread filed error"

from rh-p12-rn.

The "creating timer thread failed" error is a permission issue.

To increase real-time scheduling priority(rtprio) for current user group, (if your group is robotis)

$ sudo bash -c 'echo "@robotis - rtprio 99" > /etc/security/limits.d/robotis-rtprio.conf'

reboot and launch manager.

or.. you should launch the manager in the root shell

$ sudo bash
# roslaunch rh_p12_rn_manager rh_p12_rn_manager.launch

from rh-p12-rn.