Detectors  -  Vehicle Parameters   (MM->5->1)

Hint! - Click on a Vehicle Parameter to get Help, then return to this screen by typing the "b" key.

 <- Det#  NoAct  MaxPres  ErrCnt  FailTime
     1      0       0        0        0
     2    255     255      255      255
     3      0       0        0        0
     4     15      10        0        0
     5      0       0        0        0
     6      0       0       30        0
     7      0       0        0        0
     8      0       0        0        0
     9      0       0        0        0
......
    64      0       0        0        0
 

NTCIP detector diagnostics originated with the TS2 specification 3.9.3.1.4 - Detector Diagnostics.

These diagnostics check for a no-call and constant call on each detector using the above test values (in minutes).  For example, detector # 4 will fail if it doesn't receive a call within 15 minutes (NoAct) or if the detector locks on for more than 10 minutes (Max Pres).  Detector # 6 will also fail when the counts exceed 30 counts per minute (ErrCnt).  This diagnostic is useful to isolate "chattering detectors" in the system.

The NoAct thresholds can generate unwanted error late at night.  However, you can override NoAct with an Alternate Detector Program that is called by a free pattern late at night to avoid these errors.

 

 

 

 

 

 

 

 

 

 

 

 

 

NTCIP Object Reference - Detectors - Vehicle Parameters (MM->5->1)

The NTCIP 1202 references for the Vehicle Parameters are provided in the following table:

NoAct 2.3.2.8 VEHICLE DETECTOR NO ACTIVITY PARAMETER - This diagnostic feature determines the amount of time that must pass without a detector actuation before the detector is considered to have failed. The time is specified in minutes (0-255 min). A failed detector will place a call on the assigned phase, and the failure will be logged in the Occupancy data. A value of 0 disables this feature. 
MaxPres 2.3.2.9 VEHICLE DETECTOR MAXIMUM PRESENCE PARAMETER - This diagnostic feature determines the amount of time that must pass with a constant detector actuation before the detector is considered to have failed. The time is specified in minutes (0-255 min). A failed detector places a call on the assigned phase, and the failure is logged in the Occupancy data. A value of 0 disables this feature.
ErrCnt 2.3.2.10 VEHICLE DETECTOR ERRATIC COUNTS PARAMETER - This diagnostic feature determines the number of counts per minute (0-255 cpm) that must occur before the detector is considered to have failed. A failed detector places a call on the assigned phase, and the failure is logged in the Occupancy data. A value of 0 disables this feature.
FailTime 2.3.2.11 VEHICLE DETECTOR FAIL TIME PARAMETER - If a detector diagnostic determines that a detector is in failure mode, then Fail Time places a call on the assigned phase during all non-green intervals. The Fail Time parameter determines the amount of time in seconds (0-255 sec) that the actuation will continue into the green interval of the assigned phase. Essentially, this parameter determines how long to keep an Extend on the phase from the start of the green interval.