QS268 Hub Motor Shuts Off When Accelerating

[tedo]

UPDATE:

Installed the firmware update SiA sent me. Things are worse now but at least get error codes. I think SiA tech support is about to ghost me and block my number.

15 MOE current protect

The only thing I can find consistent is the controller or motor or whatever is bad knows when I am far from house and starts acting up. Maybe the Chinese balloons are tracking me.

For the first 6 miles or so it runs perfect. Hitting potholes or whatever. Once the motor gets to about 49 degrees AND I am far from my house, it goes to shit. If I do a drag race takeoff I can get it to kick off also.

I have 2 screen recordings. The 9 sec one is a drag race takeoff and the 13 sec one is it just acting up while I try and take off from a dead stop.

Both times I get 15. MOE and WEAK.

 

[tedo]

I don't think my screen recordings loaded. Here are screen shots of the failure. These screenshots are 1 video frame apart

 

[dominik h]

What phase current have you set?

I had an error which also showed me "weak" with no load. It was when my BMS has shut the battery off and regen was activated.

I never had an moe error, and I have no description what that means.

I had Support from fardriver. It took a few weeks, but then I had a technican in a video call , for hours on two days.

You can turn off moe errors in the app, but i don't think this is a good idea without knowing what exactly happends

 

[tedo]

I think

What phase current have you set?

I had an error which also showed me "weak" with no load. It was when my BMS has shut the battery off and regen was activated.

I never had an moe error, and I have no description what that means.

I had Support from fardriver. It took a few weeks, but then I had a technican in a video call , for hours on two days.

You can turn off moe errors in the app, but i don't think this is a good ideal without knowing what exactly happends

What is happening is that I think I have a battery with 400mps max line and 640 peak for 10 seconds according to Amorge. What I actually have is a battery of 400 max and at 410 it will self protect or over 400 for 5 seconds it will self protect. The Fardriver is doing its job and letting me know this with the 15MOE code.

I am going to pretend I have an absolute max 400 line amps battery and set my max limits accordingly. I will see if this solves the issue.

 

[dominik h]

Probably you can change the overdischarge protect to 10 seconds.
I'm only able to pull 400A for 6 seconds, but I reduce power from 100kph linear to 125kph.

 

[dominik h]

Just made a run with around 75% SOC , 450bA and 1500pA.
Battery is still to cold, voltag sag is 9V.
At the moment I can't save parameters anymore. Software tells me "slave controller" and I can not log in anymore.
I also ordered a bigger BMS. I hope I find a place for it in the scooter.

 

[tedo]

Probably you can change the overdischarge protect to 10 seconds.
I'm only able to pull 400A for 6 seconds, but I reduce power from 100kph linear to 125kph.

Im not going to start throwing BMS adjustments on top of this. It is a faulty controller or motor. I just don't know which one. Trying to decide if I should cut my losses on this project or keep spending money. About to throw in the towel and be done with it.

 

[Chalo]

Im not going to start throwing BMS adjustments on top of this. It is a faulty controller or motor.

By what mechanism do you propose the problem could be the motor? Bad plug, bad cable?

 

[n00b]

Yeah, I don't know much about the Fardriver app, but it doesn't seem like that's the case. The only thing different between the screenshots is the throttle value, yet it doesn't show any throttle errors either. Maybe it detects an intermittent throttle fault, which clears itself but the controller requires a restart anyway?

This thing handles that much amps and power?

 

[tedo]

By what mechanism do you propose the problem could be the motor? Bad plug, bad cable?

If I knew that I wouldn't be on here crying like a baby to you guys. LOL. The only consistent thing is when temperature is around 48 or over and anything upsets the wheel like a crack in the road or putting the brakes on etc.. the motor shuts off. That says motor fault. However, after 8 seconds of no spinning the motor works again. That seems like controller. I can ride this on supercross whoops without it cutting off as long as the temp is below 48. I have done a lot a wire jiggling of course, but a loose wire wouldn't have a certain temperature and 8 second delay every time.

 

[tedo]

Yeah, I don't know much about the Fardriver app, but it doesn't seem like that's the case. The only thing different between the screenshots is the throttle value, yet it doesn't show any throttle errors either. Maybe it detects an intermittent throttle fault, which clears itself but the controller requires a restart a

Throttle values look the same to me. Its pinned and the motor is running. Then its pinned and the motor stops drawing amps. On the last 2 screenshots I posted it does look different, but I must have came off the throttle. Basically the throttle still works and you can see the needle move but the wheel does not spin. If you go back and look at my previous pics I posted it is more evident.

 

[tedo]

This thing handles that much amps and power?

It is supposed to handle way more.

 

[Chalo]

I have done a lot a wire jiggling of course, but a loose wire wouldn't have a certain temperature and 8 second delay every time.

That's not motor behavior, so I have strong doubts that it's your motor. Motors work, or they don't, or they work only when they are not suffering a continuity problem. To me, that's not what you're describing.

 

[amberwolf]

I think

What is happening is that I think I have a battery with 400mps max line and 640 peak for 10 seconds according to Amorge. What I actually have is a battery of 400 max and at 410 it will self protect or over 400 for 5 seconds it will self protect. The Fardriver is doing its job and letting me know this with the 15MOE code.

if the bms protects, it completely turns off all power. it can't do anything else, as it has no electronics except a complete cutoff switch.


if anything else is happening, it isn't the bms doing it.

 

[amberwolf]

If I knew that I wouldn't be on here crying like a baby to you guys. LOL. The only consistent thing is when temperature is around 48 or over and anything upsets the wheel like a crack in the road or putting the brakes on etc.. the motor shuts off. That says motor fault. However, after 8 seconds of no spinning the motor works again. That seems like controller. I can ride this on supercross whoops without it cutting off as long as the temp is below 48. I have done a lot a wire jiggling of course, but a loose wire wouldn't have a certain temperature and 8 second delay every time.

under those conditions, you could be getting a phase current spike from the road conditions or brake action, and the controller is intolerant of this for whatever reason, then faults out, and has a reset-wait-period.

or the controller has to reboot because it crashes, and takes that time to do so.


either way, it's almost certainly a controller fault, a setting somewhere, tuning parameters, etc.


had this kind of thing happen on a gmac with a phaserunner; never resolved it.

 

[amberwolf]

there is a tiny chance that the motor is internaly damaged with winding insulation scraped away at a corner of a stator tooth, so expansion of the metals causes short from stator tooth to winding; this would usually require at least two phases being damged this way to short together, or a short elsewhere in the wiring to ground in addition to the phase winding shorting to the tooth laminations.

i had an mxus3k 450x motor with this issue thqat i fixed by drizzling coronadope down into the windings; there's a post in my sb cruiser thread or the sfoc5 thread about it, where it blew up the sfoc5 controller before i found the fault. was a crappy motor anyway, broke the not-sure-it-was-really-steel axles at some point. more than once i think.

 

[eee291]

fardriver-controllers/MANUAL.md at main · jackhumbert/fardriver-controllers

Information on Nanjing Fardriver Controllers. Contribute to jackhumbert/fardriver-controllers development by creating an account on GitHub.

github.com

This has some information about MOE.
Use Ctrl+F or find in page to find it faster.

 

[tedo]

if the bms protects, it completely turns off all power. it can't do anything else, as it has no electronics except a complete cutoff switch.


if anything else is happening, it isn't the bms doing it.

Ya all my lights and controller is staying on

 

[tedo]

fardriver-controllers/MANUAL.md at main · jackhumbert/fardriver-controllers

Information on Nanjing Fardriver Controllers. Contribute to jackhumbert/fardriver-controllers development by creating an account on GitHub.

github.com

This has some information about MOE.
Use Ctrl+F or find in page to find it faster.

Thanks!

 

[tedo]

fardriver-controllers/MANUAL.md at main · jackhumbert/fardriver-controllers

Information on Nanjing Fardriver Controllers. Contribute to jackhumbert/fardriver-controllers development by creating an account on GitHub.

github.com

This has some information about MOE.
Use Ctrl+F or find in page to find it faster.

Such good info. I was reading about this (see pics) on here but not in the original clear text like this. It sounds to me like since I am setting rated RPM at 1670 and Max RPM at 2000 then I have limited my RPM in those parameters to 1/4th of what was intended. I have a 16 pole hub motor. Should I be putting 8000 RPM for a max? If I really mean 2000?

 

[eee291]

I only have limited experience with fardriver Controllers. I didn't have to mess with the rpm values after self learn so I can't say if that is the issue. Increasing the rpm value shouldn't make it worse.

MOE can also be triggered by incorrect PID values or too much field weakening. For hub motors with surface mount magnets it says it should be 50% or less.

 

[dominik h]

My controller also stayed on after the bms had shut off the battery.
But it was showing undervoltage error and a few other things like weakening field activated.

 

[dominik h]

To be shure it is not the bms that is causing the problem, can you bridge the bms with a wire?
Must not be a very thick wire, 6mm² will be enough. It is to reduce the current flowing through the bms.

 

[tedo]

My controller also stayed on after the bms had shut off the battery.
But it was showing undervoltage error and a few other things like weakening field activated.

That sounds exactly like me. But it is doing it even if I set 100 line A Max. It turns off at 100 amps or less. I have a 400 amp BMS.