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

Running without stopping #378

Closed
A-janjan opened this issue Oct 21, 2023 · 6 comments
Closed

Running without stopping #378

A-janjan opened this issue Oct 21, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@A-janjan
Copy link

When I go to the Robot info section and then click the forward or backward command in the send command section, I see that my motors start running without stopping. Additionally, when I click stop, nothing changes.

I use POCO X3 Pro.

@A-janjan A-janjan added the bug Something isn't working label Oct 21, 2023
@hardikgarg02
Copy link
Contributor

Please ensure that the app maintains a stable Bluetooth connection with the robot, without any disconnections between commands.

@A-janjan
Copy link
Author

A-janjan commented Nov 3, 2023

No, I didn't use Bluetooth. I just used the main application and the following sections:

openbot_err1

@A-janjan
Copy link
Author

A-janjan commented Nov 7, 2023

I did the firmware testing with an Arduino serial monitor, and at first, I sent, for example, c100,100 and then the motors started running. but after I sent c0,0 and the motors didn't stop. I don't know why motors can't be stopped.

@Eashika2504
Copy link

Eashika2504 commented Dec 15, 2023

Ensure that your motor connections are accurate, and double-check that the specified serial pin numbers in the code align with the actual hardware configuration. Please review the configuration file [README]https://github.com/isl-org/OpenBot/tree/master/body/diy)

@A-janjan
Copy link
Author

A-janjan commented Mar 3, 2024

After I sent a command via a serial monitor (e.g., c50,0), the motors moved correctly, but the serial connection disconnected, and I couldn't send a new command.

@A-janjan
Copy link
Author

The main problem arises when I enable #define HAS_OLED 1 in the DIY body firmware. Consequently, other commands fail to send correctly. However, after disabling the OLED, everything is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants