Author Topic: "Motor Overcurrent" error, maybe solved  (Read 2740 times)

zr1rob

  • Fireman
  • **
  • Posts: 34
"Motor Overcurrent" error, maybe solved
« on: June 01, 2025, 03:46:19 PM »
it's only maybe solved because this solution isn't proved long term, but it did solve the problem of 'motor overcurrent' error popping up on the HC2 and shutting down the loco, till power reset.

Only one loco with this error: the electric G scale Accucraft GS4 has a huge Pittman motor, but it only draws ~1.5A when running normally. However, the current spike during initial movement was too much and thus the error. Put an "Inrush Current Limiter" inline with a motor lead, as well as raising the 'starting speed' for the loco solved the problem to the point the loco can be used regularly without errors. I used an Ametherm SL32 10015 Current Limiter Inrush 10 Ohm 15a. BTW: this loco is battery powered.

gregeusa

  • Conductor
  • ****
  • Posts: 127
    • Greg's web site
Re: "Motor Overcurrent" error, maybe solved
« Reply #1 on: June 01, 2025, 09:38:57 PM »
The Pittman motors used in Accucraft are technically servo motors, used for rapid movement.

To generate quick and low rpm torque they draw big spikes of current from stopped.

Your solution is the right one, although I'll bet even a 5 or even 1 ohm resistor would have done the trick. You might have issues pulling heavy trains and the 10 ohm resistor "eats" too much of your voltage (voltage = rpm in an electric motor)
Lots of tips and techniques on my site: www.elmassian.com contact me greg@elmassian.com

zr1rob

  • Fireman
  • **
  • Posts: 34
Re: "Motor Overcurrent" error, maybe solved
« Reply #2 on: Today at 05:45:06 PM »
hi greg -

there was a lower value ICL that I tried "Ametherm SL22 5R012", it only handles 12A, but is 5ohm, did not work. The loco would tease running, but die. So the initial current inrush must be over 12A.

so that's why I went with the big gun. Rob Pira


gregeusa

  • Conductor
  • ****
  • Posts: 127
    • Greg's web site
Re: "Motor Overcurrent" error, maybe solved
« Reply #3 on: Today at 07:38:10 PM »
Wow, well that is a good datapoint. I suspect the RP decoder is tripping much earlier than (in my opinion) is needed.

So, probably tripping at rated current, not double as often is done.

I can understand the conservative "restriction", as the model 3 decoder was not up to the G scale locos in general..

which decoder is this, the 4 or the 5?  Can't be the 5 or its not living up to it's rating.

Lots of tips and techniques on my site: www.elmassian.com contact me greg@elmassian.com