Tried another d100, same issue.
Wtf am i doing wrong?
I’ve tried 4 different motors, sometimes the sensors detect, sometimes they don’t. They don’t detect more often than they do.
Losing a lot of faith very quickly over here.
4 Likes
Backtrack to 5.2?
I tried that with vesc tool 3.0, the firmware won’t stick.
Need to try it with 3.01 and see if that works.
But that’s a job for another day, had to leave before i threw the whole lot through the fucking wall.
3 Likes
This is what it’s running. (Phase filters actually turned off) Note that this is one of the first ones. Not the newer slightly different hardware that you have.
Newest vesc tool.
Trying to detect the sensors was driving me mad. Led me to remake a load of sensor extensions again. Which changed nothing.
5 Likes
Great, so they’re garbage.
4 Likes
I think there may be a bug or two to work out.
4 Likes
So diplomatic 
I will continue banging my head against a wall another day.
Thankyou for your input, esteemed colleague 
4 Likes
Test the firmware archive out and report back!
2 Likes
Yes. This will require reading/learning/trying things/time with no promise that the problem will actually be resolved.
How good is esk8
3 Likes
did u try to reflash the bootloader in?
3 Likes
No. But to be perfectly honest, i’m having the exact same issue with two different units, this really isn’t my problem and i’m not convinced that any amount of fuckery will make this ESC a viable product in it’s current format.
If it doesn’t work straight out of the box, what’s the point?
6 Likes
That’s running custom firmware, so the VESC tools (3.0 or 3.1) won’t have it to update it. You’d need MakerX to send you the 5.2 firmware file or the source code to compile it.
2 Likes
Except for the first 15 D75s pre-installed with custom firmware based on the 75300. The rest of the versions use the default firmware of 100250.
Have you tried restoring the motor default parameters?
This might be a FW5.3 issue and not a D75 issue. Does what this guy just posted sound familiar?
Interestingly, I had pretty much the exact same issue when i tried FW5.2 on my trampa VESC6’s. Detection results were consistently terrible, and the only solution was to roll back to FW5.1. I’ve also heard of plenty of other folks having detection issues on FW5.2, and now FW5.3. Seems like a total coin flip whether someone will get decent detection results with newer firmware.
4 Likes
I installed plain 5.3 on my early batch D75 and I’m having significantly better results than the included firmware
@glyphiks
1 Like
I have never been quoted so many times in a row lol.
I also remember this happening to me before on another FW version a few years ago with the 6.6. I had to roll it back then to a previous version that worked. I assumed it would have been fixed by now, but I guess there are so many variations in the vesc designs that fixing something for one vesc will break something on another?
2 Likes
The firmware seems to be mostly developed for the official designs. It’s really up to the ESC manufacturers to contribute their own hardware configurations for the firmware to the VESC project rather than using a stock hardware config that’s close, but doesn’t exactly match.
Companies/ESCs like Lacroix, ZESC, TeamTriforceUK, Spintend, FOCers, etc all contribute their hardware configs to the project so their firmware is exactly what the manufacturer intended.
I think MakerX is in the process of that, and Flipsky couldn’t care less.
4 Likes
4 Likes
No, the Trampa VESC 6’s run perfectly in all situations and if they don’t then you just set it up wrong.
/frank
16 Likes