Skip to content
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

Robot stalls when using python SDK and wheel speeds #406

Open
TAC0C4T opened this issue Jun 15, 2023 Discussed in #405 · 2 comments
Open

Robot stalls when using python SDK and wheel speeds #406

TAC0C4T opened this issue Jun 15, 2023 Discussed in #405 · 2 comments

Comments

@TAC0C4T
Copy link

TAC0C4T commented Jun 15, 2023

Discussed in #405

Originally posted by TAC0C4T June 14, 2023

How are you connecting to your Create 3?

Bluetooth (Python SDK)

Computer(s) Model(s) and Operating System(s)

Thinkpad P43s Windows 11

Which version of ROS 2 is installed on your computer?

None

Which firmware version is installed on your robot?

G.4.3

Which RMW is your robot running?

I don't know

Does your robot have an assigned namespace? If so, please share.

No response

Is the robot connected to a network? If so, what is the network type?

No response

Are there multiple Create 3 robots connected to your network?

None

Is multicast enabled?

None

What is the Adapter Board's USB/BLE Toggle currently switched to?

None

Describe your question.

certain values cause a stall when using robot.set_wheel_speeds(left, right). See attached image. Why do these ones cause this behavior?
image

Edit: I believe this to most likely be a firmware issue (correct me if I am wrong) as this error persists when the robot is held upside down and there is no resistance on the wheels. This still happens for the green values and the red values do not stall in the same manner.

@lukeopteran
Copy link

I have also found sometime while turning the robot via /cmd_vel it can turn quickly then it gets locked out, preventing further robot movement. Turning on and off the e-stop (ros service) allows it to move again. Running Galactic + FW5.2, also happened with previous versions

@shamlian
Copy link
Collaborator

Might this have to do with reflexes being enabled, and conflicting with commands sent? What is the status of the reflexes_enabled parameter?

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

No branches or pull requests

3 participants