Before you can monitor CitiLog media servers or CitiLog SmartTraffic-TD ACAP running on Axis cameras as traffic sensors in Security Center, you must add CitiLog units as TSS entities to the plugin.
Before you begin
- From the Config Tool home page, open the Area view task.
- Click Add an entity () and select TSS.
From the TSS model list, select CitiLog,
and then enter and entity Name.
Tip: For better search indexing, it is a best practice to include the location of the sensor in the name.
Click the Properties tab and configure the entity
- Stale data age
- If the system does not receive data for a zone by the time indicated here, it considers the data to be stale.
- Analytics schedule
- (Optional) If the TSS device sends alerts only, select a schedule to receive alerts. Alerts received while the schedule is inactive are discarded.
- Maximum cached data age
- Specifies the maximum time within which data from the TSS zone can be reused.
When the TSS plugin is restarted, it stops storing the last known status of each zone. If the status is more recent than the time specified, it is used as the initial zone status for the zone. If it is older, the zone initializes with no data available.
- Override icon traffic parameter
- If enabled, select the data type that controls the color of the zone icon.
For people counting, if the default traffic icon parameter is not set to Volume in the plugin properties, select Volume.
- Zone icon size
- Size of the zone icon displayed on maps, in pixels.
- No data threshold
- If the TSS entity does not receive data from the device by the time indicated here, it triggers the custom TSS no data event.
Click the Communications tab and set the communication
- Polling interval in seconds.
- Period, in seconds, for collecting and displaying data.
Select and configure the data source type for your TSS entity:
- Media server data source
- Data source
- Select the previously configured CitiLog media server data source.
- Camera ID
- Enter the Camera ID from the CitiLog media server for this TSS unit.
- Manage analytics
- Select to allow Security Center to send analytics management commands to the CitiLog media server, such as disabling alerts based on operator commands or schedules.
- Camera data sourceNOTE: This data source type only works if you are using a CitiLog SmartTraffic-TD ACAP on an Axis camera.
- Data source
- IP of the camera in IPv4 format.
- Port of the camera to poll for CitiLog data. The default value is 20803.
- Media server data source
- To use simulated data for all zones of the TSS unit, select Simulation.
- Click the Zones tab.
Click , and in the Add/Edit
CitiLog Zone dialog box, configure the zone's properties:
- This sets the ID of the zones in the camera’s field of view.
- Zone description
- Enter a description for the zone.
- Vehicle Class
- CitiLog integrations can send up to five count values to the TSS plugin, tagged as “Count”, “C1”, “C2”, “C3” or “Hazmat”, which can act as filters for the TSS zone. Select which vehicle classification types are added together as the count for this zone.
- Lane ID
- Enter a lane ID for the zone.
- Scheduled analytics
- Select to allow the analytics schedule set at Step 4 to apply to this zone.
- Travel time node ID
- (Optional) Enter the corresponding node ID from the Travel Times Engine where the average speed data is sent to. Travel time detection must be configured in the TSS plugin.
- Select the direction of traffic. If you are using analytics confirmation macros, this setting can be configured to find all zones that are the same or opposite direction of the zone that triggered the analytic.
- Click OK.
Select the new zone. On the right of the Zone list, set the
When enabled, threshold persistence prevents the zone state from changing rapidly when data is fluctuating around the threshold point.
- For each zone configured with a third-party traffic sensor system that you want to associate to the entity, repeat steps 9 - 11.
- Click Apply.
From the entity tree, right-click the TSS entity and select Put
Security Center starts polling or accepting data from this sensor.