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.
1 Like
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
1 Like
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
1 Like
@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?
1 Like
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)
4 Likes
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?
2 Likes
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.
1 Like
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?
1 Like
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
1 Like
the resistance and inductance detection values go up and down and all around. under load trying to ride it just for shits and giggles in sensored foc it stutters nd bucks like hell but sensored bldc runs like a MFer.
hardware is makerbase 75100v2 box with the fw 6.0 from the top of this thread.
here’s what it’s running…
1 Like
Can you take some screenshots of the motor detection using the 2kg outrunner and any other settings you change after reseting defaults. Does it detect halls and it’s running with those at low rpms?
Do you have the ability to measure motor resistance and inductance manually to compare?
If the detected values are bad it won’t run FOC right. You can also do manual detections on the FOC tab and play with current / time constants to see if you get something that works.
Flipsky 75100 v1 and makerbase 75100 v1 with oficial 6.02 no limit I tried the limited version also this is the result with laotie es10p motor 1000w 52v (motor with no halls) and this are the results with same motores same controller but with 75300_r2 firmware how can it be? Witch firmware should I use?
2 Likes
i keep getting these transient under voltage and over current faults, went through all my connection points and wiring thoroughly but it’s legit.
1 Like
Anyone had any luck with AS5047P on a 75100v2 over SPI? Connecting to the hall lines I get nothing except induced noise on my analyzer, it doesn’t seem to pull hall3 low for CS. I saw another post about there being caps on some flipsky hall inputs that break SPI, but I can’t see the same layout on the PCB for the 75100.
I tried using the hardware SPI port too but I can’t figure out how/if that’s exposed on the port. It looks like the 75300 is meant to expose this on the COMM port using RX for CS, ADC2 for MISO and ADC1 for SCK, but that doesn’t look right for the hwconf which has CS on A4 rather than shared with RX1 on B11… So I’m not sure the hardware SPI is actually fully exposed on the 75100 at all? Or possible it’s misconfigured away from the I2C/UART pins, since the trampa 75300 hwdef also seems to mismatch the SPI labels on the case…
I suspect I should be trying to use soft SPI, but if caps need removing maybe it’s easier to recompile the soft SPI to use something other than the hall pins if they have pullups or caps that interfere with SPI… I’m only otherwise using the CAN interface so I could detach the UARTs or I2C if I had to…
Help appreciated!