Creating and Editing OBlocks, Portals and OPaths

Start by entering each occupancy block of your layout into the Occupancy Block Table.

1. Enter a system name for the OBlock. If you do not preface the entry with "OB", it will be prepended to your entry automatically.

2. (Optionally) Enter a user name for the OBlock.

3. Enter the system or user name of the detection sensor for the block. You can skip entering this now and come back and enter it later.

Note: (You can also read this note later.) If there is more than one sensor that detects occupancy of the the block 'OR' them together and trigger a single internal sensor to use for this entry. For example, suppose, LS10, LS11 and LS12 are detection sensors and IS100 is an internal sensor. Presuming "Active" means ocupied, write a Logix Conditional with state Variables:
Sensor "LS10" state is Sensor Active
Sensor "LS11" state is Sensor Active

Sensor "LS12" state is Sensor Active

Select OR as the Logic Operator.
and add the Actions:

On Change to true, set Sensor, "IS100" to Active.
On Change to false, set Sensor, "IS100" to Inactive.

Note: The row of a new entry will jump to its sorting position as ordered by system name. To continue editing the row, look for it at the top of the window. It will stay in place as long as it has the same system name.

Next, enter the portals between the blocks into the Portal Table.

4. For each point between the the blocks you have defined in the Occupancy Block table, enter a portal row for each portal (gap) between the two blocks.

A pair of adjacent blocks may have several portals between them. This is expected, so just give each portal a unique name. The block names can be dragged from the Occupancy Block table to save typing.

Note: The computer will notify you from time to time until you have entered a block on each side of the portal name. It doesn't matter on which side of the portal name you enter a block name, just be sure to enter both sides

Note: It may be helpful to open the Block-Portal Cross Reference Table to review whether all the portals have been entered.

Next, If there are signals at a portal, enter them into the Signal Table.

5. Enter the system or user name of the signal. This may be either a SignalMast or SignalHead.

6. Enter the name of the block facing the signal into the From (Approach) Block column. It is important that the approaching block of the signal is correctly named. This is the block that will detect when a speed change might be needed.

7. Enter the portal name or the name of the block whose entrance is protected.

8. Enter any delay of milliseconds to wait after entering the approach block before changing the train speed. (This time delay is used only when the signal indicates a speed change.)

Next, identify the Paths in each block.

Reminder: You may use 'Drag and Drop' to enter text. When selecting an item to drag, it may reqire two clicks; one to select the row and a second to select the column entry. Holding the second click down, you can drag the text from that row, column field.
9. Moving through the Occupancy Block table row by row, do:
9a. Press the Paths button and open the Block-Path table for the row

9b. Enter a path name for a path within the block of the row in the Path Name column.

Note: The name of the block is in quotes in the title bar of the table.
Enter the names of the portals where the path enters and exits the block.
Note: It doesn't matter on which side of the path name you enter a portal name. Dead end spurs will only have one portal.

Finally, complete the definition of each Path in each block.

10. For each path in each Block-Path table, do:

10a. Press the Turnouts button and open the Block-Path-Turnout table for the each row in the Block-Path table

10b. Enter the system or user name of a turnout in the path.

Note: The name of the path and its block are in quotes in the title bar of the table.

10c. Enter the position of the turnout in the Turnout Setting column - either 'Closed' or 'Thrown'.

Most likely you will have encountered several dialogs urging you to fix this or that, so try to resolve all of them.

Now, you are ready to define some routes for warrants. Of course, there will probably still be a few errors or missing items, but the 'Create Warrant' frame provides a tool to find and fix them.<\p>

11. Select Create New Warrant from the Warrants menu in a Panel Editor Panel.

To read about how OBlocks, Portals and OPaths can be used to generate train routes and make automated train scripts, see Warrants.

Also See Warrant Table help for more details on creating and editing warrants.

---