Other phones are so full of security holes, you can use them as a sieve. Not interested.
I hooked up an older Unity today and flashed the new firmware with the vesc tool.
I did it using the PC and it was quick and I just worked…
I then unplugged the PC and ran the wizard off my phone like I usually do…
First pass I got some weird different values for the motors and one said unsensored…
So I shook some wires and ran it again and everything seemed normal.
Did ten miles on new build and it all seemed good.
Oh. And push to start is freaking cool.
I will just copy my question here, since I am on last fw, and @Deodand is pretty active here
last few rides my mosfet temperature is constantly 24.9 degrees C, both in vesc app and in logs. I know for a fact that is not possible because my heatsink was hot after today’s ride. I’m running my focboxes on 13s (80A bat, 120A motor each). Should I be prepared for burned focboxes or is that problem nothing to worry about? I can always connect bt module to second focbox, but I would not like to get my controller dead during ride. Halp
EDIT - reistalled latest fw, still no temperature reading. moved bt module to other focbox and I am getting readings now. but I still didn’t solve my problem and I am still scared.
80A per esc? That seems kinda high without a large heatsink and access to air
One of these in combination with a cutout in the enclosure would be perfect
I do have 3dservisas esc enclosure, so yeah, there is big enough heatsink on open air. Usually it gets warm, yesterday it was hot (long uphill rides).
I am not getting mosfet temp readings for last few days and I am failing to see reason for that.
Downgrade to a known good version and see if they come back
To add on to this, @deodand, can you explain in layman’s terms what setting duty cycle to 85% is doing?
Is it limiting my top speed to 85% or only smoothing duty cycle past that point?
Once you go past 85% it will begin to gradually ramp the power down. As you approach the 95% limit you will have almost no power. Its not limiting you to 85% duty but just reducing power past that point so that you don’t abruptly hit the hard limit at 95%.
I hate to be the one to break this to ya, but the iPhone is the DHS wet dream.
I’d hate to know what they call Android then.
The answer: Difficult to crack when a quality phone is properly setup.
Updated my unity from R2.1 to test this new firmware 5.2 (6d old)
My flipsky vx 2 remote is not reporting speeds anymore unless i put it on FSESC mode on the remote (Use to be Focbox mode to make it work with unity). -->UART changes ?
The motor temperature sensors are giving weird values. (I’m sure the hardware is fine as it worked on firmware 23.46) both displaying minus 89-90*C
I left the temperature sensors settings as is. (NTC 10k @25*C) 3380 beta
And as you can guess, the temp is pretty important on these hubs
makes sense since your not using unity firmware anymore
could be wrong but thats part of vesc firmware
It appeared to me that he was trying to fix that in this test-version which is newer as release
Alright had some… fun… testing today.
I set both motors duty cycle to 85% after having some full throttle weirdness.
Everything was working OK but the power was underwhelming compared to my previous firmware.
I bumped it up to 90% and had a bit more power in the acceleration. I hesitantly hit the full throttle to see if the motor wiggle/oscillation was still present and WHAM street face. Full brakes.
I got up, checked for fault codes and got nothing.
I checked for the other side of the esc and got no faults as well.
I propped the board up and got this result when throttling under no load.
Although I swear when I crashed, both motors locked up. I’ve had one side lock up before and this was not it. This was a full rug pulled out underneath you kinda deal. I noticed my right belt is halfway snapped now.
I dropped duty cycle on both motors back to 85% and tested again:
Seemed normal but still jolted, I limped home. Braking is super weird like it’s trying to do a smart reverse even though I turned that off.
This is what happens when I brake at full stop and move the board with my foot.
I noticed my right belt is half way snapped,
Bloody photos will be in the NSFW thread 
That’s no bueno, you good?
Sounds familiar, check your phase wires. I found location of my problem by running foc_openloop command on high current and heatshrink tube on one of the motor connectors started melting.
If they bumped eachother it would do that certainly but the fact that I could repeat the cutout seems off. Plus I rode it very slowly home and had no cutouts after dropping the duty cycle back.



