THE SHORT ANSWER
PoE identification reports information about a supply; it does not prove sustained power delivery at the device. An inline meter observes the connected device’s demand, while a suitable load tester applies its own test load. Record the method, measurement point and operating conditions so the result stays within what was actually tested.
Which of these four observations have you made?
Keep voltage detection, advertised supply information, inline observation and an applied-load test separate in your notes. They describe different parts of power delivery. A voltage indication can exist without the camera operating reliably, and a camera’s present demand does not by itself establish the maximum power available from the port.
What should an under-load record include?
An under-load record needs the PSE and PD or load identity, the measurement point and the operating condition, as well as the displayed values. Include duration and other powered ports because a shared switch budget can affect the result. Reproduce the feature that triggered the fault, such as infrared lighting, heating or PTZ movement.
- Confirm compatible supply, device and instrument ratings.
- Record whether the instrument observes a real device or applies a test load.
- Record where voltage and power are measured.
- Repeat the failing operating mode with the same other-port loads.
- Save the result and repeat it after repair.
Why does the measurement point matter?
Power reported at the supply and power available at the device are different quantities because the cable and connections have losses. Label the measurement point before comparing readings from a switch, inline instrument or load tester. A difference between two displays may reflect their methods and locations, so it is not automatically evidence of a fault.
The LinkIQ documentation describes advertised power and loaded voltage/power measurements for that model. Do not transfer those capabilities to a different instrument merely because its menu says PoE.
What still remains unproven after a successful load test?
A successful test supports a conclusion about the tested setup and operating conditions. It does not certify the cable category, validate the camera application or prove stability under every possible load and duration. Keep the original restart symptom in view and check device uptime and service operation after reconnecting the actual equipment.
Follow the camera-restart troubleshooting sequence when the practical symptom remains unresolved.
What else should you check before relying on the result?
A test result is useful only within the instrument’s documented capability and the setup used for that measurement. Check the exact model, permitted connection state and acceptance requirement before acting on a PASS. The questions below clarify common assumptions that can otherwise turn a useful observation into an unsupported conclusion.
Does a displayed PoE class guarantee my camera will stay online?
No. Confirm device compatibility, port limits, shared budget, cable condition and behaviour in the failing operating mode.
Can a normal inline meter replace an applied-load tester?
It answers a different question. An inline meter observes the connected load; an applied-load instrument tests according to its own supported method and limits.
Which sources support this guide, and what are their limits?
These references support the distinctions and troubleshooting methods described above. Manufacturer capabilities apply to the named model and operating mode; external cases describe the author’s reported observations. Neither is presented as a WireTrace UK measurement. References were checked on 22 September 2026, and project requirements still govern any acceptance test.
- Fluke Networks — LinkIQ loaded PoE measurements
- Fluke Networks — cable verification, qualification and certification
What should you record for the next visit?
Record the original symptom, equipment models, cable details, connection state and measurement method alongside the result. After a repair, repeat the conditions that produced the problem and save the retest. The blank field record helps keep expected behaviour separate from observed readings; it contains no example values that could be mistaken for measurements.
Download field record ↓