Ndk

MPN Structure

NDK MPNs follow this general structure:

[PREFIX][SIZE][VARIANT]-[FREQUENCY][OPTIONS]
   |       |      |          |         |
   |       |      |          |         +-- Temperature grade, packaging
   |       |      |          +-- Frequency code (MHz or kHz)
   |       |      +-- Variant/specification letter
   |       +-- Size code (2 digits indicating package dimensions)
   +-- Product family prefix (NX, NT, NZ, NV, etc.)

Family Prefixes

Example MPN Decoding

Crystal Example

NX3225SA-24.000M
|  |  | |     |
|  |  | |     +-- 24.000M = 24 MHz frequency
|  |  | +-- - = Separator
|  |  +-- SA = Series/specification variant
|  +-- 32 25 = 3.2 x 2.5mm package
+-- NX = Standard Crystal family

Oscillator Example

NZ2520SDA-20.000M
|  |  |  |     |
|  |  |  |     +-- 20.000M = 20 MHz frequency
|  |  |  +-- - = Separator
|  |  +-- SDA = Series/specification variant
|  +-- 25 20 = 2.5 x 2.0mm package (note: size code is first 2 digits after prefix)
+-- NZ = Standard Oscillator family

Automotive Crystal Example

NAT3225SBTC-25.000M
|   |   |     |
|   |   |     +-- 25.000M = 25 MHz frequency
|   |   +-- SBTC = Automotive specification variant
|   +-- 32 25 = 3.2 x 2.5mm package
+-- NAT = Automotive grade Crystal

Supported Component Types

The NDKHandler supports these ComponentTypes:

Note: SAW devices (SF, SR, SD) are registered under ComponentType.IC in patterns but SAW_FILTER_NDK and SAW_RESONATOR_NDK are listed in getSupportedTypes().

Package Code Extraction

The handler extracts package dimensions from the size code in the MPN. The size code is positions 3-4 (0-indexed) after the prefix.

Crystal Packages (NX, NT, NH, NAT)

Extraction Logic:

// For crystals: extract characters at positions 3-4 (after NX, NT, NH, or NAT prefix)
// Example: NX3225SA → position 3 is "3", position 4 is "2" → "32" → 3.2 x 2.5mm
String sizeCode = upperMpn.substring(3, 5);  // Gets "32" from "NX3225..."

Oscillator Packages (NZ, NP, NV, NO)

Extraction Logic:

// For oscillators: extract characters at positions 3-4
// Example: NZ2520SDA → "25" → 2.5 x 2.0mm
String sizeCode = upperMpn.substring(3, 5);

Series Extraction

The handler returns descriptive series names based on the MPN prefix:

Crystal Series

Oscillator Series

VCSO Series

SAW Device Series

Frequency Code Patterns

NDK MPNs include frequency specifications after the hyphen:

Extraction Logic:

private String extractFrequencyCode(String mpn) {
    // Extract everything after the last hyphen
    int lastDash = mpn.lastIndexOf('-');
    if (lastDash >= 0 && lastDash < mpn.length() - 1) {
        return mpn.substring(lastDash + 1);
    }
    return "";
}

Common Example MPNs

Standard Crystals (NX)

Tuning Fork Crystals (NT)

Automotive Crystals (NAT)

Standard Oscillators (NZ)

TCXOs (NT oscillator)

VCXOs (NV)

OCXOs (NO)

Handler Implementation Notes

Pattern Registration

The handler registers patterns for both base types and NDK-specific types:

// Crystal patterns - register for BOTH generic and manufacturer-specific types
registry.addPattern(ComponentType.CRYSTAL, "^NX[0-9].*");
registry.addPattern(ComponentType.CRYSTAL_NDK, "^NX[0-9].*");

Prefix Overlap Issues

NT Prefix Conflict: The NT prefix is used for BOTH:

• Tuning fork crystals (when followed by size code like NT1612, NT2012)
• TCXOs (Temperature Compensated Crystal Oscillators)

The handler's extractSeries() method has overlapping checks:

// This check comes first, returning "Tuning Fork Crystal"
if (upperMpn.startsWith("NT")) return "Tuning Fork Crystal";

// This check is never reached because the first one matches
if (upperMpn.startsWith("NT") && upperMpn.length() > 3) {
    // TCXO logic
}

NH Prefix Conflict: The NH prefix is used for BOTH:

• High frequency crystals
• High stability OCXOs

Replacement Compatibility

The isOfficialReplacement() method checks:

1. Series compatibility - Same series or compatible upgrade path
2. Package match - Same physical dimensions required
3. Frequency match - Identical frequency code required

// Compatible series: Wide temp/stability can replace standard
if (series1.startsWith("Wide Temp") &&
    series2.equals(series1.replace("Wide Temp ", ""))) return true;
if (series1.startsWith("High Stability") &&
    series2.equals(series1.replace("High Stability ", ""))) return true;

Related Files

• Handler: manufacturers/NDKHandler.java
• Component types: CRYSTAL, CRYSTAL_NDK, OSCILLATOR, OSCILLATOR_NDK, OSCILLATOR_TCXO_NDK, OSCILLATOR_VCXO_NDK, OSCILLATOR_OCXO_NDK, SAW_FILTER_NDK, SAW_RESONATOR_NDK

Learnings & Quirks

Handler Issues (Identified)

• HashSet in getSupportedTypes(): Uses mutable HashSet, should use Set.of() for immutability (see CLAUDE.md "Handlers Without Tests" section)
• Missing IC type in getSupportedTypes(): SAW devices (SF, SR, SD) register patterns under ComponentType.IC but IC is not in getSupportedTypes()
• NT prefix ambiguity: Same prefix used for tuning fork crystals AND TCXOs; series extraction logic has unreachable code
• NH prefix ambiguity: Same prefix used for high frequency crystals AND high stability OCXOs
• Package extraction position: Uses fixed positions 3-4 which assumes 2-letter prefix; NAT (3-letter) will extract wrong characters ("T3" from "NAT3225...")

Size Code Mapping

NDK uses a unique size code system where digits represent dimensions:

• First digit = first dimension (mm), second digit = second dimension
• "32" = 3.2mm x 2.5mm (but "25" in oscillators = 2.5mm x 2.0mm)
• The mapping is not always intuitive; always verify against datasheet

Oscillator Type Hierarchy

SAW Device Applications

Competing Products

Temperature Grade Suffixes

Common temperature grade indicators in NDK MPNs:

• No suffix: Commercial (0°C to +70°C)
• T or TC: Industrial (-40°C to +85°C)
• A or AC: Automotive (-40°C to +125°C)

Packaging/Tape Options