Lashup does not move

 Try this.... Turn off the tiu and turn it back on again making sure the lash-up is on a track receiving power. Lash-ups need to hear the watch dog signal which goes out each time the voltage on any tiu  channel is raised above 0 volts. There is a difference between the watch dog signal and dcs signal.     

Gregg,

I think I am doing that. The power to the track is off when I transfer the engines from the programing track to the layout. The layout TIU is powered b/c there are other trains running on other channels. After the engines are on the track, I raise the handle from 0 to ~18v. That should generate the watchdog signal, correct?

I'm not getting any error messages on the remote. The engines simply do not move.

Some more details: I'm using a Z4K on the layout, and a 1960's era ZW on the programing track. There are 2 separate TIUs, each set to Address 4. TIU 4 is the only TIU in the remote. The programing track TIU is tethered to the remote when actually doing programing. Otherwise, that TIU is powered down so as not to interfere with the layout's TIU. I tried tethering on the layout's TIU- no difference.

Chris

LVHR

Chris,

What DCS version is in the two TIUs and the remote? They must all be the same.

Regardless, just delete the lashup and rebuild it on the layout using the layout's TIU.  That should correct the problem.

Should be working as you described.  Maybe try placing tiu (actually remote in super mode) I'm just heading out the door back later.

Chris,

What release of DCS is in each TIU and in the remote? Ensure that they are all the same.

Regardless, just delete the lashup and rebuild it on the layout, using the layout''s TIU. That should correctt the problem.

Hi Chris, how did you make out? We have the same set up (tethered) except our tiu numbers are 1.  I've run into a few problems just trying to add engines let alone create a lash-up. I've  had to cycle tiu  and can't remember what else to get engines added. In theory it should work . I was curious whether you came up with anything??

Adding the engine on the layout defeats the purpose of the second tiu.

Gregg,

Adding the engine on the layout defeats the purpose of the second tiu.

How so? Building a lashup is not a DCS signal-intensive process. Why use a second TIU at all?

Sorry, I've been at work today.

Barry, Both TIUs and the remote were at 4.10, as I recall. I did the upgrades quite a while ago.

The are 2 TIUs because we were running at the Allentown show. So we use one TIU as a programing setup and the tether the operator's remote to it. I have a log beside the programing track to keep track of addresses so we do not have multiple engines with the same address. Check the log. If the address is already taken, change the address of the new engine to something else. As long as we are adding the engines, it makes sense to create the lashup at the same time and test it.

The programing TIU is rev G and the layout is a rev L, which should make no difference, as both are set the same address. We just make sure the programing track is off or has a remote tethered to it. The set up works quite well.

I actually need to put the layout back together in my train room, so it will be a bit until I can actually try out the suggestions.

Chris

LVHR

We don't use it that often but when we have visitors  with their own engines and no remote it comes in handy. No  interruptions while the rest of guys are operating. (single track layout) In theory it seemed like a great idea. No so sure now.