Categories
Knowledge Support Support exacqVision Server Products

Axis D2110-VE Radar Motion does not work

Please provide these builds to customers for this issue and make sure the customer knows that motion is available as an analytic now, and needs configuration from the webpage. We will tweak the record as well once we close the ticket and in the next official release.

Once this is version is out we can remove this KB.

https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x64.deb​https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x64.exe​https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x86.deb​https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x86.exe

Categories
Knowledge Support Support exacqVision Server Categories Products

Event Linking Input Names are renamed after updating to any software between 20.01 through 21.06.4.0

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.

Reference build:
​https://crm.exacq.com/release/Vision%20Server/21.06.x/21.06.x/exacqVisionServer_21.06.114.0_x64.exe

Categories
Documentation Integrations Categories Products exacqVision Integrations

Axis Perimeter Defender Integration Guide

AXIS-perimeter-defender-integration-guide-updated-3-21.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Using Axis Networked Speakers with exacqVision for Pre-Recorded Clips

Description

Axis networked speaker(s) are individually capable of having pre-recorded audio clips loaded onto them for playback. Audio effects such as door bells, barking dogs, event announcements, and more may be desired for a given site.

Models C1410 / C2005

Playback of audio files from the network speaker(s) cannot be triggered through exacqVision Client or Server.

Whether or not the networked IP speaker is added to the exacqVision server as a licensed device, an operator may trigger various audio clips for playback through the device’s web browser interface or by using a REST endpoint for the device.

The REST endpoint cannot be triggered via exacqVision webhooks.

exacqVision webhooks are currently only capable of issuing ‘POST’ requests, but Axis networked speakers require a ‘GET’ request, as well as authentication to the device.

As a result the current workarounds are suggested:

  1. Trigger playback using API commands through a web browser.
  2. Trigger playback using API commands in your CLI.
  3. Write your own intermediary HTTP listener that accepts ‘POST’ requests from exacqVision webhooks and issues it’s own ‘GET’ requests to your device.

The above suggestions are for advanced users and assistance via Exacq’s Support team is not provided.

Model C1310-E

The C1310-E Network Horn Speaker provides a workaround to native plugin audio playback or the use of webhooks, mentioned above. The following steps detail how to configure a Digital Output and trigger audio clip playback through exacqVision. This method has been tested with Axis firmware 11.4.63 using exacqVision Server and Client 23.03.

  1. Log into the web interface of the C1310-E. Expand the System menu, then select Events.
    System menu<br><br>
  2. From the Rules tab, select ‘Add a rule.’
    Add a rule option<br><br>
  3. Using the Add rule dialog pop-up, provide a descriptive name for the rule. In our example we wish to trigger the built-in ‘Ding Dong’ audio clip, so simply name it ‘Ding Dong.’
    Add rule dialog<br><br>
  4. Complete the rest of the dialog options as seen in the picture below. Select ‘Digital output is active’ from the Condition drop-down menu and select the ‘Use this condition as a trigger’ checkbox.

    From the Action section, select ‘Play audio clip,’ then choose your selected audio clip from the Clip drop-down menu. Optionally, make any changes to the Repeat or Volume fields. Click ‘Save’ when done.
    Add rule dialog filled out<br><br>
  5. Within your exacqVision Desktop Client, enter Configuration mode, then navigate to the Event Linking setup page by clicking the Event Linking node from the tree on the left. <br><br>
  6. Along the bottom of the page, click the New button to create a new Event Linkage.
    Event Linking New button<br><br>
  7. In this example we will choose to create a Soft Trigger to manually trigger the audio playback, but you can just as easily choose another option to trigger playback. Refer to our User Training Videos for more on configuring Event Linking.

    From the Event Type menu, we select ‘Soft Trigger’, then click New under Event Source to create and name a new Soft Trigger.
    <br><br>
  8. Next, select the newly created Soft Trigger from the Event Source list.
    Event Source List<br><br>
  9. Select ‘Output Trigger’ from the Action Type list. You will not have the option of renaming the trigger from the device, but you will note that the C1310-E shows an Output 1 listed as a possible Action Target. Select this option as your Action Target.
    Action target selection<br><br>
  10. Click ‘Apply’ from the bottom of the page to save your changes.
    <br><br>
  11. Returning to Live mode in the client, click the ‘Soft Trigger’ menu icon from the toolbar above.
    Soft Trigger icon<br><br>
  12. From the Soft Trigger menu, you may trigger the audio playback by toggling your newly created soft trigger into Alarm state.
    Soft Trigger menu<br><br>

NOTE: The Axis firmware currently only allows one output trigger to be created at a time, therefore it is only possible to choose one audio clip for playback. Although, you may create many different Event Links to trigger the audio clip to play regardless of the source event it will play the same clip. See workaround methods above for the C1410 and C2005 if this presents an issue.

<br>

Categories
Knowledge Support Support Categories Products exacqVision Integrations

What Files Are Stored To The SD Card In Axis Edge Installs

*** INTERNAL ***

Here is a listing of all the files that sit on the SD card in an Axis Edge installation.

The size of all installed files with no recording is around 25MB


Disk space listing of SD card (cmd: du -h /var/spool/storage/SD_DISK):

64.0k   ./exacq/logs

64.0k   ./exacq/audit

32.0k   ./exacq/blob

18.9M   ./exacq/edvr/2012/05/01/01

106.2M  ./exacq/edvr/2012/05/01/02

96.8M   ./exacq/edvr/2012/05/01/03

100.0M  ./exacq/edvr/2012/05/01/04

76.6M   ./exacq/edvr/2012/05/01/05

398.5M  ./exacq/edvr/2012/05/01

398.6M  ./exacq/edvr/2012/05

398.6M  ./exacq/edvr/2012

398.6M  ./exacq/edvr

32.0k   ./exacq/posdata

32.0k   ./exacq/exacq

10.9M   ./exacq/lib

64.0k   ./exacq/perl/warnings

96.0k   ./exacq/perl/List/Util

160.0k  ./exacq/perl/List

64.0k   ./exacq/perl/Exporter

416.0k  ./exacq/perl/B

64.0k   ./exacq/perl/Net/SSLeay

192.0k  ./exacq/perl/Net

64.0k   ./exacq/perl/auto/List/Util

96.0k   ./exacq/perl/auto/List

64.0k   ./exacq/perl/auto/Socket

64.0k   ./exacq/perl/auto/DynaLoader

160.0k  ./exacq/perl/auto/B

2.7M    ./exacq/perl/auto/Net/SSLeay

2.7M    ./exacq/perl/auto/Net

64.0k   ./exacq/perl/auto/IO

3.2M    ./exacq/perl/auto

64.0k   ./exacq/perl/Scalar/Util

128.0k  ./exacq/perl/Scalar

64.0k   ./exacq/perl/Carp

192.0k  ./exacq/perl/IO/Socket

288.0k  ./exacq/perl/IO

5.1M    ./exacq/perl

4.0M    ./exacq/plugins

419.7M  ./exacq

419.7M  .

Detailed listing of SD card (cmd: ls -R /var/spool/storage/SD_DISK)

.:

exacq

./exacq:

SoftTriggerPI.xml             edvr                          groupspi.xml                  plugins                       psfpi.xml

audit                         edvrserver.key                lib                           posdata                       sendEmail.pl

axispi.xml                    eventpi.db                    logpi.xml                     pospi.db                      serialpi.xml

blob                          eventpi.xml                   logs                          pospi.db-shm                  streampi.xml

core                          exacq                         notify.xml                    pospi.db-wal                  useraccounts.xml

core.xml                      exportpi.xml                  perl                          pospi.xml                     useraccountsAdminDefault.bin

./exacq/audit:

20120501.txt

./exacq/blob:

./exacq/edvr:

2012

./exacq/edvr/2012:

05

./exacq/edvr/2012/05:

01

./exacq/edvr/2012/05/01:

01  02  03  04  05

./exacq/edvr/2012/05/01/01:

3554-00070280.ps   3554-00070280.psi  4054-00070280.ps   4054-00070280.psi  5054-00070280.ps   5054-00070280.psi  5554-00070280.ps   5554-00070280.psi

./exacq/edvr/2012/05/01/02:

0054-00070280.ps   0554-00070280.psi  1554-00070280.ps   2054-00070280.psi  3054-00070280.ps   3554-00070280.psi  4554-00070280.ps   5054-00070280.psi

0054-00070280.psi  1054-00070280.ps   1554-00070280.psi  2554-00070280.ps   3054-00070280.psi  4054-00070280.ps   4554-00070280.psi  5554-00070280.ps

0554-00070280.ps   1054-00070280.psi  2054-00070280.ps   2554-00070280.psi  3554-00070280.ps   4054-00070280.psi  5054-00070280.ps   5554-00070280.psi

./exacq/edvr/2012/05/01/03:

0054-00070280.ps   0554-00070280.psi  1554-00070280.ps   2054-00070280.psi  3054-00070280.ps   3554-00070280.psi  4554-00070280.ps   5054-00070280.psi

0054-00070280.psi  1054-00070280.ps   1554-00070280.psi  2554-00070280.ps   3054-00070280.psi  4054-00070280.ps   4554-00070280.psi  5554-00070280.ps

0554-00070280.ps   1054-00070280.psi  2054-00070280.ps   2554-00070280.psi  3554-00070280.ps   4054-00070280.psi  5054-00070280.ps   5554-00070280.psi

./exacq/edvr/2012/05/01/04:

0054-00070280.ps   0554-00070280.psi  1554-00070280.ps   2054-00070280.psi  3054-00070280.ps   3554-00070280.psi  4554-00070280.ps   5054-00070280.psi

0054-00070280.psi  1054-00070280.ps   1554-00070280.psi  2554-00070280.ps   3054-00070280.psi  4054-00070280.ps   4554-00070280.psi  5554-00070280.ps

0554-00070280.ps   1054-00070280.psi  2054-00070280.ps   2554-00070280.psi  3554-00070280.ps   4054-00070280.psi  5054-00070280.ps   5554-00070280.psi

./exacq/edvr/2012/05/01/05:

0054-00070280.ps   0554-00070280.psi  1554-00070280.ps   2054-00070280.psi  3054-00070280.ps   3554-00070280.psi  4554-00070280.ps   5054-00070280.psi

0054-00070280.psi  1054-00070280.ps   1554-00070280.psi  2554-00070280.ps   3054-00070280.psi  4054-00070280.ps   4554-00070280.psi  5554-00070280.ps

0554-00070280.ps   1054-00070280.psi  2054-00070280.ps   2554-00070280.psi  3554-00070280.ps   4054-00070280.psi  5054-00070280.ps   5554-00070280.psi

./exacq/exacq:

./exacq/lib:

libboost_date_time.so.1.45.0   libdaemon.so.0.5.0             libnss3.so.1oe                 libptypes.so.21                libwx_base-2.9.so.0.0.0

libboost_filesystem.so.1.45.0  libgssapi_krb5.so.2.2          libnssutil3.so.1oe             libsoftokn3.so                 libwx_base_net-2.9.so.0.0.0

libboost_regex.so.1.45.0       libk5crypto.so.3               libperl.so.5.10.1              libsqlite3.so.0                libz.so.1.2.3

libboost_system.so.1.45.0      libkrb5.so.3                   libplc4.so.0d                  libssl.so.0.9.8

libbz2.so.1.0.6                libkrb5support.so.0            libplds4.so.0d                 libssl3.so.1oe

libcom_err.so.2                libldap60.so                   libprldap60.so                 libssldap60.so

libcrypto.so.0.9.8             libnspr4.so.0d                 libproc-3.2.8.so               libstdc++.so.6.0.10

./exacq/logs:

20120501.txt

./exacq/perl:

AutoLoader.pm   Carp            DynaLoader.pm   Exporter.pm     List            SelectSaver.pm  XSLoader.pm     perl            warnings

B               Carp.pm         Errno.pm        IO              Net             Socket.pm       auto            strict.pm       warnings.pm

B.pm            Config.pm       Exporter        IO.pm           Scalar          Symbol.pm       constant.pm     vars.pm

./exacq/perl/B:

Concise.pm  Debug.pm    Deparse.pm  Lint.pm     Showlex.pm  Terse.pm    Xref.pm

./exacq/perl/Carp:

Heavy.pm

./exacq/perl/Exporter:

Heavy.pm

./exacq/perl/IO:

Handle.pm  Socket     Socket.pm

./exacq/perl/IO/Socket:

INET.pm  SSL.pm   UNIX.pm

./exacq/perl/List:

Util     Util.pm

./exacq/perl/List/Util:

PP.pm  XS.pm

./exacq/perl/Net:

SSLeay     SSLeay.pm

./exacq/perl/Net/SSLeay:

Handle.pm

./exacq/perl/Scalar:

Util     Util.pm

./exacq/perl/Scalar/Util:

PP.pm

./exacq/perl/auto:

B           DynaLoader  IO          List        Net         Socket

./exacq/perl/auto/B:

B.so

./exacq/perl/auto/DynaLoader:

dl_findfile.al

./exacq/perl/auto/IO:

IO.so

./exacq/perl/auto/List:

Util

./exacq/perl/auto/List/Util:

Util.so

./exacq/perl/auto/Net:

SSLeay

./exacq/perl/auto/Net/SSLeay:

SSLeay.bs                     get_https3.al                 httpx_cat.al                  put_http3.al                  ssl_write_all.al

SSLeay.so                     get_https4.al                 make_form.al                  put_http4.al                  sslcat.al

autosplit.ix                  get_httpx.al                  make_headers.al               put_https.al                  tcp_read_CRLF.al

debug_read.al                 get_httpx3.al                 new_x_ctx.al                  put_https3.al                 tcp_read_all.al

do_https.al                   get_httpx4.al                 open_proxy_tcp_connection.al  put_https4.al                 tcp_read_until.al

do_https2.al                  head_http.al                  open_tcp_connection.al        put_httpx.al                  tcp_write_CRLF.al

do_https3.al                  head_http3.al                 post_http.al                  put_httpx3.al                 tcp_write_all.al

do_https4.al                  head_http4.al                 post_http3.al                 put_httpx4.al                 tcpcat.al

do_httpx2.al                  head_https.al                 post_http4.al                 randomize.al                  tcpxcat.al

do_httpx3.al                  head_https3.al                post_https.al                 set_cert_and_key.al           want_X509_lookup.al

do_httpx4.al                  head_https4.al                post_https3.al                set_proxy.al                  want_nothing.al

dump_peer_certificate.al      head_httpx.al                 post_https4.al                set_server_cert_and_key.al    want_read.al

get_http.al                   head_httpx3.al                post_httpx.al                 ssl_read_CRLF.al              want_write.al

get_http3.al                  head_httpx4.al                post_httpx3.al                ssl_read_all.al

get_http4.al                  http_cat.al                   post_httpx4.al                ssl_read_until.al

get_https.al                  https_cat.al                  put_http.al                   ssl_write_CRLF.al

./exacq/perl/auto/Socket:

Socket.so

./exacq/perl/warnings:

register.pm

./exacq/plugins:

AxisPI.so         ExportPI.so       LogPI.so          PosPI.so          SoftTriggerPI.so  psfpi.so

EventPI.so        GroupsPI.so       NotifyPI.so       SerialPI.so       StreamPI.so

./exacq/posdata:

Categories
Knowledge Support Support exacqVision Server Categories Products

Axis encoders erroneously display video loss message

Affected Versions

exacqVision Server 7.4

<br>

Description

Axis encoders display video loss message even when the video is being received and displayed.

<br>

Resolution

Update exacqVision Server to version 7.8.0 or higher

Categories
Knowledge Support Support Categories Products exacqVision Integrations

Axis with metadata support does not stream audio-in for jpeg mode

Description

Audio-in failed to stream in jpeg mode for Axis cameras with fw >= 5.70 that support metadata streams for both h.264 and jpeg.

Workaround

Either downgrade the fw if available or stream in h.264 mode.

Categories
Knowledge Support Support exacqVision Server Categories Products

Axis plugin with newer fw failed to trigger digital output

Description

This affects Axis cameras with firmware 5.70 and above, that started using Apache HTTP server. Apache HTTP server is more restrictive in parsing non URI characters such as simicolon and slash and requires percent encoding. For example, “:/” would be encoded into %3a%2f. The end result is that it affect the triggering of digital outputs.

Customer was using Associations to trigger an Alarm output for this camera to trigger an audible alarm at a car dealership. However, after re-clicking the association, the siren continues to sound.

The only way they found to stop the siren was to go to the camera webpage, reverse the Hi/Lo normal state, then reverse it back.

The same thing occurred using a soft trigger as well.

<br>

Tested Version

  • exacqVision Client 7.4.1.89736
  • exacqVision Server 7.4.3.90110

<br>

Platform

[All]

<br>

Steps to reproduce

Trigger and alarm output, then deactivate.

<br>

Expected result

Alarm state reverses.

<br>

Actual result

Alarm state remains.

<br>

Work Around

  • Reverse Hi/Lo normal state at the camera.
  • Downgrade firmware to 5.55.3.5

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Axis analytic event linking items become invalid from add/remove analytic application in camera.

Description

This issue was discovered when we implemented additional shock analytic event support for the Axis plugin. The event linking items were not assigned an unique id but rely on the next item in the list. So if additional analytic event applications are loaded, the initial ID assigned to the analytic event linking item would be invalid depends on the order it is loaded. The fix would be to assign an unique id to each analytic event supported by Axis so any new analytic event added to the system would not invalid or replace the existing ones.

<br>

Version Introduced

r88921 (7.3.20.88942/7.4.0.89235)

<br>

Platform

All

<br>

Steps to reproduce

  1. load cross line application from the camera page(P1364 AC-CC-8E-02-A8-BB was used for this example)
  2. connect to server and add cross line analytic in event linking list.
  3. load VMD3 application in the camera.
  4. disable/enable the axis camera from server.
  5. this Axis should have both cross line and VMD3 in the analytic event linking list.

<br>

Expected result

the existing cross line analytic event should stay valid.

Actual result

the existing cross line analytic event is invalid.

<br>

Work Around

manually replace the invalid event linking item

<br>

Version Fixed

none

<br>

Keywords

Axis Analytic

Categories
Knowledge Support Support exacqVision Client Categories Products

Axis Digital Autotracking

What is Axis Digital Autotracking?

It is an automatic tracking of moving objects. For a detailed explanation and a list of Axis devices that support this feature, go to http://classic.www.axis.com/products/autotracking/index.htm.

<br>

Axis Digital Autotracking Feature Support

exacqVision 7.0 (scheduled for June 2015) adds support for the Axis Digital Autotracking feature.

<br>

Is it enabled by default?

No, it is not enabled by default.

<br>

How do I enable Digital Autotracking?

Download autotracking from http://classic.www.axis.com/techsup/compatible_applications/autotracking/software.php. Install and enable autotracking on the Axis device, and then create View Areas on the device per the manufacturer’s instructions. When this is complete, the created views appear as multistreams in the exacqVision Client tree and on the camera’s settings page in exacqVision Client.

NOTE: Be sure to follow the manufacturer’s guidelines regarding resolution sizes for the primary and autotracking View Areas. Failure to strictly follow those guidelines will significantly impact the device’s performance.

<br>

Which Cameras Support Digital Autotracking?

For a list of devices that support Digital Autotracking, see http://classic.www.axis.com/techsup/compatible_applications/autotracking/software.php.

<br>

Expectations When Upgrading to exacqVision 7.0

If you upgrade to version 7.0, you will not see any changes to Axis camera configurations until you download, install, and enable Digital Autotracking on the device. Digital Autotracking requires that you create View Areas in the device to enable them as secondary streams in exacqVision.

If you used secondary streams before installing and enabling Digital Autotracking, you must manually add View Areas for each secondary stream to ensure they are still available. When enabling View Areas, the device will automatically enable View Area 1 as the primary stream. The device will also activate a View Area called Digital Autotracking if the Digital Autotracking application is enabled and running.

<br>

Benefits of Enabling View Areas

  1. Mirror, rotation, and PTZ functionality in each View Area is independent from other View Areas.
  2. Some devices offer more than four View Areas, which allows more than four secondary streams, which is the current limit in version 6.8 of the Axis plug-in.

<br>

Limitations When Enabling View Areas

  1. This must be done through the device’s web interface.
  2. Some devices allow you to enable View Areas only after installing the Auto tracking application.
  3. Enabling PTZ preset tours in the autotracking view will have a negative impact on performance.