Coordinate  -  Pattern Table   (MM->2->4)

The NTCIP pattern table (2.5.7 PATTERN TABLE) is shown above.  Each Pat# references a unique cycle, offset, split and sequence combination with "no dependencies on other rows" (current NTCIP definition).  Pat# 1 and Pat# 2 in the above menu show the minimum and maximum values of the following NTCIP objects.

2.5.5 MAXIMUM PATTERNS PARAMETERS         - 48 patterns are provided for the Ver 50/60/61 controllers

2.5.6 PATTERN TABLE TYPE                          - Naztec supports the Patterns table type
                                                                (each row in the table represents a unique pattern
                                                                  independent of the other patterns for maximum flexibility)

2.5.7.1 PATTERN NUMBER ENTRY                       - Pat# ("read-only") cannot be changed 

2.5.7.2 PATTERN CYCLE TIME                        - Cycle length defined in seconds (0-255)

2.5.7.3 PATTERN OFFSET TIME PARAMETER      - NTCIP only references the Offset (seconds) to the beginning of
                                                              the first coordinated phase. 
         See MM->2->5, right menu to reference the offset to the begin or end of the specified coord phase.

2.5.7.4 PATTERN SPLIT NUMBER PARAMETER - the Split table programmed in MM->2->7

2.5.7.5 PATTERN SEQUENCE NUMBER PARAMETER -  references the Sequence table (MM->1->2->4)

2.5.8 MAXIMUM SPLITS -  The maximum number of splits in ver 50/60 is 24 (32 split tables in version 61).

You can also associate alternate phase and detector tables with patterns (MM->2->6) and program additional parameters that are associated with the Pat#.  Please note that calling a Pat# with a 0" cycle length, implements free operation with all the sequence, alternate timing maps and parameters associated with that pattern.

Naztec recommends that you program Pat# 1-24 with Split# 1-24 so there is a one to one relationship between Pat# and Split#.  This will make it easier to manage your system, because if you can easily reference the correct Split Table# given the Pat#.