FOCBOX UNITY | Support, Setup & Troubleshooting

Gerrycorrado · May 24, 2019, 8:28am

Updated the app but According to the change log, no bug fixes? Issue is still there then @Deodand?

Toughook · May 24, 2019, 8:51am

Report Back :

Still alive. First full test after new firmware and so far so good. 10s5p on dual belt 6374 / 107mm. I have to say that this is the first time I’ve ever ridden my main board in FOC having opted for kick-push-to-go BLDC when I had Focboxs CAN inside. Forgive my enthusiasm here, since most of you run FOC anyways, but OMG what a difference. Standing starts, silent running, butter smooth throttle and decent brakes. OK I took it easy and didn’t push any limits (on a busy industrial estate during the day) but this thing just handled amzingly. It was like a 100% new board, and if it didn’t look the same on the outside then I would swear it wasn’t my build

I tried to replicate the stutters I’d had previously, doing the same low speed throttle then coast then throttle routine and as far as I can tell it’s gone away now. Need more miles to confirm of course, but given it was doing it all the time before, and isn’t now, things are looking good.

Still in a slight state of shock at how good my board is now - and I thought it was pretty amazing before - so I’m off for a lie down in my office…

McErono · May 24, 2019, 11:03am

Still 23.43 here in EU region, last update April 14.

rey8801 · May 24, 2019, 11:04am

I am in Belgium and got the 23.44. check on Google Play

Gerrycorrado · May 24, 2019, 11:17am

23.44 but changes mentioned on google store do not mention bug fixes…

McErono · May 24, 2019, 11:51am

Just updated! Maybe there was just a slight delay in the Swiss playstore.

Going to test this tonight as Jeff thinks thats the reason for my cutouts from standstill.

Added an advanced motor settings window for tuning pwm freq, sensorless erpm transition for boards with hall sensors

Toughook · May 24, 2019, 12:10pm

I agree that they should state ‘bug fixes’ but I suspect in doing so they would then incriminate themselves and accept that the unit was ‘faulty’ in the first place. I’m no legal expert, it’s just a hunch, but I reckon they would argue they are ‘improving’ things rather than fixing them.

Either way, my unity works better after the update. For the moment, at least, I’m happy with the update.

murloc992 · May 24, 2019, 12:11pm

They would add fuel to a lawsuit that could come up if hurt people unite(haha, unity).

Gerrycorrado · May 24, 2019, 12:38pm

Euh, deo already posted they found an issue, so that’s too late…

Gamer43 · May 24, 2019, 3:41pm

Is the switchover a hard switchover? Or does it run the observer for a bit and waits until the sensored and sensorless speed estimators agree on a value before making the switch? If not, does the switchover have hysteresis?

Deodand · May 24, 2019, 4:38pm

@Gerrycorrado Look at the firmware changelog not the app changelog.

@Gamer43 it’s coded by vedder, the estimator is always running and then whenever the rpms cross the threshold (plus some added hyst) the halls are used to add a correction to the estimation.

Look at line 2844 of this file if you wanna see implementation of hall correction, it’s pretty fun:

github.com

vedderb/bldc/blob/master/mcpwm_foc.c

/*
	Copyright 2016 - 2020 Benjamin Vedder	[email protected]

	This file is part of the VESC firmware.

	The VESC firmware is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    The VESC firmware is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.
    */

#ifndef _GNU_SOURCE

This file has been truncated. show original

epss4 · May 25, 2019, 2:05am

So i just did the new firmware update but now it look like it don’t detect sensor from one motor … it was fine before the update !! And both motor seem to roll perfectly fine like if they were sensored…i did re install the unity app and reflash the new firmware but nothing’s change …is it possible that the update make this ? @Deodand

Gerrycorrado · May 25, 2019, 10:02am

@Deodand can you still pretty please let me know with what setup you have tested? Thx

anon26002665 · May 25, 2019, 11:07am

Bajaboards do it with straps, seems to work

banjaxxed · May 25, 2019, 11:23am

Looks ok, they even have a quasi rider weight simulation built in using those tie-downs, all very rudimentary for checks. A better one in the factory he says.

The point being is you can test a wide range of load/power on a bench which is essential when QA’ing controller software. You can’t just go for a ride and expect what you experience to cover all use cases. Multiple test mules with differing hardware which can be dropped onto a jig is the way to go, probably even just a truck mule with the exception of a 4wd or two

McErono · May 25, 2019, 11:41am

My TBDD sensors are fine after the update but I couln’t test… raining again. Worst May ever…

epss4 · May 25, 2019, 12:52pm

One of my sensor wasn’t connect properly… thanks anyway man

Gerrycorrado · May 25, 2019, 8:46pm

So, can we get some test results from real people then?

Yes, tested and all ok
Yes, tested. Still an issue (please comment)
No, haven’t tested yet

0 voters

Thx

Venom121212 · May 25, 2019, 9:25pm

I think this is a great idea but belongs in a separate thread as the top post so it doesn’t get buried. I can make one if you like or you can. Make sure FW version tested is in the title if you make it.

murloc992 · May 25, 2019, 9:26pm

I think this is just for the newest firmware. We would have a literal ton of threads every update. Let it be here I guess and bookmark it?