Phases - Ring / StartUp / Concurrency (MM->1->1->4)
|
|
The following definitions were taken from the Naztec Version 50/60/61 Software Manual. Object references are also provided based on NTCIP specification 1202 for each "read-write" data object present in the controller menu shown above.
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.2.1 PHASE NUMBER is a "read-only" object and is fixed for the 16 rows of data in the above menu (shown in red). Therefore, you can't change the PHASE NUMBER under the Ø column, but you can change the "RING", "STARTUP" and "CONCURRENT Ø" objects associated with PHASE NUMBER 1-16 in this menu.
| Ring | 2.2.2.22 PHASE RING PARAMETER - This parameter indicates the ring number of the associated phase. The Ring object cannot exceed the the "read-only" MaxRings object (maximum of 4 rings for a Naztec ver 50/60/61 controller). |
| Startup |
2.2.2.20
PHASE STARTUP - The phase Start Up parameter determines the start up state for the associated phase. The settings are described below.
|
| Concurrent Ø's | 2.2.2.23 PHASE CONCURRENCY - The Concurrent Phases define the barriers of the phases assigned to different rings. The Concurrent Phases may time currently with the associated phase and are similar to permissives programmed for the MMU or conflict monitor. The associated phase listed in the Ø column does not need to be included in the list. |