Is Your Dot Peen DataMatrix Unreadable? Readability, AS9132, and ISO/IEC 29158
Your DataMatrix code looks fine to the eye, but the scanner reads it intermittently. This is a common issue in dot-peen marking, and the cause is rarely the machine itself—it is usually dot size, dot spacing, part fixturing, or scanning illumination. In this guide, we break down the root causes, aerospace AS9132 criteria, and ISO/IEC 29158 verification for DPM codes.
By Erden Arıkan · Mechatronics Engineer
Why Is Dot Peen DataMatrix Harder to Read?
In an ink-printed DataMatrix, cells are solid squares with continuous borders. In dot-peen marking, however, each cell is an individual dimple, resulting in discontinuous edges. Standard DataMatrix decoding algorithms can therefore struggle with dot peen codes. Developed specifically for DPM codes, the ISO/IEC 29158 standard incorporates an approach that links dots together to identify cells. The 2020 revision of the standard also introduced a continuous grading scale (in 0.1 increments), providing more stable results for codes fluctuating between letter grades.
Symptoms of Poor Readability and Likely Causes
Symptom | Probable Cause | Corrective Action |
|---|---|---|
Dots are too large, touching each other | Excessive impact force or narrow cell spacing | Reduce force, increase code size |
Dots are small with wide gaps | Low impact force, worn pin stylus | Increase force, inspect the pin tip |
Cells shifted off-grid | Part not securely clamped or backlash in marking head | Tighten fixturing, request service for head maintenance |
Intermittent scanning / poor read rates | Illumination, low contrast, or surface glare | Adjust scanner angle and lighting; test on a matte surface |
Code is too small | Insufficient optical resolution | Mark over a larger area with bigger cell pitch |
Practical Rule of Thumb for Dot Size and Spacing
A frequent industry recommendation is that dot diameter should be roughly 80% of dot spacing—meaning adjacent dots are close enough to nearly touch without overlapping. If the gap between dots exceeds half the dot size, readability drops significantly. Exact parameters vary depending on the workpiece, stylus pin, and scanner, so treat these as a baseline. On rough surfaces such as castings, keep the cell size larger: NASA-STD-6002 requires cells to be significantly larger than surface irregularities so that surface pit shadows are not misinterpreted by the scanner as dark cells.
What Does AS9132 Require?
AS9132 is a quality standard used across aerospace and defense supply chains for dot-peen and similar dot-based DataMatrix codes, commonly mandated by customer specifications. It evaluates three key criteria simultaneously, requiring all of them to pass:
- Dot size: Must be between 65% and 105% of nominal cell size
- Dot center offset: Maximum 20% relative to the ideal grid
- Angle of distortion: Maximum 6° deviation on the L-shaped finder pattern
If dots are oversized, impact force is too high and must be reduced. If dot centers are shifted, the workpiece is either insufficiently clamped or backlash has developed in the marking head. Always verify specific tolerance limits in the AS9132 revision cited in your contract.
Reading vs. Verification: Not the Same Thing
Just because a standard scanner decodes a symbol does not mean it meets quality standards. Verification is an independent measurement process that demands repeatable imaging: changing the lighting angle can alter a code's grade. Therefore, verification should be performed under controlled lighting, ideally right after marking. While ISO/IEC 15415 applies to flat printed labels, ISO/IEC 29158 governs direct part marking (DPM).
A code read by a smartphone might not yield the same result with an industrial scanner or a certified verifier. In our example on DataMatrix marking on automotive parts, various code sizes were tested and readability was confirmed using a standard mobile app. This is a quick field check, not a substitute for formal verification.
Pre-Marking Checklist
- Select code size based on marking window area and scanner resolution
- Clamp the part firmly in place to eliminate vibration
- Adjust impact force so dot diameter is roughly 80% of cell pitch
- Regularly inspect the pin tip condition; wear alters dot geometry
- Test scanner and lighting angles under actual production conditions
- If your customer requires AS9132 or ISO/IEC 29158, verify under calibrated, controlled lighting
Request a Sample Test on Your Part
The fastest way to determine optimal DataMatrix parameters and size is directly on your component. Send us your sample; we will mark it and evaluate readability results together. To learn more about DataMatrix standards and symbology, check out our article What is DataMatrix Code.
Frequently Asked Questions
A phone scans it, but the industrial reader fails—why? Smartphone camera software uses adaptive image post-processing, whereas industrial fixed-mount or handheld readers operate under fixed illumination and exposure settings. Your industrial scanner must be dialed in and tested under actual production lighting conditions.
Who requires AS9132 compliance? It is typically mandated by OEMs throughout aerospace and defense supply chains. Review your contractual technical specifications to determine whether AS9132 is required.
Does stylus pin wear affect DataMatrix quality? Yes. A worn pin alters dot diameter, depth, and symmetry, degrading cell quality and contrast. Pin tips should be inspected and sharpened or replaced regularly.
My code fails verification; what should I check first? Check dot size first: if dots are oversized, lower impact force; if undersized, increase it. Next, ensure rigid part clamping to avoid shift. If the issue persists, contact our technical team for parameter optimization.
###