@JesseM has had a ubox fire too
2 Likes
Fuk yeah i did… hit motor detection, and then it did the big woof
3 Likes
I haven’t seen reports of issues since they cleared up the firmware mess to be honest.
From what I gathered VESCTool showed the default firmware as applicable/uploadable when it should not have… which caused some of the issues we’ve seen.
2 Likes
Oof, that brings us to double digits. Will I link this post here as the reference or did you post elsewhere that I didn’t find? Hope you didn’t have anything else burn up as a result, also cheers @glyphiks
2 Likes
Ah ok, do you know roughly when that was? There are posts reporting fire at least as recently as November of this year, could be outdated VESC tool but it’s still causing issues, and if a device needs custom firmware to the extent it’ll catch fire it’s still a problem
1 Like
I had 2 UBOX fires in March/April, running 18s. One fire during the first 5km of riding, the second fire in motor detection after they sent a replacement . For me it was a case of being a guinea pig stuck in the firmware mess in the early stages, but I haven’t heard of many issues recently since they have sorted the firmware out and have released specific instructions for setting up.
6 Likes
VESC is also a software project. This thread is about hardware.
A certain vendor has been trying to create confusion in this space by borrowing the name.
2 Likes
HAHAHA last night i updated back to 6.0 firmware the ubox no longer connects to vesc tool by any method and the red leds are now having a disco rave anytime you turn the thing on.
1 Like
has Spintend released their 6.0 firmware?
2 Likes
it’s officially part of vesc tool. please do not down load it, for me atleast it was very buggy and bricked my ubox
2 Likes
Spintend controllers have to use their custom firmware or you risk popping on detection. I don’t think they’ve released their custom 6.0 version yet, I haven’t heard anything about it.
I would switch back to 5.2/5.3, you can find the firmware files on Spintend’s website
2 Likes
Yeah personally I’m in the “write the firmware once and leave it tf alone” camp, which feels strange to admit for some reason. It seems like new FW features often/usually require new HW, like HFI and a full setup of phase shunt filters. Maybe I just haven’t had enough time or combinations of gear to have encountered big feature or performance increases though
1 Like
Yeah, same here. I was hesitant to even switch to 5.3, but luckily haven’t had any issues yet.
Been hearing a few horror stories regarding 6.0 firmware, so definitely holding off for a while
1 Like
i was the one who told them to put a warning on there website about that.
they literally did a pull request. i even emailed them and they confirmed it
and when i say it bricked it, i mean it has royally fucked it as it can’t even be detected by an st-link and it constantly flashes red
Did you manage to unfuck it with a bootloader reflash or is it still borked?
Have you tried shouting at it yet?
Must be something wrong with h/w now if you can’t swd
1 Like
still fucked
it has heard some colourful language
and yeah thats what me an jaykup think, but i can’t find my multimeter to poke around with it
2 Likes
f 
on the bright side, at least it’s not the fiery kind of hardware problem
2 Likes
The thread name being “100v dual ubox fire” gives the incorrect impression that most of the issues are the 100v version.
It looks like it’s really the 75/300 version that is fire prone. I’m not sure the 100/250 100v ubox deserves a firey reputation, or if it’s just an unfortunate association with the 75v version. Maker x seemed to see more exploding escs on the D series when they were on 75/300, before they switched to 100/250.
@jaykup any thoughts on explodyness of 75/300 vs 100/250 designs?
OP - 100v
@Skyart - 75v
@BigBen - 75v
@Pickled_Monkey - 75v
@whaddys - 75v
@Tasventouras - 100v (post says says: case of being a guinea pig stuck in the firmware mess in the early stages)
@Halbj613 - 75v
@Katarsis - 75v
Reddit user - 75v (admits to using wrong firmware)
Ubox single - 75v
@JesseM - 75v
6 Likes
75v here
1 Like