topblog Ivoire blogs

13/03/2019

Yanhua ACDP mini is confirm to work perfectly with BMW 35160WT

Tested successfully! Yanhua ACDP mini is confirm to work perfectly with BMW 35160WT - able to read and write odometer.

you should have an 35160WT simulator

acdp-36150-35080-simulator

Source: http://www.cardiagtool.co.uk/yanhua-35160-35080-programmi...

The simulator is used for those 35160WT chips that cannot be erased. It also works for M35080/ M35080-3/ M35080-6/ M35080V6/ M35080VP/ D80DOWQ/ 160DOWQ/ 35160WT*/ 35128W for dashboard odometer correction.

The test... Here you go.

solder the 35xx chip on the meter to the specified location of the simulator

pay attention to the chip direction

acdp-36150-read-write-km-1 acdp-36150-read-write-km-2

Connect the emulator to the mini usb cable, plug in the computer usb interface

acdp-36150-read-write-km-3

add a new folder on your Desktop, such as folder named "mileage modification"

copy the compressed file named 35xx mileage modification tool.rar to the folder "mileage modification"

extract it to the current folder, get the 35xx mileage modification tool.exe file

copy the 35160 original data to the folder "mileage modification"

acdp-36150-read-write-km-4 acdp-36150-read-write-km-5

enter the mileage data you want to modify as prompted

(note the mileage you want to put with a unit like xxxkm or xxxmi)

then press enter to confirm and the new data will be automatically generated

acdp-36150-read-write-km-7 acdp-36150-read-write-km-6

delete the 35160 simulated data

acdp-36150-read-write-km-8

copy the new data generated in the "mileage modification" folder to the "35xx memory" u disk

acdp-36150-read-write-km-9

replug the simulator

acdp-36150-read-write-km-10 acdp-36150-read-write-km-11

data comparison

if the data is the same, the operation is successful

solder the simulator to the instrument chip location

acdp-36150-read-write-km-12 acdp-36150-read-write-km-13 acdp-36150-read-write-km-14

Done!

12/03/2019

Yanhua Mini ACDP BMW CAS New Update

Yanhua Mini ACDP CAS1 - CAS4 data renew update on March 7,2019

CAS1 (0K50E) renew

CAS2 (2k79x) renew

CAS3  (0L01Y/0L15Y/0M23S) renew

CAS4 (1L15Y / 5M48H /1N35H) ICP renew.

Attach several images for the update:

  1. CAS1 (0K50E) renew

  1. CAS2 (2k79x) renew

  1. CAS3  (0L01Y/0L15Y/0M23S) renew

  1. CAS4 (1L15Y / 5M48H /1N35H) ICP renew.

Capabilities:

The EEPROM data of CAS1 - CAS4 can be renew. First load the EEPROM data from the other car, then modify the car frequency, VIN, ISN code and other information to generate new EEPROM data. So that it can solve the problem that the CAS EEPROM data lost or the CAS module damage and the EEPROM data can't be read out and the CAS module needs to be changed.

Step 1:
Prepare the EEPRON data for the corresponding chip model and copy the data to the APP path: ":/ Atmatch/bmw/CAS4/CAS_Renew', then select the corresponding EEPROM file for parameter calculation.

Step 2
Enter the VIN number, vehicle frequency, ISN code, etc that need to be modified, modify the loaded data and save it, the device will automatically clear the CAS mileage.

Step 3
Write the saved new EEPROM data to the CAS module, then load the CAS module

Step 4
After the module is loaded, if the vehicle cannot be started, or the "Direction lock" is displayed on the meter, please synchronize the ELV or DME according to the situation.

Step 5:
Use professional equipment to clear the trouble codes of the vehicle.

Remarks:
The original car key is invalid and you need to relearn the new key to start the car.

Done.

Learn more please click Yanhua BMW ACDP

11/03/2019

eCOM to work with Xentry 7/18 enabling DOIP

I want help to configure eCOM to work with Xentry 7/18 enabling DOIP

Code:

C:Program Files (x86)Mercedes-BenzXentrybinPDUSDConnectPDUAPI_I+ME_ACTIA_XS.ini
then Go to section [eCOM PFW]
Edit value of key "Firmware" to "eCOM_SDconnect_24_Fw.zip":
Firmware=eCOM_SDconnect_24_Fw.zip
Here is configuration Protocol

Control Panel ? Network and Internet ? Network Connections ? Local Area Connection ? Properties ? Internet Protocol Version 4 (TCP / IPv4) ? Properties ? Use the following IP address (check)

Ip For eCom
IP address 169.254.255.42
Subnet mask 255.255.0.0

Use the address of the next DNS server (check)

Preferred DNS server blank
Alternate DNS server blank

Advanced setting ? Add

Ip For SDconnect to make Toolkit alive with eCOM
172.29.127.100

result
169.254.255.42 255.255.0.0
172.29.127.100 255.255.0.0

OK ? OK ? Close

With this, "eCom & SDconnect" works within Xentry.

Note : This config working 100%

Here is eCOM with Xentry with test on DoIP!

eCOM_xentry_doip