pushing the all button with lash ups doesn't seem to work. On 4.20 and latest TIU.
Clem
Original Post
Replies sorted oldest to newest
Clem,
If you're referring to ALL ENGINES, it works just fine with lashups under DCS 4.20.
How about you tell us exactly what you're doing and exactly what happens, and we'll proceed from there.
I put together three lash ups all diesel PS2. Three engines, two engines and two engines. As I built each one I let them idle until I was done, that left one active engine which I put on the inactive list. The trains where spread out on the mainline about three scale miles, I pushed the all button and nothing responded just sat there at idle, no horn or bell either. Would not shut down so i turned off the power until i could get back. Have not tried to start yet.
Clem
Before you hit the ALL button, did you first shut them down? I thought the all button starts them all together.
Clem,
Did you do the following (from page 99 of The DCS O Gauge Companion 2nd Edition):
Starting an All Engines Session
When starting an ALL engines session, it is important to first ensure that all of the engines that are to participate in the ALL engines session are on tracks that are receiving power and are in DCS mode. Next, press the READ key. This will ensure that only those engines that are drawing power will participate in the ALL engines operation by moving those engines that are drawing power to the Active Engine List and those that are not to the Inactive Engine List. Press the ENG key to see the Active Engine List.If operating using DCS release 4.0 and PS2 lashups are to be included in the operating session, move them from the Inactive Engine List to the Active Engine List and move their member engines to the Inactive Engine List.
If any engines are in the list that will not be included in the ALL engines operations, they should be moved to the Inactive Engine List by pressing soft key S1 (INA). Then press soft key S3 (ALL) to initiate the ALL engines session. If there is more than one TIU on the layout a list of TIUs will be displayed. If operating in Normal TIU mode, select the TIU whose engines will participate in the session. If operating in Super TIU mode, select any TIU. In either case, the Engine Control Screen will be displayed showing an engine name of ALL.
This and a whole lot more is all in MTH’s “The DCS O Gauge Companion 2nd Edition", available for purchase as an eBook or a printed book at MTH's web store!
Only active engines where used the other two where on inactive list. Whenever i do lash ups I have issues, usually i just put them on the track all facing the right directions and then just hit all and everything works. I might have a signal problem. This time when I returned, turned on the power hit start and they all started and ran when i wanted. Noticed they did not respond to throttle well, delayed horn, smoke on/off not working, bell not working, when shutting down Had to shut down each lash up separately. Found one engine still trying to pull(the middle unit) No sound, turned off Z4000 then it stopped.
Was getting check track message sometimes, during entire run. I did not push read button. One TIU. Also when after shut down I selected one of the lash ups to reposition,without hitting start, and one inactive PS3 engine started running also, been sitting there all this time.
Clem
Clem,
If you had any engines in the Active List that were not getting power, that will mess up the ALL session. You'll get Check Track errors and sporadic response to commands because DCS is trying to operate every engine in the Active List, whether or not it's getting power.
Pressing READ ensures that all unpowered engines go to the Inactive List. Then, if necessary, manually move all lashup members to the Inactive Engine List and all Lashups to the Active List.
Thank you Barry I will try again, when I get back from a trip.
Clem
Just one word of caution. As one who uses the "ALL" command everytime I run my trains (looper with normal TIU operation of 4 TIUs and multiple trains per loop), I have a dedicated handheld per loop and I never intentionally use the "read" command. In my operation, the "read" command sometimes does not see all engines on its loop and clobbers my MUs most of the times. This forces me to rebuild MUs and with almost every train having an MU (2 to 4 engines) it becomes a real pain in the neck. With up to 9 engines per loop, getting the handheld back up to running the loop properly usually requires at least hour to rebuild the trains after accidently depressing the read button on the handheld.
