MAIN TRACK POWER OVERLOAD

[fire-bot]

Sent by Wegmueller Stephan SBB CFF FFS (stephan.wegmueller@sbb.ch). Created by fire.

---

Hi,

If I activate the current for the tracks ( with <1> ) I get the following serial console output:

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=20

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=40

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=80

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=160

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=320

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=640

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=1280

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=2560

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=5120

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=10240

MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=10000

* MAIN TRACK POWER OVERLOAD current=31986 max=2988 offtime=10000

Any idea how to fix the issue, please?

I use a Pololu motor shield: https://www.play-zone.ch/de/pololu-dual-mc33926-motor-driver-shield-for-arduino.html

Serial console output: DCC++ EX v3.0.0<iDCC-EX V-3.0.0 / MEGA / POLOLU_MOTOR_SHIELD G-9db6d36>

Thanks for input.

Best regards

Stephan

[Asbelos]

This looks like a track short. First thing is to decide if this is a track problem or a command station problem.. Does this happen if the track is physically disconnected from the pololu shield?

[trainfozz]

Is this issue solved as I have the same with a DeekRobot motorshield?

Regards, Ron

[Asbelos]

The deek robot shield is fairly standard so problems of this nature fall into just 4 camps  A) your config.h is not correct for that shield.B) there is a fault on the Arduino A0 pinC) there is a fault on the shieldOrD) YOU genuinely have a track short possibly caused by an errant coin/screwdriver or by an incorrectly wired turnout frog. First check is with a multimeter or continuity tester (battery and bulb) that you dont have a genuine short when the wire between the track and the  shield is disconnected. On 12 Feb 2021 14:15, trainfozz notifications@github.com wrote: Is this issue solved as I have the same with a DeekRobot motorshield? Regards, Ron

—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.

[JoJo-86]

Having almost the same issue and can't solve it. Configured the L298N Board (not shield) and using M471 as current sensor. Output is:

<* *** MAIN TRACK POWER OVERLOAD current=3498 max=1995 offtime=20 *** *> <* *** PROG TRACK POWER OVERLOAD current=1093 max=248 offtime=20 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** MAIN TRACK POWER OVERLOAD current=3498 max=1995 offtime=40 *** *> <* *** PROG TRACK POWER OVERLOAD current=1761 max=248 offtime=40 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** MAIN TRACK POWER OVERLOAD current=3489 max=1995 offtime=80 *** *> <* *** PROG TRACK POWER OVERLOAD current=2586 max=248 offtime=80 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER OVERLOAD current=771 max=248 offtime=160 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER OVERLOAD current=566 max=248 offtime=320 *** *> <* *** MAIN TRACK POWER OVERLOAD current=3620 max=1995 offtime=160 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER OVERLOAD current=922 max=248 offtime=640 *** *> <* *** MAIN TRACK POWER OVERLOAD current=3450 max=1995 offtime=320 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** MAIN TRACK POWER OVERLOAD current=3450 max=1995 offtime=640 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER OVERLOAD current=1322 max=248 offtime=1280 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** MAIN TRACK POWER OVERLOAD current=2903 max=1995 offtime=1280 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER OVERLOAD current=1010 max=248 offtime=2560 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** MAIN TRACK POWER OVERLOAD current=3708 max=1995 offtime=2560 *** *> <* *** PROG TRACK POWER RESET delay=100 *** *> <* *** PROG TRACK POWER OVERLOAD current=966 max=248 offtime=5120 *** *> <* *** MAIN TRACK POWER RESET delay=100 *** *> <* *** MAIN TRACK POWER OVERLOAD current=3494 max=1995 offtime=5120 *** *> What confuses me ist the change of max value. It is 1995 what is close to the 2000 I've set in the #define but it's not exactly the 2000. Also for PROG ist's also set to 2000 and in the log it shows 248: #define SMALL_L298N_BOARD F("SMALL_L298N_BOARD"),\ new MotorDriver(2,4,6,UNUSED_PIN,A0,4.88,2000,UNUSED_PIN),\ new MotorDriver(3,5,7,UNUSED_PIN,A1,4.88,2000,UNUSED_PIN) #define MOTOR_SHIELD_TYPE SMALL_L298N_BOARD Also, how can the MAX471 maessure a current of approx. 3500mA when nothing is connected to the L298N output. I meassured the MAX471 RS+ to RS- resistance which is 0.5Ohm. This value should be ok. Had another MAX471 which was meassured 405Ohm. Maybe also important information from my log: <* MotorDriver currentPin=A1, senseOffset=493, rawCurentTripValue(relative to offset)=409 *> <* MotorDriver currentPin=A0, senseOffset=1023, rawCurentTripValue(relative to offset)=409 *> <* Signal pin config: normal accuracy waveform *> Any ideas? Regards JoJo

[Asbelos]

This looks like your analog pins are floating... or disconnected, or you have a short on the tracks or wiring.

The 1995 and 248 are rounding errors from using floating point... The 248 value is because the prog track is limited by nmra standards to 250mA except when actually requesting an ACK or when internally joined to the main track.

[JoJo-86]

Thank you for that fast reply. I do now understand the value 248. Didn't know that before. Also slight difference because of rounding makes sense to me. The sense pin of prog wasn't connected, so I know why there isn't a clear value coming up. For main everything was hooked up. I also measured the out pin voltage of the MAX471 and it was 2.6V according to my multimeter. Which is different from the shown milli amps but anyway too high as no track is connected yet, so I have unconnected outputs of my L298N board. This should give just the milli amps used by the motor driver itself. As I've used jumper wires for testing that may be a problem, but there's still the issue withe the 2.6V at almost no current flow. Because of that I've sent back the MAX471. Plans are now to build up a circuit like on arduino motor shield using Op-amp. I hope that fixes it. I'm going to post whether it did the fix or not.

[AaronPurpleRidout]

I have something very similar (Uno + deek), track not shorted, <1> works ok get ~80mA, but as soon as I send a command like F2 the current limit cuts in and the loco stops it's sounds. Have tried without keep alives in loco (to avoid inrush current) but no change? What fixed this for you?

[JoJo-86]

No fix yet, as family and kids need a lot of time right now. But I did already try connecting the arduino pins (for current sense) to GND which gives me 0 mA. So far so good -> no error in configuration and the mega is working. I'm going to order the OP Amp and resistors to rebuild the circuit from arduino motor shield schematic. I'm almost sure this helps. As I found out the MAX471 are often jot working correctly. In your case the sense circuit is on the Deek motor shield? Is it connected to other than the standard pins? What does your configuration look like?

[AaronPurpleRidout]

Thanks for speedy reply! Yes I believe the deek robot shield has the sense on it? I'll try the pull down to ground. I've tried with and without the pins 5to13 and 10 to 12?