CallOn

Examples:

Since ATCS Monitor treats mnemonics using O (oh) as part of the standard OK (OR block) functionality, we substitute 0 (zero) for O (oh) for this function, if trying to use in active text.

First example, no call on needed, normal operation, one EB train following another, "bounded" approach label (WAK is the first EB train going away from the plant). EGZ happens until previous train clears intermediate block just beyond the plant. Chronology:

EGZ

WAK (can't get the EGK)

EGZ

WAK (can't get the EGK)

EGZ

WAK (can't get the EGK)

wak drops

EGZ

EGK (WAK cleared, so EG could take root finally)

• This time, with Call-on:*

EGZ

WAK

EGZ,EC0Z (dispatcher realized signal wasn't going to clear)

WAK,EGK,EC0K (some plants there's a CO indication, some plants not)

WAK,EGK,EC0K (flashing red EGK)

Then, if train ahead clears the block before following train hits plant:

EGK (C0 clears since it's not needed, field sig elevates to yellow)

Or, if following train takes the call-on:

WAK,TK

WAK,TK

WAK (two trains in block, same would apply for backing onto own train)

If you want to watch this C0 behavior, it happens frequently (few times per day) in CP C&M Sub plant Oakwood, where a freight follows an overtaking Amtrak (highly unlikely collision, since Amtrak is going at least twice the freight's restricting speed). Files are in download area. Thanks to Adam Harrington for providing the feed. -- Main.GaryHahn - 07 Jul 2007