Harrier 36x AF-Zoom IP Camera with Global Shutter

Approx. 2,350,000 pixels

CVBS from camera

more than 50dB (AGC off)

1/30(25) – 1/20,000 sec

Off / 2x / 4x / 8x / 16x / 32x (/64x : 60 or 50fps mode only)

Auto, lris Priority, Shutter Priority, Manual

OFF / MAX 1x – 32x

ONVIF profile S (via interface board), VISCA (via ONVIF DeviceIO service)

OFF / Low / Middle / High / Auto

Off / BLC / HLC

Detection OFF / 3 positions

Detection ON/OFF

1080p 30fps

The Harrier IP Camera Interface Board is fitted with a standard micro-SD socket (J5) that can accept cards of up to 512GB. There is also a 12-way 0.5mm pitch FFC connector (J6) to enable connection to external/remote SD card sockets.

ONVIF Profile S, IPv4/v6, HTTP, HTTPS, RTSP, RTP, TCP, UDP, RTCP, ICMP, DHCP

The Harrier IP Camera Interface Board is fitted with a 10-way 0.8mm pitch connector to enable connection to a PELCO controller and mono microphone.

When connected to a suitable power supply the Harrier IP Camera Interface Board will boot and then power-up the camera. Once the camera has initialized it will start transmitting an LVDS video stream; the camera interface board will compress the video (H.264), convert it to RTP format, and broadcast it from the Ethernet port. Any RTP/ONVIF compatible application (e.g. VLC player or GStreamer) can then receive and display the video. ONVIF services can be used to control the camera and video stream settings.
When the interface board is connected to the network, any ONVIF compatible application, such as the ONVIF Device Manager (https://sourceforge.net/projects/onvifdm/), can be used to discover the IP address of the board/camera and control the camera/video settings.

The Harrier IP Camera Interface Board platform supports an RTSP server for streaming video and the ONVIF profile S standard for camera control. The RTSP server enables connected host devices to receive and control the H.264 video stream.

ONVIF is a SOAP webservice that standardises the network interface for network video products. The ONVIF services include the following areas:

• IP configuration
• Device discovery
• Device management
• H.264 encoder configuration
• Camera control

The ONVIF and RTSP services can be consumed from many programming languages and several software frameworks already exist to use those services.
For example:

• ONVIF can be readily used from C# using Visual Studio’s ‘Add Service Reference’ utility.
• There are several Python modules available to consume ONVIF services
  • Valkka – “Python Media Streaming Framework for Linux” – supports both ONVIF and RTSP https://elsampsa.github.io/valkka-examples/_build/html/onvif.html
  • Zeep is a SOAP client for Python, which can be used to consume the ONVIF WSDL files. https://docs.python-zeep.org/en/master/client.html
• The GStreamer library includes an RTSP client and can be used to decode and display the live video. GStreamer is a C library with C# and Python bindings.

Visual Studio can load the WSDL files that describe the various ONVIF SOAP services and generate a C#class with methods for the various ONVIF functions.

The ONVIF services supported are listed below:

• Device Management service: allows control of the platform (e.g. set time and date, etc.).
• Media service: Media configurations are used to determine the streaming properties of requested media streams; this enables control of the H.264 encoder and on-screen displays (OSD).
• Imaging service: provides configuration and control data for imaging specific properties.
• DeviceIO service: provides direct communication to the camera serial port (this enables VISCA communication with an attached camera to allow full control of the camera and all its features).

For detailed information on these services please refer to the ONVIF documentation at https://www.onvif.org/profiles/specifications/.

The Harrier IP Camera Interface Board hosts a website which can be used to control the board and camera. When the board is connected, the website can be accessed by connecting to the IP Address of the camera in a web browser.

For more information see the Harrier IP Camera Interface Board datasheet (download tab).

The Harrier IP Camera Interface Board supports direct RS-485 serial communication with external devices. Applications can access the serial port via the ONVIF DeviceIO service.
Function GetSerialPorts() is used to query the list of available serial ports. The Harrier IP has two ports.

• SERIAL_PORT_000: this port is connected to the block camera (VISCA communication).
• SERIAL_PORT_001: this port is connected to the RS-485 port on connector J7.

Function SendReceiveSerialCommand() is used to send and receive data to the port.
This function allows applications to send, and optionally receive, data to/from RS-485 devices attached to the RS-485 port. Please refer to the ONVIF DeviceIO specification for the complete documentation of this function. For serial port examples, please refer to the Harrier IP Example Software.

The Harrier IP Camera Interface Board is able to superimpose graphics and text on the live video stream. This includes graphics with transparent/alpha blended pixels. The application manages these overlays using an API from the ONVIF Media service. The overlays can be stored in system memory (volatile) or in the flash on the platform (non-volatile). The flash has a high but limited number of guaranteed writes, hence in applications where the overlays are frequently changed it is recommended that the volatile setting be used. The functions CreateOSD() and SetOSD() of the media profile have had an optional boolean element added to select if the OSD should be volatile (saved to memory) or not (saved to flash).

More in the Harrier IP Camera Interface Board datasheet (download tab).

The Harrier IP Example Software from Active Silicon contains sample application code that shows how to use the ONVIF services for adding text and graphical overlays to the live video stream and sending VISCA commands to the camera to enable full camera control.

The Harrier IP Camera Interface Board is fitted with several multi-color LEDs to indicate camera status.

• LED1 – ACT
  – indicates activity on the Ethernet link (flashing=activity, steady on=no activity).
• LED2 – LNK
  – indicates the state of the Ethernet link (Green=1G link OK, Red= 10/100 link OK, Off=no link).
• LED3 – Wi-Fi
  – [to be implemented].
• LED4 – STAT
  – indicates the status of the board system (steady green=board has booted successfully).

The board is available in two versions, the Harrier Ethernet Connection Board (AS-CIB-IP-IFETH-001-A) and the Harrier PoE Connection Board (AS-CIB-IP-IFPOE-001-A); the latter allowing Power over Ethernet.

The Ethernet/PoE connection board can be mounted on the back of a camera, or stacked on top of the Harrier IP Camera Interface Board. See product image and views of the boards mounted in the Harrier IP Camera Interface Board datasheet (download tab).

to be confirmed; about 9W

-20°C to +60°C

approx. 141.5 x 55.6 x 65.5mm (L x W x H)
(AS-CIB-IP-001-36LGHD-A and AS-CIB-IP-002-36LGHD-A [wireless])

For PoE:
approx. 153.5 x 55.6 x 65.5mm (L x W x H)
(AS-CIB-IP-003-36LGHD-A and AS-CIB-IP-004-36LGHD-A [wireless])