Tag: Plugin

Categories
Plugin Knowledge Support Support exacqVision Server Products SamsungPI

Samsung PNM-C34404RQPZ Connection Issues

Description 

There have been several reports of connection issues with the Samsung PNM-C34404RQPZ. Reports of the units rebooting upon connecting it to the client and which plugin to utilize.


Product 

Exacq Server 24.03.7.0
Camera Info: Samsung PNM-C34404RQPZ
FW used: 23.01.04_20240417_R650

https://www.exacq.com/integration/ipcams/#getCameraRecord=901b747e-fcbf-5464-7543-5aeb7ae3afe8~nstep_id=step-3

Steps to Reproduce 

In the Client go to Add IP Cameras under the configuration. Add the first set of fixed camera’s as you would normally do for any camera.
Add the PTZ camera using the method seen below with the override.

Expected Results 

Camera should connect and work as designed.

Actual Results 

Some reports experience the camera rebooting during connection due to the none use of the power supply that is shipped with the unit. The Power supply must be used.

When connecting the camera as Hanwha or Samsung Plugin on older FW 23.01.03_20240119_R528 will connect but it was reported that motion was not working.

Solution

Update Exacq Server to 24.03.7.0 or above.
Use FirmWare 23.01.04_20240417_R650.
Add PTZ sensor manually using ipaddress#bank=2
Add the camera as Hanwha or Samsung device type.
Make sure the power adapter is of correct specification for proper functioning of the camera. Refer to the camera data sheet.


NOTE:
We have noticed Hanwha has started changing the gov size down to the framerate when users lower the framerate, but not the other way around.

If a user attempts to change a setting while the HTTPS connection is still being attempted, the camera has trouble sending data.

To check this, Log Into the camera web page and verify the GOV size is set to frame rate or higher. Out of the box they are set to 2x framerate. For example- 30fps 60GOV.

AES-878

Categories
Knowledge Support Support exacqVision Server Categories Products

analyticpi plugin fails to load

Description

Users may note that within the exacqVision Client on the System Information page, within the Version Information panel that the analyticpi plugin shows a Status of “Failed – – 1” and the Version column displays “load code – 1”.

<br>

Product

  • exacqVision Server 20.09.0 and above

<br>

Expected Result

Users expect the analyticpi plugin to show a Version number and Status of ‘OK’.

<br>

Actual Result

  • Status: “Failed – – 1”
  • Version: “load code – 1”.

<br>

Solution

The analyticpi plugin is made available for specific analytic appliances and systems, such as the Tyco Analytics Appliance and the Avigilon Analytics Appliance. If there is no such integration the exacqVision Server will not load this plugin, leading to the status shown.

This does not affect cameras with on-board AI analytics as these are supported by the individual camera plugins.

<br>

Categories
Software Categories DSX Documentation Integrations Categories Products exacqVision Integrations

exacqVision DSX Integration Guide

Overview

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:

  1. Obtain a valid Username and Password from the exacqVision Server that will be used with WinDSX.<br><br>
  2. 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>
  3. 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>
  4. Download the exacqVision plug-in for WinDSX from https://support.exacq.com <br><br>
  5. Proceed with the Configuration section

<br>

Configuration

  1. On the WinDSX server, install the exacqVision plug-in for WinDSX. Follow the on-screen prompts.<br><br>
  2. From the Start menu, select All Programs > WinDSX. Log in using the User ID and Password obtained previously.<br><br>
  3. Click the Database window:
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a. Double-click Locations.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;b. Double-click your location.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;c. Click Camera.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;d. Click on the New button in the menu to display the New Camera window.

<br>

  1. On the General tab, enter the following information:
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;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.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;b. Name: This can be any name that you want to assign to the camera.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;c. Camera Type: Select Exacq Technologies from the drop-down list.

<br>

  1. On the Digital Video Camera tab, enter the following information:
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a. DVR Server Name: Enter the IP address of the exacqVision Server.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;b. Assign Cameras: The number of the exacqVision camera (numbering starts at zero). See TIP below.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;c. DVR Server User Logon: The exacqVision Username obtained previously.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;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>

  1. Click OK.<br><br>
  2. Click the Workstation window.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a. Double-click your location.
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;b. Click Cameras.

<br>

  1. 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.

<br>

Categories
Knowledge Support Support exacqVision Server Categories

Cameras Added With the Wrong Plugin Causes exacqVision Server Crash Loop

Description

Adding certain cameras with the wrong plugin type causes the exacqVision Server to go into a crash loop.

Product

  • exacqVision Server

Steps to Reproduce

  • Add a camera using the wrong plugin type

Expected Results

  • Camera fails to connect

Actual Results

  • Camera fails to connect
  • The Server status alternates between “Connected” and “Address Found but Not an exacqVision Server” on the Client Systems page

Solution

  • Stop the exacqVision Server service
  • Import a saved export OR
  • Edit the associated plugin xml file, removing the section for the offending camera(s) OR
  • Delete the associated plugin xml file being mindful this could also remove cameras that are correctly using the plugin
  • Start the exacqVision Server service
  • Determine the correct plugin https://www.exacq.com/integration/ipcams/
  • Add the camera(s) using the correct plugin

NOTE:  This has been specifically observed when Illustra cameras are added with Illustraflex instead of Illustra3 and Samsung cameras are added with Onvif instead of Samsung

<br>

Categories
Knowledge Support Support exacqVision Server

Samsung Trigger Inputs Not working

Description

When the input is triggered on the camera, the input trigger in exacqVision client does not change state.  
Note: this effects Samsung SUNAPI2 cameras

Steps to Reproduce

  • Connect a switch to the cameras input trigger. 
  • In the camera
    • Configure Alarm output 1 (N.O.)/Pulse/5s
  • In the Client
    • add the camera using the Samsung plugin
    • Configure Trigger Input (Open)
    • Verify trigger status Normal and Connection Status Connected
  • Trigger the switch connected to the camera

Expected Result

  • Trigger Input 1’s trigger status changes to alarm in the client.

Actual Result

  • Status does not change in the client

Work Around

  • None at this time, but there will be a fix available in exacqVision Server 22.03.

Categories
Knowledge Support Support exacqVision Server Categories Products

ONVIF Plug-in Crash with Invalid First Video Profile

In rare cases, a camera’s firmware might not provide valid video as the first profile, causing the ONVIF plug-in to crash and producing a log message of “profile 0 missing video encoder configuration.” This was specifically observed with an APAC camera running version 1.1 firmware. This could affect exacqVision Server 6.2.x and later.

<br>

As a workaround, specify a valid profile with the IP hostname:

10.16.10.224#profile=1
10.16.10.224#profile=2

Categories
Knowledge Support Support exacqVision Server Categories Products

ONVIF plugin memory leak: Motion and alarm events received via metadata streaming could cause crash

Affected platforms

exacqVision 5.4 or later

<br>

Symptom

When certain cameras are connected using the ONVIF plugin and the plugin is configured to use metadata streaming to receive motion and alarm events, a memory leak is possible. If memory usage increases enough exacqVision can crash. The crash is typically in ntdll which show a heap memory issue.

To validate this issue is the root cause of a crash, stop the Onvif plugin from requesting a metadata stream as described in the workaround.

<br>

Workaround

Edit the /exacqVision/server/onvifnvcpi.json file to remove the manufacturer’s entry. This will result in the loss of motion-based recording, so modify the recording schedule to use free run recording.

<br>

Resolution

No fix at this time.

Categories
Knowledge Support Support exacqVision Server Categories Products

Illustra3 links device level connection to video stream

Description

Illustra3 supports a separate http socket to stream metadata such as analytic/motion/input trigger. This allows the device level support of events independent of the video stream. Which provides a device level connection state that could be use to monitor the device.

<br>

Version Introduced

r52213 (RC 5.10.x)

<br>

Platform

All

<br>

Steps to reproduce

illustra3 camera(625/825/mini-dome/mini-bullet/Pro/Flex)

program an “IP Camera Connection” event linking for the illustra3 device connection.

disable streaming recording.

<br>

Expected result

stream connection disabled.

device connection is connected and input trigger still available.

<br>

Actual result

stream connection disabled.

device connection is also disconnected with the video stream.

<br>

Work Around

none

<br>

Version Fixed

none

<br>

Keywords

Illustra3

Categories
Knowledge Support Support exacqVision Server Categories Products

Illustra3 – Invalid event linking item when analytic rule name is changed on the camera

Analytic support for the Illustra3 plugin in server version 8.0.x requires firmware 1.2.x and above.

<br>

There are two analytic engines, face detection and object tracking. For object tracking rules, the firmware does not provide a unique id but are based on name provided by the user when the the rules are created. Because of that the user has to be aware that if the name of the rules are changed after they are already added to our event linking, the event linking item could become invalid and would need to be updated in our client.

Categories
Knowledge Support Support exacqVision Client Categories Products

Axis plugin motion detection alarm event might not expire

Description

Setting a Record Video via Video Motion Event will not clear on an Axis Q6114-E camera running Edge software.

<br>

Tested Version

Edge 7.6.1.93449
Firmware 6.20.1
Client 7.6.4.94409

<br>

Platform

Edge

<br>

Steps to reproduce

  • Set a Motion Window on the camera via the Client
  • Confirm Motion Detection is functional
  • Create a new Event in Event Linking – Video Motion > “Motion Test” > Record Video > Pre set to 1 > Post set to 1 > Apply
  • Trigger motion on camera

<br>

Expected result

  • Motion triggers a red border based on the Event. The event should clear 1 second after motion has ceased being detected (based on Post-Trigger timing).

<br>

Actual result

  • The red border only clears when the 127.0.0.1 input is disconnected and re-connected to the Edge server.
  • Deleting the Event while the border is present does not clear the border.
  • Setting the schedule to Event Only has no effect.
  • Soft Triggers still function as expected

<br>

Fixed Version

7.9.16.99811