Hey all I have a build that I have been having issues with. I built a street board with the Unity ,10S5P battery, 200kv motors and 100mm boa wheels, 2.1 gear ratio. Recently I’ve had 2 buddies fall on my board doing speed runs at full throttle and both got seriosly injured. Both times it happened they said it felt like the breaks locked up but weren’t 100% certain if they didnt accidentally hit the breaks themselves. So I wasnt sure what to think. Last night I went on a ride on my regular path and noticed a long incline so I wanted to test my board up this hill at full throttle…i was going about 26mph uphill and all of a sudden my board instantly stopped into a full on break and violently threw me forward, luckily I was about to run it off. Almost felt like it rebooted or something but it engaged breaks no doubt! Now I feel horrible I dont know if it’s a setting I didnt properly input or if its a faulty Unity esc?.. Anyone else had this issue?
Sounds to me like a simple cutoff. Is your bms bypassed?
I’m using a Psychotiller built battery charge only bms connected directly to unity.
Does a cutoff mean the breaks might engage?..I was going up a steep hill full throttle & the board instantly stopped it actually skidded from the wheels locking up.
Sorry to hear this, you need to stop letting people test pilot this and be very careful until this issue is eliminated.
Have you considered for a start -
Bypassing the bms, it is a relatively simple operation & eliminates a possibility that the bms is stuttering power delivery & petgaa asoectesetting the Unity due to a problem that is not apparent under a specific load
Get a Metr or DaveGA for data logging
What unity firmware version are you running?
Hey its unity Version 2.43 and I’m using a 2.4ghz rc remote . I have not considered bypassing the bms but I am now.
Wasn’t 2.43 fw the one that was having nasty cut outs under load!? You need to upgrade to 23.44 or 23.46
Connect your unity to the Android app, check if it says firmware is too old
No that was the fix version. Makes sense to go to latest tho
Latest have been working good so far. Even with metr pro
In your photo it shows that your motor phase leads are not shrink wrapped at the joint. Possibly they could have shorted and they would cause the motor to brake. Even if it is not your problem it’s something to look at.
The exposed phase wire connections were my first guess too. High speed + lots of vibrations + one split second of phase lead contact = shorted motor, instant brakes, ride over.
Thanks for noticing that I will make sure I fix that and will check firmware to makensure its up to date. I use the UI app almost every ride and I dont ever remember it saying to upgrade.
What FW are you currently running? This is not a common issue, you should update the title if this post as it’s deceiving and could cause people to be afraid to run their Unities
FW 2.43 …I would change title but from previous comments seems as this has been an issue in the past.
"Wasn’t 2.43 fw the one that was having nasty cut outs under load!? You need to upgrade to 23.44 or 23.46
I will update fw if possible run setup and fix exposed wires to see if this resolves issue…its easy enough to test on another hill.