Well here it is Christmas Day and I go to run trains, My remote says no engines on track and the engine that ran fine two days ago is inactive. Full voltage on track changed batteries in remote, I'm ready to sell everything. The Lionel system still runs fine and always has for years. Can anyone help or make me an offer I cant refuse. Very frustrated wit DCS.
Replies sorted oldest to newest
I have the same problems. I got a ton of Proto 2 &3. Hate trying to run them. The latest issue is the wiu. What a pain in the you know what
There is another thread regarding DCS issues.
I have an early Rev. L TIU being looked at. Very similar issues to this and the other thread. Operated PS2 and PS3 engines one day would not find them the next. And, the two engines on their separate loops came up in conventional mode.
The one software update that I had not done yet was for the WIU. I am being patient and will see what the technician has to say.
Billsrr posted:Well here it is Christmas Day and I go to run trains, My remote says no engines on track and the engine that ran fine two days ago is inactive. Full voltage on track changed batteries in remote, I'm ready to sell everything. The Lionel system still runs fine and always has for years. Can anyone help or make me an offer I cant refuse. Very frustrated wit DCS.
When you bring them from inactive to active do they run ok?
I can't get them off the inactive list.
I had the same problems. One engine would go active and run fine. I would shut it down. Come back an hour later. It would not respond. I’ve also had engines respond to remote but not Wi-Fi and vice versa. Lately with DCS it’s been a crap shoot for me to often. Very frustrating and i’ve entertained the same thought: get rid of it and my PS3 engines. What’s particularly frustrating is this problem exists with Wi-Fi which MTH is heading to use exclusively.
Just as an FYI...
DCS works just fine using the remote and TIU, or the DCS App, TIU and WIU. If it doesn't, the reason is almost certainly one of the following:
On a properly wired layout with properly functioning hardware, and the correct versions of all software and firmware, DCS just plain works.
 | Everything that you need to know about DCS is all in MTH’s “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store! |
 | Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" |
If you guys are selling, let me know. I am in.
Mind you MTH has a larger learning curve that TMCC/Legacy. But knock on wood, its pretty bullet proof.
Things NOBODY told me and I missed in the instructions:
1) Fixed one channel ALWAYS needs to be on
2) Do you see the red LED light? That is the watch Dog signal... this must be on at all times.
3) Before you run any trains hit the read function on the remote to confirm the remote is talking to the TIU
4) If your engines are off on a block powered track, there is a good chance it will not see the watch dog signal or not be found. make sure you block powered track is powered up before the fixed one port is powered on.
5) Make a programing track! You will be so happy you did.
6) Always check your track signal strength. I wired my layout with bus powered wiring with 3 foot drops. 9s and 10s around the 40 x 40 layout.
7) Only error I noted is the Voltage read on the remote vs. track was not the voltage measured. My track is always 3-5 volts lower
8) READ your manual, ask questions, go over all the functions. Own it. Once your confidence is up on using it you will be less confused.
MTH DCS is an Engineered software to run trains. It has much more flexibility and more capabilities than TMCC and Legacy, I like it. Now if MTH could only improve their sound files!
Bill,
If you drop your remote or even over time, the transceiver board can come loose and need re-seating. Try tethering the remote with a CURY telephone cord to see if you can move your engine from the Inactive list. If so, the board in your remote needs re-seating and it could also be the transceiver in the TIU. Just something easy to try first.
J Daddy,
You have a few misconceptions in your suggestions:
1) Fixed one channel ALWAYS needs to be on
Not true. The TIU can be powered via the Aux. Power port rather than Fixed #1 Input. In fact, doing so is preferred over always having Fixed #1 powered.
2) Do you see the red LED light? That is the watch Dog signal... this must be on at all times.
Half true. The TIU's red LED must be on at all times that you are running trains on any channel. However, it has nothing to do with the watchdog signal. That is issued any time the voltage on any TIU Output channel is changed from zero to any other voltage.
3) Before you run any trains hit the read function on the remote to confirm the remote is talking to the TIU
No, absolutely not a good idea, unless you want to send all of your engines that are on non-powered tracks to the Inactive Engine List.
4) If your engines are off on a block powered track, there is a good chance it will not see the watch dog signal or not be found. make sure you block powered track is powered up before the fixed one port is powered on.
That's true, however, if you turn on a siding's power and the engine comes up in conventional mode, just press either Startup to put it into DCS mode or Shut Down to make it go quietly into DCS "stealth' mode, with all lights off.
5) Make a programing track! You will be so happy you did.
Any track block is de facto a "programming track", as long as its center rail is insulated from adjacent center rails and no other engines are powered on when the DCS engine is added.
6) Always check your track signal strength. I wired my layout with bus powered wiring with 3 foot drops. 9s and 10s around the 40 x 40 layout.
A good idea, regardless of how you wired your layout.
7) Only error I noted is the Voltage read on the remote vs. track was not the voltage measured. My track is always 3-5 volts lower
That's not any kind of a DCS issue. It's typically a symptom of a large amp draw that causes voltage at the tracks to decease. (Voltage = Current X Impedance)
8) READ your manual, ask questions, go over all the functions. Own it. Once your confidence is up on using it you will be less confused.
Good suggestion! Even better, purchase a copy of one or both of the DCS Companion books! 
| Everything that you need to know about DCS is all in MTH’s “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store! |
| Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" |
Since yesterday I checked the voltage on the track,17., I could not get the loco off the inactive list. The sound came on and would respond to throttle but would not move. Everything was fine on Sunday. The TMCC and Legacy were fine. I deleted the locos and tried to reload them. The message was could not find new loco. Out of desperation I unplugged the Legacy signal booster , then tried the DCS. Things were back normal, I have loaded the engine back in and it runs fine. I sure glad my truck is more reliable. I sure would like some input here. Thanks Bill
Some, but not all, Lionel engines kill the DCS signal. You most likely have at least one that caused the problem.
Billsrr posted:Since yesterday I checked the voltage on the track,17., I could not get the loco off the inactive list. The sound came on and would respond to throttle but would not move. Everything was fine on Sunday. The TMCC and Legacy were fine. I deleted the locos and tried to reload them. The message was could not find new loco. Out of desperation I unplugged the Legacy signal booster , then tried the DCS. Things were back normal, I have loaded the engine back in and it runs fine. I sure glad my truck is more reliable. I sure would like some input here. Thanks Bill
This happened to me just last week with a Proto 2 SD70M I have. It would start up (sounds) and shut down (sounds), couplers fired and all, but that's about it, it would not respond to forward or reverse signals and wouldn't move a mm in any direction. Being a Proto 2 engine (5V), I decided to check the battery but it was fine.
I put the engine on my test track, and using my DCS remote, did a full reset (or maybe a feature reset) and it came right back up. I believe that adding the engine to multiple MU setups was my issue, the engine had begun to give me issues a while back and it finally gave out when I tried to set up another MU with other units. To clarify, i have used this as a helper engine before with other consists, when I tried to make a different MU with different engines, it would not respond at all, the other engines would just drag the SD70 around (which I did't allow to continue for too much distance).
In any case, my full reset (or feature reset) using the DSC remote, brought it back to life.
Hope this helps!
P.s. Barry is right about the test track, you NEED one, BUTT K,I,S,S doesn't agree with his setup. I think a 30" section of good ole Lionel tubular track on a bench connected to a TIU output is the best method as it eliminates a lot of possible layout wiring issues. This is how I have it set up and as you can see I got me engine back up and running.
Joe Allen posted:Some, but not all, Lionel engines kill the DCS signal. You most likely have at least one that caused the problem.
From what I have read in the past, this issue pertains to TMCC and not Legacy or Lionel. Any TMCC engine can interfere with the DCS signal, GRJ has even recommended to install the RF chokes on anything track powered, even command switches. I have followed the warnings, to date I get all 10's on my layout, be it a small one at that. All of my TMCC engines have RF chokes installed on the pickup roller wires as to combat this issue as well as all of my AC/DC circuits I build to power my LED building lights. Heck he even recommended to install it on a few passenger car LED conversions I did, and the chokes are there as well.
Hope this helps!
Daniel J. Gonzalez posted:Joe Allen posted:Some, but not all, Lionel engines kill the DCS signal. You most likely have at least one that caused the problem.
From what I have read in the past, this issue pertains to TMCC and not Legacy or Lionel. Any TMCC engine can interfere with the DCS signal, GRJ has even recommended to install the RF chokes on anything track powered, even command switches. I have followed the warnings, to date I get all 10's on my layout, be it a small one at that. All of my TMCC engines have RF chokes installed on the pickup roller wires as to combat this issue as well as all of my AC/DC circuits I build to power my LED building lights. Heck he even recommended to install it on a few passenger car LED conversions I did, and the chokes are there as well.
Hope this helps!
This only one of many that say different:
Joe Allen posted:Daniel J. Gonzalez posted:Joe Allen posted:Some, but not all, Lionel engines kill the DCS signal. You most likely have at least one that caused the problem.
From what I have read in the past, this issue pertains to TMCC and not Legacy or Lionel. Any TMCC engine can interfere with the DCS signal, GRJ has even recommended to install the RF chokes on anything track powered, even command switches. I have followed the warnings, to date I get all 10's on my layout, be it a small one at that. All of my TMCC engines have RF chokes installed on the pickup roller wires as to combat this issue as well as all of my AC/DC circuits I build to power my LED building lights. Heck he even recommended to install it on a few passenger car LED conversions I did, and the chokes are there as well.
Hope this helps!
This only one of many that say different:
Hey Joe,
That thread is talking about an issue with a legacy base, not legacy engines my friend.
TMCC engines traveling in close proximity to a DCS engine would make the MTH unit unresponsive. On the other hand, I do the same test with an unmodified legacy engine and don't experience the same issue. Although I said I was not 100% sure, and I appreciate the link to the thread, I still stand by what I said, I believe TMCC is the only really issue when it comes to DCS signal interference.
Another member on the thread you sent said he was experiencing the same issue as GRJ and simply swapped the legacy base with another and his problem was solved.
Thanks for the link though!
Bill,
I unplugged the Legacy signal booster , then tried the DCS. Things were back normal, I have loaded the engine back in and it runs fine.
That tells me that the problem is obvious - the Legacy signal booster is causing the DCS signal tp degrade considerably.
Daniel,
From what I have read in the past, this issue pertains to TMCC and not Legacy or Lionel.
I believe TMCC is the only really issue when it comes to DCS signal interference.
The issue is not dependent upon any particular manufacturer, however, it does pertain to both some TMCC engines and some Legacy engines.
| Everything that you need to know about DCS is all in MTH’s “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store! |
| Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" |
Barry Broskowitz posted:Daniel,
From what I have read in the past, this issue pertains to TMCC and not Legacy or Lionel.
I believe TMCC is the only really issue when it comes to DCS signal interference.
The issue is not dependent upon any particular manufacturer, however, it does pertain to both some TMCC engines and some Legacy engines.
Everything that you need to know about DCS is all in MTH’s “The DCS Companion 3rd Edition!"
This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!
Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!"
This book is available from many fine OGR advertisers and forum sponsors, as an eBook or a printed book at MTH's web store!
Hey Barry,
The issue is not dependent upon any particular manufacturer, (Yup, that's why I said "not Legacy or Lionel", meaning the issues didn't pertain to Lionel per say, any manufacture that used TMCC electronics would cause the issue.) however, it does pertain to both some TMCC engines and some Legacy engines. (Well I will take your word for it over mine, I am the rookie on the matter but in practice, I have never had this issue with any of my 4 legacy engines and all 6 of my TMCC engines did destroy my DCS signal when in proximity of the DCS engine. You learn something new everyday!) 
In any case I am heavy MTH becasue of my LHS so I hope not to deal with this anyway.
Thanks!
GRJ mentioned "chokes" as helping the TMCC interference with DCS; is this helpful in general operation or just with WIFI ops? Exactly what choke; what do I order? thanks.
Wally
Access to this requires an OGR Forum Supporting Membership
