Description:
User cannot change OSD colors for rules defined in Analytics tab in Camera configuration
Tested Version:
20.09.08
Fixed:
21.03.107.0
Description:
User cannot change OSD colors for rules defined in Analytics tab in Camera configuration
Tested Version:
20.09.08
Fixed:
21.03.107.0
To enable motion detection on an Illustra 825 Pro Minidome in exacqVision, Stream 2 should always be set for H.264 video compression format with a resolution of 1920×1080 or less. The encoder chip in this camera generates motion notification only on an H.264 stream at that resolution or lower.
Illustra cameras running the exacqVision Edge application in non-DHCP environments
<br>
In a non-DHCP environment, a factory default Illustra camera will acquire a known IP address of 192.168.1.168. Follow these steps to assign the desired IP address to the edge camera:- Connect the Edge camera to the network.
<br>
exacqVision Server 5.10 or later with Illustra cameras using the Illustra3 plugin
<br>
When exacqVision reconnects to an Illustra camera during a stream restart, the socket connection communicating motion events and input trigger events could fail. If this happens, exacqVision will stop processing motion events and input trigger events.
This is caused by the camera responding with an error when the plugin requests the metadata stream URL after the stream restart. If the camera is not yet ready to respond and sends an error to the plugin, the plugin will no longer try to re-establish the connection.
<br>
Two possible workarounds:
<br>
Fixed in exacqVision Server 7.4 and above
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>
r52213 (RC 5.10.x)
<br>
All
<br>
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>
stream connection disabled.
device connection is connected and input trigger still available.
<br>
stream connection disabled.
device connection is also disconnected with the video stream.
<br>
none
<br>
none
<br>
Illustra3
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.
The Pro Gen3 series uses the TI video chipset and requires at least one H.264 stream at 1920×1080. The illustra3 plugin would not allow changing the encoder type to MJPEG in Stream 2 but it does not prevent the user from setting Stream 2 to MJPEG, which causes motion related issues with our plugin. Setting Stream 2 to MJPEG could cause two issues.
<br>
RC5.10
<br>
All
<br>
<br>
<br>
<br>
From the camera web interface, set Stream 2 to H.264.
<br>
Motion mask configuration from the api has been updated by the firmware and now uses motion window index instead of in the motion region. For Illustra Essentials, the updated firmware supports both version 1(motion region) and version 3(motion window) types for configuration of motion mask. The supported firmware to use for Essentials Gen2 should be greater than vEsse5.01.01.00.0004.
When connecting to some essentials camaera’s OEM’ed by Dahua, the customer can put the camera in a mode that shows jpeg in a low quality and the quality slider has no apparent effect.