FAQ

Frequently asked questions about the Interceptor PoE Board

General Questions

How many PoE ports can I have?

  • Single board: 8 ports
  • Dual boards: 16 ports (maximum supported by the Interceptor Carrier Board)

Each PoE board provides 8 ports. The carrier board has two FFC connectors (J9 and J10) for connecting up to two PoE boards.

What PoE standard is supported?

The Interceptor PoE Board supports IEEE 802.3at (PoE+), which provides up to 30W per port. It is also backward compatible with IEEE 802.3af (PoE) devices.

StandardMax PowerCompatibility
802.3af (PoE)15.4W✅ Supported
802.3at (PoE+)30W✅ Supported
802.3bt (PoE++)60W/90W❌ Not supported

Can I use the PoE ports for regular Ethernet?

Yes, the PoE ports function as standard 10/100 Mbps Ethernet ports even when PoE is disabled. However, for Gigabit speeds, use the carrier board’s 4-port switch (J8).

What speed are the PoE ports?

The PoE ports operate at 10/100 Mbps (Fast Ethernet). This is sufficient for most PoE devices like IP cameras, WiFi access points, and VoIP phones.

For Gigabit connectivity, use the carrier board’s built-in 4-port Gigabit switch.

Power Questions

What power supply do I need for PoE?

The PoE boards require:

  1. VOITA 48Vdc Power Converter - Converts PSU 12V to 48V
  2. ATX PSU with adequate 12V rail capacity

PSU Recommendations:

ConfigurationRecommended PSU
8 ports, light load450W+
8 ports, full load550W+
16 ports, light load600W+
16 ports, full load850W+

How much power does each device typically use?

Device TypeTypical PowerMaximum
Basic IP Camera5-8W12W
PTZ Camera15-25W30W
WiFi Access Point8-12W15W
VoIP Phone3-6W10W
Door Access Controller5-10W15W

What happens if I exceed the power budget?

If total power demand exceeds supply capacity:

  • Individual ports may reset or enter fault state
  • System voltage may become unstable
  • Connected devices may power-cycle randomly

Always calculate your power budget before deployment.

Control Questions

How do I enable/disable PoE on a specific port?

Use the /proc/pse interface:

# Enable port 0 on board 0
echo "enable-port 0 0" > /proc/pse

# Disable port 0 on board 0
echo "disable-port 0 0" > /proc/pse

# Check status (streams continuously, Ctrl+C to stop)
cat /proc/pse

The ip link set command controls the network interface, not the PoE power delivery. These are separate functions.

ip link set poe0 down    # Only disables network, NOT PoE power
echo "disable-port 0 0" > /proc/pse  # Actually disables PoE power

Can I control ports without root access?

No, writing to /proc/pse requires root privileges. You can:

  1. Use sudo:

    echo "enable-port 0 0" | sudo tee /proc/pse
    
  2. Create a privileged script or service

  3. Set up sudo rules for specific commands

Can I set ports to enable automatically on boot?

Yes, create a startup script:

  1. Create /usr/local/bin/poe-init.sh:

    #!/bin/bash
    for port in 0 1 2 3 4 5 6 7; do
      echo "enable-port 0 $port" > /proc/pse
    done
    
  2. Make it executable:

    chmod +x /usr/local/bin/poe-init.sh
    
  3. Add to your init system (rc.local or systemd service)

Installation Questions

Which way does the FFC cable go?

  • Contacts face UP (printing visible on top)
  • Blue reinforcement tape faces DOWN
  • Push in as far as possible
  • Check alignment: Both sides should be at the same depth - if one side is deeper than the other, remove and reinsert
  • Lock the clips before powering on

Can I hot-plug the FFC cable?

No. Always power off the system before connecting or disconnecting FFC cables.

Do I need both PoE boards connected?

No, you can use just one PoE board connected to either J9 or J10 - either connector works. The second connector is optional for expansion to 16 ports.

Compatibility Questions

Why don’t my existing PoE cables work?

The Interceptor PoE Board uses Mode B power delivery, which requires all 8 wires in a standard Ethernet cable.

ModePower PinsData PinsCable Requirement
Mode A1, 2, 3, 61, 2, 3, 6 (shared)4-wire minimum
Mode B4, 5, 7, 81, 2, 3, 68-wire required

Some NVR systems and budget surveillance equipment ship with 4-wire cables (only pins 1, 2, 3, 6 connected). These cables work with Mode A devices but will not work with the Interceptor PoE Board.

How to identify 4-wire cables:

  • Often labeled as “CCA” (Copper-Clad Aluminum) or budget Cat5e
  • May be thinner or lighter than standard cables
  • Work with 10/100 Mbps data but only Mode A PoE
  • Common with Swann, Lorex, and other consumer NVR systems

Solution: Replace with standard 8-wire Cat5e or Cat6 cables.

Will any PoE device work?

Most PoE devices work, but verify:

  1. Device supports 802.3af or 802.3at
  2. Device power requirement is under 30W
  3. Device works with 100 Mbps Ethernet (not Gigabit-only)
  4. You are using a standard 8-wire Ethernet cable (for Mode B compatibility)

Can I power a Raspberry Pi via PoE?

Not directly from the Interceptor PoE Board. The Pi uses a non-standard PoE HAT. However, you can use a PoE splitter that provides 5V Micro USB output.

Can I use passive PoE devices?

Not recommended. The Interceptor PoE Board uses standard IEEE 802.3at PoE, which requires proper negotiation. Passive (non-standard) PoE devices may not work or could be damaged.

Network Questions

How do I find the IP address of a connected PoE device?

Use networkctl status with the PoE interface name:

networkctl status poe0

The output shows “Offered DHCP leases” with the IP address assigned to the connected device (if DHCP server is enabled for that interface).

Interface naming:

  • Board 1 (J9): poe0 through poe7
  • Board 2 (J10): poe8 through poe15

Troubleshooting Questions

My device won’t power on from PoE

  1. Verify device is 802.3af/at compatible (not passive PoE)
  2. Check port status: head -20 /proc/pse
  3. Enable the port: echo "enable-port 0 X" > /proc/pse
  4. Try a different cable (Cat5e or better, all 8 wires)
  5. Try a different port

The /proc/pse file doesn’t exist

  • Update to Exaviz OS 2025-05-01 or newer
  • Check FFC cable is connected
  • Check 48V power is connected
  • Verify driver is loaded: dmesg | grep ip808

Port shows “fault” status

  1. Disconnect the device
  2. Reset the port: echo "reset-port 0 X" > /proc/pse
  3. Check for cable damage
  4. Verify device is PoE-compatible
  5. Try a different port

More Questions?

Contact support@exaviz.com with your question.

Last modified February 25, 2026