Bosch SF8172V Spezifikationen PDF herunterladen (Seite 129)

ONVIF

33-7

FPS. If the user attempts to configure an invalid FPS e.g. 7 the HikVision will accept the

next lowest value (6 FPS) but the web GUI will display 7 FPS.

7 The ONVIF Handler does not support patterns. It does however support presets.

8 Resolutions - The HikVision camera models also display a limitation with regard to their

advertised resolutions. The cameras maintain two media profiles, the primary profile and a

substream secondary profile. For the H264 codec the primary profile can support the

larger resolutions "1280x720" and "1280X960" only, whilst the secondary profile can

support "704x576", "352x288" and "176x144".



An ONVIF query to determine the range of resolutions for the H264 codec will return the

full list of resolutions. When the user attempts (via the NVR web GUI) to configure a

second H264 dual stream they will be presented with the full list of resolutions but in

practice the second stream can only support the 3 lower resolutions values. If the camera

rejects an illegal resolution the NVR will roll back the resolution to the previous value (if

configured previously)



The user should refer to the camera's web page to accurately determine the appropriate

res7)

9 Codecs - Another limitation with the HikVision camera concerns the codec. The HK bullet

camera has two VideoEncoderConfigurations (VEC). The main VEC is hardcoded to H264

and cannot be modified. The substream VEC can support either H264 or MJPEG but the

user has to modify the VEC via its web page to the desired codec and reboot the camera

unit in order to effect the changes. This has serious implications for the ONVIF handler.



The user could choose to modify the codec type through the NVR web GUI and the

change would be successfully propagated to the camera - there is no provision within

ONVIF to determine if a configuration change on the camera should be followed up with a

unit reboot. The net result is the user is unable to configure the codec via the NVR web

GUI for these type of cameras but there will be no warning or error message.



The recommendation is for the user to pre-configure the camera via its web page (where

possible) and allow the NVR web GUI to automatically provision the second stream (eg

during the setup of motion detection alarms)



Note that Bosch cameras return a Payload Type Number=35 for codec=H264. The

gstreamer pipeline within the ONVIF handler cannot support this (assumes H264 codecs

will belong in the dynamic range[4] 96-127). The pipeline could be modified with the

addition of a caps setter element to modify the PT on the fly but this would be a limited

workaround. The Bosch camera will however stream MJPEG correctly to the ONVIF

handler.

10 Dry Contacts/Digital Inputs -These must normally be enabled via the camera's web page

and the unit rebooted in order to take effect (see appendix)

11 Depending on the camera manufacturer, the event ID (which controls preset and dry

contract) may either be 0 based (event count starts with 0) or 1 based (count starts with 1).

Our handler is unable to identify which offset the camera is using. We always assume that

the camera uses 1 based offset for Dry contacts. As a result, for any cameras that are 0

based event ID, when activating Dry Contact 1, it will actually appear as Dry Contact 2 on

victor client

12 We always assume that the camera uses 0 based offset for Presets. As a result, for any

cameras that are 1 based event ID, when activating Preset 1, it will actually appear as

Preset 2 on victor client.

1 2 ... 124 125 126 127 128 129 130 131 132 133 134 ... 174 175

Kommentare zu diesen Handbüchern

Keine Kommentare

Bosch SF8172V Spezifikationen Seite 129

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Sicherheitszugriffskontrollsysteme Bosch SF8172V