interface between UIDs and Rules

You are here: Home > Forum > Simulations > Timetables > interface between UIDs and Rules

Page 1 of 1

interface between UIDs and Rules 03/12/2022 at 18:39 #149116
jc92
Avatar
3631 posts
Online
I thought I'd ask this on the forum in case the answer helps anyone else.

I'm currently working on a Saltley timetable which chains to Derby and handles trains which disapear into the new street black hole before reappearing. both are throwing up some interesting issues with UIDs and rules.

Situation 1) a train enters at Stoke works, proceeds through Kings Norton into New Street and then runs via Landor Street and Water Orton. I could for example have train 1E01, UID 1E0101 enter at stoke works, then 1E01, UID 1E0102 enter at New street with a rule that 1E01 must not enter until 4 mins after 1E0101 leaves the sim. That works fine unless there's a chainable new street timetable, in which case every through train would need to form a new working. If I use the same UID twice, it would prevent the train entering until the first part had left, but I can't enforce any rules, for instance where a train has a loco change or shunt and needs a sizable amount of station time.

Is there a way to enforce the second trains entry to a variable amount while keeping 1 UID for chaining purposes?

Situation 2) I have a train which runs New Street - Tamworth, then forms an ECS to Longbridge via a reversal at Burton on Trent, coming back via Wichnor and Kingsbury. when chained no issues occur, but when running solo, Derby is happy with the ECS running as 1 UID, however on Saltley, the train exits at wichnor reenters with a duplicate UID, again meaning rules can't enforce a turnaround. do I need to split the train at Burton to form a new working with a new UID or is there a way to enforce it with a single UID? unfortunately a terrible place for this move right on the chaining divide between sims.

TIA

"We don't stop camborne wednesdays"
Log in to reply
interface between UIDs and Rules 03/12/2022 at 18:54 #149117
Dionysusnu
Avatar
575 posts
Online
I believe there's an option called "increment UID on transfer"? Which will make option 1 possible with the different UIDs.
Log in to reply
interface between UIDs and Rules 03/12/2022 at 21:38 #149123
jc92
Avatar
3631 posts
Online
Dionysusnu in post 149117 said:
I believe there's an option called "increment UID on transfer"? Which will make option 1 possible with the different UIDs.
according to the below page, this is redundant due to UIDS and shouldn't be used:

https://www.SimSig.co.uk/Wiki/Show?page=usertrack:ssrun:func:f4:wttnew#Incident%20Control%20Panel

"We don't stop camborne wednesdays"
Log in to reply
interface between UIDs and Rules 03/12/2022 at 21:47 #149124
Steamer
Avatar
3926 posts
jc92 in post 149123 said:
Dionysusnu in post 149117 said:
I believe there's an option called "increment UID on transfer"? Which will make option 1 possible with the different UIDs.
according to the below page, this is redundant due to UIDS and shouldn't be used:

https://www.SimSig.co.uk/Wiki/Show?page=usertrack:ssrun:func:f4:wttnew#Incident%20Control%20Panel
Indeed.

The train should use the same UID on Derby, Saltley, New Street and (should it ever be re-released) Gloucester.

On Saltley, the train may have two TDs (1E01-1, 1E01-2 for example) which will allow rules to reference different instances of the train. However, the UID takes precedence during chaining, so the different TDs don't matter.

"Don't stress/ relax/ let life roll off your backs./ Except for death and paying taxes/ everything in life.../ is only for now." (Avenue Q)
Log in to reply
interface between UIDs and Rules 03/12/2022 at 22:01 #149126
GeoffM
Avatar
6288 posts
jc92 in post 149123 said:
Dionysusnu in post 149117 said:
I believe there's an option called "increment UID on transfer"? Which will make option 1 possible with the different UIDs.
according to the below page, this is redundant due to UIDS and shouldn't be used:

https://www.SimSig.co.uk/Wiki/Show?page=usertrack:ssrun:func:f4:wttnew#Incident%20Control%20Panel
The functionality is still there. I've corrected the linked page.

SimSig Boss
Log in to reply
interface between UIDs and Rules 04/12/2022 at 00:41 #149131
jc92
Avatar
3631 posts
Online
Steamer in post 149124 said:
jc92 in post 149123 said:
Dionysusnu in post 149117 said:
I believe there's an option called "increment UID on transfer"? Which will make option 1 possible with the different UIDs.
according to the below page, this is redundant due to UIDS and shouldn't be used:

https://www.SimSig.co.uk/Wiki/Show?page=usertrack:ssrun:func:f4:wttnew#Incident%20Control%20Panel
Indeed.

The train should use the same UID on Derby, Saltley, New Street and (should it ever be re-released) Gloucester.

On Saltley, the train may have two TDs (1E01-1, 1E01-2 for example) which will allow rules to reference different instances of the train. However, the UID takes precedence during chaining, so the different TDs don't matter.
Just to be clear. What you're saying is have ID 1E011 enter at Stoke works and 1E012 enter at new street, both with UID 1E01, then use the differing headcodes for the rules, and leave the uid to do its normal work when transferring info for the chain transfer?

Theoretically that would work at Tamworth depending on where the two simulations actually transfer as well.

"We don't stop camborne wednesdays"
Log in to reply
interface between UIDs and Rules 04/12/2022 at 01:57 #149133
Meld
Avatar
1098 posts
Joe - take a look at London Bridge & North Kent for the circulars (2O/2Ixxs) I used the same TID throughout and suffixed the UIDs as necessary, so 1Z99 (Original UID A12345 for example) Departs LB as A12345A then becomes A12345 on NK and re-entering on LB also as A12345. Re-entry rules are $A12345 must appear xx Mins after $A12345A leaves the area. The Same principle can be applied to Wimbledon & Feltham for the Waterloo Circulars (of which theres a hell of a lot more )

Since the release of NK I have not yet noted an issue with using this method.

Lets say you have 1Z99 in Derby Saltley Newstreet and Leamington the UIDs would Be DBY A12345 SY A12345A BNS A12345 SY (re-enter) A12345 & Leamington A12345 Saltley would have the same A12345 must appear xx mins after A12345A leaves the area rule as described above

Hope this gives you a few ideas

Passed the age to be doing 'Spoon Feeding' !!!
Last edited: 04/12/2022 at 01:58 by Meld
Reason: None given

Log in to reply
The following users said thank you: GeoffM, jc92
interface between UIDs and Rules 04/12/2022 at 06:55 #149137
jc92
Avatar
3631 posts
Online
Yep that makes sense having looked through them.

So from a chaining perspective, when a train is transferred, the sim will first attempt to match a UID to the entry location, and if it can't it reverts to ID instead. Provided theres only one instance of that headcode, it will end up picking the right one (obviously wouldn't work with old school routing IDs or other multiple instances).

So taking the SY-BNS example, 1Z99/A12345 passes through Derby, when it hits Wichnor, Saltley sim looks for A12345 but can't find it, but does find a 1Z99 ID entering there and uses that, changing UID to A12345A, then at Landor Street (or wherever BNS and SY chain) the reverse as BNS doesn't have an A12345A entering at Landor so uses the only 1Z99 ID available, thus jumping back to A12345.

Ingenious. thank you very much.

"We don't stop camborne wednesdays"
Log in to reply
interface between UIDs and Rules 04/12/2022 at 09:24 #149138
Meld
Avatar
1098 posts
jc92 in post 149137 said:
Yep that makes sense having looked through them.

So from a chaining perspective, when a train is transferred, the sim will first attempt to match a UID to the entry location, and if it can't it reverts to ID instead. Provided theres only one instance of that headcode, it will end up picking the right one (obviously wouldn't work with old school routing IDs or other multiple instances).

So taking the SY-BNS example, 1Z99/A12345 passes through Derby, when it hits Wichnor, Saltley sim looks for A12345 but can't find it, but does find a 1Z99 ID entering there and uses that, changing UID to A12345A, then at Landor Street (or wherever BNS and SY chain) the reverse as BNS doesn't have an A12345A entering at Landor so uses the only 1Z99 ID available, thus jumping back to A12345.

Ingenious. thank you very much.
You've got it, it's a little more time consuming to set up with the individual rules, but the results are well worth it.

As you know real life UIDs are formatted Xnnnnn and associations use this format. With any terminal station you would need to make sure that the arriving service is modified to the suffixed UID. If your data had A54321 with a next working of A12345, you must change this to the suffixed UID A12345A

Passed the age to be doing 'Spoon Feeding' !!!
Log in to reply
The following user said thank you: jc92