Categories
exacqVision Server Windows Knowledge Support Support exacqVision Server exacqVision Webservice Products

Axis P3247-LVE “Axis Object Analytics” not passing through the Exacq Mobile 3 app Analytic Rules

Description 

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.

  1. Once camera is set up navigate to the mobile app and connect to the NVR.
  2. Once Connected navigate to the main menu.
  3. Select Push Notifications
  4. Select Analytics
  5. 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.

Solution

Update exacqVision Web Service to 23.09.2

<br>

Categories
exacqVision Server Products

Password Strengthening and Augmented Authentication Integration with S2

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.

Tested versions:

evAPI v1.35.2.53326 :x:
evAPI v1.45.8.0 :check_mark:
evAPI v1.47.15.0 :check_mark:

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.

Internally, Support can obtain the latest evAPI public release here: https://artifactory.exacq.org/artifactory/evapi-local/1.47.x/master/15/

Updating server and web isn’t necessary to get OVID working in this case.


Integration Guide
https://dp0i6fzt6z37.cloudfront.net/wp-content/uploads/S2-Netbox-Integration-Guide.pdf

Fixed in Sept 2023 Release.

Categories
Knowledge Support Support exacqVision Client exacqVision Server exacqVision Webservice Products exacqVision Integrations

exacqVision SDK / API and OEM Solution Partner Requests

Title

exacqVision SDK / API and OEM Partner Solutions

Summary

exacqVision SDK & OEM Solutions, we are part of the Connected Partner Program, so all request must first register via the Connected Partner Portal to be considered.

Description

Exacq Technologies provides integration tools that enable dealers and development partners to rapidly integrate external devices and third party solutions with exacqVision Video Management System (VMS) systems. Video can be integrated with access control systems, retail Point of Sale (POS) systems and more. Exacq provides tools for developing custom integrated solutions and drivers for off the shelf third party products. Multiple options are available with exacqVision open architecture VMS solutions depending on your integration needs.

Product

  • exacqVision CLI 
  • exacqVision Client SDK – evAPI 
  • exacqVision Web Service SDK – evWebAPIexacqVision
  • eDVR Video Compression Boards

Solution

  • Sign-up to the Connected Partner Portal (agreement to legal terms, contact information, tracking, etc.).
  • An exacqVision representative will be notified and assist you with remainder of the process 

NOTE: We do not accept registration from generic email addresses i.e. @gmail.com or @outlook.com, but rather business addresses i.e. @jci.com or @exacq.com.

Categories
Knowledge Support Support exacqVision Server Categories Products

How to: Using EVAPI_Discover to Detect the Connectiodn to an exacqVision Server

Overview

The EVAPI_Discover function is used to test the connection between evAPI and an exacqVision server. When EVAPI_Discover is called, it initiates a Discover request to be sent to an exacqVision server. If the Discover request is received by the server, it sends a Discover response indicating the server was found.

<br>

Usage

It is possible to use the EVAPI_Discover function to detect the connection to an exacqVision server after a logged-in connection has been established with a server. Before a logged in-connection is established, the response from EVAPI_Connect and EVAPI_Login should be used to determine the server connection.

Before calling EVAPI_Discover, it is necessary to set an EVAPI_Callback function that handles the Discover response from the server. If no callback is defined or if ParamType Discover is not handled in the callback, the Discover response from the server is not seen.

The behavior of the EVAPI_Discover function is to queue a Discover request packet in an evAPI instance’s write buffer to be sent to the exacqVision server. If the write buffer has space for the Discover request packet, it return a 0 to indicate success. If the write buffer has filled up because evAPI has not been able to send any data or the write buffer is not being flushed, the function returns a 1 to indicate failure.

To send the Discover request, the EVAPI_Select function or the advanced network I/O should be used. If either of these methods returns an error, there is an issue with the network socket and the evAPI instance must be cleaned up and reinitailized before trying again. (Windows only:) If the EVAPI_CreateWindow function is used, it is not necessary to call EVAPI_Select or use the advanced network I/O function to perform network I/O; the network I/O is tied to the Windows message loop and is performed automatically.

<br>

Possible reasons for a socket error:

  • The connection between evAPI and the exacqVision server is closed.
  • The network cable between the client computer hosting the evAPI instance and the router is disconnected.

<br>

If there is no error on the socket and the Discover request packet is sent, it is then necessary to detect ParamType Discover in the EVAPI_Callback function. If the discover response packet is received by evAPI, ParamType Discover is passed to the callback function indicating that the server was found. If no discover response is received,  ParamType Discover is never passed to the callback.

The console sample shipped with the SDK contains an example of using the EVAPI_Discover function using the command line argument “discover-server”.

<br>

Example

Function evCallback(Parameters: ParamType param, int value, Payload* payload, size_t length )

Switch to handle ParamTypes

Case Discover

Disable or reset watchdog timer

End Case

End Switch

End Function evCallback

Function Main

Intialize evAPI (EVAPI_Init)

Connect to server (EVAPI_Connect)

Login to server (EVAPI_Login)

Set evAPI callback to evCallback (EVAPI_SetCallback)

Queue discover request (EVAPI_Discover)

Perform network I/O (EVAPI_Select)

If queue discover request succeeds and network I/O succeeds

Enable watchdog timer for discover paramtype in callback

Else if queue discover request fails or network I/O fails

Handle failed connection to server

End if

If the discover watchdog timer expires

Handle failed connection to server

End if End Function Main

<br>

How-to-Using-EVAPI_Discover-to-Detect-the-Connectiodn-to-an-exacqVision-Server.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

How to: Executing and debugging C# applications with evAPI and Visual Studio 2005 or newer

C# or other managed applications created with Visual Studio 2005 or newer cause a System.AccessViolationException in the EVAPI_CreateWindow function on Windows Vista and Windows 7. To avoid this while debugging within Visual Studio and during application execution, complete the following steps.

  1. After the project has loaded, select the project properties under the Project item on the toolbar (or press Alt+F7).
  2. Select the Build Events tab.
  3. Enter the following command in the Post-build Event Command Line:
    • call “$(DevEnvDir)..\tools\vsvars32.bat”
    • editbin.exe /NXCOMPAT:NO $(TargetPath)
  4. Select the Debug tab.
  5. Uncheck the Enable the Visual Studio hosting process. This must be done for all configurations that will be executed from Visual Studio.
  6. Save and close the project properties page.
  7. Clean and rebuild the project.

<br>

How-to-Executing-and-debugging-C-applications-with-evAPI-and-Visual-Studio-2005-or-newer.pdf