1080p 60/30 fps

Up to 512GB

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

OTG (in development)

The Harrier IP Camera Interface Board is fitted with a 24-way 0.5mm pitch vertical FFC connector (with clamp) for connection to an Ethernet or a Power over Ethernet (PoE) connection board via FFC cable.

The Harrier IP Camera Interface Board is fitted with a standard micro-SD socket.

The Harrier IP Camera Interface Board is fitted with a 10-way 0.8mm pitch connector to enable connection to a PELCO controller and 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 a video stream; the camera interface board will compress the video (H.264), convert it to RTP format, and stream it to the Ethernet port. Any RTP/ONVIF compatible application (e.g. VLC media 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 camera 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/ONVIF servers enables connected host devices to receive and control the H.264 video stream.
ONVIF is a SOAP webservice that standardizes 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.
• Device IO 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 see the ONVIF documentation at https://www.onvif.org/profiles/specifications/; examples of how to use the media and DeviceIO services are available from Active Silicon.

The Harrier IP Camera Interface Board hosts an administration website, the Harrier IP 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 using a web browser.

The SD card interface supports all standard micro SD cards (up to 512GB) and operates them in SDR25 mode.  High data rates that come with UHS II cards are not supported and UHS II cards will operate in UHS I modes (lower data rate).  The SD card can be used to store video from the camera.

The SD card interface supports all standard micro SD cards (up to 512GB) and operates them in SDR25 mode. High data rates that come with UHS II cards are not supported and UHS II cards will operate in UHS I modes (lower data rate).
The SD card can be used to store recordings of the camera video. [To be implemented.]

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 – WiFi – TBD.
• LED4 – STAT – indicates the status of the board system (steady green=board has booted successfully).

If your Harrier IP interface board supports WiFi it will have a wireless module fitted and will have a serial number that starts with 724. The title of the Harrier IP Website will also indicate that the board has Wireless/WiFi support.

To receive WiFi signals there must be at least one antenna fitted to the wireless module. The antennae fit to the small microcoaxial MHF4 connectors (A and B) on the module. The connection to a wireless network is achieved using the Wireless page on the Harrier IP Website. On the Wireless page you can scan for available wireless networks, select a suitable network/SSID and enter the password. The Harrier IP will then connect to the network and update the WiFi status on the page. The network SSID and password will be stored and used next time the Harrier IP is powered up. Only one SSID and password is stored.

The wireless network you connect to must be running a DHCP server as, by default, the Harrier IP wireless connection is set to obtain its IP address from a DHCP server. This can be changed by accessing the Harrier IP Website, opening the ‘Network Setting’ web page, selecting the wireless interface, changing the appropriate settings and then clicking on Select. When setting fixed IP addresses please ensure that the address is correct and that you have a note of it before changing it, as it can be very difficult to locate a device at an unknown/incorrect IP address.
Note: when you click on ‘Submit’ the IP address will change, and you will need to use the new address to access steaming video and the Harrier IP Website.

12g (interface board and SD card only, no cables).

1.9 – 2.1W (1080p30)
2.6 – 2.8W (1080p60)

0°C to +60°C (ambient environment).

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 on a Tamron MP1110M/MP1010M under the “More” tab on this product page.

The Harrier Ethernet Connection Board (AS-CIB-IP-IFETH-001-A) is fitted with a 9-way connector for connection to external devices. For pin out see the datasheet.

Connector type: JST – BM09B-SRSS-TB(LF)(SN)

Mating cable: JST – SHR-09V-S-B connector
A suitable cable can be supplied with the evaluation kit (see ordering information)

The Harrier PoE Connection Board (AS-CIB-IP-IFPOE-001-A) is fitted with a 9-way connector for connection to external devices. For pin out see the datasheet.

Connector type: Molex Picoblade 9-way socket 53398-0971

Mating cable: Molex PicoBlade – 0510210900 connector and cables
A suitable cable can be supplied with the evaluation kit (see ordering information).

AS-CIB-IP-IFETH-001-A: 5.5g

AS-CIB-IP-IFPOE-001-A: 15g, without heatsink

AS-CIB-IP-IFETH-001-A: ~ 0.0W (Note: does not include camera or SoC board power)

AS-CIB-IP-IFPOE-001-A: ~ 15% of load current (1.8W max)

0°C to +60°C (ambient environment)

Active Silicon makes the following approval statements:

CE
In accordance with the CE Marking regulations, the Harrier IP Camera Interface Board and the Ethernet/PoE Connection Boards are not a finished product and are supplied for further integration into a finished product that will be CE marked by the final manufacturer/integrator. Therefore, no CE marking or Declaration of Conformity is required or allowed.

RoHS3
This product is compliant with the RoHS3 requirements (Directive 2015/863/EU).

REACH
Please contact Active Silicon for the latest formal REACH declaration (EC 1907/2006).

EMC
This product is designed to be compliant with the following requirements when housed in a suitable enclosure:

• EN 55022:2010 (Class A) and EN 55024:2010 (EU Directive 2014/30/EU Electromagnetic Compatibility
• FCC Rules for Class A digital devices

UL
All printed circuit boards used in this product are manufactured by UL recognized manufacturers and have a flammability rating of 94-V0.