Dedicated ports
Each camera has its own link; the host processes the combined traffic.
Knowledge · GigE cameras
Each camera works on its own, but images go missing when they run together. A shared link or the PC may be unable to keep up. Compare dedicated network ports with a switch, then check addressing, power and timing across the complete system.
Dedicated ports
Each camera has its own link; the host processes the combined traffic.
Through a switch
The uplink must carry the combined camera traffic.
Power
A compatible PoE switch or vision PC can power cameras directly.

A dedicated Ethernet port keeps each camera link separate. A switch can suit cameras grouped together at a distance from the PC. The main selection points are below.
| Choice | Dedicated PC ports | Switch |
|---|---|---|
| Data path | Each camera has its own link; resources inside the PC may still be shared. | The PC uplink carries the combined camera streams. |
| Cabling | Each camera cable runs to the PC. | Cameras connect locally; an uplink runs to the PC. |
| Selection check | Are enough ports and sufficient aggregate card capacity available? | Can the switch support the combined data rate, bursts and PoE load? |
For either layout, check the network card’s aggregate capacity and its PCIe connection inside the PC. A switch also needs sufficient switching capacity and buffering when cameras transmit together.
Two 1 Gbit/s camera-facing ports feeding a 1 Gbit/s uplink still share a 1 Gbit/s path to the PC. A faster uplink can help when supported by the switch, host adapter and cabling. Each camera remains limited by its own interface.
For separate direct links, use a different subnet for each adapter-camera pair. For example, PC port A could use 192.168.10.1 with camera A at 192.168.10.2; port B could use 192.168.20.1 with camera B at 192.168.20.2. All use mask 255.255.255.0 in this example. Check for existing subnet use before applying it.
Cameras sharing a switch and the connected PC adapter can use distinct addresses in the same subnet. Record serial number, camera name, port and IP address together. The application must associate each image with the correct inspection point after a restart, regardless of device-discovery order.
For PoE, check per-port power and the combined demand against the selected switch or card's specifications and operating conditions. Some cards require an auxiliary power connection to supply their PoE ports. Follow the documentation for the exact hardware variant.
For each camera, multiply payload bytes per image by the highest required acquisition rate. Add streams wherever they share a connection, then allow for protocol traffic and retransmissions. Include additional acquisitions required during recipe changes or repeat measurements.
The bandwidth example uses 2448 × 2048 Mono8 images at 20 frames per second, producing about 100.27 MB/s per camera. Two streams require about 200.54 MB/s before overhead. A shared 1 Gbit/s uplink has a nominal ceiling of 125 MB/s and cannot sustain this load. Dedicated 1 Gbit/s ports still require individual-link and whole-host testing to confirm usable capacity and processing deadlines.
A larger switch buffer can absorb temporary bursts. If the sustained input rate exceeds the output rate, it will continue filling. The long-term remedy is more capacity or less traffic.
Some measurements require cameras to expose the same moving product at nearly the same instant. Select a suitable trigger method and verify the actual exposure timing. Images arriving close together on the PC do not necessarily represent simultaneous acquisitions.
Where supported, spread image transfer using an inter-packet delay or a delayed start of frame transmission. Check available features and their time units for the camera. Spreading traffic increases transfer time and must still meet the inspection-result deadline.
Precision Time Protocol (PTP) can align clocks on supported devices. Enabling PTP alone does not make exposures simultaneous: a suitable acquisition mechanism, such as a supported scheduled trigger, and timing verification are also needed. Hardware triggers likewise require checks of signal levels, delay and variation.
Validate each camera independently at its production settings. Then run all cameras together with processing, storage and machine communication enabled. Include the case in which all cameras transmit at once.
For each camera, count requested triggers, complete received images and results delivered before the deadline. Record retransmissions and buffer errors where available. A mismatch can originate in triggering, transfer or processing, so retain timestamps and error messages to distinguish these stages.
Test a camera fault, cable interruption and power cycle. Define whether the machine stops, rejects the affected product or takes another controlled action. After restart, camera identity must still match the inspection point. Verify that a delayed image cannot be mistaken for the next product's acquisition.
If failures occur only with the full camera set, examine the shared uplink, buffers and host load. If one connection fails independently, focus on its cable, port and camera configuration. Change one item at a time and repeat the same test.
Compare extra PC ports with the cost of a switch and faster uplink, including cable routes, power and available space. A central switch may simplify wiring, but a switch failure can affect several inspection points together. Separate links require more host ports and can make connection faults easier to isolate.
Include commissioning, spare parts and recovery work in the business case. Use current downtime and manual inspection effort as inputs, and measure fault handling during the trial. This supports a comparison of complete installation costs.
Consult the GigE manual for power, network configuration, packet size, packet interval and pixel format. Available features depend on the camera model and software release. Check the exact model manual for timing features.
A practical benefit of VC-series industrial PCs is built-in PoE on supported models. One Ethernet cable carries image data and powers the camera, removing the need for a separate PoE injector. Choose the model and power budget to match your cameras.

Industrial vision PC with PoE options for multiple cameras. Compare network ports and PC configurations by variant.
Four PoE ports listed for MV-VC5525-256G70-2T and MV-VC5715-256G70-2T.

Vision controller with four GigE ports. Select a VC2143 variant for integrated PoE; VC2140 variants do not include PoE.
VC2143: 20 W total PoE loading according to the product specification.
Send a connection diagram and the settings for each camera. State which exposures must coincide and when the machine needs the result so we can review network capacity and the test plan.
Discuss your camera setup