Check Consist Rule - Humpyard

[Dap]

Here are links for the latest release. Hope to have 2.0 next month.

CMTM Article

CMTM User's Manual 0408 Release

CMTM System Files CDP

 

[trev999]

I am looking at various ways of implementing a rule to aquire the running number of the vehicle at a trackside object and running child rules to switch junctions.

There are several ways to approach this and a rule usually evolves rather than being specified and written, at least when I do it!

I have downloaded the humpyard kit and find that it is not necessary to use an "Uncouple at trackmark" as the humptower does the decouple anyway.

There are questions I would like to know concerning the choice of running numbers: Do you guys care about what the numbers are for prototypical reasons?
Would you be happy to use the same running number for all vehicles going to the same destination or would we need a range for each destination? Single numbers are easier but would need to be typed into the rule at set-up time. It would be like using the running number as a destination number.

RN's can be assigned in Surveyor (TRS2004) but are not shown in Driver using view details. Has that changed in later versions?

The running numbers are preserved when saving the consist and the train could be built up of several consists chosen at random by a portal or portals.

This process could take quite some time, however I am busy trying out parts of the rule and will bump this thread when I have some useful.

@DAP - Will have to spend some time studying your CMTM package to see how it ties in.

Cheers - Trevor

 

[Dap]

I beleive tha emcnally has a working humpyard using CMTM. You might drop him PM to see how it is working.

 

[Crumpet49]

Hi Crumpet49 - I am not familiar with "Check consist at trackmark" but have another idea. It is possible to assign running numbers to vehicles.

The destination table might be something unique to the Hump kit, (not familiar with that either) but it sounds to me like they might make use of the Worktable rule, which allows free-form data tables to be created. They are used with driver commands like "Velocity Controlled Drive to Trackmark" for setting up speed tables.

Now one could set up a "Running number range" table with format:

Rn, t,x,mmmm,nnnn

where Rn is the rule identifier, t the trackside mark, x the range number and mmmm & nnnn the starting and ending running numbers of that range, then all that would be needed is a rule "Check Worktable" (which needs to be written) which can execute a set of child "SwitchJunction" rules when the running number of the vehicle falls within the specified range.

If this method of sorting vehicles is in line with what you want, I will look into producing a rule that does the job, but don't hold your breath!

I have only TRS2004 currently so much of the new stuff on DLS won't load on my machine. Also, I am on dial-up ISP so I don't hang around on the forum.

Cheers - Trevor

Hi Trevor,

Yes a system for checking running numbers would be ideal! That gives a lot more flexibilty for the system! I would be very very grateful if you or anyone else could look into creating this, I imagine it would be very useful for a variety of uses, as well as in a automated humpyard!

Thanks again!

 

[trev999]

New rule ready for testing: Check Running Number

Hi All - I have finished the first draft of the rules required to sort trains automatically by running number using a humpyard.

If anyone is seriously interested in beta testing these rules please send me an e-mail so I can sent the package.

e-mail trev999@gmail.com

Cheers - Trevor