Status  -  Coordination   (MM->7->2)

The Coordination Status screen provides the active pattern and the status of the various operation modes (or OpModes) which are used to select the active pattern (see Streetwise ATMS Hierarchy of Control ).  The Coordination screen also shows how far "out of step" the current offset is relative to the programmed offset and indicates the alternate maps used with the current pattern.

OpModes (Operation Modes)

The Current Operation Mode from any of the following sources:

• REMO (Remote Control) - manual control pattern issued from the StreetWise ATMS
  

• TEST (Test Mode) - manual control pattern issued from the Test OpMode (MM->2->1)
  

• SYS ( System Control) - the secondary is defined in a master or sub-master closed loop system and  "Closed Loop" is programmed ON under MM->2->1
  

• TBC ( Time Base Control) - the secondary schedule under MM->4 is used to select the plan
  

• BTBC ( Backup Time Base Control) (same as TBC, the secondary falls back to this mode if the closed loop system fails)
  

• MTBC - Master Time Base Control - the master schedule under MM->9->5 is currently being used to generate the active plan (the MTBC pattern in the master is the SYS pattern in the secondary controllers defined in the master's closed loop system)

The Coordination Status screen also indicates the Active pattern running in the controller.  When a pattern change is requested by the current operation mode, the new pattern is shown as Next and becomes Active when the local cycle counter of the active pattern reaches zero.

Current Cycle and Offset Information

The Coordination Status Screen shows the Programmed cycle length and Programmed offset of the current pattern and indicates how far the controller is out of step.  Keep in mind that the offset is referenced to either BegGRN (beginning of green) or EndGRN (end of green) of the coord phase programmed in the split table of the active pattern - see MM->2->5 (right screen).

The following example shows a controller that is in shortway transition.  When the controller gets in step, the SHORT message is replaced by SYNC and the Err: value is zero.

The difference between the Local cycle counter and the Tbc cycle counter is the Programmed offset.  The Tbc  counter is the repeat cycle counter beginning at midnight  (see  the "Online Time-Base Calculator" for more information on time base coordination).

In the example above, 14" is the Programmed cycle length, so the Local counter should be 14" past the Tbc counter - 81" + 14" or 95".  

However, the Local counter is at 20" which is 120" + 20" - 95" or 45" ahead of the Tbc counter.  So the Local counter has a +45" offset error and the controller is currently in a SHORTway transition to correct this error.

Alternate Maps Attached to the Active Pattern

The bottom right area of the Coordination Status screen displays any alternate maps currently called by the active pattern.

The example above indicates that the active pattern is using alternate phase interval times from MM->1->1->6.  Alternate phase options, call/inhibit/redirect (CIR) and detector programming can be called by pattern using MM->2->6.  This area of the Coordination Status screen displays a zero if an alternate map is not used or the alternate map number currently implemented in the active pattern.