Is MTH Software Upgrade Ready?

Hi Phil,

Not yet.  We haven't seen a beta for testing so far.

Phil,

If you're operating in Super TIU mode, make sure that:

• When you build a lashup that you use only engines that were associated with the same TIU when they were last added to a DCS Remote
• When you access a lashup or a lashup member that is in the Inactive Engine List, that you have that engine or lashup sitting on a track belonging to the TIU with which it was associated when it was last added.

This will avoid the bug that is likely plaguing you.

This and a whole lot more is all in "The DCS O Gauge Companion 2nd Edition", now available for purchase as an eBook or a printed book from MTH's web store site! Click on the link below to go to MTH's web page for the book!

This raises a question I've had for a while. I run 2 TIU's in the super mode and have about 50 engines loaded into the system. I've always heard that you should load the engines into one TIU. I run 2 circuits thru TIU #1 using all 4 channels. It just so happens that when I get a new engine, I place it on one of these two tracks to load. So I assume I've been lucky and loaded most of my engines into TIU #1. Is this correct? Is there any way to tell where the engines are loaded? I suspect I have some mavericks.

Yes.  At least when you loaded the engines they all would have gone in through TIU#1.  If you pressed the "Read" button latter all bets are off.  The engines would re-associate with whichever TIU they were running through at the time.

Yes.  If you set the TIU's to normal mode in the remote the engines will only run on the TIU to which they are associated.  If the engine is on TIU #1 and it still runs it's associated with TIU #1.  If it's on TIU #2 and it doesn't run it's associated with TIU #1, etc.

I don't think there is away to tell where your engines  are loadedThe "read" is of  king of engine / Tiu association. If the engine was added to tiu #1 and somehow ended up in the inactive list in tiu#2s zone the "read" will find the engine and let you start it up, The engine  /tiu association has now changed from Tiu #1 to tiu #2.  As you know the read takes forever  and any engine on toggled off siding automatically go to the inactive list. You can end up in a big mess. I also never use the "read". I know it's not always possible to park an engine in the  tiu zone it was added to  but as long as the engine is in the active list things seem to work ok.

Thanks for the reponses. I have considered removing the dreaded read key from my remotes. As Gregg says "it can create a big mess". In my situation, with many engines not even on the layout, some on dead sidings and some parked where the signal strength is not the best, I have learned to make sure I hit the headlight key and not the read key. You only have to make that mistake once. I'm not having any problems with my system, but I was wondering if there was any way to tell where the engines are in the TIUs. I guess for me the simple answer is no.

"At least when you loaded the engines they all would have gone in through TIU#1."

Dave: Would that be true even if loco was first added when on a track controlled by TIU2?

GHD, while it's a pain, it's not that bad.  Just have to make sure that every loco is on a powered track, with good signal, when you hit "READ."  However, in truth I do get annoyed in a grandchild hits read.

No.  The engine associates with whatever TIU it is running through when it is loaded.  GHD said in his post that he always used a track that happened to be powered through TIU 1 out of habit and convenience.  My comment was specific to him, not a general statement.

Gents, along Phil's line of question about upgrades, the reason I look for the headlight button a lot is that I'm running 4.1 and many times when hitting the smoke on button, the lights go off in the engine. Has this bug been fixed? Things are pretty good otherwise and I'm resisting the upgrade.

GHD. I'm glad you posted this infomation, We have had the same problem with more than one engine when  turning on the smoke, We stillhad a head light but the class and interior lights are gone. I figured the MUX board shorted out but don't really know. A feature reset usually restored the lights but not any more. Kind of ****es you off a bit.

Gregg, when this happens, I can usually use the headlight button to turn it back on, and go to the "more" feature to turn the other lights back on. It is a pain. I like to run playback programs and this bug has deterred me from turning smoke units on and off while running a program. I see we are keeping Phil's picture at the top of the list here.

George