2026/06/02

Ford 4D63 40bit vs 4D83 80bit

If you work with Ford or Mazda vehicles, you’ve likely encountered two common transponder chip types: the ID83 (4D-DST80) and the ID63 (4D-DST40).  Here we will make a comparison between 40-bit and 80 bit transponder chips in Ford PATS systems 2005-2011.

 

Why Convert Instead of Generating?

Most modern key programming tools allow you to generate a new chip of any type. However, there are situations where you might already have a specific chip on hand — for example, a DST80 — but your vehicle requires a DST40. Instead of discarding the chip or searching for a different blank, you can reconfigure it manually/automatically using the right device.

This is especially useful for locksmiths and auto technicians who buy chips in bulk and want maximum flexibility.

 

1. QUICK GUIDE
Ford 40-Bit ↔ 80-Bit (When the Key WON’T Program)
For technicians just starting out who get stuck without knowing why

The Problem (More common than it seems)
In certain Ford models between 2005 and 2011 (Especially the Ranger and F-150):
– The key appears to be the correct one
– The procedure is correct
– But it simply won’t program

DIAGNOSTIC SIGNALS

  • The key turns but the engine doesn’t start
  • Security light flashes rapidly or stays on
  • The scanner does not recognize the key as programmed
  • Error appears during programming or it doesn’t complete
  • Another key works without problems

Often, it is NOT the equipment.
It is NOT the procedure.
It is the transponder’s bit type.

 

A Key Fact Few People Know:
40-Bit → Reads as 4D (63)
80-Bit → Reads as 4D (83)

Typically, H92 keys or equivalents are used.
However, the system sometimes requires the other bit type.

 

2. Practical Solution:
Switch from 40-bit to 80-bit.
Or from 80-bit to 40-bit.
There isn’t always a logical explanation, but it works in practice.

 

VISUAL CHECK FLOW
  1. The key won’t program
  2. Reads the transponder
  3. Verifies 40 Bit or 80 Bit
  4. Converts the necessary bit
  5. Tests and verifies programming
  6. Solution completed

40 BIT
4D (63)
80 BIT
4D (83)
Identification in Xhorse4D (63)4D (83)
Common UseMost frequentLess frequent
CompatibilityNot compatible with 80 BitNot compatible with 40 Bit
Ford Systems (2005–2011)Some modelsSome models
SolutionConvert to 80 BitConvert to 40 Bit

Chips Explained

Chip IDCommon NameMemory TypeTypical Use
ID834D-DST8080-bitFord, Mazda (older models, some F150s)
ID634D-DST4040-bitFord, Mazda (different immobilizer versions)

BEST PRACTICES BEFORE REPLACING COMPONENTS

  • Always verify the bit type (40 or 80).
  • Confirm the transponder with a reliable tool.
  • Try converting the bit before buying another key.
  • Ensure stable batteries and good connection are used.
  • Do not install new parts without first ruling out bit incompatibility.

 

3. STEPS (Using Xhorse Key Tools, i.e Key Tool Max)
Bit Conversion Without Re-reading the Key or Transponder
1). Go to “Clone Transponder”
2). Select “Read Transponder”
3). Tap “Edit” (bottom center)
4). Select “DST+”
5). Scroll down to the very bottom
6). P30 must be set to 0000
DO NOT re-scan the key or transponder
7). Tap the zeros and enter:
0046 = Convert to 40-Bit
0846 = Convert to 80-Bit
8). Tap “OK”
9). Tap the pencil icon (on the right side)
10). You should see: “Write Complete”.

 

Can You Convert Back?

Yes. The process works in reverse. If you need to turn a DST40 chip back into a DST80, follow the same steps but change the value from 0046 back to 0846 (or whatever your tool requires for DST80). The Xhorse Key Max allows two-way conversion between these two chip types.

xhorse convert ford 4d63 to 4d83 1

xhorse convert ford 4d63 to 4d83 2

xhorse convert ford 4d63 to 4d83 3

xhorse convert ford 4d63 to 4d83 4

xhorse convert ford 4d63 to 4d83 5

xhorse convert ford 4d63 to 4d83 6

STEPS (Using Keydiy Key Tools, i.e KD-X2/KD-X4)

1). Read Transponder

2). Select “Chip Editing”

3). Select “DST+”

4). KD will will give you options: select “Convert to DST40” or “Convert to DST80”

5). Hit “Agree”

6). Exit and auto detect transponder again.

Keydiy tools also allow two-way conversion between these two chip types.

keydiy convert ford 4d63 to 4d83 1

keydiy convert ford 4d63 to 4d83 2

keydiy convert ford 4d63 to 4d83 3

keydiy convert ford 4d63 to 4d83 4

keydiy convert ford 4d63 to 4d83 5

Final Verification
Return to “Clone Transponder”
Read the transponder again
Confirm that it now shows as 4D (63) or 4D (83), depending on your requirements.

 

Key Tip for Future Programmers
If a Ford key fails to program:
DO NOT buy a replacement just yet
Check the 40 / 80-Bit setting first.

 

Important Tips

Not all chips are rewritable. This method works with cloneable DST80 and DST40 chips. OEM or locked chips may not allow manual overwriting.

Write, don’t Convert. Some tools have both a “Convert” and a “Write” function. For manual editing, always use Write after changing values.

Generate as an alternative. If you don’t have a chip to convert, the Xhorse tool can also generate a brand-new DST40 or DST80 chip from scratch. Conversion is just one option.

www.obdii365.com

2026/06/01

Autotuner Adds Toyota Denso Gen3 R7F701202 ECU by OBD

Toyota & Lexus Denso Gen3: Live via OBD & Bench!

A colossal update has arrived on your AutoTuner Tool! The highly anticipated Denso Gen3 ECU (R7F701202) is now fully supported.

Get ready to flood your workshop with one of the best-selling car brands in the world! We are extremely proud to announce a massive update: the Denso Gen3 ECU (R7F701202 microcontroller) is now officially supported on your AutoTuner Tool.

This release covers a gigantic portion of the modern Asian car park. Whether your customers are looking for more towing torque in their diesel workhorse or engine optimization for their daily hybrid commuter, you now have the ultimate solution.

Methods: OBD & Bench (Normal Read / Virtual Read). Enjoy absolute flexibility! Identify and flash the vehicle directly through the OBD port with Virtual Read (VR) support, or work on the Bench with a full Normal Read (NR) depending on your workflow.


Supported Highlights:

  • 4x4s, Pick-ups & Commercial (2.4 & 2.8 D-4D): Toyota Hilux, Land Cruiser, Prado, Fortuner, HiAce, Innova.
  • Sedans & SUVs (2.0 & 2.5 Petrol/Hybrid): Toyota RAV4, Corolla, Camry, Avalon, Crown, Sienna...
  • Premium Lexus Range (2.0 & 2.5): Lexus ES, NX, UX.

Update your Tool today and tap into the phenomenal tuning demand for these notoriously bulletproof vehicles!

Key Features

  • Type: Engine Control Unit (ECU) 
  • Mode: OBD & Bench NR/VR - Tool 
  • Readout: Calibration 
  • MCU: R7F701202 
  • Read time: 35min 
  • Write time: 4min 45sec 
  • Checksums correction 
  • Backup creation 
  • Secure Gateway present 

Compatibility List*

Lexus Models: ES (2018) / NX (2022) / UX (2018)
Lexus Engines: 2.0 / 2.5
Toyota Models: Auris - Blade (2018) / Avalon (2019) / Camry (2001) / Corolla (2018) / Crown (2018) / Fortuner (2020) / Harrier (2020) / HiAce (2004 – 2019) / Hilux (2015 – 2020) / Innova (2020) / Landcruiser (2015 – 2018) / Prado (2021) / Rav4 - Wildlander (2012 – 2018) / Sienna (2020) / Venza (2020)
Toyota Engines: 2.0 / 2.0 CVT / 2.5 / 2.4 D4-D / 2.8 D-4D / 2.8 D-4D GR

Autotuner Adds Toyota Denso Gen3 R7F701202 ECU by OBD

Q: Does bench do a full backup? Is there a recovery mode?

A: This ECU does not have a recovery mode, but Autotuner has developed a robust protocol designed to prevent the most common user mistakes.

 

Q: After mail unlock?

A: No, it’s normal release.

 

Q: OBD NR or VR?

A:  OBD VR, Bench NR.

 

Q: What read & write times?

A: Read time: 35min
Write time: 4min 45sec.

 

Q: if there are any plans for future support of Toyota Denso Gen2 ECUs based on the following Renesas MCUs:
– D76F0199GD – 1280 KB
– D76F0196F1 – 1536 KB
– D76F0198F1 – 1536 KB
– D76F0219F1 – 2048 KB

A: These MCUs are already covered by our Toyota Gen2 bench protocol.

 

 

2026/05/28

Dimsport The Genius Adds Ford SID212 Protocol

Here is the long-awaited SID212 protocol. Dimsport The Genius has now released Ford SID212 protocol.


The following protocol is available ONLY on The Genius tool!

CAR/LCV

NEW: FLASH_0994 FORD CONTINENTAL SID212 TC297 CAN R/W

  • FORD EVEREST 2.0L ECOBLUE 157kW
  • FORD FOCUS Mk4 2.0L TDCi 110kW
  • FORD GALAXY 2.0L TDCi 110/140kW
  • FORD MONDEO 2.0L TDCi 88/110/140kW
  • FORD RANGER Mk3 Facelift 2.0L TDCi 157kW
  • FORD TRANSIT 2.0L TDCi 95/125kW
  • FORD TRANSIT CUSTOM 2.0L TDCi 77/95/125/140kW

Dimsport The Genius Adds Ford SID212 Protocol

2026/05/26

EoneBoss TLK1 Failed to Unlock Toyota 8A A9 Smart Key?

Problem:

Failed to unlock a 2018 Toyota 8A smart key with EoneBoss TLK1 remote unlock device. However, it did a 2022 8A model. Any idea?

EoneBoss TLK1 Failed to Unlock Toyota 8A A9 Smart Key 1

EoneBoss TLK1 Failed to Unlock Toyota 8A A9 Smart Key 2

Solution:

The P4 page of this 8A smart key is A9.

EoneBoss TLK1 will unlock original Toyota/Lexus 8A 8A-AA BA B9 B8 smart keys.  It cannot unlock original 8A A9 smart key.

Use other device instead.

ID46 vs. PCF7936 vs. Hitag2 Chip

ID46 vs. PCF7936 vs. Hitag2, these are three names that MANY people use as if they were one and the same.
And they are NOT.
In fact, confusing them can ruin a job.

Because:

  • some are referring to the transponder ID
  • others to the physical chip
  • others to the internal technology

And that is where it starts:

  • incorrect purchases
  • ailed clones
  • stalled programming

 

ID46 vs PCF7936 vs Hitag2

FeatureID46PCF7936HITAG2
ManufacturerPhillipsPhillipsNXP (formerly Philips)
Frequency125 kHz125 kHz125 kHz
TypePassive RFID transponderPassive RFID transponderPassive RFID transponder
ChipPCF7936PCF7936 / PCF7936AA / PCF7936ASHitag 2
MemoryRead-onlyRead-onlyRead-only
SecurityMediumMediumMedium-High
Main useImmobilizersImmobilizersImmobilizers
Cloning/CopyingYes (with compatible equipment)Yes (with compatible equipment)Yes (with compatible equipment)
RewritableNoNoNo

ID46 vs PCF7936 vs Hitag2

Brand & Models

ID46 (PCF7936)PCF7936HITAG2
Toyota (some models)
Lexus (some models)
Subaru (some models)
Honda (some models)Used mainly in Japanese and Asian models
VW, Audi, BMW, Peugeot, Citroen, Fiat, Renault,
Opel, Benz (some models)Very common in European brands.
Benz (Some models)
Ford (Some models)
Volvo (Some models)
Land rover (some models)
Used in European and some American brands

 

When are they interchangeable and when not?

Interchangeable in some cases

  • ID46 and PCF7936 can be compatible in vehicles that use the same immobilizer system.
  • Depends on the system, year and immobilizer configuration.

NON-Interchangeable

  • Hitag2 is not compatible with ID46 or PCF7936. It has a different protocol.
  • Using the wrong transponder = the vehicle does not recognize the key,

 

Quick Reference Table

ModelFrequencyChipMemoryManufacturerCross CompatibilityMost Common Vehicles
ID46125 kHzPCF7936Read-onlyPhillipsCompatible with PCF7936 in some casesToyota, Lexus, Subaru, Honda (some)
PCF7936125 kHzPCF7936 / PCF7936AA / PCF7936ASRead-onlyPhillipsCompatible with ID46 in some casesVW, Audi, BMW, Peugeot, Citroën, Fiat, Renault, Opel, Mercedes (some)
HITAG2125 kHzHitag 2Read-onlyNXPNOT compatible with ID46 or PCF7936Mercedes-Benz, Ford, Volvo, Land Rover (some)

 

NOTE: Always verify the correct transponder before programming. Using the wrong transponder = vehicle does not recognize the key.

 

Related item:

ID46 transponder chip (supports PCF7936)

VVDI super chip XT57B

Keydiy KD D26 super chip (supports PCF7936)

 

FYI: Some other transponder chip information/knowledge.

ID46 vs ID48

The question that most confuses beginners is this: How do the ID46 and ID48 differ if both are 48-bit chips?
The difference does not lie in the encryption level. It lies in the manufacturer and the protocol used.
The ID46 is Philips — Hitag 2. It was adopted by Renault, Fiat, Opel, BMW (in their CAS2 and CAS3 systems), and many others.
The ID48 is Megamos. It was developed specifically for the VAG Group — Volkswagen, Audi, Seat, and Skoda — and subsequently spread to Porsche, Volvo, and a few others.
These are parallel technologies from the same era. The base chip is different, the algorithm is different, and the equipment must recognize each one separately.
If your equipment states that it supports ID46 but makes no mention of ID48, it will not work on a Jetta. It’s as simple as that.

 

 

A Practical Reference: The Most Common Chips by Brand.

European vehicles:

Volkswagen and Audi: ID48 in models up to approximately 2013. ID49 AES on the MQB platform starting from 2014.
BMW: ID33 in EWS2 (1990s), ID44 in EWS3 and EWS4 (2000–2006), ID46 in CAS2 and CAS3 (2005–2012), ID47 in FEM and BDC (2012 onwards).
Renault: ID46 across practically the entire lineup since 2000—including the Clio, Megane, Logan, and Koleos.
Peugeot and Citroën: ID45 in generations produced between 2000 and 2010. Do not confuse this with the ID46, even if the hardware appears similar.
Fiat: ID13 in older models; ID48 in newer models; and ID46 in intermediate generations, depending on the specific model.
Opel: ID40 in older models; ID46 in models produced after 2005.

This roadmap tells you exactly which equipment you will need before the vehicle even arrives.

 

 

The ID48 Trap: Before and After CAN
The ID48 chip has a peculiarity that creates problems for beginners:
Not all ID48 chips are programmed in the same way.
Prior to 2005, in VW vehicles, the ID48 operated without a CAN bus. With compatible equipment, the chip could be cloned directly, provided the original key was present. It was a relatively straightforward process.
After 2005, VW migrated its IMMO system to the CAN bus architecture. It uses the same ID48 chip, but programming is now performed via the OBD port and requires the equipment to communicate directly with the control module. It is no longer a simple matter of cloning.
Furthermore, in models featuring the IMMO4 system within the VAG Group, even OBD programming is insufficient in some cases—you require direct access to the control module or platform credits from providers such as Autel, VVDI, or Lonsdor.
The name of the chip remains the same, but the work involved is completely different.

www.obdii365.com