Machine vision slip rings for GigE and USB3 cameras.
Define the camera-to-host path before choosing a rotary assembly. Bring image workload, camera power, both cable ends and motion into one review brief for your rotating inspection system.
For OEM and vision integrator selection. Camera-standard interoperability, requested throughput and rotary performance require configuration-specific evidence.
Supplier reference image; configuration subject to confirmation. Family reference only; not a drawing for an NRD request code.
TRACE THE COMPLETE CHAIN
Two cameras do not always mean two rotary data paths.
A switch or hub on the rotating side can share an upstream path; direct camera connections can require independent paths. Specify camera count and crossing-path count separately, including every host controller, switch, hub or active conversion. Shared bandwidth, power, triggering and device support need their own review.
Illustrative chain only. The arrows do not specify pinouts, directionality, internal construction or approved switch/hub placement. Record the actual architecture for review.
KEEP THE CAMERA TRANSPORT AND PAYLOAD DISTINCT
Choose the required acquisition path, then review its evidence.
Integration question
GigE Vision / Ethernet camera
USB3 Vision / USB camera
Camera and host identity
Camera model, standard version, requested Ethernet rate, NIC/switch and driver. GigE Vision is not universally limited to 1 Gb/s or one transport architecture.
Camera model, standard version, negotiated USB mode, host controller/driver and any hubs. USB connector shape alone does not establish a mode or camera-standard compliance.
Image workload
Resolution, pixel format/packing, frame rate, payload and burst/trigger pattern. Include shared-link traffic and camera throughput settings.
The same image-mode inputs plus shared controller/hub traffic. A nominal USB signaling rate is not guaranteed image payload throughput.
Power and both ends
PSE/PD type/class and device load if PoE is requested; otherwise separate camera power. Identify both mating connectors, leads and shield/bonding requirements.
Bus-power, external power or separately reviewed USB-C PD requirements. Identify host/device roles, both connector/locking geometries and leads.
Acceptance evidence
Actual acquisition results, link/camera diagnostics and relevant transport counters. Record configuration, duration and motion/load.
Actual acquisition results, failed/incomplete buffers, resets or missed frames as exposed by the camera SDK. Include controller, cable and motion/load conditions.
Interface standards describe camera ecosystems; they do not certify a proposed NRD assembly. A cable-category report, USB plug-in check and sustained rotating camera acquisition are different evidence.
Supplier reference image; configuration subject to confirmation. Family reference only; not a drawing for an NRD request code.
LIGHTING AND TRIGGERING ARE PART OF THE MACHINE
Keep frame timing and auxiliary power in the same brief.
State software or hardware triggering, synchronization needs, exposure/strobe timing and whether I/O crosses the rotary boundary. For camera lighting, motors and sensors, list each circuit group, voltage, continuous/peak load and return/PE arrangement separately.
PoE, USB bus power and external lighting power are different requests. A requested power mode does not establish available power at the camera. Review start-up loads, voltage drop, grounding and the actual powered-motion test together with the signal path.
Record camera quantities separately from independent data paths. Blank optional inputs remain open review items. These fields prepare a request; they do not calculate throughput or select an approved assembly.
Changing transport excludes inactive protocol details from exports. Its draft is retained if you switch back. Common requirements and typed contact information stay intact.
Technical exports contain the brief. Use the form below to include company, quantity and application. For long requests, use the online form or attach the downloaded text; email clients may limit prefilled text.
CONFIGURE / MACHINE VISION / APPLICATION BRIEF
Send the complete engineering request.
Send the operating conditions that determine a useful quote. Connector, cable and test scope selections travel with your request.
AGREE THE SAMPLE TEST BEFORE ORDERING
Follow one camera configuration from still capture to powered rotation.
1 / Record the baseline
Identify camera, host/controller, firmware/SDK, exact image mode, topology, cable route and power. Establish acquisition behavior in the agreed stationary setup; this is not yet a rotary acceptance result.
2 / Exercise representative motion
Repeat acquisition with the selected assembly, intended speed/profile and energized lighting/drive loads. Log transport/device counters, incomplete frames, resets and trigger behavior over the agreed duration.
3 / Retain configuration and limits
Record actual settings, observed outcomes, test equipment and drawing revisions. Agree acceptance thresholds with the system owner; do not turn a brief or a clean short demonstration into a universal no-loss guarantee.
Collect evidence that separates transport faults from host bottlenecks.
Observed behavior
Information to capture
Review direction
Missed or incomplete images
Image mode, shared traffic, SDK/buffer diagnostics and host configuration.
Check acquisition/processing and link conditions; an image fault alone does not identify the rotary section as the cause.
Faults appear with rotation or drive/lighting loads
Motion/load/time correlation, cabling/shields, power and comparable stationary observations.
Review connection retention, signal/power integrity and bonding under that actual operating condition.
A lower image mode works but the target mode fails
Both exact modes, requested line rate, camera throughput settings and complete cable/controller path.
Investigate the full bandwidth and power budget; do not infer qualification from the lower mode.
Resolve the topology before asking for a replacement part.
Can two rotating cameras share one slip ring data path?
Possibly, with an explicitly designed network or USB topology. Camera count is not the number of independent paths crossing the rotary interface. State the switch/hub location, upstream link, host and power. Shared throughput, device support, triggering and fault behavior all need review.
Is a GigE Vision camera always a 1000Base-T camera?
No. State the camera model, standard version and actual requested interface/rate. GigE Vision has evolved across faster Ethernet and different transport architectures. A standard name alone is not a selected rotary channel specification.
Can a slip ring with a USB connector be called USB3 Vision compliant?
The connector alone does not establish camera-standard compliance or end-to-end interoperability. Identify the camera, host/software and required USB mode. Request evidence for the intended acquisition path rather than treating a connector or family name as certification.
Should I calculate the link from megapixels and frame rate alone?
Include the actual pixel format, packing, ROI, payload and acquisition/burst pattern, plus protocol overhead and shared traffic. Prefer camera documentation/settings and measured system data over an unqualified megapixel estimate. This brief records the workload; it does not calculate approved throughput.
Does PoE or USB bus power remove the need to specify lighting power?
Camera power and external illumination or motor circuits are separate requirements. Record each load, voltage, peak/start-up condition and return arrangement. The complete power path must be checked; selecting a power mode does not approve a lighting load.
Can I reuse a cable-length limit quoted for a standard camera cable?
A plain-cable limit or demonstration is not a qualified rotary channel limit. Include both leads, connectors, adapters, switches/hubs and the rotary section. Camera/controller compatibility, requested mode, flex duty and power remain part of the full review.
Which SDK counters prove that the rotary assembly passed?
No single counter establishes that. SDK definitions and availability vary by camera, interface and version. Retain relevant frame/buffer/link diagnostics with hardware/settings, motion/load, duration and agreed acceptance criteria. Host starvation and processing limitations can also create incomplete acquisition.
What is needed to review an installed Moog, Kübler or other original?
Send the complete installed suffix, controlled drawing/pinout, actual camera/host route and known mechanical or electrical differences. Use the replacement library alongside this application brief. A similar diameter or nominal data rate does not establish a compatible replacement.
Primary references support interface and diagnostic distinctions. They do not certify or endorse an NRD product. This page reports a proposed selection/test workflow, not a measured installation or customer case study.
