@RickO posted:I thought the stalled motor detection was 1 consecutive cab light flash.
don't recall anything with the horn blasting constantly as an indicator.
In Gary's video. The cab light doesn't even appear to be flashing.
Reviewing the video again, yeah sure, the cab light does not blink, but the hand was in the way to see the status of the universal remote until this point in the video and I do not see any of the 3 engine buttons showing connection to the engine.
.
Which again, just amplifies the question of trying other control methods like normal conventional, TMCC, or Bluetooth Lionchief App operation (using a phone or tablet) to ensure this is not a communications issue with that universal remote.
Again, turning the knob on a remote that isn't showing connection to the engine- is not generally expected to work.
Just to show it's not that frame in the video, another frame grab showing absolutely none of the 3 engine selection butons are showing connection to the engine.
The idea here is to eliminate variables and determine if the engine is locking up and then losing connection with the remote, or if somehow that universal remote glitched out (bad firmware, old firmware, low batteries, user error?) vs this specific LC+2.0 engine keeps doing the last command it received.
Other scenarios- again a power glitch where the engine lost power, stopped, disconnected, and is getting a DC horn offfset from the transformer or some other power error. Again, a power loss or glitch could have caused the disconnect from the engine side, and the engine is blowing th horn from also seeing a DC offset while sensing conventional mode since it is disconnected from the remote.
Again, it might be something with the engine, I'm not saying that's impossible, but from one rather short video, I cannot for sure say the engine caused this state (engine stopped, horn blowing, universal remote not connected) if it was caused by external actions or sources.
