CAN transceiver obsolescence: which parts are EOL & how to cross them
The high-speed CAN transceiver is one of the most standardized 8-pin parts in industrial and automotive electronics, and two of the most common legacy parts are now obsolete: the Microchip MCP2551 (SOIC-8) and the NXP TJA1050. The same 8-pin outline hides the two things that actually decide a swap: the supply rail (5V vs 3.3V) and the function of pin 5. A footprint match tells you neither. Suggested candidates to validate in your own design, not drop-in equivalents.
The family map
Every legacy part routes to a same-vendor go-forward that keeps the 5V rail and has a documented migration, or out to a wider pool where the supply rail and pin-5 function change. The two load-bearing axes are the rail and pin 5; the arrow keeps the rail, never the pin-5 function.
migration
family
Two kinds of risk on the board
There is the obsolescence you came for, and the one you can design straight back in. Check both before you standardize on a cross.
The named obsolescence
The MCP2551 is obsolete in its SOIC-8 package (-I/SN) per distributor lifecycle flags; the PDIP-8 has historically shown Active or NRND, so confirm the exact package. The TJA1050 reads END OF LIFE at NXP: the last-standing orderable (TJA1050T/CM,118) carries that status and no active TJA1050 orderable remains.
Confirm the exact package & orderableThe one you design back in
Several parts a cross-reference suggests are themselves late in life. The most-searched TJA1050 cross, the TI SN65HVD230, is active but TI now offers a newer pin-for-pin part (TCAN332), and its legacy SN65HVD230D tube orderable shows Obsolete at distribution.
Check every candidate’s own statusA footprint-and-function match tells you nothing about whether the candidate outlives your redesign. Two of the most common legacy crosses (MCP2551, TJA1050) are already obsolete or end-of-life, and a third (SN65HVD230) has a newer generation, so the obvious cross can carry its own obsolescence.
The four catches that decide every cross
Supply rail: 5V vs 3.3V Load-bearing
The same 8-pin outline covers 5V parts (MCP2551, MCP2561, SN65HVD251, TJA1050, TJA1051) and 3.3V parts (SN65HVD230). Sharing the outline does not share the rail: the supply and the logic-interface levels move with it, not just the part number.
Pin 5 function Load-bearing
Across the family pin 5 is VREF, SPLIT, a logic-supply (VIO) pin, or an enable pin, and one base number can split by suffix: the TJA1051 ships as T (n.c.), T/3 (VIO) and T/E (enable). A cross-reference treats “TJA1051” as one part; the suffix is not a filterable column.
The cross’s own lifecycle
A footprint-and-function match tells you nothing about whether the candidate will outlive your redesign. Confirm each candidate at its own maker status field before you standardize on it. The obvious cross can be next.
Controller vs transceiver
The common query tja1050 vs mcp2515 compares a transceiver with a stand-alone CAN controller (the MCP2515, an SPI device). They pair together in the CAN node. A controller is not a transceiver replacement.
The CAN transceiver landscape
The common parts a cross-reference returns, mapped by the two axes that decide the swap, supply rail and pin 5, and by their own lifecycle. Confirm every standing at the maker field before you design a part in; a distributor flag can sit on one orderable while another is active.
| Part | Vendor | Supply rail | Pin 5 | Lifecycle |
|---|---|---|---|---|
| MCP2551 | Microchip | 5V (4.5-5.5V) | VREF | Obsolete SOIC-8 |
| MCP2561 | Microchip | 5V (4.5-5.5V) | SPLIT | Active TB3101 cross |
| MCP2562 | Microchip | 5V (+VIO 1.8-5.5V) | VIO | Active |
| SN65HVD230 | TI | 3.3V | Vref | Active newer TCAN332 |
| SN65HVD251 | TI | 5V | VREF | Active clean 5V cross |
| TJA1050 | NXP | 5V (4.75-5.25V) | Vref | EOL no active orderable |
| TJA1051 | NXP | 5V (4.75-5.25V) | n.c. / VIO / EN by suffix | Active |
| TJA1057 | NXP | 5V | VIO on GT/3 & BT | Active ISO 11898-2:2024 |
The two load-bearing columns are the supply rail (the SN65HVD230 is 3.3V where the others are 5V) and pin 5 (five functions across the family and, on the TJA1051, across ordering suffixes of one part number). Lifecycle, rail and pin-5 data is vendor/distributor-reported, not independently audited.
The per-part teardowns
Each legacy part has a full forensic teardown: the fit-catch on every cross, the comparison table, and the procurement path:
Microchip · obsolete SOIC-8
MCP2551 replacement: MCP2561, SN65HVD230 & SN65HVD251 compared
The obsolete Microchip part, its same-vendor successors (with the pin-5 change), and the clean active 5V cross, worked in full.
NXP · end of life
TJA1050 replacement: the TJA1057, TJA1051 & SN65HVD230 crosses
The end-of-life NXP part, the pin-5 variant split by ordering suffix, and the 3.3V rail change on the most-searched cross.
How to approach a CAN transceiver obsolescence
No single winner across the family, a fit to your design, your logic rail, and your program:
Stay same-vendor where a migration exists Lowest friction
Microchip’s TB3101 covers MCP2551 to MCP2561; staying in-family carries the least requalification. Account for the pin-5 change (VREF → SPLIT) even so.
Match the rail first
Settle 5V versus 3.3V before the footprint. The 8-pin outline is shared; the rail, and the logic-interface levels with it, is not.
Confirm pin 5 against the exact suffix
Not the base part number. The ordering suffix that matches your controller rail and netlist (e.g. TJA1051T vs T/3 vs T/E) is the one to order.
Check the candidate’s own lifecycle
At the maker status field. Two of the most common legacy crosses are already obsolete or EOL and a third has a newer generation, so the obvious cross can carry its own obsolescence.
Requalify in your own system
A matching footprint and CAN standard do not qualify the part; validate the bus common-mode range and fault tolerance against your actual network.
Procurement
For an EOL or obsolete part, buy only from franchised distribution or a traceable authorized source; sequence any last-time-buy against the design-in of one named cross, and budget a requalification regardless of which cross you pick.
Frequently asked questions
Which CAN transceivers are obsolete?
The Microchip MCP2551 is obsolete in its SOIC-8 package, and the NXP TJA1050 is end-of-life with no active orderable remaining at NXP; the NXP TJA1040 is also end-of-life. Confirm the exact package and orderable you use, because a lifecycle flag can differ between the SOIC and PDIP versions of the same part.
Are CAN transceivers pin-compatible?
They share a common 8-pin footprint, but that does not make them interchangeable. Across the family the supply rail (5V or 3.3V) and the function of pin 5 (VREF, SPLIT, VIO, enable, or not connected) both change, so a footprint match can still be a rail or logic-level mismatch.
Is the MCP2515 a CAN transceiver?
No. The MCP2515 is a stand-alone CAN controller with an SPI interface, a different device in the CAN node than a transceiver. A controller and a transceiver pair together rather than substitute for each other.
What is the difference between a 3.3V and a 5V CAN transceiver?
The supply voltage and the logic-interface levels differ. The same 8-pin outline covers both, so crossing between them (for example from a 5V MCP2551 or TJA1050 to a 3.3V SN65HVD230) changes the supply rail and the logic levels, which is a redesign consideration, not a footprint swap.
What replaces the TJA1050 and the MCP2551?
Each has its own set of real crosses with a specific catch; the two teardowns linked above work them in full. In short: the TJA1050’s crosses are the NXP TJA1057 and TJA1051 and the TI SN65HVD230 (the rail changes on the last), and the MCP2551’s are the Microchip MCP2561/MCP2562 and the TI SN65HVD251 (the clean active 5V cross) and SN65HVD230. Treat all as candidates to validate.
Keep reading
Sources · public, primary
- Microchip MCP2551 datasheet (PDF)
- Microchip MCP2562 product page + MCP2561/2 datasheet (PDF)
- DigiKey MCP2551-I/SN lifecycle & stock page
- NXP TJA1050 product page (END OF LIFE) + datasheet (PDF)
- NXP TJA1051 datasheet + TJA1057 datasheet (PDF)
- TI SN65HVD230 product page + datasheet (PDF)
- TI SN65HVD251 product page + datasheet (PDF)
- Microchip MCP2515 (stand-alone CAN controller, SPI)
Lifecycle, supply-rail, pin-5 and status data is vendor- and distributor-reported, not independently audited. Alternates are candidates to validate in your own design; confirm every detail with the manufacturer before committing.
About the author