> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moverse.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Luxonis OAK (RVC2) PoE

> Deployment, network configuration, and troubleshooting.

The **Luxonis OAK (RVC2) PoE** are intelligent cameras used by Moverse Capture.
Typical variants used are wide-angle ones, but narrower field-of-view variants also exist.
Options for either monocular (OAK-1) or stereo and infrared (OAK-D) exist.

> **[Luxonis OAK-1 W PoE Specs](https://shop.luxonis.com/products/oak-1-w-poe?variant=44051403571423)**
>
> ![Luxonis OAK-1 W PoE Camera](https://mintcdn.com/moverse/1XdPWQvShn_qmFDd/images/equipment/cameras/oak1_w_poe.webp?fit=max\&auto=format\&n=1XdPWQvShn_qmFDd\&q=85\&s=64e0d53897e185f93245821379c619ff)

> **[Luxonis OAK-1 PoE Specs](https://shop.luxonis.com/products/oak-1-poe?RGB+Camera+Focus=Fixed-focus)**
>
> ![Luxonis OAK-1 PoE Camera](https://mintcdn.com/moverse/1XdPWQvShn_qmFDd/images/equipment/cameras/oak1_w_poe.webp?fit=max\&auto=format\&n=1XdPWQvShn_qmFDd\&q=85\&s=64e0d53897e185f93245821379c619ff)

> **[Luxonis OAK-D W PoE Specs](https://shop.luxonis.com/products/oak-d-w-poe?variant=44043279302879)**
>
> ![Luxonis OAK-D W PoE Camera](https://mintcdn.com/moverse/1XdPWQvShn_qmFDd/images/equipment/cameras/oakd_w_poe.jpg?fit=max\&auto=format\&n=1XdPWQvShn_qmFDd\&q=85\&s=6a3ad67bd7a5480f3be6c5c10837905d)

> **[Luxonis OAK-D S2 PoE Specs](https://shop.luxonis.com/products/oak-d-s2-poe?RGB+Camera=Fixed-focus)**
>
> ![Luxonis OAK-D S2 PoE Camera](https://mintcdn.com/moverse/1XdPWQvShn_qmFDd/images/equipment/cameras/oakd_w_poe.jpg?fit=max\&auto=format\&n=1XdPWQvShn_qmFDd\&q=85\&s=6a3ad67bd7a5480f3be6c5c10837905d)

***

## Hardware Deployment & Networking

**1. Cabling & Power**

Each OAK (RVC2) PoE unit needs to be connected to a dedicated Power over Ethernet (PoE 802.3af / PoE+ 802.3at) switch port using certified shielded Cat6 or Cat6a cabling.

**2. Network Subnet Configuration**

The host capture workstation network interface card (NIC) must be in the same local IP subnet as the cameras.
Verify that local firewall profiles permit UDP/TCP broadcast traffic for automatic camera discovery.

**3. Automatic Discovery**

Once the Moverse Capture Studio [spawns](/sections/studio/camera_connection.md), it will automatically detect the cameras and populate the Devices list.

***

## Diagnostic Troubleshooting

> **Camera Fails to Power On**
>
> * **PoE Budget Exhaustion:** Verify that the network switch supplies active 802.3af/at power on the specific port and that aggregate array draw does not exceed the switch power supply ceiling.
> * **Cable Integrity:** Test the run with a certified Ethernet cable tester. Passive PoE injectors or non-compliant pinouts will fail to initiate the hardware handshake.

> **Camera Not Discovered by Moverse Capture Studio**
>
> * **Subnet Mismatch:** Ensure the host workstation adapter and camera nodes reside in the identical IPv4 address range (e.g., `192.168.1.xxx` with a `255.255.255.0` mask).
> * **Broadcast Filtering:** Verify that network firewalls or managed switch VLAN configurations are not dropping multicast discovery packets.
> * **Power Cycle:** Disconnect the Ethernet cable, wait 10 seconds to fully discharge internal capacitors, and reconnect to re-trigger DHCP or link-local address assignment.

> **Video Stream Failure or Black Viewports**
>
> * **Process Handles:** Close and relaunch Moverse Hub and Moverse Capture Studio to clear stale camera socket handles.
> * **Switch Backplane Saturation:** Confirm the network switch backplane throughput can handle concurrent continuous video feeds across all active nodes.
>   If bandwidth contention occurs, reduce the **Bandwidth Allocation** slider in Moverse Hub.

> **Frame Drops & Intermittent Disconnections**
>
> * **Flow Control:** Enable flow control on all switch ports.
> * **Jumbo Frames / MTU:** Set the maximum transmission unit (or Jumbo Frame) to the max value (typically 9000).
> * **Dedicated Topology:** Isolate the camera network array from secondary high-traffic office or internet data feeds to eliminate packet collisions.

> **Image Artifacts or Rolling Shutter Flicker**
>
> * **Anti-Flicker Setting:** Match the **Anti-Flicker Frequency** in Moverse Hub (50Hz vs. 60Hz) to the electrical grid frequency of your powerline.
> * **Illumination Levels:** Ensure sufficient volume illumination to prevent high sensor gain amplification, which introduces high-ISO image noise.

***

## Additional Technical Resources

> **[Luxonis Technical Documentation](https://docs.luxonis.com/)**
>
> Low-level hardware schematics, sensor timings, and DepthAI documentation.

> **[Luxonis Community Forum](https://discuss.luxonis.com/)**
>
> Hardware architecture discussions and engineering support threads.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.