Lash Up - error "Engine not on track"

Ted,

I tried on wi-fi as well - was able to create lash-up but when i tried to start-up - same result "Check Track"

I don''t believe that's the error message that the DCS App generates.

Please say exactly what you did to build and operate the lashup, using both the remote and the app, and exactly what were the results.

Also, please verify which platform you're using with the app, iOS or Android, and that the app is version 3.0.2 and the WIU is at firmware 1.1.

hi barry

here is what i did

track power on, two engines in active engine list, go to create lash-up, add eng-selected one of the active engines, selected front engine, forward diretion, then added second active engine -back engine -forward direction - then named lash-up and <D>.  DCS remote says saving lash-up - then when i select the lash-up any pressing the scroll wheel - it shows up in my DCS remote screen as I labeled it and with the (L) showing it is a lash-up.  i then press the start-up button and get a message "check track", then "engine not on track"  

the wifi app v3.0.2 on iphone, wifi firmware 1.1

What about when building and operating with the app?

is this still the same remote?

https://ogrforum.com/...urred-and-can-t-read

it says "command failed"  after i selected the lash-up engines, named etc - this was using the wifi app

no the remote is a new one - i got MTH to fix the other one - but  not using the one that got the screen repaired

Did you load new software into the remote? What version?

Different versions won't get along fully and this could be an example. What version of DCS is loaded into the TIU?

the remote has version 6.0 - the repaired one has 6.1 - but i can easily run the two engines using either the DCS remote or the wifi app.  they work fine and respond to all the commands - only get this issue when i try running a lash up

my layout is basically an oval 12 ft by 10ft

the engines after deleting and reinstalling go in the same numbers spaces - i cleared all the engines in the remote and the engines i am using go into #3 &#5 slots

What DCS version is in the TIU?

TIU is 5.0l

WHOA! no wonder you have this. I'm surprised they work at all.

so you think the TIU should be updated to 6.1 and that will solve the issue?  interesting that the engines work fine when i s/u using the remote

Yes, I'd have to guess at that. There are constant changes to DCS versions. One thing that happened was first trying to get PS2 and PS3 engines in lash-ups to sync in the correct direction. Then, the app came along and things got updated again.

 So with 5.0 having some issues, 5.1 and then 5.2? Now 6.0 and 6.1 I believe?

So your TIU is 3 or 4 releases behind. One did not change the remote much but it did make changes to the TIU to get along with the app.

ok thanks - i will update and hopefully it will work

Ted,

TIU is 5.0l

That's your problem. The DCS App specifies that the TIU must be at DCS 6.1.

i updated the TIU and now my DCS remote and TIU are 6.1  tried it again and the lash-up worked - i had the TIU replaced a month or so and thought it had the most up to date version - i was wrong - appreciate all of your help - sorry it was something so simple   thanks again

All, I know this is an old post but I have the same lash-up issue as Ted. When I follow the instructions to create a lash-up, I receive the engine not on track error message. However, I can run the All Command perfectly.

My DCS Remote version is 6.10 but my TIU code is 4.20. How can I upgrade the software version for my TIU? I'm not technically savvy. Thanks!

DCS Version 6.10 Software Upgrade Revision | MTH ELECTRIC TRAINS (mthtrains.com)

download the latest DCS 6.10 software and make sure you have the latest DCS Loader on your computer.

If your TIU is a version "L", it has a USB port for connecting to your computer. Older ones need a serial port adapter cable.

go here and pick DCS support videos in the top headings

https://mthtrains.com/service-videos

and then

the DCS video of using the loader

https://mthtrains.com/dcs-loader-program

Unfortunately, it's the older version TIU with the RS-232 PC serial port. Today's laptops do not have serial ports anymore. However, I could purchase a serial to USB adapter if they exist.

yes, and you'll have to get one.

Do a search here on the forum for the proper one to get

USING DB9 SERIAL TO USB CABLE FOR CONNECTING TIU TO COMPUTER | O Gauge Railroading On Line Forum (ogaugerr.com)

@pdash posted:

Unfortunately, it's the older version TIU with the RS-232 PC serial port. Today's laptops do not have serial ports anymore. However, I could purchase a serial to USB adapter if they exist.

If you do order one, I recommend the USB-Serial adaptor (U209-000-R) from Tripp-Lite. They still use the FTDi chip which is also compatible with the WIU if you ever add that to your DCS system. Tripp-Lite also includes a driver disc with drivers for Windows XP through 11 support.

Thank you all for your advice! I will be ordering the Tripp Lite cable from Amazon.

Actually I do have a USB cable. It is the USB Type A/B cable that I need. I see Tripp Lite makes that as well.

Wow!  I think this is the same issue that I had a week ago and didn’t post the original issue and that was the lash up engine not on track error.  That is what started me down my post of chasing down a DCS signal strength problem of an AA pair with differing RF out of range messages. When I read this title from 6 years ago and @pdash issue and @engineer-joe response it was obvious.  I checked my remote and it’s 5.0. Tomorrow I think I update to 6.1.  Thanks for the unplanned assistance.

This thread should be shared throughout the DCS WORLD!!!

         Thank you

Interesting thread. And good advice to always use the same software version in both the TIU and handheld.

One very annoying thing about DCS is you can have a lashup working perfectly one day, then park it on a siding overnight, and the next day (or week) you get “Engine Not on Track” What? Where did that come from? And no amount of retrys or track Reads seems to make any difference. A couple of times I have had to power the lashup up in conventional then move it out to the mainline somewhere and hit Startup to get it working properly. Once this happens all is well again. Weird.