Track plan analyzer

Content Rocrail Server

  • Track plan analyzer



Features

  • Analyze the track plan and create all possible routes automatically.
  • Sets the routes field in tracks, signals and sensors → route representation.
  • The direction track can be used to restrict a route generation only in that direction.
  • The Connector can be used to connect distant elements
  • Turnout commands are added to the route.
  • Signal pair selection (optional).
  • Enter- and In-Sensor assignment to blocks (optional).
  • Module support.
  • Fiddle Yard support.


Note: The Analyzer was introduced as a tool especially for the new and inexperienced user allowing for quick access to fully automated model railroading.
However, with complex or unusual layouts the Analyzer may fail to generate all routes possible or it may generate unexpected routes or in worst case it may even hang.
In all these cases settings have to be adjusted or completed by hand while those routes generated correctly by the Analyzer can serve as a blueprint. See also section Limitations


Operation

Requirements

  1. Track plan must be healthy before analyzing!
  2. Activated option Use block side routes in the Rocrail automatic tab.
  3. All items must be connected without a space in between them. Exception: The Connector
  4. Only one item at one position in the plan is allowed. (No overlapping.)
  5. The analyzer is based on the symbol sizes found in the default SpDrS60 theme. (See also themes basics)


Activation

The Analyzer can be activated manually.

The feature is started manually by

  • either entering z in the Rocrail server terminal if the -console option is active
  • or by selecting Analyze from the File menu of Rocview.


Clean up

On rerunning the analyzer after changes in the track plan all routes with an ID starting with “autogen-” that became invalid, e.g. due to changes in the relations of blocks or by introducing direction tracks, will be deleted from the route list.
Manually added routes not starting with “autogen-” will stay in the list unmodified.


Sensor Configuration

Sensors have to be assigned to the routes on the routes tab found in the block properties. The sensors are assigned to the routes all enter + and all enter -, respectively. The all enter + route is for all routes entering the + side of the block (marked with the little + in SpDrS60 theme). The all enter - route accordingly is used for all routes entering the - side of the block.


Direction Tracks

Direction tracks (s. also Types of Tracks) can be used to restrict the routes generated by the analyser to one particular direction. For this purpose the direction track is placed between one or more blocks:

Example Description Routes generated by the analyser
Two blocks connected by tracks From A to B and from B to A
Two blocks with a track indicating both directions in between Same as above; the track for both directions is descriptive only but has no function
Two blocks with a direction track in between, arrow pointing to the right Only from A to B
Two blocks with a direction track in between, arrow pointing to the left Only from B to A
Branch without direction tracks A to B, A to C, B to A and C to A
Direction track within a branch A to B, A to C and B to A
Direction track in front of a branch A to B and A to C


Connector

Connectors can be used to connect distant elements: The analyser is seeking for a counterpart (second connector) in the same direction and ignores gaps and elements between these two. Example: Connectors illustrating a bridge.

  • The maximum distance between corresponding connectors is unlimited
  • Connectors on the same track plan level where the orientation is in the way shown in the above example and the connectors face each other are handled as counterparts (Exception below)
  • Connectors configured with a track numnber between 10 and 99 must have one corresponding connector with the same track number anywhere in the plan. The direction of the counterpart doesn't matter. The counterpart may be on a different track plan level.

Connectors should not be used between modules.


Limitations

Symbols 1 (double track railroad crossing), 10, 11 and 12 (single track railroad crossing), 40 (double track bridge), 41 (single track bridge), track 2 (bridge connector) and track 3 (bridge crossing) are recognized by the Analyzer Other Accessory# symbols are not supported . It doesn't know the various grid sizes and orientations of these symbols. Therefore, before starting the analyzer these objects should be replaced temporarily (and possibly later again) with normal track objects.

Note: Do not use two or more double track items consecutively. The Analyzer will generate some wrong routes :!:


Example

Generated Routes

<stlist>
    <st id="autogen-[01+]-[02+]" bka="01" bkb="02" bkaside="true" bkbside="true" show="false" x="0" y="0">
      <swcmd id="sw1" cmd="straight"/>
    </st>
    <st id="autogen-[01+]-[03+]" bka="01" bkb="03" bkaside="true" bkbside="true" show="false" x="0" y="0">
      <swcmd id="sw1" cmd="turnout"/>
    </st>
    <st id="autogen-[04+]-[01-]" bka="04" bkb="01" bkaside="true" bkbside="false" show="false" x="0" y="0"/>
    <st id="autogen-[02-]-[04-]" bka="02" bkb="04" bkaside="false" bkbside="false" show="false" x="0" y="0">
      <swcmd id="sw2" cmd="straight"/>
    </st>
    <st id="autogen-[03-]-[04-]" bka="03" bkb="04" bkaside="false" bkbside="false" show="false" x="0" y="0">
      <swcmd id="sw2" cmd="turnout"/>
    </st>
  </stlist>

Personal Tools