Detectors
The Detectors section is designed to add, edit, configure, and remove detectors from the System.
When you click on Menu item Detectors, you go to the detectors page which contains a filter and a list of all detectors existing in the System. The filter specifies parameters for sorting detectors by name, project, connection status, ID, state of the switch responsible for the primary data analysis, and application of the duplication algorithm.
Next to the list name of Detectors, information about the total number of detectors in the System is displayed.
In the table below the Filter parameters on the Detector page
| Parameter | Description |
|---|---|
| Name | Field for entering the detector name |
| Projects | The drop-down list displays a list of projects available to the user |
| Detectors without project | Clicking on the button displays all detectors that are not associated with the project |
| Connection status | The drop-down list displays a list of available detector operating statuses. The choice is made by setting a checkbox. By default, all connection statuses are selected |
| Detector ID | Field for quick sorting of detectors by detector ID |
| Analysis | Application of primary analysis of data coming from the detector |
| Doubling algorithm | Applying the phantom object removal algorithm |
The list allows you to sort by the parameters specified. In addition, the Detector list parameters
| Parameter | Description |
|---|---|
| # | The serial number of the entry in the list |
| Name | Detector name specified when adding the detector to the system |
| Project | The project to which the detector belongs in the System |
| Project status | Status of adapter connection to the detector. The status is displayed as a switch. When you click on the icon, the detector status changes to inactive |
| Connection status | Detector connection indicator. The element shows the status of data exchange with the detector; detailed descriptions of detector statuses in Detector operation status section. |
| Errors | An exclamation mark icon is displayed if all fields are not completely filled in when adding a detector |
| Analysis | Application of primary data analysis for this detector |
| Index | The detector index is entered in the field, which is assigned depending on the number of detectors in a given project (PUIDD 1, Adaptive intersection 4) |
| Doubling algorithm | Whether or not a phantom object removal algorithm is used for this detector |
| Number of lanes | Number of lanes on the road on which the detector is installed |
| Calibration | % discrepancy between statistical data and actually received data for the selected time interval |
| History of changes | Detector movement history |
Adding a detector
Adding a new detector to the System is done by clicking on the button Add detector to the pages Detectors and on the interactive map at Home page left click and click on the button Create detector.
The administrator must be sure that the detector transmits data to the System - the equipment is available and the software is configured.
In the table are described the Add detector page parameters
| Field name | Field description |
|---|---|
| Detector name* | The unique name of the detector is entered in the field |
| Detector type* | Select the series of the custom detector from the drop-down list |
| Detector index* | The detector index is entered in the field, which is assigned depending on the number of detectors in a given project (PUIDD 1, Adaptive intersection 4) |
| Project status | The switch that is responsible for turning on detector to the list of those polled by the adapter when connecting to adapter via DB or RabbitMQ. If you configure the adapter through a config file to display the detector in the web interface the commands sources must be specified. Otherwise the detector wont be displayed on the map |
| Organization* | The organization to which the detector belongs in the System. It is displayed if more than one Organization is registered on the System |
| Project* | The drop-down list indicates the project in which the detector will be included |
| Data latency *, ms | The delay time for receiving data from the detector is entered in the field. By default it is recommended to specify value = 60000 |
| Waiting for connection*, ms | The wait time for detector connection is entered in the field. By default, it is recommended to specify value = 100 |
| Advanced Mode | Checkbox for enabling advanced mode to the detector. This mode should only be enabled for detectors with series TMS.0C |
| Interface type | In the field, select the type of connection to the detector |
Depending on the type of DT created, the set of fields for filling out will change
Interface type Ethernet (TCP), Ethernet (UDP)
| Field name | Field description |
|---|---|
| Adapter/Detector IP address* | The IP address of the adapter or the IP address of the detector is entered in the field, depending on the survey type: - If "Client" is selected in the "Poll Type" field, the IP address of the computer on which the adapter is deployed, it is indicated. - If “Server” is selected in the “Poll Type” field, the IP address of the detector is shown |
| Adapter/Detector port* | The adapter port or detector port to which the detector sends information depending on the polling type |
| Survey type * | It is used for selecting the operating mode of the equipment: * Customer * Server |
Type Ethernet (TCP), Ethernet (UDP) interface for TMS.13
| Field type | Field description |
|---|---|
| Detector IP address | Detector IP address depending on the survey type. |
| Data port | Port through which objects and PVR are transmitted |
| Port for commands | The port through which commands are sent to the detector and responses to these commands are received |
| Survey type * | In the field the operating mode of the equipment: * Customer (inactive) * Server |
Interface type RS485
| Field name | Field description |
|---|---|
| Port name | Port number, for example COM1 |
| Transmission speed | Specify the transfer rate in bits/sec |
| Number of bits | Standard RS connection setup |
| Number of stop bits | Standard RS connection setup |
Ethernet interface type (Multicast)
| Field name | Field description |
|---|---|
| Adapter IP address | Enter the IP address of the adapter in the field |
| Detector IP address | The IP address of the detector is entered in the field |
| Detector port | The port used to communicate with the detector |
| Multicast group IP address* | Enter the IP address of the multicast group in the field |
| Multicast group port* | Enter the port of the multicast group in the field |
| Survey type | In the field the operating mode of the equipment: * Customer (inactive) * Server |
Detector location
| Field name | Field description |
|---|---|
| Place name | Enter the name of the location in the field detector installation |
| GPS coordinates (lat, long) * | The field indicates the GPS coordinates of the detector installation location. When creating a detector on the interactive map, this field is filled in automatically. |
| Detector direction* | In the drop-down list select the viewing direction of the detector related to the beginning location (0 kilometer) of the road on which the current detector is installed. |
| Picket * | The name of the detector picket is entered in the field. |
| External IP equipment | The name of the router IP address or the IP address of PUIDD |
External relay
| Field name | Field description |
|---|---|
| Active relay | This section is available for editing only when the mode is enabled. Switch to connect the detector to an external relay (it is used for sites where detectors are installed at intersections mostly) |
| Relay IP address* | Enter the IP of the external relay in the field |
| Relay port* | Enter the port number of the external relay in the field |
| Check interval*, sec | The value (in seconds) of the external relay check interval is entered in the field. |
| Number of HW errors * | Enter the number of permissible relay hardware errors |
| Control Packet IDs | In the drop-down list, select the control packet identifier value to be sent to the relay |
| Waiting for detector to reboot* | The reboot waiting time from 60 to 120 seconds is entered here |
| Additional Information | A description of the detector and additional information about the detector |
| Road type | In the drop-down list, you can select a road type from the road type directory |
| Create | A detector with parameters entered by the user is added to the system |
| Cancel | Cancel all changes |
(*) - It means that the field is mandatory
You can determine the location of the zero (0) kilometer of the road on which the custom detector is installed on the website of the Road Funds Control System of the Federal Autonomous Institution ROSDORNII by using the following links:
When installing a detector at an intersection (as part of the PUSO), the specified intersection is taken as zero.
Here the Control packet ID values to be sent to the relay
| Control Packet IDs | Description |
|---|---|
| 0X2FF | Message synchronization (for 2G model) |
| 0X320 | Fast boot/bootloader mode (for all detector models) |
| 0X3A0 | Detector setup (for 2G model) |
| 0X3F2 | Message for transmitting new parameters and initiating various commands to the detector (for 2G model) |
| 0X400 | Diagnostic message about detector setup (for model UMRR-0C) |
| 0X430 | Coprocessor status message (for TMIB model) |
| 0X434 | Coprocessor status message (for UMRR-0C model) |
| 0X500 | Sensor Control Message (all detector models) |
| 0X501 | Message about the number of transmitted objects and the number of messages for each object (for all detector models) |
| 0X502 | Message with object length according to class (for model UMRR-0C) |
| 0X700 | Message about detector parameters (for model UMRR-0C) |
| 0X734 | Coprocessor Status Message (for model UMRR-0C) |
| 0X780 | Message with statistical data (for all detector models) |
| 0X785 | Message about PVR from the detector (for all detector models) |
| 0X786 | Output queue message (for all detector models) |
Required fields whose values are entered incorrectly will be highlighted in red. The values in them must be changed. After entering the parameters and clicking the Create button, the system will prompt the user to save the entered data without entering additional configuration parameters (then, click the Finish button) or enter additional detector configuration parameters (click the Configuration button to do this).
Editing detector information
The page for Editing Detectors includes sections: Detector Configuration, Calibration. This functionality is configured jointly by an engineer with Superadmin role.
You should move the mouse cursor over the line in the list with the selected detector or click on the edit button To change the detector parameters. When you click on the specified button, the detector editing page will open.
All section parameters in Main settings section are the same parameters that apply when adding a detector.
Additionally, information from the detector is displayed in the form of subsections: Detector software/hardware - this information is transmitted from the detector, and sections Detector zones, Detector stripes, Installation Options — are filled in automatically when the adapter starts. The data in the sections listed above can be updated by clicking on save button.
In the table you can find the Detector Zones page parameters
| Field name | Field description |
|---|---|
| Zone index | The serial number of the entry in the list |
| Vehicle classes | Number of vehicle classes |
| Direction | Direction of movement of detection zones |
| Distance from detector, m | Distance from DT in meters |
| Zone length, m | Length of the DT zone in meters |
| Zone width, m | DT zone width in meters |
| Band index | Band index |
| Band index for report | The index of the band that will be displayed in reports. Setting this parameter is used only if no bands are received from DT |
Besides the Detector Strip page parameters
| Field name | Field description |
|---|---|
| Band index | The field displays the indices of the zones associated with this DT |
| Band type | Changeable parameter, lane type from the road editor |
| Counting lines | The field displays the number of counting lines |
| Direction | The field displays the direction of the detector stripes |
| Splines | The field displays the number of points for bending the road |
| Bandwidth, m | The field displays the DT bandwidth in meters |
| Strip length, m | The field displays the length of the DT strip in meters |
Here the Installation Options page options
| Field name | Field description |
|---|---|
| Mounting height | The field displays the installation height of the diesel engine |
| Azimuth correction | The field displays the angle of installation of the DT in azimuth |
| Zenith | The field displays the zenith angle of the DT installation |
You should turn on o switch Settings mode to edit a section Configuration.
In addition, you must press the button Save to save the changed detector settings, and to cancel the changes made, the button Cancel.
Configuration
This window allows you to configure the detector configuration. The detector configuration contains:
- Algorithm for removing duplicate objects
- Additional DT configuration options - detector network parameters, tracking parameters, detector detection parameters, camera parameters.
Algorithm for removing duplicate objects
Double objects - these are cases when the same vehicle is mistakenly counted twice by the system due to the characteristics of the detectors or conditions on the road.
The algorithm for removing double objects can only be used for German radars series TMS.0 A, T.0C, TMS.0F, MS.11, MS.12 series (operating frequency = 24 GHz). This algorithm is not used for detectors series TMS.13 and TMS.14 (operating frequency = 77 GHz).
Manual calculation of vehicles is performed using video from surveillance cameras. The lanes of the road are numbered from left to right relative to the direction of the detector. In case of manual calculation, it is required to take the number of vehicles, more than 100 units in order to reduce the magnitude of the calculation error.
If there is a discrepancy between the number of objects recorded by the system and their actual number, it should be determined in which direction (greater or lesser) the discrepancy is going.
Underestimation of the number of registered vehicles may be caused by detector settings during the PNR. Check and/or reconfigure the detector to correct the issue. Furthermore, you should contact a certified support engineer.
If the vehicle statistics are overestimated (i.e. there is a significant difference between the data obtained as a result of manual calculation and the web interface), algorithms for removing double objects should be activated.
Double object removal algorithms should be activated only when vehicle statistics are overestimated.
The algorithm should be applied to all lanes of the same direction at once!
In the detector editing page you can configure the algorithm for deleting double objects by the web interface. Just turn on the Setup mode switch to activate the Configuration tab, where the parameters for deleting double objects are set. The parameters of the section for removing double objects are selected iteratively until an error in the number of vehicles is ± 3-5%, and according to their classification ± 10%.
The results of calculating the number of vehicles that passed during the selected time interval are available on the Statistics section in Detailed reports page. Besides, there are possible options for dividing the counting period into intervals (for instance: 1, 5, 10, 15 and 30 minutes).
In the table below are described the Parameters for the Delete Double Objects section
| Field name | Field description |
|---|---|
| Use duplicate object removal algorithm | The parameter activates the main mechanism for eliminating duplicate objects. It is important to ensure that the detectors are reporting data to the system and that the traffic lanes are set to them. If you try to activate without meeting these conditions, a warning will be displayed: The detector has no stripes. The algorithm cannot be turned on. Connect the detector and configure the stripes |
| Clean by PVR | The algorithm analyzes vehicle passages through counting zones and excludes double objects based on the following criteria (following each other): - Time between 2 vehicle passes <=800 ms - Speed difference <5 km/h - Difference in direction of movement in degrees <10 - Length difference <4 m - Band difference <2 |
| Clean by object | An algorithm that activates the removal of double objects by analyzing vehicle tracks in each lane: - Distance between objects <10 m - Speed difference <3 km/h - Difference in direction of movement in degrees <5 - Length difference <4m - Band difference <2 |
| Clean by PVR v2 | The algorithm is designed to eliminate double objects (moving in parallel), providing increased accuracy in identifying unique vehicles in counting areas in the corresponding lanes: - Time between 2 vehicle passes = 0 μs - Band difference = 0 |
| Clean by PVR v3 | The algorithm is responsible for enabling duplicate removal if the PVR algorithm does not demonstrate adequate duplicate removal performance. The algorithm uses the following parameters: - Time between 2 vehicle passes <=1 s - Speed difference <2.5 km/h - Difference in direction of movement in degrees <5 - Band difference <2 |
| Clean by objects v2 | The algorithm, which is responsible for enabling the removal of double objects for objects on each strip configured in the detector, tracks vehicle tracks: - Distance between objects <15 m - Speed difference <2.5 km/h - Difference in direction of movement in degrees <5 - Band difference <2 |
| Clean by objects v4 | An algorithm that is responsible for enabling the removal of double objects by v2 objects on each band configured in the detector (recommended for experienced System users) |
Signs of double phantom objects
Double or phantom objects have characteristic features: non-directionality and the same speed of movement. The assessment is carried out throughout the entire detection zone of the detector:
- The phantom object
followsthe physical object at a slight distance at the same speed, repeating the changes in the trajectory of the physical object. - A phantom object can
movenext to (parallel) a physical object. In this case, the location can be either without an offset relative to the physical object, or with an offset. - A phantom object can also
overlaya physical object.
If the configured detector does not have any configured bands, the System will display a message stating that the double object algorithm cannot be used.
Additional detector configuration options
In this section you will find the Additional detector configuration parameters.
Detector network parameters
| Parameter type | Description |
|---|---|
| Detector IP address | Detector IP address |
| Mask reminded the detector | Mask reminded the detector |
| Detector gateway | Detector gateway |
Tracking options
| Parameter type | Description |
|---|---|
| X-point coordinates (lat, long) * | The field indicates the X coordinate of a point located at a distance of about 50 meters in the direction of viewing of the detector |
| Y-point coordinates (lat, long) * | The field indicates the Y coordinate of a point located at a distance of about 50 meters perpendicular to the viewing direction of the detector |
| Detector rotation angle (degrees) | The set angle of rotation of the detector relative to the road is entered in the field. |
| Previous detector* | In the drop-down list, select the name of the previous network detector |
| Distance to previous, m * | Distance between detectors from current to previous |
| Next detector * | In the drop-down list, select the name of the next detector |
| Primary data analysis | Switch that activates primary analysis of data from the detector |
Detector detection parameters
| Parameter type | Description |
|---|---|
| Distance to stop line | The distance to the vehicle stop line is entered in the field. |
| Detection distance | In the field, enter the distance at which the detector will perform the initial registration of objects |
Camera options
| Parameter type | Description |
|---|---|
| Use camera | Switch to configure camera settings |
| Camera IP address | The IP address of the camera is entered in the field |
| RTSP-URL of video stream | The RTSP-URL of the camera video stream is entered in the field |
| Manufacturer | Select the camera manufacturer from the drop-down list |
| Preset number | Select the camera preset number from the drop-down list.The preset number is located in the camera web interface |
| Camera login | The camera login is entered in the field |
| Camera password | Enter the camera password in the field |
| Save | Saving detector settings |
| Cancel | Cancel all changes |
(*) - It is a required field
Calibration
This page will display a list of all DT calibrations loaded into the System. You must click the button Add calibration to add a calibration to the System.
Adding a Calibration
In the Detectors page you should select the specific device. Next click on tab Calibration, and then on button Add Calibration
In the table below Add Calibration page options are described
| Field name/Buttons | Field description |
|---|---|
| Count date | The calibration date is selected in the calendar. This field is required. The default is the current date |
| Added by user Full name | This field indicates the full name of the engineer who configured the equipment. This field is required |
| Vehicle class group* | A group of vehicle classes combined into a group. This field appears only when you select the counting type by Direction and classification |
| Counting type | The system for calibration comparison is selected from the drop-down list. In this list, the user can select data for comparison with the System data - depending on the choice of calculation type, the table for entering diesel fuel calibration data will change. |
| The configuration file | A file in .tisf format is added to the field. Clicking on Browse opens a navigation window for selecting a file |
| File the form | A file in .tisf format is added to the field. Clicking on Browse opens a navigation window for selecting a file |
| Period for downloading detector data | The time period for which the equipment operation error is calculated is entered in the field. |
In addition the Table for determining measurement error. Here the direction of the DT is indicated
| Error type | Description |
|---|---|
| Counting type/Class | According to the selected calibration type |
| Statistics data | Statistics data obtained from DT |
| Factual data | Actual data counted by counters |
| Error | Change error |
(*) - Field is required
Fields whose values are entered incorrectly will be highlighted in red. Their values must be changed in the adding calibration section.
Removing a Calibration
Click on the Delete button to remove a calibration from the System, and confirm deletion in the dialog box.
Removing a detector
Click on the Delete button to remove a detector from the System. When you click on this button, you must confirm the deletion of the detector in a pop-up window by clicking the button or cancel the deleting action by pressing the button Cancel.