Phase Options (MM->1->1->2)

 Options        Ø..1..2..3..4..5..6..7..8 ->   
         Enable Ø  X  X  X  X  X  X  X  X
       Min Recall  .  X  .  .  .  X  .  .
       Max Recall  .  .  .  .  .  .  .  .
       Ped Recall  .  .  .  .  .  .  .  .
      Soft Recall  .  .  .  .  .  .  .  .
       Lock Calls  .  X  .  .  .  X  .  .
 Auto Flash Entry  .  .  .  X  .  .  .  X
 Auto Flash Exit   .  X  .  .  .  X  .  .
       Dual Entry  .  X  .  X  .  X  .  X
 Enable Simul Gap  .  X  .  X  .  X  .  X
 Guarantd Passage  .  .  .  .  .  .  .  .
     Rest In Walk  .  X  .  .  .  X  .  .
 Condit'l Service  .  .  .  .  .  .  .  .
   Non-Actuated 1  .  .  .  .  .  .  .  .
   Non-Actuated 2  .  .  .  .  .  .  .  .
   Added Init Calc S  S  S  S  S  S  S  S

 

 

 

 

 

 

 

 

 

 

 

NTCIP Object Reference - Phase Options (MM->1->1->2)

The following definitions were taken from the Naztec Version 50 Software Manual.  Object references are also provided based on NTCIP specification 1202 for each "read-write" data object in the above menu.

Note that all the database elements in this menu are stored as "bits" (Yes or No values) within the Phase Options object defined in NTCIP 1202, section 2.2.2.21 for each phase in the controller. 

NTCIP makes a distinction between "read-write" objects (data you can edit in the controller menu) and  "read-only" objects (constants that cannot be changed by the user).  For example, NTCIP object 2.2.1 MAXIMUM PHASES is a "read-only" object and is fixed at "16" for the Naztec 16 phase controller.  

NTCIP 1202 defines the ACCESS attribute for each data object that governs the "read" and "write" access of the object and whether it is accessible from protocol messages.  NTCIP objects designated as "read-only" will be shown in red in the example menus presented here to emphasize that these values cannot be changed by the user.

Enable Ø  2.2.2.21 PHASE OPTIONS (bit 0) - The Enable Phase option indicates whether or not the associated phase is used in the current configuration. A disabled phase does not generate any outputs or respond to any phase inputs.
Min Recall 2.2.2.21 PHASE OPTIONS (bit 6) - Minimum Recall places a call on the associated phase when the phase is not timing the green interval
Max Recall 2.2.2.21 PHASE OPTIONS (bit 7) - Maximum Recall places a call on the associated phase while the phase is timing the red and yellow intervals, and extends the associated phase to the Maximum Green time.
Ped Recall  2.2.2.21 PHASE OPTIONS (bit 8) - When enabled, Pedestrian Recall causes a recurring call similar to an external call. However, it will not recycle pedestrian service until a conflicting phase has been served.
Soft Recall 2.2.2.21 PHASE OPTIONS (bit 9) - Soft Vehicle Recall generates a call on the associated phase when all conflicting phases are in Green Dwell or Red Dwell, and there is no serviceable conflicting call. For example:
  • Min Recall on Ø2 and Ø6 - if Ø4 is being serviced and a call comes in on Ø3, then Ø2 and Ø6 must be serviced before Ø3 even if no calls exist on Ø2 and Ø6.
     
  • Soft Recall on Ø2 and Ø6 - if Ø4 is being serviced and a call comes in on Ø3, then Ø3 will be serviced before Ø2 and Ø6.
Lock Calls  2.2.2.21 PHASE OPTIONS (bit 5) - When Lock Calls is enabled, the controller locks calls at the beginning of the yellow interval.

NOTE: The controller data object "Lock Calls" conforms to the NTCIP definition "Non Lock Detector Memory"; however, the menu display is inverted because the definition "Lock Calls" is easier for users to understand than "Non Lock Calls"..
Auto Flash Entry 2.2.2.21 PHASE OPTIONS (bit 1) - When Automatic Flash is actuated, the controller services the designated entry phases, clears to all red, then proceeds with flashing operation. 
Auto Flash Exit 2.2.2.21 PHASE OPTIONS (bit 2)  - When Automatic Flash is complete, the controller proceeds to the beginning of phases designated as exit phases.
Dual Entry  2.2.2.21 PHASE OPTIONS (bit 10) - Enabling Dual Entry causes the associated phase to activate upon entry into its concurrency group (crossing a barrier), and there are no calls in its ring within its concurrency group.
Enable Simul Gap 2.2.2.21 PHASE OPTIONS (bit 11) - Enabling Simultaneous Gap for a phase allows the Passage timer to reset while a compatible phase in another ring is timing Passage and there is a call on a conflicting phase.  

For example, assume that main street phases are Ø2 and phase Ø6.  

  • If Ø2 gaps out while Ø6 is being extended, the Ø2 Passage timer will reset if Enable Simultaneous Gap is set  and Ø2 receives a new call.
      
  • However, if Ø2 gaps out while Ø6 is being extended and Enable Simultaneous Gap is NOT set for Ø6, then Ø2 will remain in the gap-out state until Ø6 terminates (even if a new vehicle call is received on Ø2).  

This is a very important setting for the through movement phases during actuated operation.  If Enable Simultaneous Gap is not set, you can easily create the situation when one main street phase remains gaped out when the leading edge of a platoon of vehicles begins hitting the detector. 

NTCIP defines bit 11 as Simultaneous Gap Disable and setting bit 11 to 1 disables simultaneous gap.  Naztec inverted the logic in the controller menu after discovering that users were confused about "enabling the option to disable the feature".   The logic defined by NTCIP for this bit is maintained according to the standard; however, it is much easier for users to understand that enabling this option with an 'X', "enables" simultaneous gap instead of "disabling" it.
Guarantd Passage 2.2.2.21 PHASE OPTIONS (bit 12) - Guaranteed Passage is used for operation in volume density mode (using gap reduction): This option enables the actuated phase to retain the right of way for the un-expired portion of the passage time after the decision to terminate the green due to a reduced gap.

Note:  This option was not defined by NTCIP to provide a "full" Passage extension  after the phase has gapped out.  The option only insures that the "unexpired" portion of the Passage time is provided at the point of gap out.
Rest In Walk  2.2.2.21 PHASE OPTIONS (bit 13) - Actuated Rest-In-Walk causes an actuated phase to rest in walk until there is a conflicting call after the the end of timing the walk.

Rest-In-Walk is typically used in coordination with Walk Recycle to reservice the ped indications on the coordinated phase. The coordinator calculates a point in the cycle called PedLeav (MM->2->8->2) which terminates Walk and begins Ped Clearance to end at the force-off for the phase.

Condit'l Service  2.2.2.21 PHASE OPTIONS (bit 14) - Conditional Service causes a gapped/maxed phase to conditionally service a preceding actuated phase. 
Non-Actuated 1 2.2.2.21 PHASE OPTIONS (bit 3) - The Non-Actuated 1 option indicates that the associated phases responds to hardware Non-Actuated 1 inputs.
Non-Actuated 2 2.2.2.21 PHASE OPTIONS (bit 4) - The Non-Actuated 2 option indicates that the associated phases responds to hardware Non-Actuated 1 inputs.
Added Init Calc 2.2.2.21 PHASE OPTIONS (bit 15) - Added Initial Calculation indicates how the controller uses the detector added initial data. The programmed value ‘S’ sets bit 15 to zero.  The programmed value ‘L’ sets this bit to 1.

To increase inital by summing detector actuations from all detectors assigned to a phase, set this option to ‘S’ (Sum). To use the largest detector accumulation during the red and yellow interval, set the option to ‘L’ (Largest).