ntf module is definitely supposed to go to 3.3v not 5v, correct? cause the hm10 I always ran at 5v
I also tried both voltages 
They ended up cut off and back in the drawer – while the ESCs are out shredding the gnar on the streets. With USB plugs sticking out of the enclosure. In little tiny bags.
1 Like
if you try to connect the VESC to the computer using USB, is it able to be connected in the computer?
Or it acts as if no USB is connected?
connecting to computer via usb is fine, no issues there
1 Like
That’s odd, different situation as mine…
Mine was bricked so it doesn’t work on both BLE and USB…
Managed to unbrick mine using SWD prog 
obviously i should stop at this point, but id really like to test and report back, so heres my questions:
is this true ? what if my pc for whatever reason crashes during that time?
to me it seems that i need an STLINK debugger before daring to attempt updating (dont have another unity or focbox available, only 2 ancient raptor 1 enertion esc’s) - to be safe
since im a bit clueless should i stop right now ? 
It was true for me. Going from 23.46 to 5.0 beta took around 3 hours IIRC. This is on a Unity, and after that first time, it took like a minute for subsequent upgrades.
1 Like
I made the upgrade on my unity using usb from stock firmware and it took ~2min. Running in sensored foc and so far everything is working properly
5 Likes
Upgraded to the latest FW, will test tomorrow. Detection worked as per v2020-03-22v2, and I could access both VESC IDs to do the setup.
Did a bench test to see that HFI worked on both and we’re good, I’ll do an onboard test tomorrow morning on my commute. Thanks @Deodand!
3 Likes
I have a questions regarding the battery current limits with the unity. you can now configure this per motor/can id. Am I supposed to enter half the values my battery is able to put out or the full amount? So lets say my battery can handle 60/-9: should i enter 30/-4.5 per motor or 60/-9?
1 Like
Any chance we might see field weakening support in the future (any insider/behind the scenes development going on)? I’ve been reading the pull request thread on GitHub and last update was from a few weeks ago… It looks to me like the people working on it are intending to use it for electric car motors or something, and I’d love to know if this ever was implemented if it would be a viable way to increase 10S battery speeds closer to 12S with our electric skateboard VESCs and motors?
Besides HFI, this is the one feature I am most excited about, but seeing as it’s been worked on for almost a year in not holding my breath…
2 Likes
So I’m having some wired behaviour in my unity. I just rebuilt my board to see if I could verify that my sensors were working correctly. Also added some extra cable length between battery and unity in preparation for moving to top mount battery.
After the rebuilt and redid motor setup, I keep getting abs_overcurent faults and drv faults with the “no drv8301 faults” code. Seems to be happening with both motors which is making me think it’s probably not a hardware problem. Any ideas?
In currently still on 22/3 so Might try updating to the latest build.
1 Like
Ok so I keep getting firmware upload timeouts when trying to update from the newest Android app.
1 Like
Did you double check all your battery and phase connections, as well as the solder pads to make sure there are no cold solder joints or lifted pads, and scan over your DRV for anything obvious looking off?
Ok so used the windows tool and updated to beta3, ran motor and input Wizard. Everything good. Seems to be back to normal. Going for a cautious ride to test.
2 Likes
beta 3 of the unity fw?
Yeah, think that’s what is called. The current latest. Defenatly some sort of software gremlins.
Before the update it was throwing abs_overcurrent faults in the bench, After the update everything seems fine. Went on a long hard ride and didn’t have any issues.
Only thing I can think they may have caused this was doing the motor and sensor calibrations from Metr @rpasichnyk any ideas?
1 Like
Battery you config the total you’ll draw out of it, and motor you config the total you’ll put into each motor. You do both twice. So if your battery can handle 60/-9 you should enter that per VESC ID.
2 Likes
You would have noticed that the Absolute Maximum Current was 400A by default, this was intentional after I reported this behaviour below. Now the Unity hardware handles those instead of the FW, hence why you don’t see the overcurrent fault anymore.
nah this is not that, i was getting over current faults whilst running motors unloaded on the desk, metr logs show no more than 6 amps yet still getting over-current faults.
1 Like