Ubuntu Linux desktop exacqVision Client crashes experienced when using VM Desktop Joystick Controller. Rapidly pressing multiple keypad buttons (and/or possibly disconnecting the Joystick USB cable) may result in intermittent buffer overruns and random crashes of the client.
exacqVision Client direct access of Cloud-Drive storage does not list cameras by server configured camera names or display video time & date stamp.
Customers that attempt to review Cloud-Drive video from an off-site independent exacqVision Client pointed at the Cloud Drive URL https://exacq-gateway.cloudvue.com/v1/exacq with the proper credentials will be faced with the following limitations.
Limitations:
1. The exacqVision Client Search Cameras page shows a Cloud folder where the cameras are listed by a unique 6-digit name. The original server configured names are not associated in any way with the new camera names making it more difficult to locate a particular camera by the new name alone. This information is not stored in the cloud so the client has no way of accessing it.
Cameras
Cloud (Folder)
0123456789AB
[ ] 361568
[X] 361312
[ ] 361569
[ ] 361570
[ ] 362080
[ ] 361571
2. The exacqVision Client Search Cameras page has no On-Screen Display of the time & date stamp unlike when the Client connects through the server.
No Workaround:
None available.
Unfortunately there is no immediate solution, neither of the two items are presently supported. The original camera names are not stored in the Cloud-Drive so the remote client has no way of accessing them. The video time & date stamp is not provided by the Cloud-Drive either. These items have been raised as feature enhancement requests to Cloud-Drive Product Line Management for future discussion and possible inclusion.
If all of the boxes for the camera are greyed out for a camera on the Schedule page under Archiving…
Check to verify in the Exacq Client under Storage you DO NOT have a Expiration Configuration rule set; if you do remove it. Then go back to the Archiving Schedule page and select your cameras and whether you want Motion, All or Alarm.
If you run in to an Exacq system where it says “Motion Not Supported” there are several camera manufacturers where you have to Enable Motion in the Web GUI of the device; as well as setting it in Exacq Client software.
It will be listed under something like Analytics>Motion or Alarms or Motion.
Servers are reporting Health Warnings in exacqVision Enterprise Manager. The event details in EM show “This result is based on an Attribute check on Disk /dev/csmi0,2” Note: the device may vary for example /dev/csmi0,0 instead of csmi0,2 or perhaps both.
The corresponding exacqVision Enterprise Manager logs show:
5/9/2021 02:09:11.356 PM (GMT-7:00) SysMgmtPI Warning 5516# Disk = /dev/csmi0,2 Status = This result is based on an Attribute check.
It has been determined that these are false positives and can safely be ignored as they do not affect normal operations. A fix will be available in exacqVision Server 21.09.
Multiple exacqVision Client operators may experience contention and /or “runaways” while simultaneously controlling American Dynamics MP3200 or MP48 Matrix Switcher analog PTZ cameras.
When multiple exacqVision client workstations connect to a NVR that is in-turn connected to a MP3200 or MP48 Matrix switcher, attempts by operators to control multiple analog PTZ cameras simultaneously results in control contention and/or PTZ “run-aways.”
Solution:
The Mechanical PTZ camera protocols “AD-M3200 Multi” and “AD-MP48 Multi” were added to the server to permit simultaneous analog PTZ camera control with these matrix switchers.
Limitation:
WARNING: No more than one recorder may be connected to any one American Dynamics MegaPower 3200 or MegaPower 48 matrix switcher/controller for analog PTZ control.
Updating from 19.12 through 21.06 could cause the event linking Inputs to be renamed. There is a developement build to correct this and will be release in the September release. This is contained to Axis A8027 cameras with relay inputs. The relays will work but the names of the inputs in event linking will be renamed. Rolling back to 19.12 Server will correct this. If this is the case please update to Dev build or our September release.
When set to record, exacqVision Server stores serial data in a database called pospi.db
Default locations are:
Windows C:\Program Files\exacqVision\Server\pospi.db
Linux /usr/local/exacq/server/pospi.db
After verifying that serial data is configured correctly and data is being received if searches fail to return results for serial events check the exacqVision Server logs for entries similar to the following.
POSPI Warning Failed to insert new record into posdb. Statement step failed: 11 database disk image is malformed
POSPI Warning statement reset failed: database disk image is malformed
These messages are indicating the database is corrupted.
Solution
Stop the exacqVision Server Service
Rename or remove the file pospi.db
Restart the exacqVision Server Service Note: The service will detect the missing pospi.db and create a new empty one.