16 November 2026
ELECBEE
69

Automotive Ethernet to PC: 100BASE-T1 / 1000BASE-T1 Media Converters and Setup

Connect a 100BASE-T1 or 1000BASE-T1 ECU to a PC using an automotive Ethernet media converter or USB T1 interface, with DIP switch setup and troubleshooting.

To connect a point-to-point 100BASE-T1 or 1000BASE-T1 device to a PC's standard RJ45 Ethernet port, use an active automotive Ethernet media converter. T1 carries full-duplex Ethernet over one balanced twisted pair; the PC's 100BASE-TX or 1000BASE-T port uses different physical-layer signaling. Re-pinning an H-MTD or MATEnet connector to RJ45 cannot make those interfaces communicate.

Two practical options are a T1-to-RJ45 media converter connected to the PC's Ethernet adapter and a dedicated T1-to-USB network interface. The setup depends on the device under test (DUT), its T1 speed and clock role, and which port carries data to the computer.

Two hardware paths to connect a T1 DUT to a PC

In the PEAK manual, the automotive 100BASE-T1 / 1000BASE-T1 port is labeled SPE (Single-Pair Ethernet), while the standard PC 100BASE-TX / 1000BASE-T RJ45 port is labeled MPE (Multi-Pair Ethernet). For foundational cable standards or multi-port harness layouts, see our Automotive Ethernet Cable Assembly Guide and H-MTD Cable Assemblies. On the test bench, choose your active conversion hardware based on how Ethernet frames reach the computer.

Two bidirectional data routes: T1 to RJ45 to PC Ethernet, or T1 to USB network interface to PC USB.

Path 1: T1-to-RJ45 media converter and a PC Ethernet port

An active T1-to-RJ45 media converter supports 100BASE-T1 or 1000BASE-T1 on its automotive port and 100BASE-TX or 1000BASE-T on its RJ45 port. Ethernet packets travel over a standard RJ45 patch cable into the PC's network interface card (or into a standard USB-to-RJ45 adapter if the laptop has no built-in Ethernet jack).

A USB port on a media converter may provide configuration, power, or network data, depending on the device. These two RJ45 converter models illustrate why the exact model matters:

PEAKIPEH-101101User manual v1.1.0

USB-C

Configuration and status via USB CDC serial: COMx in Windows or /dev/ttyACMx in Linux.

Operating power

6–36 V DC via Phoenix, or 5 V via USB-C from a supply capable of at least 500 mA.

TechnicaTE-140x seriesModel documentation

Micro-USB-B

Serial debugging, including link-quality and error information.

Operating power

Use the MQS connector: 6–30 V DC. Micro-USB is the debug connection.

Ethernet data on both: T1 port ↔ converter ↔ RJ45 port ↔ PC network adapter.

Path 2: Direct T1-to-USB network interface

If you prefer to connect a T1 device to a PC over USB without using an RJ45 port, choose hardware built specifically as a T1-to-USB network interface.

For instance, the ATMES aDongle (datasheet PDF) provides a 100BASE-T1 / 1000BASE-T1 interface on one side and a USB 3.0 Type-B receptacle on the device for connecting to the host PC. Unlike a serial-only USB control port, the aDongle enumerates in the operating system as a standard Ethernet interface for direct communication and Wireshark packet capture. However, verify the physical T1 connector before ordering cables: because the aDongle uses a D-sub 9 connector on its T1 side rather than a board-mounted H-MTD or MATEnet socket, you must confirm the exact D-sub pin assignment and transition harness for your setup.

Both paths above connect the PC as an active endpoint in a point-to-point link with the DUT. If your task is to passively monitor traffic between two existing automotive nodes, a single point-to-point media converter cannot act as a transparent pass-through tap. Monitoring that existing link requires a dedicated automotive Ethernet network TAP or a mirror-capable switch/test interface matched to your network topology.

Five parameters to check before power-on

Matching the connector shell alone is not enough to bring up a T1 link. Check these five parameters in your DUT documentation and converter manual before applying power.

Parameter What to Confirm in DUT & Converter Manuals Result of a Mismatch
1. Transfer Rate (100 vs. 1000 Mbit/s) What to Confirm in DUT & Converter ManualsConfirm whether the DUT port runs at 100BASE-T1 (100 Mbit/s) or 1000BASE-T1 (1000 Mbit/s), and check whether the converter requires the PC-side RJ45 link to run at the same synchronous rate. Result of a MismatchT1 link fails to establish, or the PC-side RJ45 port fails to link at the required speed.
2. PHY Clock Role (Master vs. Slave) & ANEG What to Confirm in DUT & Converter ManualsCheck whether the DUT uses a fixed Master or Slave PHY role. Set the converter to the opposite role (Slave for a Master DUT; Master for a Slave DUT), or use Auto-Negotiation (ANEG) only when both ends support and enable it. Result of a MismatchT1 physical link remains down despite valid power and cabling.
3. IEEE vs. Legacy Mode & Hardware Revision What to Confirm in DUT & Converter ManualsCheck whether a 100BASE-T1 link requires standard IEEE 802.3bw or legacy BroadR-Reach mode, and verify the DIP switch table for your converter's exact model number and hardware revision. Result of a MismatchMisaligned PHY mode or wrong switch mapping prevents T1 link training.
4. Active T1 Connector Selection What to Confirm in DUT & Converter ManualsVerify whether the converter has a single T1 port (H-MTD, MATEnet, or D-sub) or multiple sockets that must be selected via switch or software. Result of a MismatchHarness is plugged into an inactive port, leaving the T1 link LED off.
5. Device Power Supply (No Default PoDL) What to Confirm in DUT & Converter ManualsVerify the voltage and current requirements for both the DUT and the converter. Single-pair T1 connections do not supply Power over Data Lines (PoDL) by default. Result of a MismatchConverter or DUT stays unpowered, or the ECU remains in sleep mode.

Clock roles and hardware revision differences

On a full-duplex single-pair 100BASE-T1 or 1000BASE-T1 link, one transceiver must act as the Master—sourcing the reference transmit clock—while its link partner acts as the Slave, recovering clock timing from the received signal. This Master / Slave relationship exists strictly at the physical layer and has nothing to do with upper-layer IP servers or clients. If an ECU is configured with a fixed PHY role in firmware, setting both devices to Master or both to Slave prevents the physical link from establishing. Automatic negotiation (ANEG) can resolve role and speed only if both the converter and the T1 peer support and enable it.

Technica's TE-140x series illustrates why settings must match the model. TE-1402 and TE-1405 use MATEnet; TE-1403 and TE-1406 use H-MTD. DIP 3 selects IEEE/Legacy mode on TE-1402/1403, as described for the older H-MTD unit in the v1.6 manual. On TE-1405/1406, DIP 3 instead controls Autosearch; these newer models also add web configuration and TC10 support. Use their own instructions, including for Autosearch, rather than PEAK's ANEG switch logic.

Port selection is model-specific too. PEAK's H-MTD and MATEnet sockets are alternatives: selecting one deactivates the other. Other multi-port devices may work differently.

PEAK PAE-Media Converter setup (IPEH-101101)

The following settings apply to the PEAK PAE-Media Converter IPEH-101101, described in its User Manual v1.1.0.

Assumed Bench Scenario: The target DUT is specified as a 1000BASE-T1 device with a fixed Master PHY role and a matching H-MTD port, powered via its own supply, and the PC provides an active Gigabit RJ45 port (1000BASE-T). All switch positions and LED states below apply specifically to the IPEH-101101 under these conditions.

1. Set the DIP switches

The IPEH-101101 reads its six DIP switches at startup. During operation, moving a switch applies its new setting and clears the USB API override for that switch.

PEAK IPEH-101101 example: DIP 1, 2, 3, 5 and 6 upper; DIP 4 lower ON. ANEG off, 1000 Mbit/s, Slave, H-MTD, frame generator off, reserved switch upper.
Only switch 4 is down (ON) in this example. Use these settings for the fixed-Master, 1000BASE-T1 H-MTD scenario above.

When adapting these settings to a different DUT on the IPEH-101101, note the manual's rules for the opposite switch positions:

  • Auto-Negotiation (1 / ANEG): Manual rate and role settings are preferred when the peer's configuration is fixed. If 1 / ANEG is set to Lower (ON), the settings of switches 2 / SPEED and 3 / ROLE are ignored, and the T1 peer must also support and enable auto-negotiation.
  • Speed, Role, and Connector Alternatives: Setting 2 / SPEED to Lower (ON) selects 100 Mbit/s (on the IPEH-101101, the T1 port and the RJ45 port operate synchronously at the same transfer rate). If your DUT is a fixed Slave, set 3 / ROLE to Lower (ON) for Master. To use the right-hand MATEnet socket instead of H-MTD, set 4 / CONNECTOR to Upper—simultaneous transmission across both T1 ports is not supported. Keep 5 / FRAME GEN in the Upper (off) position during normal operation; setting it to Lower (ON) continuously transmits 64-byte alternating-bit test frames on the T1 side.

2. Connect the devices and check their status

Follow this order to put the converter into operation and verify the link:

  1. Set the DIP switches on the front panel according to the scenario above.
  2. Connect the PC RJ45 side: Run a standard Ethernet cable from the converter's ETHERNET RJ45 port to the PC's Gigabit RJ45 port (or a standard Ethernet switch).
  3. Connect the T1 side: Connect the DUT to the converter's left H-MTD port using an appropriate 100 Ω H-MTD cable assembly.
  4. Apply power to both devices.
    PEAK bench: DUT and converter receive separate power feeds; bidirectional T1 and RJ45 carry Ethernet data. A separate optional USB cable connects the PC to rear USB-C for serial control.
    This setup powers PEAK through its rear Phoenix input. USB is optional for configuration and status; Ethernet frames reach the PC over RJ45.

    USB power alternative: use a 5 V USB supply capable of at least 500 mA. Phoenix takes priority if both inputs are connected. Power the DUT per its manual; T1 does not provide PoDL by default.

  5. Read configuration, link and traffic indicators separately.
    PEAK front LED matrix and RJ45 indicators. SQI varies; STAT off, SPD green for 1000, M/S yellow for Slave, H-MTD green selected and MATEnet off. LNK is green with a link; ACT yellow and RJ45 left green flash with traffic; RJ45 right yellow indicates link.
    The front view places RJ45 traffic on the left and link on the right. Link indicators can stay on while no application frames are being sent.

    SQI quality: green 6–7 · yellow 3–5 · red 0–2. SQI reports link quality, not traffic activity.

    Other settings: SPD yellow means 100 Mbit/s; M/S green means Master. This example uses 1000 Mbit/s and Slave.

  6. Verify No Runtime USB API Override Is Active and Prepare Host Capture: Over the USB CDC virtual serial port (COMx on Windows; /dev/ttyACMx on Linux), runtime ASCII commands can override individual DIP switch settings until that DIP switch is toggled again or the converter is restarted.

    If the unit was previously used with automated test scripts, open a serial terminal to the converter's virtual COM port (not the PC's system shell) and send the read-only command CONFIG GET to read the active SPEED, ROLE, CONNECTOR, and FRAMEGEN configuration, and STATUS GET to read the current T1 and RJ45 link states, transfer rates, role, polarity, and SQI. CONFIG GET does not list the auto-negotiation setting; also check that STAT is off for this manual-configuration scenario.

    Set the serial terminal to end each command with carriage return and line feed (CR + LF). Once confirmed, select the appropriate physical or VLAN capture interface on your PC and apply the network settings required by your DUT documentation.

Troubleshooting a T1-to-PC connection

When a bench link fails to come up or Wireshark captures no target traffic, isolate the issue from the physical layer upward rather than changing IP settings or swapping cables blindly.

Layer 1: No power or only a serial port appears

  • Symptom: Converter LEDs are off, or plugging in USB only adds a serial port in Device Manager / /dev/ without creating a network interface.
  • Next Checks: Confirm both the DUT and the converter receive power within their specified voltage and current ratings. If you connected USB on an RJ45 media converter where USB is dedicated to configuration or debugging (such as COMx / /dev/ttyACMx on the PEAK IPEH-101101, or the Micro-USB serial debug interface documented in your Technica TE-140x manual), remember that Ethernet packets do not cross that USB cable—connect the converter's RJ45 port to the PC's Ethernet adapter.
  • Symptom A — T1 Link Indicator Is Off:
    • Verify the cable is plugged into the selected active T1 socket (H-MTD vs. MATEnet on the PEAK converter).
    • Confirm the converter's Master/Slave role is set opposite the DUT's fixed role (or that both devices support and enable auto-negotiation).
    • Check that the transfer rate (100 vs. 1000 Mbit/s) and PHY mode (IEEE vs. Legacy, where supported) match the DUT.
    • Read the active configuration (for example, with CONFIG GET on the PEAK serial interface) and compare it with the intended DIP settings to identify a runtime software override.
    • Confirm the DUT is powered and awake; if the ECU requires TC10 wake-up signaling, check whether your specific converter model supports TC10.
  • Symptom B — T1 Link Is Up, But PC RJ45 Link Indicator Is Off:
    • Confirm the PC's Ethernet adapter is enabled and test with a known-good RJ45 patch cable.
    • Verify that the PC network port supports the active transfer rate—especially on synchronous converters like the PEAK IPEH-101101, where a 100 Mbit/s or 1000 Mbit/s T1 link requires the same rate on the RJ45 port.
  • Symptom C — Intermittent Link Drops or Degraded Signal Quality:
    • Read the converter's signal-quality indication or diagnostic status. On PEAK, STATUS GET reports link state and SQI; Technica documents error counters through its serial debug console. Because SQI scales and thresholds depend on the specific converter and PHY, combine those readings with a known-good 100 Ω cable assembly, secure connector latching, and shielding/grounding checks per your system specification.
Traffic must reach the PC NIC, pass capture selection and filters, and remain visible under the display filter.
Check these stages in order. Link LEDs alone do not prove that target frames reached the capture interface.
  • Confirm the DUT Is Transmitting and Check the Capture Interface: A working physical link does not guarantee that the ECU is sending application frames. First confirm that the DUT is in an active state configured to transmit traffic and that those frames reach your PC port—as explained in the Wireshark Ethernet capture guide, promiscuous mode on an endpoint NIC cannot capture unicast traffic that a switch never forwards to that port. In Wireshark's interface list, verify you selected the intended network adapter and check interface packet counters. Review capture filters before starting a new capture. Also clear any display filter that may hide packets already captured; display filters change what is shown, not what is stored in the capture file.
  • Ensure Built-In Test Frame Generators Are Off: Confirm that any internal test generator on the converter (such as 5 / FRAME GEN on the PEAK unit) is turned off, so continuous test frames are not mistaken for DUT communication.
  • Check VLAN Interface Selection and Driver Tag Handling: When a DUT sends 802.1Q VLAN-tagged frames, choose the physical or VLAN sub-interface that matches your test setup. As detailed in the Wireshark VLAN capture notes, whether VLAN tags remain visible in Wireshark—or are stripped or filtered before capture—depends on the specific PC network adapter and its driver hardware-offloading settings. Missing VLAN tags in a capture do not automatically mean the traffic was untagged on the wire.

Layer 4: Packets are captured, but the application fails

  • Do Not Confuse PHY Master with IP Services: The T1 Master setting only controls physical-layer clock timing; it does not determine whether that device runs an IP service or a DHCP server.
  • Configure Host Addressing Per the DUT Specification: Set the PC's network interface parameters—such as a static IP address, subnet mask, route, or VLAN ID when required—strictly according to the target DUT's network documentation.
  • Treat ping as a Secondary Check: Use ping (ICMP Echo) only when the DUT documentation confirms that ICMP responses are enabled on that address and VLAN. If the DUT is not configured to answer ICMP, verify connectivity using the documented diagnostic or application protocol alongside Wireshark.

Match the passive T1 cable assembly to the setup

Once your active media converter or USB T1 interface is configured for 100BASE-T1 or 1000BASE-T1, match the passive 100 Ω differential cable assembly to the exact interfaces on both ends:

  • Endpoint Connector Series: Verify whether your bench link requires an H-MTD-to-H-MTD assembly, a MATEnet-to-MATEnet assembly, a cross-interface H-MTD-to-MATEnet assembly, or a verified D-sub transition cable wired to the exact pin assignment of a D-sub 9 T1 device.
  • Coding, Pinout, Shielding, and Length: Confirm complete connector coding and pin assignment at both ends, check whether your interface and system specification require a shielded assembly, and choose an appropriate bench length.

Single-port cable examples for the bench

These 1 m, 100 Ω shielded twisted-pair assemblies provide two different end configurations. Choose the mating interfaces first.

Elecbee EB-E6S10A-1CAZ5-Z-E6S10A-1M product photo, two single-port H-MTD plug ends.

Plug to plug

E6S10A-1CAZ5-Z at both ends.

For a single-port link where both equipment interfaces accept H-MTD plugs.

View SKU EB-E6S10A-1CAZ5-Z-E6S10A-1M
Elecbee EB-E6K10A-1CAZ5-Z-E6S10A-1M product photo, one H-MTD plug and one H-MTD jack; original photo labels identify the two ends and cable.

Jack to plug

E6K10A-1CAZ5-Z jack to E6S10A-1CAZ5-Z plug.

Photo labels: 1 plug · 2 jack · 3 cable.

For a single-port link whose two mating interfaces require different cable-end genders.

View SKU EB-E6K10A-1CAZ5-Z-E6S10A-1M

Match coding, pin assignment and the complete channel requirements before ordering. These passive assemblies do not perform T1-to-RJ45 or T1-to-USB conversion.

When both endpoints are confirmed, browse our Automotive Ethernet Cable Assembly category to select passive T1 cable assemblies for your test setup.