Lionchief 2.0 Stuck

Yes, easily explained. Lionchief Plus 2.0 is a speed control feedback based tachometer system. If the track voltage is too low, or the load too high, or the motor is physically stalled- then the motor attempting to spin the tachometer can not reach the commanded speed. When that happens- to prevent motor and control system burnout from a locked motor condition the controller disables motor control.

Since both recent Lionel Legacy engines and Lionchief Plus 2.0 use the same electronics platform- this feature is shared across them. LCP2 and LCP3

Unlike previous Odyssey and Lionchief Plus control board which did not have this locked or overloaded motor detection, they would not disable the motor drive. Example Lionchief Plus board without Bluetooth did not have this behavior

@John Ptak posted:

I have a Lionel Lionchief 2.0 GP7 that seemed to be stuck in neutral.  I would put it in reverse or forward and the engine would rev, but it would not go anywhere.  The cab light also flashed when I tried getting it to go.  I eventually turned it off, took it off the track, put it back on, and then it worked just fine.  Anyone have any idea what this could be?

Again, this is a KNOWN function of a LCP2/LCP3 based control set found in Lionchief Plus 2.0 engines and recent Legacy engines.

Simply put, you created a condition where the engine either saw lower voltage (example dirty track or a switch) or lost voltage (power droop on the track from bad connections) on the track and at the same time was commanded a speed higher than the motor could achieve at that voltage. The controller assumes this is a fault condition and in order to prevent motor burnout and possible control board damage, it locks out motor control until the power is cycled long enough for the board to completely reboot. When in the fault condition- the firmware will flash the cab light with an error sequence.