Will the new firmware allow a combination of hall sensors and encoder? I already have the as5311 installed. But would like to use the hall sensor for position alignment on startup.
I think the firmware will allow it, but the limit will be how many spare pins you have to get both in at once.
Ok. I’ll use only encoder for now, and do the calibration on each startup, and we’ll see what happens in the future about indexing, or maybe a low power mode to count pulses when the vehicle is not in use.
What configuration settings do you recommend for the hoverboard motors? I installed the first motor today, but got DRV fault, so I’ll do the cap modification tomorrow.
So actually the high inductance of these motors and the noise of the current sensors means that there are stability issues with the current controller at the hard-coded bandwidth. You can take a look at the
powerwheels branch, but unfortunately you will have to figure out what’s going on. I can’t support it right now, if you can’t get it to work you will have to wait until I have integrated the hoverboard wheel stuff into devel and I have added documentation.
Excellent, we received in Brazil an odroid v3.4 about three months ago and we are trying to make it work with these 6.5 "wheels. Now I see that the question is very complex, do you have any tips or parameters that can help us?
Yes, I get error code 3 now. Will decreasing the resistance by resoldering the motor from star to delta make it work?
In a few weeks I hope to find the time to do a hoverboard wheel configuration recommendation writeup.
that would be brilliant!
Fantastic, here we have the wheels BLDC and Odrive 3.4, if there is any test that we can do or collaborate please let us know we will do it quickly and return the result