2020/03/27

SVCI 2020 Interface Not Connected Error Solution

Problem:
When install svci 2020 software on Win7 32bit system, it failed to load software and gave error:
“Connection Error: Interface not connected!
If you have already connected the interface, please try to reconnect it and restart the application.
The interface should be connected with a car. ”
svci-2020-interface-not-connected
Possible reason:
The usb driver is not compatible with windows system.
This problem will not occur if you install svci 2019 or svci 2020 software in win10 64bit professional.
The main reason is that the USB driver version is too low. By default, v2.12.28 version driver will be installed in the system, but this version driver cannot be successfully installed due to system reasons.
The solution is to update the USB drive v2.8.24 to v2.12.28.
Download

Detail procedure:
svci-2020-interface-not-connected-solution-1
Download USB FTDI v2.12.28 driver above and extract to desktop
1. Update USB Serial Port COM4 & COM5
svci-2020-interface-not-connected-solution-2

Go to computer device manager to check USB driver version
Right click on USB Serial Port COM4-Property
svci-2020-interface-not-connected-solution-3
COM4 USB driver version is too low
svci-2020-interface-not-connected-solution-4

Right click COM4 to select Search for the driver software on your computer
svci-2020-interface-not-connected-solution-5
svci-2020-interface-not-connected-solution-6

Choose driver software destination folder, replace COM4 FTDI driver in C:Users/Desktop/CDM v2.12.28 WHQL Certified_X64/ftdiport
svci-2020-interface-not-connected-solution-7
svci-2020-interface-not-connected-solution-8
Update COM4 Port driver succeed
svci-2020-interface-not-connected-solution-9
COM4 driver update to 2.12.28.0
Follow same step to update COM5 USB driver
svci-2020-interface-not-connected-solution-10
svci-2020-interface-not-connected-solution-11
2. Update USB Serial Converter A & B
svci-2020-interface-not-connected-solution-12
In Device manager, we need also update Controller USB (Universal Serial Bus). Update USB Serial Converter A and USB Serial Converter B
svci-2020-interface-not-connected-solution-13

USB Serial Converter A version is too low
Right click to select Search for the driver software on your computer
svci-2020-interface-not-connected-solution-14
Choose to install and replace driver in C:Users/Desktop/CDM v2.12.28 WHQL Certified_X64/ftdibus
svci-2020-interface-not-connected-solution-15
Update USB Serial Converter A driver succeed
svci-2020-interface-not-connected-solution-16
svci-2020-interface-not-connected-solution-17
Follow same step to update USB Serial Converter B
svci-2020-interface-not-connected-solution-18
Now SVCI 2020 software is ready to use.
svci-2020-interface-not-connected-solution-19


2020/03/26

How to Solve TangoPlus Toyota Error Payable Option ?

Problem:
I got the original Tango key programmer. When try to load TangoPlus Toyota software, it gave me error:
Error:
Sorry, payable option.
To continue it is necessary to install the Toyota Maker option.
tango-no-toyota-maker-license


Reason:
You don't have Toyota Maker license activated.


Solution:
After pay for the license. Add it to the tango software.
Go to Help tab-> Add Keymaker to add Toyota Maker license.
add-toyota-maker-license-to-tango

http://www.obdii365.com/producttags/tango.html

2020/03/24

Top 5 Tools to Repair BMW FRM3

Car model and year: BMW Mini E81 / E71 with FRM3 (BMW Footwell Module).

Purpose: repair BMW FRM3

Possible Tools to repair FRM3:
1.Xhorse VVDI Prog
2. Yanhua Mini ACDP
3. CG Pro 9S12
4. Hextag programmer
5.Xprog M Box



VVDI PROG repair FRM3: confirmed
I have not had any trouble yet with my VVDI prog.
When using vvdi prog, you must first write partition (choose dflash 0kb) and ALSO write your new eeprom file. Function Write partition does not write your .bin eeprom file.

Step-by-step procedure:
BMW E-series E71 for example.
Step 1: Read Dflash
Connect FRM module with VVDI-prog
Open VVDIprog software
Select MCU->Motorola -MC9S12->9S12XEQ384 unsecured
vvdi-prog-repair-frm3-1
If vvdi prompts “Partition information error, please select the partition size manually”
vvdi-prog-repair-frm3-2
Select the partition size EEE:0 sector, DFlash: 128 sectors (32K), press OK
vvdi-prog-repair-frm3-3
Read and then save Dflash, i.e E71 xe

Step 2: Dflash to Eeprom 
vvdi-prog-repair-frm3-4
Open Dflash to EEE for FRM3 Software, upload Dflash data just read
vvdi-prog-repair-frm3-5
Then convert Dflash to eeprom.
(You can use free online FRM3 D-Flash to EEPROM converter here as well:
Save eeprom, i.e: eee_L508991.bin

Step 3: Write EEPROM
Back to VVDI Prog software, select Type 8-Others->BMW->FRM E-series XEQ384
Click Write Partition (will erase Dflash and eeprom data)
vvdi-prog-repair-frm3-6
Write EEPROM partition to 16 sectors (4K), DFLASH: 0 sector
vvdi-prog-repair-frm3-7
Open EEPROM data just converted from Dflash.
vvdi-prog-repair-frm3-8
Click Write tab to write eeprom
Reset FRM success.
vvdi-prog-repair-frm3-9
Install FRM module back to vehicle.


BMW FRM 2M25J/3M25J(9S12XEQ384) pinout to VVDI-Prog.
vvdi-prog-repair-frm3-10

BMW FRM F-series 2M25J (MC9S12XET512) pinout to VVDIProg.
vvdi-prog-repair-frm3-11
You can use VVDI BMW to do coding.




Yanhua Mini ACDP
ACDP MiniFRM adapter repair FRM3: confirmed
It depends on the chip types.
Connect the Yanhua Mini ACDP device and BDM adapter with the FRM unit.
Backup data before operation.
yanhua-acdp-repair-frm3-1
yanhua-acdp-repair-frm3-2
Run Mini ACDP app on a mobile
Select BMW->FRM Programming->ICP MC9S12XEQ384 MASK: 3M25J
yanhua-acdp-repair-frm3-3
yanhua-acdp-repair-frm3-4
yanhua-acdp-repair-frm3-5
Select FRM Data Recovery (Automatic mode)
yanhua-acdp-repair-frm3-6
Detect pins and probe connection
yanhua-acdp-repair-frm3-7
Reading chip data
yanhua-acdp-repair-frm3-8
Read and display chip data
Check the data. If reads D-Flash as 32K, the FRM module data is corrupted.
If reads EEPROM data as 4K , FRM module data is not corrupted.
yanhua-acdp-repair-frm3-9
Uploading data
Auto saved D-flash to Yanhua Mini ACDP file folder
Show programming data
yanhua-acdp-repair-frm3-10

Verifying data
yanhua-acdp-repair-frm3-11

FRM data recovery completed.


CG PRO 9S12
CG Pro repair BMW FRM: confirmed
Procedure:
1: Check car model
Car model: BMW E series
Module: FRM
Chip: 9S12XEQ384

2: Turn off the ignition switch and remove the FRM module from the driving left foot of the car
cg-pro-repair-frm3-1

3: Disassemble FRM module and confirm the SN, type and chip
cg-pro-repair-frm3-2
cg-pro-repair-frm3-3
cg-pro-repair-frm3-4
4: Open CG PRO software
Select type, car make and model
Follow the corresponding wiring diagram to connect FRM module to CG PRO 9S12 programmer via DB25 adapter
cg-pro-repair-frm3-5
cg-pro-repair-frm3-6
cg-pro-repair-frm3-7
5: Read EEPROM data and save
cg-pro-repair-frm3-8
cg-pro-repair-frm3-9
6: Write the data has been read or new data after partition operation
cg-pro-repair-frm3-10
cg-pro-repair-frm3-11
cg-pro-repair-frm3-12
cg-pro-repair-frm3-13
cg-pro-repair-frm3-14
After finishing repair the data, install the FRM module back to the car, and set code for FRM by CGDI BMW key programmer.


HexTag repair a module FRM3: confirmed
You don’t have to buy AutoHex, you can buy HexTag separately.
Step-by-step procedure:
Go to Microtronik HexProg main menu, software 1.0.6 for example.
Click on “On Bench Programmer”-> “BMW”-> “FRM”-> “FRM3 E Series”
hextag-repair-frm3-1
Click on “Wiring” to follow it to connect.
hextag-repair-frm3-2

Click on “Read” and get message “ Error on reading EEPROM shows the files in FRM3 is corrupted”.
hextag-repair-frm3-3
Click on “P-FLASH” and then “Read”.
To check the communication with FRM you can try to read the P-flash.
hextag-repair-frm3-4
Click on “EEE” -> “Read” again, Click on “Repair” and get message “This function is used to repair corrupted FRM EEPROM data. It will try to recover the original data from D-Flash, if it failed please contact Microtronik for help”, go on click on “Repair”.
hextag-repair-frm3-5
FRM EEPROM data has been repaired.
hextag-repair-frm3-6
When it shows the FRM Repair prompt again, just close it.
hextag-repair-frm3-7
Now we can read EEE shows FRM is back to normal state.
hextag-repair-frm3-8
You are advised to code FRM using AutoHex after repair.


Xprog M repair FRM3: Need Luck
Xprog M box (UPA as well) is the cheapest device to read fault FRM3 data. But it is not stable as other programmers.
Some will have these kinds of issues a lot when use Xprog clone to repair FRM’s.
You can hook the frm back to the xprog and made a backup of the EEE and pflash. Then perform coding using WinKFP/Ncs expert.
Check guide here:


FYI:
There are several devices you can used to perform FRM coding job:  BMW ICOM Engineering software Ncs expert, Launch X431 V,  VVDI BMW, CGDI BMW, Autel Maxisys Pro MS908P etc
To be upgrading…