1/2.8″ Sony IMX462LQR-C CMOS sensor (progressive scan) [issue02 camera]

1080p/60, 1080p/30, 720p/60 720p/30

Color (1/30s, 60dB): 0.003 lux; Color DSS (1/8s, 60dB): 0.00075 lux;

BW (1/30s, 60dB): 0.0004lux; BW DSS (1/8s, 60dB): 0.0001 lux;

[values for AS-CAM-10SHD-A issue02]

OFF/ON

Internal

Off / 2x / 4x / (8x:60 or 50 fps only)

[DSS = Digital Slow Shutter]

Auto, lris Priority, Shutter Priority, Manual

OFF / MAX 2x – 32x

57° to 6.2° [issue02 camera]

Serial VISCA
Pelco-D / Pelco-P

Infrared Cut filter Removal (ICR). Auto / Day / Night / Ext-in.

2D+3D DNR. OFF / Low / Middle / High / Auto

OFF / ON / Night only.

Detection OFF / 3 positions.

Available, ON/OFF.

The Harrier IP Camera Interface Board is connected to the main camera module by a 100mm KEL cable. The corresponding connector on the camera interface board is the same 30-way miniature connector that carries camera LVDS video signals.

H.264

ONVIF profile S, VISCA (via Ethernet connection and ONVIF DeviceIO service)

802.11 a b g n and ac
Dual 2.4 and 5GHz bands

The Harrier IP Camera Interface Board is fitted with a 12-way 0.5mm pitch FFC connector (J3) to enable connection to external/remote SD card sockets.

The Harrier Ethernet Connection Board is fitted with a 24-way 0.5mm pitch vertical FFC connector (with clamp – J1) for connection to a Harrier IP Camera Interface Board.

The Harrier Ethernet Connection Board is fitted with a 4-way JST connector (J3) for connection to an external power supply. The same supply will also power the Harrier IP Camera Interface Board via J1.

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.

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 graphical overlays or video from the camera.

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).

8.25V to 12.25V DC

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

20% to 80% (no condensation)

approx. 165g.