Axis thermal cameras provide heat-based detection for monitoring property or detecting thermal anomalies which could lead to incidents involving smoke or fire. This guide is intended to introduce the use of these devices with your exacqVision VMS software.
Requirements
Axis Q19 Series Camera
Camera firmware 11.8 or higher
exacqVision Server/Client 24.09 or higher
At the time of writing this article, these instructions pertain to the Axis Q19 Series of cameras and assume you have already located the device on your network and logged into the web browser interface.<br><br>
Thermometry Configuration
Detecting a Temperature Change (Temperature Tripwire)
Expand the Thermometry menu from the left-hand side, then select Temperature Reading. <br><br>
Select a color palette of your choice from the Palette menu on the right.<br><br>
Set the Temperature unit you intend to use, either Celsius or Fahrenheit. <br><br>
Select Temperature detection, beneath the Thermometry menu on the left. <br><br>
Back on the right, select Add detection area. <br><br>
Use the handles to drag out the bounding area on the video panel to highlight the polygonal area of interest.<br><br>
Provide a descriptive name in the Name field, such as “High Temperature” or “Low Temperature” depending on what you may be concerned about sensing.<br><br>
Enable the Use area control to enable monitoring this detection area.<br><br>
Set Temperature in area choice.
If detecting a high temperature is desired, choose ‘Warmest Spot’ from the Temperature in area options. Then select ‘Above’ and enter the temperature degrees you wish to be alerted at.
If detecting a low temperature is desired, choose ‘Coolest Spot’ from the Temperature in area options. Then select ‘Below’ and enter the temperature in degrees you wish to be alerted at.<br><br>
You may wish to adjust the Delay field time if some fluctuation is expected in the region. This setting will allow the event to trigger only after remaining above/below the set temperature threshold for a given amount of time.<br><br>
The Include detection area in video stream selector determines if, or when, the bounding area is included in the video stream as it will be sent to exacqVision.<br><br>
Checking the Include temperature checkbox will display the detected temperature.<br><br>
Detecting Smoldering Fire
The Thermometry functionality of the camera combined with the Early Fire Detection app may be used to sense if a fire could ignite in a designated area. The early fire detection app filters uninteresting moving objects, to minimize false alarms.
Expand the Thermometry menu from the left-hand side, then select Temperature Reading. <br><br>
Select a color palette of your choice from the Palette menu on the right.
NOTE: Axis recommends avoiding the use of palettes beginning with ‘Iso’ for best performance, preferably using the ‘White-hot’ option.<br><br>
Set the Temperature unit you intend to use, either Celsius or Fahrenheit.<br><br>
Select Temperature detection, beneath the Thermometry menu on the left. <br><br>
Back on the right, select Add detection area. <br><br>
Use the handles to drag out the bounding area on the video panel to highlight the polygonal area of interest.<br><br>
Provide a descriptive name in the Name field. If you were monitoring a waste disposal area for the potential of a fire, you might name this “Waste Bin”.<br><br>
Enable the Use area control to enable monitoring this detection area.<br><br>
Use the Temperature in area control to select ‘Warmest Spot’ and ‘Above’.<br><br>
Within the temperature field, enter 50°C (122°F)<br><br>
Open the Apps menu from the left-hand side of the screen.<br><br>
Enable the Early Fire Detection app.
NOTE: At the time of this writing, this app is a beta release, version 1.2.0.<br><br>
Select the Open button for the Early Fire Detection app. <br><br>
Examine each of the defined detection areas on the right-side of the screen to ensure they are active for early fire detection.<br><br>
exacqVision Use
Add the camera to your exacqVision Server, using the AXIS VAPIX Device Type, following the steps shown in How to Add IP Cameras – Manual Method.<br><br>
Select the camera from the left-hand navigation tree to reach the camera settings page.<br><br>
Select the Analytics tab from the bottom half of the page <br><br>
A panel lists each analytic from the camera, including each detection region you defined on the camera as well as an ‘AnyArea’ option which acts as an alert when any of the regions have been triggered. Users may define the appearance of bounding areas for each analytic separately.<br><br>
Users may also configure Event Linking or Event Monitoring actions to occur when any of these analytics are triggered. Use these to perform actions such as sending SMTP email notifications or change views for live viewers. More details on configuring Event Linking and Event Monitoring can be found in the exacqVision Client User Manual or the video links at the bottom of this page. <br><br>
When configured properly, exacqVision may be configured to react to Elgato Stream Deck to take actions, such as changing camera views or activating output alarms. This is made possible by exacqVision’s Serial Profile settings combined with Event Monitoring or Event Linking. This guide provides the steps needed to get started, which you may customize to suit your needs.
IMPORTANT: This guide is provided for user benefit, but Exacq Support will not provide assistance or troubleshooting for Stream Deck devices or Stream Deck software.
<br>
Stream Deck Configuration
Download and install the Stream Deck software, which includes drivers needed to recognize the device when plugged into your workstation as well as software used to customize its behavior.<br><br>
Open the Stream Deck software from the Start menu or system tray on the taskbar. Stream Deck has limited capabilities out of the box, but provides a marketplace where developers offer plugins to expand its functions, similar to adding apps to your mobile phone or tablet.<br><br>
With the Stream Deck software window open, access the Marketplace by selecting the Marketplace icon, which will open a web browser to the Marketplace page.<br><br>
Use the search field to find CommandSender, which at the time of this writing was the most capable plugin available for this purpose and free to download and install.<br><br>
Click on CommandSender in the search results, then select the Get button. Once installed, return to the Stream Deck software.<br><br>
Locate and expand the Custom section from your actions panel on the right, then expand the CommandSender item. Drag an instance of the Send Command action from the panel onto a button in your layout. This button is customized in the lower part of the window.<br><br>
Set the Communication Type to ‘TCP’.<br><br>
Enter the IP address of the system running your exacqVision Server into the IP Address field. The Port number defaults to ‘45671’, but you may customize this if that port is already being used on your system.<br><br>
In the Command Pressed field, enter something unique and descriptive to the action you want to take. In the pictured example we enter GoToCamera 09 because in later steps we will configure a camera panel to change when pressed. This text can be anything you’d like because you will pair it to an action in later steps.<br><br>
Next, add the code for a line feed, \x0a, to the end of your command. This is used to help separate commands when received by exacqVision.<br><br>
You will not use the Command Released field for use with exacqVision.<br><br>
Finally, you can choose to customize the icon using icons from Stream Deck, import icon packs from the Marketplace, or upload custom icons you’ve created. You also have an optional Title field.<br><br>
You may add as many instances of the CommandSender plugin to your button layout as you wish, but the Command Pressed field should be unique for each one. The IP Address and Port fields should be the same unless you are sending commands to different NVRs.<br><br>
<br>
exacqVision Serial Port Configuration
You will need Full Admin or Power User privileges on the system to perform the following steps. The steps in this section are performed only once on each NVR you are sending commands to.
Open the exacqVision Desktop Client application and enter Configuration mode by selecting the cog wheel icon in the upper-left corner.<br><br>
From the left-hand navigation panel, expand the system name, then select the Serial Ports node on the tree.<br><br>
Under the IP section, press the New button.<br><br>
In the new row that appears, enter something in the Name field, such as “Stream Deck”.<br><br>
Change the Use column to ‘POS’.<br><br>
Change the Profile field to ‘New…’.<br><br>
Change the Type field to ‘TCP Listener’.<br><br>
In the Address column field, enter the IP address of the workstation you have plugged your Stream Deck into.<br> NOTE: It is expected that you will connect the Stream Deck to a Client workstation, but if you are connecting it directly to the system running the exacqVision Server application, the IP Address used here and in CommandSender will be 127.0.0.1.<br><br>
In the Port field, enter the port number displayed in CommandSender, which by default is ‘45671’.<br><br>
The remaining fields are left as is.<br><br>
Because ‘New…’ was selected in the Profile column, when you press the Apply button you will be automatically taken to the Serial Profiles page to configure the profile described in the next section.<br><br>
<br>
exacqVision Serial Profiles Configuration
Begin by providing a descriptive Name to your Serial Profile.<br><br>
Test the ability to receive commands from the Stream Deck by pressing the configured CommandSender button on the panel. You should see the commands you configured on the button appear in the data window.<br><br>
For this use case you do not need to enter anything into the fields for SOT marker or EOT marker.<br><br>
Select the Event Keywords tab.<br><br>
Press the New button.<br><br>
In the String field, enter the text exactly as you entered when configuring the button in CommandSender, without the line feed code.<br><br>
Press Apply to save your changes.<br><br>
<br>
NOTE: If you need additional help with the configuration of Serial Ports or Serial Profiles, please see the exacqVision User Manual or refer to our User Training Videos on the Exacq Support Portal covering these features.
<br>
Event Monitoring and Event Linking
As this document is not intended to be a complete training guide on the use of exacqVision’s Event Monitoring and Event Linking features, we will provide a single example of changing a camera panel to display another camera when the button is pressed. Keep in mind that Event Monitoring provides client-side actions visible to the user of the workstation, such as changing camera panels, live Views, enabling audio, or digital PTZ presets, while Event Linking performs server-side actions, such as recording video, mechanical PTZ presets, auto exports, sending notifications, or triggering webhooks.
NOTE: For additional help with the configuration of Event Monitoring or Event Linking, please see the exacqVision User Manual or refer to our User Training Videos on the Exacq Support Portal on these features.
For this example:
Select the Event Monitoring node on the navigation tree, located near the top of the left-hand panel.<br><br>
Press the New button under the Profiles panel and enter a descriptive Name in the Profile Configuration area to the right.<br><br>
Change the Show Event List field to ‘On Event’.<br><br>
Check the Show Newest Event box.<br><br>
Set the Type selection to ‘Video Panel’.<br><br>
The first Client Action is added for you. Configure the default action by selecting ‘Default’ from the Event Type panel. Default events do not have an Event Source to select.<br><br>
From the Action Type panel, select ‘Switch Video’.<br><br>
Select a camera from the Action Target panel to display when nothing else is being triggered.<br><br>
Press the New button under the Client Actions panel in the middle of the window.<br><br>
From the Event Type panel, highlight ‘Serial Profile’.<br><br>
You may have many items listed on your system, or several systems to select from. The drop-down menu will filter to specific systems or show them all. Select the item displaying the name of the Serial Profile you created earlier with the Keyword you configured. The profile is monitoring the incoming data being sent from CommandSender on your Stream Deck for this Keyword.<br><br>
Select ‘Switch Video’ from the Action Type panel.<br><br>
Choose a camera from the Action Target panel that you want to display when the Stream Deck button is pressed.<br><br>
Next, you’ll set exacqVision to return to the Default camera after a set number of seconds rather than forcing a user to click in the Event List panel to acknowledge it each time.<br><br>
Uncheck the Confirm checkbox near the bottom of the window.<br><br>
Change the Timeout field to “5”.<br><br>
Press the Apply button to save your changes.<br><br>
<br>
Use the same Event Monitoring profile you just created to continue adding additional Client Actions for each CommandSender button you have configured on the Stream Deck.
Navigate to the Live view in the Client window to test your setup.
Drag several different cameras to the layout.<br><br>
Right-click one of the panels. In the menu that appears, expand Event Monitor, and select the name of the Event Monitoring profile you just created. The camera you configured as the Default should display. <br><br>
Press the CommandSender button you created on the Stream Deck. This camera panel should now change from the default camera to the camera you configured in your Event Monitoring profile with the Event Keyword.<br><br>
After the 5 second timeout period you set, the camera panel should return to the Default camera.
<br>
Opening the exacqVision Client
If you’d like to create a button on your Stream Deck to automatically open an instance of the exacqVision Client, this can be done without additional plugins or serial data configuration using the built-in Open action.
Within Stream Deck, perform the following:
Expand the System menu from the actions panel.<br><br>
Drag an instance of the Open action from the panel onto an empty button in the layout.<br><br>
Customize this instance near the bottom of the window.<br><br>
Provide an optional Title and/or customize the button’s icon.<br><br>
In the App/File field, either navigate to the edvrclient.exe file on your machine, or enter the path manually. The default path is C:\Program Files\exacqVision\Client\edvrclient.exe
Users of customized Client .XDV files may open instruct the Open action to open the client using their desired .XDV file by adding the file path to the file. e.g.- C:\Program Files\exacqVision\Client\edvrclient.exe -F"C:\Users\myUserName\Documents\myCustomFile.xdv"
Axis offers a camera-based License Plate Verifier application for detecting and reading vehicle license plates. The data from the license plate captures may be viewed within the exacqVision Client as text, sent as serial over IP data. This document provides the steps to set up the integration with exacqVision.
NOTE: This guide is not meant to be a comprehensive guide for the Axis application itself. For greater details on licensing and configuration settings of the Axis License Plate Verifier, please refer to Axis support and documentation.
<br>
Requirements
Axis License Plate Verifier is currently supported on specific Axis camera models, using firmware 8.40 and higher. Visit Axis for a list of cameras compatible with this application.
<br>
Installing Axis License Plate Verifier
Mount the camera at the best viewing angle for license plate reading. (See User Manual for more information)<br><br>
Login to the camera’s web interface and access the Settings page.<br><br>
Depending on the camera firmware version, you may find the menu options along the bottom of the page or the side. Navigate to the Apps menu page.<br><br>
Select the Add or Add App option.<br><br>
Select the downloaded Axis License Plate Verifier application file.<br><br>
After successful upload, the Axis License Plate Verifier application will be shown in the list of installed apps.
<br>
Licensing
The Axis License Plate Verifier application requires licensing from Axis, purchased separately. Please contact Axis for license orders.
When purchasing, you may be provided with a license code. This code must be used to generate a license key and may be done in one of two ways.
Use the Axis License Key Registration page, to enter the serial number and license code. Download the generated license key file.
Use the automatic key generation feature of the application. This requires that the camera have direct internet connectivity to communicate with Axis.
Firmware 11.x
Select the vertical ellipses on the far-right side of the License Plate Verifier ribbon.
Choose either:
Activate with a license key to upload a key file
Activate license automatically to download from Axis
Enter the license code into the text field provided.
Press the Activate button
Firmware 10.x
Select the License Plate Verifier app
Choose either:
Use the center Install button to upload a key file
Enter the license code into the text field provided, and press the Install button beside it
<br>
Configuring the Application
Use the toggle switch to enable the application.
Wait for the Status to indicate the application is Running. Shown below are the indicators for firmware 11.x and 10.x.
Press the Open button to configure the application.
If presented with a setup wizard, select Skip.
<br>
The main menu for the application displays tabs for various configuration settings, as follows:
Event log – displays live video from the camera as well as a searchable history of detected plates. Press the Live button to display live video and live updates to the log.
List management – provides the ability to add plate numbers to Allow and Block lists for access control purposes.
Settings – camera image, event, and access control settings.
Integration – configuration settings to send license plate information to external systems.
Refer to the Axis License Plate Verifier documentation for greater details on each setting and optimization for best performance. Each installation site is unique, but a general order of steps to follow will likely include:
Select the Settings tab.<br><br>
exacqVision integration will not utilize the settings within the Access control section. These settings affect utilization of relays or the camera’s I/O ports to communicate directly with access control devices or compatible access control software.<br><br>
Within the Image panel, set the Resolution as needed.<br><br>
The Save full frame setting only affects images saved to the camera’s local storage and does not affect the streaming video received by exacqVision.<br><br>
Set the Region and Camera location based on the camera’s physical location to help optimize detection of plates expected to be read by the device.<br><br>
Use the Edit area of interest button to adjust the area the camera will look for license plates. Keep the area as small as possible, while permitting room for vehicles of various sizes and alignment to the entry/exit path.<br><br>
The Events section configures retention of events saved locally to the camera and does not affect the retention of data saved by exacqVision.<br><br>
The Detection parameters section allows users to determine how strict the device will be with regard to matching plates listed in the Allow and Block lists.<br><br>IMPORTANT: License plate character recognition accuracy may vary based on angle to camera, lighting and weather conditions, plate size, etc. These may be important considerations when used for access control.<br><br>
An Additional DataBETA is provided in License Plate Verifier versions 2.7.1 and higher to provide Country and Region of the plate. Enhancements in 2.9.19 and higher added Vehicle Type and Color. This data is included in the serial data regardless of being disabled and only controls the display of this data within Axis software.<br><br>
Utilize the Event log tab to monitor how changes to settings affect the ability to consistently match the license plates seen.
<br>
Sending Data to exacqVision
After configuring the License Plate Verifier application for best results, you must configure the application to send data to the exacqVision Server.
Within the License Plate Verifier application, select the Integration tab.<br><br>
Within the Push event panel, you will configure an active profile.<br><br>
Ensure the Protocol field is set to TCP.<br><br>
The Server URL field will be set to the IP address of your exacqVision Server, followed by a port number of your choosing to communicate with exacqVision. Example: 192.168.0.25:9080<br> NOTE: You will enter this port number later when configuring your exacqVision Server to receive communications from the app, and must be a port number unused by other applications or devices communicating with the server.<br><br>
You may choose to disregard the Device location settings if you’d like but the data entered here will be available in the data feed sent to exacqVision if you need to use it.<br><br>
The Device ID field may be disregarded as well, but may be helpful if multiple devices are in use. This data will also be available in the data feed sent to exacqVision.<br><br>
Under Event types, multiple options provide the ability to choose which data points are sent to exacqVision. New – first detection of a license plate Update – either a correction of a character on a previously detected license plate, or when a direction is detected as the plate moves and is tracked across the image. Lost – the last tracked event of the license plate before exiting the camera image, also contains the direction of the license plate.<br><br>
Depending on the version of License Plate Verifier you are using, enable the Do not send images or Do not send images through HTTP POST toggle control.<br><br>
Enable START to send event data to server.
<br>
exacqVision Serial Port Configuration
Configure the exacqVision Server software to receive the data sent from the License Plate Verifier app.
Open the exacqVision Client software and select the Configuration button (cog wheel icon).<br><br>
From the navigation tree along the left-hand side, expand the options shown beneath the name of the server.<br><br>
Select Serial Ports from the tree.<br><br>
Locate the IP connections panel and select the New button below it.<br><br>
Enter a helpful name to identify the connection. This example has named this “AxisLPR”.<br><br>
Select POS from the options in the Use column.<br><br>
Skip to the Type column and select TCP Listener.<br><br>NOTE: The TCP Listener type may never show ‘Connected’ in the Status column. This is normal. A TCP Listener sits and waits for data to be received and will only ever show ‘Connected’ while receiving data. However, the incoming data is often so fast as to be imperceptible. In between each burst of data received it returns to a waiting state of ‘Disconnected’.<br><br>
In the Address field, enter the IP address of the Axis camera you configured with the Axis License Plate Verifier in the steps above.<br><br>
Change the Max Line Length field to ‘250’. Some of the data sent by the application is rather long, providing file paths to files locally stored on the camera. The Max Line Length forces a new line when the specified number of characters is met. Making this large enough to accommodate long lines will make your job setting Line Masks easier in a later step.<br><br>
Return to the Profile column and select New. This will begin a new Serial Profile for you, configured in the next section. If you have a pre-existing profile for Axis License Plate Verifier, you may opt to select this instead.<br><br>
Press Apply.
<br>
exacqVision Serial Profile Configuration
The Serial Profile configuration determines how the incoming data is displayed or recorded and provides additional options for events, if needed.
Because New was selected from the Profile field in Serial Ports, a new profile is created automatically for you. Begin by changing the Name field to something descriptive for easy identification. The example shown has chosen to name this “AxisLPR”.<br> IMPORTANT: One of the most vital steps in getting Serial Profiles configured correctly is setting the SOT and EOT marker fields. These determine the beginning and end of each “transaction”. In the case of LPR these mark the start and end points of the data for each license plate detected by the camera.<br><br>
When configuring the SOT and EOT markers it can be helpful to enable the Show Raw Data checkbox to view hidden formatting characters. At the time of publishing this guide we are using Axis License Plate Verifier version 2.3-1 through 2.10.13. The data points provided by the License Plate Verifier may change with versions, as noted previously in Configuring the Application, Step 9. Below is a sample of the raw data provided from a single plate read using version 2.10.13 of the app.
Use the first line of the transaction to find a suitable SOT marker. In this case, the first line is {"packetCounter":"24947",\x0d\x0a. Watching the serial data, the packetCounter number changes with each transaction, so you should not use the entire line as the SOT. Instead enter just {"packetCounter" as the SOT to ensure that all transactions beginning with this string will be captured.<br><br>
Now find a suitable EOT marker. Note how each line is terminated with \x0d\x0a, these are invisible formatting characters to perform a line feed and return. This would make a poor EOT marker as it would separate every line as a new transaction. However, the last data point works well, "sensorProviderID":"defaultID"\x0d\x0a. Adding this to the EOT marker field properly marks the end of the transaction.<br><br>NOTE: Using Steps 3 and 4 will help you to correctly bracket serial transactions of any type or adapt to any changes in formatting from different versions of Axis License Plate Verifier.<br><br>
Leave the Parser and Marker Type fields as their default settings.<br><br>
Press the Apply button to save your changes.<br><br>
The Live Display tab allows you to view how the serial data overlay will appear on top of a live camera image or on an empty background and permits you to change the text formatting.
<br>
Line Masks
The Axis License Plate Verifier app sends several data points for each plate, some of which you may not wish to record or display to users of the exacqVision software. Line Masks hide all the text on any row with a matching string.
As an example, referring to the sample block of serial data in the previous section, one row begins with "imagesURI", listing the file path on the camera to the locally stored image. Most exacqVision users are unlikely to need this information. it may be hidden with the following steps.
Within the Serial Profile, select the Line Masks tab.<br><br>
Select the New button.<br><br>
In the empty row that is added, enter the text in the String column. In this example, the text entered is "imagesURI".<br><br>
The check boxes in the Live and Search columns for each text string determine where to apply the mask. If the box is checked for Live, the row will be hidden in Live view. If unchecked for Search, the row will still be displayed in serial search results. Checking both boxes will hide the row from both locations. In some cases it may be useful to hide data in Live, but leave it available in Search to perform forensic searches.<br><br>
Press Apply to save your changes.<br><br>
Repeat these steps as necessary for each line you wish to hide from Live or Search, using the Configuration or Live Display tabs to view your changes taking place.
<br>
String Replacements
In some cases you may find some text less human friendly. Selected text strings may be replaced to be more legible to users. Referring to the sample serial data block again, one of the data points provided is "plateRegion", which in the United States correlates with the State. This can be updated using the following steps:
Within the Serial Profile, select the String Replacements tab.<br><br>
Select the New button.<br><br>
In the empty row that appears, enter the text to be replaced in the String column. In this example it is "plateRegion". Including or excluding the surrounding parenthesis is your choice.<br><br>
In the Replace column, you will enter the text you wish to show instead. In this example is has been replaced with State.<br><br>
Just as with Line Masks, each entry has the option of being applied to Live or Search as you choose.<br><br>
Press Apply to save your changes.<br><br>
Repeat as necessary for each string of text you wish to replace in Live or Search, using the Configuration or Live Display tabs to view your changes taking place.<br>
NOTE: Line Masks and String Replacements do not support wildcard characters or regex expressions at this time. This means that you cannot reformat types of data which are different in every transaction, such as the date and time parameters. They will appear in the format send from the License Plate Verifier application.
<br>
Event Keywords
Keywords may be configured within exacqVision Serial Profiles to trigger user configured actions when the selected keyword is detected in the serial data feed. Example actions include recording video on detection of plates on the Block list, or sending a notification when a specific vehicle’s plate arrives. This guide provides two such examples below, each of which will then be configured with Event Linking in the following section.<br><br>
Example 1
In this example, there is more than one Axis camera running License Plate Verifier sending data to the exacqVision Server. You want to perform an action when activity is detected by one of the cameras. In this example the steps will record video.
Locate the "camera_info" field in the raw serial data, which contains the camera “SerialNumber” value. Make note of this value. <br><br>
Within the Serial Profile, select the Event Keywords tab.<br><br>
Select the New button.<br><br>
In the empty row that appears, enter the serial number value into the String column, and ensure the Enable checkbox is marked.<br><br>
Press the Apply button.<br><br>
Continue to the Event Linking or Event Monitoring sections below, for Example 1.
<br>
Example 2
Newer versions of the License Plate Verifier provide the "plateList" data point, which can tell you if the plate is on the Allow or Block list. However, older versions did not provide this. The steps in this example will use a workaround for this on older versions, then use this in Event Linking to send a notification.
Within the License Plate Verifier application, navigate to the List management page.<br><br>
Add a license plate number of interest to either the Allow or Block list. Leave the Description field empty for now. <br><br>
Return to the exacqVision Client and examine the raw serial data on the Serial Profiles page by checking the Show Raw Data checkbox.<br><br>
Locate the data property for “plateListDescription” and note that the value is empty. <br><br>
While the "plateListDescription" does not automatically contain any data, you can use the Description field to provide information for this or similar keyword uses.<br><br>
Return to the camera app on the List management page. Select the Edit icon for the previously entered license plate from Step 2 above. In the image below we have entered Deny beside the entry in the Block list. Save your change.<br><br>
Examine the raw data again in the exacqVision Serial Profile. The "plateListDescription" value will now display the description entered on the List management settings. You can now use this as an Event Keyword. <br><br>
Navigate to the Event Keywords tab in the Serial Profile.<br><br>
Select the New button.<br><br>
In the empty row that appears, enter the description used in the app in Step 6 above. In the image below, we have entered Allow and Deny as separate keywords. <br><br>
Select Apply.<br><br>
Continue to the Event Linking section below, for Example 2.
<br>
Event Linking
The Event Linking page provides the capability to automate server-side actions triggered by a wide range of events. Refer to the exacqVision Client User Manual or our Video Library for further details on configuring Event Linking beyond these examples.
The examples below continue from the numbered examples in the Event Keywords section above.
Example 1
This example continues from Event Keywords – Example 1 above to record from one of several Axis LPR cameras connected to the same exacqVision NVR.
Navigate to the Event Linking page within the exacqVision Client software.<br><br>
Select the New button near the bottom of the page.<br><br>
From the Event Type list, select Serial Profile.<br><br>
The Event Source list will display all Serial Profiles followed by the configured keywords available. Select the profile you intend to use as a trigger. In this example, we selected “AxisLPR – Keyword B8A44F0ADBE2”, where the keyword is the serial number.<br><br>
Select the Action Type from the next panel. In this example Record Video is selected.<br><br>
From the Action Target list, you will select the target, which in this example is the camera to be recorded when the keyword is detected in the serial data.<br> NOTE: Notice that we did not use the term “seen in the serial data”. The keywords may still be detected within the raw serial data, even if hidden from view by Line Masks or String Replacements.<br><br>
Press Apply to save your changes.
<br>
Example 2
This example continues from Event Keywords – Example 2 above with an example of sending a notification when a plate on the Block list is detected.
Navigate to the Event Linking page within the exacqVision Client software.<br><br>
Select the New button near the bottom of the page.<br><br>
From the Event Type list, select Serial Profile.<br><br>
The Event Source list will display all Serial Profiles followed by the configured keywords available. Select the profile you intend to use as a trigger. In this example, we selected “AxisLPR – Keyword Deny”, where Deny was previously entered as a keyword.<br><br>
Select the Action Type from the next panel. In this example, we have selected Notify.<br><br>
From the Action Target list, you will select the target, which in this example is a previously created Email Message Profile. NOTE: Sending a notification requires a successfully configured Email Server.<br><br>
Press Apply to save your changes.
<br>
Event Monitoring
Event Monitoring will not be covered in detail in this guide, but provides the ability to trigger client-side actions such as changing views on events. Refer to the exacqVision Client User Manual or our Video Library for further details on configuring Event Monitoring.
Example 1
This example continues from Event Keywords – Example 1 above as an illustration of changing the view displayed to the user when any license plate is read by the License Plate Verifier app.
This example requires at least two previously saved Views. One will display multiple camera panels to be shown to the user when no other activity is present. The second contain only the video from the Axis camera running the License Plate Verifier with the serial number entered as an Event Keyword in previous steps.
Navigate to the Event Monitoring page within the exacqVision Client software.<br><br>
Select the New button to create a new Event Monitoring profile.<br><br>
Enter a descriptive profile Name.<br><br>
Select On Event from the Show Event List setting.<br><br>
Check the Show Newest Event box.<br><br>
Select the View button from the Type field.<br><br>
Skip to the Event Type list near the bottom of the page and select Default.<br><br>
The Default type has no source option. Skip to the the Action Type panel and select Switch View.<br><br>
From the Action Target list, highlight the multi-camera view to be displayed when there is no activity.<br><br>
Uncheck the Confirm checkbox near the bottom of the screen.
Near the middle of the screen, under the Client Actions panel, press the New button.<br><br>
From the Event Type list, select Serial Profile.<br><br>
This example uses the serial number unique to the camera as the keyword to change Views. From the Event Source panel, locate the Serial Profile name followed by the camera’s serial number keyword and select it.<br><br>
Leave the Lasts at Least box unchecked.<br><br>
From the Action Type list, select Switch View.<br><br>
Use the Action Target list to select the view to change to. In the image below, this is our single camera view showing the Axis License Plate Verifier camera.<br><br>
If your Event Monitoring profile includes multiple view changes or LPR cameras, utilize the Priority setting to define which views take precedence.<br><br>
If the Confirm box is left checked, the view will not return to the Default view until the exacqVision user confirms they’ve taken note of the event. If unchecked, the Timeout setting determines how many seconds must elapse before automatically returning to the Default view.<br><br>
Press the Apply button at the bottom of the screen to save your changes.
Navigate to the Live view of the exacqVision Client.<br><br>
Activate the Event Monitoring profile by changing the left-hand navigation tree to Views. Scroll to the list of Event Monitors and drag the profile name to the live display panel. When data is received from the camera with that serial number, the view will automatically change to show that camera. Clearing events from the Event Monitor List that appears returns to the Default view.
<br>
Disable Client Indicator (optional)
Due to the nature of TCP Listeners only remaining periodically connected, as mentioned above in exacqVision Serial Port Configuration, Step 7, you may choose to disable the exacqVision Client Indicator message warning users of a loss in connection on the serial port.
Select Indicators from the left-hand navigation tree.<br><br>
If connected to multiple exacqVision Servers, select the system for which the Axis camera is sending license plate data.<br><br>
Locate the line item under Error that reads, “Serial port {Source Name} not connected on system {System Name}”, and uncheck the Enabled box for this item.
<br>
Serial Live View
After careful application of several Line Masks and a couple of String Replacements, the Live view provides just the information desired for the user. In this case, the Date/Time, license plate number, and State. Recall that the text may be formatted on the Live Display tab of the Serial Profiles page.
Navigate to Live view.<br><br>
Change the device list shown to Cameras.<br><br>
Find the name given to the Serial Port, then drag and drop it into a live camera panel to display serial data as it arrives. This can be done in an empty panel or as an overlay to live video.
<br>
Forensic Search
In the event you must search for a specific plate number, state, or other data, exacqVision provides the ability to search for serial data to expediate the process of locating events of interest.
Navigate to the Search page<br><br>
Checkmark the Serial Port providing the data you wish to search from the device tree on the left.<br><br>
Select the device(s) you intend to search. You may include more than one camera, in the pictured example we have only selected one.<br><br>
If you intend to search for specific terms in the serial data, enter this into the Search Serial text field provided. The drop-down allows you to select from previously used terms. This field is only provided when serial data devices are check marked for searching.<br><br>
Enter the dates and times of your Search Range into the provided fields.<br><br>
Press the Search button to populate the timeline with results.<br><br>
If you wish to see the serial data recorded, toggle the Show/Hide Keywords and Serial Data button.<br><br>
In the serial data explorer panel that appears note that the SOT and EOT markers configured in the Serial Profile affect the beginning and end of each transaction.<br><br>
Clicking on any of the transactions listed will move the playhead on the timeline to that event.<br><br>
Matches to serial data searched from Step 4 above, are highlighted.<br><br>
Matches to serial data searched will also thin the results of the serial data events displayed on the timeline.
<br>
Troubleshooting
Serial data includes massive block of random characters
Cause: The “ImageArray” block appears within the serial data feed when the camera is sending image data through the HTTP POST method.
Solution: Return to the Integration settings page of the License Plate Verifier app. Enable the Do not send images or Do not send images through HTTP POST setting.
This document will guide you through step-by-step procedures for keyboard use and suggested button mappings.
Product
Axis TU9001 Control Board
TU9002 Joystick
TU9003 Keypad
The Axis TU9001 Control Board consists of the combination of the TU9002 Joystick and the TU9003 Keypad.
IMPORTANT: The TU9002 and TU9003 appear to the operating system as separate devices. As of Client version 24.03 only one Joystick device may be enabled on a workstation at a time. This article will be updated in the case of further enhancements.
<br>
Setup
Follow the Installation Guide from Axis for the steps to attach the two devices and connect the corresponding USB cables.<br><br>
Plug the keyboard’s USB cable into the USB port on the Client viewing machine, where the keyboard will be operated from.<br><br>
Navigate to the Joystick configuration page within the exacqVision Client.
Select the cog wheel icon in the top left-hand corner of the Client window to enter Configuration settings.
Expand Client from the navigation tree on the left-hand side.
Select Joystick from the tree to load the Joystick configuration page.<br><br>
Select the joystick that appears from the drop-down menu. If the device fails to appear, close and re-open the exacqVision Client instance. <br><br>
Select the Calibrate button to zero out the joystick positioning.<br><br>
Adjust the sensitivity to your liking.
X/Y Axis controls camera Pan/Tilt, while Z Axis controls zoom.
Suggested settings include increasing the sensitivity on the X/Y Axis and Z Axis.
<br><br>
Pressing any of the buttons on the keyboard will highlight that number in the button menu to help you find the corresponding mapping. You may need to scroll the window if you do not see the button highlighted when pressed. <br><br>
Once you have located the button, you may use the drop-down menu to select the action you wish to assign to the button.<br><br>
After applying changes to the keyboard configuration, return to the Live camera view and the controls will be available for use.
<br>
Buttons on the TU9002 Joystick
The TU9002 features 7 buttons across the top of the device and 2 buttons on top of the joystick. The center Toggle button along the top acts as a Function Key. When pressed this will highlight button 17 in the button map, but you should notice the illuminated LEDs shift on the device. This toggles the ability to assign additional actions to each of the other buttons on the device.
For example, when the buttons are illuminated above, pressing J1 will highlight button 1 in exacqVision. If the center button is pressed, the illumination shifts below the buttons. Pressing the same button now highlights button 9 in exacqVision. The actions available in exacqVision Joystick settings do not align with the rewind, play/pause, forward symbols indicated on the device.
The TU9002 Joystick also features the ability to switch between joystick and mouse modes. The default mode is set to act as a joystick. Switch to mouse mode by pressing and holding the center Toggle button then press the J1 button. Moving the joystick now moves the mouse cursor. While in mouse mode the J1, J5, and left joystick button act as a left-click. The J2, J6, and right joystick button act as a right-click. Press and hold the Toggle button then press the J1 button again to revert back to joystick mode.<br><br>
<br>
Troubleshooting
Check that the device is recognized by the operating system.
Windows – Navigate to Start > Control Panel > Game Controllers
Ubuntu/Linux – Open Terminal and run ‘lsusb’ to see if the devices are listed
Integrated Dell Remote Access Controller (iDRAC) is a proprietary technology that allows IT administrators to remotely manage and monitor Dell-built servers. This includes software and hardware components.
The Exacq X-Series NVRs include iDRAC micro ports on the front of the system and iDRAC network interfaces on the back. The location of these is noted on the X-Series Quick Start Guide.
<br>
Out of the Box
iDRAC ports are not enabled out of the box. To enable either, or both interfaces, you must access the Lifecycle Control Center on the system.
Enabling iDRAC Ports
During boot up of the system, watch for the boot options to appear on screen.<br><br>
When shown, press the F10 key to boot into the Lifecycle Control Center. <br><br>
The Lifecycle Controller automatically begins a network configuration wizard if it has not been configured before. You may select the Back button to exit the wizard.<br><br>
From the Lifecycle Controller Home screen, navigate to System Setup > Advanced Hardware Configuration. <br><br>
Select iDRAC Settings. Continue to Step 6 to enable iDRAC Direct on the iDRAC micro port. Skip to Step 7 to enable iDRAC networking.<br><br>
To enable the iDRAC micro port, select Media and USB Port Settings. <br>
Beneath USB Management Port, locate the iDRAC Direct: USB Configuration XML setting.
The default setting is ‘Enabled while server has default credential settings only.’ However, for the security of your system, these credentials are changed before shipping from the factory.
Change the above-mentioned setting to ‘Enabled‘.
Select the Back button.<br><br>
To enable the iDRAC network port on the rear of the system, select Network.
NOTE: A VLAN is recommended as a best security practice when iDRAC is in Dedicated or Shared LOM mode, to isolate network access to iDRAC’s management interfaces. Technologies such as VLANs and firewalls help ensure that only authorized users can access network resources.<br><br>
Beneath Network Settings, change the Enabled NIC setting to ‘Enabled‘.
Leave the NIC Selection set to ‘Dedicated‘.
Scroll down to the IPv4 Settings section. The default settings are as follows:
Enable IPv4: Enabled
Enable DHCP: Enabled
Static IP Address: 0.0.0.0
Static Gateway: 0.0.0.0
Static Subnet Mask: 0.0.0.0
Use DHCP to obtain DNS server addresses: Disabled
Static Preferred DNS Server: 0.0.0.0
If you plan to connect this interface to a network with a DHCP server, you may leave the settings as they are.
If you wish to use a static IP address for the iDRAC interface, change the Enable DHCP setting to ‘Disabled‘ and enter the proper Static IP address settings in the fields below.
Select the Back button when done.
Press the Finish button to save your changes and return to the System Setup menu.<br><br>
Press Finish again to return to the Lifecycle Controller main menu.<br><br>
Leave the Lifecycle Control Center and boot to the operating system by selecting the Exit option in the corner of the screen.
<br>
Accessing the iDRAC9 Dashboard
The iDRAC9 Dashboard is accessible using any modern web browser, but there are various methods available to reach it: Local, Network, and USB (iDRAC Direct). <br>
Local Browser Access
Accessing the iDRAC9 Dashboard locally requires a keyboard, mouse, and monitor connected to the system.
Log into the system’s operating system (Windows or Linux).<br><br>
Open a web browser.<br><br>
In the browser address bar, enter: https://169.254.1.1<br><br>
Use the browser’s advanced settings to continue past the warning message. This message appears because the SSL certificate is self-signed.<br><br>
Log into iDRAC using the proper credentials.
<br>
Network Access
iDRAC network interfaces support RJ45 jacks, with 1G BASE-T Ethernet Cat5/6 cables.
The Lifecycle Control Center provides the ability to set the iDRAC network interface to DHCP or static IP address.
If set to a static IP address, a site administrator should be able to provide the configured address.
If configured for DHCP, but a DHCP server is not available, or has no available addresses to offer, this interface should fall back to 192.168.0.120. Otherwise, you may need to determine what address the DHCP server assigned to the system.
Whether using a static or dynamically allocated IP address, you will enter this address into the browser’s address bar.
Example: https://172.10.10.4
<br>
USB Access (iDRAC Direct)
iDRAC Direct allows you to utilize the front-facing iDRAC micro port to connect directly to the system over USB, say from a laptop, which makes ad hoc management in a server room/stack easily accessible.
iDRAC micro ports couple with a USB 2.0 Micro-A or Micro-B connector. You will need a cable with either of these interfaces to connect between the X-Series system and your laptop/workstation. Cable length should not exceed 3ft (0.91m). Cable quality could affect performance. The iDRAC micro port is a Micro-A type port, which will accept either Micro-A or Micro-B connectors, but will not accept USB 3.0/SS Micro-B.
Before beginning, you MUST disable all other network or wireless interfaces on the laptop/workstation you wish to connect from.<br><br>
Make sure the iDRAC micro port is enabled, see Step 6 of Enabling iDRAC Ports above.<br><br>
Turn the flat side of the USB micro connector to the right, so that the beveled side of the USB micro connector faces left, then insert the connector into the iDRAC micro port.<br><br>
Wait a few moments and the laptop/workstation should detect a new virtual network interface.<br> This can be seen using the ipconfig command on Windows, or ifconfig command on Ubuntu/Linux.<br> The IP assigned to this interface should be 169.254.0.4.<br><br>
Open a web browser on the laptop/workstation. In the browser address bar, enter the IP of the iDRAC micro port: https://169.254.0.3<br><br>
Log into the iDRAC Dashboard with the proper credentials.
<br>
Logging into the iDRAC9 Dashboard
When logging into the iDRAC9 Dashboard, use the following credentials
Username: root
Password: admin256
Consider changing your iDRAC Dashboard password using the steps below.
<br>
Changing the iDRAC credentials
Most system users will probably only use the default root user account and factory set password. However, up to 16 local users may be configured in iDRAC with specific access permissions.
If you are already connected to the iDRAC9 Dashboard, you may do this using the following steps:
Select the iDRAC Settings menu.<br><br>
Select Users from the menu drop-down, or from the tabs on the iDRAC Settings page. <br><br>
Select Local Users. <br><br>
Edit an existing account or add a new user account.
If you are not connected to the iDRAC9 Dashboard, you will need physical access to the system.
During boot up of the system, watch for the boot options to appear on screen.<br><br>
When shown, press the F10 key to boot into the Lifecycle Control Center. <br><br>
The Lifecycle Control Center automatically begins a network configuration wizard if it has not been configured before. You may select the Back button to exit the wizard.<br><br>
From the Lifecycle Controller Home screen, navigate to System Setup > Advanced Hardware Configuration. <br><br>
Select iDRAC Settings. <br><br>
Scroll down to find and select User Configuration. <br><br>
Select the text field beside Change Password to enter a new password. <br><br>
When done, select the Back button.<br><br>
Click the Finish button to save your changes.
<br>
iDRAC9 Dashboard Basics
The iDRAC9 Dashboard provides a quick overview of the system. Describing all aspects and controls is outside the scope of this document. The items you should pay the most attention to are your system and drive health.
The Dashboard home page shows a high-level overview of System Health and Drive Health.
Clicking on Details for either of these will bring you to the corresponding pages. You may also reach these pages by selecting System or Storage from the top menu bar.
The System > Overview page displays the status of many hardware components, such as memory, CPU, power supplies, and cooling (system fans). Selecting any of these will provide greater detail on each.
The Storage > Overview page lists the number of physical disks, virtual disks, and graphics of drive status. 2U systems will also display a graphic of the system’s front panel to help identify the drive bays.
Each Virtual Disk is comprised of multiple Physical Disks. These are listed on the corresponding Virtual Disks and Physical Disks pages.
<br>
Virtual Console
iDRAC9 provides a Virtual Console feature which provides a desktop environment as if you were sitting in front of the system. This negates the need to also configure RDP or VNC to configure the system using a GUI.
IMPORTANT: Do not use the Virtual Console for client monitoring of cameras. This method may be used to configure exacqVision software only: add and configure cameras, managing licensing, check system statuses and logs, etc. For regular camera monitoring, install the exacqVision Client on a client workstation suitable for this purpose. See system hardware requirements.
NOTE: Virtual Console performs better when connected via the iDRAC network interface than when connected using iDRAC Direct using the micro USB port.
Enabling the Virtual Console
Virtual Console is disabled by default. Once logged into the iDRAC9 Dashboard, you may enable this feature for use.
From the iDRAC9 Dashboard, locate the Virtual Console panel. The message in this panel indicates the feature is currently disabled for use. <br><br>
Click on the Settings option above the empty panel.<br><br>
From the Virtual Console settings page, change the Enabled setting from ‘Disabled’ to ‘Enabled’, then press the Apply button below. <br><br>
Return to the Dashboard and note that the Virtual Console panel will display an image from the system based on its current state.<br><br>
Select the inset image or press the Start the Virtual Console bar below to open a Virtual Console session.
<br>
Virtual Console Basics
Virtual Console will open a session in a new browser window. Note that the frame rate of the console display is included in the window’s title bar. The console provides some of the following features from the menu buttons. <br><br>
Menu Item
Description
Boot
Chooses what the system will boot to on the next boot up. Options include the Lifecycle Controller, as well as physical or virtual media.
Power
Allows the user to remotely power cycle or shutdown the system.
Chat
Provides a chat window for use when more than one person is using the machine’s Virtual Console.
Keyboard
Displays a virtual keyboard. May be useful when attempting to enter multi-key commands such as CTRL+ALT+DEL.
Screen Capture
Allows the user to save a screen capture PNG image to their local machine.
Refresh
Refreshes the console window.
Fullscreen
Displays the Virtual Console in fullscreen mode. Press ESC to exit fullscreen mode.
Virtual Media
Virtual media allows the managed server to access media devices on the management station or ISO CD/DVD images on a network share as if they were devices on the managed server.
Select Connect Virtual Media to begin, select your chosen media. Use Disconnect to remove that media from the machine’s console connection.
Disconnect Viewer
Closes the console session and window.
Console Controls
Provides settings for viewing, including a virtual clipboard for copying text between the managed server and the management workstation.
DSX is a powerful access control system monitoring application. This integration solely supports PTZ, Live View and Recorded View video and utilizes evAPI.
<br>
Requirements
Licensed exacqVision Server 23.09 or later
WinDSX version 3.7.52 or later
<br>
Installation
Before configuring WinDSX for use with the exacqVision System, complete the following steps:
Obtain a valid Username and Password from the exacqVision Server that will be used with WinDSX.<br><br>
Obtain the IP address of the exacqVision system. Alternatively, you may use the domain hostname if the system is on the same domain as WinDSX.<br><br>
Obtain the User ID and Password for the WinDSX Database/Server.
NOTE: It is strongly advised to use or create an account with limited privileges for this purpose. (e.g. – Live + Search)<br><br>
On the WinDSX server, install the exacqVision plug-in for WinDSX. Follow the on-screen prompts.<br><br>
From the Start menu, select All Programs > WinDSX. Log in using the User ID and Password obtained previously.<br><br>
Click the Database window: a. Double-click Locations. b. Double-click your location. c. Click Camera. d. Click on the New button in the menu to display the New Camera window.
<br>
On the General tab, enter the following information: a. Camera #: This is generic, such as 1, 2, 3, and so on. It is not the same as the camera number on the exacqVision Server. b. Name: This can be any name that you want to assign to the camera. c. Camera Type: Select Exacq Technologies from the drop-down list.
<br>
On the Digital Video Camera tab, enter the following information: a. DVR Server Name: Enter the IP address of the exacqVision Server. b. Assign Cameras: The number of the exacqVision camera (numbering starts at zero). See TIP below. c. DVR Server User Logon: The exacqVision Username obtained previously. d. DVR Server Password: The exacqVision Password obtained previously.
TIP: Clicking Help > Camera List from the exacqVision Driver window will show all camera names, camera IDs, and input numbers on the server. Use the camera ID in step 5b above.
NOTE: If you are using a PTZ camera, select the PTZ box and enter any preset position you want to see in the PTZ Preset Position field.
<br>
Click OK.<br><br>
Click the Workstation window. a. Double-click your location. b. Click Cameras.
<br>
The cameras defined for your location appear in the right window. Right-click any camera and choose Live Video or Recorded Video from the pop-up menu. A window with the desired video is displayed.
<br>
NOTE: If socket errors appear when you try to view live or recorded video, ensure that the dongle is correctly plugged in and the DSXKey service is running on the WinDSX server.
This document will guide you through installation, configuration, and functionality of the Illustra Body Worn Camera system and how to view this video, both live and recorded, from the ExacqVision Server.
<br>
Requirements
Kiosk Requirements
Illustra Body Worn Kiosk 2.0.124 or higher
NOTE: Microsoft .NET 4.8 or higher is needed and will be included if not already found during installation.
Workstation Requirements
For best performance, we recommend installing the Kiosk software on hardware that meets or exceeds that of an Exacq C-Series workstation. For third-party workstations, not built by Exacq, adhere to the following specifications:
Operating System – Windows 10 or later
RAM – minimum 16GB
CPU – Intel Core i7 or greater
If using a C-Series workstation, built by Exacq, please use the Windows OS image release version 22.02.07 or above.
ExacqVision Requirements
ExacqVision Server 23.09 or higher
ExacqVision Client 23.09 or higher
<br>
<br>
Kiosk Software Installation
Unpack the contents of the downloaded .ZIP file containing the install package.<br><br>
Within the extracted files, locate and run the Setup.exe file.<br> <br><br>
Use the text fields provided to create a Kiosk Password. Enter this twice to confirm the entered password before clicking Next.<br> <br><br>
The following step displays the four Kiosk components to be installed. Click the Agree and Install button to accept the End User License Agreement and continue.<br> <br><br>
When installation has finished, click the Close button.<br> <br><br>
If you did not uncheck the box to create a Desktop shortcut, you may now use the created shortcut to open a web browser to access the Kiosk software. If you did not choose to create this shortcut, you will need to navigate to https://localhost:5000 in your web browser.<br> <br><br>
NOTE: Successful Kiosk installation will include four new running Windows Services.
JCI Body Worm Camera Kiosk Driver Service
JCI Dock Controller Service
Illustra Mobile Video Manager
Illustra Mobile Live Relay
<br>
Kiosk Setup
The Bodycam Kiosk is where camera checkouts are managed and recorded video will be uploaded. These recordings can be searched from a connected ExacqVision server.
The Kiosk utilizes a self-signed certificate A self-signed certification cannot be verified by your browser, so your browser will most likely warn you that your connection is not private. Use the Advanced option to continue to the Kiosk login.<br><br>
Login using ‘admin’ as the Email ID for the default administrator account, and the Kiosk Password you created in Step 3. Additional accounts may be created by followin the User Setup steps.<br> <br><br>
Click the gear icon in the upper-right corner of the page to access the Kiosk Settings.<br> <br><br>
Create and enter an API Username and an API Password in the labeled fields. These are used in a later step to connect the ExacqVision VMS to your Kiosk.<br><br>
If your deployment will include live video streaming, you will also need to complete the Relay Server field. Enter the IP address of the Kiosk workstation followed by the port number 4257. Example: 192.168.10.3:4257<br><br>
In the bottom-right corner is the Charging Threshold. A camera that is docked will not become Available to check out again until the battery charge has reached this threshold. By default this is set to 90(%).<br><br>
Lastly, it is recommended to check the One Camera Per User box, near the bottom, to prevent multiple devices being allotted to a single user/camera wearer.<br> <br><br>
Click Save.
<br>
Creating a Camera Profile
Camera profiles allow you to define common configurations to be easily applied to multiple cameras.
Click the menu icon in the top-left corner of the page, then select Profiles.<br> <br> IMPORTANT: At this time only the Default profile supports WiFi. Edit the Default profile, using the pencil icon, if you require WiFi enablement. WiFi is only necessary for live streaming.<br><br>
Click the Add New Profile button. Within the New Camera Profile Configuration window, the Profile Overview tab appears.<br> <br><br>
Provide a unique Profile Name.<br> <br><br>
You may toggle the option to apply this profile to all available cameras. This will only apply to cameras already added to the Kiosk. Cameras added later will need the profile applied manually, or by re-editing the profile configuration. Alternatively, you may opt to select specific cameras to apply the profile to, using the Select Camera menu and Add button.<br><br>
Navigate to the Camera and Recording option. Use the Camera tab to select the aspect ratio, resolution, and frame rate settings for this profile.
Additional controls on the Recording tab permit you to enable/disable Auto IR and audio recording settings, as well as enable/disable Privacy Mode. Privacy Mode allows the camera wearer to prevent live streaming. The camera firmware must be version 8.2.0.111 or higher to enable Privacy Mode.<br> <br><br>
If your intended deployment requires live video streaming, you will configure the Illustra Mobile Video Manager tab. Within the Server Address field, enter the IP address of the Kiosk workstation, which hosts the Illustra Mobile Video Manager service. Example: 192.168.10.3<br> <br><br>
APN Settings are not supported at this time.<br><br>
Toggle the control to Enable WiFi. See also: Network Profiles. Cameras must be connected to the same internal network as the Kiosk workstation and Illustra Mobile Video Manager service via WiFi for live video streaming.<br> <br><br>
Using the Actions and LEDs tab, you may configure the behavior and actions taken by the camera’s buttons and LED indicators.<br> <br><br>
The Sounds and Vibrations tab provides the ability to customize audio indicators to alert the wearer to status changes.<br><br>
Click the Save button when you are finished making settings changes to the profile.
<br>
Network Profiles
Enabling WiFi within a Camera Profile permits the device to use WiFi capabilities. To configure the network authentication, select the Network Profiles tab at the top of the Profiles page.
Enter the network SSID.<br><br>
Enter the authentication Password.<br><br>
Select the Security method.<br><br>
Click the Add Network button. Repeat the previous steps as needed for additional SSIDs.<br> <br><br>
Click the Save button when done.<br><br>
Additional network settings may be located towards the bottom of this page.
<br>
Configuring Users
Click the menu icon in the top-left corner of the page, then select Users.<br> <br><br>
Click the Add New User button.<br> <br><br>
Complete the provided fields for the user’s First Name, Last Name, and Email.<br><br>
Create the user’s password by completing the Password field. It is suggested that the user enters this while being enrolled to prevent an administrator from knowing other user’s passwords.<br> <br><br>
From the User Type selector, choose whether the user account will be a Camera Wearer or Kiosk Admin.
Camera Wearer – may check out cameras, cannot affect changes to Kiosk settings or users.
Kiosk Admin – full Kiosk access.<br><br>
Check the box confirming the identity of the user before clicking the Save button.<br><br>
Repeat Steps 2 through 6 for each user needed.
<br>
License Management
Bodycam Kiosk requires licensing for live video and audio streaming.
Click the menu icon in the top-left corner of the page, then select Live Stream License.<br> <br> <br><br>
This page allows Kiosk Admins to quickly view the license status. Click the View Available Licenses button for an overview of the number of licenses in use or available.<br> <br><br>
Clicking Request a New License provides a new dialogue window. Complete the Email and Sales Reference Number fields, then select whether to:
Email the license request (requires an email client on your Kiosk workstation).
Download the license request file to send from another workstation, or at a later time.<br><br>
Once a valid license file has been provided, return to this page to utilize the Upload a New License button so it may be applied to the system.
<br>
Connecting Cameras
Illustra Body Worn Cameras may be connected to the Kiosk workstation in one of two ways:
USB Cable – each camera is packaged with a USB-C to USB-A cable. The USB-A connector will connect to the Kiosk workstation while the USB-C end will connect to the camera.
It is strongly recommended to keep these cables even if using the Docking Station as you may find that many USB-C cable connectors are not of sufficient depth to properly connect when plugged into the camera.<br><br>
Docking Station – an optional 8-port docking station is available, capable of charging and transferring data for up to 8 cameras over USB-A 3.0 cable. Multiple docking stations may be utilized on a single Kiosk.
IMPORTANT: It is strongly recommended to connect cameras and Docking Stations to the blue USB 3.0 ports on the Kiosk workstation. Failing to do so will result in much slower data transfer times.
<br>
Updating Firmware
The process of updating the firmware running on the cameras can be performed through the Kiosk dashboard by a Kiosk Administrator.
Select the gear icon in the upper-right corner of the dashboard and choose Update Firmware, or select the gear icon on one of the individual camera tiles and select Update Firmware.<br><br>
Use the Browse Files button to locate your firmware .APK file.<br><br>
Select the Update button.<br><br>
During the update process you will notice cameras in the Kiosk move to Not Ready and the cameras will reboot. Do not disrupt the update process or disconnect the cameras during this period. When completed, the cameras will return to the Available state.
The camera firmware files may be found in the Kiosk install package. Open the contents of the extracted .ZIP file and locate the .APK file within the ‘bin’ folder.
NOTE: A firmware update will affect all connected cameras.
<br>
Kiosk Dashboard
Kiosk Admins will see a Tiled View by default. Each camera is displayed as a tile, showing the camera name and status information.
The camera tiles are separated into three sections:
Available – cameras to ready to be checked out for use.
Checked Out – cameras already checked out.
Not Ready – cameras still transferring data or charging.
Clicking on the gear icon allows a user to manually change the profile assigned to the camera. If changing the profile assigned to a camera, this must be done prior to check-out. It is not recommended to change the camera password in the camera settings as this is tied to Mobile Video Manager and will prevent live streaming without manual intervention to match this password within the MVM software.
An administrator also has the option of using the Forget Camera button in the camera settings to permanently remove a camera from the Kiosk, as in the case of a lost or damaged camera that will not be reconnected.
A Kiosk Admin may also choose to view cameras in a List View using the View type buttons in the upper right-hand corner of the page.
Adding a new camera to the Kiosk is as simple as plugging in the USB cable or seating the camera in the Docking Station.
When connecting a camera to charge or transfer data, it may take a moment to be recognized and its status to be updated in the Kiosk.
NOTE: A camera must reach the configured battery charge threshold before it becomes Available.
<br>
Connecting to ExacqVision
ExacqVision integration copies the downloaded video/audio from the Kiosk workstation to the ExacqVision Server making the video easy to store and search alone, or alongside your connected IP security cameras.
Within the ExacqVision Client software, click the gear icon to enter Configuration settings.<br><br>
Within the navigation tree on the left-hand side, expand the node labeled with the server name, to display the nodes nested beneath it.<br><br>
Expand the Configure System node.<br><br>
Select the Body Worn Cameras node.<br><br>
On the Body Worn Cameras page, check the Enable checkbox.<br><br>
Using the Type selector, choose Illustra Body Worn.<br><br>
Enter the IP Address of the Kiosk workstation. Do not alter the port number.<br><br>
Enter the API Username and API Password you created in the Kiosk Setup steps into the Username and Password fields.<br><br>
If you plan to use live streaming in your deployment, check the Enable Live Streaming checkbox.<br><br>
Click Apply.<br>
Body Worn Camera users will appear on the camera tree to the left alongside any infrastructure IP or analog cameras.
<br>
Camera Check Out
IMPORTANT: When checking out a camera, wait until the light on the camera begins flashing before disconnecting from the USB cable or Docking Station. This light not only indicates the assigned camera, but tells the user it is ready to be disconnected. Disconnecting prior to this will leave the camera in a disconnected, unassigned state.
Kiosk Admin
When logged in as an administrator:
Select one of the Available cameras to use.<br><br>
Press the Check-Out button.<br><br>
In the field titled User ID number, enter the assignee’s email address. This was configured when creating the User account. You may also begin typing the user’s name and select it from a displayed list of matches.<br><br>
Check the box titled, I certify that I have confirmed the identity of this user.<br><br>
Click the Check-Out button.<br><br>
Wait for the camera light to flash before disconnecting.<br><br>
Camera Wearer
If the deployment is not attended by a Kiosk Admin, the Kiosk provides a self check-out experience. A registered Kiosk user will:
Sign into the Kiosk using the registered email and password.<br><br>
Click the Assign A Camera button.<br><br>
The Kiosk will inform the user which camera to remove by name.<br><br>
Wait until the light on the camera flashes before disconnecting.<br><br>
Close the window by clicking the X or the Cancel button to automatically logout, ready for the next user.
<br>
Camera Check In
Reconnect the camera to the USB cable or Docking Station. The Kiosk will automatically begin transferring recorded data. The camera will become Available again once charged and all data has been transferred.
NOTE: A camera must have at least 90% battery charge before it becomes Available.
<br>
ExacqVision Live Streaming
Cameras with WiFi enabled will automatically connect when in range of access points correlating with the SSID and credentials entered in the Network Profile. Cameras that are connected and ready to live stream will display a green arrow in the camera tree of the ExacqVision Client’s Live viewing page.
To view the live stream, add the camera to a panel just as you would a fixed IP or analog camera, by dragging it onto a camera panel or double-clicking it.
When viewing live streaming video or listening to live streaming audio the data is automatically recorded on the NVR. You may stop the live stream by positioning your cursor over the center of the panel and pressing the Stop icon that appears. This will also cease recording on the NVR, but will not stop local recording on the camera if the wearer has enabled recording.
Streams which have been disconnected may be restarted by pressing the Play icon when the ‘Live Stream Available’ message appears.
If attempting to display a live stream when the camera wearer has enabled Privacy Mode, the following image will appear until Privacy mode has been disabled.
<br>
ExacqVision Search
Performing forensic search and playback of video and audio is similar to that of fixed cameras. However, you will note that each camera wearer’s name appears twice in the Camera List pane.
Video and Audio recorded locally on the device while being worn is downloaded from the device to the Kiosk when docked. This data is then transferred to the NVR. Locally recorded video and audio data is searched using option labeled ‘– Recorded‘.
Video and Audio that have been live streamed to ExacqVision Client users is recorded directly to the NVR. This is a separate stream and is searched using the option without the ‘– Recorded‘ label.
Live stream recordings, camera-side recordings, and fixed infrastructure camera recordings may all be displayed side-by-side within the Search screen of the ExacqVision Client, and/or exported.
<br>
GPS Data
Cameras with location data enabled, with a clear view of the sky for GPS positioning, record GPS data as an analytic. Select the geolocation box beneath the camera wearer name from the camera tree, as pictured.
Enter your search date/time range, then press the Search button as you would any permanently positioned IP camera. GPS data is recorded in intervals when the device is moving. This is indicated by the red lines on the geolocation row in the timeline.
Clicking the Show/Hide Keywords and Serial Data icon below the Quick Export button will toggle the Keywords and Serial Data panel to view the geolocation data similar to analytics from infrastructure IP cameras.
TrueVUE Cloud is a cloud-based retail analytic software that integrates with ExacqVision Video Recorders. This integration allows retailers to connect video to loss events.
This integration is based on ExacqVision’s webAPI.
<br>
Requirements
ExacqVision Web Service version 23.06.1 or higher
ExacqVision Server version 23.06.1 or higher
<br>
Configuration
The ExacqVision Web Service must be configured for HTTPS, with a valid SSL certificate.
While logged into the ExacqVision Web Service Administration on the Service Status page, find the Inbound Internet Connection section. Check that the HTTPS Port is configured and has a green checkmark.<br><br>
Make note of the HTTPS Port number as well as the External IP and/or External URL shown under the Internet Address section.<br><br>
Provide the following information to Johnson Control’s Professional Services team to setup your TrueVUE Cloud account to complete the integration.
External IP address or External URL
Web Service HTTPS Port number
Username for a Power User account configured within ExacqVision
Password for the Power User account
<br>
Support
Sensormatic For Sales and General Inquiries: +1-800-642-7505 (US) Monday – Friday: 9am – 5pm ET Existing Customers (US/CA) Service/Install/Technical Inquiries: crc@jci.com
Hanwha cameras may be configured with the Road AI license plate recognition application. The data from license plate captures can be viewed in the ExacqVision Client as text, sent as serial data over IP. The Road AI application is pre-installed and licensed from the factory on select camera models. This document will step through setting up the application integration with ExacqVision.
<br>
Tested Versions
ExacqVision 22.12 and higher
Camera models PNO-A9081RLP – firmware 1.41.02 PNV-A9081RLP – firmware 2.21.00
Road AI application Version 7.2.7.6
<br>
Installation
Mount the camera according to the manufacturer’s installation manual. LPR applications typically provide specific guidelines on positioning camera distance and angle to the target. <br>
If needed, download the Road AI User Manual to help with configuration from the manufacturer’s website.<br>
Open a web browser and navigate to the camera’s IP address.<br>
Log in with the username and password<br>
Navigate to the Open Platform settings page.<br>
Once the application is running, you may configure how it sends data to ExacqVision.
<br>
Road AI Application Configuration
Open the camera’s web interface. Navigate to Setup > Open Platform > Go App
<br>
Refer to the Road AI user manual for greater detail on the best way to install and position your camera. Once you have completed this, you may configure the camera for license plate capture.
Select the Settings tab from the top of the application. <br>
By default there is a single zone bounding box, which you may manipulate. A second zone may be configured using the + button under Zones Management. Drag the corners of the bounding box to your desired size, shape, and location in the field of view.<br>
Set the Region field to select your country of interest.<br>
Select the Plate Capture Mode setting.
Low speed mode with 4K resolution
High Performance mode with Full HD resolution<br>
Enabling the Wizard button displays a statistic of the latest 1000 plate sizes detected to help you increase detection rates. See the Road AI user manual for more details.<br>
The Plate Size Measurement feature also aids in increasing the detection rate. Recommended plate width is 130-350 pixels in the camera image.<br>
Scroll down to Recognition Setup to enable/disable Model Recognition and Color Recognition.<br>
Scroll to the Integration Options section.<br>
Select the check box for NVR Integration.<br>
Beneath this check box, enter the IP address of the ExacqVision Server on your network in the field on the left.<br>
Choose a port number that will be used to communicate with ExacqVision. This must be a port number that is not used by any another devices on your network. This port number will also be configured in the ExacqVision Client. Enter the port number in the field to the right of the Server IP address. In the example above, the ExacqVision Server is located at 192.168.0.6, and the port number selected is 9393.
IMPORTANT: When using multiple Hanwha cameras running Road AI on the same network, each device MUST be assigned a unique port number.<br><br>
Click the Save Settings button at the bottom when these steps have been completed.<br>
Before continuing with ExacqVision configuration, ensure that license plates are being captured by navigating back to the Events tab. If you are experiencing trouble successfully detecting license plates refer back to the guides on camera positioning and placement.<br>
NOTE: In our testing, it took some time for the application to complete saving changes when pressing the Save Settings button. You may also need to be patient for the Road AI application to display the camera image.<br>
NOTE: If a red banner appears when navigating back to the Events tab, this may delay events being sent to ExacqVision.
<br>
ExacqVision Serial Port Configuration
Within the ExacqVision Desktop Client, select the Configuration icon from the top-left toolbar.<br>
Select the Serial Ports node from the left-hand navigation tree, nested beneath your server name.<br>
Under the IP section, click the New button<br>
Enter a Name for the Serial Port.<br>
Under the Use column, select POS from the menu.<br>
From the Type column, select TCP Listener.<br>
In the Address field, enter the IP address of the Hanwha LPR camera.<br>
In the Port field, enter the port number you selected and entered into the Road AI application earlier. Recall in our earlier example we entered 9393.<br>
Under the Profile column you will select New, unless you had previously configured a Serial Profile, in which case you would select that profile name.<br>
Click the Apply button to save your changes. If you selected New in Step 8, this will automatically take you to Serial Profiles to continue setup.
<br>
ExacqVision Serial Profile Configuration
If you selected New during setup of the Serial Port, you will begin by naming your Serial Profile. If you did not do this, then you will begin by selecting the New button, then enter a Name for the profile. Example: Hanwha LPR
Choose one of the following options for the Marker Type. Your choice will depend on how you’d like the data to appear in live and search.<br>
For records in this format: LPR LPR = ZTD904 Dodge RAM SUV
Select XML as the Marker Type
Enter <LPR in the SOT Marker field This is not a typo, do not enter a closing >
Uncheck the Case Sensitive box
Click the Apply button to save your changes.<br>
For records in this format: ZTD904 Dodge RAM SUV
Select Standard as the Marker Type
Enter <LPR> in the SOT Marker field
Enter </LPR> in the EOT Marker field
Uncheck the Case Sensitive box
Navigate to the String Replacements tab.
Click the New button.<br>
Enter <LPR> in the String field, then enter a single space character in the Replace field. This field cannot be left empty.<br>
Click the New button again, to add a new row.
Enter </LPR> in the String field, then enter a single space character in the Replace field.
Click the Apply button to save your changes.<br>
Use the Live Display tab to preview how your data will appear in the Live View overlay. Enable Line Removal if you wish to periodically clear the text. <br>
Optional – If you wish to trigger events from ExacqVision’s Event Linking or Event Monitoring features based on specific words, you will need to configure this on the Event Keywords tab within your Serial Profile. Example keyword: LPR
<br>
Event Linking
ExacqVision can use the analytic events from Road AI to trigger various actions, such as recording video from a specific camera.
Select the Event Linking node from the navigation tree on the left side of the ExacqVision Client window.<br>
Click the New button.<br>
Within the Event Type list, select Serial Profile.<br>
In the Event Source list, select the serial profile name to trigger this event on all keywords you configured. Select the profile name with ‘Keyword’ to trigger this event only when that keyword is encountered.<br>
From the Action Type list, select the action you intend to take when triggered.<br>
Select the Action Target.<br>
Some Action Types, such as Record Video, provide the ability to set a Pre and Post Trigger settings.
Click Apply to save your changes.
<br>
Related Materials
Find more details on topics mentioned in this article at the following links:
After making changes to the network settings within the Road AI application, it may be necessary to Stop, then Start, the Road AI application from the camera’s Open Platform page.<br><br>
As noted above, during configuration of the Road AI port numbers; When using multiple Hanwha cameras running Road AI on the same network, each device MUST be assigned a unique port number.<br><br>
The camera is detecting license plates in the Road AI application and the port numbers are correctly set in both the camera application as well as in ExacqVision’s Serial Ports page but no data is being received. You may need to add an incoming port exception to the firewall of the system running your ExacqVision Server application.
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br>
<br><br>
<br><br>
