The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Can you tell us what the value is of LC_NUMERIC? You can print it using echo $LC_NUMERIC in a terminal.
There is a good chance you're running into an issue with urdf and locales which use , for decimals instead of . (ie: comma vs dot).
| | 2 | No.2 Revision |
Can you tell us what the value is of LC_NUMERIC? You can print it using echo $LC_NUMERIC in a terminal.
There is a good chance you're running into an issue with urdf and locales which use , for decimals instead of . (ie: comma vs dot).
See #q272692 for a related Q&A.
the output gives
LC_NUMERIC=it_IT.UTF-8. Should I set the english standard?
As a test, you could see whether the following "solves" your problem:
export LC_NUMERIC="en_US.UTF-8"If your robot -- with the scaling in place -- now does appear, it's most likely ros/urdfdom_headers#41.
| | 3 | No.3 Revision |
Can you tell us what the value is of LC_NUMERIC? You can print it using echo $LC_NUMERIC in a terminal.
There is a good chance you're running into an issue with urdf and locales which use , for decimals instead of . (ie: comma vs dot).
See #q272692 for a related Q&A.
the output gives
LC_NUMERIC=it_IT.UTF-8. Should I set the english standard?
As a test, you could see whether the following "solves" your problem:
export LC_NUMERIC="en_US.UTF-8"If your robot -- with the scaling in place -- now does appear, it's most likely ros/urdfdom_headers#41.
If it is 41, then it should have been fixed recently. According to this comment on the bug report, enabling the bionic-updates repository and updating urdfdom and urdfdom-headers should really fix things (ie: you should not need to use the LC_NUMERIC="en_US.UTF-8" work-around).
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.