Egocentric Car Battery Replacement Data

It is real-world, first-person video of a person testing and replacing a car battery: reading voltage with a multimeter, unbolting the old battery, fitting the new one and cleaning and tightening the terminals. It is recorded from the operator viewpoint, with 3D hand pose, depth, contact events and frame-accurate action segments aligned on one hardware clock. The task is the one the site’s task catalog lists in three rows.

The data is human capture by paid, consented contributors, not robot or teleoperation data. This page is about car battery replacement robot training data in the sense of what a policy can learn from watching skilled service work, and it makes no claim that any robot has been trained on it.

Three, all in the Auto Service Center & Tire Shop environment of the Automotive & Transport sector, all rated Medium. The first is named "Test and replace a car battery using a multimeter and socket set": "Read voltage with a multimeter, unbolt the old battery, fit the new one and tighten terminals." Its status is Active collection. The second is named "Test, remove, and replace car batteries and terminals using a wrench and a multimeter.", and its catalog description reads "Automotive repair shop with vehicle lifts, tool chests, and dedicated service bays." Its status is Active collection. The third is "Battery Test & Replacement": "Test the battery with a multimeter, disconnect and swap it and clean the terminals." Its status is Ready to deploy.

All three list a head-mounted phone or a multiview rig as the capture setup. The site says nothing further about what Active collection or Ready to deploy means in volume or hours, so this page claims no completed collection and no delivered hours. It names only the tools and items that appear in the rows: a multimeter, a socket set, a wrench, a battery and terminals. The first table below reproduces the rows as the catalog states them.

The egocentric vehicle maintenance page covers thirteen rows across oil and fluid, filter, battery, brake and diagnostics work. The three battery rows are one of its five groups, listed in a table alongside the rest. The stereo oil and fluid change page, the stereo brake pad and rotor service page and the egocentric tire and wheel page each take other rows of the same environment, and none lists a battery row.

This page gives the three battery rows their own treatment: the steps in order, how the capture works around a battery, what each episode carries and where the failure modes are. The comparison table below sets the pages side by side.

Testing comes first: the rows name a multimeter and describe reading voltage. The data needs to show the meter, the probes and the point of contact, and a spec decides whether reading the meter is a step of its own. Disconnecting and unbolting follow, using a socket set or a wrench as the rows name them, where the hand and the tool matter more than the wide scene. The swap, removing the old battery and fitting the new one, is the largest hand motion in the chain.

Terminal work closes the sequence: the Ready to deploy row says to clean the terminals and the first row says to tighten them. The site notes that terminals are tightened after the swap, so order matters. The site states no voltage figure, battery type or size for any row, so what the meter reads and which battery is swapped are agreed in the spec rather than assumed.

Across all steps, action segments carry the start and end of each one as the skill spec defines them. A spec can ask for the whole job in one episode or isolate a single step, and the segment boundaries are what let a policy learn the order.

A battery job is close-range work: a probe on a terminal, a socket on a bolt, two hands lifting a battery. A head-mounted camera keeps the whole reach in frame from the viewpoint a manipulation policy will see from, and two wrist-mounted cameras give a closer view of the hands and the fastener.

A multiview rig adds synchronized third-person angles when the spec asks for them. That is useful in a service bay, where the vehicle itself or the battery can hide the hands from the head view. Which angles a battery order uses is set in the spec. The site does not state where the battery sits on the vehicle, so this page does not describe the vehicle layout.

The catalog lists one capture setup for all three rows: a head-mounted phone recording the first-person view of real work on site, with a multiview rig adding synchronized third-person angles when the spec asks for them. The wider stack the site documents for hard environments is a global-shutter 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras and 200 Hz 6-DoF IMUs. Which of those a battery order uses is Not stated, and the third table below sets what is stated beside what is not.

Streams are hardware-triggered onto one clock, synced under 2 ms. Depth is aligned to video, and distance-invalid pixels beyond the sensor reliable range are flagged rather than interpolated. The site does not state which shop, dealership or vehicle a collection runs in or on, and it does not state capture at a customer’s own facility, so the environment, access and schedule are agreed in the spec.

Each episode follows the same episode schema as every Firsthand custom collection: ten streams synced under 2 ms, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events and frame-accurate action segments. The only language data is one task instruction per episode.

For battery work, hand pose tracks the operator through the grip on a probe, the turn of a wrench and the lift of the battery. Contact events mark when a hand takes hold of an item such as a terminal and when it lets go, and action segments mark the start and end of each step. Because the labels share one clock with the video and depth, a step boundary lines up with the exact frame where it happens. The fourth table below lists each item.

Occlusion is the first risk. A multimeter, a socket set, a wrench or the battery itself can hide the fingers that hold them, and the vehicle can block the first-person view. The per-joint visibility flag is the answer the site gives, contact events mark when a hand meets an item, and a spec can ask for wrist or multiview angles so a grip the head camera loses is still recorded. The site does not say whether a terminal or a probe counts as the object for contact events, so settle it in the spec.

The meter reading is the second. The rows describe reading voltage, but the site states that screens are detected and blurred at ingest and does not say whether a multimeter display counts. Whether the reading stays legible in the delivered video is Not stated, so decide in the spec whether it matters before capture. Surfaces are the third: the site states that under-vehicle capture is hostile to infrared depth and that such episodes carry a depth-quality flag instead of being silently interpolated, but how depth behaves around a battery and its terminals is Not stated, so check it on a Spec Pilot.

Sequence is the fourth. A job is a chain of dependent steps and the rows do not say what one episode covers, so the spec decides whether one episode is one battery swap or a longer visit. Voltage figures, battery types and brands, vehicle makes and types, electric or high-voltage vehicles, service times, throughput and any safety or certification claim are Not stated and are not claimed on this page.

Every batch is validated against signed accept criteria before it ships, with a reject log. The site states that an episode is rejected when the manipulated object is out of frame for more than 15 percent of it, when more than 35 percent of depth pixels in the manipulation region are invalid, or when an undocumented bystander appears.

Billing is per validated hour, and rejected items are recaptured at our cost. The site does not state an accuracy figure for battery step labels, so what counts as a pass for a step boundary is set in the accept criteria.

Every episode links to a signed contributor release through a documented consent chain, and the consent record is part of the delivery. Faces, plates and screens are detected and irreversibly blurred at ingest, and a reviewer confirms the result before anything ships. The site also states that licence plates and VIN plates in service-bay footage are blurred at ingest without exception. The anonymization record is delivered with the data.

Whether shop signage, a work order or a customer’s documents are blurred beyond that general rule is Not stated, and this page makes no claim about it. Raise any such rule in the spec.

The October 2026 off-the-shelf catalog lists ~324,800 hours across 18 datasets. None of them names a battery test or replacement among its tasks. Car battery replacement collection to a spec is therefore custom collection: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The site states no provider count or throughput for these rows.

The off-the-shelf catalog shows what the capture rigs deliver, and the custom order applies the same approach to your task. Two rows are Active collection and one is Ready to deploy, and the site does not say how many hours exist for either.

Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd. The first three are training-loader formats, HDF5 and zarr carry arrays for custom pipelines, and Rerun .rrd gives a synchronized playback file for review. Converter source is readable, so you can retarget the schema to your own loader, and the episode schema page lists the fields.

Delivery is rolling, per validated batch, and formats are confirmed when the work is scoped.

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. Two rows are Active collection and one is Ready to deploy, and the site does not say which speed applies to a battery order, so the timeline is quoted against your spec before capture begins.

On-demand top-ups run against the same spec and accept criteria after each training run, so new battery data stays consistent with what you already hold. The site does not state a batch size or a later-batch turnaround, so those are quoted against your spec.

Describe the steps you want and where each starts and ends: the multimeter test, the disconnect, the swap and the terminal work. Name the tools you expect to see, whether an episode covers one battery or a longer visit, whether the meter reading must stay legible, what counts as a reject and the variation your pipeline is missing. We turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria, then quote reach, timeline and price against that document before any capture begins.

Most programs begin with a Spec Pilot, a small first batch that proves the spec and the accept criteria on real footage before you scale. The collection runs through the same seven-stage end-to-end custom collection pipeline as every Firsthand program, under a perpetual, buyer-owned commercial license, with exclusivity available. The fifth table below shows what each spec element decides.