For the attention of DAP regarding Path Rule

[Kennilworth]

Hi David

There are two path rules, “jsTRF Path Control” by brummfondel (kuid2:192081:16:2) which is on the DLS and “Path Rule” by _mutton_ (kuid2:71155:60006:4) which is built in to later versions of Trainz.

They both work in a similar way, the main difference being that the brummfondel one requires all the signals along a path to be named. The other difference is that the brummfondel one will find the path ahead automatically in the editor when you enter the name of the first signal on the path so it is just a matter of switching the junctions in the editor until you set the path to where you are going. The _mutton_ one requires each junction to be entered and set individually and so takes a little longer to set up.

In addition each rule has an associated driver command “PathControl setpath” for the brummfondel one (kuid2:192081:6:2) and “Path Command” for the _mutton_ one (kuid2:71155:60007:1). These allow you to set the required path for each train in the driver commands. They also each have an “Autodrive”, brummfondel (kuid2:192081:4:4) and “Autopilot Command”, _mutton_ (kuid2:71155:60001:5) which in effect just tell the train to keep driving until it reaches or passes the target trackmark.

I put some instructions on how to set up the _mutton_ rule in this thread (post 4) some time ago http://forums.auran.com/trainz/showthread.php?101288-Path-Rule-Troubles&highlight=path+rule.

Personally I prefer to use the brummfondel rule as it can be used alongside his "jsTRF Path Trigger" (kuid2:192081:15:4) to automate much of the driver command route selection. For example on the ECML route I have paths set up for trains to access any of the platforms at King's Cross and the driver command is simply Autodrive to the required platform trackmark. When the train activates the Path trigger it automatically sets up the path to that particular trackmark without any other intervention.

If you are just using one of the rules to check if the trackmark is valid, I would use the _mutton_ one as it requires less preparation but if you have already named the signals then I would suggest the brummfondel one.

Regards

Brian

 

[Dap]

Brian,

Thanks for the input. It seems my original post got lost in the Forum crash earlier this week. Glad you remembered my delema. I'll be working on this over the weekend. I'll report back my results.

David

 

[Dap]

I used the "Path Rule” by _mutton_ (kuid2:71155:60006:4), because I did not need to interface to a trigger. All is working fine. I have tested several days of operations and every train made it to the correct track as it navigated through the yard throat.

Thanks for your advice and explainations.

I'll be releasing this route later this fall. It is the Soo Line Schiller Park Yard. Fifteen active classification tracks at each end of the yard along with 6 arrival tracks. Five regular inbound and outbound road trains and 13 transfer runs each day. 720 inbound cars on Monday and it gets busier as the week progresses.

David

 

[Kennilworth]

Hi David

I am pleased to have been of help. The reason I started using the path rules was because it took the guesswork out of the AI making decisions about pathing through complex trackwork. I look forward to the new route.

Regards

Brian

 

[JackDownUnder]

I have been having problems recently with Path Rule by _mutton_.
Was working then became a missing dependency today.
Cannot find the latest one kuid2:71155:60006:4 on the download station.
Any help would be appreciated

 

[Kennilworth]

Hi JackDownUnder

The rule is built in to TS12 so try a Revert to Original on it in content manager.

Regards

Brian

 

[JackDownUnder]

I had disabled it instead of the older version. Looks OK now.

 

[Dap]

Well, everything was working fine until I added a new path command for the southbound engines.

My northbound trains have no trouble negotiating my yard throat. As they approach, the path command implements and the appropriate switches are thrown and the train enters the correct tracks.

When a southbound train arrives in the yard and the engines uncouple and pull out past the yard throat, they stop at the engine reverse trackmark, wait for 5 seconds, reverse direction then the path rule is implemented and the appropriate five switches are thrown. The next driver command it to navigate to trackmark which happens to be on track 6. As the engines approach the first switch, Junction 1, controlled by the path command, it comes to a stop and I get the following message in the message window.

drivername - waiting for access to junction 1.

It does not move forward from this location no matter how long I wait.

If I stop the AI control and manually drive it past junction 1 and then continue schedule, it proceeds to the second switch controlled by the path command, comes to a halt and gives the following message:

drivername - waiting for access to junction 2.

When I repeat the same step of manually driving past the switch and reverting to AI, I get the same results and message for the next switch.

Any idea what is going wrong here?

 

[Isegrinns]

Yes, use the autopilot through the path.
I´m uploading a video which shows the driver setup, might be useful.

Basically, the sequence is "select path *name", "autopilot to trackmark *bla*".
Make sure there is a trigger on the way which releases the path, otherwise they will stay locked!

 

[Kennilworth]

Hi Dap

As mentioned above you need to use the Autodrive command otherwise the train will just sit and do nothing. Navigate To or Navigate Via will try to set the path themselves but the Path rule will already have locked it. I always use the last junction that the train has traversed to free the path as it frees the path immediately it has been completed but you can also use a signal or trigger behind the last junction.

You can even use one of the junctions midway through the path to free it (e.g. where a train stops across a junction before completing the path) but only use that with caution as some other train could change a junction before the train clears the path leading to a derailment. In a busy area with complex trackwork I try to break the path into sections if possible to minimise the amount of time that junctions are locked. In a yard for example there will usually be a number of tracks radiating from one approach track. The path would be in two sections, one to get the train onto the approach track and a second one directing it into the required siding.

Regards

Brian

 

[Isegrinns]

Part 1, part 2 will follow. You can see the sequence I used though.

 

[Dap]

Damm, getting old is a pain. The more I learn, the more I forget. Its like Leonard Cohen said, "I can't forget, but I don't remember what."

Trains are now running smoothly.

David