Uupgraded DCS and lash up still gets lost

Is the engine battery charged.  Does it play shutdown sounds when you turn off track power?   G

Yes, all else is normal in the sense each engine in the lash-up can be started individually, but only the lead engine starts up as the lash-up.  Batteries are full up in both.

What kind of a track signal do you have?     Lash-up require the watch dog signal to move (they are a few work arounds) but... Make sure the  engines see the watch dog signal. 

You could give both engines the same ID and would not  have to worry about the watch dog... (double everything)    It's just an option and not a fix.

Did upgrade to 4.3 or 5.0?

Gregg posted:

What kind of a track signal do you have?     Lash-up require the watch dog signal to move (they are a few work arounds) but... Make sure the  engines see the watch dog signal. 

9-10 with it sitting still.

Riverrailfan posted:

Did upgrade to 4.3 or 5.0?

4.3

Gregg posted:

You could give both engines the same ID and would not  have to worry about the watch dog... (double everything)    It's just an option and not a fix.

 

That's something to try ; thanks Gregg.

GGG posted:

Is the engine battery charged.  Does it play shutdown sounds when you turn off track power?   G

Yes.  Batteries are both charged.

It seems to vary depending on if the engines were added and the lashup built on a track connected to TIU 1, Fixed 1.  If done on a track connected to TIU 1, Fixed 2 ... it gets lost when set on a dead track for a session or two.  Usually only the front engine will respond.  The second engine is not starting or responding in lash-up  mode, but will start up and run as an independent engine.  Continues to be vexing.  Using the save settings file softkey doesn't appear to make a difference.

Kerrigan posted:

Riverrailfan posted:

Did upgrade to 4.3 or 5.0?

4.3

I would try updating to 5.0. 4.3 has lash up issues but I'm not sure if it was you are experiencing but 5.0 is supposed to address lash up issues that 4.3 was having.

Riverrailfan posted:

Kerrigan posted:

Riverrailfan posted:

Did upgrade to 4.3 or 5.0?

4.3

I would try updating to 5.0. 4.3 has lash up issues but I'm not sure if it was you are experiencing but 5.0 is supposed to address lash up issues that 4.3 was having.

Being the UN-lucky, non-electronically inclined individual, I had a terrible time getting the entire layout upgraded to 4.3, so I was really hoping to avoid having to "chase the monkey around the tree" again upgrading for the WiFi App I don't need.  Don't know why, but it took the better part of 1-1/2 days of effort to finally get it working under 4.3.

On the otherside, I'm pleased to report this layout has never had a problem with the TMCC side; always worked, never needed upgrading.

5.0 also fixes bugs that were in 4.3. I never updated a TIU or remote till 5.0 came out. It was less that 30 minutes to do.