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. 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

  3. 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.

  4. #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.

  5. #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.

  6. #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.

  7. #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.

  8. 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?