I accidentaly flashed a wrong firmware on my FocBox and, without noticing the mistake, I made FOC motor detection, there was magic smoke right after that and my DRV chip is tosted.
I wonder if someone had this happening before?, if an incorrect firmware could cause this to happen or if the error could come from a shorted motor.
Yep, definitely from the wrong f/w. Installed f/w for hardware version 48 once and same thing happened during detection. Luckily there was a fuse that prevented the VESC from killing itself.
Sorry for reviving an old thread.
I have a raptor 2 and I connected the focbox to focbox unity ui and updated it.
Now I know that focbox and focbox unity are two completely different things (it’s really confusing)
Anyway, I don’t believe anything burnt, how do I return to the old firmware? Do I really need a programmer? Enertions bldc tool won’t connect,(saying version too old) but focbox unity connects fine.
What is the hw version?
You need to get a STLINK usb programmer. If the boot loader no longer works, allowing you to reprogram the f/w, then this is the only way to access the h/w
If you are using the Unity s/w against an older model Focbox, you are doing it wrong.
I would first try using the vesc tool and see if you can connect & flash it with a stock f/w, then go from there.
Do not willy-nilly use and VESC-type software and randomly select a firmware to upload or you’ll hit this type of problem, it might be clear that lesson has already been learned.
Is the st-link for firmware also or only bootloader?
I am still not sure what to do, as you can see in above screenshot, it’s detecting fw 23.44 on the focbox which is completely wrong. I upload a screenshot successfully but it’s still detecting fw 23.44 when I power cycle