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”
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.
When adding an IP device to your ExacqVision Server, each device will be associated with a Device Type that selects the underlying plugin used for communication.
You are unable to find the required Device Type when attempting to add the device. <br><br>
Cause
When using an existing ExacqVision install, possible reasons are:
The plugin was not selected to be included in the initial installation.<br><br>
The first version of the plugin was released after your initial server installation version.<br><br>
In the first example, running the installer manually, a dialogue window appears providing users with the option to select or deselect each individual plugin to be included with the server installation. Most users are fine using the default selections. There are some plugins not selected by default because they may be older or used only in rare instances.
When performing automated updates using the Check for Updates button the software updates only the plugins already installed. It does not install additional plugins.
In the second example, you may be looking for a plugin used for a newer integration. This may also eventually lead to the cause mentioned above. <br><br>
Resolution
Download the ExacqVision Server installer directly from the Software Downloads page.<br><br>
Run the downloaded installer file manually.<br><br>
Watch for the dialogue in which the listed plugins may be selected for install.<br><br>
Scroll to the plugin you need and be sure it is check marked for install.<br><br>
Complete the remainder of the installation steps. After the service restarts, the desired plugin should be listed in the Device Type options.
This article applies to the Axis A8207-VE and A8207-VE MkII Network Video Door Stations using firmware 11.5.64.
exacqVision does not currently support SIP calling functions. However, these door stations can be integrated for interactive operation with exacqVision as detailed here.
In the example that follows we will step through an example scenario wherein pressing the door station call button brings the door station camera to the attention of the exacqVision operator to trigger a door lock.
The following topics are discussed:
Wiring an electric door strike to the door station
Adding the device to exacqVision
Enabling Two-Way Audio
Adding Associations
Creating custom Views
Creating an Event Monitoring profile
You will combine several features and functions within the exacqVision Client. It is recommended that users acquaint themselves with the exacqVision Client prior to use. We provide User Training Videos on these topics.<br><br>
Wire a Door Strike
The simplest configuration is that of a single electric door strike, or maglock, wired directly to the door controller.
The Axis A8207-VE and A8207-VE MkII can be wired in a number of different ways, using PoE, external power sources, A9801 Relay, A9161 Network I/O Relay, or an Axis access control system. For more information on the many wiring and hardware configurations please refer to the manufacturer’s website or documentation. <br><br>
Add the Device
You will want to use a web browser to log into the door station and perform the initial setup, which at this stage usually means setting a non-default username/password, and possibly setting a static IP address.<br><br>
The call button should be enabled by default. <br><br>
If you do not already know the IP address of the door station, you will need to discover it on the network.<br>
If using the Find IP Cameras tab on the Add IP Cameras page, note that you may find the device listed twice. Ignore results with a 169.254.x.x address. You will want to use the IP address in the same range as your exacqVision VMS, however this result may be discovered with ‘Onvif’ displayed in the ‘Type’ column. Access the discovered IP address in your web browser to set the username and password. <br><br>
Add the device manually by clicking the New button under the IP Camera List in the top half of the page. Select AXIS VAPIX from the Device Type selector. Enter the IP address in the same range as your exacqVision VMS, then enter the username and password credentials before clicking Apply to add the device. The device should display a ‘Connected’ status in the IP Camera List before continuing. <br><br>
Enable Two-Way Audio
Expand the Add IP Cameras node from the navigation tree.<br><br>
Select the Audio Inputs/Outputs node nested beneath the Add IP Cameras node.<br><br>
The resulting list displayed will show each door station device listed twice. Note the column, titled Audio. One of these rows shows ‘Audio,’ while the other displays ‘Audio Output.’ For easier identification we can apply our own labels here. We change ‘Audio Output’ to ‘Talk’ and change ‘Audio’ to ‘Listen.’ <br><br>
Find the Record Enable column. Place a check in the box for both of these rows for the door station. This enables two-way audio functions within exacqVision.<br><br>
Press the Apply button to save your changes. Use the Talk and Listen buttons to verify audio is functioning and adjust the audio gain as desired in the door station’s web browser interface.<br><br>
IMPORTANT: Client workstations intended for use with two-way audio devices MUST have a microphone enabled. Two-way audio menus and controls are disabled or hidden until a microphone is recognized by the operating system. Each client workstation used for two-way audio must have its own microphone.<br><br>
Add Associations
You have the option of using soft triggers and audio controls from the top toolbar in live view, but these will open dialogues showing all system options. Controls that are used frequently and directly related to the specific camera being displayed in a panel may be easier for operators to use when added as Association buttons within the camera panel.
Select the Associations node from the navigation tree.<br><br>
The panel along the left lists existing cameras. Find and click to select the door station.<br><br>
From the Available Controls panel, we select the ‘Listen’ option we relabeled earlier and click Add. There will be two controls labeled ‘Talk’ that we relabeled earlier. Select and add the one showing the microphone icon.<br><br>
So that your exacqVision operators can unlock the door remotely, find and add the control labeled ‘Door.’ Note: This control may be relabeled from within the door station’s web browser interface, but is labeled ‘Door’ by default for us.<br><br>
You should now have three Associated Controls listed. You may wish to edit the Button Style listed. ‘Sustained’ requires a click on, and another click to turn off. ‘Momentary’ functions only while a user is pressing down the button which will also prevent a user from accidentally forgetting to lock the door or leaving a microphone on. You may refer to the User Manual or Associations training video for more information on customizing your Associations.<br><br>
Click Apply to save your changes when done.
<br><br>
Create Custom Views
In our example we will create a View to display when triggered, rather than changing a single video panel. Learn more about these two options in the Event Monitoring training video. To make this work, we will create two custom Views to use later when creating an Event Monitoring profile. Refer to the Views training video if you need more details on performing these steps.
Select the Views node from the navigation tree.<br><br>
Click the New View button, then enter a descriptive name. In this example, we name our view ‘East Entry.'<br><br>
Select a layout for the view from the layout toolbar above. This view may have a single panel layout showing only the camera view from the door station, or you may use a multi-panel layout displaying the door station and other cameras showing the entry from different angles.<br><br>
Use the Available Items panel to find your door station camera and drag it to the empty panel in the layout. If using a multi-panel layout, fill the other panels as you like. <br><br>
Because the Associations are already displayed, an exacqVision operator may easily enable/disable each when viewing in Live mode. However, if you’d like the Microphone or Speaker to be on automatically upon the view changing, you may also drag one of these onto the layout as well. Only one may be active.<br><br>
Click Apply to save you changes when done.<br><br>
Since we are changing the entire view displayed in Live mode, we will also want to create a view that is displayed when the door station is not in use. Repeat the steps above to create another view titled ‘Default View.’
<br><br>
Create an Event Monitoring Profile
Next you will create the Event Monitoring profile that changes the view displayed while in Live mode.
Select the Event Monitoring node from the navigation tree.<br><br>
Click the New button under the Profiles panel to begin creating a new profile.<br><br>
Enter a descriptive Name under the Profile Configuration panel. Our example will name this ‘East Entry’ for the door where it is being placed.<br><br>
The option you select for the Show Event List menu will depend on your intended use.
Never is the less obtrusive option as it hides the Event List from popping up in our view. The trade off for this is you will probably want to set Timeout later so the View changes back to the default display after a given amount of time. Without this, the displayed View will remain on the door station camera.
On Event will pop open the Event List window which some users do not like. However, the benefit of this is the exacqVision user can decide when to return to the default View and the View will not change in the middle of being used simply because a timer ended. When the event is cleared the Event List window will disappear.
Always will always be displayed whether or not the door station is being utilized.<br><br>
Checking the Show Newest Event box is optional. This feature is most useful when many possible events are included in an Event Monitoring profile. An example may be a site with multiple door stations, in which case checking this box will change the view to display the station with the most recently pressed Call Button.<br><br>
As mentioned previously, this example will use ‘View’ from the Type field. Refer to the Event Monitoring training video for more on the ‘Video Panel’ option, which does not require creating custom Views.<br><br>
Under Client Actions in the middle of the window is where you will create the actions that occur when triggered by various events. Our first row, currently labeled ‘Unknown’ should already be highlighted because we are creating a new profile.<br><br>
From the Event Type panel list below, select ‘Default’.<br><br>
From the Action Type panel list, select Switch View. Note that you could also opt to make your default display a Tour, which is covered in the Tours training video.<br><br>
From the Action Target panel list, select the default View you created earlier.<br><br>
Click the New button under the Client Actions panel in the middle of the window. This adds a new row to configure.<br><br>
With the newly created row highlighted, select Input Trigger from the Event Type list.<br><br>
The door station has already named the input for you. Locate the door station in the list. It has several inputs, select the one labeled ‘Call button’. Do not enable the ‘Lasts at Least’ checkbox.<br><br>
From the Action Type list, select Switch View.<br><br>
From the Action Target list, select the door station View you created earlier. In our example we named this ‘East Entry’.<br><br>
Your next choice will depend on the option you selected from the Show Event List, in step 4, above.
If you chose Never and want the Live view to return to your default view after a set number of seconds, uncheck the Confirm box and set your Timeout as desired.
If you chose On Event or Always and want to allow your exacqVision users to acknowledge the event to return to the default view, leave the Confirm box checked.<br><br>
Click the Apply button to save your changes when done.
<br><br>
Handling Calls From exacqVision
Using the exacqVision Client software, browse to Live mode.<br><br>
By default, the panel along the left side of the window displays a list of Live Cameras. Using the options at the bottom select Views to update this panel to Live Views.<br><br>
The Live navigation panel lists System Views, User Role Views, User Views, and System Tours, which includes any Views created earlier in the process of configuring our profile. Towards the bottom is a list of Event Monitors. <br><br>
Find the name of the Event Monitoring profile you created. Again, our example was named ‘East Entry’. Drag this profile to the cameras panel to the right.<br><br>
You should now be viewing your default View. When the Call Button on the door station is pressed the View will change to display the door station camera view you created earlier.<br><br>
The Association icons we added earlier can be seen at the bottom corner. The door station will continue to ring until an exacqVision user presses the Talk button or the configured ring timeout is reached. <br><br>
Press the Talk button to transmit audio from your client workstation microphone to speak to door station users. Press the Listen button to hear door station users speaking.
Note: Audio from Talk and Listen actions may be buffered, presenting a delay. Practice with the system to gain a feel for this on your network.<br><br>
If you have correctly wired a door strike, maglock, or other electronic locking mechanism to the door station, pressing the icon for the output will unlock the door.
Note: Door controls may be customized within the door station’s web browser interface.<br><br>
Door Station Visitor Operation
A visitor using the door station may simply press the Call Button to activate the Event Monitoring profile, as created above.<br><br>
The use case detailed in this article does not prevent the door station from being used for SIP calls.
Once a SIP server has been configured within the door station’s web browser interface, a SIP call is initiated by dialing a designated SIP extension number prior to pressing the Call Button.
Note: When used together with SIP, any press of the Call Button will trigger the Event Monitoring profile regardless of whether it was used when dialing an extension number or not.<br><br>