Automotive Ethernet Common-Mode Chokes: 100BASE-T1/1000BASE-T1 EMC and Sourcing Checklist

Meta description: Select automotive Ethernet common-mode chokes for 100BASE-T1 and 1000BASE-T1 with the right EMC, SI, temperature, qualification and sourcing evidence.

TL;DR: An automotive Ethernet common-mode choke must be chosen for the exact single-pair Ethernet standard, PHY/reference design, cable topology, EMC target, temperature range and qualification evidence. A CAN, USB or consumer-Ethernet filter with a similar footprint is not automatically an automotive Ethernet alternate.

Vehicle networks are shifting toward zonal controllers, cameras, gateways and central compute. That makes 100BASE-T1 (100 Mb/s) and 1000BASE-T1 (1 Gb/s) sourcing questions more common—but it also makes EMC and signal-integrity mistakes more expensive. The small common-mode choke near the PHY is often the part buyers see late, after a pre-scan failure or an allocation notice.

The sensible response is not to search for the biggest attenuation number. It is to identify the actual channel and the failed requirement, then source a part with the correct evidence.

Contents

Sourcing automotive Ethernet filters? See our component sourcing service and include the exact MPN, PHY and documentation requirements.

1. Why automotive Ethernet filters are interface-specific
2. What to evaluate beyond impedance and footprint
3. The correct sourcing and alternate-approval workflow
4. Common traps in automotive RFQs
5. PERGUNTAS FREQUENTES

Why automotive Ethernet filters are interface-specific

Common-mode filters attenuate in-phase noise while seeking to preserve the wanted differential transmission. In automotive single-pair Ethernet, the physical channel, cable, PHY, protection network and filter all work together. A filter that is suitable for CAN can have the wrong high-frequency behavior for 100BASE-T1; a commercial Ethernet part can have the wrong temperature, qualification or EMC evidence for a vehicle program.

TDK’s 100BASE-T1 application note directly compares an automotive-Ethernet choke with a CAN-BUS example and reports that the CAN-oriented example does not meet the referenced OPEN Alliance requirements. Its test context includes radiated emissions from 30 MHz and above, conducted-noise behavior over 150 kHz to 70 MHz, and BCI testing from 1 MHz to 400 MHz (TDK application note). Those figures show why a generic “common-mode choke” specification is inadequate.

TDK also lists distinct application parts for 100BASE-T1 and 1000BASE-T1 in an automotive gateway guide (TDK). The names are not an approved-parts list for your ECU; they are useful evidence that the interface family matters.

What to evaluate beyond impedance and footprint

Exact Ethernet standard, PHY and cable topology

State whether the port is 100BASE-T1, 1000BASE-T1, 10BASE-T1S or another SPE variant. Include the PHY MPN, cable length/topology, connector and protection circuit. In an engineering discussion about current vehicle platforms, practitioners distinguish legacy CAN/CAN FD from the different role played by 100/1000BASE-T1 and emerging multi-drop variants (discussion).

Differential loss, return loss and mode conversion

The core engineering check is not a nominal impedance label. Request the manufacturer’s relevant S-parameters and selection guidance, then review differential insertion loss, return loss and mode conversion against the link/channel budget. A filter can improve common-mode emissions while causing a link-margin problem if its differential behavior is unsuitable.

EMC target and test evidence

Specify the target OEM/Tier requirements and the test issue you are trying to solve—radiated emission, conducted emission, BCI, ESD or another failure mode. Manufacturer application data can guide part selection, but it does not certify your finished ECU. The cable harness, shielding, ground strategy, PCB layout and ESD/surge elements are part of the result.

Automotive environmental and qualification scope

Ask for operating-temperature range, AEC-Q200 status where required, PPAP/documentation expectations, MSL, package, mechanical robustness and PCN/PDN status. Do not write “AEC-Q200” as a proxy for the complete OEM approval package: it is one component-qualification input, not a blanket authorization for a particular vehicle program.

Protection coordination and placement

TDK’s 10BASE-T1S note combines common-mode chokes with chip varistors, illustrating that the filter is normally selected with a protection strategy rather than in isolation (TDK). Follow the PHY and protection suppliers’ placement rules; preserve pair symmetry and return paths, and do not add a component after routing without rechecking the channel.

An alternate approval workflow that respects automotive risk

1. Lock the requirement. Record standard, PHY, cable/harness, required tests, temperature, qualification documents and exact approved MPN.
2. Screen documents first. Compare datasheet, package/land pattern, S-parameters, temperature range, qualification evidence and lifecycle status. Reject candidates lacking one of the required facts.
3. Validate on hardware. Use production-intent PCB, harness and protection network. Test link performance and the relevant EMC/surge conditions; include the vehicle-program requirements, not only a bench demo.
4. Control the source. Purchase only traceable stock with manufacturer identity, lot/date-code data and documentation appropriate to the program. Update the AVL with the reviewed evidence.

An independent distributor can assist in finding exact MPNs, qualified inventory channels and documented candidates, especially when an authorized allocation cannot serve sample or bridge demand. The right disclosure is “candidate pending your validation,” not “drop-in automotive replacement.”

Common traps in automotive Ethernet RFQs

• Asking for “a 1000BASE-T1 choke” without PHY, topology or EMC requirement.
• Treating a CAN or USB choke as a substitute because its package fits.
• Using a manufacturer’s demonstration result as vehicle-level compliance evidence.
• Requesting an automotive part without stating temperature, AEC/PPAP and traceability requirements.
• Mixing lots or accepting unclear provenance on a component that supports an EMC-qualified design.

Use this minimum RFQ checklist: approved MPN/acceptable makes; T1 standard and PHY; cable/harness topology; target EMC requirement; temperature and qualification scope; package/footprint; build date, quantity and date-code/CoC requirement.

Frequently asked questions

Can a CAN common-mode choke be used for 100BASE-T1 because both are differential pairs?

Not without evidence. Both use differential signaling, but their data rates, channel requirements and filter behavior differ. The manufacturer data and an actual board-level validation must show that the candidate preserves the Ethernet link and meets the required EMC behavior in your complete harness system.

Does AEC-Q200 qualification mean a filter is approved for my vehicle program?

No. AEC-Q200 can be an important component-level qualification requirement, but program approval may also require particular temperature grades, PPAP materials, OEM test evidence, change-control terms and exact AVL status. Confirm the complete requirement with the Tier/OEM quality process.

Will a common-mode choke fix every automotive Ethernet EMC failure?

No. It may address a common-mode noise mechanism, but emissions and immunity are system outcomes. Diagnose the failing test and review cable, shielding, grounding, layout, PHY settings and protection network before selecting or changing a filter.

Conclusion: source the documented interface, not a generic choke

Automotive Ethernet common-mode choke selection needs more than a package match. Define the T1 standard, PHY, cable topology, EMC target, environmental requirements and traceability rules; then treat alternates as validated engineering changes. This approach preserves link integrity and gives purchasing a quote they can act on.

Need a 100BASE-T1 or 1000BASE-T1 filter for your automotive Ethernet BOM? Share the exact MPN, PHY, quantity, required date and documentation requirements for a component sourcing review. Identify any approved alternatives; other candidates require engineering validation.

Related reading

• CAN FD vs CAN XL transceiver selection
• AEC-Q100, Q101, Q102, Q104 and Q200 comparison
• How to prepare a BOM for quotation

For parts headed into production, who verifies them before they ship matters as much as the part itself. How Cosolvic operates covers our inspection process, counterfeit refund policy, and why we work as an independent distributor rather than a franchise reseller.

Sources

• TDK: Automotive Ethernet 100BASE-T1 EMC Countermeasures, accessed July 25, 2026.
• TDK: Automotive central server/gateway application guide, accessed July 25, 2026.
• TDK: Common-mode chokes and chip varistors for 10BASE-T1S, accessed July 25, 2026.

Editorial quality check

• Direct answer, interface-specific decision guidance, RFQ checklist, FAQ and CTA: Pass.
• Makes no claim of vehicle-level compliance or automatic automotive qualification: Pass.
• Primary keyword placement and source coverage: Pass.