TJA1057GT/3J - 1 Mbit/s CAN Transceiver | NXP Semiconductors
MPN: TJA1057GT/3J ✗ End of LifeTJA1057GT/3J Overview
A CAN transceiver is a physical-layer interface IC that converts logic-level controller signals into differential bus signals and converts received differential signals back into logic-level data. The TJA1057 belongs to NXP's Mantis family of CAN transceivers, placing it within the hierarchy of CAN interface IC, communication transceiver, interface IC, and semiconductor. Its high-speed differential operation allows a CAN controller and transceiver combination to communicate over a noisy wiring harness while preserving signal integrity.
The principal feature of the /3 variant is its dedicated VIO supply connection. According to the manufacturer documentation, VIO should be connected to the microcontroller supply voltage, allowing the TXD and RXD interface levels to be adjusted for either 3.3 V or 5 V operation. This helps avoid unnecessary voltage-level conversion between the CAN controller and the physical bus transceiver. The TJA1057 family implements the CAN physical layer defined by ISO 11898-2:2016 and the SAE J2284-1 through J2284-5 specifications.
TJA1057GT/3J provides one CAN channel and uses an 8-pin SOIC footprint identified as PDSO8 in distributor data. Its architecture separates the controller-facing digital interface from the differential CANH and CANL bus connection. The VIO domain supports integration with modern microcontrollers, while the bus side handles the higher-voltage signaling required by a wired CAN network. This division of voltage domains is central to correct PCB design because input, output, transceiver, and ground connections have different electrical roles.
Typical uses include automotive body and chassis networks, industrial automation equipment, diagnostic systems, electric-vehicle subsystems, robotics, and embedded control platforms. It is particularly suitable when the CAN controller operates from 3.3 V while the surrounding vehicle or industrial network uses a conventional 5 V CAN physical layer. In these systems, the transceiver provides the physical interface while the CAN controller handles arbitration, framing, error management, and higher-level protocols.
PCB implementation should follow the manufacturer's pin and layout guidance, including a common reference plane and a controlled return path beneath the bus connections. Decoupling and protection requirements should be evaluated against the actual vehicle or industrial network because external bus transients and ground offsets can exceed nominal logic-level conditions. The VIO connection must be referenced to the microcontroller supply, and unused or unused-after-configuration pins must not be left without consideration.
This product record consolidates the verified NXP documentation, distributor availability, package information, lifecycle status, and same-family replacement information. It also highlights the practical distinction between the VIO-enabled /3 variant and other TJA1057 options so engineers can make a pin-compatible selection without confusing protocol support, interface voltage, or temperature-grade suffixes.
Drop-in alternatives for TJA1057GT/3J — same package, pin-to-pin compatible. Different-package parts requiring PCB rework are excluded.
Variants in this series
Same-series models that are drop-in compatible with TJA1057GT/3J (same form factor and footprint) — differing in Package, Protocol, Operating Temperature, Family, Function.
TJA1057GT/3
✅ Drop-In ⚠️ Specs Unverified📋 Reference alternative (not in catalog)
TJA1057BT/3
✅ Drop-In ⚠️ Specs Unverified📋 Reference alternative (not in catalog)
TJA1057T/3J
✅ Drop-In ⚠️ Specs Unverified📋 Reference alternative (not in catalog)
TJA1057GT/3J
✅ Drop-InContact for price
View Datasheet →TJA1022HGZ
✅ Drop-InContact for price
View Datasheet →TJA1027T/20/2Z
✅ Drop-In📋 Reference alternative (not in catalog)
TJA1057GT/3J Specifications
| Product Type | High-speed CAN transceiver |
| CAN Channel Count | 1 channel |
| Maximum CAN Data Rate | 1 Mbit/s |
| Bus Interface | Differential two-wire CAN bus |
| Controller Interface | TXD and RXD |
| VIO Supply | 3.3 V or 5 V microcontroller interfacing |
| CAN Physical-Layer Standard | ISO 11898-2:2016 |
| Automotive Communication Standards | SAE J2284-1 through SAE J2284-5 |
| Package | 8-pin SOIC, PDSO8 |
| Mounting Type | Surface mount |
| Transmit and Receive Capability | Differential CAN transmit and receive |
| Manufacturer | NXP Semiconductors |
| Lifecycle Status | NRND |
TJA1057GT/3J 8-pin soic, pdso8 Pin Configuration Guide
Pin configuration for TJA1057GT/3J (8-pin soic, pdso8 package). Pin numbering, functions, and connection diagrams are defined in the manufacturer datasheet. Refer to it for the exact footprint and soldering guidelines.
No detailed pinout data available for TJA1057GT/3J.
Refer to the datasheet for full pin configuration.
Typical Applications
TJA1057GT/3J is suitable for 6 applications: 3.3 V Automotive Body Control, Industrial Automation CAN Network, Electric Vehicle Subsystem Interface, Diagnostic and Service Equipment, Robotics and Sensor Network Backbone, High-Speed CAN Gateway.
3.3 V Automotive Body Control
The TJA1057GT/3J fits an automotive body-control module where a 3.3 V microcontroller must connect to a conventional differential CAN network. Its VIO input is intended to follow the controller supply, allowing TXD and RXD to operate with 3.3 V logic without a separate translator. The transceiver handles the physical-layer conversion to CANH and CANL, while the CAN controller manages framing, arbitration, and fault recovery. Its 1 Mbit/s capability and ISO 11898-2:2016 alignment suit conventional high-speed CAN networks. The PCB still needs vehicle-grade bus protection and grounding designed for the specific harness environment.
Recommended
Industrial Automation CAN Network
The TJA1057GT/3J can bridge a 3.3 V embedded controller to an industrial CAN bus carrying sensor commands, drive status, and diagnostics. The VIO connection supports direct interfacing with a 3.3 V or 5 V controller, while the differential bus side provides noise-resistant communication over factory wiring. At rates up to 1 Mbit/s, it is appropriate for real-time control traffic where deterministic short-frame communication is required. Designers should add surge protection, maintain a continuous return path, and verify that the transceiver's supply and common-mode limits match the installation's grounding and fault conditions.
Recommended
Electric Vehicle Subsystem Interface
The TJA1057GT/3J is suitable for an electric-vehicle subsystem that uses a 3.3 V controller but communicates over a 5 V-class high-speed CAN network. Its VIO domain permits direct controller interfacing, and the physical-layer transceiver provides the required CANH and CANL differential signaling. This arrangement is useful in battery-management, thermal-management, inverter-control, and vehicle-computing modules where the logic supply and legacy CAN bus voltage domains differ. Because vehicle transients are severe, the final design still requires correctly selected protection, adequate grounding, and qualification for the target electrical environment.
Recommended
Diagnostic and Service Equipment
The TJA1057GT/3J can be used in diagnostic equipment that connects a low-voltage controller or test interface to a vehicle CAN network. The /3 VIO architecture supports a 3.3 V host while maintaining compatibility with a 5 V CAN physical layer, reducing the need for level-shifting components. The 1 Mbit/s CAN capability allows the diagnostic interface to exchange vehicle status, DTC information, and service data using standard high-speed CAN frames. In service-bay equipment, bus protection must tolerate disconnected cables, diagnostic equipment faults, and vehicle-side transients rather than relying only on the transceiver's internal operating limits.
Recommended
Robotics and Sensor Network Backbone
The TJA1057GT/3J fits robotic controllers and distributed sensor nodes that use CAN as a shared communications backbone. Its differential transmit and receive interface supports robust communication over cables running near motors and switching equipment, while VIO permits connection to a 3.3 V embedded controller. Data rates up to 1 Mbit/s suit real-time coordination among motion controllers, sensors, and safety monitors. System designers should preserve the recommended return-path geometry, avoid long unprotected stubs, and place any protection network where it will not distort the intended bus impedance or unnecessarily slow edge rates.
Recommended
High-Speed CAN Gateway
The TJA1057GT/3J can form the physical-layer section of a CAN gateway or protocol bridge that links a modern 3.3 V processor to a high-speed vehicle or industrial network. The gateway processor handles protocol conversion, filtering, diagnostics, and data transformation, while the TJA1057GT/3J performs differential bus transmission and reception. The VIO input simplifies the logic interface, and the 1 Mbit/s rate supports high-speed CAN traffic. Gateway designs should separate digital and bus-return paths carefully, account for ground-offset effects, and include protection appropriate to the external cable and power environment.
Recommended
Recommended Products Summary
Engineering reference data for TJA1057GT/3J — comparison, design guidance, and compliance information.
Selection Guide
Comparison with Alternatives
| Parameter | This Product | TJA1057GT/3 | TJA1057BT/3 | TJA1057T/3J | TJA1022HGZ | TJA1027T/20/2Z |
|---|---|---|---|---|---|---|
| Manufacturer | NXP Semiconductors | NXP Semiconductors | NXP Semiconductors | NXP Semiconductors | NXP Semiconductors | NXP Semiconductors |
| Package | SOIC-8 (PDSO8) | SOIC-8 (PDSO8) - same | SOIC-8 (PDSO8) - same | SOIC-8 (PDSO8) - same | SOIC-8 (PDSO8) - same | SOIC-8 (PDSO8) - same |
| Product Function | Single-channel high-speed CAN transceiver | TJA1057 high-speed CAN transceiver | TJA1057 high-speed CAN transceiver | TJA1057 high-speed CAN transceiver | CAN transceiver | CAN transceiver |
Key Differentiators
- VIO-enabled logic-side interfacing (vs TJA1022HGZ)
- Single-channel 1 Mbit/s CAN physical layer (vs TJA1057T/3J)
- Established 8-pin SOIC footprint (vs TJA1027T/20/2Z)
- Standards-aligned high-speed CAN operation (vs TJA1027T/20/2Z)
Design Notes
Connect VIO to the same supply rail used by the CAN controller so TXD and RXD use the intended 3.3 V or 5 V logic levels. Route CANH and CANL as a coupled differential pair with a continuous ground reference beneath the pair. Avoid adding long stubs, sharply diverging the traces, or routing the bus through areas of high switching current; these practices reduce common-mode disturbance and help preserve the intended CAN edge behavior.
Treat the transceiver supply and VIO rail as separate design domains. Verify the exact absolute-maximum and operating limits from the manufacturer datasheet, then confirm that both rails remain valid under normal operation, bus dominant/recessive states, and fault recovery. The supplied data confirms the functional purpose of VIO but does not include the numerical supply ranges, so those limits must be obtained from NXP before component selection and protection design.
Do not treat an SOIC-8 CAN transceiver as a complete bus protection solution. Vehicle and industrial CAN cables can receive electrostatic discharge, surge, or induced transients that exceed nominal operating conditions. Select external protection only after checking its capacitance, clamp behavior, and impact on bus communication. Also verify the complete numbered pinout because the verified results establish PDSO8 packaging but do not provide a complete pin-by-pin table.
Place the transceiver close to the CAN connector and protection components to minimize the unprotected portion of the external bus path. Maintain a low-impedance ground connection between the transceiver ground, controller ground, and cable shield or return reference. Follow the manufacturer datasheet layout and component-placement guidance for input and output decoupling; do not infer capacitor values or placement from generic CAN examples because the verified data does not specify them.
Compliance Information
The retrieved comparison results mention RoHS and REACH as comparison fields, but the supplied data does not state their results. AEC-Q100, lead-free, halogen-free, and conflict-minerals status also remain unverified.
