SIMOS18.10 flash in bench with VCP

Pages: [1]

« previous next »

Author

Topic: SIMOS18.10 flash in bench with VCP (Read 3897 times)

vt1111

Jr. Member

Karma: +0/-0
Offline

Offline

Posts: 27

	SIMOS18.10 flash in bench with VCP « on: October 12, 2021, 08:42:13 AM »

Hi,

today I tried to flash a SIMOS 18.10 with VCP on Bench but this is the output:

Code:

Block #0 Len: 1
Block #1 Len: 80672
Block #2 Len: 1
Block #3 Len: 449008
Block #4 Len: 1
Block #5 Len: 600592
Block #6 Len: 1
Block #7 Len: 911008
Block #8 Len: 1
Block #9 Len: 243600
OK !
Read identification ...
83A906259   EV_ECM20TFS02083A906259 001003
Check programmingPreconditions ...
programmingPrecoditions not fullfilled :Immo On.
ECU flashing finished with errors !
Closing communication ...
Communication closed
Turn on/off ignition

Looks like IMMO On Protection does not allow to flash on bench. All other functions like live values, coding and that stuff works.

With same wiring a SIMOS18.1 is full flashable.

Really strange. Tools like bflash and cmd should do it also on bench via CAN.

Any Ideas?

Thanks.


	Logged

IamwhoIam

Hero Member

Karma: +44/-101
Offline

Offline

Posts: 1034

	Re: SIMOS18.10 flash in bench with VCP « Reply #1 on: October 12, 2021, 09:03:03 AM »

If your SIMOS18.1 flashes on the bench then it means it has immo disabled or it's a native dev ECU, OR that immo status is virgin. No VAG production ECU since 1998 has allowed bench OBD flashing as soon as immo has been coded to a car.


	Logged

I have no logs because I have a boost gauge (makes things easier)

vt1111

Jr. Member

Karma: +0/-0
Offline

Offline

Posts: 27

	Re: SIMOS18.10 flash in bench with VCP « Reply #2 on: October 12, 2021, 09:25:58 AM »

Thanks for you're reply.

Are you sure? Got the SIMOS 18.1 from ebay but looks very used. And flashed several times with vcp on bench so if Immo was disabled it should active after a flash or not?

Any way to check immo state on simos18.1?

How does cmd, bflash and other tuning tools the flash on bench via CAN (no need for open ecu)


	Logged

kuebk

Jr. Member

Karma: +3/-0
Offline

Offline

Posts: 44

	Re: SIMOS18.10 flash in bench with VCP « Reply #3 on: October 12, 2021, 09:40:10 AM »

Because these tools are doing so called BENCH flashing, you are doing OBD flashing on bench - nothing in common between these two things.


	Logged

IamwhoIam

Hero Member

Karma: +44/-101
Offline

Offline

Posts: 1034

	Re: SIMOS18.10 flash in bench with VCP « Reply #4 on: October 12, 2021, 09:47:54 AM »

Quote from: vt1111 on October 12, 2021, 09:25:58 AM

Thanks for you're reply.

Are you sure? Got the SIMOS 18.1 from ebay but looks very used. And flashed several times with vcp on bench so if Immo was disabled it should active after a flash or not?

No, I'm not sure, I only wasted 3 minutes of my life here because I had nothing better to do than to talk shit and give you an incorrect answer.


	Logged

I have no logs because I have a boost gauge (makes things easier)

d3irb

Full Member

Karma: +131/-1
Offline

Offline

Posts: 186

	Re: SIMOS18.10 flash in bench with VCP « Reply #5 on: October 12, 2021, 10:21:07 AM »

Quote from: vt1111 on October 12, 2021, 09:25:58 AM

How does cmd, bflash and other tuning tools the flash on bench via CAN (no need for open ecu)

They don't.

I attached the bFlash compatibility matrix, note that Simos past Simos16 requires opening the ECU (so-called "boot" mode by some these commercial tools), not connecting via only the external connector outside of the car (so called "bench" mode by these commercial tools).

Something is odd about your Simos18.1. Either the Immo is not active for some reason (particularly odd patch, sample ECU, dflash data) or you are not truly flashing successfully and the ECU is stuck in CBOOT.


	Logged

prj

Hero Member

Karma: +915/-427
Offline

Offline

Posts: 5839

	Re: SIMOS18.10 flash in bench with VCP « Reply #6 on: October 12, 2021, 12:47:05 PM »

Most likely it's stuck in CBOOT.

Also OP presenting random things he came up for facts like a boss.
No tool can bench flash S16 and up. No VAG ECU will let you flash via OBD protocol with immo on unless it's dev.


	Logged

PM's will not be answered, so don't even try.
Log your car properly.

cherry

Full Member

Karma: +24/-2
Offline

Offline

Posts: 246

	Re: SIMOS18.10 flash in bench with VCP « Reply #7 on: October 12, 2021, 01:08:34 PM »

Only EDC15 could be flashed with immo active Grin

I flashed Simos18.1 on table too, but sure i had valid cluster with key connected and even need to send CAN message to power up cluster.

Also MQB DSG are only flashable with immo released, Audi TCU even older cars from 2003 where TCU is part from immo.


	Logged

vt1111

Jr. Member

Karma: +0/-0
Offline

Offline

Posts: 27

	Re: SIMOS18.10 flash in bench with VCP « Reply #8 on: October 13, 2021, 12:28:36 AM »

Thanks for your answers guys.

Rechecked the bflash stuff and I see, need to open ecu. Sorry for that.

Flash of my S18.1 was sucessfull many times with vcp.

Is there a way on S18 to completly disable the immo, and its still disabled after a full flash via obd? I always thought that an Immo off patch disappears after all blocks are rewritten. Do I have a way to test the 18.1 if it is a Dev ECU?

Strange thing is i have also a 18.6 here, but same result: Full flashable. Here the ECU Infos:

Code:

==== Manufacturer data ====
HW : 06K907425E  Serial no:No data found,Manufacturer ID:No data found,Prod.Date.:No data found
ECU variant :H13,Controller ID :No data found,Con.number:895741

Engine type :No data found
LogicalBlock[0] : ProgrammingDate: 00.00.00 TesterID: [0,0,0] Status: 00
LogicalBlock[1] : ProgrammingDate: 00.00.00 TesterID: [0,0,0] Status: 02
LogicalBlock[2] : ProgrammingDate: 00.00.00 TesterID: [0,0,0] Status: 02
LogicalBlock[3] : ProgrammingDate: 00.00.00 TesterID: [0,0,0] Status: 02
LogicalBlock[4] : ProgrammingDate: 00.00.00 TesterID: [0,0,0] Status: 02

====  ODX INFO ====
Serial:  ODX ID: EV_ECM20TFS02006K907425E ODX Version: 001002

Here is the Flash Log:

Code:

Block #0 Len: 1
Block #1 Len: 80560
Block #2 Len: 1
Block #3 Len: 573344
Block #4 Len: 1
Block #5 Len: 518480
Block #6 Len: 1
Block #7 Len: 417744
Block #8 Len: 1
Block #9 Len: 174896
OK !
Read identification ...
06K907425E  EV_ECM20TFS02006K907425E 001002
Check programmingPreconditions ...
OK ...!
Setting DTC Control of ...
OK ...!
Setting special communication mode ...
OK ...!
Entering programming mode ...
OK ...!
Seed request ...
Sending key :
OK ...!
Writing Fingerprint ...
FlashTool Code: 12345 123 12345
OK ...!
Protocol version : 1.0.0
Start Flashing DataBlocks ...
Processing DataBlock EMEM_5G09062590010.DB_0ERASE
Erasing memory :01 130560
Flash memory erased OK.
Processing DataBlock EMEM_5G09062590010.DB_0
Request download :01 AA 146944 014101
OK ...!
Transfer Data, blocksize :0FFF/4093
Processed OK,Closing transfer ...
OK ...!
Signing ...
Signed ok.
Processing DataBlock EMEM_5G09062590010.DB_1ERASE
Erasing memory :02 785408
Flash memory erased OK.
Processing DataBlock EMEM_5G09062590010.DB_1
Request download :02 AA 1047552 014101
OK ...!
Transfer Data, blocksize :0FFF/4093
Processed OK,Closing transfer ...
OK ...!
Signing ...
Signed ok.
Processing DataBlock EMEM_5G09062590010.DB_2ERASE
Erasing memory :03 785408
Flash memory erased OK.
Processing DataBlock EMEM_5G09062590010.DB_2
Request download :03 AA 785408 014101
OK ...!
Transfer Data, blocksize :0FFF/4093
Processed OK,Closing transfer ...
OK ...!
Signing ...
Signed ok.
Processing DataBlock EMEM_5G09062590010.DB_3ERASE
Erasing memory :04 785408
Flash memory erased OK.
Processing DataBlock EMEM_5G09062590010.DB_3
Request download :04 AA 523264 014101
OK ...!
Transfer Data, blocksize :0FFF/4093
Processed OK,Closing transfer ...
OK ...!
Signing ...
Signed ok.
Processing DataBlock EMEM_5G09062590010.DB_4ERASE
Erasing memory :05 457728
Flash memory erased OK.
Processing DataBlock EMEM_5G09062590010.DB_4
Request download :05 AA 523264 014101
OK ...!
Transfer Data, blocksize :0FFF/4093
Processed OK,Closing transfer ...
OK ...!
Signing ...
Signed ok.
All blocks transferred OK
Checking programming dependencies ...
Programming OK, resetting ECU ...
Reconnecting ...
ECU flashing finished sucessfully !
Closing communication ...
Communication closed
Turn on/off ignition

And that us ECU Info after Flash, so I think its full flashed or not?

Code:

==== Manufacturer data ====
HW : 06K907425E  Serial no:No data found,Manufacturer ID:--H13---,Prod.Date.:No data found
ECU variant :H13,Controller ID :No data found,Con.number:895741

Engine type :CHHB
LogicalBlock[0] : ProgrammingDate: 21.10.13 TesterID: [12345,12345,123] Status: 00
LogicalBlock[1] : ProgrammingDate: 21.10.13 TesterID: [12345,12345,123] Status: 00
LogicalBlock[2] : ProgrammingDate: 21.10.13 TesterID: [12345,12345,123] Status: 00
LogicalBlock[3] : ProgrammingDate: 21.10.13 TesterID: [12345,12345,123] Status: 00
LogicalBlock[4] : ProgrammingDate: 21.10.13 TesterID: [12345,12345,123] Status: 00

====  ODX INFO ====
Serial:  ODX ID: EV_ECM20TFS0215G0906259 ODX Version: 001014

What is meant by "Status" after TesterID?

Strange is no Serial No and no VIN also. Got the 18.4 from same dude as the 18.6 - is it possible that i got 2 Dev ECUs?

Here is the ECU Info from the 18.1:

Code:

==== Manufacturer data ====
HW : 06K907425B  Serial no:No data found,Manufacturer ID:--H13---,Prod.Date.:No data found
ECU variant :H13,Controller ID :No data found,Con.number:895741

Engine type :CHHB
LogicalBlock[0] : ProgrammingDate: 21.10.12 TesterID: [12345,12345,123] Status: 00
LogicalBlock[1] : ProgrammingDate: 21.10.12 TesterID: [12345,12345,123] Status: 00
LogicalBlock[2] : ProgrammingDate: 21.10.12 TesterID: [12345,12345,123] Status: 00
LogicalBlock[3] : ProgrammingDate: 21.10.12 TesterID: [12345,12345,123] Status: 00
LogicalBlock[4] : ProgrammingDate: 21.10.12 TesterID: [12345,12345,123] Status: 00

====  ODX INFO ====
Serial:  ODX ID: EV_ECM20TFS0215G0906259 ODX Version: 001014

And here is the ECU Info from the 18.10 (but also no Serial No / Prod.Date):

Code:

==== Manufacturer data ====
HW : 06K907425J  Serial no:No data found,Manufacturer ID:--H13---,Prod.Date.:No data found
ECU variant :H13,Controller ID :No data found,Con.number:895741

Engine type :DHHA
LogicalBlock[0] : ProgrammingDate: 19.07.15 TesterID: [16,6385,790] Status: 00
LogicalBlock[1] : ProgrammingDate: 19.07.15 TesterID: [16,6385,790] Status: 00
LogicalBlock[2] : ProgrammingDate: 19.07.15 TesterID: [16,6385,790] Status: 00
LogicalBlock[3] : ProgrammingDate: 19.07.15 TesterID: [16,6385,790] Status: 00
LogicalBlock[4] : ProgrammingDate: 19.07.15 TesterID: [16,6385,790] Status: 00

====  ODX INFO ====
Serial:  ODX ID: EV_ECM20TFS02083A906259 ODX Version: 001003


« Last Edit: October 13, 2021, 02:02:09 AM by vt1111 »	Logged

prj

Hero Member

Karma: +915/-427
Offline

Offline

Posts: 5839

	Re: SIMOS18.10 flash in bench with VCP « Reply #9 on: October 13, 2021, 04:31:19 AM »

Neither ECU is exiting cboot or eeprom error.


	Logged

PM's will not be answered, so don't even try.
Log your car properly.

keine ahnung

Newbie

Karma: +0/-0
Offline

Offline

Posts: 2

	Re: SIMOS18.10 flash in bench with VCP « Reply #10 on: November 25, 2022, 01:13:30 AM »

Hello

It is possible to flash only the CBOOT and ASW without flashing the Cal block an a Simos18 ECU?

Thank you.

keine ahnung


	Logged

gt-innovation

Sr. Member

Karma: +60/-89
Offline

Offline

Posts: 447

	Re: SIMOS18.10 flash in bench with VCP « Reply #11 on: November 25, 2022, 04:02:46 AM »

Quote from: keine ahnung on November 25, 2022, 01:13:30 AM

Hello

It is possible to flash only the CBOOT and ASW without flashing the Cal block an a Simos18 ECU?

Thank you.

keine ahnung

No because part of the calibration area is beeing re-written by cboot temp so whatever you are trying to get from that calibration will be half gone.


	Logged

Pages: [1]

« previous next »

Jump to:

Navigation

Personal Tools

April 23, 2024, 11:34:13 AM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search