Strange Issue, Engine not adding to DCS also lash up issues *Update*

Greg,

More information, please:

• DCS App platform, iOS or Android?
• Connection, MTH or HOME?
• DCS App software version?
• DCS TIU software version?
• WIU firmware version?

Barry,

iOS app

MTH Connection

App version v3.0.2

DCS version 6.0 

don't know the WIU firmware version. It was purchased within weeks of the initial release. Ive never done any kind of upgrade.

Another thing to note, I am using 2 TIUs in super mode with 2 WIU units. The system seems to be working. I am able to run other locomotives without any issue.

Maybe try the recover engine feature with the dcs remote... Must be TIU #1 and probably a good idea to have no other engine receiving power anywhere.

Greg,

DCS version 6.0 

The latest DCS App 3.0.2 requires DCS 6.1.

don't know the WIU firmware version. It was purchased within weeks of the initial release. Ive never done any kind of upgrade.

If it isn't firmware 1.1, all bets are off.

Another thing to note, I am using 2 TIUs in super mode with 2 WIU units. The system seems to be working. I am able to run other locomotives without any issue.

I've found and reported a bug using lashups in Super TIU mode. To avoid the bug, make certain that both engines are associated with the same TIU.

Also, if you have issues where the lashup engines "fight" each other directionally, after startup, tap the Reverse and Forward arrows a couple of times.

Thanks,

I will make sure to upgrade my TIUs to 6.1 asap. I also see the firmware upgrade on the MTH site as well. Hopefully these will solve my issues. And it appears this will help with my issue running legacy locos with the app too.

OK, so all the system updates are in place.

App ver 3.0.2

DCS 6.1

Wifi 1.1

Im able to add, start and run other locomotives but the Proto 2 K4 will still not add to the list. It is receiving the watchdog signal and is starting up dark when power is applied. Any additional things i can try? Im wondering if resending the sound file to the loco would do anything?

Can you use the loader to find what address is stored on the engine's memory?

I would then make sure that address is open by editing and moving anything in that address so it's open.

Does the engine run in conventional? Does it play full shut down sounds when the power is killed?

I'm just fast reading this but it sounds like a dead battery so far.

If it is, this is not weird and actually makes sense. When you added it the address change probably did not stick. So later, nothing could find it. The board is doing what it should now. Staying dark at power up and waiting for a command that never comes. With a dead battery everything becomes a battle. There is a bug in an older DCS version that maybe still is showing up here? The cure was to toggle the direction button in the lashup to tell each engine to go in the correct direction. With the battery being dead, that proto 2 engine lost it's running commands and/or settings of the lash-up.

 I was researching if there was a bug with the app that set the engine's address in a lashup, that made it so the remote would not find it? Something was happening that made it so the remote and the app lost engine's associations to the TIUs after building a lashup. It even happened just by upgrading DCS in the system and things didn't work right after this.

 The issue seemed to go away with the latest releases or it was just the way I use my system to run different scales? I have many engines and lost track of addresses so I might have been wrong about this. I did not post it as after I changed the way I use my system, the problem went away. It was frustrating while it happened and I never identified the cause.

Greg,

If the engine cannot be found by either of the remote or the DCS App, a Recover Engine may be in order. However, if one device does find it and the other does not, that isn’t the issue.

Joe, I don't think the battery is an issue. I tried to replace the battery with a bcr right when this first started and that did not yield any different results. It does run totally normal in conventional. 

Barry, Neither the remote or the app can find it.  I have never done a recover engine. I will give that a shot. I'm sure it is covered in your book right? I have a copy that I keep right next to my TIU just for when these situations come up.

Greg,

It's on page 174 of The DCS Companion 3rd Edition and on pages 115-117 of The DCS WiFi Companion 1st Edition.

Thanks Barry!

The Proto 3 was in front Proto 2 in the rear. The rear was pushing on the front loco resulting in throwing a traction tire, one would randomly go into clickety clack mode, smoke would go off in one.. i would try and turn it back on the other would go off, turning smoke o and off would result in marker lights going on and off.

Thanks!!!

 

 

 

Ok, sounds like you know what's going on. I will let Barry help u.

I tried the recover engine feature this weekend and that didn't work. I think the reason why is because the TIU that was originally associated with this locomotive was damaged (in an unrelated short that blew out the internal fuses) so i was truying to do the reset with the new TIU that was added. I did try and connect the damaged tiu to a separate section of track and power just that piece but still got no signal and was unable to attempt a reset with it. 

So, my next question is would i have to bring the loco to an MTH tech and have them wipe out the memory on the board and reinstall the sounds? Or in there any other options i can try myself?

Greg,

I tried the recover engine feature this weekend and that didn't work. I think the reason why is because the TIU that was originally associated with this locomotive was damaged (in an unrelated short that blew out the internal fuses) so i was truying to do the reset with the new TIU that was added.

If you were using the DCS Remote to attempt to recover the engine, the TIU must be TIU #1 (1 blink of the red LED when power is applied to the TIU). If it is any other number, the recover engine attempt will fail.

However, if you attempt to recover the engine with the app instead of the remote, you'll have an opportunity to tell the app which TIU number upon whose tracks the engine is residing.

You can either change the TIU's DCS ID# to 1 and retry with the remote or try using the app. Instructions for using the app to recover an engine.

From page 180 of The DCS WiFi Companion 1st Edition:

To reset a DCS engine with a DCS ID# that is outside of the normal range, proceed as follows:

• Set the engine on a track connected to a TIU with a strong DCS signal and provide power to the track. You should not have any other engines powered up on any track connected to that TIU while attempting to recover an engine
• Navigate to the DCS Application's Recover Engines Screen.
• Tap on the TIU that is connected to the track upon which the engine to be recovered resides.
• Tap the Recover button. The DCS Application will display that it is attempting recovery of a lost engine.
• If the DCS Application is able to recover the engine it will display Engine Recovered. The newly recovered engine will be automatically Factory Reset by the DCS Application.
• The engine may now be added to the DCS Application as described in Part VII - Engine Operation Using the DCS Application, 1. DCS Application Engine Control Screens, DCS App Add Engine Screens earlier in this book.
• If the DCS Application is unable to recover the engine it will display No Engine Recovered. If this occurs, then there may be an issue with this particular engine. Contact your local service center or MTH for service options.

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st 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! Get the free TMCC & Legacy Addendum here!

The TIU was set as #1. I tried doing it with both the remote and the app. Both gave me a message that there was no engine to recover.

How about a remote reset and a programming track with no other engines receiving track power... Yep A remote reset deletes everything but gives you a clean slate eliminating any ID conflicts.

I tried that setting up a separate program track. Nothing else had power or signal going to it. Tested with a different loco that was already in the app and that started up fine. was able to get the k4 to start up dark on the test track but would not reset, recover or ad as new

 Usually A remote reset helps.  

I feel like the combination of running the lash up with the older software versions and the TIU dying/being replaced put this loco in an odd situation. Everything that SHOULD work isn't working. 

I was finally able to get this issue resolved. Turned out when we replaced the main TIU on the layout we never properly changed its aggress to 1. Thats why the recover engine was not working.  So with a properly set up TIU I was able to reset and get all of my functions back!

i just wanted to say THANK YOU!!!! to all who responded and offered advice. It was greatly appreciated!