Wi-Fi Control question

Chris,

What do I do to get it back to the active side? Nothing I tried worked

On the Engine Roster screen:

• Power the lashup's member's tracks
• Tap Edit
• Locate the lashup name in the inactive list
• Grab the icon to the right side of the lashup name and slide it up into the active list
• Tap Done
• Select the engine and return to the Engine Control Screen.

This is also how to make a TMCC or Legacy engine active.

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store! Get the free TMCC & Legacy Addendum here!

Barry,

Thank you! I was missing the "Edit" step. 

I was able to get things working. But the lashup is continuing to give trouble. I played around with it today with both the handheld and the i-pad. I've come to the conclusion that the problem is not the TUI, the Wi-Fi, i-pad, or the hand held remote. The problem lies in one of the engines. The lashup will startup normally with all the usual sounds. Horn, bell, couplers, and lights all work. But neither unit will move. I have them on the same track, separated by several inches. If I shut the lashup down, and call up the individual engines, one will always respond correctly, including moving. The other is a crap shoot. Sometimes things work, sometimes they don't. Anything to look at before I contact a MTH service center? The engine is under warranty.

Chris

LVHR

did you check your signal strength with your remote should be 10 

Alan

Chris,

did you check your signal strength with your remote should be 10 

That won't help.

Make sure that the lashup  gets power when the TIU channel initially gets power. If you toggle power on after the channel has been powered up, the lashup will miss the watchdog signal and do everything except move.

lehighline posted:

Barry,

Thank you! I was missing the "Edit" step. 

I was able to get things working. But the lashup is continuing to give trouble. I played around with it today with both the handheld and the i-pad. I've come to the conclusion that the problem is not the TUI, the Wi-Fi, i-pad, or the hand held remote. The problem lies in one of the engines. The lashup will startup normally with all the usual sounds. Horn, bell, couplers, and lights all work. But neither unit will move. I have them on the same track, separated by several inches. If I shut the lashup down, and call up the individual engines, one will always respond correctly, including moving. The other is a crap shoot. Sometimes things work, sometimes they don't. Anything to look at before I contact a MTH service center? The engine is under warranty.

 

Chris

LVHR

First of all, sorry for your troubles.  The good news is, I believe I know what the issue is.  We (MTH) had an issue with certain versions of engine firmware relative to lash up power up that causes the exact symptoms you are experiencing.  Call MTH service and request new DSP code for your models.  You can load the new firmware yourself over the rails using your TIU.   We have a free PC application called DCS Loader that will allow you to do this quickly and easily.  If I was a betting man, I'd bet this resolves your lash up issues.  In the meantime, a work around is to start up the individual engines, build the lash up, and run them.  The bug rarely occurs unless power is cycled.  

MTH RD,

Thank you very much for the response. I will give MTH service a call and ask for the DSP code. Is the DCS Loader the same one I used to install the rev 6 software?

Meanwhile, I played some more using the remote. I have 3 loops powered by 2 Z4Ks running through a Rev L TIU. 2 tracks are powered via the fixed input/outputs of the TIU. The third is on the variable input/output. The TIU has an external power supply, so I don't worry about which channel gets power first.

The drill has been to work with the fixed voltage tracks. The TIU is powered, but not the track. Place the engines on the track, and rapidly raise the voltage to ~18v. If the engines have sat for 48 hours or more, both of these will come up in conventional 99% of the time. I find if I let the engines sit powered for about a minute, then cycle the track power, the engines come back in command mode. But the lashup may or may not work.

I decided to try the variable track. The voltage in the remote is preset to 22.0v. Engines on the track, power the input to 18v. No voltage on the track until I access the TR button, find the track, and use the thumb wheel to roll the voltage back to 21.5v, then back to 22.0v. Track now has power. If the engines have sat un-powered for ~48 plus hours, we are back to conventional. I let them sit powered for a minute, then cycled the power with the transformer handle. The lashup came up in command, and ran correctly. Maybe I got lucky.

Again, thanks for the response and suggestion. I'll report back after I have it installed.

Chris

LVHR

Chris,

Be aware that replacing the engine’s DSP code is only an option with PS3 engines.