MV-GS100 Frame Grabbers

XoFLink · 2 ports · Original

mv-gs1002f

Vision Components

The frame grabber must match the camera protocol, number of camera links, host slot and sustained data load. The MV-GS100 family contains five supplied combinations for 10GigE or XoFLink cameras, two or four ports, and original or V3.0 board generations. PCIe configuration, memory, operating-system support, power, connector layout and bandwidth differ by exact SKU.

Beschikbare configuraties

mv-gs1002f-v3-0 — XoFLink · 2 ports · V3.0
mv-gs1004f-v3-0 — XoFLink · 4 ports · V3.0
mv-gs1002f — XoFLink · 2 ports · Original
mv-gs1004f — XoFLink · 4 ports · Original
mv-gs1004 — 10GigE · 4 ports · Original

Aantal

Select variant

Camera protocol

Camera ports

Board generation

SKU: mv-gs1002f

Selection guide

Match the frame grabber to the camera links and host PC

A frame grabber can become the bottleneck when its camera protocol, port count, PCIe connection or sustained throughput does not match the acquisition task. Start with the cameras and simultaneous data load. Then check whether the host has the required slot, operating-system support, cooling and connector clearance.

Calculate the complete data path

Add the expected data rate of every simultaneously active camera, including the selected pixel format, line or frame rate and protocol overhead. Compare that result with the documented sustained board bandwidth, the host slot and the processing and storage path. A link speed by itself is not an acceptance criterion.

Camera protocol

MV-GS1004 is the supplied 10GigE option. The F models use XoFLink. Select the protocol implemented by the exact cameras; these connections are not interchangeable through a selector setting.

Two or four ports

Choose enough physical ports for the cameras that must acquire at the same time. Also verify the total board bandwidth, because four connected cameras do not guarantee that every camera can run at its maximum data rate simultaneously.

Original or V3.0 board

The generations differ in PCIe configuration, on-board memory, power consumption, connector details and operating-system support. Treat V3.0 as a separate host-integration choice and check the exact SKU specifications.

PCIe lanes, memory, connector layout, power consumption, operating-system support and throughput remain SKU specifications. MV-GS1004 currently has no detailed imported specification set, so confirm its datasheet during selection.

Prove sustained acquisition in the final host

Acceptance should use the selected cameras, transceivers, cables, host PC, drivers and application settings.

Acquire from every required camera at the intended pixel format and line or frame rate for a representative production run.
Record dropped data, board and host utilisation, processing latency, storage load and recovery after a link interruption.
Verify connector retention, cable routing, airflow and component temperatures in the closed machine or cabinet.
Restart the host and cameras and confirm deterministic recovery of enumeration, triggering and acquisition.

Inputs for the business case

Compare complete acquisition paths rather than card prices alone.

Frame grabber, transceivers, cables, host slot, cooling and storage costs.
Engineering time for drivers, triggering, data handling, diagnostics and commissioning.
Downtime risk, spare-card strategy, cable replacement, maintenance access and recovery time.

Discuss an MV-GS100 configuration

Specifications

Brand	Hikrobot
Camera-link speed	10 Gbps per port; 20 Gbps total
Supported camera quantity	Up to 2
Supported camera type	XoF fibre-port line-scan camera
Category	Frame grabber
Certification	CE, KC, RoHS
Client software	MVS
Connector	Female header
Camera interface	2LC fibre port
Delivery bandwidth	4000 MB/s maximum; 3200 MB/s sustained
Dimensions	181 mm × 126.3 mm × 21.6 mm (7.1" × 5.0" × 0.9")
Humidity	10% RH to 95% RH (no condensation)
I/O type	24 I/O connectors: 4 opto-isolated inputs (4.5 to 28 VDC), 4 opto-isolated outputs (4.5 to 28 VDC), 4 RX422 inputs, 4 TX422 outputs, 4 TTL inputs and 4 TTL outputs
Status indicator	1
Host interface	PCI-E gen2 × 8
On-board memory	2 GB DDR3L
Operating system	Windows 7/10/11
Board generation	Original
Camera ports	2 ports
Camera protocol	XoFLink
Power consumption	Typ. 20 W
Series	MV-GS100 frame grabbers
SFP+ modules	SFP+ × 2
Camera protocol	XoFLink
Camera streams	2
Stream indicators	2 pairs
Temperature	Operating: 0 °C to 60 °C (32 °F to 140 °F). Storage: –20 °C to 70 °C (–4 °F to 158 °F)

MV-GS100 selection

Frequently asked questions

Can a 10GigE camera be connected to an XoFLink model?

No. Select MV-GS1004 for the supplied 10GigE configuration. The F models use XoFLink. The camera and frame grabber must implement the same protocol and matching optical connection.

When is a four-port card required?

Use a four-port model when three or four cameras must be connected to one card, or when the installation reserves additional physical ports. Confirm the combined sustained data rate; port count alone does not define total throughput.

What changes with the V3.0 board generation?

The documented XoFLink V3.0 models use a different PCIe configuration, DDR4 memory, lower typical power consumption and broader listed operating-system support than the original XoFLink models. Connector details also differ. Check the exact SKU table before specifying the host.

How should required bandwidth be calculated?

Calculate the output of each camera from image width, image or line rate and transmitted bits per pixel. Add simultaneously active cameras and protocol overhead. Compare the result with the documented sustained card bandwidth and with the host, processing and storage limits.

Is the PCIe slot interchangeable between generations?

Do not assume this. The imported specifications list PCI-E Gen2 ×8 for the original XoFLink models and PCI-E Gen3 ×4 for the V3.0 XoFLink models. Verify slot mechanics, available lanes, BIOS behaviour and sustained host bandwidth in the selected PC.

Which items should be included in an acceptance test?

Use the final cameras, transceivers, cables, host, drivers, trigger setup, processing and storage path. Run all required streams together and record dropped data, latency, temperatures, utilisation and recovery after restart or a link interruption.