Ring Barrier Controller User Manual: PTV America August 2010
Ring Barrier Controller User Manual: PTV America August 2010
User Manual
PTV America
August 2010
Ring Barrier Controller 1.60 PTV America August 2010
PTV America August 10
Contents
1 Introduction 5
2 RBC Editor 8
2.1 Menus 9
2.1.4 Extras 12
2.1.5 Buttons 13
2.1.7 Tables 14
3 Definitions 17
3.1.1 Basic 17
3.1.2 Advanced 19
3.1.6 Sequence 32
3.1.8 Overlaps 32
3.2 Detectors 35
3.2.1 Vehicle 35
3.2.2 Pedestrian 37
3.2.3 Queue 37
3.3.1 SC Communication 39
3.4 Preempt 39
3.4.1 Preempts 40
4 Examples 56
4.4 Preempt 65
5 Troubleshooting / Services 73
5.1 Troubleshooting 73
5.1.1 Errors 73
5.1.2 Warnings 73
5.1.3 Messages 75
5.2 Services 77
5.2.1 Links 77
1 Introduction
The VISSIM Ring Barrier Controller (RBC) emulator has been integrated into VISSIM. This
interface provides users with a seamless way of simulating actuated control in a VISSIM model.
During a simulation VISSIM passes the status of its detectors and signal heads to the ring barrier
controller and the controller returns the state of the signal heads for the next time period. The time
period used for this interaction is determined by the Controller Frequency and can be as small as
one tenth of a second.The RBC Editor allows the user to set the timings used during the VISSIM
simulation by the controller and stores these values in external RBC data files with the .rbc file
extension.
- Manual control operation with selectable call, omit, and protected pedestrian clearance
signal groups
- Per signal group preempt timing
- 4 rings
- 16 timed overlaps
- 8 transit signal groups
Detector Features
► 32 vehicle detectors
- Programmable call and extend signal groups
- Extend and delay timing
- Stop bar disconnect mode with carryover (extend) timer
- Detector cross-switching
► 16 pedestrian detectors
► 8 transit detectors
- Programmable calls for transit and vehicle signal groups
- Extend and delay timing
- Travel time delay
- Alternate travel times by Time of Day
- Adaptive arrival time adjustment
Coordination Features
► 8 coordination patterns
- Cycle time and offset per pattern
- Flexible per signal group split expansion and shrinking during transition
- Fixed or floating force-offs (per signal group)
- Automatic permissive calculations
Single-band or multi-band permissive modes with permissive limit timer
Three pedestrian permissive modes
- Programmable recalls and omits active during each pattern
- Actuated coordinated signal groups can gap-out early and distribute unused time to
movements with greater demand
- Selectable reservice signal groups (a.k.a. “fully actuated coordination”)
Preemption Features
► 2 prioritized preempts
- Two track clearance states, dwell state, and exit state per preempt
- Permit or allow any signal group and overlap individually for each preempt state
- Presence preempt input with optional fail-safe interlock input
- “Check-in / Check-out” preempt detection option with check-out override timer
Transit Priority Features
► Programmable transit priority options for each transit signal group
► Separate options for free or coordinated operation
- Extend only (no signal group abbreviation) or Early/Extend operation
- Minimum signal group green times
- Maximum extend limit
- Optional vehicle/pedestrian signal group omits
► Adaptive arrival times to automatically compensate for fluctuating station dwell times
Previous versions of VISSIM included the NEMA signal controller type. The VISSIM Ring Barrier
Controller (RBC) replaces the need for the NEMA signal controller. Through VISSIM Version 5.20,
both types of controllers will be available for simulation; however, beginning with VISSIM Version
5.30, the NEMA controller will no longer be available. As such, it is necessary to convert any NEMA
signal controller types (*.nse file type) in VISSIM to the RBC format (*.rbc).
To convert from NEMA to RBC, VISSIM users have two options:
Option 1: Convert a single NEMA signal controller to RBC:
In the Signal Control dialogue box, select the signal controller to change from the list on the
left and use the drop-down menu on the right to change type to Ring Barrier Controller and
click OK.
This will result in a *.rbc file being created in the project directory with the same file name
as the previous *.nse file. In addition, the Program File and Dialog DLL file reference will
update to reflect the RBC controller type.
Option 2: Convert all NEMA signal controllers in a network to RBC:
Under the Signal Control menu, select “Convert NEMA to RBC”.
This will create *.rbc files for all *.nse files in the network. In the Signal Control dialogue
box, all signal control types that were NEMA will now be changed to type Ring Barrier
Controller.
This conversion process will only convert the signal timing and detector parameters. Transit
signal priority (TSP) and railroad pre-emption parameters do not automatically convert but can
be manually transferred to the RBC by the user.
2 RBC Editor
The first step toward setting up an actuated signal is creating the signal controller you will use at
the intersection in your VISSIM network. To create the controller, go to Signal Control – Edit
Controllers and select the New… button. The dialog box Signal Controller will appear and you will
need to define a controller number and controller type. To use the RBC controller you should
select the Ring Barrier Controller type.
Once you have selected Ring Barrier Controller type, the RBC_Controller.dll will be selected as
your Program File and the RBC.dll as your RBC Editor and pressing the Edit Parameters button will
launch the editor where you can set up your controller. The controller settings will be saved in a file
with the extension *.RBC in the same directory as the inp file. Only one Data File is required for the
RBC signal controller type and it is defined when you use File – Save File As within the RBC
Editor.
Please see Section "6.7 Signal Controllers" of the main VISSIM Manual for more information on
setting up a signal controller in VISSIM.
2.1 Menus
2.1.1.5 Print
This prints your signal timing information to your desired printer. If Print Selection
in the menu is checked, only the items selected in the tree view will print.
2.1.1.7 Exit
This option exits the Editor without saving the RBC file.
2.1.3.1 Help
This option opens the helpfile, which is a chm version of the RBC manual.
2.1.3.2 About
Shows information about the RBC Editor and has links to Hotline support and the
PTV America website.
2.1.4 Extras
2.1.4.1 Notes
This field is not used by the controller or VISSIM, but provides a way to store
information within the controller file.
2.1.4.2 Frequency
This setting determines how many times per second the controller will
communicate with VISSIM during the simulation. During the communication
information about detector calls are passed to the controller and signal heads
indications (green, red, yellow) can be changed. Only one frequency can be
defined per controller type per VISSIM file and the frequency must be equal to or
less than the simulation resolution. This setting will be saved in the rbc.frq within
the VISSIM inp directory. Please note that within an instance of VISSIM, once the
simulation has been run once, the controller frequency will be stored in memory
until the next simulation begins. This will prevent you from setting the simulation
resolution to a value lower than the controller frequency was during the previous
simulation run.
2.1.5 Buttons
2.1.5.1 Ok
This will save the RBC file, exit the Editor and return to VISSIM. Note - when you
add, delete, or change signal group numbers, it is important that you save your
VISSIM file. Otherwise your VISSIM file may become incompatible with your
controller files.
2.1.5.2 Cancel
This will cancel all changes made in the Editor and return to VISSIM.
pattern shown in this table will define which pattern is displayed in the Timing
Diagram.
2.1.7 Tables
This is a Modern Graphical User Interface for timing entries. Only items selected
within the Tree View will be shown in the tables.
2.1.9.1 Errors
This table lists situations that have been created that may cause VISSIM to crash
or a simulation to not be able to run.
2.1.9.2 Warnings
This table lists situations that have been created that are invalid.
2.1.9.3 Messages
This table lists other logged messages regarding the current session.
3 Definitions
3.1.1 Basic
3.1.1.1 SG Number
Signal Group numbers for corresponding signal group. The signal group
number that will be created in VISSIM and will be used to create signal heads.
3.1.1.2 SG Name
The signal group name is currently only used within the RBC graphical interface.
3.1.1.5 Max 1
This parameter defines the maximum time that the signal group will be allowed
to extend before it will max-out. A max-out will make a signal group eligible to
terminate, even though it may not have gapped-out. Normally, the maximum
green timer will not begin counting until an opposing call to the signal group is
present. An exception to this rule is when the signal group is a flagged as a Max
Recall signal group, in which case the maximum green timer will begin counting
as soon as the signal group changes to green. Max 1 is the default maximum
green time for each signal group.
3.1.1.6 Yellow
The time a signal group will time a yellow interval before advancing to red. This
time cannot be abbreviated by any operation.
3.1.1.9 Walk
The minimum time a signal group will display a walk indication before advancing
to the pedestrian clearance interval (flashing don’t walk). Pedestrian signal
groups may rest in the walk interval following the minimum walk time if the Walk
Rest option is flagged for the signal group. The minimum walk time can be
shortened if the signal group is not permitted by an active Preempt. A signal
group may not advance to yellow while the pedestrian movement is in the walk
interval.
3.1.1.11 Start Up
Signal Groups that will be green at the start of the simulation. By default, these
signal groups will begin timing in green with walk (if there is pedestrian timing
defined). The controller will not start up conflicting signal groups if conflicting
signal groups are defined in this parameter. If no signal groups are selected for
Start Up, the first signal groups listed in the Sequence will start in green at the
start of the simulation.
3.1.2 Advanced
3.1.2.1 Max 2
An alternate maximum green time for the signal group that is only observed if
Maximum timing is called for by a pattern.
3.1.2.2 Max 3
An alternate maximum green time for the signal group that is only observed if
Maximum timing is called for by a pattern.
SG Red SG Green
Vehicle
Actuations
SG Red SG Green
GAP IN
EFFECT
Min Gap
TIME
rings are not ready to terminate. The signal group that is ready to terminate can
conditionally “backup” and serve a signal group that is sequentially before it if:
► There is a call in a conflicting concurrent barrier group.
► The “backup” signal group is flagged as a conditional service signal group.
► The “backup” signal group is in the same concurrent barrier group as the
other timing signal groups.
► There is enough time remaining on another concurrent signal group
(maximum green time or time until force-off during coordination) to time
yellow and red clearance on the current signal group and a minimum green
time on the “backup” signal group.
Once the “backup” signal group begins service due to conditional service, its
maximum green timer will be set the same as the maximum green time
remaining on the concurrent signal group. Pedestrian movements will not be
served during the conditional service of a signal group.
Conditional Service Minimum Green (CS Min Green), Cond Service – Allows a
SG to be reserved prior to a barrier crossing provided there is enough remaining
green time on a concurrent SG.
SG 2
SG 6 SG 5 CS
3.1.2.23 CNA
Signal groups flagged for this option will have a Max Recall and Ped Recall
placed.
3.1.3.1 CycleLength
This value defines the cycle length of the pattern. This is the maximum time it
will take for each signal group to cycle once. The cycle length is only used for
coordination. If a cycle length is not defined (set to zero), the pattern will run in
Free mode. RBC has a minimum cycle length for Patterns of 30 seconds.
3.1.3.2 Offset
When coordinated, the local cycle timer will be offset from the master cycle timer
by the defined offset time.
3.1.3.3 MaxGreenMode
This setting determines the maximum green mode that will be used for all signal
groups while the coordination pattern is active. This selection is only valid for
coordinated patterns; if used for free running patterns the value will be ignored.
The selections are:
► MaxInhibit – All signal groups will ignore their maximum green timers.
Signal groups will only terminate if they gap-out or reach their force-off point.
► Max1 – All signal groups will observe their Max 1 setting.
► Max2 – All signal groups will observe their Max 2 setting.
► Max3 – All signal groups will observe their Max 3 setting.
3.1.3.4 PermissiveMode
This setting defines the permissive mode for the coordination pattern. The
permissive mode controls the method in which permissive periods are opened
and closed for all non-coordinated signal groups. The controller will only yield to
signal groups that are permissive following the end of green on each
coordinated signal group. The permissive modes are as follows:
► SingleBand – The permissive period for non-coordinated signal groups will
open:
At the beginning of the coordinated signal group green for signal groups
in the same ring and concurrent barrier group as the coordinated signal
group, or
At the beginning of the lagging coordinated signal group green for signal
groups outside of the same concurrent barrier group as the coordinated
signal groups.
The permissive period for non-coordinated signal groups will close:
When there is no longer enough time to clear all timing signal groups
and serve the longer of the Minimum Green or Permissive Green on the
signal group, or
When the signal group is in a different concurrent barrier group then the
coordinated signal groups and any coordinated signal group has yielded
to a signal group that is sequentially before the coordinated signal
group, in the same ring and concurrent barrier group (i.e. a lagging
coordinated signal group yielding to its opposing left turn will close all
cross street permissive periods for the remainder of the cycle).
► MultiBand – The permissive period for non-coordinated signal groups will
open:
The same as Single Band Permissive operation above, but only for the
first signal group in each ring that sequentially follows the coordinated
signal group.
For each subsequent signal group, the permissive period will open once
the previous signal group’s permissive period closes (Only one signal
group per ring can be permissive at any given time).
The permissive period for non-coordinated signal groups will close the same
as they do for Single Band Permissive operation above.
► Reservice – The permissive mode will operate the same as Single Band
Permissives until the Coordinated signal groups yield to a non-coordinated
movement. ALL signal groups will be allowed to reserve. After the
coordinated signal groups yield once:
Conflicting SG ***Minimum
clearance permissive green
*** Minimum permissive green = SG minimum green unless a higher value is specified
under coordination pattern
3.1.3.5 PedPermMode
This setting defines the pedestrian permissive mode for the coordination pattern.
This mode determines how pedestrian calls will be served based on the
computed pedestrian permissive period. The pedestrian permissive modes are
as follows:
► Yield – Once the pedestrian permissive has closed, a pedestrian call will be
omitted until the next cycle. However, if a vehicle call is placed while the
vehicle permissive is still open but the pedestrian permissive has closed,
pedestrian calls WILL be served once the signal group turns green. In this
case, there will not be enough time to serve the pedestrian movement
without possibly going into transition.
► Partial – Once the pedestrian permissive has closed, a pedestrian call will
be omitted until the next cycle. If a vehicle call is placed while the vehicle
permissive is still open but the pedestrian permissive has closed, pedestrian
calls WILL NOT be served once the signal group turns green.
► Omit – Once the pedestrian permissive has closed, a pedestrian call will be
omitted until the next cycle. If a vehicle call is placed while the vehicle
permissive is still open but the pedestrian permissive has closed, pedestrian
calls WILL NOT be served once the signal group turns green. This is the
default setting.
SG 2/6 SG 4/8
Minimum
walk+pedclr
Conflicting SG
clearance ***Minimum
permissive green
SG 2/6 SG 4/8
SG 2/6 SG 4/8
SG 2/6
SG 2/6 SG 4/8
3.1.3.6 WalkRestMode
This setting defines the walk rest mode of the coordinated signal groups when
the coordination pattern is active. The selections are:
► Yield – The coordinated signal groups flagged for Walk Rest operation will
always terminate their pedestrian indications so the pedestrian timing is
finished by the force-off point. This way, the coordinated signal groups will
always be ready to terminate at the force-off point due to an opposing
permissive call. If all permissive periods close and the coordinated signal
groups have not yielded to an opposing signal group, the coordinated
pedestrian signal group can recycle to walk.
► Opposing Call – The coordinated signal group pedestrian movements will
terminate only if there is an opposing call to a signal group that has an open
permissive period. When this mode is selected, permissive periods for all
signal groups will close earlier if the pedestrian movement of a coordinated
signal group must first be terminated before the signal group can be served.
3.1.3.7 ExplicitForceOffs
During an active coordination pattern, activates explicit Force Offs defined in the
pattern instead of using Splits.
3.1.3.8 ExplicitPermissives
During an active coordination pattern using explicit Force Offs defined in the
pattern, activates explicit Permissive Periods defined in the pattern instead of
using automatically defined Permissive Periods. These can only be used with
explicit Force Offs.
3.1.3.9 AltPattern1
During an active coordination pattern, it is possible to activate one of two
alternate patterns based on an active Queue detector (i.e. activate an alternate
pattern due to congestion detected by a queue detector). Once a queue detector
with a Control of AltPat1 has detected a queue, the corresponding AltPattern1
will be selected in place of the current commanded pattern.
3.1.3.10 AltPattern2
During an active coordination pattern, it is possible to activate one of two
alternate patterns based on an active queue detector (i.e. activate an alternate
pattern due to congestion detected by a Queue detector). Once a queue
detector with a Control of AltPat2 has detected a queue, the corresponding
AltPattern2 will be selected in place of the current commanded pattern.
3.1.4.1 Split
The amount of time allocated in the cycle for each signal group to time. The split
includes the time it will take the green, yellow, and red intervals to time for each
signal group. The split should at least accommodate the signal group Min Green
plus Yellow Clearance plus Red Clear time, but it doesn’t necessarily need to
accommodate the full pedestrian service time for an actuated pedestrian signal
group. The sum of the splits of all signal groups in each ring should add up to
the CycleLength. Please take into account that in concurrent barrier groups that
have one or more rings without any signal groups, the controller will
automatically insert split time into the rings without any signal groups so that the
split sums will be aligned at each barrier.
than its force-off point, if there is nothing extending the signal group. For
example, a value of 5 for a coordinated signal group will allow the coordinated
signal group to terminate 5 seconds earlier than its force-off if there are no
vehicles extending the signal group. For non-coordinated signal groups,
programming a non-zero value for this parameter will force-off the signal group
this amount of time earlier than the normal force-off would be. This may be used
when the full pedestrian timing will utilize the full split, but it is desired that when
the vehicle movement times alone, it will finish earlier (by the time defined in this
parameter) than the full Split. For example, if the full split is 30 seconds, the
signal group clearance (yellow plus red) is 5 seconds, the pedestrian timing
(Walk plus Ped Clear (FDW)) is 25 seconds, this implies a green time of 25
seconds (30 second split minus 5 second clearance). If it is desired that the
vehicle movement alone (without the pedestrian movement) only times 20
seconds of green, program the Extended Split time to 5 seconds.
parameter, the split will never be reduced shorter than the sum of the signal
group Min Green plus Yellow Clearance plus Red Clear.
3.1.4.14 Max 2
Signal groups that will observe Max 2 timing while the pattern is active. This
setting is also used in Free Mode.
3.1.4.15 Max 3
Signal groups that will observe Max 3 timing while the pattern is active. If both
Max 2 and Max 3 are selected for a signal group, Max 3 will be used. This
setting is also used in Free Mode.
3.1.4.17 Coordinated
There must be a coordinated signal group in each ring of any ring group that will
be coordinated. All coordinated signal groups must be in the same concurrent
barrier group. Coordinated signal groups are automatically called, and are
usually held in green until their force-off point (also known as the yield point).
Coordinated signal groups are typically the main street through signal groups of
a street where vehicular progression is desired. If you do not define any
coordinated signal groups the controller will run in Free Mode.
3.1.4.26 Lead
Allows the user to change the sequence when a pattern is running; the timing
diagram will show the new sequence. If the sequence does not change for this
pattern, this parameter does not need to be set. Pattern 8 uses an Alternate
Sequence instead of Lead.
3.1.4.27 CNA
Signal groups flagged for this option will have a Max Recall and Ped Recall
placed.
3.1.6 Sequence
Clicking on the column header will create a barrier to the right of the column
below. Only signal group numbers that have been defined can be used in the
Sequence. A signal group can only be placed once in the sequence. A Signal
Group must be included in the Sequence for the signal group to time, otherwise
the timing information will be ignored. A maximum of 8 barriers and 4 rings are
available.
3.1.8 Overlaps
3.1.8.1 Overlap SG
Signal Group numbers for corresponding overlap. The signal group number that
will be created in VISSIM and will be used to create signal heads that used the
timing defined for this overlap.
3.1.8.6 Parent
These are the signal groups that the overlap will be allowed to time with. When
one parent signal group is timing and another parent signal group is next, the
overlap will remain green (unless a negative vehicle or pedestrian signal group
is next). When the last parent signal group terminates, the overlap will also
terminate.
SG 2 SG 3 SG 2
Overlap
SG 2 SG 3 SG 2
Overlap
Figure 17: Overlap Negative Green Operation (Right Turn Head Control)
3.1.9.1 OffsetReference
This is the point in the cycle where the master cycle timer will be equal to the
defined Offset time when the controller is coordinated and not in transition (offset
seeking). The selections are:
► LagFO (Lagging Force-Off) – The reference point will be at the force-off
point for the lagging coordinated signal group.
► LeadGreen (Leading Start of Green) – The reference point will be at the
start of the leading coordinated signal group green (the computed start of
green, note that the signal group may actually return to green early if there is
lack of demand on opposing movements).
► LagEnd (End of Lagging Red) – The reference point will be at the end of
Red Clear for the lagging coordinated signal group.
► CoordEnd (End of Coordinated Group Red) – The reference point will be at
the end of red for the last signal group in the concurrent barrier group with
the coordinated signal groups.
Leading coord SG Lag coord SG FO Lag coord SG end Coord group end
LeadGreen LagFO LagEnd CoordEnd
3.1.9.2 TransitionMode
This is the mode that all coordination patterns will use to transition when the
local dial does not have the correct Offset to the master clock, VISSIM. The max
transition values are automatically set to the split value plus 20%, and will be
adjusted whenever a split value is changed. The selections are:
► Best – The controller will determine whether implementing one or more
shorter cycles, or one or more longer cycles will achieve coordination the
quickest. Min Green and pedestrian signal group timing restrict how short a
transition cycle can be.
► LongMode – The controller will implement one or more longer cycles in
order to achieve coordination.
► BestIgnorePed – Same as Best Way above, except when determining how
short a transition cycle can be, the controller will ignore minimum pedestrian
signal group timing for all actuated pedestrian movements (Note, this may
allow for a cycle length that is shorter than needed if the actuated pedestrian
movements are called which will in turn require subsequent transition
cycles).
► Best2 – Same as the Best Way mode above with the exception of how the
transition point is decided. Under any other transition mode, the local dial will
halt whenever a coordinated signal group is not green at the beginning of its
computed split. With the Best2 mode, the local dial will continue to run as
long as the all coordinated signal groups will be able to time the larger of
their Min Green or Perm Min Green times. This results in extra slack in the
cycle that will prevent unnecessary transition.
3.2 Detectors
3.2.1 Vehicle
3.2.1.2 Delay
The amount of time a detector input must have continuous presence before
placing a call to the Call signal groups.
3.2.1.3 Extend
The amount of time that Extend SGs will be extended after the detector input is
off. See Detector Mode for alternate uses of the Extend time for different modes.
on all detectors enabled for the Added Initial Mode and the Added initial time
defined for the signal group. The actuation count will then be reset to zero.
3.2.1.8 Call
Signal Groups that are called when the detector input is on.
3.2.2 Pedestrian
3.2.3 Queue
The 16 queue detectors are designed to detect vehicle queues that will impede
traffic flow if not cleared. Each queue detector is linked to a vehicle detector. A
queue detector must sense a programmable duration of constant presence
before activating. Once the queue detector has activated, it must sense a
programmable duration of no presence before it deactivates. Once a queue
detector is activated it can alter the controllers pattern mode, initiate a preempt,
alter signal group max times, or adjust transit priority operation.
presence for the Delay On time period, the queue detector will be activated. A
value of zero disables this queue detector.
3.2.3.2 Delay On
The Vehicle Detector Number must sense a constant presence for this time
period before the queue detector is activated.
3.2.3.4 Control
Once the queue detector has activated, it will modify the control mode according
to the value of this parameter:
► None – The control mode will not be modified.
► Free – The controller will run Free.
3.2.3.5 Alt Pattern 1 – If the controller is running an active coordination pattern, the
controller will run the ExplicitForceOffs
During an active coordination pattern, activates explicit Force Offs defined in the
pattern instead of using Splits.
3.2.3.6 ExplicitPermissives
During an active coordination pattern using explicit Force Offs defined in the
pattern, activates explicit Permissive Periods defined in the pattern instead of
using automatically defined Permissive Periods. These can only be used with
explicit Force Offs.
► AltPattern1 programmed for the active pattern.
► Alt Pattern 2 – If the controller is running an active coordination pattern, the
controller will run the AltPattern2 programmed for the active pattern.
3.2.3.7 Action
Once the queue detector has activated, the controller will take the following
action based on the value of this parameter:
► None – No action will be taken.
► Max2 – The controller will enable the Max 2 timing for the signal group
programmed in the Action Index parameter.
► Max3 – The controller will enable the Max 3 timing for the signal group
programmed in the Action Index parameter.
► Preempt – The controller will place a preempt call for the preempt number
programmed in the Action Index parameter.
► Priority SG – During a transit priority request, the controller will modify the
following operations of the signal group number programmed in the Action
Index parameter:
The signal group will not be omitted due to the transit priority request.
The signal group green time will not be abbreviated due to the transit
priority request.
3.3 SC Communication
SC communication allows interaction between two or more signal controllers. The
communication is defined within VISSIM and this table allows you to specify how the
information will be used in this controller or what values will be sent from this controller.
3.3.1 SC Communication
3.3.1.3 Connect To
This defines where the information from the channel will be used.
► None – No action will be taken.
► Preempt detector – The controller will send or receive calls, based on the
In/Out value, to/from the channel for the Preempt detector programmed in
the Index parameter.
► SG Status – The controller will send or receive the status, based on the
In/Out value, to/from the channel of the selected SG Number defined in the
Index parameter. Output values are as follows: 1 for green, 2 for amber, 3
for red, and zero for anything else.
3.3.1.4 In/Out
This value defines whether the Channel will be used for sending or receiving.
► None – No action will be taken.
► In – The controller will receive values from the channel for the signal group
programmed in the Index parameter.
► Out – The controller will send values from the channel for the signal group
programmed in the Index parameter.
3.3.1.5 Index
This defines the number for the selected Connect To option. For Preempt
detector, this defines which Preempt detector will be accessed by the channel.
For SG Status, this defines which signal group will be accessed by the channel.
3.4 Preempt
Please note that this is a licensed feature and is not available with all VISSIM license
levels.
Normal preempts are traditional preempts that are activated by a presence input or by a
check-in/check-out input pair. Normal preempts have the typical track clearance, dwell,
and exit states (all but the dwell state can be omitted).
There are 2 available preempts. The signal groups and overlaps permitted in the dwell
state will serve normally. Upon entering Dwell, the controller will place calls to ALL Dwell
Vehicle Permit signal groups until one or more of these signal groups are timing.
3.4.1 Preempts
3.4.1.1 Preempt #
Internal ID number per preempt.
3.4.1.2 Enabled
This parameter determines whether or not the Preemptis enabled to run. No
disables the preempt while Yes enables the preempt and allows the controller to
respond to preempt calls.
3.4.4.1 Inputs
These are the internal preempt input ID numbers.
3.4.4.3 Presence
Presence detector number to be used within VISSIM for the corresponding
Preempt input; numbers hard coded as 401-410. Calls using this detector
number will be lost when the vehicle leaves the detector.
3.4.4.4 Check In
Detector number to be used within VISSIM for the corresponding Preempt input,
numbers hard coded as 411-420. Calls using this detector number will place a
check in call with the Preempt; the call remains checked in until the
corresponding Check Out detector gets a call.
3.4.4.7 Lateness
This parameter defines the threshold value in minutes for lateness in order to
cause a Preempt. Lateness is only used with Error! Not a valid bookmark
self-reference.s. The vehicle must be later than the defined lateness value in
order to receive priority. Values permitted are -600 to 600 seconds.
Priority service for any Transit SG can be enabled. When a Transit SG operates in a
priority mode, signal groups that conflict with the Parent SGs of a Transit SG can be
abbreviated or omitted based on the following parameters. The controller will attempt to
adjust its operation so that it can have the Transit SG green by the time the vehicle
arrives at the intersection.
PRIORITY/
RECOVERY SG SG SG SG
CYCLE 3/7 4/8 1/5 2/6
Minimum Cycle
Priority Extension Maximum
Extension,
recovery begins
PRIORITY
SG 1/5 SG 2/6 SG 3/7
CYCLE
PRIORITY
SG 3/7 SG SG SG 2/6
EARLY 4/8 1/5
CYCLE
Priority Early Adjustment (with SGs 1+5 Omit) – (Priority SGs 2+6)
NORMAL
CYCLE SG 3/7 SG 4/8 SG 1/5 SG 2/6
Minimum timing –
SGs 1&5
PRIORITY
EARLY SG 3/7 SG 4/8 SG 2/6
CYCLE
3.5.2.1 Transit SG
There are 8 Transit SGs available. The signal groups numbers for transit priority
are hard coded as SG 301-308. The signal groups are not necessary for transit
priority to be used, but allow additional flexibility if you wish to have a separate
signal head for the Transit Priority movement. The Transit SGs will not be
available within VISSIM unless you select Use as VISSIM SG.
SG 2 SG 1
SG 5 SG 6
LRV
SG 2 SG 1
SG 5 SG 6
LRV
Priority times with its sole
parent SG
3.5.2.7 Yellow
The time a Transit SG will time a yellow indication before advancing to red. This
time can not be abbreviated by any operation. Values permitted are zero to 25.5
seconds.
3.5.2.10 Extension
This parameter defines the time that a Transit SG will extend its green interval
following the dropped detection (either loss of presence on a Presence detector
or Check Out on a Check In/Check Out detector). During this extension, the
Transit SG will remain green unless Parent SGs are terminating before the
extension expires. Values permitted are zero to 255 seconds.
3.5.2.12 Priority
By default, transit priority requests with lower estimated travel times are served
ahead of transit priority requests with higher estimated travel times. For higher
priority transit movements, the Priority should be defined to a higher value than
that of lower priority transit movements. Transit movements with higher Priority
values (regardless of estimated travel time) will be served ahead of those with
lower Priority values. Values permitted are zero to 255.
cycle (the cycle following the priority extension). The controller can only extend
the Priority SGs to the point where it can still serve the greater of the Min Green
time or Recovery Minimum Green time to all subsequent signal groups by the
end of the next cycle.
EARLY
PRIORITY SG 3/7 SG 4/8 SG 1/5 SG 2/6
(COORD)
CYCLE
PRIORITY/
SG SG SG SG
RECOVERY 3/7 4/8 1/5 2/6
CYCLE
computing whether the controller can serve the signal group, it takes into
account the time required by all signal groups that must time prior to the priority
service.
3.5.5.1 Inputs
These are internal transit input ID numbers.
3.5.5.2 Call
Signal groups that receive a vehicle call and extension while the transit detector
input is on. It is not necessary to flag the transit Parent SGs since any Transit
SG with a call will automatically call its Parent SGs.
SG 2
SG 6
3.5.5.13 Lateness
This parameter defines the threshold value in minutes for lateness in order to
receive priority. Lateness is only used with Calling Point Detectors. The vehicle
must be later than the defined lateness value in order to receive priority. Values
permitted are -600 to 600 seconds.
3.5.5.17 Presence
Presence detector number to be used within VISSIM for the corresponding
Transit input; numbers hard coded as numbers 301-308. Calls using this
detector number will be lost when the vehicle leaves the detector.
3.5.5.18 Check In
Detector number to be used within VISSIM for the corresponding Transit input;
numbers are predefined as numbers 311-318 but can be edited. Calls using this
detector number will place a check in call with the Transit SG; the call remains
checked in until the corresponding Check Out detector gets a call.
4 Examples
Figure 32: Signal Head & Detector Placement for Signal Controller 2
Figure 37: Signal Head & Detector Placement for Signal Controller 3
4.4 Preempt
The Rail Road Preemption settings described in this section only controls an intersection
near a rail road crossing. The rail road gate will require an additional signal controller.
The RR Gate Crossing VAP shown in this example is intended for this use. The two are
meant to be used in conjunction; however, the RR Gate Crossing may be used alone.
During Clearance, traffic blocking the tracks is cleared from the intersection before the
train arrives. Dwell occurs while the train is crossing the intersection and allows traffic
that is non-conflicting with the train to continue. Opening the Preempt.ini settings file
within the RBC dialog will allow you to see the timing in the same format as in the
figures. Features of this example include:
► Controller frequency of 1 (the VAP used in this example for the Gate uses 1);
► 3 vehicle signal groups;
► Vehicle Signal Groups 2, 4, and 8 are all actuated and have detectors that call and
extend the signal groups;
► Preempt Inputs 1 & 2 are used, 1 for North Bound and 2 for South Bound;
► Check In/Check Out detection for Preempt;
► The Gate VAP uses Presence detection;
► Signal Group 2 is coordinated;
► Cycle length is 110 seconds;
► Offset is 0 and is referenced to LeadGreen;
► Exit mode is In Step;
► Zero SG Green is set for signal groups 2 & 4 (this causes the signal to immediately
go to clearance for these signal groups when the Preempt triggers the Check In
detector.);
► Track Clearance 1 is used to clear the West Bound movement, and is 12 seconds;
and
► Signal Group 2 is a Dwell SG, allowed to run with the Preempt.
Figure 42: Signal Head & Detector Placement for Signal Controller 2
5 Troubleshooting / Services
5.1 Troubleshooting
5.1.1 Errors
Message: "The cycle length:# for Pattern:# does not match the accumulated split
length:#. This may cause problems in the simulation."
5.1.2 Warnings
Message: "SG:# has been marked as coordinated, and was placed in ring:#,
barrier:#. However ring:# does not contain any other SG in barrier:# that is also
coordinated. The signal will run in free mode unless at least one coordinated SG
exists in each ring."
Message: "Walk Rest Mode is only possible for coordinated SG's, however the
SG:# has been checked for WalkRest, but not for coordinated. WalkRest will be
ignored unless the coordinated box is checked.
Message: "[Added Initial | Max Initial] has been set for SG:#, but vehDetector:#
uses that SG, and does not have AddedInitial enabled. The mode must be
enabled in order to work as added initial."
Message: "SG:# has a MaxGreen of #s, but a MinGreen of #s. The MinGreen
will supersede the Max." or…
"Pattern:# uses SG:# with a MaxGreen of #s, but a MinGreen of #s. The
MinGreen will supersede the Max." or…
"Pattern:# uses SG:# with a Split of #s, with available green time of #s, but its
MinGreen is #s. The MinGreen will supersede the allotted green time."
Message: "Pattern:# uses SG:#, which is coordinated, but has a split of 0. The
controller will determine the split time automatically, but it may not be what is
desired, or expected."
Message: "In Free Running Mode with no pattern definded, PedSG:# has length
of #s, but the SG:# that it is attached to has a green time of #s. The ped timing
cannot exceed that limit.” or…
Pattern:# uses PedSG:#, which has a length of #s, but the SG:# that it is
attached to has a green time of #s. The ped timing cannot exceed that limit."
Message: "Pattern Schedule has overlapping start times (t=#sec) for rows {#,
#,..., #}. Only the last one will take effect."
Message: "Signal Group Column ### had its SG changed from ### to ###. This
will update any signal group associations to signal heads, stop signs, etc. for the
original signal group number to the new number within VISSIM."
Your license level does not support Transit Priority. Values set in this table will
be ignored during simulation." or…
Your license level has somehow become corrupted, and it is not recognized as
being valid."
5.1.3 Messages
5.2 Services
5.2.1 Links
5.2.1.1 Website
PTV America's website is at: http://www.ptvamerica.com.
5.2.1.2 Training
PTV offers training classes both for new and advanced users. Classes can be
arranged as training-on-the-job at whatever location you prefer, or you may join
one of our set training sessions. Details are available on our websites at
http://www.ptvamerica.com/training/.
5.2.1.3 FAQ
At http://www.ptvamerica.com/support/vissim/vissim-faq/ you can find a wide
selection of FAQ (frequently asked questions) on VISSIM.
For all clients with a software maintenance contract, an extended range of FAQ
is available after entering the password supplied with the program license (see
letter of delivery with your VISSIM package).