Tag: Illustra3

Categories
Knowledge Support Support Categories Products exacqVision Integrations

Illustra3 with illustraFlex fw 3.1.4 returns http error 500

Description

IllustraFlex firmware 3.1.4 returns http 500 from the http metedata request. The camera failed to respond to a motion/input trigger event. This is a fw issue and is fixed in 3.1.5 archived here.

\\shares.exacq.org\Public\Software\American Dynamics\Illustra Flex firmware\web-update-Ver.3.1.5-20170213.opk.

<br>

Version Introduced

8.2.2.108683

<br>

Platform

All

<br>

Steps to reproduce

  • Connect illustrFlex(ADCi600F/ADCi800F) that supports iAPI3(fw > 3.0.14) to illustra3 plugin.

<br>

Expected result

  • Camera connected and events works as expected.

<br>

Actual result

  • Motion/trigger event failed and return http error 500.

<br>

Work Around

  • Revert to earlier supported fw(3.0.14)

<br>

Version Fixed

Camera firmware 3.1.5

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Illustra3 continues to send disconnect state with status causing an ESM duration rule to fail to trigger

Description

This was reported by Tyco security using ESM and noticed that an illustra3 Pro camera that is disconnected for a while continues to post a disconnected status. The issue is fixed in server 8.2 and later with separating status for device/stream connect state and status only. With earlier server that supports common connection status, all connection status was sent with the connected state. Tyco security was using server version 7.6 and with the illustra 2MP Pro being offlined, it continues to send status with connect state of 0 and status of camera not responding.

<br>

Version Introduced

server 7.6.x

<br>

Platform

All

<br>

Steps to reproduce

  • connect an illustra3 camera and monitor with ESM or evAPI console app.
  • disconnect the camera

<br>

Expected result

  • should only get a camera disconnect state change once followed by status that caused disconnect.

<br>

Actual result

  • continuous to send status update with disconnect state and status.

<br>

Version Fixed

8.2.x

Categories
Knowledge Support Support Categories Products exacqVision Integrations

EdgeStor Issues with Illustra3

Current Issues for using Illustra3 with EdgeStor

  • Camera motion used to trigger Edge recording only records at the start of a motion event with pre/post duration. It does not record again until there is a new motion event.

    Example: If a motion event is detected and continues for an hour, but the pre/post settings are each 10 seconds, the recording will only be 20 seconds in length.
  • It is best for camera configured for continuous Edge recording to be set to GMT-0 and connected to a known, public NTP server.
  • Search on the server might create an overlap of video between EdgeStor video and local server recorded video. This may create a video artifact during playback and/or inconsistent display of vertical bars in the ‘Search Camera’ page. Due to be fixed in a later version. 
  • EdgeStor may drop some video if the camera and/or server disconnected from the network in the middle of retrieving video from the camera. Due to be fixed in a later version.
  • The camera must be in ‘Standard’ mode. A firmware bug causes EdgeStor to fail in ‘Enhanced Security’ mode. 
  • EdgeStor video fails in search if the server is set to a different timezone than local. Due to be fixed in a later version.

Additional Engineering notes and further details can be found here: https://trac.exacq.com/DVR/wiki/TrickleStor

Categories
Knowledge Support Support exacqVision Server Categories Products

Illustra3 links device level connection to video stream

Description

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

<br>

Version Introduced

r52213 (RC 5.10.x)

<br>

Platform

All

<br>

Steps to reproduce

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

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

disable streaming recording.

<br>

Expected result

stream connection disabled.

device connection is connected and input trigger still available.

<br>

Actual result

stream connection disabled.

device connection is also disconnected with the video stream.

<br>

Work Around

none

<br>

Version Fixed

none

<br>

Keywords

Illustra3

Categories
Knowledge Support Support exacqVision Server Categories Products

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

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

<br>

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

Categories
Knowledge Support Support exacqVision 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
Knowledge Support Support exacqVision Server Categories Products

exacqServer Server Crash with Illustra3 Camera Plug-in

exacqVision Server versions earlier than 5.10.3 can crash if you select Apply Defaults on the Camera Settings page of an Illustra camera that does not have a motion mask configured. <br>

To avoid this issue, upgrade to exacqVision Server 5.10.3 or later. As a workaround on earlier versions, create a motion mask on the camera. <br>