Wiring DCS AIU to Fastrack

Page 76 in Barry's Book.

Thank you for the response.  I see the diagram on page 76 but it isn't clear to me if you have to choose between the remote switch controller or the AIU.  Can both be in play at the same time?  Perhaps once the app is able to control switches there is little purpose to the remote switch controllers.  

SF,

   If you do not have FasTrack Command Control Switches you must run thru the DCS AIU, if you have the Fastback CC switches you can control them via your TMCC or Legacy Hand Held Remote Contol, there is also a way to program the APP with the FTCC Switches, however I do not use APPs so I can not direct you as to how to set it up.

PCRR/Dave

Steven,

I see the diagram on page 76 but it isn't clear to me if you have to choose between the remote switch controller or the AIU.  Can both be in play at the same time?

There's not need to close. As per Figure 21 on page 76 of The DCS Companion 3rd Edition, you can wire the switch to the AIU and also to the manual controller (as per the switch's instructions). Both the AIU and the manual controls can be used together.

This and a whole lot more is all in “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store!

Thanks Barry,  Candidly I'm new to following wiring schematics so indulge me for what may be a dumb question but in order to operate both is it necessary to run two sets of wires from the switch track, one to the remote switches and the other two the AIU?  BTW the book is very helpful!

Steven Finkel 123016 posted:

Thanks Barry,  Candidly I'm new to following wiring schematics so indulge me for what may be a dumb question but in order to operate both is it necessary to run two sets of wires from the switch track, one to the remote switches and the other two the AIU?  BTW the book is very helpful!

Yes. Each device needs it's own set of wires to connect to the switch terminal. The FasTrack lever is four, because of the light in the lever. The AIU only needs thru, gnd, and out. No yellow wire.

You can save yourself several feet of wire by taping into the wires at your controllers that lead to the switch track connections that you would be connecting to at the track, or if your switch controllers open up by removing 2 screws like the MTH controllers, you can solder your AIU wires to the proper locations inside the switch housing. It does not matter where the hook up is made, at the track or at the switch controller, as long as you make the correct connections. I used the solid, four color, telephone wire. Only three are used though. Once your all done, it's fun to record a session, and watch the switches switch on their own.

Steven,

is it necessary to run two sets of wires from the switch track, one to the remote switches and the other two the AIU?

Yes, as Carl stated above.

All good ideas!  Thanks.  I have two engines. One is a Proto-Sound 2 and one a Proto-Sound 3.  The App readily finds the PS3 but not the PS2.  Any idea as to why PS2 isn't found or how to enable it to do so?  The help from everyone on the forum has been great.  Much appreciated. 

Steven Finkel 123016 posted:

All good ideas!  Thanks.  I have two engines. One is a Proto-Sound 2 and one a Proto-Sound 3.  The App readily finds the PS3 but not the PS2.  Any idea as to why PS2 isn't found or how to enable it to do so?  The help from everyone on the forum has been great.  Much appreciated. 

Steven,

If this can help:  When I had problems with the "Add MTH Engine" on the Wi-Fi DCS App (in fact, I got this problem yesterday with a new WIU), it appears to be because the firmware in the WIU was not updated to 1.1.  Doing the update to 1.1 on the WIU yesterday fixed the problem immediately.

Ref:

https://ogrforum.com/t...rmware-update-is-out

"...WIU FIRMWARE NOTES
• Cleaned up miscellaneous issues concerning reading, adding, and addressing engines... "

Thank you for the link above showing the WiFi update instructions.  The instructions are very clear and begin on page 9 of the WiFI  DCS User's Guide, however, when you get to page 11 you will be instructed to "Choose File" and navigate to the new firmware filename, select the file and click open.  The problem is that there will be no file to click unless you've downloaded a file from the following:

http://www.mthtrains.com/sites...ldcats/WIU_1.1.0.bin

After that you can continue with instructions and all should be fine as far as updating firmware is concerned.  I'm anxious to see if the PS2 engine will be discoverable.  

As a follow-up: So far even with the updated firmware I'm unable to connect with the PS2 engine.  I'll call technical support and see if they can help.

Steven Finkel 123016 posted:

As a follow-up: So far even with the updated firmware I'm unable to connect with the PS2 engine.  I'll call technical support and see if they can help.

Just in case, together with the latest WIU firmware installed, you might want to confirm that you have the latest Wi-Fi DCS App (V1.2.0)  and the latest TIU DCS Software (V5.00) installed.

Keep us informed of your findings !  Good Luck !

Yes I've downloaded the latest software however I did not find a DCS App (V1.2.0).  The latest I could find is (V1.1.0).  If you have a link to a newer version I'd love to know about it.  Thanks.  

Steven Finkel 123016 posted:

Yes I've downloaded the latest software however I did not find a DCS App (V1.2.0).  The latest I could find is (V1.1.0).  If you have a link to a newer version I'd love to know about it.  Thanks.  

Depending if you are using an IOS device or an Android device, you get the Wi-Fi DCS App directly from the "Apple App Store" or from "Google Play". 

MTH Info: https://www.youtube.com/watch?v=0MFWtKxqb_A

Thanks, so it looks like I have the latest software available.  It turns out that the problem I'm having with PS2 not being found by the App is due to a faulty presumption.  The box is labeled S-2 Turbine with Protosound but it turns out the engine is actually PS1 and will only run in conventional mode.  Unfortunately, problem solved.