GENERIC DRIVERS SEETEC CAYUGA R7

Transcription

1 GENERIC DRIVERS SEETEC CAYUGA R SeeTec AG All rights reserverd Version /11/2015

2 Introduction A generic driver is designed as a driver that can handle different camera or encoder models instead of being determined to a specific camera model. Important: Any camera that is planned to be used with a generic driver should be tested before making any binding agreements. Manufacturer Specific Generic Drivers (Axis, Canon, Hikvision, Samsung, Sony, Arecont Vision) Manufacturer specific generic drivers expand the range of camera model specific static drivers and can be used with any camera model that fulfils the specifications in the table below. For the communication with the device Cayuga uses the manufacturer's proprietary protocol (except Canon which uses Onvif) which is based on the existing implementation that has been well proven over years. For this purpose the native implementation has been extended by querying the camera for its capabilities (codecs, resolutions, frame rates,...) instead of storing all this information about each camera model statically within Cayuga. Configuring a camera with a vendor specific generic driver requires that the camera is available on the network. Generic Onvif Drivers Generic Onvif Drivers can be used for cameras that are not supported via the vendor's native protocol. The camera needs to support the vendor independent Onvif standard. The 'Generic Onvif Driver (Simple)' can be used for low requirements as it doesn't set any parameters on the camera. It simply authorizes at the camera and performs RTSP streaming. Furthermore PTZ control is supported. For higher requirements the much more complex 'Generic Onvif Driver (Profile S Devices)' can be used for any camera which is Onvif Profile-S compliant. In addition to the functionality of the 'Generic Onvif Driver (Simple)' it also supports setting parameters and event triggers. Driver (RTSP/Motion-JPEG) The ' Driver' is the simplest kind of camera driver which is limited to video streaming only using the Motion-JPEG or RTSP protocol. Therefore the administrator has to enter the Motion-JPEG or RTSP streaming URL manually in the configuration for the driver. The streaming URL can be requested directly from each camera manufacturer. It is recommended to test the RTSP/Motion-JPEG compatibility with VCL Media Player first. Notes SeeTec will continuously improve the existing generic drivers and will enhance the spectrum of supported cameras. Please check on if updates are available. Please watch out for an updated list of supported devices at our web pages which were positively tested with one of our generic drivers. We generally recommend compatibility tests before any productive usage of generic drivers since firmware versions of future cameras of the same camera family might behave different compared to the models we have tested. Please feel free to contact SeeTec in case of doubt.

3 Arecont Vision Axis Canon Hikvision Samsung Sony Onvif (Profile S devices) Onvif (Simple) (RTSP) (Motion-JPEG) Cayuga Version Protocol Camera Generation Firmware Versions Video Codecs (max.) Audio Codecs (listen) H.264 Streaming Profiles MJPEG Streaming Modes H.264 Streaming Modes Multi channel support** Read capabilities Set Streaming Parameters Virtual Cameras PTZ: continuous R7 or higher R5 or higher R6 or higher R4 or higher R5 or higher R5 or higher R2 or higher R2 or higher R2 or higher R2 or higher Native Arecont Vision Protocol Any VAPIX Version 3 Onvif Profile-S ISAPI 2.2 Sunapi 2.0 G Onvif Onvif RTSP Motion-JPEG F/M/P/Q Series (H.264 Generation) H.264 Generation: VB-H/VB-M/VB-S Not Specified 5.x Not specified recommended 8x MJPEG 8x H.264 8x total 3x MJPEG 3x H.264 6x total G.711 G.711 µ-law G.726? Baseline Baseline, Main, 1x MJPEG 2x H.264 3x total Not Specified WiseNetIII Generation 6 Not Specified Not Specified Not Specified Not Specified 2x MJPEG 2x H.264 2x total G.711 µ-law G.711 µ-law G.711 a-law Baseline Http_Serverpush HTTP_Serverpush RTP_Over_UDP_Multicast RTP_Over_RTSP_Over_HTT P_unicast RTP_Over_UDP_Multicast Baseline, Main, HTTP_Serverpush Not specified. FW needs to support Sunapi 2.0 2x MJPEG 3x H.264??? 3x total G.711 µ-law G.726 Not Specified 2.x FW needs to meet Core Specification and Profile S 3x MJPEG 3x H.264 3x total 10x MJPEG 10x H x total G.711 µ-law G.711 µ-law G.726 Baseline, Main, HTTP_Serverpush Baseline, Extended, Main, RTP_Over_RTSP_Over_HTT P_unicast RTP_Over_UDP_Multicast FW needs to meet Core Specification x MJPEG 2x H.264 2x total Not Specified 4x MJPEG 4x H.264 4x total Not Specified 4x MJPEG 4x total Not Available Not Available Not Available Not Specified Not Specified Not Available RTP_Over_RTSP_Over_HTT P_unicast Yes Yes No No No No Yes No No No Yes Yes Yes Yes Yes Yes Yes No No No Yes Yes Yes Yes Yes Yes Yes No No* No* Yes Yes No No No No No No No No No Yes Yes Yes Yes Yes Yes Yes No No HTTP_Serverpush Not Available

4 Arecont Vision Axis Canon Hikvision Samsung Sony Onvif (Profile S devices) Onvif (Simple) (RTSP) (Motion-JPEG) PTZ: ClickToCenter PTZ: Area Zoom VMD Trigger Analytics Trigger Tampering Trigger VideoLoss Trigger Dynamic Event Triggers*** HTTPS Digital Inputs Digital Outputs Quad View Camera DeWarping Client DeWarping Edge Storage No Yes No Yes Yes Yes No No No No No Yes No No No No No No No No Yes Yes Yes Yes Yes Yes Yes (max 1) No No No No No No No Yes Yes Yes (max 1) No No No No Yes Yes Yes No Yes No No No No No Yes No No No No No No No No No Yes Yes (max 1) No Yes Yes Yes (max 1) No No No No Yes Yes No Yes Yes Yes No No No Yes Yes Yes (max 1) Yes Yes Yes Yes (max 1) No No No Yes Yes Yes Yes Yes Yes Yes No No No No Yes No No No No No No No No No No No No No No No No No No Yes No No No Yes No No No No No No Yes No No Yes No No No No No General Information / Restrictions Older firmware versions may also work but with functional restrictions. Max configurable frame rate for different capture modes is always 60. Hidden resolutions that aren't available on the web frontend are not supported. Motion Detection has to be set manually on the camera before reading capabilities. 2nd H.264 stream has to be activated manually on the camera before reading capabilities. 'Check Time on Authentication' needs to be disabled on the device Older firmware versions may also work but with functional restrictions. Multi channel encoders: Each channel has its own IP address so they are handled as single channel devices. Instead of the motion detection trigger you can select different trigger types if supported by the camera (max 1). Stream configuration has to be set directly on the camera. The stream from the camera cannot be chosen. It is assigned camera internally. RTSP streaming URL has to be entered manually. Stream configuration (resolution, frame rate etc.) has to be set directly on the camera. Motion-JPEG URL has to be entered manually. Stream configuration (resolution, frame rate etc.) has to be set directly on the camera.

5 Any supported feature depends on the capabilities of the used camera * For some cameras it is possible to set streaming parameters via commands in the streaming URL ** The number of channels will be added automatically ***List of supported event triggers are queried from the device dynamically (e.g. analytics triggers) How to use vendor specific generic drivers Connect camera to the network Create new camera in configuration mode and select the Generic Driver of the manufacturer Cayuga queries the capabilities from the device and offers it for configuration Until the capabilities are read you can only use the RTSP stream from the camera Once you see the model name and firmware version the camera is ready for configuration If you use a PTZ camera please activate PTZ manually in the configuration Known issues for vendor specific generic drivers In certain cases the number of channels for multi channel devices won't be read correctly. Workaround: delete device, add again. The wizard for adding cameras does not fully support generic drivers When adding a camera using a generic driver it may take up to several minutes. Example: If a camera offers multiple capture modes it takes some time to set and query each capture mode one by one. If you add a multi channel device the number of channels will be added automatically. If you change the IP address to a device which has a lower number of channels the number of channels cannot be reduced. Workaround: Delete device, add again For each device that offers different video parameters (especially resolutions) for different video sources only the parameters of source #1 can be used for any source (encoder quad view or virtual cameras of fisheye camera models may be affected) Converting static camera drivers into generic ones may lead to loss of some information For multi streaming the same stream from the camera can be selected twice for different streams in Cayuga. Please make sure you use each stream only once. Example: Hikvision: Use 'Main Stream' for the first stream and use 'SubStream' for the second stream or vice versa PTZ cameras do not show a PTZ camera icon

6 FAQ for vendor specific generic drivers Q: What is the difference between a generic driver and a static driver? A: For static drivers any information about each device is stored in Cayuga (codecs, resolutions, frame rates, digital I/Os, etc.). The generic driver uses the same protocol but queries the camera for its capabilities and offers it to the operator. Q: Is my camera supported by a generic driver? A: If your camera meets the requirements described in the table above it can be used with the generic driver. The compatibility should be tested before productive use. SeeTec is continuously testing and certifying new camera models for the generic drivers. Q: How can I see that a camera was queried correctly? A: Once you can see the correct model name and firmware version of the device in the configuration the device is correctly queried and can be configured. Q: Once the capabilities of a camera are queried in which cases will the information be updated? A: The device will be queried again if the firmware version of the device was upgraded or you enter a different IP address in order to connect to a different device. You can also query again manually by clicking 'Query device'. This may be necessary if some functionality on the device has changed (Example1: On some devices a digital input can be changed to a digital output. Example2: For some devices the supported resolutions may change if it is switched from NTSC to PAL) Q: Will firmware versions different from the specified ones work as well? A: Firmware versions older than the specified ones may work with restrictions. There is no guarantee that firmware versions newer than the specified ones may work. Adjustments to the driver may be necessary. It is recommended to use the firmware versions specified in the table above. Q: Can I fully pre-configure a Cayuga system in the lab before installation on site? A: Yes, for each camera model used on site you need at least one of each for pre-configuration. If a device isn't reachable only limited configuration is possible. Connect the cameras to the network Create each driver once in Cayuga Cayuga reads the cameras capabilities (resolutions, frame rates, I/Os, etc ) Copy each driver as many times as needed Example: On site the following cameras are used: 5 x Axis Q6035 You need one sample in the lab 10x Axis P3367 You need one sample in the lab 20x Sony SNC-EM600 You need one sample in the lab Q: Will further static drivers be released in future? A: For vendors where a generic driver exists no further static drivers are planned.