Can 2 people use different cab1's to control 2 different locos or will the both control the last addressed loco?
Thanks; Don
|
Can 2 people use different cab1's to control 2 different locos or will the both control the last addressed loco?
Thanks; Don
Replies sorted oldest to newest
An individual cab one controls whichever loco "it" addresses. You can have numerous cab ones all addressing/operating different locos at the same time.
We routinely have 7 or 8 Cab-1's controlling different locomotives simultaneously on my layout. Works like a charm.
However do not try using a CAB-1 and a CAB-2 to control the same engine, it causes wickedness and failure
it causes wickedness and failure
I don't remember all the details, but that was a warning when Legacy first came out, the units seem to fight each other when they are both set to the same engine
I've actually tried this, and it usually works fine. Once in a while, the engine will do something that doesn't truly make sense for the command input, but nothing major will explode.
Yes it works ok here too and the wickedness is when you know you can grab another club members train and make it all sorts of crazy stuff.
Well, you can do that with two CAB2's as well.
Right from the Legacy Manual:
Sharing ControlTwo operators, one with a CAB-2 and one with a CAB-1, should not operate the same Engine or Train Simultaneously. It is not recommended to “go between” CAB-2 and CAB-1 while operating the same Engine or Train. Doing this will make the graph on the CAB-2 incorrect
CAB-2's stay in synch so there is not a problem. Not sure of all the issues, we were just told when Legacy was released not to do it
It is not nearly as problematic as when you leave the TMCC Command Base attached to the outside rail instead of wiring it to the Legacy base using the cable
Somehow, I don't think the speed graph being incorrect is the end of the world. It makes sense that wouldn't work, if the CAB2 is probably in TMCC mode and the CAB1 is doing relative steps.
Probably would be an issue also if the CAB-2 was running in Legacy mode with a Legacy engine and you address the engine from a CAB-1
Interesting point, that would be an experiment to try. I don't have the old command base connected now, but that may be one of the combos that would create some interesting issues.
The only TMCC insanity I can remember was advanced control of consists. Once an engine was assigned to a consist, even though the consist was taken apart, it remembers. Procedure was to assign the engine to TR 0. Problem solved.
Access to this requires an OGR Forum Supporting Membership