Looking for a straight answer on DS64 power sourse options along with Loconet.
I find conflicting info in the Digitrax tech notes for the DS64 concerning use of Loconet with the various optins for applying power to the DS64. I plan to use routes with some stored in the command station (DCS200) with others as local routes stored in the DS64 where some local routes may involved turnouts controlled by seperate DS64.
Some tech notes say you MUST use track power to get the job done while others indicate Loconet will take care of message traffic and you can use auxilary power sources. I asked Digitrax Tech Support which of the three following options is the correct way to meed my needs.
1) Track power only (no Loconet)2) Track Power plus Loconet3) Aux power plus Loconet (no track power)
The response was that either 2 or 3 was prefered. My original plan was option 3 so I would not be tapping into track power. However, that conflicts with some of the Digitrax tech notes which imply that a connectin to the track is necessary. As an example, Digitrak tech note KB327 says
" When using a DCS100 or DCS200 to setup routes within the Command Station in conjunction with DS64 Stationary Decoders, the DS64 needs to be connected to Track Power. The DCS100/200 does not send internal route messages via LocoNet. DCS100/200s only send Routes as a series of switch commands out to the Track in DCC format. The DSC100/200 were designed in 1996 and had no requirement to echo these same switch commands out via LocoNet.
I know that some tech notes have errors. How about notes related to the DS64? Is anyone using the option 3 above and able to issue route commands (stored in command station) and also be able to issue route commands stored a DS64 that includes turnouts from multiple DS64? This last requirement is the tricky one. Some tech notes imply that one DS64 cannot trigger turnouts controlled by a different DS64 except via track power.
Paul D
N scale Washita and Santa Fe RailroadSouthern Oklahoma circa late 70's
That's not an error.
The DS64 can get it's switch commands from either track power or the LocoNet, but the switch commands it generates as the result of a stored route are sent via LocoNet only.
On the other hamd, the DCS100/200's do not send switch commands from their internally-stored routes over the LocoNet, they just transmit them as DCC commands on the track bus.
So if you want to use BOTH command station routes AND DS64 routes that span DS64's, you'll need both track power and the LocoNet.
Personally, on my layout I only use DS64 routes. I stay away from command station routes both to avoid the above restriction (my DS64's are all externally powered via the 2.1mm plug), and because any time you have to reset your command station, you lose all it's routes.
I use several DS64 all powered by wall worts and NOT by track power. I use DS64 routes exclusively. Some of the routes activate switches controlled by multiple DS64s.
[Edit] Oh ya... they are all interconnected to each other and the command station by Loconet.
Like the others, I have 9 DS64s. They are all powered by wall warts and connected by Loconet cables. All my routes are stored in the DS 64s, none in the command station. All routes and switch commands are documented and labeled.
Dave
Lackawanna Route of the Phoebe Snow
That's probably the best solution, as long as you have enough DS64 capacity for all your routes. Remember that you can nest routes, too, if you have to.
And one thing not mentioned, but implied - You'll notice that all of us who replied use external power for our DS64's, either wall warts or in my case a dedicated higher-capacity DC supply. DS64's using track power have been known to lose their programming, most likely as a result of electrical noise caused by a track short. So Option #3 also gives you higher reliability.
OK - if I read this info right and I put all my routes in a DS64, the DS64 will transmit route info via Loconet. Next question, will the command station retransmit the DS64 route info out over the track to control devices with track connections but no Loconet connection?
My objective would be to drive a Digitrax DS44 which has a track connection but no loconet connection.
PED OK - if I read this info right and I put all my routes in a DS64, the DS64 will transmit route info via Loconet. Next question, will the command station retransmit the DS64 route info out over the track to control devices with track connections but no Loconet connection? My objective would be to drive a Digitrax DS44 which has a track connection but no loconet connection.
I *think* the answer to that is "No", because Digitrax specifies that when cascading routes from one DS64 to the next, they must have a LocoNet connection between them.
I have a feeling that the "some cases" mentioned in that article are when you have the DS64 hooked to the track bus and are using routes in the command station. Considering it is followed by "but Loconet is more reliable" - which goes to the whole "don't connect a DS64 to the track power at all if you can avoid it"
I'm guessing the answer is no also, based on how I understnad the DS64 and Loconet traffic to work. The DS64 sends switch state report messages (all the time - this is why a throttle reflects a turnpout change initiated by the local buttons on the DS64) and switch state control message (as part of a route). The command station does not just generate NMRA DCC packets for every Loconet packet that comes in.
If you're REALLY curious, Tony's still lists one of the NCE DCC Packet Sniffers as available for $40. This works with any system - it's designed to decoder the packets on the rails. It will work with a simple terminal program on a PC, or with JMRI and show the NMRA DCC packets on the rails, so you could see for yourself what gets send where and when (combine with the loconet Monitor in JMRI to see the Loconet traffic, compared to what the DCC Packet Sniffer gets from the rails).
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
My design criteria for DCC is pretty simple.
1. Track is for locos.
2. Loconet is for control. Throttles. Turnouts. Control panels.
3. The one and only place 1. and 2. interconnect in any way is at the command station, in my case a DB150.
4. Loconet interconnects 14 control devices to the DB150.
4. All control devices are powered from wall worts. About 1/3 of the devices share a wall wort between two adjacent devices.
5. The rest is device config using JMRI.
Stay safe. D.