What Is a PoE Camera? Power and Data Over One Ethernet Cable
Half the cost of putting a camera somewhere is getting power to it. The optics are decided in an afternoon; the electrician is booked for a week.
A PoE camera removes that second job. One Ethernet cable carries the video down and the power up, so the camera goes where the view is rather than where the socket is. Power over Ethernet camera is the full name; PoE is what everyone actually says.
This post covers what a PoE camera is in practical terms, how the power negotiation actually works, which standard your build needs, and which Vadzo Innova modules fit. Every module here is a board-level embedded vision camera rather than a boxed unit.
What Is a PoE Camera and What Makes It Different
Answer first: a PoE camera is a network camera that draws its power from the same Ethernet cable that carries its video, so no separate DC supply is needed at the mounting point.
Everything else about a Power over Ethernet camera is ordinary. It captures images for inspection, monitoring, or analytics exactly as any other camera does, and it streams them to an embedded computer, an industrial PC, or an edge processor over the network.
So what a PoE camera is is a question about wiring rather than imaging. The sensor, the lens, and the ISP behave the same whether the board is powered locally or over the network.
A PoE IP camera is therefore still the eye of the system. What changes is that the eye needs one cable instead of two, which is the difference between a cable tray and a cable tray plus a conduit run.
A PoE network camera also becomes a managed device on your network the moment it is plugged in, discoverable and configurable from the same place as everything else in the rack.
How Does a PoE Camera Work: Switch, Injector and Negotiation
Three pieces make it work, and only one of them is the camera.
On the camera side, the board carries a PoE interface behind its RJ45 connector. You plug in Ethernet and nothing else.
On the network side, the other end goes to a PoE switch, which is a network switch that can put power onto its ports, or to a PoE injector sitting between an ordinary switch and the camera. A PoE injector is the cheaper route when you only need to power one or two devices off existing infrastructure.
On the cable, DC power and network data travel together. Before any power flows, the powering equipment and the camera negotiate: the camera signals what class it belongs to, the PoE switch allocates that budget to the port, and only then is the port energised. That negotiation is why a non-PoE device plugged into a PoE port is not damaged.
Once it is up, the camera appears on the network, and you reach it through an NVR network video recorder, through VMS video management software, or through a browser or SDK. For an embedded build, the third route is the usual one, since the host application talks to the camera directly rather than through a recording platform.
That is the whole of how a PoE camera works: negotiate, energize, stream. No part of it is specific to the camera vendor.
PoE Standards: IEEE 802.3af, 802.3at and 802.3bt
The standard sets how much power the port can deliver, and picking the wrong one is the most common specification error in a PoE camera installation.
IEEE 802.3af is the original, and the one most camera modules are built for, delivering roughly 15 W at the port across a 36 to 57 V range. Every Vadzo Innova module in this post is an IEEE 802.3af device, so any af-capable switch or injector powers it.
PoE 802.3at, often called PoE+, roughly doubles that budget. You need PoE 802.3at when the camera carries a heater, a motorised lens or an illuminator rather than for the imaging itself.
PoE 802.3bt goes further again and is aimed at PTZ heads, multi-sensor housings and equipment well beyond a camera board. Specifying PoE 802.3bt for a module that draws af-class power costs money and buys nothing.
The rule is simple. Match the standard to the load, confirm the switch’s total budget rather than its per-port rating, and remember that a switch advertising af on every port may not sustain af on every port at once.
Cable, Distance and the RJ45 Connector
Standard structured cabling is the whole infrastructure. A Cat5e cable carries Gigabit Ethernet and PoE without qualification, and a Cat6 cable does the same with more headroom for noise and for longer channels in electrically busy plant.
PoE camera cable length is governed by the Ethernet limit rather than by the power: 100 metres per run, camera to switch, on either Cat5e cable or Cat6 cable. That covers most buildings outright.
Past that, PoE camera cable length extends with PoE extenders, or with fibre and media converters where the run crosses a yard, a city block or a large plant. The converter is then the thing that needs local power, not the camera.
The RJ45 connector at each end is the same one used everywhere else on your network, so terminations, testers and spares are ordinary stock rather than a camera-specific part. That is worth more on site than it sounds when a connection has to be remade at height.
Why Embedded Systems Choose PoE: Placement and Centralized Power Management
Answer first: PoE is chosen in embedded and industrial builds because it solves deployment problems, not imaging problems.
Single-cable installation is the first of them. One run carries power and the video stream, which simplifies wiring inside machines, along conveyor lines, on robot arms, on traffic poles, and above ceilings. On an AGV, a single cable installation is also one less thing in the harness to chafe through.
Flexible placement follows from it. You put the camera where the optics are best rather than where a socket happens to be: high in a factory cell, on a signal pole for vehicle counting, above shelves for retail analytics, or on a mobile platform where a second cable would be a liability.
Centralized power management is the benefit that shows up after commissioning. Every camera is powered from a switch in the control cabinet, so you can power-cycle one camera remotely and monitor consumption per port. For an industrial PoE camera on a gantry or a pole, centralized power management turns a site visit into a command.
A PoE camera for machine vision gains one more thing: the host does not have to sit near the camera. Defect detection, barcode reading on a fast conveyor, and automated optical inspection can all run on a PC in the cabinet while the industrial PoE camera sits at the line.
The same logic covers a PoE camera for robotics and for AGVs, where a PoE camera for robotics cuts the harness down to one Ethernet run and lets the controller sit in the chassis rather than on the arm.
PoE Camera vs USB Camera: Which Interface Fits Your Build
The PoE camera vs USB camera decision comes down to distance and where the host sits.
A USB module is tied to a few metres of cable and expects a host at the other end of it. That is the right answer on a bench, inside a kiosk, or anywhere the processor is already beside the sensor.
A GigE PoE camera runs to 100 metres, through switches, to a host anywhere on the network, and brings its own power with it. That is the right answer the moment the camera and the host are in different places, or when there are several cameras and one processor.
So PoE camera vs USB camera is rarely about image quality, because the same sensors appear on both. It is about the length of the cable and the cost of putting power at the far end of it.
The second difference is management. An ONVIF PoE camera is discoverable and controllable by any platform that speaks the standard, which makes integration a configuration task. A USB camera is a device on a bus, which is simpler but entirely local.
The Vadzo Innova PoE Camera Range
Every Innova module is a GigE PoE camera running on IEEE 802.3af through a standard RJ45 connector, with ONVIF compliance for network integration. The tables below group them by what they are good at.
Ultra Low Light and HDR PoE Camera Modules
Module | Sensor | Resolution | Notable | Buy Now |
Innova-662CRE | Sony IMX662 STARVIS 2 | 2MP, 1080p and 720p streaming | Ultra-low light | |
Innova-678CRS | Sony IMX678 STARVIS 2 | 8.4MP, 3856 × 2180 (4K) | 110 dB HDR, enhanced NIR, 1/1.8”, 2.0 µm | |
Innova-715CRS | Sony STARVIS IMX715 | 8.46MP, 3864 × 2192 | Multiple Exposure and Digital Overlap HDR, NIR |
These three are the night and mixed-light modules. The 662CRS is the one to reach for when the scene is dark and 1080p is enough, for traffic monitoring, patient monitoring, security and video surveillance, smart parking, and ICU work. The 678CRS adds 4K and 110 dB of dynamic range for high-contrast scenes such as a doorway against daylight. The 715CRS sits between them on resolution and offers two HDR modes rather than one.
All three use S-Mount (M12) optics with an auto IR-cut filter for day and night imaging, carry GPIO for trigger and control signalling, and are configured through Vadzo NXT software, with the NXT SDK exposing exposure, gain, HDR, and network stream control.
Global Shutter PoE Camera Modules
A global shutter PoE camera exposes every pixel at the same instant, so a moving subject is captured without the skew a rolling shutter introduces. If the part moves, the vehicle moves, or the camera itself is on a moving platform, a global shutter PoE camera is a requirement rather than a preference.
High Resolution Rolling Shutter PoE Camera Modules
These are the detailed modules for static or slow scenes where resolution decides the application. The 2020MRS is monochrome, which is the right choice when you are measuring rather than displaying, since every pixel contributes luminance instead of sitting behind a colour filter.
Which PoE Camera Should I Choose?
The question of which PoE camera I should choose answers itself in three steps, and none of them start with resolution.
Start with motion. If anything moves during exposure, you are choosing between the Innova-234CGE and the Innova-234CGA, because no amount of resolution repairs rolling shutter skew.
Then light. If the scene is dark, backlit, or runs day and night, the Sony STARVIS modules are the answer: the 662CRS at 1080p, the 715CRS at 8.46MP, and the 678CRS when you need 4K with 110 dB of HDR.
Then detail. For a static, well-lit scene where fine features decide the outcome, work up through the 521CRS, 821CRS, and 1335CRS, and take the 2020MRS when 20MP monochrome is what the measurement needs.
Power and network are settled either way, since every module is an IEEE 802.3af device on standard cabling.
Frequently Asked Questions
What is a PoE camera?
A PoE camera is a network camera that takes its power and sends its video over one Ethernet cable, so no separate supply is needed where it is mounted. What is PoE camera is is a wiring question rather than an imaging one, because the sensor, lens, and ISP work the same either way. A PoE IP camera plugs into a PoE switch through an RJ45 connector and comes up as an ordinary network device, so a Power over Ethernet camera in an embedded build is simply a camera that needs one cable instead of two. Vadzo's Innova Series delivers this as a board-level embedded vision camera, so what you specify is a PoE camera module you fit inside your own enclosure.
How does a PoE camera work?
Power flows only after a negotiation: the camera signals its class, the switch allocates that budget to the port, and the port then energizes. That is what makes how does a PoE camera safe on a mixed network, since a non-PoE device on a PoE port is not damaged. Power and data then share the cable, and the camera is reachable from an NVR network video recorder, from VMS video management software, or straight from your own host software. A PoE injector does the same job as a switch for one or two devices, and the result either way is a single-cable installation with centralized power management from the cabinet. Every Vadzo Innova module does this as a standard PoE network camera, with no vendor-specific setup.
How much power does a PoE camera need?
A camera module needs about 15 watts, which is what the oldest and most widely used PoE standard delivers. That standard is IEEE 802.3af, and every Vadzo Innova module runs on it across 36 to 57 V, so any af switch or injector will power one. The next level up, PoE 802.3at, supplies roughly 30 watts, and you only need it if the camera carries a heater, a lamp, or a motorized lens. PoE 802.3bt reaches 60 watts and beyond, which suits large PTZ cameras and displays rather than a camera board. One thing to check before you buy a switch: it may be rated for af on every port but unable to run every port at full power at the same time, so look at its total power budget and not just the per-port figure. Choosing af keeps an industrial PoE camera installation on ordinary, inexpensive switches.
How far can a PoE camera be from the switch?
PoE camera cable length is set by the Ethernet limit rather than the power, so it is 100 meters per run from camera to switch on Cat5e cable or Cat6 cable. Past that, you add a PoE extender, or move to fiber with a media converter where the run crosses a yard or a city block. Cat6 is worth the small extra cost in an electrically noisy plant, though Cat5e carries Gigabit and PoE without qualification. Planning a PoE camera installation around the 100-meter figure is cheaper than extending later, and Vadzo Innova modules run on standard structured cabling so your installer works with ordinary stock.
Should I use a PoE camera or a USB camera?
PoE camera vs USB camera is a question about distance and where the host sits, not about image quality, since the same sensors appear on both. Choose USB when the processor is already beside the camera. Choose a GigE PoE camera when the camera and host are in different places, when several cameras feed one processor, or when getting mains power to the mounting point is the expensive part. An ONVIF PoE camera also integrates with management platforms by configuration rather than custom driver work, which matters for a PoE camera for machine vision or a PoE camera for robotics feeding an existing system. If the PoE camera I should choose has to cover moving subjects, a global-shutter PoE camera is the first choice, and Vadzo builds both interfaces so you can evaluate the same sensor on either.
