Tag: Axis

Categories
Knowledge Support Support exacqVision Server Categories Products

Axis with VMD4 reporting “Device reporting an error” and stream video

Description

This is limited to Axis cameras supporting VMD4 (fw 6.50 and later) either after factory default or out of box. In this case, the plugin detects VMD4 is preferred over VMD1 and by default VMD4 is stopped. The Axis plugin in this case sends a request to start VMD4 and some camera model and fw might not response correct and return http error 500. The device reports/logs the error. This is resolved by disable/enable the device or manually start VMD4 before connecting to the camera.

<br>

Version Introduced

9.0.0.123243

<br>

Steps to reproduce

factory default axis camera with fw 6.50 and later with VMD4 support

<br>

Expected result

camera connect with motion configuration setting for VMD4.

<br>

Actual result

camera connected and stream but missing motion configuration and connection status showing “Device reporting an error”.

<br>

Work Around

disable/enable the camera would resolve the issue.
manually start VMD4 from the camera web page before connecting to the server.

Categories
Knowledge Support Support Categories Products exacqVision Integrations

Axis M3007 Vs M3047/3048 differences on exacqVision

The M3047/48 are based on different hardware “Ambarella Chipset” when compared to the M3007 cameras.

  • There are some streaming limitations on these cameras and only view areas 1 & 2 are available and no view areas 3 & 4. Although, selecting a dewarped capture mode, you can have overview [fish-eye] plus a dewarped view (view areas 1 & 2 are counted as one dewarped view).
  • The combination of different available views/resolutions in different capture modes are described in the user manual and work is being done will to have this be more clear/specific on the web GUI as well.
  • Selecting the view areas 1 & 2 as dewarped view, you can zoom, pan and tilt on the view areas and then you have the possibility to create preset positions (see page 9 of the user manual). [This can be described as an improvement for those that like modifying view areas]
  • Please be aware that the number of simultaneously pulled and individually configured video streams is a max of 4 on these products. [Because of the Ambarella Chipset]
Categories
Knowledge Support Video Library Demo Support exacqVision Server Categories Products

2021-04 Axis Body Worn Training

Forum Q&A:

https://forum.exacq.com/t/training-q-a-2021-04-axis-body-worn/93/2

PowerPoint

2021-04-Axis-Body-Worn.pptx
Download
Categories
Knowledge Support Support exacqVision Server Categories Products

Axis showing “Request Not Found” when streaming video

Description

When connecting to some Axis cameras that do not support shock event, it could get into a state showing “Request Not Found” in the status of “Add IP Cameras” page. When in this state, the camera is actually connected and streaming video. The issue is that the device does not support shock returning a http error and the plugin did not clear the error. The “Request Not Found” error is also a valid status when try to connect to a non-axis camera.

<br>

Version Introduced

8.2.0.106946

<br>

Platform

All

<br>

Steps to reproduce

  • Verified on Axis M3007
  • Connect camera to server

<br>

Expected result

Device showing “connected” status with video streaming.

<br>

Actual result

Device showing “Request Not Found” with video streaming.

<br>

Work Around

Try reconnect to clear the error.

<br>

Version Fixed

8.2.1.xxxxx

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

Categories
Knowledge Support Support exacqVision Server Categories Products

Axis P8221 audio/DIO only device failed input trigger state

Description

Axis device without video and only support audio/DIO failed to handle notification events.

<br>

Version introduced

8.6.0.114658

<br>

Platforms

All

<br>

Steps to reproduce

Connect to P8221 and trigger input.

<br>

Expected result

Input trigger as expected.

<br>

Actual result

No input triggered.

<br>

Workaround

Revert to server 8.4.x

<br>

Version fixed

8.7.8.115465

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Axis crash server with date/time settings

Description

Server crashes when add Axis camera with date/time on the camera is set to sync manually or with computer time.

<br>

Version introduced

8.6.1.115070

<br>

Platforms

All

<br>

Steps to reproduce

  1. In the camera web page, change the “Time mode” to either manual or with computer time in “Date & Time Settings” page.
  2. connect Axis camera to 8.6.x server.

<br>

Expected result

NTP is sync either to server or override setting.

<br>

Actual result

Server crashes.

<br>

Workaround

Manually set “Time mode” to “Synchronize with NTP server” option.

<br>

Version fixed

8.7.8.115465

<br>

Categories
Knowledge Support Support exacqVision Server Categories

IP Plugin Overrides

The standard form for exacqVision camera addresses is as follows:

{host}{?parameter_1=value_1}…{?parameter_n=value_n}{#override_1=value_1}…{#override_n=value_n}

  • The host is required and must be in the format of an IPv4 address or FQDN (dot separated domain location).
  • The 1 or more name=value parameters are separated by ? and are optional. These are passed to the device.
  • The 1 or more name=value overrides are separated by # marks and are optional, but always last. These are passed to the plugin to modify plugin behavior.

<br><br>

Overrides

PluginOptionUsage
ACTitransport=httpHTTP stream support for legacy platforms and user data
ACTitransport=rtspRTSP stream with separate metadata socket for motion/input trigger/video loss/etc.
Axiszoom=configBy default zoom only cameras support.
Axiszoom=operationForce zoom only operation and controls as part of PTZ and live view.
Axisblocksize=offOn by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues.
Axistransport= {udp,tcp,rtsph,rtsphs}Transport overrides for use with Secure Streaming
Axistunnelport={1025-65535}Override for tunnel port when not the same as CGI port. Use as a workaround for only having 1 port input box/XML attribute.
Axistimestamp={server,trusted}Override timestamp to server time(server) for problem cameras or to camera adjusted by RTSP/RTCP per RFC(trusted)
Arecontnone
Dahuatransport= {udp,tcp,rtsph}Transport overrides for use with Secure Streaming
Dahuatimestamp = serverStamp with server time.
Dahuatimezone=cameraAllow camera to retain timezone when connected to exacq (do not push GMT as we normally do).
Dahuatimezone=utcpush GMT to device, this is also default if not provided.
Hikvisiontimestamp=rtpForce to camera timestamp without waiting for RTCP sync.
Hikvisiontransport={tcp,udp,rtsph,rtsphs}Transport overrides for use with Secure Streaming
Hikvisiongetparameter_override=trueNeeded for HQHI-SATA encoder to prevent stream interruption.
Hikvisionosd_override=offAllow camera time OSD to be displayed (when enabled on camera)
Hikvisiontimezone=cameraAllow camera to retain timezone when connected to exacq (do not push GMT as we normally do).
Hikvisiontimezone=serverPush GMT timezone to camera (because Illustra standard does NOT do this as default)
Hikvision1 timestamp=serverStamp with server time.
Hikvision1 timestamp=rtcpStamp with server time until sync with RTCP server report.
Hikvision1 support=legacySupport original CGI interface.
Hikvision1 support=isapiSupport ISAPI interface.
Illustra3transport=udpStream RTSP session with UDP protocol.
Illustra3zoom=operationForce zoom only operation and controls as part of PTZ and live view.
IllustraFlexnone
Illustranone
Ioimagenone
Ipxnone
IQEyenone
Onviftransport=udp1 TCP socket for RTSP and up to 6 UDP sockets for video, audio, and application data and their RTCP streams.
Onviftransport=rtsp1 TCP socket for RTSP with all other streams interleaved in it.
Onviftransport=httpDefault 2 TCP sockets for RTSP over HTTP over TCP. ( 1 long POST and 1 long GET )
OnvifProfile=xConnect to a specific profile number.
Onvifnat=1Support nNAT translation to WAN address.
Onviftimestamp=serverStamp with server time.
Onvifbank=xSelect 4 channel encoder banks.
Onvifhttp=1.0For Samsung SPE-100/400 that requires http1.0 for live555.
Onvifsupport=profile-sForce Profile-S implementation for cameras that do not fully support Profile-T.
Onvifevents=pull or streamSelect metadata event mode when the manufacturer option is ALL.
Onvifuse_caps={on,off}Use deprecated GetCapabilities for when GetServices is poorly implemented.
Onviftunnel_alive = auto,get_parameter,set_parameter,options,noneKeep alive mechanism during RTPS-over-HTTP, defaults to auto.
Panasonictransport=udpStream RTSP session with UDP protocol.
Panasonictimestamp=serverStamp with server time.
Pelcotransport=udpStream RTSP session with UDP protocol.
RTSPtransport=udpStream RTSP session with UDP protocol.
RTSPtransport={tcp,udp,rtsp,rtsph,rtsphs}All Transport overrides.
RTSPtimestamp=serverStamp with server time.
RTSPtimestamp=rtcpStamp with server time until sync with RTCP server report.
RTSPtimestamp=trustedStamp with cameras time adjusted by RTSP/RTCP per RFC.
RTSPstream=xSelect specific stream number.
RTSPtrack=xSelect specific track number.
RTSPtunnelport={1025-65535}Tunneling port replacing the :portnum on URL.
RTSPembed_port=*Forced RTSP URL format in tunnel.
RTSPhttp=1.0,1.1Forced RTSP URL version number.
RTSPbc_audio=supportedBackchannel audio out.
RTSPbc_samplerate=xxxxBackchannel sampling rate.
RTSPbc_samplesize=xxxxBackchannel sampling size.
RTSPbc_mode=tsBackchannel timestamp mode(duration(default)/timestamp using RTCP adjustment).
Samsungtransport={tcp,udp,rtsp,rtsph,rtsphs}Transport overrides for use with Secure Streaming
Samsungtunnelport={1025-65535}Tunneling port if different than one used for CGI.
Samsunghttp=1.0,1.1Fix for some older devices.
Samsungembed_port=*Fix Internal URL inside tunnel if needed.
Sanyonone
Sonytimestamp=serverStamp with server time.
StarDotnone
UDPnone
Vivoteksupport=legacyUse legacy API and support.
Vivoteksupport=onefwUse OneFW API and live555 stream.

1 The use of these overrides requires the use of IPv4 dotted address, FQDNs cannot be used.
<br><br>

Override Definitions

OverrideDescription
transportStream session with the specified protocol { TCP | UDP }.
timestampStamp frames with server or camera time.
timezone{ UTC | camera | server } Determine if camera timezone is set to UTC+0, left as camera or set to that of server.
zoomOverride configuration or operation zoom function.
blocksizeOn by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues.
profileConnect to profile number N; N is a number from 1 to the number of profiles supported by the camera.
natSupport NAT translation to WAN address.
bankSelect 4 channel encoder banks. N is 1 – number of banks, usually in set { 1 | 2 | 3 | 4}.
supportOverride support API. For example, used by Vivotek to support either legacy or oneFw.
streamSelect a specific stream ID for devices supporting multiple streams.
trackSelect a specific track for devices supporting multiple media tracks.
tunnelportWorkaround for our XML and GUI only giving us one box for port. Used if tunnel port is different than CGI and does not come from CGI.
embed_portValue does not matter. Forces RTSP URL inside tunnel to put port in the URI if it is default. A small selection of cameras need ip:554 even when in a tunnel over 80

<br>

Categories
Documentation Integrations Categories Products exacqVision Integrations

Axis

Axis.pdf
Categories
Documentation Integrations Categories exacqVision Hardware Products

Axis (Perimeter Defender Integration Guide)

Axis-.pdf