Skip to main content

Hoping you Forum members can help! I just bought, tried and tested a DCS system for the first time.

I run a Lionel TMCC/Legacy layout with 2 lower level loops on a modern ZW with 180 Watt bricks. I have two upper level loops that I power with a postwar ZW, for running in conventional mode for postwar trains and occasionally MTH stuff. I connect a ground wire from modern to postwar ZW so I can still run the upper level loops with a TMCC engine. I also run MTH engines on the TMCC loops using 'conventional' operation, Using Cab-1 or Cab 2 to control track voltage. Ok so I finally took the plunge to try DCS.
DCS Question. Once assigned to the DCS remote, do MTH engines no longer respond to Conventional control ? 2020-09-09 23.04.182020-09-15 23.58.58
I just bought an older (PS2 era) DCS system and upgraded the TIU and Remote to the latest version. 
 
I successfully put an O-72 loop on my carpet and tested out a new MTH MP15 (PS3) BC Hydro diesel . After watching the quick instruction video:
1) I connected a Postwar ZW to the TIU fixed voltage in.
2) connected the TIU fixed voltage out to the track with a lock-on
3) Turned on the DCS remote, selected the 'Read' button for the remote to identify the TIU. Success.
4) Selected 'system', 'Engine setup', 'add engine, 'add MTH engine', then it found the new engine. Success.
I fumbled my way around with the remote for a few but successfully ran the MTH engine back and forward for a few laps. OK - DCS success!
Now, taking my MTH engine back down to my TMCC layout, I put the engine back on a ZW powered track I use in conventional mode, along with the MTH PGE RS-3. (also PS3)
Now, the BC Hydro engine no longer responds in conventional mode. The PGE RS-3 does.
After applying power - the engine immediately takes off in forward, instead of waiting for the capacitor to charge and the power up sequence to happen. After a full lap the sound finally comes on. I have NO Fwd-N-Rev control; using the ZW direction button. I'm in full on, forward only mode. (I do have a TMCC ground wire connected to U terminal on Postwar ZW from my TMCC ZW U terminal, so I can run TMCC engines on all loops) 
The RS-3 still behaves 'conventionally' and I haven't exposed it to the DCS setup.
Any suggestions for my BC Hydro diesel ?
Once assigned to the DCS remote, do MTH engines no longer respond to Conventional control ?
Thanks, Kyle Miller

Attachments

Images (2)
  • 2020-09-09 23.04.18: MTH MP15 diesel running on TMCC layout in conventional mode
  • 2020-09-15 23.58.58: MTH MP15 and RS-3 running with postwar ZW power conventional mode
Original Post

Replies sorted oldest to newest

It is locked in fwd and you need to do an unlock sequence with bell/whistle button.  Procedure in manual.  Or a conventional reset.  More problematic with an engine that wants to run at full speed.  You can lower your track voltage to about 10V to do it.

I would first go back to DCS and do a factory reset with remote.  That may resolve this issue.  If it still takes off after moving to Conventional track, follow advice above.  G

I have had similar issues with multiple MTH locomotives (but not all MTH locomotives). Specifically after operating in DCS the locomotive will not move when operated in conventional mode. The locomotive starts up but just sits still on the tracks. The solution for all of my locomotives that have this response is to do a feature reset when I am done operating in DCS mode and next remove power to the locomotive. Note DO NOT RUN the locomotive in DCS after performing the reset. This has solve the issue every time.

Being added to the DCS remote has no effect on conventional operation.  If there is no DCS signal on the tracks, 100% of your DCS locomotives should come up in conventional mode.

Take note of: If there is no DCS signal on the tracks

With all due respect, as your DCS and electronics knowledge dwarfs mine, here is my experience...

I have 2 completely separate layouts.  One has DCS, one doesn't.  Have added several PS 3.0 engines via the remote on the DCS layout - they run perfectly.  Powered down, picked up the engine, placed it on the conventional layout and powered it up - nada.  Put it back on the DCS layout, powered it up, then powered down and deleted the engine.  Put it on the conventional layout and it runs normally.  I just live with it.  I didn't think that the engine stored any information, but apparently that's not the case.

That's not a bug - it's a feature! 

Well, the engines do store information, they remember their ID and associated data.  That's the only way you could take that engine to another layout and add it to a remote and have it remember a customer altered engine name & number.

FWIW, I tried your experiment with two PS/3 engines, a steam and a diesel.  They both started fine in conventional after being added to the remote and run in command.

Last edited by gunrunnerjohn

Well, the engines do store information, they remember their ID and associated data.  That's the only way you could take that engine to another layout and add it to a remote and have it remember a customer altered engine name & number.

FWIW, I tried your experiment with two PS/3 engines, a steam and a diesel.  They both started fine in conventional after being added to the remote and run in command.

Thanks for the info about info storage in the engines.

Not sure what's different in your experience - my engines (all diesels in this case) are recent production - within the last 18 months, and my TIU has been updated fairly recently (don't ask which version).

Thanks very much everybody, John, Paul, Matt, GGG, Lou, Mallard  for your advice and guidance. Your solutions make great sense and I'm trying them now.

I have retested everything but suspect my TIU is problematic.

Starting over, I rewired a new loop on the carpet. I tested a postwar Alco  with a TW and ZW and all runs fine. I put the MTH MP15 on and it still went around in FWD only.

Connecting the TIU and DCS remote, my MTH engine powered up and moved a few feeble inches with the DCS remote. Testing the power up again, the TIU red light comes on, blinks once (indicating TIU address 1), then fades out. The DCS remote come up with a throttle setting of 19 (must be from my original session) but then did not respond to throttle wheel. Couplers fired, horn & bell OK. Then after about 3 feet it died.

I opened the TIU (labelled as PS2 production) to check for a fuse, as is stated in the current DCS manual, but can see none. I suspect this is the first edition TIU. Repeated attempts to connect, address and reset the engine failed, and I smell of hot electronics.

I am taking the engine to a friend's DCS layout tomorrow to reset, and we'll try again.

Thanks again for the help and expertise! More to come!

Kyle 

The TIU light going out is an issue and indicating a problem inside the TIU.  If your powering via Fixed one do you have voltage out when TIU LED goes out after blink?  Once that is out, remote and engine can no longer receive commands.

There are two separate memory in PS-3 that do not fully go to factory reset when doing a DCS Factory reset.  Hence the need for conventional reset.  Even back in PS-2 day, were were advised to do a DCS reset, then follow up with a factory reset conventional.  Then ship to customer.

I see this occasionally were engine works in DCS, but I have to do a conventional reset to get it moving in conventional.  The run away trains have been a rare occurrence, that I have not see this past year?  So not sure if it was a software bug, worked out in current flash codes.  G

Add Reply

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×