Industrial interface advantages: why GigE cameras still win

A production hall rarely lets you put the host PC next to the camera: cells sit tens of meters apart, drives and relays share the same power grid, and every camera still needs power and a common time base. GigE Vision was written for exactly that plant, and since the standard appeared in 2006 it has stayed the default camera interface on factory floors. This guide collects the numbers behind the choice: a full Ethernet segment per cable run, PoE power classes from 15.4 W to 90 W over the same cable as the data, roughly 950 Mbit/s of usable bandwidth per link, and PTP synchronization that aligns shutters across cameras without a trigger wire. The final section turns those numbers into a per-camera decision: keep GigE, or step up to 10GigE or CoaXPress.

What the standards guarantee

GigE Vision, introduced in 2006, defines four parts: device discovery for handing out IP addresses, a control protocol over UDP, a stream protocol over UDP, and an XML file describing the camera's features in GenICam form. GenICam and its SFNC feature-naming convention are why an exposure control or a trigger mode reads the same in any compliant library, whichever company built the camera. Two plant-floor consequences follow. Any GigE Vision-compliant software works with any GigE Vision-compliant camera, so a software change does not strand hardware. And the stack runs on standard switches and network cards, so cabling, spares and diagnostics come from the IT shelf instead of a frame grabber catalog. The fine print of that interoperability is in what GigE Vision compatibility guarantees, and the network side of attaching GenICam cameras to a controller is in connecting a GenICam camera over Ethernet.

Cable distance: one full segment, and the other interfaces for scale

Ethernet specifies 100 m per segment on Cat 5e or better, and a switch port starts a fresh segment, so longer paths are built from switch hops. No other mainstream vision interface gets close on a generic cable:

Cat 6a extends the specified bandwidth to 500 MHz, enough for 10 Gbit/s Ethernet over a full segment, and comes unshielded or shielded, with individually shielded pairs for the noisiest cells. RJ45 connectors terminate in the field, so a 60 m run is cut and crimped on site rather than ordered custom. Match the build to the cell: high-flex drag-chain cable where the cable moves, screw-lock RJ45 where it does not. Off-the-shelf camera data cables in the accessories finder run from 3 m to 15 m per cable.

PoE: pick the IEEE class, then size the switch pool

PoE feeds DC power to the camera over the same twisted pairs as the image data, so one cable serves the camera completely. The IEEE classes are power limits at the switch port; what reaches the camera is less, because each class reserves margin for loss along the cable:

An 802.3af port sources 15.4 W so that a camera still receives 12.95 W at the far end of the cable. A GigE area scan camera draws a few watts, so Type 1 covers it with margin: six cameras at 5 W each consume 30 W in total against 6 × 15.4 W = 92.4 W of reserved port capacity. Where a camera's power input lists no PoE, the data cable still runs to a switch and power takes its own line; the PoE support check and alternatives to camera power over Ethernet cover both wirings.

Bandwidth: one camera against one gigabit link

A 1 Gbit/s link moves 1,000 Mbit/s, and packet framing decides how much of that is image. Each 1500-byte packet carries 58 bytes of Ethernet, IP and UDP overhead, so the payload share is 1500/1558 = 96.3%, about 963 Mbit/s. Jumbo frames at 9000 bytes cut the overhead to 9000/9058 = 99.4%, about 994 Mbit/s.

The LS-CMR-0053 is a 12 MP GigE camera that runs 9 fps. At 8 bits per pixel, its demand on the link is:

One camera takes about 90% of the link. Alone that works; it also means no second camera shares that cable. A camera streaming this close to the line rate is exactly where the packet-size setup before acquisition and the horizontal-line symptom of packet loss earn their keep: set jumbo frames end to end, then let packet resend catch what still drops. GigE Vision packets carry image and packet numbers, so the host asks for a missing packet by number and the stream reassembles in order; resend is a supported feature rather than a compliance obligation, which is why it appears in camera feature lists.

All three of these GigE cameras are C-mount, at 6 MP, 12 MP and 20 MP.

Isolation and noise: two quiet advantages

Ethernet links couple through transformers on both ends, so a GigE camera and the host do not share a ground. Ground-potential differences between cabinets, the classic source of loop currents around drives and relays, cannot circulate through the data cable. The physical layer adds a second margin: Gigabit Ethernet signals at 125 MHz, far below the crowded 2.4 GHz ISM band where Wi-Fi, Bluetooth, Zigbee, cordless phones and microwave ovens operate, so the camera link neither receives their interference nor causes it. In cells dense with drives, shielded Cat 6a handles the residual coupling the transformers leave.

Synchronization without trigger cables

PTP, the IEEE 1588 protocol incorporated in GigE Vision 2.0, turns the network into the time base. Devices exchange timestamped packets, an algorithm elects a master clock, and every other device disciplines its clock to it. Two production modes come out of that. Scheduled action commands fire precisely timed software triggers across every camera on the network, so the trigger generator and its wiring disappear. Synchronous free run aligns free-running shutters to sub-microsecond agreement, so several cameras see the same part at effectively the same instant. The PTP master, slave and timestamp check shows how to bring that up, and the trigger-mode comparison from free run to PTP shows where a wired trigger still wins.

When the default answer is wrong

Two situations push you off 1 GigE. The first is one camera that needs more than one link: a payload above roughly 950 Mbit/s. 10GigE multiplies the payload by ten over the same twisted-pair cable at full segment length, and CoaXPress takes the coax route at 130 m per connection into a frame grabber. The second is aggregation: gigabit links belong to single cameras, so a six-camera cell wants six network-card ports, or a 10 Gbit/s uplink per switch serving several cameras. The MV-CH250-25TC-F-NF pairs a 25 MP color global-shutter sensor with a 10GigE link and an F-mount.

For the bandwidth, cabling and switch demands behind that step, the 10GigE interface guide to bandwidth, cables and distance carries the numbers.

The per-camera decision

Work the numbers per camera and the interface chooses itself:

• Cable run within one Ethernet segment, switch hops acceptable: stay on GigE. One longer run: CoaXPress at 130 m, or add a switch.
• Payload below about 900 Mbit/s (10% headroom under the 963 Mbit/s a standard-frame link carries): 1 GigE holds. Above that: 10GigE or CoaXPress.
• Camera power inside a PoE class after cable loss: one cable carries everything. Otherwise: data on Ethernet, power on its own line.
• Synchronization tolerance of tens of microseconds or looser: PTP over the network. Microsecond-class strobe timing: hardware trigger.
• Several cameras near the link limit: one link and one network-card port per camera.

Start from the area scan cameras and filter Interface to GigE in the camera finder; the camera configurator step matches interface, sensor and lens in one pass. Related setup guides sit under the systems topic page, and for a cell that mixes interfaces, contact the applications team with your frame sizes before ordering.