[rickloader]

I have been asked via the OR website for help in enabling a runround under signals for the Czech route " Breclav-Praha". The signalling is complex ; there are 234 signal types and each type has up to 30 sub objects. Rather daunting!
My understanding is this. (Am I correct?)
In coupling operations $attach $detach $pickup $transfer Runround (ADT for short) a train will not pass a normal stop signal to complete an ADT when it is in auto signal mode ie in a signalled route.
A signalled route needs the Sigscr.dat modifying to enable callon for ADT as in the manual 10.15.3 TrainHasCallon for open line and TrainHasCallon_Restricted for platforms.
From the website query, it seems that ordinary users face difficulties in modifying signal scripts, and even worse may be baffled why their train is blocked by a red signal.
Timetable mode is a magnificent part of OR. What can we do to make coupling operations accessible to ordinary users?
Rick

[Weter]

I have encountered a problem, that I couldn't solve, when trying to perform runaround: the engine of AI train succesfully detached, reverced, but couldn't exit from siding at the opposite side, as exit signal didn't open in front of him.

At "platform 1 left"(very bottom track in diagram), another train is waiting for activation, at that time, for moving to the left.

[rickloader]

Hi Weter, thanks for the diagram. Yes,this is the kind of situation we are talking about. I think your runround should have worked, because after the red signal you have a reversal through a switch with no signals.
There are 2 modes in timetables Auto signal - trains are under signal control and won`t clear for ADT. Auto node trains are not under signal control. (see manual 10.3.1)
You can move from auto signal to auto node by reversing through a switch. A new sub path starts, and ADT can be completed. So if you can`t complete ADT under signals shunt the train to an area with no signals e.g. a yard.
Note however that commands like $wait $hold $activate do not work on subsequent sub paths. If you need these you witll have to $form a new train in the #dispose, so that they are on the first sub path. You can see a sub path counter in the Shift F5 dispatcher window like this [2]
Rick

[rickloader]

Here is my friend Jan`s runround problem. It is similar to Weters, except in the last move the engine must pass the signal to couple to the train. This signal will not clear unless the sigscr.dat is modified to enable call on. Jan`s route has 234 signal types, so it is very hard for a user to know which types should be changed.
Here is my own callon script. This is for shunt type signals guarding routes into platforms. (use trainhascallon for open line situations).
My script can be substituted in the sigscr.dat for a normal stop signal to enable callon. But you can get side effects so beware of modifying all signals in a route. e.g My script does not work as it is with 2 head junction signals - both aspects clear.

Attached thumbnail(s)

• 

Attached File(s)

•  rick_callon_script.txt (1.03K)
  Number of downloads: 5

[Weter]

Quote

to know which types should be changed

Track Viewer can show the signal's type:
You have to tell him to "show all signals" and their *.s-file names(Track items/interactives/show also other signals and Statusbar/show signal info menus), then hilight the signal, You are interesting, with a mouse pointer.
The information about signal, then, can be seen at status string at the bottom of trackviewer's window.

I've just forgot to note, that at "platform 1 left"(very bottom track in diagram) at that time, another train waited for activation for moving to the left.

[Weter]

Correction: that trains are BOTH AI "Player's train" should be read as "discussed AI train, which can't finish runaround action"

[rickloader]

Quote "Track viewer can show the signal type"
I can only see the signal file name in trackviewer. Taking the file name I look in the sigcfg.dat and find the signal shape (attached). There are 20 subobjects in this signal. We need to find the right SigSubSType to modify the script in the sigscr.dat to enable callon. But which?
Ignoring the decor items i`ve extracted the SigSubSType s from the sigcfg.dat (attached)
In most cases it will be the script with a normal stop function to modify for callon. But I`m afraid that the complexity of this signal defeats me, and with 234 others to consider too!
So the questions remain, can we help Jan., and how can an ordinary user compile a timetable in a signalled route?
Rick

Attached File(s)

•  Jan_sicfg.txt (3.07K)
  Number of downloads: 3
•  Jan_sigscr.txt (8.25K)
  Number of downloads: 3

[rickloader]

Reply to Weter - crossed post.It is possible another train is holding your signal at red.
Can you post the Shift F5 dispatcher viewer of your player train in the run round please? This may give the reason why the train is stopped. Very likely there is a conflict with another train that has claimed the route beyond the signal. In the path section look for things indicating deadlock like #&*^~ and get the train number that is in conflict.

[Weter]

Quote

can only see the signal file name in trackviewer

Shape file name, actualy.

Quote

Taking the file name I look in the sigcfg.dat and find the signal shape (attached). There are 20 subobjects in this signal. We need to find the right SigSubSType to modify the script in the sigscr.dat

I went the same way.

Quote

But which?

Try to count lights, their colours and arrangement to guess. There referenced, which script controls which signal subobject.
https://www.youtube....h?v=EOk0kpTkRys

[Weter]

Correction: that trains are BOTH AI
Green one stays there for 40 minutes (inactive) and the 1st track's exit signal is belived to hold on close state till 2 minutes before that train's arrive time.
The discussed train (red) has to reach its platform, change "head" during RR-action and depart immidiately, well before the first train.

Quote

post the Shift F5 dispatcher viewer of your player train in the run round please

Maybe, later :(

It's possible, You're somewhere right:
I already corrected sigscr.dat for such signal type, as it didn't open for incoming trains, when was used as entrance signal.

Quote

can move from auto signal to auto node by reversing through a switch

Can You explane this a little more verboose, please?