topblog Ivoire blogs

10/08/2017

How to use Fgtech 4 Galletto v54 for EDC17CP14 read/write/checksum?

Topic: Is possible to read/write edc17cp14 with Fgtech 4 in boot mode??

 

 

Fgtech 4 EDC17CP14 Reviews:

 

Works great with FGTECH !

 

Tested in boot mode, read&write eeprom+flash ok

 

Galleto v54 clone read - write ok in bootmode

 

read write ok,but one time was somethink about checksum,and cannot write mod file,i did with Ktag

 

Tested ok read/write

 

I have tested clone, perfectly worked many times on this ECU, both reading/writing via OBD and boot mode. Regards!

 

 

Galletto v54 EDC17 Reviews:

 

Galletto v54 EDC17success:

EDC17CP14 03L906022G Read/Write ok (OBD and boot mode)

BMW edc17 in boot mode ok
BMW E87 116D 2.0 EDC17C06 Bootmode r/w ok
BMW X6 3.0D 2012 and 2013 (306 and 245hp)BOSCH EDC17CP45 read/write BOOT ok
bmw 3/5/7 series: edc16c31/35 obd r/w ok, edc17 in boot mode ok

bmw x3 edc17 read write ok

Landrover /jaguar EDC17CP11 read out in boot mode ok, not tried write yet.
citroen C3 II 2012read/wrote tricore EDC17C10 by bootmode , with a non reworked v54.

VW EDC17CP14 and Galletto v54 write in boot mode

PSA edc17cp10 no problem read/write

 

Galletto v54 EDC17 failed:

BMW F10 2010y EDC17CP45 TPROT10 on the bench...boot SAK1797 only ecu data...can not read ee not read int. flash
Jaguar xm edc17 read fail

Opel insignia Edc17c19 read ok write fail , Use fgtech v52 read ok write ok

Porsche 2012 MY - VAG EDC17CP44 readwrite in boot mode failed - could not disable TPROT
Sirius32 make a checksumm fail

 

 

Galletto v54 EDC17 Questions & Answers:

 

Q: Galletto works fine on VW EDC17CP14ecu?

A: Yes

 

Q: with edc17cp10 psa no problem read/write but with this cp14 vag not work even in bootmode and obd ( read ok in both)

A: CP14 shouldn't be problem on Tricore boot. I think you have broken ECU or device.

 

Q: Galletto v54 checksum not supported, how to do?

A: 0. Read Original ALL with Galletto boot mode. It will give you "All" file (4,224kb), internal flash+external flash+eeprom, (in my case).
1. Paste mod internal flash (make sure checksums are already correct) into the original 'all' file. Align correctly. Internal flash starts at 00, so it is easy.
2.Triple checkthat the paste is ok!
3. Flash modded "all" file in Galletto. This is done using "Write All" button.
4. It takes much longer to flash a file with differences. It took about 6+ minutes on first part - internal flash. It went to 100%, then to 75% and up to 100% slowly many times. Total over 10 minutes.
5. Read All to verify!
6. Compare with Hex Editor.

Car started, DPF functions are all gone.

 

Q: Is it possible to attempt to flash the big 4.2 MB 'all' file (int flash, ext flash, eeprom combined)?

can I paste my changes there, and checksums too?

A: The answer is YES

I flashed the original 4224kb 'all' file back to the ecu successfully. Galletto skips checksum correction for the ALL file.

Risky, but I guess I was brave enough. The boot pin accidentally untouched, and galletto stopped and told me to remove power and reconnect. WHILE FLASHING. Nearly peed my pants.

I repositioned boot pin, reconnected power, and it continued error free!

After, I did a verification read of all.

100% identical to original

Now I will paste my internal flash mods (with checksum corrected already) into the 4224kb file, and flash that.

 

Q: How to delete individual dtc codes from edc17 (cp14 was the flavor i was working with)?

A: example:

009298 - Diesel Particle Filter; Differential Pressure Sensor

P2452 - 000 - Elect. Malfunction - MIL ON

 

find the p code in the p code look up table. 16bit, hex.

location: 190a7a

p code table start: 190654

get your hex calculator!

190a7a - 190654: 426. divide by 2, 213.

find your vag specific dtc look up table. 8 bit.

 

example:

table start location: 18569e

18569e + 213: 1858b1. this is the location of the p2452 dtc. 00 this byte.

no more dtc light.

same process as me7 except /2 instead of /8.

 

Car OBD2 Tools global one-stop shopping supplier ---OBDexress.co.uk

09/08/2017

VVDI Prog and Xprog, which is better?

Xhorse VVDI Prog and Xprog, which is better?

 

Type

VVDI Prog

Xprog

MC9S12DP crack

Yes

Yes

MC9S12XD crack

Yes

Yes

MC9S12XE crack

Yes

Yes

MC65HC(9)08 crack

Yes

No

CDC32XX crack

Will be available

Yes

M35080V3 erase encrypted sites

Yes

Yes

M35080V6 erase encrypted sites

Yes

Yes

080D0 erase encrypted sites

Yes

No

160D0 erase encrypted sites

Yes

No

24Cxx read/write

Yes

Yes

24Exx read/write

Yes

Yes

25Cxx read/write

Yes

Yes

25xxx read/write

Yes

Yes

95xxx read/write

Yes

Yes

95Pxx read/write

Yes

Yes

93Cx6 read/write

Yes

Yes

TC8910x read/write

Yes

Yes

MC965HC05 read/write

Will be available

Yes

MC9S12H read/write

Yes

Yes

MC9S12P read/write

Yes

Yes

MC9S12XH read/write

Yes

Yes

MC9S12XS read/write

Yes

Yes

ATMEGA read/write

Yes

Yes

XC236x read/write

Yes

Yes

MAC724x read/write

Will be available

Yes

AT89x5x read/write

Will be available

No

ATtiny read/write

Will be available

No

PIC read/write

Yes

No

RSF212xx read/write

Yes

No

M308xx read/write

Yes

No

uPD70F3xxx read/write

Yes

No

ST6xxx read/write

Will be available

No

ST10Fxxx read/write

Yes

No

STM8 read/write

Yes

No

STM32 read/write

Will be available

No

MSP430 read/write

Will be available

No

TMS37xxx read/write

Will be available

No

 

 

In summary,

Xprog is a good universal programmer for various chips and MCUs in automotive.

But if you can pay more, i suggest you to buy vvdi prog

 

Tip: VVDI PROG vs Xprog-m vs R270 vs Orange5 clone:

 

  1. faster to clear 35080, 080D0, 160D0 (within 10S)
  2. more stable than Xprog-m to read MC9S12 series chips
  3. faster to attack MC9S12series chips
  4. less error than Orang5 to read some EEPROM that Orange 5 fail to recognize
  5. with voltage attack function for use
  6. with CAN bus,K-Line for use

 

So, VVDI Prog should be the best solution for ECU programming.

It covers chips that Xprog supports, works with less error than Orange 5, has the function of r260+r270

 

 

10:43 Publié dans Blog, Shopping, Web | Tags : vvdi prog | Lien permanent | Commentaires (0)

27/07/2017

OPCOM Op-com Firmware 1.60 1.59 1.45 1.39 Update User Manual

Here’s the OPCOM firmware update user manual. The op-com software version use one or other firmware version as fw 1.33, fw 1.39, fw 1.41, fw 1.43, fw 1.44 fw 1.45, fw 1.47 fw 1.59 fw 1.60 ( the last one ).

 

OPCOM firmware introduction:

OP-COM China clone ( op-com 100219a ) from 2009 use fw 1.39 – do not use other firmware

 

OP-COM software from 2011 use fw1.44

 

OP-COM software from 2012 used fw 1.45 and the software released at the end of that year used fw1.47

 

OP-COm software from 2014 used fw1.59 (fw 1.45 & 1.59 come with the same pcb)

 

VAUX-COm version, Romanian and German version of OP-COM used fw1.60

 

So the difference it is not in the firmware as 1.44, 1.45, the difference it is in the software version

 

NOTE:

– With other words if you have an op-com tool that it has firmware 1.39 and you’ll try to use it

– with for instance OP-COM 131223c English version the software will upgrade the firmware of your interface to the version that its need- to 1.59

– If then you try one of the version in Romanian/ German or vaux-com version 131223 the software will upgrade the firmware of the tool to the fw 1.60

 

So now in conclusion. You do not need to change the firmware of your tool with one or other. You only need to use the necessary firmware for the software version that you are using it.

OPCOM firmware update:

changing (upgrade or downgrade) firmware version in op-com chinese clone is at risk – you’ll damage the tool and it will not work anymore

 

The only way to change Opcom firmware is

 

to replace the MCU with a original Microchip PIC18F458

remove 2 component from PCB

Remake a connection on bord and cut another one

Then reprogram the new brand chip PIC18F458 and you can have a brand new clone that will be available to upgrade the firmware of the interface

NOTE:

– The firmware must be the one that it is required by the software version

– Do not use other one because will not 100% correct

– A normal clone not model cannot works with the Model software that works with as we named HQ clone

– This not depend on the ept or firmware and depend on the FTDI ID and PIC dump. All it is about a marriaged dump of PIC MCU with the FTDI ID – a uniq combination

– firmware 1.59 and 1.60 update is most populous:

 

Good luck