Skip to content

Conversation

@chazyman
Copy link

Updates to

  • urdf xacro to remove tag warning for imu &depth sensor
  • match linorobot starting orientation with gazebo and Navigation
  • added launch files linorobot pose parameters navigation and slam launch files.
  • remove problematical navigation nodes from slam launch file>

@grassjelly grassjelly merged commit 11426a8 into linorobot:jazzy Sep 28, 2025
2 checks passed
@grassjelly
Copy link
Member

thanks @chazyman

@PaulBouchier
Copy link
Collaborator

PaulBouchier commented Sep 28, 2025

@chazyman @grassjelly Was this tested against a background of a system that had been apt update/upgraded recently? AFICT simulation is totally broken again, so navigation in simulation shouldn't have been possible. I checked out the version before this merge and same thing, so the environment is what has broken simulation. In short, I am unable to verify that this fix is good (other than the warnings are gone) until simulation as a whole is fixed.

A likely culprit is the periodic backports of nav2 rolling into jazzy, but this is unproven at present. I went to test this update and I get collision-related errors and the robot doesn't move from its initial position and navigation stops immediately.

I ran the docker image which I have not rebuilt since it last worked, and it worked fine (but it doesn't have this change in it).

I would love to know if you guys see simulation run and are able to navigate the robot on a system that has been apt update/upgraded - maybe I'm doing something stupid (which is not uncommon :-( )

@chazyman
Copy link
Author

chazyman commented Sep 28, 2025 via email

@PaulBouchier
Copy link
Collaborator

Thanks for the reply @chazyman . OK - maybe I'm being stupid and there isn't a regression. The failure I saw was on updated Ubuntu 24.04 running in Gazebo doing navigation. Good to know it worked for you - it's likely my mistake then. We'll talk in a few hours.

@PaulBouchier
Copy link
Collaborator

I was being stupid. I forgot to add the sim:=true parameter when running navigation. Thanks for the help @chazyman - all good now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants