Open alexswerner opened 2 months ago
We replaced the drive units of the base which did not fix the issue.
It looks like a bumper sensor is being triggered when starting to drive.
After cleaning the bumper inside I'm still getting:
header:
stamp:
sec: 0
nanosec: 0
frame_id: base_link
detections:
- header:
stamp:
sec: 1727197777
nanosec: 639798548
frame_id: base_link
type: 0
---
header:
stamp:
sec: 0
nanosec: 0
frame_id: base_link
detections:
- header:
stamp:
sec: 1727197777
nanosec: 991799204
frame_id: base_link
type: 0
---
header:
stamp:
sec: 0
nanosec: 0
frame_id: base_link
detections: []
---
And after this the robot still stops/turns around.
And /ir_intensity
is showing:
---
header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: base_link
readings:
- header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: ir_intensity_side_left
value: 0
- header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: ir_intensity_left
value: 3
- header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: ir_intensity_front_left
value: 0
- header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: ir_intensity_front_center_left
value: 1
- header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: ir_intensity_front_center_right
value: 4
- header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: ir_intensity_front_right
value: 0
- header:
stamp:
sec: 1727197947
nanosec: 740484766
frame_id: ir_intensity_right
value: 1
---
Where all values are flickering from 0-4.
Setting reflexes_enabled: false
in the motion_control yaml configuration does fix the behavior. My guess is that the bumper electronics have an issue (since it affects all bumpers). Temporarily this is acceptable but some functionality of the base is apparently still impacted - automatic docking does not work.
Hi there Alexander for creating this ticket.
I'm sorry to see your TB4 is experiencing this issue.
Could you please replicate your concern and then please share the Create3 logs?
Big thanks,
Rusty
base.log
@RustyCPR
Here is the log. I rebooted the robot and let it start completely. Then backed it off the base and drove it onto the base (manually). This is with reflexes_enabled: false
, so I'm not sure if the issue is visible. If needed I can provide another log with reflexed_enabled: true
. Just let me know.
Hello @alexswerner ,
Thank you for providing the logs. Would it be possible to provide logs with reflexed_enabled: true
and if possible, the strange driving behaviour replicated.
Looking forward to hearing from you soon. Best Regards, Saif
base.log
Here is the log with reflexed_enabled: true
. It immediately displayed the strange behavior. In this session I rebooted the base while the robot was on the dock. Then drove it backwards off the base. This resulted in the robot spinning, like it was trying to avoid an obstacle.
Hello @alexswerner Thank you for sending these logs. We'll begin our analysis and let you know what we find. Looking forward to connecting soon. Best Regards, Saif
Hello @alexswerner , Apologies for the late reply on this. Reviewing the log details it seems that the drive issue may be due to a firmware issue on the Create 3. Would it be possible to try and:
Following the above process let us know if the Turtlebot 4 unit still exhibits the erratic driving behaviour.
Looking forward to hearing from you soon. Best Regards, Saif
Hello @alexswerner , It has been quite some time since I last heard from you. Do you have any updates to share? Looking forward to hearing from you soon. Best Regards, Saif
Robot Model
Turtlebot4 Standard
ROS distro
Humble
Networking Configuration
Discovery Server
OS
Ubuntu 22.04
Built from source or installed?
Built from Source
Package version
Base: H2.6.
Expected behaviour
The robot should move forward or backward in a straight line when commanded to do so.
Actual behaviour
When commanding the robot to drive forward, the robot is spinning on the spot, alternating between clock-wise and counter-clock-wise every 500ms. The same happens when command backwards.
Error messages
To Reproduce
Launch console application for keyboard teleoperation. Command the robot to move forward and backwards.
Other notes
Performed factory reset of the base, but this did not change the behavior.