I am not clear after reading the manual on the Legacy E8/9 A-A manual. Should I program each A unit with a unique ID, or should they both be programmed at the same time with the same ID?
Thanks,
Ed
|
I am not clear after reading the manual on the Legacy E8/9 A-A manual. Should I program each A unit with a unique ID, or should they both be programmed at the same time with the same ID?
Thanks,
Ed
Replies sorted oldest to newest
Same ID to each so when you activate smoke for instance....both will respond.
Program them with different numbers and MU them.
Thanks for the replies. But so far I have gotten two completely opposite answers. Which one is the better choice.
I suspect the second A is a dummy with lights and smoke, no motors. Is this correct?
Product number is always helpful.
Yes, the second A unit is non-powered, but does have smoke and a working front coupler. The Lionel number is 6-39609.
I'm sure you assign them both the same ID. The dummy A couple will fire when the rear is pressed. Lighting should follow as well. Won't hurt to try the same ID and see how the dummy reacts.
As Marty said.
I have a Legacy ABA set, FA2.
Motors only in the A unit. Your set (nice Daylight colours!) also only has motors in the lead A.
I program them separately to the same ID number. That way all 3 (ABA) respond to the one ID.
Smoke, directional lighting and couplers all work well this way.
Hope this helps.
Interesting - I programmed my new Pennsy powered A and dummy A as a "lashup" and it works well.
Thanks for all the replies. From the input it seems that either method works fine. I setup my E9's today and used the same id for both. Seems to work just fine. I did notice one thing concerning the rear coupler on the dummy A (really the front). When fired using the same id method you hear the coupler opening sound. When two ids are used and in a lash-up, when the rear coupler is fired it opens but no sound is produced. I prefer the single id method.
Ed
Keep it simple like Soo Line and Marty posted. I have those engines and do it this way.
Access to this requires an OGR Forum Supporting Membership