Category: User Guides

Re-installing an exacqVision Capture Card Driver

Post author By Bhargav Atturu
Post date April 17, 2012

Important

Beginning 12/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems which have an eDVR capture board. In addition, starting with exacqVision Server version 22.06 the XDVPI plugin has been removed and systems where the plugin is present will be blocked from upgrading. In order to either extend the SSA or update to 22.06 or higher the board and the XDVPI plugin must be removed.
Beginning 06/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems using the Dahua DHVECxxxx capture board. The board must be removed in order to extend the SSA.

Note: If your exacqVision Utilities DVD is labeled with a software version 5.6.1.43456 or later, use the following procedure. If your DVD is labeled with an earlier version, skip ahead to the second procedure.

Instructions for exacqVision utilities DVD Versions 5.6.1.43456 and later

Linux

Insert the exacqVision Utilities DVD into the optical drive of the server. The disc will auto-launch.
Double-click BoardPrep.
Type the admin password (admin256 is default).
Press 1 to install the driver.
Press Enter to exit.
Open a Terminal window.
To confirm the module loaded, type the command appropriate for your system:

eDVR: lsmod | grep xdviomod
sdvr, s7dvr, xsdvr: lsmod | grep s6stretch
Dahua: lsmod | grep dm64xc
tDVR: lsmod| grep Exacq

Windows

Insert the exacqVision Utilities DVD into the optical drive of the server. The disc will auto-launch.
Navigate to the Recovery folder and then the Maintenance folder.
Right-click BoardPrep and select Run as Administrator.
Select OK to run.
Press Y to install the driver.
Restart the server.
To confirm the driver has been installed, open Device Manager and verify that the board appears without any yellow exclamation mark.

Instructions for exacqVision utilities DVD Versions earlier than 5.6.1.43456

Determine which capture card is installed

Linux

Enter the following in Terminal: lspci|grep 18a2
The output might look similar to this:

05:00.0 Multimedia controller: Device 18a2:0026 (rev 01)

The portion after “Device” identifies the capture card. Write down this device code and proceed to Step B.
If you see no results, enter the following in Terminal: lspci|grep TriMedia
The output might appear similar to this:

Multimedia controller: Philips Semiconductors TriMedia TM-1300 (rev83)

This is an eDVR card. Write down this information and proceed to Step B.
If you still see no results and you are sure this is a hybrid system, please contact technical support.

Windows

Open Device Manager. If the capture card driver is not installed, the card appears in the device list as Multimedia Controller under Other Devices.
Right-click the Multimedia Controller entry and select Properties.
On the Details tab, select Hardware IDs from the Property drop-down list.
If the device is an exacqVision capture card, the returned Value should appear similar to the following:PCI\VEN_18A2&DEV_0026&SUBSYS_000018A2&REV_01

The device code for the card in the example above is 18a2:0026, based on the numbers and letters immediate after VEN_ and DEV_. Write down your specific device code and proceed to Step B.
If the card is an eDVR card, the returned Value should appear similar to this:

PCI\VEN_1131&DEV_5402&CC_0480
This is an eDVR card. Write down this information and proceed to Step B.
If you do not see a Value similar to the ones listed above, and you are sure this is a hybrid system, try to find another Multimedia Controller in Device Manager or contact technical support.

Download the driver

If you have Internet access, you can find the driver in the following location:

https://exacq.com/support/downloads.html

Otherwise, you can find the driver on the exacqVision Recovery CD that shipped with your system.
Use the following table to determine which driver to download:

Device Code (from Step A)	Card Type	Installer Type	Linux Filename	Windows Filename
19e5:xxxx	DHVRC8008HB	Dahua	dahua.deb	N/A
19e5:3520	DHVEC8016HB (see note 1)	Dahua	dahua.deb	N/A
TriMedia TM-1300	N/A (see note 2)	eDVR	xdvapi.deb	xdvapi.exe
18a2:0002	VRC6016	SDVR	sdvr.deb	sdvr.exe
18a2:000a	VRC6016C	SDVR	sdvr.deb	sdvr.exe
18a2:002b	VRC6016C	SDVR	sdvr.deb	sdvr.exe
18a2:0020	VRC7016L	SDVR	s7dvr.deb	s7dvr.exe
18a2:0023	VRC7008L	SDVR	s7dvr.deb	s7dvr.exe
18a2:0025	VRC7032	SDVR	s7dvr.deb	s7dvr.exe
18a2:0026	VRC7016LX	SDVR	s7dvr.deb	s7dvr.exe
18a2:002A	7008E	SDVR	s7eDVR.deb	s7eDVR.exe
18a2:002B	7016XE	SDVR	s7eDVR.deb	s7eDVR.exe
18a2:1974	xsDVR6516	SDVR	xsdvr.deb	xsdvr.exe
18a2:19e8	xsDVR6632	SDVR	xsdvr.deb	xsdvr.exe
5851:8008	TDVR8008	tDVR	tdvr.deb	tdvr-Setup.exe
5851:8016	TDVR8016	tDVR	tdvr.deb	tdvr-Setup.exe
5851:8032	TDVR8032	tDVR	tdvr.deb	tdvr-Setup.exe

Note 1: Beginning 06/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems using the Dahua DHVECxxxx capture board. The board must be removed in order to extend the SSA..

Note 2: Beginning 12/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems which have an eDVR capture board. In addition, starting with exacqVision Server version 22.06 the XDVPI plugin has been removed and systems where the plugin is present will be blocked from upgrading. In order to either extend the SSA or update to 22.06 or higher the board and the XDVPI plugin must be removed.

Install the driver

Linux

Double click on the appropriate driver file found in Step B.
Click Install Package.
If asked for a password, enter admin256.
After the installation is complete, click Close.
Exit the package installer application by clicking the X in the upper-right corner of the window.

Windows

Run the EXE file found in Step B.
Open Device Manager.
Verify that the board appears as a device without any yellow exclamation marks.

Note: For eDVR systems, you must run Control Center in Windows, or /usr/local/xdvapi/bin/xdvccl in Linux, to populate the device info in XDVAPI.ini.

Re-installing-an-exacqVision-Capture-Card-Driver.pdf

Tags Linux, Windows, KB-00148-148-210209, Re-install, Card Driver, Recovery, SDVR Board, exacqVision Utilities, 1269, Guest

User Guides Documentation exacqVision Mobile Categories Products

Accessing exacqVision from Tablets and Phones using the Exacq Mobile 3 App

Post author By Bhargav Atturu
Post date March 16, 2011

NOTE: This article is a reference for Legacy Exacq Mobile 3 users. Users capable of upgrading their exacqVision Server to version 24.09 and higher should refer to the article: Accessing exacqVision from Tablets and Phones using the exacqVision Mobile App on using the exacqVision Mobile app.

Exacq Mobile 3 receives live and recorded video from the exacqVision Web Service that is connected to the exacqVision recording application.

The Exacq Mobile 3 app allows you to use Apple or Android tablets and smartphones to view live video from an exacqVision server, search for recorded video, and more. To access your exacqVision server over the internet from Exacq Mobile 3, additional configuration is required. The exacqVision Web Service must be installed and configured, and the web server must be accessible through the internet.

The following steps provide an overview of the process required to deploy Exacq Mobile 3 in your environment:

The web service can be installed on the Exacq NVR server or on a separate server. See the exacqVision Web Service User Manual for more details on installation and configuration.
By default, the exacqVision Web Service listens on port 80. This can be modified as needed.
NOTE: A static IP address or DNS name resolution for the web server is recommended to ensure clients can consistently connect from the Internet.
Install and configure the Exacq Mobile 3 application on your device. Compatible devices and configuration steps are described in the Exacq Mobile 3 User Manual.

If you have completed these steps but you cannot see video from Exacq Mobile 3, perform the following troubleshooting steps until the issue is resolved:

On the web server, open a browser and go to the address 127.0.0.1. (If you have changed the port from the default of 80, add a colon and the port number, such as 127.0.0.1:81.) If the exacqVision Web & Mobile Solutions login page does not load, the exacqVision Web Service is not running or is not properly configured on the server.
If the page does load, open the web browser on your mobile device using the cellular data connection instead of WiFi. Load the externally accessible web address of the web server. If the exacqVision Web & Mobile Solutions login page does not load, the name resolution or internet connectivity of the web server is not properly configured on the server.
If the page does load, open the Exacq Mobile 3 app and confirm the address and port settings for your server.
If these steps to not resolve the problem, contact Exacq Technical Support.

Tags Smartphone, Tablet, Exacq Mobile 3, Guest, Mobile, FAQs, KB-00407-407-210209, Phone, 1795, Networking

User Guides Documentation exacqVision Client Categories Products

How to: Using EVAPI_Callback and EVAPI_CallbackEx

Post author By Bhargav Atturu
Post date January 20, 2011

Overview

The evAPI callback functions are used to receive event notifications from the exacqVision server, such as motion detected by a camera or a configuration change made to a server.

Usage

To use the evAPI callback functionality, it is necessary to define and declare a callback function and then assign the function in the API. The format of the definition for the EVAPI_Callback and EVAPI_CallbackEx functions can be found in the API documentation under the Core API module.

To assign the callback function to be used by evAPI, it is necessary to call EVAPI_SetCallback or EVAPI_SetCallbackEx. If both callbacks are assigned, the API will default to using the EVAPI_Callback function and will not execute the EVAPI_CallbackEx function.

Parameters

int param – the event identifier

int value – the event state

PayloadType *payload – data associated with event

size_t length – the size of the payload parameter

PayloadType

u32 camera – camera ID or device ID associated with an event

i32 time – UTC time of the event

u16 ms – millisecond part of the event time

u8 type – 0 for audio, >=1 for video

u8 flags – 0x80 for motion, 0x40 for alarm

u32 trigger – trigger ID associated with an event

i32 time_end – UTC time of the end of the event

u16 ms_end – millisecond part of the event end time

ParamTypes

ParamType Discover – indicates a server was found.

param – Discover

value – N/A

payload – NULL

length – size of payload

ParamType Login – indicates there was a login attempt on the server.

param – Login

value – 0 for success, otherwise error

payload – NULL

length – size of payload

ParamType Config – indicates configuration information has been sent from the server.

param – Config

value – N/A

payload – NULL

length – size of payload

Notes: A ParamType Config is sent any time the configuration of the server changes, such as when a camera is added or removed from the server or a soft trigger is created.

ParamType Status – indicates status information has been sent from the server.

param – Status

value – N/A

payload – NULL

length – size of payload

ParamType Loss – indicates that there is no video signal detected on an analog camera input for the camera id in the payload.

param – Loss

value – 1 for video loss, 0 for no video loss

payload – camera

time

length – size of payload

ParamType Motion – indicates that motion was detected on the camera that corresponds to the camera id in the payload.

param – Motion

value – 1 for motion, 0 for no motion

payload – camera

time

length – size of payload

ParamType Connected – indicates the server no longer detects a previously detected IP camera with the camera id in the payload.

param – Connection

value – 1 for connected, 0 for not connected

payload – camera

time

length – size of payload

ParamType Live – indicates that a live video frame corresponding to the camera id in the payload has been received and decompressed.

param – Live

value – N/A

payload – camera

time

type

flags

length – size of payload

Notes: The type payload field indicates whether audio or video data is being streamed. The flags payload field indicates whether motion or an alarm associated with the camera has been triggered.

ParamType Stored – indicates that a stored video frame corresponding to the camera id in the payload has been received but NOT decompressed.

param – Stored

value – N/A

payload – camera

time

type

flags

length – size of payload

Notes: The type payload field indicates whether audio or video data is being streamed. The flags payload field indicates whether motion or an alarm associated with the camera has been triggered.

ParamType SoftTrigger – indicates that a soft trigger has been set to either on or off on the server.

param – SoftTrigger

value – 1 for trigger on, 0 for trigger off

payload – time

trigger

length – size of payload

ParamType InputTrigger – indicates that an input trigger has been set to either on or off on the server.

param – InputTrigger

value – 1 for trigger on, 0 for trigger off

payload – camera

time

trigger

length – size of payload

Notes: The camera payload field represents the device ID associated with the input trigger.

ParamType EVAPI_DISPLAY – indicates that a frame is ready for display after a call to EVAPI_SetFrame. This means that the frame has been decompressed.

param – EVAPI_DISPLAY

value – N/A

payload – camera

time

type

flags

length – size of payload

ParamType EVAPI_SEARCH_COMPLETE – indicates the server has completed and sent all the found video or meta data from a search.

param – EVAPI_SEARCH_COMPLETE

value – N/A

payload – camera

time

type

flags

length – size of payload

ParamType EVAPI_TEMPERATURE – indicates the temperature status of a device on the server.

param – EVAPI_TEMPERATURE

value – 1 for alarm, 0 for no alarm

payload – camera

time

ms (optional)

length – size of payload

Notes: The camera payload field may also represent a device_id.

ParamType EVAPI_LICENSE – indicates exacq license information has been received from the server.

param – EVAPI_LICENSE

value – N/A

payload – NULL

length – size of payload

ParamType EVAPI_DEVICE_FAIL – indicates that a capture card on the server has failed to initialize.

param – EVAPI_DEVICE_FAIL

value – 1 for alarm, 0 for no alarm

payload – camera (device ID)

– time

– ms (optional)

length – size of payload

ParamType EVAPI_STORAGE_ALARM – indicates the status of a storage drive on the server.

param – EVAPI_STORAGE_ALARM

value – 1 for over threshold, 0 for below or equal to threshold

payload – camera

time

length – size of payload

Notes: The drive number associated with the alarm is indicated by the camera field of the Payload.

ParamType EVAPI_DEVICE_BUTTON – indicates the status of the front panel push button on the exacq server.

param – EVAPI_DEVICE_BUTTON

value – 1 for alarm, 0 for no alarm

payload – camera (device ID)

– time

– ms (optional)

length – size of payload

ParamType EVAPI_LICENSE_PACKET – indicates that a license packet has been received after a call to EVAPI_LicenseRequest.

param – EVAPI_LICENSE_PACKET

value – N/A

payload – NULL

length – size of payload

ParamType EVAPI_CORE_THROTTLING – indicates the status of the server throttling video.

param – EVAPI_CORE_THROTTLING

value – 1 for alarm, 0 for no alarm

payload – time

length – size of payload

ParamType EVAPI_DEVICE_FAN_FAIL – indicates the status a video capture card fan.

param – EVAPI_DEVICE_FAN_FAIL

value – 1 for alarm, 0 for no alarm

payload – camera (device ID)

– time

– ms (optional)

length – size of payload

ParamType EVAPI_SYS_MGMT – indicates the status of storage device.

param – EVAPI_SYS_MGMT

value – 1 for alarm, 0 for no alarm

payload – camera (storage ID)

– time

length – size of payload

ParamType UpdateStatus – indicates the status of a remote server update.

param – UpdateStatus

value –

INSTALL_TIMEOUT = -21,

INSTALL_ERROR = -20,

WGET_PARSE_ERROR = -17,

WGET_FILE_IO_ERROR = -16,

WGET_NETWORK_ERROR = -15,

WGET_SSL_ERROR = -14,

WGET_AUTH_ERROR = -13,

WGET_PROTOCOL_ERROR = -12,

WGET_HOST_ERROR = -11,

WGET_ERROR = -10,

INVALID_PATH_URI = -6,

INVALID_HOST_NAME = -5,

CHECKSUM_FAILED = -4,

INVALID_URI_LOCATION = -3,

NO_BUNDLE_NAME = -2,

UPDATE_FAILED = -1,

NO_UPDATE = 0,

BUNDLE_DOWNLOAD = 1,

BUNDLE_INSTALL = 2,

PENDING_UPDATE = 3,

BUNDLE_FILE = 4,

UPDATE_SUCCESS = 13

payload – time

length – size of payload

ParamType EVAPI_META_DATA_SEARCH – returns video meta data from a EVAPI_MetaDataSearch.

param – EVAPI_META_DATA_SEARCH

value – 0

payload – camera

– time (beginning of meta data block)

– flags (0x80 for motion, 0x40 for alarm, 0x0 for free run)

– time_end (end of meta data block)

length – size of payload

ParamType EVAPI_SOFT_TRIGGER_SEARCH – returns results from a soft trigger search.

param – EVAPI_SOFT_TRIGGER_SEARCH

value – 0

payload –

– time

– time_ms

– trigger

– time_end

– ms_end

length – size of payload

ParamType EVAPI_INPUT_TRIGGER_SEARCH – returns results from an input trigger search.

param – EVAPI_INPUT_TRIGGER_SEARCH

value – 0

payload –

– time

– time_ms

– trigger

– time_end

– ms_end

length – size of payload

ParamType EVAPI_ARCHIVE_ALARM – indicates if the server has lost connection to an archive target .

param – Connection

value – 1 for connected, 0 for not connected

payload – camera ( target ID)

– time

length – size of payload

Example

Function evCallback(parameters: int param, int value, PayloadType *payload, size_t length)

Switch on param

Case Discover

Do something

End Case

Case Login

Do something

End Case

….

Continue for other params

….

End Switch

End Function evCallback

Function Main

Initialize evAPI (EVAPI_INIT)

Set evAPI callback to evCallback (EVAPI_SetCallback)

….

Continue with other functions

….

End Function Main

Note: Samples of how to use the callback with C/C++ or C# are shipped with the SDK in the window and c-sharp samples.

How-to-Using-EVAPI-Callback-and-EVAPI-CallbackEx.pdf

Tags EVAPI Callback, Use Callback, KB-00469-469-210212, EXAPI callbackEx, 2872, Guest

User Guides Integrations Categories Products exacqVision Hardware

Automation Control Circuitry

Post author By Bhargav Atturu
Post date June 2, 2010

What is TTL?

TTL stands for Transistor-to-Transistor Logic, where the “logic” determines which values are high and low.

Standardized common TTL circuits operate with a 5-volt power supply. A TTL signal is defined as low when the voltage is measured between 0.0 V and 0.8 V with respect to the ground terminal, and high when measured between 2.2 V and 5 V (precise logic levels vary slightly between sub-types).

Exacq Hybrid NVR systems and the exacqVision USB I/O Module provide TTL inputs to activate input triggers and create output alarms. This allows exacqVision to interact with external devices/controls which may not provide means to be activated via software integration. The controllers in these systems follow the voltages listed above closely, as shown in the graphic below.

TTL uses a high/low indicator instead of the standard open/closed indicator of a contact closure. Many devices will accept this kind of information; if you have a device that works only with contact closures, you can find devices that convert TTL to contact closure.

Controlling External Devices with TTL Output

Using Event Linking, exacqVision can activate external devices based on configured events, such as motion detection, analytic object detection, system health, input triggers, and more. See our User Training Videos on Event Linking and Event Monitoring, or refer to the User Manual, for information on configuration.

AC Devices

If you want your exacqVision Server to activate a 120VAC device during an event, it is recommended that you use the Xantech AC-1 switched AC outlet and a 120VAC power source/outlet. Event Linking must also be programmed in the exacqVision Client software.

DC Devices

If you want your exacqVision Server to activate a low-voltage device during an event, it is recommended that you use the Altronix RBSN-TTL relay and a 12-24VDC power supply. Event Linking must also be programmed in the exacqVision Client software.

Wet and Dry Contacts

Automation and control devices come in countless forms, from different manufacturers, models, and types of devices. But, the general purpose is to turn a circuit on or off to drive a load of some type. In electrical terms a “load” is the end output device. This could be a light bulb or a motor.

When electricity is applied to actuators or relays there is typically some sort of switching involved, whether a physical switch used by a person, a sensor, or a relay. The contacts switch between an open and closed position to either complete the circuit or break the circuit. Additionally, we tend to think of a completed circuit as being “on”, however when using relays our voltage could be applied to the normally open (NO) or the normally closed (NC) contact, which will determine the behavior of the circuit.

DRY CONTACTS require electricity to be sent to the load from some sort of external source. This is the case when using relays, including those found on Exacq Hybrid NVRs or the exacqVision USB I/O Module. Voltage is usually supplied through a “common wire”. In addition, the I/O terminals on many IP Cameras are relays as well.

WET CONTACTS provide power directly, where the current driving the load flows through the switch itself. Consider the circuit breaker panel for your home. The switch on the circuit breaker allows the current to flow through it to power the devices on that circuit.

Exacq Hybrid NVRs and the exacqVision USB I/O module provide both TTL and relay outputs. While TTLs provide electricity directly through solid-state switching, they usually provide too little current to do anything more useful than power a tiny LED, which is why the relay devices mentioned above are used to introduce external current. Whether you use AC or DC will depend on the device you are attempting to control.

Note, that in Figure 1 and Figure 2 above, both modules provide power to the load from an external source. This is required because the output terminals from Exacq do not provide enough voltage or amperage to drive most devices, only enough to signal another device of a change.

Tags TTL circuits, 2565, Relay, Dry Contact, Guest, TTL, TTL Output

User Guides Documentation exacqVision Server Categories Products

How can I find the version of my exacqVision Client, Server, or Web Service software?

Post author By Bhargav Atturu
Post date April 12, 2010

exacqVision Server

Open the exacqVision Client and connect to the server. Click the Configuration (gear icon) button.
Select Systems from the Configuration tree to open the Systems page.
Find the entry row for the server.
View the version number in the Version column. (If you do not see the Version column even if you scroll all the way to the right, right-click a column header and make sure ‘Version’ is selected.)

Related links:

Download the latest exacqVision Server software

exacqVision Client

Open exacqVision Client.
Click the exacqVision logo in the upper-right corner to display the About box.
View the Client Version number in the About box.
To check for a newer version, connect to the internet and ‘Check for Updates’. Otherwise, click the window ‘X’ to close the About box.

Related links:

Download the latest exacqVision Client software

exacqVision Web Service

Open the Web Service interface.
Hover the cursor over the exacqVision logo in the upper-right corner until the version number appears.

Related links:

Download the latest exacqVision Web Service

Tags Client, Server, Web Client, KB-00474-474-210212, 2898, Version, Software Version, Guest