There’s definitely some very wrong values there in the protection section.
read the names. look at the values. i bet you can spot them.
you can compare to mine posted above.
2 Likes
Yeah something definitely looks wrong, that’s how it came. How can I tune it if mines a 12s8p p42a?
Your battery is set up to only charge at absolute zero, the temperature.
As far as the ESC, you should reinstall vesc tool or try a different version. It should come with firmware.
1 Like
I’m not really sure how to tune it to my 12s8p, I put your values in but obviously they are not the same for mine.
Yeah I see that for the battery, now I just have to put in the right info? I already reinstalled Vesc tool, I tried 5.3 from the precompiled Vesc tool thread and 6.06 from the website, no firmware shows up except for the archive when I download it and even then, it says that “this Vesc tool does not have the correct firmware for your hardware.”
Ya done goofed it up by flashing makerx firmware and probably by fucking around in vesc tool wizards before having fixed the firmware lol. I partially blame whoever recommended you flash makerx firmware.
Maybe a ST-Link can unfuck the fuckery? Anyone?
2 Likes
edit.
wait which hardware is in use here?
yeah one you flash the wrong firmware… the vesc tool thinks it’s different hardware… it only knows from what the firmware says it is.
2 Likes
OG single focbox
2 Likes
But that’s the weird part. His vesc tool does not show him any firmware. Usually it offers any available firmware in vesc tool whether you have the specific hardware or not.
I don’t think i have seen that behavior 
2 Likes
Yes, you need to fix all of the protection values. Fessyfoo’s battery looks like it is 12s, so most of that should work.
I don’t know how to help you with the vesc tool thing. This is what mine looks like for 6.05:
1 Like
Is it supposed to only show you the correct firmware? Maybe I should connect to something and double-check, but my recollection is that it always shows all options.
2 Likes
Yeah it doesn’t show any firmware options on any Vesc tool bc it doesn’t recognize the Frankenstein I have created 
Does anyone know how to extract the firmware .bin files from vesc tool? Couldn’t we just let him flash “custom files” aka the extracted firmware .bin from the 410/411/412?
Maybe we should check vedders firmware repo and see if he published it there
2 Likes
Sorry for making this confusing with the multitasking, but I put all of the same as fess and it still shows the same.
I guess I was wrong. I swear I’ve seen it give me all the options while connected to hardware before, but that isn’t what is happening when I connected my Solo now.
Yeah, you can find all the firmwares on github if you look hard enough. That is how I’ve gotten them when I flashed things with an STLink I’m pretty sure.
1 Like
I take no responsibility
I’m also not sure if his focbox/makerx monster expects a flashed bootloader before allowing him to flash firmware? Makerx always had that bootloader quirk
2 Likes
So I should try it but you have no liability ok 
Mines a 12s 12p board… so…
most of those BMS settings copy over fine
but I wanted you to say which ones you noticed were wrong. so you did some thinking about what they mean. 
from your video:
temps:
charge over temp … “don’t charge if it’s over -273c”… so… don’t charge. it’s never over that temp.
also… don’t charge under temp -273c… so. only charge at -273c… lol.
tho … it’s not actually giving over/under temp as a warning.
battery over voltage:
940mV is 0.94 V non sense. this is triggering your total pack voltage alarm
12s pack is 12*4.2 = 50.4v = 50400mV
battery under voltage
0mV. um. no…
12s pack 12 * 3.0 = 36V = 36000mV (3.0v/cell is conservative.)
Cell over voltage:
0mV … nonsense. this is triggering your cell over voltage alarm.
over 4.2v for lion considered bad. usually set to 4.25V 4250 mV
cell under voltage:
55471mV 55V ??? nonsense.
every cell is going to be under 4.2v usually.
set to 3v to be conservative. 3000mv
Charge over current
29200 mA 29.2A ??? bonkers.
you’re not charging that fast. set it to something slighly above what you normally charge at.
Discharge overcurrent
ideally you’re bipassing discharge BMS in a skateboard, and leaving that to the ESC settings.
but… 410mA would also immediately trigge.
IDK how you got a unit with such scrambled numbers.
but set them all up better, then take clear screen shots of the whole config, and get someone to say LGTM.
the Release condition numbers. Thse are the values that will clear an alarm once it has been triggered. They’re usually just a small percentage off of the trigger condition.
3 Likes
It’s an option. Maybe let others chime in before doing anything.
@Evwan sorry to drag you into this but maybe you know what’s best.
Lemme know if you need context or if the above is enough
1 Like
I’m not sure I’m following which things are which.
but I think we’re saying he flashed go-foc dvs4 firmware onto a non go-foc dv4s esc.
if this is the case, I think vesc tool will see it as that hardware after that. because it’s just a field in the firmware to say what hardware you are, not actually hardware being identified.
does go-foc dv4s have it’s firmware distributed with vesc-tool? I note they have the separate download page and if it’s not distributed with vesc tool, that would be why it’s not showing up now that vesc tool thinks it’s talking to a go-foc dv4s
1 Like