Lashup A-OK, but not the individual engines - why?

Alex,

I wanted to see the INFO on the two powered engines, so I tried to access them, but this resulted in "ENGINE NOT ON TRACK". I ran the lashup to a different location, but still the individual engines were not recognized.

Please describe exactly what you did and exactly what happened.

I've been testing for the last  15 minutes , After creating  a 2 engine lash-up, I could bring each engine out of the inactive list and start it up.  Some times the whistle would not  blow on the trailing engine.   Volume  going all over the place when switching  between the lash-up & individual  engines. 

 I couldn't find the "info" soft key anywhere.... Where is the "info" suppose to be?

Barry -

(CAVEAT: When you take your car to the mechanic because the engine has developed a squeak, rest assured that the noise will stop as soon as you arrive at his workshop.)

I ran the 2-engine Lashup as detailed below, and everything ran fine. I recorded a video of it. 

1. Engine (Lashup) found on remote - Start - volume OK - whistle OK - bell OK - ditch lights OFF but back ON after using MENU - CONTROL - Ditch lights ON. Run Fwd OK - Run Rev OK - Shut Down. 

2. ENGINES on remote - the only active engine listed is #2, the Lashup. Found the two Lashup component engines in the inactive list, tried to select them, but ENGINE NOT ON TRACK message appeared for both individual engines. And yet, they had just run fine as part of the Lashup. 

3. Deleted Lashup - Display: NO ACTIVE DCS ENGINES. Pressed READ, same results.

4. Deleted both engines and added them back, both added with their former address numbers, #24 and #25, but #24 had no name; just #24. I edited it and added the name as had been previously.

5. Was able to get the INFO on each engine:

#24 ODOM = 423.8, BATTERY = OK, CHRONO = 157.20

#25 ODOM = 267.6, BATTERY = OK, CHRONO = 49.32

6. Ran each engine individually, and all the features worked fine. Recorded video.

7. Recreated the Lashup, and it was 'awarded' the same address as before, #2. (All of the preceding steps and results have occurred at least four times in the past two days.)

8. Ran the new Lashup fine, everything worked OK.

9. However, unlike had happened previously, this time I was able to access the individual engines and obtain INFO on each:

#24 ODOM = 424.4 BATTERY = OK, CHRONO = 157.49

#25 ODOM = 268.4, BATTERY = OK, CHRONO = 49.51

Why where they ON TRACK this time and were accessible? Because Barry asked!

Will tomorrow be a different story? We'll see; I have left everything as it was, and will give it another try.

Thanks!

Alex

Alex,

Some very specific questions:

• Are you operating in Super TIU mode with multiple TIUs?
• What version of DCS are you using?

Good morning, Barry - (well, almost)

Version 4.2. and as far as I know, yes; super TIU for two TIU's  for the past five years and running fine except for the occasional hiccup.

HOWEVER, this morning things are not as good as they were last night, when everything was running fine.

Keep in mind that I left the engines on the same track as when I 'parked' them last night after several successful runs of the engines, individually and together as a Lashup.

After powering up, the remote showed that one engine had gone to the inactive list, while the other engine and the Lashup were on the active list. I successfully moved the one engine from the inactive list to the active list. This engine started fine, but when I moved the thumb wheel one notch, the engine took off at full speed. I tried several different times, but the same thing happened. All other functions were fine. 

The engine that remained on the active list ran just fine. No, I did not take a chance with the Lashup as I am 99.99% sure that the 'full-speed' engine would just try to go full speed and drag the other engine along.

I just read (here in the forum) a couple of threads regarding the full-speed problem, and will take a look later today.

Is there anything you would care to suggest?

THANKS!

Alex

Alex,

As I suspected, you're seeing a bug that's been corrected in DCS 4.30 and DCS 5.0.

The bug is that if an engine is moved into the Inactive Engine List when it's sitting on a track connected to a TIU that isn't the one with which it was associated when it was last added to the remote, it cannot be made active.

The work-around solution is to physically move the engine to a track connected to the TIU with which it was associated when it was last added. Then, it can be promoted to the Active engine list.

The permanent solution is to upgrade to DCS 5.0, wherein the bug (and a few others) has been eliminated.

This and a whole lot more is all in “The DCS Companion 3rd Edition", available for purchase  from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store!

Alex,

 This engine started fine, but when I moved the thumb wheel one notch, the engine took off at full speed.

That's a different story.

I suggest that you do the upgrade first and then revisit this issue, if it still exists.

That makes sense, Barry.

I will upgrade to 5.0 before I do anything else, and will report back.

Thx - Alex

Barry,

Successfully upgraded both TIU's and both Remotes to 5.0. I removed the TIU's from the layout, and took them together with the remotes, to my desk, where I upgraded them. I had a separate 18v supply to power them up. 

Unfortunately, this does not appear to have any effect on the problems I had experienced. The ES44AC engine that went from 0 to max in one wheel step still does the same. As far as multiple units or Lashups, I have another one that I have been running for a long while, a Union Pacific that consists of an AC4400CW and an ES44AC. These engines run fine as a Lashup, but when I tried to access them individually (a few minutes ago), I had the same message as I previously had with the BNSF Lashup - ENGINE NOT ON TRACK - for both engines!

Anyway, I am glad I have the system updated, and I will take a look inside the BNSF ES44AC to see if I can find the cause for the lack of speed control. This engine always has been a fine running engine, as are the rest.

Will appreciate any further words of wisdom; especially related to the lack of speed control of the one engine, which malady just surfaced earlier today.

Thx!

Alex

Hello Alex.........I have been having this problem with engines taking off at full speed with one throttle step. Two engines,  both are PS3 switch engines U25B and RS11, didn't do it before, but now happens regularly, all others just fine .   So I'll be monitoring this thread,  

Thank you and good luck.

Clem

Alex,

Regarding the engines not being found, does that happen only when the lashup is active or all the time?

The engine taking off at full speed is an engine problem, not a DCS problem. However, you could try doing a Factory Reset to the engine and then re-adding ti to DCS.

If that doesn't correct the problem, it's possibly a problem with the engine's tach reader or timing stripes.

Maybe time to check out the batteries in each engine by editing the address of the engines in question and seeing if they remember the new  address after a minute or so of  layout power down.  You can put the address back to what it was and it only takes a second or so do outside of the track power down.   We  add all our engine to tiu #1 using a dedicated programming track  so that the engines are always  associated with tiu #1.

Barry, Greg -

Resetting the engine, whether feature or factory, did not have any effect. I have been able to 'find' all 12 engines I have on the layout now, although some displayed 'Required Maintenance'. I have another nine on the shelves, which I will have to test as well. I have received the SuperCaps and will start changing them. Oddly enough, the batteries I checked using INFO tested OK.

As far as the engine with no speed control, I looked at it again, but did not find anything obvious, so I will send it out to be repaired - maybe.

I do thank you!

Alex.

I have been able to 'find' all 12 engines I have on the layout now, although some displayed 'Required Maintenance'.

Yes that pesky message shows up every now & now...Easy fix... Go to the engine's soft keys  and find maintenance  ( under the more) Press RST  to reset it.   (whether you lube/clean  or do anything is up to you)

PS I'm really happy with version 5. best one yet for super mode runners.