|
SB_GLI
|
 |
« Reply #675 on: July 16, 2017, 08:29:15 AM »
|
|
|
Sometimes you need toggle "boot in intelligent mode" for it to work. As in, turn it on, test, turn it off, test, save, exit. |
|
|
|
|
Logged
|
|
|
|
vigneiswaran
Newbie
Karma: +0/-0
 Offline
Posts: 4
|
|
« Reply #676 on: July 18, 2017, 09:51:13 PM »
|
|
|
Hey Bro ,
Sorry for the late reply . I did as you instructed me to but I am still getting the communication failed message . I unchecked the boot in intelligent mode in vcds and closed it and loaded the me7eeprom and still got a communication failure message . Not sure where else to look into now .
Thnk you so much for your replies
|
|
|
|
|
Logged
|
|
|
|
|
_nameless
|
|
« Reply #677 on: July 19, 2017, 07:35:58 AM »
|
|
|
as far as i know a vcds cable will not workfor this software. the program looks for a com port witch the usb vcds cables are not. the china ft232rl cables are a virtual com port.
|
|
|
|
|
Logged
|
Giving your mom a tuneup
|
|
|
ceecnm
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #678 on: July 25, 2017, 05:52:31 AM »
|
|
|
Hi all,
after read one boy tested this good util with EDC15C2 and it worked, I'm testing with EDC15C7 Alfa/Fiat Infineon CPU now.
ECU is working ok with OBD KKL and different diagnosis programs. All looks like ok.
OBD MODE ifails with full bench config (ecu+key+immo+kkl usb).
>ME7EEPROM --OBD -p 3 -b 9600 -r 95p08.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 9600
Opening COM3 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM3
BOOTMODE fails with CSpin auto (I don't know it).
>ME7EEPROM --bootmode 95P08 -p 3 -b 9600 -r 95p08.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 9600
Memory type: 95P08, size: 1024
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... FAIL. (error=0x70301)
Closing COM3
Then I try with CSPin 8.2 and works but eeprom file is FF, so I think CSPin is wrong or different issue there.
Any idea guys?
Regards.
|
|
|
|
|
Logged
|
|
|
|
ceecnm
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #679 on: July 25, 2017, 10:03:06 AM »
|
|
|
Well, some extra info... I tryed with CS 4.7 and I think it's working, e2p file looks like ok now vs others e2p files from similar ecus  Next test I'm going to write...not fear...lol. |
|
|
|
|
Logged
|
|
|
|
paste
Newbie
Karma: +0/-1
Offline
Posts: 6
|
|
« Reply #680 on: July 31, 2017, 12:31:26 AM »
|
|
|
I have had to read through fifty pages of various threads before I finally figured this all out. The broken English is cute at times, but I am beginning to see the annoyance of it.
*Edit* I was able to read the EEPROM with the OBD function and make the necessary changes using a hex editor. However, after many unsuccessful attempts at writing in boot mode, I have given up for today.
|
|
|
|
« Last Edit: July 31, 2017, 09:38:55 AM by paste »
|
Logged
|
|
|
|
fdante
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #681 on: July 31, 2017, 01:01:05 PM »
|
|
|
I am currently having trouble reading out the 95040 of the ECU through OBD, as I want to clone the current ECU to play safe. I am getting error code 0x1 (80401)
This is a 00 TT 1.8T
ECU id response 8L0906018M
1.8L R4/5VT
0002
SoftCod: 05710, WSC: 21583
|
|
|
|
« Last Edit: July 31, 2017, 01:05:13 PM by fdante »
|
Logged
|
|
|
|
fdante
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #682 on: July 31, 2017, 01:14:40 PM »
|
|
|
I have a 021906018m that will not let me read the eeprom. I keep getting Error=0x80401. Nefmoto will let me connect but says Immobilizer not authenticated.
I have tried to short pin 24 to put it in bootmode but it does not seem to be going in to bootmode. Does anyone have any help?
UPDATE: I fixed it.
How? I have the exact same code. Are you reading through OBD? |
|
|
|
|
Logged
|
|
|
|
paste
Newbie
Karma: +0/-1
Offline
Posts: 6
|
|
« Reply #683 on: July 31, 2017, 03:20:09 PM »
|
|
|
I'd try the other version of the software first. The cable I was working with did not seem to take but then the FTDI chipped cable worked for the OBD readout. However, I can not get to write. A reoccurring error code of 0x20F07 comes up.
|
|
|
|
|
Logged
|
|
|
|
fdante
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #684 on: July 31, 2017, 10:18:41 PM »
|
|
|
I tried both versions, but no success. But after having read the whole thread, it seems that there are quite a few problems with OBD reading. I need to try bootmode.
But this brings some more questions.
1, Is there any tools which can read the old ECU without opening up? I have no problems opening up the replacement ECU, but as this is my first time doing this stuff, I would rather not open up the old one.
2, Will the car run If I just disable the immo bits in the replacement?
3, What tools do I need If I flash a virgin IMMO dump onto the replacement ECU? I need to readapt the ECU to cluster but exactly how? In this case I need the SKU from the old one, not?
|
|
|
|
|
Logged
|
|
|
|
paste
Newbie
Karma: +0/-1
Offline
Posts: 6
|
|
« Reply #685 on: August 01, 2017, 12:04:35 AM »
|
|
|
I just scrapped this whole idea and used Vag K+ Commander to and used the key learning to program my new keys instead of bypassing the RFID chips by disabling the IMMO like I initially planned. On my table I have a cluster from the junkyard and I assume that since Commander was able to take the dump and save it as a bin file, I can just write it onto the new cluster and go about my business.
|
|
|
|
|
Logged
|
|
|
|
jochen_145
Full Member
Karma: +9/-4
Offline
Posts: 177
|
|
« Reply #686 on: August 22, 2017, 12:59:25 AM »
|
|
|
Is there anywhere a list of all availible error codes of ME7EEPROM ?
Yesterday I tryed to readout a 1.8T ECU (8N0906018Q) via OBD in the car, but I didn´t get connection to ECU and error 0x21007 ..
Interface is a "stupid RS232 KKL" on COM1.
Does the cluster interferrens on k-line, so I need to pull fuse, when I like to read the EEPROM in car ?
Thanks for help..
|
|
|
|
|
Logged
|
|
|
|
fdante
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #687 on: August 22, 2017, 02:16:05 AM »
|
|
|
On the 2 1.8T ECUs I ve tried, I was not able to read out through OBD just though bootmode.
If I am right, this is a 512Kb flash model (narrowband) and with IMMO2(immo stored completely in cluster, no SKC/immoID in ECU)
|
|
|
|
|
Logged
|
|
|
|
jochen_145
Full Member
Karma: +9/-4
Offline
Posts: 177
|
|
« Reply #688 on: August 22, 2017, 01:35:25 PM »
|
|
|
In my case, yes you are right  Ok, then I will pull-out ECU and give bootmode a try.. What is the difference between ME7EEPROM and e.g. VAG-dashcom ? Are they able to manage seed-and-key to read and wirte EEPROM via OBD without bootmode ? |
|
|
|
|
Logged
|
|
|
|
TTunasalad
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #689 on: August 28, 2017, 03:40:34 PM »
|
|
|
as far as i know a vcds cable will not workfor this software. the program looks for a com port witch the usb vcds cables are not. the china ft232rl cables are a virtual com port.
It is more than putting it into dumb mode you need to download the vcds vcp drivers and manually install them (if you used vcds on the same machine) Just used it with a usb key-com cable which uses same drivers as the original hex. The latest cable (hex v2) and the net won't work with the vcp drivers but the other usb cables should. You can still open and configure vcds to run it as usb, so you don't need to change back and forth each time. It just will likely tell you the driver is out of date. |
|
|
|
|
Logged
|
|
|
|
|
