-
Notifications
You must be signed in to change notification settings - Fork 71
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
Navigation failure #26
Comments
Hello, I don't know what to do with this, I haven't looked at the robot for years. ODrive updated their firmware so the units are different. I have no easy way to test your pull request before merging it. Feel free to fork the repository / publish your own version though. |
@PranshuTople maybe you can help point me in the right direction here? I updated the arduino code to convert the new units from the new ODrive firmware. I can drive the robot around with the rosremote and create a good map, but whenever I make a way point with the navigation stack, the robot stutters its movement. Any ideas on what I can look at? |
Hey @kssummer, Can you share a video of your robot's motion first in teleoperation mode and later in navigation? I want to see how it behaves in order to comment on anything |
Couldn't get the unit conversion right. @kssummer would you mind sharing your fix? |
I'm having trouble with the navigation stack. When I make a waypoint, my robot starts jerking around; no smooth movement. Today the robot fell over because of this. Any idea on what could cause this? Or how to fix it?
For background, I was able to get the robot moving smoothly. I had to change the arduino code to convert the Odrive turns to millimeters, but now its fine. The odom, base_link, and lazer show up in rviz. I can drive around fine, the lazer scan stays put, and I have built a map of my living room. I launched the navigation stack, the map comes up, although the costmap looks rather inflated, but the robot is oriented right, assuming I place it in my room where I started the map.
It looks like the navigation stack is continuously updating its plan. The robot never really gets a chance to drive straight; instdead it whips back and forth like a low-rent murder bot. My dogs are concerned.
(I rolled back the git repository to the original navigation commit, before the simulation stuff was merged just to be sure that wasnt the issue, but both versions have this issue. In the latest code, the lazer scan gets out of synch with the map; that doesn't happen in the original version)
Here's the log from the navigation:
roslaunch rur_navigation rur_navigation.launch map_file:=$HOME/ros_catkin_ws/src/rur_navigation/maps/livingroom_sean.yaml
... logging to /home/sean/.ros/log/546ce954-4473-11ed-920f-bfb2a73f92b8/roslaunch-beefcake-62996.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://beefcake:38965/
SUMMARY
PARAMETERS
NODES
/
amcl (amcl/amcl)
map_server (map_server/map_server)
move_base (move_base/move_base)
rviz (rviz/rviz)
ROS_MASTER_URI=http://beefcake:11311/
process[map_server-1]: started with pid [63010]
process[amcl-2]: started with pid [63011]
process[move_base-3]: started with pid [63012]
process[rviz-4]: started with pid [63013]
[ WARN] [1664949824.319884472]: global_costmap: Pre-Hydro parameter "static_map" unused since "plugins" is provided
[ WARN] [1664949824.322084663]: global_costmap: Pre-Hydro parameter "map_type" unused since "plugins" is provided
[ INFO] [1664949824.323612027]: global_costmap: Using plugin "static_layer"
[ INFO] [1664949824.335591525]: Requesting the map...
[ INFO] [1664949824.552640402]: Resizing costmap to 4000 X 4000 at 0.050000 m/pix
[ INFO] [1664949824.638152634]: Received a 4000 X 4000 map at 0.050000 m/pix
[ INFO] [1664949824.641547153]: global_costmap: Using plugin "obstacle_layer"
[ INFO] [1664949824.648233895]: Subscribed to Topics: laser_scan_sensor
[ INFO] [1664949824.690791106]: global_costmap: Using plugin "inflation_layer"
[ WARN] [1664949824.714233355]: local_costmap: Pre-Hydro parameter "static_map" unused since "plugins" is provided
[ WARN] [1664949824.714581156]: local_costmap: Pre-Hydro parameter "map_type" unused since "plugins" is provided
[ INFO] [1664949824.715196525]: local_costmap: Using plugin "static_layer"
[ INFO] [1664949824.716935080]: Requesting the map...
[ INFO] [1664949824.723119098]: Resizing static layer to 4000 X 4000 at 0.050000 m/pix
[ INFO] [1664949824.817654056]: Received a 4000 X 4000 map at 0.050000 m/pix
[ INFO] [1664949824.822867309]: local_costmap: Using plugin "obstacle_layer"
[ INFO] [1664949824.830207345]: Subscribed to Topics: laser_scan_sensor
[ INFO] [1664949824.862274927]: Created local_planner dwa_local_planner/DWAPlannerROS
[ INFO] [1664949824.863158973]: Sim period is set to 0.10
[ INFO] [1664949825.372567819]: Recovery behavior will clear layer 'obstacles'
[ INFO] [1664949825.383337989]: Recovery behavior will clear layer 'obstacles'
[ INFO] [1664949825.460528551]: odom received!
[ INFO] [1664949838.910582055]: Got new plan
[ INFO] [1664949839.110644220]: Got new plan
[ INFO] [1664949839.310618806]: Got new plan
[ INFO] [1664949839.510602139]: Got new plan
[ INFO] [1664949839.710688622]: Got new plan
[ INFO] [1664949839.910631436]: Got new plan
[ INFO] [1664949840.110506338]: Got new plan
[ INFO] [1664949840.310614113]: Got new plan
[ INFO] [1664949840.510615518]: Got new plan
[ INFO] [1664949840.710569169]: Got new plan
[ INFO] [1664949840.910464401]: Got new plan
[ INFO] [1664949841.110492117]: Got new plan
[ INFO] [1664949841.310661979]: Got new plan
[ INFO] [1664949841.510527558]: Got new plan
[ INFO] [1664949841.710613075]: Got new plan
[ INFO] [1664949841.910624391]: Got new plan
[ INFO] [1664949842.110641782]: Got new plan
[ INFO] [1664949842.310630494]: Got new plan
[ INFO] [1664949842.510672744]: Got new plan
[ INFO] [1664949842.710608765]: Got new plan
[ INFO] [1664949842.910698871]: Got new plan
[ INFO] [1664949843.110593497]: Got new plan
[ INFO] [1664949843.310540360]: Got new plan
[ INFO] [1664949843.510582199]: Got new plan
[ INFO] [1664949843.710666019]: Got new plan
[ INFO] [1664949843.910593931]: Got new plan
[ INFO] [1664949844.110599047]: Got new plan
[ INFO] [1664949844.310571304]: Got new plan
[ INFO] [1664949844.510679543]: Got new plan
[ INFO] [1664949844.710543665]: Got new plan
[ INFO] [1664949844.910458401]: Got new plan
[ INFO] [1664949845.110632632]: Got new plan
[ INFO] [1664949845.310576916]: Got new plan
[ INFO] [1664949845.510588454]: Got new plan
[ INFO] [1664949845.710548413]: Got new plan
[ INFO] [1664949845.910618182]: Got new plan
[ INFO] [1664949846.110646003]: Got new plan
[ INFO] [1664949846.310541918]: Got new plan
[ INFO] [1664949846.510692447]: Got new plan
The text was updated successfully, but these errors were encountered: