You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value of the J23_factor can be determined at runtime using info that is stored on the controller on which the KAREL programs are running. As this is (at the moment) the only difference between the fanuc_driver and the generic industrial_robot_client binaries, this would allow the fanuc_driver to return to using those generic binaries.
This would reduce the amount of custom code and launch files, thus reducing maintainance effort and potential sources of errors.
The text was updated successfully, but these errors were encountered:
This is possible -- and I've already done it -- but changing this behaviour of fanuc_driver will break compatibility between fanuc_driver Karel code (ie: ROS_STATE) and the ROS side. Users will have to be instructed to upgrade the Karel code as well if this ever gets implemented.
The value of the
J23_factor
can be determined at runtime using info that is stored on the controller on which the KAREL programs are running. As this is (at the moment) the only difference between thefanuc_driver
and the genericindustrial_robot_client
binaries, this would allow thefanuc_driver
to return to using those generic binaries.This would reduce the amount of custom code and launch files, thus reducing maintainance effort and potential sources of errors.
The text was updated successfully, but these errors were encountered: