Skip to main content

I've got a stupid question!

Now that winter is here, I started running my engines, well kind of!

I've got a new DCS system that I just bought last year.  My TMCC is the initial version.  Last year, I hooked the TMCC via the DCS system so all engines can be controlled via the MTH hand held controller.  I use MTH's interface cable to connect TMCC to DCS.  All has been working fine.

But now, this winter:

Via VAR 2, every time I turn power on via a Lionel brick, power is immediately applied to the track, and no engines can be controlled when selected via the controller.  VAR 2 via the controller is set to zero then power is applied. 

However, I thought I'd be creative and hook the track up to VAR 1 and all works great.  The usual procedure; I first need to select VAR 1 to dial up the throttle to 22 volts and all engines stay off.   I can then select an engine and run it normally.  The engines work great when power is increased from zero to 22 via VAR 1 but the immediate surge of 22 volts via VAR 2 causes all head lights to come on the engines and they fail to respond to commands.  This holds true only for the TMCC engines but the MTH engines will respond with no problems.   One caveat:  The MTH engines also don't like the immediate surge of 22 volts but one can turn them off via 'SHUT DOWN' and then restart them. 

I have separate bricks going to VAR 1 and VAR 2.  Each brick goes into its respective input side (outside end ports) of the DCS module.

It appears that maybe the TMCC for VAR 2 is 'hosed'!!

Thanks for any suggestions you may have.

Original Post

Replies sorted oldest to newest

Martye:

Commons on the TIU:

Something that I didn't know.  During the switch: I had the TMCC command base wire connected to only one of the inner fixed (Red side) terminals and the TIU distributes the TMCC commands to the other outputs and all worked OK (including starting up TMCC engines).  Initially, I thought I needed the command base wire connected to each output side that I wanted TMCC to work but it appears that is not true (I'll do some more testing).

Also, Initially, I thought the power from one red output terminal going to another output red terminal would create problems with power distribution but that is not the case.  Guessing that since the grounds are separate, the output power regulation will remain isolated.  I have 3 separate loops of track that are all power independent. 

Joe,

I'll have to research how to set 'start voltages' and see if that works.

 

Barry,

As mentioned above, it appears that connecting just one base command wire to one output (I did the red/hot side) and the TIU seems to distribute the commands to all outputs.  I'll have to do some more testing to verify this.  Thinking about it, it seems like the ground side would be common to all terminals.

 

Correct me if I am wrong, but I think you stated VAR2 goes to  full voltage when you turn on the transformer, even though you have set it to zero?  IF you do not have control of voltage, the VAR2 channel has failed.  This is repairable.  If voltage has gotten too high on V2 that may be causing the issue with TMCC engines not responding.   G

samparfitt posted:

Martye:

Commons on the TIU:

Something that I didn't know.  During the switch: I had the TMCC command base wire connected to only one of the inner fixed (Red side) terminals and the TIU distributes the TMCC commands to the other outputs and all worked OK (including starting up TMCC engines).  Initially, I thought I needed the command base wire connected to each output side that I wanted TMCC to work but it appears that is not true (I'll do some more testing).

Also, Initially, I thought the power from one red output terminal going to another output red terminal would create problems with power distribution but that is not the case.  Guessing that since the grounds are separate, the output power regulation will remain isolated.  I have 3 separate loops of track that are all power independent. 


 

The one wire from the TMCC base has to go to the commons, which is connected in theory, to the outside rails.  If not, the TMCC engine will not perform as they should.  They are expecting to see that part of the signal on the common (outside rail).  And in the case of the newer TIUs that means you need to tie the commons together or supply the one wire connection to all commons, basically doing the same thing via the TMCC command base.

Last edited by MartyE

MARTYE,

I moved the command base wire to the ground side, which makes sense. 

I have to agree with GGG in that the TIU is, probably, damaged.  Possibly due to me connected the command base wire to the hot side. 

I had the initial issue of DCS, last year (before buying a new one), and it was not functioning properly.  I bought some surge suppressor diodes from TMC to try to fix it, but it was academic as the board was shot.  I have a surge suppressor diode left and can try replacing the old one and see if that works. 

FYI,

The initial surge of 22 volts doesn't appear to confuse the engines on that track as when I dial in VAR 1 with a starting 22 volts (and not zero volts), the engines behave properly (ie idle with no sound or movement).  Thus it does, indeed, appear to be a damaged TIU.  Not too happy about that as I just bought it a year ago.   Again, it may have been my fault connecting the TMCC command base to two hot output sides (although that could easily be done by mistake on many TIU's!).

Add Reply

Post
The DCS Forum is sponsored by
×
×
×
×
Link copied to your clipboard.
×
×