OAK-FFC 4P PoE¶
The OAK-FFC 4P PoE baseboard uses PoE for power and connectivity, and has 4 FFC interfaces which allows for:
Two 2-lane MIPI camera modules, eg. OAK-FFC-OV9282 (stereo pair)
To see which cameras are compatible with this OAK FFC baseboard, see the guide here: OAK FFC camera modules. Some of camera modules have a M12 mount, so you can use different lenses to get custom FoV (with wide or narrow FOV M12 lenses).
This device also supports PoE passthrough, so you can daisy chain multiple OAK-FFC 4P PoE boards. As the chip is PoE 802.3af, it can supply up to 15.4W of power, which means you can connect up to 3 devices in a row (as each consumes ~5W of power). Note that if you have longer cables and/or utilize all available computation (NN, Stereo, CV, video encoder, CPU, etc.), it might be that you could only connect 2 devices in a row.
This OAK device is built on top of the RVC2. Main features:
4 TOPS of processing power (1.4 TOPS for AI - RVC2 NN Performance)
Run any AI model, even custom-architectured/built ones - models need to be converted.
Encoding: H.264, H.265, MJPEG - 4K/30FPS, 1080P/60FPS
Object tracking: 2D and 3D tracking with ObjectTracker node
Developing with the OAK FFC¶
After connecting cameras to the baseboard, you can use the utilities/cam_test.py script to quickly test whether cameras are working as expected. By default, it will try to run 2x mono cameras on 2-lane mipi ports B (left) and C (right) and 2x color cameras on port A (rgb) and D (4-lane mipi ports).
If you have different cameras connected, you can specify which camera types to use with the
--cameras argument. For example, if you have 3x mono cameras connected to ports A, B, and C, you can run the following command:
python3 cam_test.py --cameras rgb,m right,m left,m
Similarly, to add such configuration into your script you can use the following code:
cam_a = pipeline.create(dai.node.MonoCamera) cam_a.setBoardSocket(dai.CameraBoardSocket.CAM_A) # Same as CameraBoardSocket.RGB cam_a.setResolution(dai.MonoCameraProperties.SensorResolution.THE_400_P) cam_b = pipeline.create(dai.node.MonoCamera) cam_b.setBoardSocket(dai.CameraBoardSocket.CAM_B) # Same as CameraBoardSocket.LEFT cam_c = pipeline.create(dai.node.MonoCamera) cam_c.setBoardSocket(dai.CameraBoardSocket.CAM_C) # Same as CameraBoardSocket.RIGHT cam_d = pipeline.create(dai.node.MonoCamera) cam_d.setBoardSocket(dai.CameraBoardSocket.CAM_D)
Dimensions and Weight¶
Width: 63 mm
Height: 34 mm (PCBA and heatsink)
Length: 125 mm
Weight: 81 g (PCBA and heatsink)
2x 2-Lane MIPI interface
2x 4-Lane MIPI interface
PoE for connectivity and power
Interface for Luxonis OAK-SoM-Pro
Pads for OAK-SoM-Pro 1.8V Aux Signals (I2C, UART, GPIO)
PSRBS connector for FSYNC
Design files produced with Altium Designer 20
Minimal and maximal perceiving distances of the camera¶
Minimal depth perceiving distance of the camera depends on mono camera FOV, resolution, baseline and stereo depth mode, more info is available on the Stereo Depth documentation.
Since this device has modular mono cameras, you can choose a custom stereo baseline (depending on how it is set up). When using OAK-FFC-OV9282, the formulas for min/max depth perceiving distances are:
Min distance (800P) =
882.5 * baseline / 95
Min distance (400P) =
441.25 * baseline / 95
Min distance with extended disparity (800P) =
882.5 * baseline / 190
Min distance with extended disparity (400P) =
max(441.25 * baseline / 190, 19.6)
Max perceivable distance (using subpixel) =
baseline/2 * tan((90 - 71.9/1280) * PI/180)
For more information about the maximum distance see the Stereo Depth documentation.
For FFC cables we use Molex series 15166. Along with the OAK FFC board, we ship 26 pin count, same-sided, 152mm cables (part number 151660281). If you would like to use shorter/longer FFC cables, you can get them here.
It is not possible to power the OAK-FFC-4P-POE via the USB-C connector. So to connect through the USB-C, you will need to power via RJ45 (POE).
Most of the power is consumed by the RVC2, so the power consumption mostly depends on the workload of the chip:
Base consumption + PoE circuitry + camera streaming: 3W - 3.5W
AI subsystem consumption: Up to 1W
Stereo depth pipeline subsystem: Up to 0.5W
Video Encoder subsystem: Up to 0.5W
So the total power consumption can be up to ~5.5W if you are using all the features at 100% at the same time. To reduce the power consumption, you can reduce FPS of the whole pipeline - that way, subsystems won’t be utilized at 100% and will consume less power.
The maximum operating ambient temperature of RVC2 based devices is between 50°C* when fully utilizing the VPU.
Similarly to the Power consumption, max operating temperature depends on VPU utilization. The higher the VPU utilization, the more heat the VPU will generate. The RVC2 VPU can continuously operate at 105 °C, after which the depthai library will automatically shut down the device (to avoid chip damage).
To find out more, see our Operative temperature range documentation.