Stereo Wire Crimping and Harness Assembly Data

It is first-person video of a person doing wire and harness work at an assembly bench: crimping a terminal onto a wire, or routing conductors to a form board and clipping them. It is recorded from their own point of view with two calibrated cameras, with hand pose and sensor streams alongside. Stereo describes the capture, and MCAP describes the container. They are separate choices.

The site does not state that stereo is already running on these rows. The catalog lists a multiview rig with handheld grippers as their capture setup, so a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The data is human capture by paid, consented contributors, not robot or teleoperation data, so using it for a specific robot still needs your own retargeting step. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Two, both in the Precision Assembly Bench (electronics) environment of the Manufacturing & Workshops sector. "Crimp connector" is described as "Crimp a terminal onto a wire." and rated Hard. "Route + clip harness" is described as "Route conductors to a form board and clip." and rated Medium. The catalog describes the environment as "Assembly bench: PCB/electronics, fasteners, fixtures, solder/crimp tools, small parts".

Both are listed as Available on request. The catalog does not define that status further, and the site says nothing about delivered hours or delivered stereo footage for either row, so this page claims none. The rows name a terminal, a wire, conductors, a form board and clips, and no tool brand. The first table below reproduces the rows as the catalog states them.

The egocentric cable routing and wiring page lists fifteen cable and wiring rows, including both of these, as first-person catalog capture with ten streams, and stereo and MCAP are not its subject. The stereo soldering and circuit board assembly page covers "Circuit board assembly" and "Component soldering", both Available on request, and says it does not cover the housing and harness rows. The stereo electrical installation page covers five electrical rows in four environments, and neither crimp nor harness is among them. The stereo consumer goods assembly page covers three Plastic & Light-Assembly Manufacturer rows, all Ready to deploy, and neither row is among them. The egocentric precision assembly bench page covers all fifteen bench rows, all Available on request, as egocentric catalog capture.

This page is the stereo and MCAP treatment of the two wire and harness rows only, with its own stream map and failure modes. The second table below sets the pages side by side.

The catalog lists "Multiview rig + handheld grippers" for both rows, as it does for the whole Precision Assembly Bench environment. The site does not state a head-mounted stereo setup for these rows. Stereo applies through the site general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot.

The site states that handheld grippers are listed so demonstrations map onto a robot end effector, and states no accuracy for that mapping. A multiview rig adds synchronized third-person angles, and wrist cameras give a closer view of the hands, when the spec asks for them. Whether a stereo pair is worn, mounted or combined with the grippers on these rows is Not stated.

Harness and crimp work is close and cluttered. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so a terminal, the wire it goes onto, the form board and the hand around them share a frame. The site gives no depth accuracy figure for these rows and no label for crimp quality, routing, clip placement or success, so what a buyer does with that depth is their pipeline question.

A stereo pair adds depth, not a verdict. The site states 1080p per eye for dataset 06, and whether that suffices to see a terminal, a conductor strand or a clip at working distance is Not stated, so a spec should check it on a Spec Pilot. The site also states that Firsthand does not capture at a customer own facility.

Both rows are two-handed: one hand holds the wire, the terminal or the conductor in place while the other works the crimp tool or presses the conductor into a clip. The site states 3D hand pose of 21 joints per hand with a per-joint visibility flag, plus contact and grasp events that mark when fingers meet an object, so each hand has its own record.

The site does not say whether a terminal, a wire, a conductor, a clip, the form board or the crimp tool counts as the object in a contact event, so settle what an event means for your task in the spec. Action segments carry a verb and a noun per step as the skill spec defines them, so a spec that wants strip, insert, crimp, route and clip separated has to name them.

The crimp tool, the fingers and a clip can cover the exact spot being worked, and the head camera sits close to the work, as close as a robot onboard camera would. The site states that fingers disappear behind panels and tools, which is why each hand joint carries a visibility flag, and that small parts can fall below a depth sensor reliable floor: hand pose stays valid at that range, and metric depth on sub-centimetre parts is flagged rather than interpolated.

Whether a terminal, a conductor strand or a clip counts as such a part is Not stated, and the site gives no minimum object size, no wire gauge and no depth figure at working distance. The site also states that depth degrades on wet and reflective surfaces and ships per-frame confidence maps so a buyer can mask rather than guess. How depth behaves on a metal terminal, an insulated wire or a thin conductor in particular is Not stated, so thin-wire visibility is a question for a Spec Pilot.

The environment is described as a bench with small parts, fasteners, fixtures and solder and crimp tools, and the egocentric precision assembly bench page lists connector types, wire gauges and component types as Not stated. The site states no label for terminal type, no size or count of parts per episode and no wire gauge.

What it does state is how small parts are treated in depth: hand pose stays valid and metric depth on sub-centimetre parts is flagged rather than interpolated. Terminal, connector and wire types, tool models and form board layouts are Not stated and belong in the written spec.

Tool contact is stated only as contact events that mark when a hand meets an object, and as action segments with a verb and a noun. The site states no force, torque, crimp force or tactile reading in standard capture; a separate glove tier records a tactile glove signal, and its use on this bench is Not stated.

The catalog rows state no tool-safety rule, and this page states none. Crimp tool models, pull-force values and crimp specifications are Not stated, so any requirement belongs in the written spec.

MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression.

Reader and writer libraries exist for C++, Go, Python, Rust, Swift and TypeScript, and the mcap CLI can inspect, merge and split files. The foxglove/mcap repository is MIT-licensed; that is the MCAP project licence, not the licence of a Firsthand delivery. The MCAP hub page and the glossary entry cover the format in full.

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For these rows the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments, per-frame instance masks and one task instruction per episode elsewhere. What it does not state is which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate.

No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch. The fourth table below sets each stream beside what the site states about it.

Hand occlusion is the first risk. The crimp tool, a clip or the fingers cover the spot being worked, which is why each hand joint carries a visibility flag, and a spec can ask for wrist views or a second angle. An episode is rejected when the manipulated object is out of frame for more than 15 percent of it. For wire and harness work the spec decides what that object is: the terminal, the wire, the conductor, the clip or the form board.

Invalid depth near the work is the second. An episode is rejected when more than 35 percent of depth pixels in the manipulation region are invalid. Calibration is measured at the start and end of every session under a 0.28 px RMS gate, and an episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, for an undocumented bystander or for a mismatch against the named skill spec. A reject log ships with every batch.

Whether a crimp or a clip passed or failed is Not stated: the site lists no success, defect or quality label. Terminal and tool brands, wire gauges, pull-force values, cycle times, tolerances, factory or customer names, and IPC, UL or other certifications are Not stated and are not claimed here. The fifth table below lists the failure modes beside what the site states.

For every delivered episode the site states that faces, plates and screens are blurred irreversibly, that a reviewer confirms the result before anything ships, and that footage that cannot be de-identified is discarded. The anonymization record ships with the data, and an undocumented bystander is a stated reject criterion.

The site does not state a rule specific to a factory or a bench, or to branded parts or packaging, so this page makes no such claim. Settle it in the spec.

The October 2026 off-the-shelf catalog lists ~324,800 hours across 18 datasets, of which stereo is ~64,800 hours across 9 datasets. No listed dataset names wire crimping, connector crimping or harness routing, and the site does not state that any contains either row.

Stereo wire crimping and harness assembly in MCAP is therefore custom collection, not an off-the-shelf purchase: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; where it is thin, turnaround runs three to four weeks. The site does not say which speed applies to these rows, so the timeline is quoted against your spec. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Describe the steps and where each starts and ends: preparing the wire, crimping a terminal onto it, routing the conductors to the form board and clipping them. Say whether an episode covers one crimp, one run of conductors or a whole harness, since the site does not set an episode length, and name the variation your pipeline is missing. Then name the streams you want in the file, the topic naming and message encoding your reader expects, whether calibration ships inside the file or beside it, and whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset.

Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. The sixth table below shows what each spec element decides.