Skip to main content

Good morning

One unit #23 of a six unit lash up quit working. This was a middle engine. Tried to start and run by itself nothing happened  ENGINE NOT ON TRACK message, will start up in conventional but no response. I hear a faint double click when power is turned on. Sounds last a long time after power is cut. Now I can not get lash up #6 to come up onto active list. message LASH-UP ENGINE#23 WAS NOT FOUND. The lash up engines will start independently. Anything I can try, before I send in?

 

Clem k

Original Post

Replies sorted oldest to newest

Clem, You say it starts up in conventional, but no response.  What do you mean?  Have you tested the engine in conventional mode no DCS?.  Can it start up and operate?  If not do a conventional feature reset.  Need to determine if engine is working.  If not, it may have an issue.

 

I assume the lashup is not working because Eng #23 is not found.  On a separate test track with DCS you could try to add the engine, or do a recover engine.  I don't know if you would have to delete the lashup before doing this, or just use a remote that did not have the engine or lashup installed.   G

Barry and GGG

 

Operating system is 4.20…..One TIU….Normal... 180 brick

The engine will startup sounds and some lights like it is still in Lashup shows up on screen as #23 will not respond to any commands so I can't do a reset from DCS remote. I did a read but did not show up at all, It also showed up in address #6 as a lone engine in a remote I wasn't using. Ill try starting on my test track in conventional with a Z1000

Thanks

Clem 

 

Clem,

 

Delete the engine from the remote. That will also delete the lashup, as well as any other lashups of which the engine is a member. This is unavoidable.

 

Then, make sure that the engine has a fully-charged battery. Do this as follows:

  • Place the engine on a conventional track, not a track that has a DCS signal
  • Turn on track power. The engine should start up in conventional mode
  • Turn off track power. If sounds do not persist for 6-7 seconds, charge the engine's battery until they do.

Next:

  • Add the engine back into the remote
  • Start it up
  • Shut it down
  • Turn track power off and then back on
  • Start up the engine. If it starts up, proceed to rebuild the lashup.
Last edited by Barry Broskowitz

Let me  us know if these things keep going wrong. I had these type issues and I went back to 4.2

 Everyone else thinks 4.3 is OK?

I had nothing but issues with large consists. Some engines wouldn't come up to the active. Some would only out of their consists. I had a whole list of other issues.

 When I added some engines, the lights, smoke, & sound presets were all over the map. I shouldn't have to reset and engine that was just added to a new remote. I did more than normal, with 4.3!

 I rebuilt my consists because lights were acting up. After rebuilding and cycling the power, the consists would not work. Always some issue that did not make sense.

 Single engines worked fine under 4.3

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.
×
×