With the D100S am I supposed to run 6.2 firmware? It shipped with 5.3
And am I supposed to have phase filtering on or off?
David recommends 5.3. And yes it has phase filters
1 Like
Has anyone tried 200A per side on the D100S yet?
Iām running 6.2 because I need sHFI. it works great.
+1 for what Sug said, phase filters on (advised by David)
1 Like
Only managed to get up to 155A per motor. My motors get too hot any higher haha
1 Like
If anyone is wonderingā¦ Yes it can actually do 200A per side
For heavy racing it would probably have cooling issues without an efficient external heatsink though
6 Likes
Which motors?
1 Like
6495 v6 reachers 175KV
3 Likes
How long a wait are peeps getting when waiting for email reply from maker x support im 7 days NO reply 
1 Like
PM U
Legend Again for helping me Thank you for your time Robbie. 
1 Like
Finally connected the ESC I order a few months back to my battery (charged to 37V).
Bluetooth module not lighting up. No leds on the DV4 blinking. No connection seemingly via USB. Seems completely DOA or am I missing something?
@YUTW123
Edit: Nevermind I am fucking dumb. I had not connected the switch which I though was disabled by default.
1 Like
Any plans to support firmware 6.05?
OK, either Iām being dumb or the D100s hardware/firmware is sampling current really badly. Finally got around to setting up my sat-on-a-shelf-a-year D100s (Shipped like 9/3/2023) Friday. Plugged in, flashed bootloader followed by 6.02 firmware on each side via USB one at a time, ran motor detection, ran remote setup, (Hoyt Puck), hooked up Metr via CAN. Set up the usual settings like power timeout settings, etcā¦ as documented in this thread. Set up V0 45 degree silent HFI, bumped phase current to 120A per motor forward, -80A backward. (-120A backward was WAY too strong and almost threw me) (Reacher 6385 V5 motors, sensorless as halls in one motor are fried and I couldnāt remember which motor had the problem and didnāt want to risk killing anything in a brand new ESC)
OK, so hereās the issue now: Friday I rode for like 20-30 miles, HARD acceleration, braking, whatever, worked great. Only complaint was on occasion the board would fail to start up; I chalked it up to running fully sensorless with HFI and the controller not exactly finding perfect timing every time.
Today, I hopped back on the board and started a ride. Got 2 blocks, and the board accelerated REALLY slowly. No idea what happened, but I gave it more throttle and it accelerated conservatively through an intersection. And then without warning shot out from underneath me. Ripped open my motorcycle jacket at the elbow, etcā¦ Iām only bruised and scraped, but something is VERY wrong.
Lifting the board off the ground and playing with the remote, the right side stops responding pretty frequently.
Relevant settings:
- Battery amps: Ā±80A
- Phase amps: +120/-80A
- Absolute maximum current: 250A, also tried 350A
- Phase filters are ON (website indicates this is implemented correctly unlike the D60-70-100 non-S models previously)
When I can get the right side ESC to fail, (stop responding to remote input), I appear to be getting ABS_OVER_CURRENT errors. Only on the right ESC. Bumping max current to 350 causes the same error according to my METR, except instead of at like 260-270A it registers at 350A.
Video uploaded with behavior:
Iāll note that my Metr wouldnāt read both ESCās when I first started the ride. It does read both now, but didnāt at the beginning; was trying to detect one of the two ESCās continually. No idea why, it was always rock-solid on my D60 before my halls blew and mangled that unit last year. (Metr is 24/7 on, ESC gets disconnected from battery for charging)
I know the CAN transcievers are still functional for a number of reasons including that the two ESCās do still talk to each other enough to respond to throttle input.
So first questions:
- Why is this ONLY occurring on one side?
- Why am I hitting the current limit, regardless of what itās set to?
- Why is current measurement spiking to such high levels?
- What can I do to data-log this behavior in VESC Tool to identify the actual source of the problem? Clearly one of the ESCās is reading current measurements with transient spikes that are HUGE. Letās figure out why.
- As far as current shunts - Are the phase shunts only on the n-fet sides for each phase? Any other shunts for measuring power input or is that calculated in software somehow?
- Is the use of these incredibly low resistance DirectFETās inducing weird unsuppressed transients or oscillations that are throwing off measurements? Can this be filtered somehow if thatās what youāre fighting?
I have a thermal camera and Iāll be opening up the controller to look for indications of unusual component behavior if nothing else points me in the right direction. For now, I canāt trust this ESC to operate reliably and Iām highly motivated to find the problem.
If it helps, hereās my Metr accounting of the ride and incident:
Ride
And logs:
log_2024-07-02.txt (2.3 MB)
2 Likes
I thought MakerX advised to set phase filter OFF with this ESC.
It was correct custom firmware?
No v6.03 here :
With custom 6.02 FW I have many ABS_OVER_CURRENT errors on one side, as explained here :
They disappeared setting Absolute Maximum Current to 400A and removing useless traction control.
But Iāve never had such a terrible behaviour.
1 Like
Sorry, typo; 6.02 from the website. Never had any issues like this with my old D60 on 6.02 with phase filters off.
āPhase filters: yesā is listed on the website for the D100S
The thing that doesnāt make any sense here is the 400A current limit; there is no way the ESC is handling 400A; there has to be some sort of noise or transient happening to cause those readings. I was getting 350A+ overcurrent errors with fully unloaded motors. How is this possible? Why is this only happening on one of the two ESCās if both are using the same current limits? This by the way is with the Metr registering like 25A phase current
2 Likes
Try turning off the duty cycle current limit start ļ¼
Restore all parameters to defaults and then do FOC configuration again.
1 Like
Before I start making changes, whatās the best way for me to datalog straight off the VESC to see what the readings look like when I get it to fail? I thought about it for a while and the Metr may not log fast enough to catch instantaneous current spikes; regardless of whatever noise might be present, if the readings are reaching that high, it has to be for milliseconds or something or else Iām pretty sure the controller would have blown up by now. The Vesc native datalogging capabilities may be faster and allow us to get a better picture of what is happening.
Iāll try that in the morning; Any thoughts about support for firmware 6.05 yet?
Current limit start set to 100%, also enabled high current sampling mode; as a previous post suggested turning off Slow ABS Current Limit, that is actually already off with firmware defaults. Re-detection appears to be performing more reliably, however I also have my current settings left at detection defaults - Ā±90A phase, -+80A battery, absolute max current at 135A. I also have my Metr unplugged from CAN to eliminate variables. Iāll probably charge up and ride tomorrow after I tape up my jacket enough to keep the armor in place.
Also - Turned on high current sampling mode on both sides of the D100S; not sure I see a difference, but seems like a reasonable thing to do considering the currents Iām running.