-
Notifications
You must be signed in to change notification settings - Fork 409
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
Motor Command zero crossing causes disconnect #162
Comments
Hi @vamfun |
Yes.... the board has six pins that are wired differently... the problem was the v_battery is not showing any voltage so the board disengages . Software interlocks keep it from shutting down until the command is low. That’s why it will allow a half cycle of test run.
Fixing the GPIO cures the problem. The board is marked ROHS as described in the following photo.
![image](https://user-images.githubusercontent.com/4359767/104108953-de5da200-527d-11eb-9d74-13ef2e6f2aab.jpeg)
![image](https://user-images.githubusercontent.com/4359767/104108944-be2de300-527d-11eb-8fc5-fa04cefe2a28.png)
See issue #126 of EmanualFeru-hoverboard-hack-FOC. “Charging enables motors on Alternate H1 motherboard ...”. It has the new pin outs. I am using the FOC firmware since I’m making the motors into servos and need good slow speed performance. I’ve got the board working using the low resolution hall sensors for position. Not bad..gets 4 deg resolution 😎
http://vamfun.wordpress.com
Robot musing blog
iPhone
… On Jan 9, 2021, at 8:44 AM, DanielQuintana2 ***@***.***> wrote:
Hi @vamfun
I'm having the same problem here. Have you found any solutions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thank you so much @vamfun !!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a strange problem with my HOVER - 1 H1 model motherboard. (See link pictures https://vamfun.wordpress.com/2020/12/23/flying-firehose-blog-1-hover-1-h1-hoverboard-tear-down/)
Any command that transitions to reverse direction either + to - or vice versa causes a shutdown that requires a power on restart. If the board starts with a command you can adjust the motors with ADC but disconnects when command gets below 8. I’ve tried most Foc firmware and other firmware variants and all produce the same shutdown. Running a straight motor test download runs a one sided test...motors disconnect on the reverse transition.
Any thoughts?
The text was updated successfully, but these errors were encountered: