The ID is used through out the Rocrail program as a unique key for referencing this block and is therefore very important.
If the ID is changed routes using this block have to be edited, too.
Free text for display only.
Alternative name for this block to use in the graphical schedule and location view.
If set to greater than zero it will be used to compare it with the train length found in the Locomotives: General Dialogue. The comparison is made like this:
|The train will fit if the Train Length plus the Min. block - train length is smaller or equal to the Block Length.|
The Min. block - train length is set in the Rocrail Properties (pre-set to 20) and is considered as the extra length to leave room for stopping the train.
Example: With the pre-set 20cm Min. block - train length and a Block Length of 100cm a train must not exceed 80cm in order to fit into the block.
The unit, e.g. mm, cm, or inch, is user-defined but has to be the same for all length definitions throughout Rocrail, i.e. Block Length and Automatic Settings. Depending on the scale used, the most suitable unit can be applied.
The offset of the platform position used by the Center Train option.
The two values, + and -, concern the respective Block enter side.
This number reflects the minimal radius of a train, locomotive or wagon that can safely operate in this block.
If a train, locomotive or wagon has as minimum radius bigger than the radius in a block, the block won't be used.
No checking is done, if this field is zero.
After the route has been set successfully, all actions waiting for the 'depart' event will be triggered. Then the start of the loco will delayed by this time in seconds. The globally defined semaphore- or signalwaittime will remain unaffected. This can be used e.g. for announcements.
This option is used in conjunction with Loc depart delay.
This feature is only usable with automobiles which have infra red detectors to keep distance to the vehicles ahead.
In all other cases enabling this feature will lead to accidents.
The size is the number of allowed concurrently automobiles in this block.
In addition a gap can be specified here. This should be the gap the cars keep to each other due to their Infrared-Detectors.
If this gap is >0 the length of the cars + the gap will be taken into account with regard to the block length.
The current occupying locomotive is set in this field or is empty on free.
The tripple dot […] button can be pushed to modify the loco properties. This is not usable for selecting another loco.
The turntable ID is selected here if this block contains a turntable.
The turntable should have its bridge split up into 2 occupancy sections which will generate the enter and in event for this block.
No other sensors must be set for this block, and the block type has to be turntable.
In combination with block type shunting this can be used for activating a route to the home block of the scanned car.
Virtual blocks are used to group a number of slave blocks to define it as one.
Routes to and from virtual blocks are not automatically generated by the analyser and must be defined manually including the route sensors.
Use the Show flag to hide a virtual block from the layout.
Tip: The Master and slave blocks must have the plus sides all in the same direction to ensure a correct rendering.
Overlapping or nesting with other virtual blocks is not supported; A block can only be in one virtual block, and a virtual block cannot be part of another virtual block.
Create a Virtual Block:
A comma separated list of slave blocks without blanks. (Virtual blocks as slave blocks are NOT supported.)
The block infrastructure is configured using the following flags:
This option can be activated for blocks equipped with a catenary.
If NOT set this prevents locos with engine type electric (see Locomotive Details) from using this block in auto mode.
The block will be skipped if set when running in auto mode.
This option together with the Wait Options on tab Details defines whether trains have to stop in this block. This option is activated automatically if anything else than no is selected from the Wait Options on tab Details.
Define if the block permits half automatic mode: "Automatic and Half automatic mode".
| Using this option could cause uncontrolled automatic sequences; Use not if you are unsure.
If a train runs in a wrong block, caused by a defect switch, it will not be stopped if this option is set!
The block event "Ghost" is only active in automatic mode.
As soon as a sensor detects an occupancy in a block (red) without an active loco assignment the "Ghost" event will be triggered in the occupied block.
With "accept Ghost" checkbox ticked it is possible to operate a train manually in a layout which is controlled by Rocrail's auto mode without getting a power off command from Rocrail. An automatically controlled train will not enter a Block which is marked as "Ghost" due to a manually operated train.
Checkbox is unmarked: Power will be switched off = Emergency stop. The occupied Block will be marked with "Ghost". Operations will be possible again after the ghost event is removed. The "Ghost" displayed in the Block can be removed with right click at the block and choosing "Reset Loc Assignment". After that the block has to be assigned with the correct Loc by right clicking the block and Choosing "Set Loc Assignment". Afterwards the Train can be operated again in automatic mode.
Checkbox is marked: Power will stay switched on : no emergency stop. The occupied Block will be marked with "Ghost". The block will be denied for every other train that operates in auto mode. The ghost train will continue into the next block without being controlled by Rocrail. After it passes the first sensor of the next block, the train will activate the ghost event in this block. As soon as the train releases the last sensor in the previous block, the ghost event will be reset in the that block.
The ghost train has to be stopped manually. The "Ghost" displayed in the Block can be removed by right clicking on the block and choosing "Reset Loc Assignment". After that the block has to be assigned with the correct Loco by right clicking the block and Choosing "Set Loc Assignment". Afterwards the Train can be operated again in automatic mode.
Used for blocks at the end of railway lines: The locomotive's placing is swapped triggered by the in event of the block allowing the train to leave the block in opposite direction.
This flag should be used with care! The page on Directions should be carefully read to get an understanding of the behaviour.
The option has the same impact as if the train was swapped by hand!
Note: This option is disabled if the Allow change direction function is selected (and vice versa). Either "Terminal Station" or "Allow change direction" (or none of these) can be selected.
Use the road theme to visualize this block.
This flag allows using a route in the opposite running direction as from where the train came from. If necessary, the placing of the locomotive is changed so that the train can then travel in the opposite direction.
Note: This option is valid for commuter trains only! Trains other than commuter trains will not change their direction.
Note: This option is disabled if Terminal Station is selected (and vice versa). Either "Terminal Station" or "Allow change direction" (or none of these) can be selected.
Note: This option should be disabled if these blocks are part of a Critical Section.
A stop controller, like Lenz ABC, will be used in combination with the enter2in event to halt the train.
Use only with the enter2in event to avoid trains running through this block even if it has to wait.
Check this option only to permanently accept manually driven BiDi capable trains.
This option acts as an interface between manually driven trains and automatic mode. In all other cases: Do not use this option!
Note: Use this option with care because it will also accept trains which did run over a wrong set route.
Note: "Accepting" can show in the block by using this option.
Enable BBT for this block; Default is enabled.
|User option; No official support.|
Keep the loco at enter speed for this number of BBT steps.
The function of BBT is defined for the driving distance between enter and in.
Is there for the block only one feedback enter2in, the timings of BBT with the timer of enter2in can collide.
An enter2in defined sensor should be changed to enter and at the locomotives the option Generate In is to activate.
In this case the in event is determined only by the BBT timing and does not collide with another timer.
If this block is part of a Location it will always allow to depart instantly. Also the time to wait will be reduced before retrying to find a new free destination.
Info: This will overrule the minimal occupancy, FiFo and Loco priority.
This option disables evaluating sensor events during the closed state; Ghost trains are not reported.
This option is only for trains with the same option activated.
With the +/- options the block side can be defined for this behavior. Default: Both sides.
With the Route option is it possible to free up the current route too.
The value "Max. Length" defines that an early release, of the previous block, is only performed for trains up to this length.
This prevents that the "From" block is released, before longer trains have completely exited.
Show this block in the layout.
If there are cars left in the block it is normally not allowed to access this block if it is not set as shunting or the loco did not get a "goto block" order.
This option will overwrite this behaviour, i.e. irrespective of the block type access is allowed even if cars were left in the block.
See also Train Locality.
If the train must wait in a block this option allows to reserve the second next block nevertheless, and the route will be set ready to go.
The same option must be set in the loco properties.
The DCC polarisation In combination with Railcom and Use BiDi Direction.
If this option is deactivated the reported direction will be inverted.
This option can only be used in case the enter detection is always free if the train is in the block.
A ghost will be reported if the enter detection is triggered in case there is already a train in the block.
Look for Ghost options in the server settings.
See Actions for more details.