Follow-up:
The book is excellent for someone who has a now unavailable (for less than the cost of a mortgage) TIU and Remote. I'ts a great book and I am not sorry I bought it, but it doesn't help me much.
Here is the equipment I have at present:
1. Layout consisting of two concentric Fastrack Loops with two center rail toggled crossover sections.
2. A homemade 4-pin interface terminal consisting of a hot lead for each loop, an auxiliary lead, and a common ground for all three.
3. I have a power station that plugs into it consisting of two transformers:
One MTH-Z1000 (with the auxiliary utilized), and one MRC low power transformer.
What I want to do is to figure out how I can unplug the existing power station from the 4-pin interface and plug in a different one to run MTH trains.
Here is what I own to do that with:
1. An MTH Z-4000
2. An MTH DCS Remote Commander
3. An MTH DCS Explorer
I am not sure how to wire them to the four pin interface for the layout.
Thanks,
John
I'm not sure what you are intending to do here. I get the frustration and lack of TIUs and high cost of used DCS components, however you have what can be good items to have- when used properly.
Example, both the DCS wifi Explorer and the IR commander are weaker single channel output track interfaces for the DCS signal. By that, I mean the actual DCS signal output on the track is not as strong as even one channel of a given TIU- and can be attenuated or degraded quite easily to the point DCS signals and locomotive control becomes problematic.
Then we get into little tidbits like- the Wifi explorer needs a CONSTANT power source and also, cannot be used in passive mode for higher current bypass. In other words- connecting it to your Z4000 is a problem IMO for a bunch of reasons as a power source. #1 When turning the Z4000 on, the handles MUST be down in the off position. You then have to raise the handle to the desired voltage. You cannot just leave a handle up and turn on and off the Z4000. Again, let me state this- the Wifi Explorer is a tiny off the shelf module running an operating system from flash memory, and I have found that dropping power at the wrong time during the boot sequence can then corrupt that module in a way that no amount of hoping, praying, pressing the reset button is going to resolve the corruption. Again, all reasons why a variable output channel from a Z4000 are not the best and most reliable way of powering this device, and further, the high current capability of the Z4000- compared to the limited no more than 6A input labeled on the device is another problem. In fact, the current limiting and even the 5A rated fuse- people have still blown sky high these explorers in track short events. And we aren't even touching on the problems of the DCS application side of this when used with the limitations of the wifi explorer.
In short, the Wifi Explorer box:
#1 definite current (Amperage) limitations, both on what should be provided for input and what it can output. The built in current limiting has failed many folks and blown up.
#2 It requires a constant fixed voltage source to power up and boot up. It is not recommended to be used with variable power input sources. While some might say you "can get away with it", head the warnings before you brick it.
#3 Cannot be used in passive mode as a DCS signal source only (not passing power "through" it). passive mode in theory could at least work around the current limitations of the device.
#4 Has pretty serious limitations in the DCS app control system (example no steaming whistle function, no lashups, limited to 3 engines max, doesn't work with all engines -example won't work with my PS3 Monorail).
OK fine, so you have the IR commander. The good news is, they can be run in passive mode, so that's one bonus. Catch22, it requires any engine for it to control to be at default ID 1. Now where this is going to cause you massive grief, if any engine you add to your Wifi is going to have an address likely not 1 after the first engine, so then that same engine has to be reset before the IR commander could control it on the other track.
Again, in a way, you have 2 kinda sorta incompatible control methods due to the ID addressing scheme and limitations.
It can be used together, I'll try to make a "suggested" diagram, however, again, I have reservations about powering a DCS wifi explorer box with a Z4000.