-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linorobot2 bringup issue on Ubuntumate22.04.3 #85
Comments
Something similar is happening to me, only if I set LINOROBOT2_DEPTH_SENSOR to 'realsense'. I get:
If I leave LINOROBOT2_DEPTH_SENSOR blank and use only a laser sensor with LINOROBOT2_LASER_SENSOR (not the realsense), it works fine |
Dear Juan Jimeno sir, Alternatively: |
can you try setting LINOROBOT2_DEPTH_SENSOR=“” ? |
if i put depth sensor ="" its working with out realsense... no issue . BUT PROBLEM SOLVED: with regards, HEMS. |
Actual problem is located. Its due to addition of oakd... camera in "depth.launch.py" . Problem solved by commenting few lines of code which are related to oakd. |
Dear Sir,
when I run below code its throwing error as shown below'. However there is no error while executing slam and navigation files, please help me. log file is showing same content which is shown below. I think the issue may be with default_robot.launch or custom_robot.launch . this para of script have some issue with latest kernel...
""line 79-85 in the "linorobt2_bringup.launch.py"
from launch.actions import DeclareLaunchArgument, IncludeLaunchDescription
from launch.substitutions import LaunchConfiguration, PathJoinSubstitution, PythonExpression
""
Thank you,.
... HEM.
rock@rock:~/linorobot2_ws $ ros2 launch linorobot2_bringup bringup.launch.py
[INFO] [launch]: All log files can be found below /home/rock/.ros/log/2023-09-19-22-16-15-735043-rock-48883
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): <launch.substitutions.launch_configuration.LaunchConfiguration object at 0x7ffb44442290>
The text was updated successfully, but these errors were encountered: