jwils 1
Here is an extract of a post I made on the Siskiyou forum the part about Digitrax consisting is in red.
I did some experiments consisting two locos back to back with a NCE Power Cab and a Digitrax Zephyr.
I used a brand new Power Cab with Rev. 1.28 software and a 6 years old Digitrax Zephyr with a DT400 throttle to conduct these tests.
I also used 4 locos, 2 Atlas Dash 8-40CW without sound, equipped with two identical NCE D14SR V3.5 decoders. Also 2 other Atlas Dash 8-40CW with QSI sound were used.
The decoders on all 4 locos were left with their factory default setting, except for the address which was set to each loco cab #, the appropriate value in CV2 to insure every locos were crawling at speed step 1 and a value of 3 for acceleration and deceleration rate for every locos CV 3 and 4 respectively.
First test was with the Power Cab and the two non sound units. I made an advance consist with both locos operating back to back. The consist address was 127 and the leading loco was # 7300 and the trailing loco was # 838. I made sure the stack contained both consist bearing the cab # of each loco. This consist did not behave as I was expecting. Sure enough I could toggle back and forth between each end of the consist with the recall button however the lights did not react as I wanted. If I was using #7300 as lead loco the front light of loco 7300 was on, which is OK but the rear light of loco 838 the trailing loco was also on, which is not what I wanted and vice versa. What I wanted is only the leading loco with headlight on and the trailing completely dark. Fortunately I know my way around at the bit level of the most popular CV, I was able to correct this problem in programing the proper values in CV22, I was expecting better handling of consists from NCE. Why should I tinker with CV values?
When I did the same test with Digitrax Universal consist, everything worked as expected, trailing loco completely dark, no need to play with CV22.
Now