Categories
Knowledge Support Documentation Support exacqVision Server Products

ExacqVision Client Auto-start on Linux-based Systems

Every ExacqVision server is preconfigured to automatically start the ExacqVision Client software after system startup. To disable this feature, run the following commands in a Terminal console:

sudo mv /home/user/.config/autostart/evc.desktop /home/user/.config/autostart/evc.bak<br>
sudo mv /home/admin/.config/autostart/evc.desktop /home/admin/.config/autostart/evc.bak

<br>

To reverse this procedure, run the following commands:

sudo mv /home/user/.config/autostart/evc.bak /home/user/.config/autostart/evc.desktop<br>
sudo mv /home/admin/.config/autostart/evc.bak /home/admin/.config/autostart/evc.desktop

<br>

To configure ExacqVision Client to automatically start on third-party Linux-based ExacqVision systems, complete the following steps:

  1. Run Terminal.
  2. Type sudo gedit
  3. Enter the admin password.
  4. Cut and paste the following into the file:

[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=exacqVision Client
Comment=Load exacqVision Client
Exec=/usr/local/exacq/client/edvrclient
Terminal=false
Type=Application
Categories=
GenericName=

  1. Save the file as exacqVision edvrClient.desktop.
  2. Navigate to File System by typing etc/xdg/autostart/
  3. Click Save.

NOTE: To automatically start a second instance of ExacqVision Client, create a copy of the file and name it exacqVision edvrClient2.desktop. Repeat as desired to automatically start additional client instances, incrementing the number in the filename each time.

  1. Restart the system.

<br>

Categories
User Guides exacqVision Server Categories Products

Re-installing an exacqVision Capture Card Driver

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

  1. Insert the exacqVision Utilities DVD into the optical drive of the server. The disc will auto-launch.
  2. Double-click BoardPrep.
  3. Type the admin password (admin256 is default).
  4. Press 1 to install the driver.
  5. Press Enter to exit.
  6. Open a Terminal window.
  7. 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

<br>

Windows

  1. Insert the exacqVision Utilities DVD into the optical drive of the server. The disc will auto-launch.
  2. Navigate to the Recovery folder and then the Maintenance folder.
  3. Right-click BoardPrep and select Run as Administrator.
  4. Select OK to run.
  5. Press Y to install the driver.
  6. Restart the server.
  7. 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

  1. Enter the following in Terminal: lspci|grep 18a2
  2. 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.
  3. If you see no results, enter the following in Terminal: lspci|grep TriMedia
  4. 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.
  5. If you still see no results and you are sure this is a hybrid system, please contact technical support.

<br>

Windows

  1. Open Device Manager. If the capture card driver is not installed, the card appears in the device list as Multimedia Controller under Other Devices.
  2. Right-click the Multimedia Controller entry and select Properties.
  3. On the Details tab, select Hardware IDs from the Property drop-down list.
  4. 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.
  5. 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.
  6. 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.

<br>

Download the driver

  1. 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.
  2. Use the following table to determine which driver to download:
Device Code
(from Step A)
Card TypeInstaller TypeLinux FilenameWindows Filename
19e5:xxxxDHVRC8008HBDahuadahua.debN/A
19e5:3520DHVEC8016HB (see note 1)Dahuadahua.debN/A
TriMedia TM-1300N/A (see note 2)eDVRxdvapi.debxdvapi.exe
18a2:0002VRC6016SDVRsdvr.debsdvr.exe
18a2:000aVRC6016CSDVRsdvr.debsdvr.exe
18a2:002bVRC6016CSDVRsdvr.debsdvr.exe
18a2:0020VRC7016LSDVRs7dvr.debs7dvr.exe
18a2:0023VRC7008LSDVRs7dvr.debs7dvr.exe
18a2:0025VRC7032SDVRs7dvr.debs7dvr.exe
18a2:0026VRC7016LXSDVRs7dvr.debs7dvr.exe
18a2:002A7008ESDVRs7eDVR.debs7eDVR.exe
18a2:002B7016XESDVRs7eDVR.debs7eDVR.exe
18a2:1974xsDVR6516SDVRxsdvr.debxsdvr.exe
18a2:19e8xsDVR6632SDVRxsdvr.debxsdvr.exe
5851:8008TDVR8008tDVRtdvr.debtdvr-Setup.exe
5851:8016TDVR8016tDVRtdvr.debtdvr-Setup.exe
5851:8032TDVR8032tDVRtdvr.debtdvr-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.

<br>

Install the driver

Linux

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

<br>

Windows

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

<br>

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.

<br>

Re-installing-an-exacqVision-Capture-Card-Driver.pdf
Categories
Knowledge Support Documentation Support exacqVision Server Products

Configuring the Time Server on Linux-based exacqVision Systems

To configure the time server on a Linux-based exacqVision system, complete the following steps:

  1. In exacqVision Client, make sure Enable Time Server is not selected on the Date/Time tab on the System Setup page.
  2. In a Terminal window, type sudo /etc/init.d/edvrserver stop to stop the exacqVision service.
  3. In a Terminal window, type sudo /etc/init.d/ntp start.
  4. Type sudo /etc/init.d/edvrserver start to start the exacqVision service.

On the System Setup page, Enable Time Server should now be selected and not greyed out.

Configuring-the-Time-Server-on-Linux-based-exacqVision-Systems.pdf
Categories
Knowledge Support Documentation Support exacqVision Server Products

Manually Deleting Log Files from Linux-based exacqVision Systems

It is possible for log files to become large enough to prevent proper access to an exacqVision system. If this happens, complete the following steps to delete the files manually:

  1. Restart the system.
  2. During the system startup process, press the Esc key to boot to shell.
  3. Type /usr/local/exacq/server/logs.
  4. Type ls -la for a list of files and sizes.
  5. Type less 'filename' to see the error.
  6. Type sudo rm 'filename'.
Manually-Deleting-Log-Files-from-Linux-based-exacqVision-Systems.pdf

Categories
User Guides Documentation exacqVision Mobile Categories Products

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

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.

<br>

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.

<br>

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

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

<br>

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.

<br>

See also:
Exacq Software/Service Connections Diagram
Example Network Diagram for Dual NIC Systems

<br>

Categories
User Guides Documentation exacqVision Client Categories Products

How to: Using EVAPI_Callback and EVAPI_CallbackEx

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

                 ms

   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

                 ms

   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

                 ms

   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

                 ms

                   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

                 ms

                   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

                 ms

                   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

                 ms

                   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

                 ms

                   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

                 ms

                 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

                 ms

   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.

<br>

How-to-Using-EVAPI-Callback-and-EVAPI-CallbackEx.pdf
Categories
Knowledge Support Documentation Support exacqVision Server Products

RAID Setup Using 3ware Controller – LEGACY

To configure a RAID 5 array using a 3ware controller, complete the following steps:

<br>

  1. Restart the computer.
  2. When prompted, press Alt-3 to enter the 3ware RAID BIOS.
  3. If prompted, type admin256 as the password.
  4. Press any key to acknowledge the warning.
  5. The available drives are listed under Exportable Units. If you are re-creating a failed RAID array, some drives will still be a part of the old array. You must delete the old array before creating the new array. To do this, complete the following steps:

    <br>

    a.) Select the drives in the failed RAID array by pressing Enter when they are highlighted and using the up and down arrows on the keyboard.
    b.) Press Tab to enter the menu.
    c.) Select the Delete Unit square and press Enter.
    d.) Press Enter to confirm. This allows all the drives to be included into one RAID array.

    <br>
  1. Navigate to the top of the list of drives listed as Exportable Units. Highlight Direct Attached and press Enter. Each drive should have asterisk (*) next to it.
  2. Press Tab to enter the menu.
  3. Navigate to the Settings square and press Enter.
  4. Select Controller Policies and press Enter.
  5. Select each policy you want to change and press Enter. Select the correct setting from the list, or type the desired value and press Enter.

    a.) Export JBOD Disks should be No.
    b.) Staggered Spinup should be Enabled.
    c.) Delay Before Spinup should be 2.
    d.) Number of Drives Per Spinup should be 1.
    e.) Delay Between Spinups should be 1 second.
    f.) Staggered Method should be SATA00B.
    g.) Auto-Carving should be Enabled.
    h.) Carving Factor should be 2048.
    i.) Auto-Rebuild should be Enabled.
    j.) Auto-Verify Preferred Start Day should be Saturday.
    k.) Auto-Verify Preferred Start Time should be 12:00am.

    <br>
  1. Navigate to OK and press Enter.
  2. Navigate to Create Unit and press Enter.
  3. Select each setting you want to change and press Enter. Select the correct setting from the list, or type the desired value and press Enter.

    a.) Array Name should be Exacq.
    b.) RAID Configuration match the raid level desired (5 or 6).
    c.) Stripe Size should be 256KB.
    d.) Write Cache Setting should be Enabled.
    e.) Read Cache Setting should be Intelligent.
    f.) StorSave Profile should be Performance.
    g.) Auto-Verify should be Enabled.
    h.) Rapid RAID Recovery should be Fast Rebuild/Shutdown.

    <br>
  1. Select Advanced and press Enter.
  2. Select each setting you want to change and press Enter. Select the correct setting from the list, or type the desired value and press Enter.

    a.) Boot Volume Size should be 33.
    b.) Drive Querying Mode should be Enabled.
    c.) Continue On Error When Rebuild should be Disabled.
    d.) Initialization Method should be Background.

    <br>
  1. Navigate to OK and press Enter.
  2. Navigate to OK and press Enter.
  3. Press Y to confirm cache without a battery.
  4. Note values and press any key.
  5. Press F8.
  6. Press Y to Save Configuration and Exit.

    <br>

Now you can install the operating system.
<br>

Categories
User Guides Integrations Categories Products exacqVision Hardware

Automation Control Circuitry

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.

<br>

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.

Figure 1

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.

Figure 2

<br>

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.

<br>

Categories
Knowledge Support Documentation Support exacqVision Server Products exacqVision Integrations

Connecting an ExacqVision Hybrid System to a Pelco Coaxitron Translator for Analog PTZ Control

ExacqVision Hybrid servers have the ability to integrate with Pelco Coaxitron CXTA 9760 devices. This allows customers with existing Pelco PTZ cameras that are controlled through the coax with the Coaxitron protocol to be controlled using ExacqVision software. The CXTA accepts the Pelco 422 protocol from the ExacqVision server, and it outputs the data over the video cable.<br><br>

To use a Pelco Coaxitron Translator (CM9760-CXTA) to control up to 16 analog PTZ cameras using an exacqVision Hybrid system, complete the following steps.<br><br>

I. Connect video from the CXTA to the exacqVision Hybrid system

Connect the BNC Out from the CXTA to Video In on the ExacqVision Hybrid system. The input/output numbers do not have to match because the CXTA input position determines where the PTZ commands are sent.<br><br>

II. Configure the CXTA dipswitches

Set CXTA dipswitches 1 and 2 to OFF to enable 32-bit extended Coaxitron.

Set dipswitch 3 ON to enable Pelco D protocol.

Set dipswitch 8 to ON to enable Spectra equipment type.

III. Connect RS-485 TX+/- on the ExacqVision Hybrid system to the OUT RJ-485 connector on the CXTA

NOTE: For this process, you need a CAT5 cable with one RJ-45 end, a wire stripper, and a small screwdriver.

  1. On the end of the cable without the RJ-45 connector, strip wires 7 and 8 to expose the copper. If the cable is TIA standard, the wires are white/brown and brown.<br><br>
  2. Locate the RS-485 terminal block on the back of the ExacqVision Hybrid system.<br><br>
  3. Use a small screwdriver to loosen (not remove) the TX+ and TX- screws on the RS-485 terminal. You can remove the terminal connector to see the labels.<br><br>
  4. Insert the brown wire into the TX+ position on the RS-485 terminal and tighten the screws.<br><br>
  5. Insert the white/brown wire into the TX- position on the 485 terminal and tighten the screws.<br><br>
  6. Plug the other end of the CAT5 cable into the OUT RJ-485 connector on the CXTA.<br><br>

IV. Enable the serial port in the ExacqVision Client software

  1. In ExacqVision Client, open the Configuration page.<br><br>
  2. Select Serial Port Setup.<br><br>
  3. Locate the RS-485 connection. In Windows, the highest numbered COM port is typically where the RS-485 connection communicates.<br><br>
  4. In the Use column, select PTZ from the drop-down list.<br><br>
  5. Give the connection a name (Pelco CXTA, for example).<br><br>
  6. In the Profile/Protocol section, select Pelco-D from the drop-down list.<br><br>
  7. In the Baud Rate column, select 2400 from the drop-down list.<br><br>
  8. In the Data Bits column, select 8 from the drop-down list.<br><br>
  9. In the Stop Bits column, select 1 from the drop-down list.<br><br>
  10. In the Parity column, select None from the drop-down list.<br><br>
  11. Leave Flow Control at None and Max Line Length at 80.<br><br>
  12. Click Apply.<br><br>

V. Enable PTZ control on the camera and test it in the exacqVision Client software

  1. In ExacqVision Client, open the Configuration page.<br><br>
  2. Select the first input that you want to configure as a PTZ camera to open the Camera Setup page. The inputs are listed below the Camera Recording Setup icon in the configuration tree.<br><br>
  3. In the Serial Port drop-down list, select the COM port enabled in the previous steps.<br><br>
  4. In the Address drop-down list, select the address that matches the camera’s input on the CXTA. For example, if the camera is connected to Input 6 on the CXTA, select 6 as the address.<br><br>
  5. Click the Presets button on the left (not the digital Presets button).<br><br>
  6. Click the Pan/Tilt buttons to move the camera around.<br><br>
  7. Click the Zoom buttons to zoom in and out.<br><br>
  8. Repeat steps 1-7 for each of the cameras connected to the CXTA that you want to configure as PTZ cameras.<br><br>

Attached are the Pelco documents on the CXTA model.

Pelco_CM9760_CXTA_Coaxitron_Translator_manual.pdf Pelco_CM9760_CXTA_Coaxitron_Translator_spec.pdf
Categories
Knowledge Support Documentation Support exacqVision Client Products

Does the ExacqVision Client Support Multiple Monitors?

Yes, ExacqVision Client supports multiple monitors. We have tested up to four VGA monitors from a single workstation.

Typically, a user will run one instance of the ExacqVision Client per monitor. Because decompressing video is CPU-intensive, we recommend one core per Client for the best user experience. To drive up to four VGA monitors, we recommend an Nvidia T1000 graphics card. For always-on, higher end multi-monitor displays consider the Nvidia RTX A-2000 up to the Quadro GV100 discrete graphics cards.

The Nvidia P2000 has been tested running the ExacqVision Client with VGA and DVI monitors up to 1920×1200 resolution.

<br>