While I agree with Bill that a single decoder can be simpler, there can be
reasons for using two. These can include doing things that can't be done with
a specific decoder or reducing the number of wires running between a steam
locomotive and its tender.
If people didn't have reasons for two decoders the decoder lock function would
not have been suggested or implemented. Also decoders with a SUSI interface
can communicate with a second module (like a sound module), and why go to that
trouble without a reason.
A recent S scale example of a two decoder factory installation is recent PBL
steam locomotives. They have a Soundtraxx Tsunami for sound and motor control
and a separate TCS function only decoder for additional lighting functions.
Using two decoders decreases the number of wires running between the locomotive
and tender besides having additional function outputs.
In the past, I used a two decoder setup as my standard because the early
Soundtraxx (pre-Tsunami) had poor (IMHO) motor control compared to other
decoders available at that time. So I used a Zimo decoder for motor control
and a Soundtraxx DSX for sound.
And when you get into some of the more advanced features such as RailCom,
Zimo's "HLU", Lenz's asymmetrical DCC "ABC", Digitrax's transponding, etc. and
you want sound, your decoder choices become more limited.
Using a decoder on hand that you like certainly is a valid reason to me. There
are a lot of decoder choices out there and we all have our different
preferences.
Dave Heine
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/S-Scale/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/S-Scale/join
(Yahoo! ID required)
<*> To change settings via email:
[email protected]
[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
