Things were working fine - running two Legacy Stm engines on one large oval, track was clean as were the wheels and pickup rollars turned on engines and initially was ok but when i tried to turn the throttle knob -no response and the "line" on the screen was not moving so i clicked the speed dial and pushed the >> speed set and the engine moved forward = but i could not reduce the speed with the red throttle knob. the boost knob stopped the engine and the reverse light came on but again the throttle did not respond, so i started the second engine and no problem until i toggled back to the first engine and then i could only move the engines by using the speed dial wheel, tried shutting off power and restarting =no luck, put new batteries in Cab2 =no change i did not have this problem before - any ideas? all crew talk, whistle and bell all work, just the red knob isnt responding
Replies sorted oldest to newest
Ensure the brake slider is up. I've made this mistake before myself.
Brake slider on the left "Train Brake".
When you see this " when i tried to turn the throttle knob -no response and the "line" on the screen was not moving"
Again the likely reason is the brake is on so all the throttle turning won't make the line move.
Slider up is normal brake off, down is brake on.
thanks i will check tomorrow- pretty sure it was off -but will try
I'm not saying it couldn't be something else, but since it worked and then did not work as a symptom, that's one the controls (brake slider) that is not spring loaded to return to a known position. So you bump it or leave it in brake, and then "wonder" why you cannot move an engine using the throttle.
Also, when you address a different engine, I cannot remember if it assumes brake is off, or if that engine ID in the CAB2 was programmed as say CAB1 or TMCC mode and brake isn't active.
I've done it to myself and it's easy enough to overlook.
@Vernon Barry posted:I'm not saying it couldn't be something else, but since it worked and then did not work as a symptom, that's one the controls (brake slider) that is not spring loaded to return to a known position. So you bump it or leave it in brake, and then "wonder" why you cannot move an engine using the throttle.
Been there done that.
Just to put more effort into this, last night I tested my CAB2 playing around with settings for a given engine ID. It was my ERR AC commander equipped FM trainmaster. If I had it set to CAB1 mode- then brake slider is completely ignored. If I left the brake slider down, and then changed the mode to TMCC, it initially ignored the fact the brake slider was down and attempted to respond to red dial input and then suddenly acknowledged the brake slider was down. I also tried addressing a different engine and again, first time the engine is addressed if the brake slider is just down and untouched, it might ignore it- however eventually the CAB2 figures out Brake is applied on any engine ID with TMCC or Legacy modes chosen.
What I'm getting at is, I know a lot of folks recently have come into the hobby and are learning TMCC and Legacy. The default status of a fresh baseline Legacy database is CAB1 mode for all IDs. Then as a user adds them, they manually or using a memory module may change to higher level settings (TMCC, R100, Legacy). CAB1 mode ignores the brake slider completely, and the other modes respond to brake slider, but may initially ignore it when first addressed. Either way, still a good habit to know about the brake slider, and generally ensure it's up (AKA OFF) before running an engine.
CAB1 and R100 modes ignore the slider, TMCC and Legacy modes will react to the slider.
Thanks for the correction.
The reason that TMCC and Legacy settings react to the brake slider is they are absolute step settings, the CAB1 and R100 are relative step settings. Absolute step settings will command a specific power setting for a given throttle graph reading. The relative step settings just increment the power setting whenever a + or - step is input, there is no sense of the actual speed. There are different commands that are sent for absolute steps vs. relative steps.