You have a Revolution Pi on the machine and want to attach an industrial camera over GigE PoE, ideally before ordering anything. The combination works. A GigE Vision camera is a standard Ethernet device and the controller is a Linux host with Ethernet ports, so nothing in the pairing is exotic. What decides success is which port you plug into and how the camera is powered, because no Revolution Pi port sources PoE. Here are the bandwidth arithmetic, the power options with their wattages, and the day-one settings that keep the link stable.
Will a GigE Vision camera run on a Revolution Pi?
Yes — any Linux controller with a 1 Gbps Ethernet port and a GenICam-capable client acquires from a GigE Vision camera, because the camera implements the standard and the host simply talks to it over UDP. The camera cannot tell what sits at the far end of the cable; a rack PC, a robot controller and a compact PLC-style controller all look the same to it.
GigE Vision defines discovery, control and streaming, and GenICam describes the camera's feature tree, so one client drives any compliant camera. Your host needs three things: a gigabit port that passes jumbo frames, a client library, and enough CPU to drain frames as they arrive. This class of controller has all three. That is why the decision comes down to bandwidth and power rather than compatibility. Start from the area scan cameras range and filter to the GigE interface; host-side questions like these are collected under machine vision system integration.
Which port on the controller is fast enough?
Use one of the two 1 Gbps RJ45 ports on a Revolution Pi Connect module. The entry Core module's 10/100 Mbps port moves about 12.5 MB/s and caps a 12 MP camera near one frame per second, which rules it out for production rates. Everything downstream — packet size, frame rate, camera choice — assumes this port is gigabit, so settle it first.
The Connect module's interface list shows two RJ45 gigabit ports and two USB-A sockets at USB 3.2 Gen 1. Give the camera a dedicated port and keep the second for the plant network, with the camera on its own subnet so discovery traffic stays off the control side. After cabling, read the negotiated speed on the port and expect 1000 Mbit/s. A link that silently drops to 100 Mbit/s throws packet-size errors and resends; the signature and the fix are in GigE camera packet size error when your link drops below gigabit.
How much bandwidth does the camera need?
Budget about 100 MB/s of image payload on one clean gigabit port. The line rate is 125 MB/s (1000 Mbit/s ÷ 8), and protocol overhead plus resend headroom costs the rest. That budget, not the camera's rated frame rate, sets your ceiling.
Work one camera before ordering. Take the LS-CMR-0053: a 12 MP GigE camera, 1/1.7" rolling shutter, rated 9 fps. Twelve megapixels at 8 bits per pixel is 12 MB a frame, so full rate is 12 MB × 9 fps = 108 MB/s, or 864 Mbit/s. That is below the 125 MB/s line rate but above the 100 MB/s budget: it needs jumbo packets end to end, or you cap the camera at 8 fps and keep margin. The same stream on a 10/100 Mbps port is 12.5 MB/s ÷ 12 MB, about one frame per second.
| Sensor size | Frame at 8-bit mono | Ceiling at 100 MB/s | Ceiling at 12.5 MB/s |
|---|---|---|---|
| 2.5 MP | 2.5 MB | ~40 fps | ~5 fps |
| 6 MP | 6 MB | ~16 fps | ~2 fps |
| 12 MP | 12 MB | ~8 fps | ~1 fps |
| 20 MP | 20 MB | ~5 fps | ~0.6 fps |
Ceilings assume full frame and one byte per pixel, which raw Bayer color also satisfies. Two settings make or break the real number. Set the camera's GigE Vision packet size to the largest value the whole path passes, and enable jumbo frames on the controller port and any switch between — the tuning sequence for a link pinned at one gigabit is in 10GigE camera at only 1 Gbps throughput: fix packet size and NIC setup. When the host cannot drain frames fast enough, the camera reports buffer overruns; the symptom walkthrough is in GigE camera buffer overflows when the host falls behind.
How does the camera get power with no PoE from the controller?
Power it separately: either an auxiliary 12 or 24 V feed into the camera's I/O connector, or a midspan injector that adds 802.3af (about 12 W at the camera) or 802.3at (about 25 W) to the same cable. If the machine already has 12 and 24 V rails, the auxiliary feed is the simpler route — one less box in the cabinet and nothing to configure.
Most industrial GigE cameras accept an auxiliary input in the 12-24 V range on their I/O connector. For that route you want a power and I/O cable that breaks the connector out to flying leads:
- Type
- Power and I/O cables
- Length
- 6-8 m
To keep a single cable to the camera, choose a PoE variant and add a midspan injector on the run. Standard area scan cameras draw well under the 12 W of 802.3af; the 25 W of 802.3at is for onboard lighting, heated sensors or very fast imagers. Settle which power variants a camera family offers before ordering, as Does my camera support PoE: check the port before you buy walks through. If a PoE camera links but stays dark, the injector and its class come first: PoE camera gets link but no power: injector and class checks. On cameras with both PoE and auxiliary inputs, read how the two sources interact before wiring both — the behavior is covered in powering a camera from an auxiliary input with two sources present.
Pick the rail from the power supplies range, which covers enclosed 12, 24 and 48 V units for cameras, lights and controllers.
What software drives the camera on Linux?
Use the camera maker's Linux SDK where it ships an ARM build — industrial SDK lines now publish Linux support for x86-64 and ARM — or an open-source GigE Vision client from the distribution's repositories; both enumerate any GenICam-compliant camera. The library matters less than the pattern you build around it.
Many GigE cameras come up on a link-local 169.254.x.x address, so either move the controller port into that subnet or open the camera by its address — the steps are in opening a GigE camera on a link-local address from Linux. When ping answers but the client lists no devices, the transport layer and its permissions are the culprit, covered in ping works, zero cameras: the GigE transport layer is not loaded.
For Node-RED, keep the firehose out of the flow engine. Run acquisition in a small native service that grabs, processes and publishes results over MQTT or HTTP, and writes a snapshot JPEG for the dashboard. Node-RED orchestrates the logic around it the same way it runs a barcode scanner behind Node-RED on a Linux controller.
Which camera suits one gigabit port?
Pick a 2.5 to 6 MP mono GigE camera for presence, position and code reading on this class of host: those sensors land at 16 to 40 fps on a single port, which covers typical cycle times with margin. Buy resolution for the smallest feature you must measure, not for the number on the box.
Three C-mount GigE cameras that bracket the useful range on this host:
| Specification | MV-CU020-90GC | LS-CMR-0053 | MV-CS200-10GC |
|---|---|---|---|
| Sensor type | CMOS, global shutter | CMOS | CMOS, rolling shutter |
| Sensor model | GMAX4002 | IMX 226 | Sony® IMX183 |
| Pixel size | 4 μm × 4 μm | 1.85 μm x 1.85 μm | 2.4 μm × 2.4 μm |
| Sensor size | 1/1.7" | 1/1.7" | 1" |
| Resolution | 2048 × 1200 | 4000 px x 3000 px | 5472 × 3648 |
| Max. frame rate | 49 fps @ 2048 × 1200 Bayer GB 8 | 9 fps | 5.9 fps @ 5472 × 3648 |
| Dynamic range | 66.9 dB | 60.0 dB | 65.5 dB |
| SNR | 40.8 dB | >38.5 dB | 41.5 dB |
| Gain | 0 dB to 11.1 dB | – | 0 dB to 24 dB |
| Exposure time | 4 μs to 10 sec | – | 46 μs to 2.5 sec |
| Exposure mode | Off/Once/Continuous exposure mode | – | Off/Once/Continuous exposure auto, supports Timed and Trigger Width exposure mode, and Rolling and Global Reset sensor shutter mode |
| Pixel format | Bayer GB 8/10/10Packed/12/12Packed | – | Mono 8/10/12, Bayer GB 8/10/10p/12/12p, YUV422Packed, YUV422_YUYV_Packed, RGB 8, BGR 8 |
| Price | $309.00 | $560.00 | $739.00 |
Values as printed in each product's data sheet; open a part for its drawing and full specifications.
The MV-CU020-90GC is a 2.5 MP color GigE camera, 1/1.7" sensor, global shutter, C-mount. The LS-CMR-0053 is a 12 MP mono GigE camera with a 1/1.7" rolling shutter. The MV-CS200-10GC is a 20 MP color GigE camera on a 1" sensor, C-mount. At 20 MB per 8-bit frame, the largest of the three tops out near 5 fps on this port — right for a stationary scene, wrong for a fast line. Filter further in the camera finder, or start at the camera step of the system configurator.
What should you check before ordering?
Confirm five things — the port, the power variant, the cable, the packet path and the frame budget — in that order, because any one of them kills the link on its own. Ten minutes with the camera's data sheet and this list settles the order.
- Port speed. Two 1 Gbps RJ45 ports on the Connect module; 10/100 Mbps only on the entry Core. Read the negotiated speed after cabling, not from the brochure.
- Power variant. A PoE variant plus an 802.3af injector, or any variant plus the 12/24 V auxiliary feed. The model number usually encodes the difference, as GigE PoE vs USB3 camera variants: pick by model number shows.
- Cable. Cat5e or better, industrial jacket, locking RJ45 against vibration, copper run within 100 m.
- Packet path. Jumbo frames enabled on the controller port and every switch between; camera packet size set to match.
- Frame budget. Pixels × bytes × fps from your scene, against the 100 MB/s per port above.
On the cable item, the baseline from the camera cables range is an industrial data cable with locking studs at the jacks:
- Type
- Camera data cables
- Length
- 15 m
Cable categories and distance rules for camera Ethernet are in 5GBASE-T camera interface: bandwidth, cables and distance.
When is this controller the wrong host?
Step up to a vision controller or an industrial PC when you need 10GigE cameras, more cameras than there are ports, line-scan rates, or heavy per-frame processing: a gigabit port tops out near 100 MB/s and this host gives you two of them.
Two ports also means two cameras, one each, if the processor keeps up — the way to budget that is in multiple GigE cameras on one computer: bandwidth and CPU budget. The two USB 3.2 Gen 1 sockets are a second door: a USB3 Vision camera there skips the Ethernet math, though you give up the 100 m reach and should power it externally rather than from the socket. When the job grows past 20 MP at speed or into 3D sensing, send the cycle time and the smallest feature you must see through the contact page and the applications team will size camera, cable, power and host together — free expert support comes with every order.
Questions
How far can the camera sit from the controller on one copper run?
Up to 100 m on Cat5e or better — that is the 1000BASE-T limit over copper, not a camera limit. Keep one continuous run where you can; every switch you insert must also pass your jumbo packets or the effective throughput drops. Past 100 m, use fiber media converters at both ends to keep the full gigabit rate.
Which injector rating does a PoE camera need?
802.3af, which delivers about 12 W at the camera, covers standard area scan cameras with room to spare. Move to 802.3at and its roughly 25 W only for builds with onboard lighting, sensor heating or very high frame rates. The injector sits inline between controller and camera; the controller never sees or participates in the power negotiation.
How do you raise the frame rate without a faster port?
Cut pixels, not the link. Halve the region of interest and the fps ceiling doubles at the same data rate; 2 × 2 binning leaves a quarter of the pixels and buys about four times the rate on sensors that support it. Stream raw Bayer rather than packed RGB when your tool can debayer, since packed RGB costs more bytes per pixel.
Can Node-RED display the camera image directly?
Not the full stream, and it should not. A 12 MP camera at 9 fps is 108 MB/s of pixels; route that through a native acquisition service and let Node-RED see only the outputs — results over MQTT and a snapshot JPEG over HTTP, megabyte-scale traffic once a second that any dashboard renders comfortably.
Will the camera work on the 10/100 Mbps module at all?
It links, enumerates and delivers stills: 100 Mbit/s is 12.5 MB/s, so a 6 MP frame takes roughly half a second and a 12 MP frame about one second to cross. That suits an occasional manual capture, not a cycle-time inspection. Keep the packet size small on that link, and plan the gigabit-port module for anything in production.