Hump Yard assets

PapaCharlie62

Active member
I downloaded all the assets for CDE Hump sorting, but the CDE Wagon Tags Display Rule, <kuid:647907:100954> and Input Table <kuid2:131986:1012:1> do not show up under Edit Session or Create Session. Not sure what to do about them.

On the other hand, I also downloaded MSGSappers Hump Yard Kit assets they work pretty well, one car at a time.

Like everyone else that has issues, I read as much as I could, but nothing like I am experiencing with the CDE assets. These are for a new route I have been working on for 2 months and decided to add a Hump Yard.

Any thoughts or ideas?

Run 8,
PapaCharlie62

Never mind, I figured it out. Have to "Add Rule" under Edit (or create) Session (at the bottom of the screen).

I have decided to use MSGSappers Hump Yard Kit, easier to use even one at a time gets the job done.
 
Last edited:
Hi Christopher824

Thanks to Trevor and yourself for producing these assets. Do you have any instructions on how to use the assets in Flat Sort mode please? I've found the hump yard assets very useful but it would be helpful to me to be able to use them in non hump yards as well.

Regards

Brian
 
Hi Brian and Chris - It is a long time since I used these assets. The only major difference between flat sorting and hump sorting is that there are trackmarks placed after the last junction in each branch of the fan. These are to help in stopping the consist when it has gone far enough. The TM names are unimportant as long as they contain an asterisk in the middle that is used by "Approach Target Mark" (ATM) driver command to: "Couple or stop at first *TM". Example: Track *1. And you don't need speed retarders.

I found out (by enabling the ATM debug option) that pairs of trackmarks need to be placed, one at each end of the tracks that hold the sorted wagons. Again, the only criterion in the trackmark name is the asterisk.

You position the trigger facing the fan of junctions and set up the range for each leg. Each subsequent junction has its own trigger and range settings. The wagons must be tagged with numbers so that the trigger can decide which way to switch the junction. The loco then pushes the consist past the trigger, which should calculate the length of the wagons included in the shunt. A session variable: move_length_ stores the distance to move past the trackmark and another, consist_count_ stores the position of the wagon to be decoupled.

After the consist reaches the trackmark, Driver Command "Approach Target Mark" is used to "Move forward the calculated distance". Then Decouple DLX decouples at the position stored in session variable "consist_count_".

Setting up a schedule for completely automatic shunting is tricky and I may never have finally come up with an bug-free working session.

The trigger debug option shows the workings of the decision logic for each trigger.

My assets have evolved a lot since that time and I have been working on a different set of commands to do flat sorting without using triggers. You may e-mail me if you have questions.

Best regards - Trev
 
Last edited:
Hi - I edited the instructions to correct errors but have not verified that they are correct or complete.

Thanks for responding, Chris.
 
Hi Trevor

Great to hear from you again. Many thanks for the explanation and will have a play with them later today. The instructions look clear enough but I'll see how I get on with them.

Many thanks

Brian
 
Back
Top