How to Use Topdon Rlink X7 for Nissan Software?

 Topdon Rlink X7/Rlink J2534 works great with Nissan software. Nissan recommends it and not expensive.

Here we will show how to install driver and set up Rlink for Nissan OEM software.

1. Open the RLink Platform and click Login, it will automatically jump to the login screen upon the first use. Log in to the account bound to the RLink device.
Note: After binding and activating the device and downloading the driver, you can use the RLink device to perform vehicle diagnostics without opening the RLink Platform later.

2.   Click the settings icon. Then click About to check whether there is an update for the RLink Platform. If yes, click Update.

3. Click Driver Management > Driver Download. (Download the corresponding driver according to the OEM software. Do not download drivers that are not related to the OEM software.)

4. Click NISSAN and click Download to download the driver.


5.  Click Driver Management > Driver Info. Then click NISSAN to check the driver mode.

6. There are two driver modes for NISSAN.

To use RLink device for diagnostics, select RLink mode.

To use the original VI2 device for diagnostics, select VI2 mode (restore the original driver mode).
Note: For the RLink J2534, the J2534 driver is the automatic default driver. You do not need to select the driver mode here.

7. Double click the icon to open the Nissan software.

8. Choose RLink driver mode following the order below.
Select VI/MI- VCI- Rlink- Connect.



9.  After selecting the driver, the VCI status will turn green. You can start vehicle diagnostics.

AutoTuner Adds Ford Continental EMS2701 ECU Beta via OBD

 The Continental EMS2701 ECU is now supported in Autotuner OBD BETA for Ford vehicles. 

This protocol enables a real reading of the actual calibration stored in the ECU via the vehicle's OBD port. This means you access the ECU's real content, whether it has been modified before or not.

Since this is a BETA release, we rely on your feedback to identify any possible improvements. Test it out and let us know what you think! 

Key Features:

Type: Engine Control Unit (ECU).

Readout: OBD NR.

MCU: TC1791.

Read time: 4min 15sec.

Write time: 1min 45sec.

Checksum correction.

VNCI 6154A Update Firmware 1.1.7.5

 A new firmware V1.1.7.5 has been released and you can update the VNCI 6154A red dongle interface without the old/reported problems.

VAS6154A device manager 1.1.7.5

• Fix bug: KWP2000 concate timing P2.

Previous Firmware Version 1.1.6.6
Add support for remote diagnosis.

What makes the VNCI 6154A better than alternatives like the VCX SE and VAS 6154 clone?

• – VNCi 6154A best quality ( support Online , tested in Online and Offline )
• – Works with original driver
• – updatable
• – VCX SE works as VAS 6154, but VNCI will emulate VAS 6154A
• – This should work best, supports DOIP and CAN FD
• -it is a very good choice. Works just like original VAS6154A.

Autel or FDRS to Program Ford Bronco 2023 Smart Key

 2023 Ford Bronco all keys have lost, no bypass cable/adapter, possible with Autel IM608/OBDSTAR via OBD or FDRS is needed for this model?

If it is Bronco Sport, Autel IM608 can add key via OBD. If it is a regular Bronco, Autel cannot do it via OBD.

 

Remove BCM, check if BCM like the BCM picture in Autel.

If yes, it can read pin code from BCM dump.

Remove BCM read flash data with ABP131 RH850 adapter, then load file add key or do all keys lost.

Then program key by OBD after loading data.

 

OBDSTAR X300 Classic G3 also has an RH850 adapter for Ford RH850 BCM. Read flash data with RH850 adapter. G3 will read pin from dump. Then load file to add key or do all  keys lost via OBD. But OBDSTAR only supports R7F701573 BCM, not all variants.

Obdstar Ford Bronco 2023

AVDI + RH850 programmer will also do Bronco 2021+ all smart key lost by dump.  Same as Autel and OBDSTAR,  Abrites only supports some BCMs, but not all variants.

If it is MU5T BCM, there’s no aftermarket tool support by OBD, get FDRS.

FDRS is the easiest and safest way. Use cheap Autel VCI200 J2534, JVCI+ or other J2534 passthru device with FDRS.

Clone BMW MEV17.2.2 DME and Read ISN with Yanhua ACDP

 Question: 

Have a damaged MEV17.2.2 DME for a Mini Cooper. Possible to clone the DME with Yanhua Mini ACDP2? Bought a used DME with the same Bosch number and DME number.  also for key programming ISN reading by bench/adapter?

 

Here is the clue.

Part 1: Clone BMW MEV17.2.2 DME

You cannot read and write data to clone this DME. It will not overwrite OTP sector.  This ECU has an OTP area.

If doing this way, ACDP will give error “DME communication failed”.

You have to replace DME ECU to clone the DME. Perform “Read/Write CAS ISN to replace DME” function.
Need to disassemble DME and do it in boot mode to clone this DME.

Check the connection diagram and follow instructions in ACDP.

 

Part 2: Read MEV17.2.2 DME ISN Code

Yanhua ACDP will read ISN code for key programming by adapter without problem.

With jumper adapters in module 3.

In BMW DME ISN function, select Read N18 (MEVD1722) DME ISN function.

Check the connection diagram.

Step 1: Prepare ACDP, PCAN-II cable and DME.

Step 2: Check connection pinout.

Step 3: Short the jumper cap to the “CAN-R” position.

Step 4:  Connect the ACDP, PCAN-II cable and DME.

Then read DME ISN code.

Top J2534 Passthru for FCA wiTech 2.0 OEM Programming

 Question:

Can I use the Scanmatik 2 Pro as a J2534 passthru for FCA Witech 2.0 reflash and programming? or other passthrough tools like VXDIAG VCX SE, Autel J2534?

The below table shows the device that are verified for use with wiTECH2.0. These devices also support the new CAN FD communication protocol.

The best passthru for witech should be CarDaq3. witech really really likes cardaq3.

Many vehicles have 3 CAN buses which require a J2534 device that supports 3 hardware CAN channels. Please make sure your J2534 device supports 3 CAN

channels before purchasing a wiTECH 2.0 Subscription.

Windows 10 is the only operating system that is supported by wiTECH 2.0 J2534 Application.

Any 3rd party J2534 cables that are compatible with wiTech 2.0 FCA official?

Micropod2 clone can ONLY be used offline and ONLY for up to 2018 year.

Any newer than 2018, or if you need to flash ECU (which is online only for witech) you must purchase a wiTech sub, a TechAuthority sub, and a ECU flash sub. You can register your J2534 program in the wiTech portal once you sign up.

Some other J2534 interfaces also work with the TechAuthority programming subscription.

It’s actually 3 fees you need to pay to re-program:

• 1) TechAuthority subscription
• 2) WiTech subscription
• 3) Programming subscription

Techauthority and Witech can be paid by day and the programming fee is for 1 year for 1 VIN so it means you can program any module in the car.  That allows you to do everything a dealer can do. Coding, Resetting, VIN change, bi-directional use and anything that doesn’t require you to flash/program.

The subscription is for 3 days and you can download the j2534 software once you log in.

You can do diagnostic with just the Witech 2.0 daily pass ($50), but to program, you need the Techauthority subscription as well (additional $35).  In total you spend like $120 USD, it’s not much but the registering process is a bit complicated as you need to register in 3 different places and authorize your tool.

It needs internet connection to be used with J2534 version.

VXDIAG VCX SE/VCX FD: No

VXDIAG is license-based device; it does not support the Chrysler license yet.

Topon Rlink X7/Rlink Lite: Yes

Rlink X7 is also a license-based device similar to VXDIAG. Topdon released the Chrysler license. So it can be used as J2534 passthru device for wiTech 2.0 OEM software.

Check how to set up Chrysler driver in Topon Rlink manager tool.

How to set up Topdon Rlink J2534 with wiTech 2. OEM Software

Scanmatik 2 PRO (SM2 Pro): No

No success yet. It works perfectly for every other OEM software except Witech 2. If input the VIN manually, Scanmatik can read and flash 1 of the CAN nodes just fine, but won’t detect the most important modules such as the PCM, BCM, TCM etc. If the car has 3 can nodes, it only communicates with one. SM2 pro does not support CAN FD. Has to be can fd capable.

Openport 2.0: No

No success. The original Openport supports the following programs: FCA wiTech 2 is not supported. It does not support CAN FD protocol either.

Launch Smartlink: Yes

It’s not listed as supported J2534, but it works.  Launch Smartlink C acts as a VCI with J2534 capability, supporting almost all car brands Mer, BMW, VW, FORD, PORSCHE, Chrysler etc.

Read also: http://blog.obdii365.com/2023/09/07/set-up-launch-smartlink-c-with-witech-2-0/

Autel J2534: Depends

It’s not in the list of approved jboxes, but it works.  But slower than Cardaq.

The old gray Elite MaxiFlash J2534 does not support CAN FD protocol, some users may have trouble communicating new CAN FD models with it.

In older car models it lets you plug in and do programming, newer models have to be another CAN FD interface.

 

You need the newer autel passthru, the new JVCI+ J2534 or VCMI interface that support CAN FD protocol. The VCI200 J2534 also works. Restart the computer and try different USB plugs until it works.

Read also: http://blog.obdii365.com/2023/08/28/autel-maxiflash-j2534-not-detected-by-witech-2-0/

Keep updating…

KESS3 Update Hyundai SIM2K-142 SIM2K-143 SIM2K-245 ECUs

 Alientech KESS3 released new ECU and TCU Protocols for Hyundai and Kia with Continental SIM2K-142, -143 and -245 Control Units.

Read, write, and clone in BOOT mode* the Continental SIM2K-142, SIM2K-143, and SIM2K-245 ECUs and TCUs, installed on 2.0 MPi and 2.4 MPi engines. This is an effective solution for professionals who work daily on vehicles that have been on the market for over 10 years and may now require your tuning expertise.

With this update, you can operate directly on the SIM2K-143 and SIM2K-245 engine and automatic transmission control units, enabling full reprogramming or advanced repair operations. You gain full access to the memory content: adjust parameters, fix specific malfunctions, or clone the entire ECU or TCU for fast and efficient replacement.

Supported vehicles with 2.0 and 2.4 MPi engines:

• Hyundai – Azera, Grandeur, Grand Starex, H-1, Sonata, Starex
• Kia – Cadenza, Optima, Carens

* BOOT mode with KESS3 requires opening the control unit to make direct contact with the PCB. This allows full access to the memory for complete readout, write and clone operations. A technical procedure that demands experience, but guarantees maximum control during reprogramming.

BMW MSV90 DME Repair Tips

 How to repair BMW (N52 engine) Siemens/Continental MSV90 DME?

First of all, check the MSV90 DME internal components:

1.  DME internal error 

• Software Issues:

  Software errors within the MSV90 module can lead to incorrect engine operation, potentially causing the “internal fault” error.

• Programming Errors:
• If the ECU’s programming is corrupted or improperly configured, it can result in a “syntax error” and trigger the fault code.

If have an internal error on MSV90, most internal faults are caused by poor soldering (cold joints) on this CPU. Simply re-solder the chip will resolve the issue.

For syntax/communication errors: Re-solder the CPU or perform reprogramming of both the Engine ECU and CAS module. There are many tools to read this ECU, OBDSTAR DC706, CG FC200, Yanhua ACDP, Xhorse Multi Prog etc.

2. BSD failure

2E7C BSD communication fault.

The DME (Digital Motor Electronics) MSV90 BSD (Bit-Serial Data Interface) is a crucial component of your BMW’s engine management system. Breakdowns in this system can cause various issues, such as poor engine performance and misfires.

To repair BSD failure issue, need to drill a hole on the MSV90 DME board.  Replace the TJA1020 IC chip within the marked area.

3. Barometric Pressure Sensor Signal Fault

Fault code: P2227

Re-solder SMD288 PIN marked red below.

4. Throttle Fault code

Re-solder or replace ATIC61D3 control IC
Check the transistor for burn damage; replace if faulty.

5. Terminal 15 (KL.15) fault code

1B5102 fault code: specifically a fault related to Terminal KL.15, indicates a problem with the ignition power supply or the ignition switch.

A fault with MSV90 Terminal KL.15 (also known as Terminal 15) on a BMW, specifically in the context of an MSV90 ECU (Engine Control Unit), usually indicates a problem with the ignition or power supply to the ECU.It can manifest as no voltage at the DME input despite the main relay being enabled, or a disruption in the CAS (Car Access System) power supply. The root cause can range from a low battery, an unauthorized consumer drawing power, or a problem with the CAS module.

 

To solve the KL.15 fault, re-solder the fuel injector/fan integrated chip ATIC94D marked red below.

Keep updating.

 

Autel MaxiDiag MD906 Pro and MD808 Pro Comparison

 What is the difference between Autel MaxiDiag MD808 Pro and 2025 new MD906 Pro?

Check the table comparison below:

Model		Autel MD808PRO	Autel MD906PRO
Hardware	VCI	Cable	V150 Lite
	System	Embedded system	Android 9
	Battery	NA	5000mAh
	Storage	16G	64G
	Screen	4-inch	5.5-inch
Function	Vehicle Coverage	Current year vehicle of Asia, Europe, America, China	Current year vehicle of Asia, Europe, America, China
	System Coverage	All	All
	Read/ Erase Code	●	●
	Live Data	●	●
	Security Gateway	NA	FCA, SFD, Nissan, etc.
Service	OIL RESET	●	●
	BREAK BLEEDING	NA	●
	INJECTOR	NA	●
	SAS	●	●
	THROTTLE	●	●
	EPB	●	●
	BMS	●	●
	TPMS	NA	●
	DPF	●	●
	AFS Headlamp	NA	●
	A/F	NA	●
Communication Protocol	CAN FD	NA	●
Software	FREE Lifetime Software	lifetime of tool	lifetime of tool

In sum:

MD808 Pro connects via USB while MD906 Pro supports Bluetooth connection via V150 BT adapter.

MD906 Pro has a larger battery and storage memory.

MD906 Pro supports extra 5 special functions than MD808 pro, including SAS, Throttle, EPB, BMS, and DPF reset.

PADFlash Read and Write PSA EDC17C60 via OBD!

 The PADFlash progammer has OBD solution for PSA BOSCH EDC17C60 ECUs installed on brands like Citroen, Peugeot, Opel, DS.

 

EDC17C60 PSA – OBD (Flash+Eeprom) OK.

It’s like the flex doing a full backup obd.

No other aftermarket tool can do OBD on EDC17C60. Most of them do it on bench, such as OBDSTAR DC706, FC200, Launch X-prog3 etc.

No more on table, full read write via obd. It allows you to fully work on BOSCH EDC17C60 ECUs directly from OBD socket! As of now, it is possible to read and write the MICRO + EEPROM data via OBD.

It also does it on bench mode.

PADFlash has online support via Whatsapp 7 days per week. Only tool owners have access for tool support.
Tool has all the listed protocols as advertised.