DCS system remote's address to TIU

Please correct me if I've missed exactly what you want to do, You never jumper the outputs of a tiu channel. Only the inputs, As you know the tiu needs a power supply to function, (turn on) so we need power to fixed 1 in or an aux power supply that plugs into the end of the tiu. got to have one or the other or both.

You can jumper from fixed 1 in to any other channel input, could be fixed 2 , var 1 or var 2 or all of  if needed or any other combination on the input side . 

How many loops do you have and do you want to run conventional  on each one using the var channels?

Hello Gregg,

Thank you for responding, because of these holidays, we're all busy hustling around, to get back at what I was trying to describe, I explain that I hooked up jumper on the output side, I'm wrong.  I did the hook up on the input side. And as I further expained that for long time after it was set up I was to run both conventional and fixed engines. I have two independent lines and two other independent lines, the lines I'm focused on are the first two (trk) lines these lines follow to the TIU, operate through the unit. The power that is given to the TIU unit are two separate MTH blocks each operate a single trk, (1 & 2) - again for long time this method was working good. The two other lines are ID one is the trolley line the other is the yard.  My problem is running the two trk lines through my remote - I cannot control the speed and I cannot find a way to changed the reading on the screen of the remote from 'var' to 'fx'd' the support rep from MTH stated that by pressing the S5 it would allow me to change it well I forgot what I was suppose to work in order to do this. do you know, and do you know by what I described above is my problem? 

Thanks hope to hear from ya

Chuck g

I cannot control the speed and I cannot find a way to changed the reading on the screen of the remote from 'var' to 'fx'd' the support rep from MTH stated that by pressing the S5 it would allow me to change it well I forgot what I was suppose to work in order to do this. do you know, and do you know by what I described above is my problem?

Thanks hope to hear from ya

This one is used to change the var channel from fixed to var or from var to fixed

Menu/System/ DCS set up/  Select the var chanel; and hit the FXD, The FXD key is like a toggle switch and changes the channel from fixed to var , with each press it changes.

The remote will  tell  you what mode you've selected.

I'm confused.

You know you have to run conventional engines on the variable channel and if you change the variable channel to fixed, it will only run your PS2 engines?

Trying to run a conventional engine on a fixed channel will cause it to run a high speed as soon as the track gets power. Unless you have a Z-4000 transformer with a receiver and use Z4K tracks.

"You never jumper the outputs of a tiu channel. "

Gregg:  Not quite correct.  It is ok, and probably a good idea to jumper the black output terminals on Rev H and later TIU's; Rev G's black outputs are internally jumpered.  This note does NOT relate to Chuck's problem, but is posted only for general info.

The red outputs should never be jumpered.

RJR, You're right only the reds should never be jumpered.

 Hi Chuck.... The tiu has 4 channels, 2 fixed and 2 var.

The fixed   are normally used for running command engines( Proto-2  constant voltage on the track.

The var channels can be set to fixed mode with the remote  and  used to run command engines,(constant voltage on the track )

 However  the var channels can also be set to var mode where the track voltage is varied by the dcs remote for conventional engines.

So you have  fixed 1 and fixed 2 for proto-2 engines

Var 1 & var 2 for conventional engines

Power supply. seems you have 2 MTH bricks and want to use 4 tiu channels. I would use one brick for fixed 1 and var 1

The other brick for Fixed 2 and var 2.

Why don't you send me your phone number right now.  granclemmens@hotmail.com

My only point, and it was not addressing your issue, is that it is proper to place jumpers across the BLACK output terminals of a TIU, except it's not necessary if you have the original Rev G version TIU, where this is done internally.  I said this for the benefit of others reading this thread.

Turning to your issue: Quite frankly, Chuck, I'm having difficulty understanding how you have wired the system up.  But then as I age I am getting denser.  If you could start at the transformer and describe how you've run wires from what posts on transformer to what posts on TIU input side, and how you've wired the output side. it might help.

Chuck,

I'm seriously thinking that my problem is the remote for it's been played with by my grandchildren and I was unaware of them doing that, until My wife told me that night when the kids went home. I need to address my remote.

Try the READ button to see if the remote finds the TIU. If so, the remote is communicating and you can always reset the remote and TIU and start over as new.

Unless the grandchildren drop the remote & it shatters (which mine have done), there is little they can do to damage it that can't be undone.

Dropping the remote can cause the RF board to unseat and cause it to not communicate with the TIU. That's way I suggest to use the READ button above.

Joe,

Dropping the remote can cause the RF board to unseat and cause it to not communicate with the TIU. That's way I suggest to use the READ button above.

As an FYI, rather than use READ to test TIU-remote communications, I suggest using Menu/System/TIU Setup/TIU Version instead. That way, engines don't get moved around between the Active and Inactive engine lists.

Barry,

Being that he has only 2 PS2 engines, I thought it would be easier for him to just reset everything and start over if the remote is communicating with the TIU.

I've never had a problem using the READ and use it all the time. Leaving engines not in use in the ACTIVE can also cause problems with them moving on their own when left on powered up tracks. I've never had one move when placed in the INACTIVE.

I've also have no problem moving the engines back to ACTIVE. I believe the problem appears when leaving the individual engines and the lash-up together in the ACTIVE list. I always move individual engines of a lash-up back to the INACTIVE before shutting down.

Joe,

I wasn't suggesting that READ causes problems, only that I don't care to have it do a sort of my engines by assigning those that are on powered tracks to the Active List and those that are not to the Inactive List.

Getting the TIU's software level is benign and also informative.

Barry,

I can see your point with getting the software level. But the more engines I get into the remote, I find it easier to use the READ to separate the ACTIVE engines from INACTIVE, instead of having to scroll through the whole list.

Example, I'm running #4 and #25 and #60

With all engines in the ACTIVE, I have to scroll up and down to find each to adjust each ones speed, direction, horn, etc.

Using the READ places all the other engines in the INACTIVE and the 3 above that I am running, in the ACTIVE. I find it much easier this way as I don't have to scroll much to find each engine. Just a click or 2 of the thumbwheel instead of 56.

Joe,

Different strokes, I guess.  

I have all 90+ of my PS2/PS3 engines in the Active List all the time, except for lashups, which alternate in the Inactive List with their members. However, I don't scroll. I use direct addressing by DCS ID# to locate engines in the list.

I run in Super TIU mode and this largely avoids the bug that prevents engines from coming out of the Inactive List when they're not on tracks belonging to their associated TIU.

I rearely, if ever, use READ.

Barry,

I can't remember all the addresses for the engines to direct address them all. Do you remember them all from memory or keep a list of them handy?

Joe,

 Do you remember them all from memory or keep a list of them handy?

My layout is around-the-walls and three levels, all interconnected.

Engines are numbered sequentially, starting in the transfer table-driven engine yard and then progressing around the room. Each level has a set starting position and a set starting engine number.

Subways (I have 11) are numbered separately but in the same fashion, as are my few lashups. The TMCC stuff is in a completely different remote, however, there are only 20 or so entries, most of which are ERR-modified operating cars.

This process makes it relatively easy to identify a DCS engine's ID# in the remote's engine list.

I also maintain a list of all of the content in the remotes, however, that's more for documentation purposes and isn't used during operating sessions.

Barry,

Yes, I can see how that would work and even if you came up 1 or 2  addresses off, a couple of clicks of the thumbwheel and you would get to it fast enough.