Accept lots against a written AQL and critical-failure plan, not a handful of peak benchmarks. Verify identity, full capacity, V60/V90 sustained write, camera compatibility and traceability by lot and capacity.
Separate certification from production screening; sample across cartons and time; full-capacity test destructive samples; quarantine any fake capacity, mislabeled class or unexplained firmware/BOM change.
|
Bottom line Separate certification from production screening; sample across cartons and time; full-capacity test destructive samples; quarantine any fake capacity, mislabeled class or unexplained firmware/BOM change.
|
|
Decision or gate
|
What to inspect
|
Evidence to retain
|
|
Define lot
|
Model, capacity, BOM and firmware
|
Model/revision, conditions, raw result and disposition
|
|
Sample broadly
|
Cartons, time and cavities
|
Model/revision, conditions, raw result and disposition
|
|
Prove capacity
|
Full write and read
|
Model/revision, conditions, raw result and disposition
|
|
Verify class
|
Rolling V60/V90 floor
|
Model/revision, conditions, raw result and disposition
|
|
Release traceably
|
AQL, quarantine and records
|
Model/revision, conditions, raw result and disposition
|
Write the Lot Definition First
Define a lot by model, capacity, controller, NAND, firmware, assembly site, production window and packaging revision. Mixing capacities or firmware under one result hides risk. Sample cartons from the beginning, middle and end of shipment.
Classify critical defects such as false capacity, corrupted data and unauthorized marks separately from cosmetic defects. Critical failures may require zero acceptance even when general AQL sampling allows some minor defects.
Incoming Identity and Capacity
Inspect label symbols, CID or available identification, serial format, package code, dimensions and write-protect switch. Fully write and read destructive samples to prove addressable capacity; quick format cannot expose wraparound fake capacity.
Use the SD Association capacity families and expected exFAT/FAT32 behavior. Record binary/decimal display differences so legitimate capacity is not rejected.
V60 and V90 Performance Binning
V60 and V90 indicate minimum sequential-write classes of 60 and 90MB/s under the applicable SD standard. They do not promise identical peak speed. Define preconditioning, file size, reader, host, temperature, fill state and rolling-window acceptance.
Test lower-tail behavior, not only average. A lot can average above V90 while containing outliers that fail professional recording. Correlate screening limits with the formal class and target-camera validation.
Compatibility and Endurance Screens
Test representative cameras, readers and operating systems, including UHS-I fallback where claimed. Record burst clearing, long video, playback, format, sleep/wake and safe removal.
Use cycling or accelerated tests on qualification samples, not every production unit. Outgoing production screens should be short enough to avoid consuming meaningful endurance yet strong enough to catch assembly and identification failures.
Digiera Acceptance Package
For LSU100 and LSU200, Digiera should provide capacity-specific specifications, V60/V90 mark authorization evidence, BOM/firmware change control, lot code decoding, sampling results and a camera matrix.
Do not write “V90 means every card runs at the same speed.” The class is a floor, and host mode matters. Keep UHS-II reader results separate from fallback behavior in UHS-I devices.
Design the Sampling Plan Around Risk
Use stricter sampling for new suppliers, new capacity, firmware changes and professional-video claims. Relax only after statistically meaningful stable lots. Keep retain samples from every shipment so later complaints can be compared with the received condition.
Document randomization. Pulling the top five cartons or the easiest tray creates convenience sampling and can miss time-based drift.
Speed-Bin Drift and Guard Bands
Production screening should include a guard band above the claimed minimum so measurement error and environmental variation do not push customer units below class. The guard band is an internal control, not a new public speed class.
Track distributions over time. A lot can still pass while its lower percentile trends toward the limit; that trend should trigger preventive action before failures appear.
Packaging and Handling Controls
Verify moisture and ESD controls appropriate to the product, card seating, write-protect switch movement, package seals and barcode readability. Simulate shipping vibration and temperature on qualification lots.
A technically good card can still become a return when packaging bends it, mixes capacities or prints the wrong speed symbol.
From Engineering Result to Controlled Production Release
A qualification result is valid only for the configuration that was tested. The report should identify sellable model, capacity, hardware and firmware revisions, critical component suppliers, manufacturing site, sample serial numbers, conditioning, instruments, software versions, environmental conditions and acceptance limits. Photographs should show the device and setup. Raw logs must be retained long enough to investigate field returns; a presentation slide with green check marks is not a technical record.
Define failures before running the test. Separate critical data-loss or safety failures from major functional failures and minor cosmetic defects. State whether one critical failure rejects the lot, triggers expanded sampling or requires design correction. An unexplained reset, corrupted file, false capacity or unauthorized certification mark should never disappear inside an average result. Record anomalies even when the unit later passes a rerun.
Measurement systems also require control. Instruments need calibration or verification, fixtures need drawings, software and scripts need versioning, and operators need work instructions. Run repeatability checks so normal measurement variation is not mistaken for product drift. Where an official compliance method exists, internal screening may correlate with it but should not be described as certification unless the authorized program and laboratory requirements were completed.
Pilot production should demonstrate that normal manufacturing variation stays inside the engineering window. Sample across shifts, lines, cavities, component lots and the beginning, middle and end of the run. Compare distributions, not only pass counts. Keep golden samples and failed samples. Before mass shipment, review open deviations, rework, supplier substitutions, firmware branches and packaging changes with named owners and due dates.
The purchase agreement should define change notification, document retention, lot traceability, failure-analysis turnaround, access to raw evidence and responsibility for requalification. After launch, trend returns and customer complaints by model, capacity, firmware, lot and host. Qualification becomes valuable when field evidence can be traced back to the tested build and converted into corrective action.
A five-stage decision and evidence path for the article topic. Alt text: Five-stage workflow for UHS-II SD card lot acceptance plan from scope definition through evidence-based release.
Action Checklist
1. Lot definition excludes mixed capacity, firmware and BOM.
2. Sampling spans cartons and production time.
3. Full write/read capacity verification on destructive samples.
4. V60/V90 floor tested under documented preconditioning.
5. Camera matrix, trace code and change control supplied.
Where Digiera LSU100 V60 and LSU200 V90 SD cards Fits
Official Digiera product image associated with Digiera LSU100 V60 and LSU200 V90 SD cards. Alt text: Official product image for Digiera LSU100 V60 and LSU200 V90 SD cards.
Use the verified LSU100 UHS-II V60 SD card as the primary commercial reference. The article deliberately separates current page claims from independently verified results. Complete the Front Brief checks before publishing specifications, compatibility, endurance, safety or certification language.
For broader selection, review LSU200 UHS-II V90 SD card. For technical documents, controlled samples or project-specific validation, use Digiera memory card collection.
UHS-II Lot Acceptance Workflow
The plan must detect low-tail failures that an average-speed result can hide.
Apply the lot controls
-
Screen identity, capacity and obvious traceability mismatches at receiving.
-
Use risk-based samples for full-capacity and sustained-write testing.
-
Evaluate minimum speed windows as well as the batch average.
-
Retain raw traces, sample IDs, reader details and firmware information.
Place the lot on hold when
-
Any sample wraps capacity, corrupts data or reports inconsistent identity.
-
A V60 or V90 sample falls below the required sustained floor.
-
The supplier changes NAND, controller or firmware without approved revalidation.
Decision Tables
Sampling and Escalation Matrix
|
Stage
|
Minimum action
|
Escalation trigger
|
|
Incoming identity check
|
Visual, CID/identity and capacity screening
|
Mismatch or duplicate identifiers
|
|
Performance sample
|
Sustained write on selected units
|
Any unit below class floor or unstable curve
|
|
Full-capacity audit
|
Write/read verification on risk-based sample
|
Wraparound, corruption or unreadable blocks
|
|
Containment
|
Hold lot and expand sample
|
Failure cluster or unexplained component change
|
V60/V90 Evidence Matrix
|
Evidence
|
Useful for
|
Insufficient alone because
|
|
Short benchmark
|
Interface and reader sanity check
|
May fit entirely inside cache
|
|
Average long-write speed
|
Overall production trend
|
Can hide dips below the required floor
|
|
Minimum-window trace
|
Class-floor verification
|
Still needs identity and data-integrity checks
|
|
Camera recording test
|
Application compatibility
|
Does not characterize every host or card in the lot
|
Frequently Asked Questions
What do V60 and V90 mean?
They are minimum sequential-write classes of 60 and 90MB/s under the SD standard, not peak-speed labels.
Can average write speed approve a lot?
No. Use rolling minima, latency outliers and defect-rate rules so weak units are not hidden.
Should every card receive a full-capacity test?
Usually destructive full tests are sampled, while production receives shorter screens. High-risk channels may justify broader testing.
Can V90 be tested in a UHS-I reader?
No meaningful V90 qualification should rely on a UHS-I bottleneck. Use a validated UHS-II host and test fallback separately.
How should counterfeit capacity be classified?
As a critical defect requiring quarantine and supplier investigation.
What traceability is enough?
The code should resolve model, capacity, date, line, BOM/firmware revision and inspection record without ambiguity.
Why is average write speed not enough for V60 or V90 acceptance?
A card can average above the target while dipping below it long enough to interrupt recording. Review the time series and defined minimum windows, not just the final average. Correlate any dip with temperature, cache state and camera behavior.
How many cards should receive destructive full-capacity testing?
Use a documented risk-based plan based on lot size, supplier history, product maturity and the cost of escape. New or changed lots deserve broader coverage. Preserve untouched samples for comparison and increase sampling immediately after any capacity or integrity failure.
How should lower-tail performance be analyzed?
Report minimum sustained windows and the distribution across sampled cards, not only mean performance. The slowest conforming units define production margin. A lot whose average is strong but whose lower tail approaches the class floor needs investigation or tighter binning.
Does a firmware change require a new lot-acceptance baseline?
Yes when it can affect flash management, speed, error handling or identity data. Obtain the change notice and compare full-capacity, sustained-write, thermal and camera results. Do not silently pool pre-change and post-change evidence.
Should UHS-II cards be tested in UHS-I fallback mode?
Yes if users may place them in UHS-I devices. Confirm recognition, formatting and stable operation at the lower interface mode, while keeping UHS-II performance claims tied to a valid UHS-II reader and host.
How long should lot traceability records be retained?
Retention should cover the expected sales, warranty and regulatory investigation period defined by the business. Keep supplier lot, component/firmware revision, test equipment, raw results, sample identity and disposition. Summary pass sheets without raw evidence weaken root-cause work.