Wrong Direction
Wrong Direction utilises object tracking to trigger an alarm if a person or vehicle is not moving in the direction set by the user in a given area. The direction and the area dimensions are configurable, as well as the degree above which objects are considered to be going in the wrong direction.
The zones and the direction(s) that are considered to be "right" are configured via Regions of Interest (ROI), by using the Camera Editor.
- Core technology: full body and vehicle detection with object tracking.
- A camera with a minimum of 10 FPS is required!
- Minimum object size: 60 pixels.
- Compatible with fixed, PTZ, and thermal cameras.
- Areas of interest can be defined.
- Send data to third-party software.
Uses 1000 analysis slots by default - see the table below for resource usage percentages on specific hardware.
| Hardware | Resource usage (percent) | Solution number limit on device |
|---|---|---|
| Nvidia Jetson NX | 100% | 1 |
| x86-64 | 14% | 7 |
New Wrong Direction
- Choose Wrong Direction by clicking on its box. Fill in the form, as follows:
- Name: A readable name of this alarm. This name will appear in the Events view and in all notifications.
- Armed: The alarm can be deactivated here. Armed by default.
- Schedule (optional): You can associate one of your previously defined Schedules with this alarm.
- Add Camera: Select a camera from the list.
NOTE: Cameras below 10 FPS will not show up on the list of cameras for Wrong Direction!
- Draw Areas (ROI) (mandatory): The direction a road lane goes in is determined by drawing a Direction Area type of ROI. At least one such ROI is necessary for the alarm to function. Only objects inside the area are detected - no negative ROI are necessary to exclude areas.
Set object size (optional): If you have a good idea of what pixel range the detected objects would fall into, you can customise the minimum and maximum height size of detections, in pixels, here. This would ensure that only objects that fit into that range would get detected, resulting in a further decrease in the number of false alarms.
Move the the arrows by clicking and dragging them to help you determine the optimal values. Adjust the slider's endpoints on the bottom part of the screen to set the minimum / maximum values. Click Set sizes to save your changes, or Discard to cancel them.
NOTE: Take care that any object below or above the set range will NOT be detected, possibly resulting in missing incidents. It is good practice to set the minimum size slightly below, and the maximum size slightly above the desired amount.
For example: If using Ultinous AI Suite with a combination of radar and PTZ cameras, setting custom object sizes would result in detections only if the radar have detected movement - since setting the proper minimum size would rule out random noise causing false detections.
Sensitivity: The sensitivity of the detector can be fine tuned here. Lowering the sensitivity causes less false detections but decreases accuracy. Increasing it results in more alarms but may cause more false detections as well. The default sensitivity is Medium.
Object types: Choose any number of object types from this list (Car by default).
Tolerance (in degrees): The degree at which an object is considered to be in the wrong direction, compared to the direction set in Draw Areas. The default degree is 90˚.
Click the Submit button to save your settings or proceed to Integration.
Integration (optional)
Ultinous AI Suite offers a wide range of possibilities when it comes to integration with third-party services. Follow the links below to read their respective entries in the guide.
HTTP webhook (Milestone XProtect or custom solution via alarm API) Enables / disables event sending: Use this feature to send triggered events to a third-party software with an optional snapshot image of the incident attached. Sends a HTTP POST request to the URL set below, with a content type of
application/json. Read on to learn about the schema formatting. It is also possible to include an End of Event timestamp, which triggers if 5 seconds have passed without incidents after the initial event that triggered the HTTP message. End of Event occurs once the incident is over.The following information should be provided by the third-party software's administrator:
Target URL: The location of the API.
Header keys and values: Key and value of custom HTTP header. Click the Add button to add more Keys. To delete a Key, press the Trash icon next to it.
Trust all certificates: If enabled, HTTPS certification errors will be ignored.
NOTE: Custom CA certificates can be uploaded in the Control Panel, under Trusted Certificates.
Enable snapshot attach (not applicable to Milestone XProtect): Off by default. If enabled, it fills in the
snapshotfield of the HTTP message schema in base64 encoded format.Send end of event: Enables / disables End of Event sending. Note that the Cooldown setting of the Alarm has no effect on this.
End of Event records are sent as part of HTTP messages. They are not available in Milestone XProtect or in e-mail format.
Send Test Event: To test your integration, click the Send Test Event button once the HTTP webhook settings are set.
SMTP or Central Station Monitoring software
