Five 9s Communications · Field & Shop Training

PoE Injector
Bench Test Method

IP Camera Isolation Test — Shop & Field Reference
🎯

What This Test Does

The bench test removes the installed cable run from the equation entirely. By connecting the camera directly to the PoE injector with a known-good short patch cable, you can isolate the fault to one of three components in about two minutes — cable run, PoE injector, or camera — without climbing a ladder or pulling wire.

Steps Completed 0%
GEAR Equipment Needed ▼
Known-good short patch cable — 3 to 5 feet, Cat6
This is your control cable. Keep a dedicated test jumper — tape it, label it, and never use it for anything else. If you don't trust the cable, the test means nothing.
PoE injector under test (the one suspected of failure)
Bring it to the bench, or have it accessible in the field — the injector, its power brick, and all its cables
Known-good spare PoE injector (same wattage class or higher)
Required for the second half of the test. 802.3af (15W) or 802.3at (30W) — must match or exceed camera's requirement
The camera being tested (or a known-good camera of the same type)
In the shop: bring camera off the shelf. In the field: test at the camera location before dismounting if possible
Laptop or tablet — connected to the same network segment as the NVR
Needed to ping the camera IP and/or access its web interface. A phone hotspot won't work — must be on the local camera network
Multimeter (optional but recommended)
Use to confirm injector output voltage before relying on LED indicators. Measure on the DATA+PoE output port — expect 44–57V DC
DIAGRAM Test Connection Layout ▼
Bench test wiring — normal run cable is NOT connected
POWER SUPPLY AC WALL OUTLET 48V DC PoE INJECTOR UNDER TEST DATA IN DATA+PoE OUT POWER IN 3–5 FT PATCH ✓ KNOWN GOOD 📷 CAMERA UNDER TEST 💻 LAPTOP / NVR DATA IN INSTALLED RUN — BYPASSED ✕
━━ Short patch cable (3–5 ft, known good)  |  ━━ DC power  |  ╌╌ Data path to laptop  |  ━━ ✕ Installed run (not connected)
STEPS Step-by-Step Procedure ▼
1
Disconnect the Camera from the Installed Run
Unplug the RJ45 from the camera's network port (or from the injector's DATA+PoE output port at the panel end). The long installed cable is now completely out of the loop. Do not power anything down yet — note whether the injector LEDs change when unplugged.
2
Verify Injector Has Power
Confirm the injector's power LED is on. If using a multimeter, measure the output voltage on the DATA+PoE port before connecting anything — expect 44–57V DC on an idle port. A reading of 0V at this stage means the injector is dead without even starting the camera test.
3
Connect Camera Directly to Injector with Short Patch
Plug the known-good 3–5 ft patch cable directly from the injector's DATA+PoE OUT port into the camera's RJ45 port. Nothing else changes. The camera is now getting its power and data path through the short jumper only — no long run, no panel, no intermediate connections.
4
Observe Camera Boot-Up
Watch the camera's status LED and listen for the IR cut filter click (a faint mechanical click as the camera initializes — common on most IP cameras). Allow 60–90 seconds for a full boot cycle before declaring the camera unresponsive. Some cameras with older firmware are slow to come up.
5
Ping the Camera IP
From a laptop on the same network, run a continuous ping: ping -t <camera IP>. Watch for replies. If the camera boots but you get no ping, the camera may have a different IP than expected — use arp -a or a network scanner to find what appeared on the subnet.
6
Access Camera Web Interface
Open a browser and navigate to the camera's IP. A login page loading confirms the camera is fully operational — power delivery is good, network stack is good, and the camera hardware is functional. If pinging succeeds but the web interface fails, the camera may have a firmware or config issue.
7
Check NVR / VMS for Camera Status
Log into the NVR or VMS and verify the camera channel shows Online / Live. This is the final confirmation that the full chain is working: power → data link → IP connectivity → video stream. If the NVR still shows the camera offline even though ping replies, check for a firewall rule or VLAN separation between the injector DATA IN port and the NVR.
DIAGNOSIS What Does My Result Mean? ▼
What happened when you connected the short patch?
✓ Cable Run Is the Fault

The camera and injector are both working correctly. The installed cable run has the problem. Since the camera is alive on the short jumper but was dead on the long run, the fault is somewhere in the field cable — open pair, short, water damage, crushed jacket, or a bad termination at either end.

  • Next step: Run a wire map / TDR test on the installed run to locate the fault distance.
  • Re-terminate both ends first — if it was a bad termination, that's a 10-minute fix.
  • If the cable itself is damaged, plan a replacement pull.
⚠ Injector May Be the Fault — Swap It

Camera is still offline on the short patch with the original injector. The cable run is now eliminated. The problem is either the injector or the camera itself.

  • Next step: Swap the injector with your known-good spare and retest. This is the critical branch.
  • If camera comes up with the spare → original injector is bad. Replace it.
  • If camera is still offline with the spare → the camera itself is the suspect. Move to camera hardware testing.
✗ Original PoE Injector Is Dead / Failing

Camera works fine with the spare injector but not with the original. The injector is the confirmed fault. This is the most common failure mode on this site — injectors going bad over time.

  • Action: Replace the original injector. Use the same wattage class or higher.
  • Document the failure — this is another data point for the PoE switch upgrade conversation with the client.
  • Before reinstalling, verify the spare injector wattage meets the camera's stated requirement.
✗ Camera Hardware Is Suspect

Camera is unresponsive with both the original and a known-good spare injector, through a known-good short patch. The cable run and the injector have been ruled out. The fault is most likely the camera itself — or a configuration/IP issue.

  • First check: Use a network scanner or arp -a — has the camera reverted to a factory default IP?
  • Try factory resetting the camera (physical reset button — hold 10–15 seconds on most models).
  • If the camera still does not appear on the network after a reset, the camera hardware has failed.
  • Document model and serial, initiate warranty claim or replacement quote.
〜 Intermittent on Short Patch = Marginal Component

If the camera drops in and out even on the short known-good jumper, the fault is either the injector under load, or the camera's network port. The cable run is still eliminated as a factor.

  • Next step: Swap to the known-good spare injector and run a continuous ping for several minutes.
  • If drops stop with the spare injector → original injector is failing intermittently under load (very common — injectors often degrade before dying completely).
  • If drops continue even with the spare injector → camera's RJ45 port or internal network circuitry is marginal. Plan camera replacement.
  • Intermittent faults are worse than hard failures — they cause the most diagnostic confusion in the field.
TIPS Field & Shop Tips ▼
🏷️
Protect your test jumper. Label it "TEST ONLY — DO NOT INSTALL" with tape. If it ever gets run in a wall or used as a patchcord, it may get damaged and invalidate every test you run with it. Keep one in the truck and one on the bench.
🔌
PoE wattage must match or exceed the camera's requirement. A 15W 802.3af injector will appear to "work" with a 25W camera — until the camera's IR LEDs activate at night or it pans/tilts, and then the voltage collapses. Always check the camera spec sheet for maximum PoE draw, not just nominal.
⏱️
Wait the full 90 seconds. It's tempting to call a camera dead after 20 seconds of no response. Some cameras — especially those with older firmware or large configuration files — take 60–90 seconds to fully boot and appear on the network. Start your ping after you see the status LED go solid.
📡
Camera reverted to default IP? After power cycling or a reset, a camera may come up at its factory default (often 192.168.1.64 or similar). If your ping to the configured IP fails but the camera appears to be booting, scan the subnet with arp -a or Angry IP Scanner before assuming hardware failure.
💧
Perimeter / outdoor cameras: dry the connector before testing. If the camera's RJ45 or the cable end has visible moisture or corrosion, dry it with compressed air and let it sit 5 minutes before the bench test. Water on the pins can cause a false intermittent result that clears on its own.
📊
Document every injector replacement. A site that has replaced multiple injectors in a short window is a candidate for a PoE-capable switch. Each injector failure is a data point — date, model, how long it lasted. That record becomes your ROI argument when recommending a switch upgrade.
🔬
Shop use: this is your first test, not your last resort. When a camera comes in for diagnostics, do the bench test before anything else — before checking firmware, before factory reset, before calling the manufacturer. It takes two minutes and eliminates the two most common field failure modes immediately.