home.social

#odometry — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #odometry, aggregated by home.social.

  1. What's on my mind?

    Disappointment and Disillusionment!

    - Invested 7 yrs in
    - Created nodes for , , , , , , , , and

    - My robot cannot safely and reliably navigate in my complex home environment.
    - No slower turns, no inflation value can fix

    I'm done, destroyed, no strength left for "one more try". GoPi5Go-Dave is on the shelf with other "reached its limit" robots.

  2. What's on my mind?

    Disappointment and Disillusionment!

    - Invested 7 yrs in #GoPiGo3 #robot
    - Created #ROS2 nodes for #proprioception, #odometry, #LIDAR, #docking, #tts #mapping, #navigation, #simulation, #ObjectRecognition, and #LifeLogging

    - My robot cannot safely and reliably navigate in my complex home environment.
    - No slower turns, no inflation value can fix

    I'm done, destroyed, no strength left for "one more try". GoPi5Go-Dave is on the shelf with other "reached its limit" robots.

  3. At this reduced transfer rate, the can make a two byte transfer in 0.0003 seconds, which means it can retrieve the left and right wheel encoder values roughly 1700 times per second - plenty fast enough for my robot to publish and the resultant at 30 Hz.

  4. Mapping w/o Localization

    Got slam_toolbox mapping with localization turned off, but managed to figure out how to serve up a better looking map from my house floor plan.

    The weakness of dead reckoning becomes very evident with the floorplan map.

    Next up - with and

  5. #SLAM_Toolbox Mapping w/o Localization

    Got slam_toolbox mapping with localization turned off, but managed to figure out how to serve up a better looking map from my house floor plan.

    The weakness of dead reckoning #odometry becomes very evident with the floorplan map.

    Next up - #DeadReckoning #navigation with #ros2humble #nav2 and #map_server

  6. #SLAM_Toolbox Mapping w/o Localization

    Got slam_toolbox mapping with localization turned off, but managed to figure out how to serve up a better looking map from my house floor plan.

    The weakness of dead reckoning #odometry becomes very evident with the floorplan map.

    Next up - #DeadReckoning #navigation with #ros2humble #nav2 and #map_server

  7. #SLAM_Toolbox Mapping w/o Localization

    Got slam_toolbox mapping with localization turned off, but managed to figure out how to serve up a better looking map from my house floor plan.

    The weakness of dead reckoning #odometry becomes very evident with the floorplan map.

    Next up - #DeadReckoning #navigation with #ros2humble #nav2 and #map_server

  8. #SLAM_Toolbox Mapping w/o Localization

    Got slam_toolbox mapping with localization turned off, but managed to figure out how to serve up a better looking map from my house floor plan.

    The weakness of dead reckoning #odometry becomes very evident with the floorplan map.

    Next up - #DeadReckoning #navigation with #ros2humble #nav2 and #map_server

  9. SLAM - First Attempt

    My ir2scan node is working well, but setting the 52 params is a mystery.

    My create3_navigation slam.launch.py (using LIDAR parms modified for Create3 IR "distance" sensor scan), with Wali facing a wall, maps a wall!

    (bouncing around in angle in front of bot...)

    As I proceed to drive Wali around the room, more walls enclosing a "known to be open" space are mapped, but not where the sensors and put them.

  10. #Create3 #IRsensor SLAM - First Attempt

    My ir2scan node is working well, but setting the 52 #slam_toolbox params is a mystery.

    My create3_navigation slam.launch.py (using #Turtlebot4 LIDAR parms modified for Create3 IR "distance" sensor scan), with Wali facing a wall, maps a wall!

    (bouncing around in angle in front of bot...)

    As I proceed to drive Wali around the room, more walls enclosing a "known to be open" space are mapped, but not where the sensors and #odometry put them.

  11. #Create3 #IRsensor SLAM - First Attempt

    My ir2scan node is working well, but setting the 52 #slam_toolbox params is a mystery.

    My create3_navigation slam.launch.py (using #Turtlebot4 LIDAR parms modified for Create3 IR "distance" sensor scan), with Wali facing a wall, maps a wall!

    (bouncing around in angle in front of bot...)

    As I proceed to drive Wali around the room, more walls enclosing a "known to be open" space are mapped, but not where the sensors and #odometry put them.

  12. #Create3 #IRsensor SLAM - First Attempt

    My ir2scan node is working well, but setting the 52 #slam_toolbox params is a mystery.

    My create3_navigation slam.launch.py (using #Turtlebot4 LIDAR parms modified for Create3 IR "distance" sensor scan), with Wali facing a wall, maps a wall!

    (bouncing around in angle in front of bot...)

    As I proceed to drive Wali around the room, more walls enclosing a "known to be open" space are mapped, but not where the sensors and #odometry put them.

  13. #Create3 #IRsensor SLAM - First Attempt

    My ir2scan node is working well, but setting the 52 #slam_toolbox params is a mystery.

    My create3_navigation slam.launch.py (using #Turtlebot4 LIDAR parms modified for Create3 IR "distance" sensor scan), with Wali facing a wall, maps a wall!

    (bouncing around in angle in front of bot...)

    As I proceed to drive Wali around the room, more walls enclosing a "known to be open" space are mapped, but not where the sensors and #odometry put them.

  14. Anyone aware of any studies of accuracy of only versus encoder with using ?

    The even fuses encoders with IMU and an flow sensor".

    Does that suggest I should not expect great improvement with only encoders and IMU?

  15. Anyone aware of any studies of #odometry accuracy of #encoder only versus encoder with #IMU using #EKF?

    The #iRobot #Create3 even fuses encoders with IMU and an #optical flow sensor".

    Does that suggest I should not expect great improvement with only encoders and IMU?