Clean Uninstall Illustra Body Worn Camera and Mobile Video Manager
Introduction
This knowledge base article summarises how to cleanly remove the Illustra Body Worn Camera (BWC), JCI Dock Controller and the Illustra Mobile Video Manager software.
Uninstall Body Worn Camera and JCI Dock Controller
Uninstall JCI Dock controller software: Control Panel > Programs and Features > JCI Dock Controller > Uninstall
Delete directory for JCI Dock Controller software: C:\windows\System32\config\systemprofile\AppData\Local\JCI Dock Controller
Uninstall Body Worn Camera software: Control Panel > Programs and Features> Body Worn Camera > Uninstall
Delete directory for BWC software:
C:\ProgramData\BWC
Uninstall Illustra Mobile Video Manager
Uninstall the Illustra Mobile Video Manager application in Windows: Control Panel > Programs and Features> Illustra Mobile Video Manager > Uninstall
Delete the Illustra Mobile Video Manager directory: C:\Program Files (x86)\Illustra Mobile Video Manager
Delete the Registry key directory located at this path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Illustra Mobile Video Manager
Tips
The BWC setup.exe (Kiosk/JCI Dock Controller) must be installed prior to the Illustra Mobile Video Manager:
2. Usernames for the associated applications are noted below: BWC Kiosk = “admin” JCI Dock controller = “admin” Illustra Mobile Video Manager = “Administrator”
Axis P3247-LVE “Axis Object Analytics” not passing through the Exacq Mobile 3 app Analytic Rules. If seen please see AES-609. Escalate the case to be added to ticket.
Product
exacqVision Server: 23.06.1.0
exacqVision Web Service: 23.06.2.0
Steps to Reproduce
Set up the camera to allow analytics. Note we do not support line cross for axis cameras.
Once camera is set up navigate to the mobile app and connect to the NVR.
Once Connected navigate to the main menu.
Select Push Notifications
Select Analytics
You should see any analytic that cameras are sending.
Expected Results
We should be able to see the Analytics from the Axis cameras.
Actual Results
Analytics do not show up in the mobile app but do on the NVR’s Server when creating event linking and on the camera settings page.
If this setting is enabled then it is possible with certain version of Server software, an API issue could occur. Specifically with the OVID plugin when integrating with S2.
Product
TESTED Version: Client Version: “22.12.2.0” Server Version: “22.12.5.0” evOVID plugin version 1.1.12.123380
Steps to Reproduce
If the Password Strengthening and Augmented Authentication is enabled then OVID plugin will not allow the live views once it is enabled.
Enabled Strengthening.
In S2 if you go to live view, the video streaming box is “black” (i.e. no video).
Removed the Strengthening by reinstalling the software and the OVID worked successfully.
Expected Results
We should be able to utilize the Password Strengthening and maintain live views via integrations.
Actual Results
While enabled the OVID would not show live video in S2 integration.
Solution
We have verified using evOVID by upgrading evAPI is all that is needed to get the evAPI component of the integration working.
In theory, any version past 1.35.2.53326 should resolve the issue.
AES-311 WORKAROUND: To update the evAPI we can use a drag-in upgrade. Grab the DLLs from the zips (below) and copy them to the ‘bin’ subfolder of the OVID install location.
Bug Fix – Fixed issue causing server crash due to missing microSD card in Illustra multisensor cameras. If camera has no microSD for one sensor, but does for another, network loss recording action caused a crash. (AESW-7549)
Bug Fix – Prevent offload from Illustra BWC from hanging
Bug Fix – If camera does not support metadata over HTTPS, allow metadata over HTTP when camera is added with “HTTPS if Available” setting with illustra3pi and illustramultipi
Bug Fix – Added camera detection for all Illustra 2023 released models, this includes Flex 4 PTZ, Pro 4 Bullet, Pro 4 Compact Dome, Pro 4 Corner, and Flex 4 Dome models (AESW-5896)
Bug Fix – Support for motion windows when adding Onvif cameras to server, some Onvif cameras would not detect motion after adding even with enabled motion windows (AESW-7220)
Bug Fix – Fix for issue when Onvif cameras send ‘out of bounds’ motion window coordinates (AESW-7373)
Bug Fix – Decouple iris and focus debuffering from PTZs using Onvif
Feature – Improvements to core, logpi, softtriggerpi, tdvrpi, and videotestpi for logging and performance (AESW-5801)
Feature – Updated database structure and management for eventpi to improve metadata search performance, queries, and data purging (AESW-6286)
Feature – Added new retention options for AI / Object metadata Provides ability to help manage eventpi database size (AESW-6082)
Feature – Onvif motion and transport ‘plug-n-play’ support removes the need for manually updated Onvif JSON files and now Onvif plugin can dynamically read the motion topics from Onvif cameras (AESW-6069, AESW-3746)
Feature – New ‘Power User (No Video)’ security user role Supports countries where strict laws exist around video access (AESW-6387)
Enhancement – Added ability to set oldest desired content age for Cloud Drive content (AESW-3064)
Enhancement – Axispi now supports upper and lower clothing color metadata (AESW-7031)
Enhancement – Added paging support for brivopi
Enhancement – Added support for additional WDR modes on illustra3pi and illustramultipi (AESW-4618)
Enhancement – Added audit and logging of Illustra BWC privacy mode (AESW-7546)
Enhancement – Support added for Illustra BWC GPS data (AESW-5429, AESW-5528)
Enhancement – Added support for PCM16 audio for live streaming from Illustra BWC (AESW-423)
Enhancement – Added encrypted password storage to notify.xml for notifications (AESW-2085)
Build – Plugins for Basler, IoImage, IPX, Sanyo, Stardot, and UDP now unchecked by default during installation
Build – Upgraded aws-sdk-cpp to version 1.11.1
Build – Upgraded cURL to version 7.87.0
Build – Upgraded OpenSSL to version 3.1
Build – Upgraded libwebsockets to version 4.3.2
Build – Upgraded zlib to version 1.2.13
ExacqVision Client
Bug Fix – Enable appropriate buttons on the Add IP Cameras page after deleting cameras (AESW-6809)
Bug Fix – Fixed issue where Live view navigation tree reloaded on camera double-click (AESW-5618)
Bug Fix – Properly display the disabled Analytics buttons on Linux. Buttons were appearing as enabled when they should be disabled (AESW-6662)
Enhancement – Client support for the Oldest Content setting for Cloud Drive content (AESW-6779, AESW-7710)
Enhancement – Added new UX field for Frame-by-frame metadata retention period (AESW-6307)
Enhancement – Optimization for search speeds (AESW-5121)
Enhancement – Live analytic support for Illustra BWC (AESW-2846)
Enhancement – Moved generic dewarper to top of fisheye dewarper selection list (AESW-7389) Client side support for new WDR settings (AESW-5690)
Enhancement – Client side support for the new ‘Power User (No Video)’ user role. ‘Not Allowed’ text displayed for camera panels, Cameras hidden entirely from search (AESW-6388)
ExacqVision Web Service
Bug Fix – Removed no longer supported SCGI proxy folder. Action taken to prevent cross site scripting errors when performing vulnerability scans (AESW-6677)
Enhancement – Added evAPI support for detecting restricted view configuration (AESW-4288)
Enhancement – Change endpoint for S2 integration to ‘video.web’ (AESW-4903)
Enhancement – Scale web client search playback buffer with the playback speed selected (AESW-4757)
ExacqVision Enterprise Manager
Bug Fix – Update VMS audit log entries to use valid JSON (AESW-7458)
Bug Fix – Use the correct logger sync
Bug Fix – Add missing Seq settings validation
Enhancement – Add support for ‘Power User (No Video)’ user role (AESW-7169)
Enhancement – Add VMS audit trails to the EM audit logs (AESW-5498)
Enhancement – Added API endpoint for retrieving individual audit log entries (AESW-1340)
Enhancement – Add slug to audit logs where applicable (AESW-7176)
Enhancement – Add a user configurable timer for VMS audit log retrieval (AESW-6087)
Enhancement – Integration of EM/ISP logs into Seq. Provides the ability to extract logs into external Seq logging systems
Enhancement – Add migration files to upgrade AES encryption over the older ARC4 to enhance security (AESW-7512)
Enhancement – Update Apache to version 2.4.57 (AESW-6957)
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.
The Scenario Series of videos addresses setup configurations for specific use cases.
In this video our scenario is that of a user that wants to use Event Monitoring to bring attention to an ExacqVision operator when someone parks in specific parking spaces. This could be used to prevent people from parking in forbidden areas, to alert someone to customers in curb-side pickup spots, and more.
We walk through setting up AI Object Classfication within an Illustra IQ camera and configuring Event Monitoring in ExacqVision to change our displayed camera views when triggered.