Have you tested other motors or only those two? Does it happen on both sides?
1 Like
don’t have anything else apart from another set of hubs or my old tb 6374s missing the right connectors.
1 Like
That sucks. Would running the motors at .85 with the crackling noise do any harm?
That this happens on 5.01 is what really confuses me. Are you certain of that? If you reboot the ESC, does it still say 5.01?
1 Like
No idea, i wouldn’t trust using it anyway.
1 Like
have to check later. Almost 5am, time to sleep.
What i definitely can say is that the vesc tool tells me that i have older fw when using tool 3.00 (5.02) with 2.06 (5.01) firmware
Do u also have the weird speed problem with one side as well?
Im on 5.01, im certain of it.
1 Like
don’t think i have.
Just wanna note, im on android vesc tool 3.00 i believe. Ill try detection on pc and maybe try to use vesc tool 2.06, see if it makes a difference.
5.02 was the last one i flashed.
Did this ever happen on 5.01 for you? Confirmed?
i can try again.
Going by what i already observed i’d say yes.
1 Like
So, fresh install of 5.01, now doing motor detection
1 Like
this is absolutely wrong
2 Likes
still did a throttle test with NOTHING changed. Stock vesc tool 2.06 (DCCLS is at 1)
clean as it should be on full throttle, trigger is at the absolute max it can go
Now i’m going to change the duty cycle current limit start to 0.85
stock
updated
aaand it’s back
2 Likes
redid the motor detection after setting DCCLS to 0.85
this is the result that’s correct.
2 Likes
Tested it again with yet another motor.
DCCLS = 1 = no issue
DCCLS = 0.85 = issue
2 Likes
sure, but it’s not just the unity that shows this behavior.