-
Notifications
You must be signed in to change notification settings - Fork 25
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
Gen2.1.20 - YIYUN YK204U (looks almost similar to "target_1=GD32F130/v17=2.19" Gotrax" #86
Comments
As the headers have a different layout to 2.1.17 I do not think the pin definitions will be compatible. But as you should test with a 2A cc power supply anyway, it is not that dangerous to test all 2.1.x dummy binaries until one makes the motors spin. But running my autodetect binary will do no harm either and more likely gives you a complete set of working pin definitions. |
I have the same boards (16pcs) 2.18 makes the motor vibrate and my psu current limit |
use auto detect maybe |
Ok, autodetect worked :) , now the motor spins fine in one direction but has little to no torque in the other direction. Will continue investigating this tomorrow. |
How would this board fall into the naming/numbering convention? I would like to create a new config for it |
I think this board should become
Please post some nice photos of front and back here (with cables bent out of sight) No idea why no torque in other direction. |
I will post the full log tomorrow. Are you supposed to externally power the 3.3V rail during auto detect? Because my board turned off during the power switch detection. The low torque was in the RemoteDummy firmware. But I will hook up a scope tomorrow to investigate further. And the buzzer did not sound during auto detection. But I suspect it shares pins with uart0 |
no, in the final try to detect power switch, i think the board is intentionally shut down. So you should NOT power the mcu with extra 3.3V If torque is not symmetrical, then it might be that the hall sensors order is wrong. But if motor is running very smoothly, that hall order should be correct. Do you see the three led blink according to the rotation of the motor ?
|
you can use my detecting algorithm, it never make mistake yet |
got a f031 board, will play with it when i have time |
in my reverse engineering, all the battery voltage detecting voltage divider is after the p mosfet for latch |
but i think my current detect routine is good ill not change it |
current detection ??? i guess you are talking about your MM32 pinFinder. |
i mean for hall detect you can use my algorithm |
Let's wait to see if for @jonasniesner my hall permutation detection indeed got it wrong. |
Ok, I got further. It looks like the hall order was wrong. This is what I have so far
|
The third led is nice to show the three hall sensors. |
robo can you send me stlink driver thanks |
You mean this www.robosoft.de/forums/en.stsw-link004_v4.6.0.zip ? Actually i do not remember if that had been official downloads. I just found them on my computer and uploaded them for you. |
thanks, actually this is available elsewhere, but i forgot where to find it, i installed old version of stlink utilities and it didnt include the driver, i thought i need seperate file to install the driver |
Hello,
i recently bought a used Hoverboard .
The Split PCBs look almost like the GD32F130/v17=2.19 Gotrax, but not quite.
some Photos attached.
i try to use the Gotrax config and report my progress.
The text was updated successfully, but these errors were encountered: