You think they have inferior bits in the cheaper?
My flipsky version with ur firmware has been rocking!
This is max current up a hill. Why does it only do 60 amps even though set to 200 motor and 140 battery? The motor starts to magnetically saturate at 60 anyway … does the esc know there’s no point in supplying more amps?
Glad to hear! We recently found out that the 75200 is pretty noisy in terms of current and back EMF measurements due to a poor hardware design (op amps running off 5v instead of 3.3v). But the 75100 alu doesn’t have these issues and seems to work pretty well.
There could be some soft limits activating (voltage cut-off, thermals, erpm/duty start limit), current measurement noise, or just simply not enough load. If you can send me the full log as well as your settings (file → save motor config xml) I can take a look.
You can also try applying the brakes while going uphill to increase the load and see if you get more amps.
Maybe. I did a saturation test on a 63100 and ran it up to 230A. Efficiency slowly dropped, but I never found the point where torque just fell off a cliff. It must need a lot more amps before it hits that point.
The VESC firmware doesn’t currently have anything like this. It will happily supply as many amps as will flow through the ESC.
It’s only 45kv and magnetically saturates at maybe only 60 amps if even that. So the esc is overkill with its amp ability.
So sorry for the bump but i wonder if anyone bought and checked the MKS 75100/200 Alu PCB and compared them to the Flipsky’s? like component etc wise? the 75200 Alu is at ~150 which means i could probably get it into my country without getting wrecked by VAT & customs and i would enjoy the extra torque 
Ok thank you, i just wondered cause of the price difference if they maybe used worse caps etc
The caps certainly are different, I guess the MKS one since the Flipsky uses richcap in the 75200 alu, and the MKS use ymin (same brand as in the FSESC 75100 Alu PCB) altho i don’t know which is actually better lol
There are a few differences between the MakerBase 75200 and the Flipsky one.
The 75100 of both models uses 3x INA181 current sense amps which seems to work fairly well.
The 75200 they went with a quad op amp instead of 3 current sense amps.
The MakerBase one uses the SGM8584 while the Flipsky version uses the SGM8634. It’s unclear if this was a change batch to batch, an attempt to fix something, part availability, or something MakerBase does different.
What was clear is the fact that the noise at lower RPMs is pretty bad. Specifically the back emf readings that the STM32 sees.
There is a long thread on it on the VESC discord, but in the end the wave forms on an inrunner motor looked like this with either the shipped firmware or the firmware in this thread
Compare this to something like the Stormcore 100D (DRV8353RS)
Or the SKP Solo (op amps)
and it’s pretty obvious things aren’t right
This mod was made where jruncorn unsoldered the 5v power into the op amp, bent it up, and connected it to the 3.3v rail.
Which made the wave form look like this:
Then Elwin hacked modified the firmware further to average the currents together which made it run really smooth, but it’s not well tested and there may be some drawbacks
The code difference can be seen here (not incorporated into this firmware)
And here was the motor all this was run on. It’s a fairly beefy 8 pole 4kg inrunner
I don’t know if the Flipsky 75200 performs the same, and a lot of people report both versions of this ESC running fine on ebikes and scooters, so depending on the motor or use case, it may be fine for the price… but it’s certainly not the best ESC out there.
Both versions also have this problem where the caps near the inductor for the buck are rubbing on the top case and will probably short out at some point.
(from this video)
i have the makerbase 75100 from AliExpress, got it on black Friday i think for around $50-60. still trying to work the kinks out of it… have it installed in ninebot snsc 2.0 (max g30p) powered by 13s3p but under load it stutters and bucks. i don’t know which way to go with setting it up. oh yeh i forgot to mention it’s running your firmware for the blue board version jaykup.
We can only hope that they’ll add phase filters and INA241’s (110-120V survivability, the 240s were 80V max) in the next iteration of the 100V whatever current models
edit: i don’t see an edit button, so well uh, ina241’s for Phase shunts rather than low side
to add on that, the ina181’s don’t have pwm rejection like the ina24x series, my guess is that there’s also a cause of the noise
@jaykup , any updates on that? I’ve been using this Makerbase 75200 with your firmware. and It’s really jerk an noisy at low sleeps…(the original firmware felt very similar) It can handle 200A with 16S, with no warm up, but the sound it terrible. I’m using 2 harley style hub motors… the MKBASE 75200 can handle the amps, but doesn’t work for my application. I also have some UBOX 75200 v1, they are ultra smooth with those motors, but I felt it was risk running it with more than 110A.
I mean, do you believe this hack worth the risk?, or do you know where I can find more info on it?
You are welcome to use it, but I haven’t tested this beyond a few spin ups. There is some concern at high duty cycles that it may be an issue.
This is basically the firmware in the first post, but removes the average current from each of the sensors to get rid of the noise.
Source code is in the github link above
fsesc_75_200_alu_sample2.bin (512.0 KB)
I will try it today. I will keep a current limit of 100A when I go over 50% duty cycle, and see how it goes. thanks! the source on github you mean the korjaa changes or your link on the top?
Both. The hw_fsesc_75_200_alu .h and .c files in the first post along with the changes to the mc_interface.c and mcpwm_foc.c listed in the korjaa github link. He was following along in the discord thread and created that github branch, while I was just modifying the code directly and compiling to see if the changes would even work.
With some more testing this could be merged with the main project, but it’s still experimental at this point
heres the results, night and day. Amazing.
default firmware
The sample firmware posted above. this is after motor and hall detection only and zero tweaking yet, other than flux linkage, as detection set it at 100mwb for some reason. i set it at 21mwb and here is the result. keep in mind i had the samples set a bit high so it looks rougher than it would normally, i didnt feel like re recording another run.
the 75100 in my m365 using sensorless bldc sounds like an f1 car… wtf 
Hello guys and thank you for your work. I have two 75100 v1 in laotie es10p and 1 75100 V2 on xiaomi. What firmware you recoments I have 6.02 but battery is not reading right also the motor test is giving bad readings. Any idea?
I can’t get the same detection results twice with mine when I ran through the foc wizard with my ninebot max and a xiaomi m365… but atleast it sounds cool. 
What readings are you getting that are bad?
For scooter/ebike hub motors the 2kg outrunner setting in the motor wizard works pretty well
