diyre
Newbie
Karma: +0/-0
 Offline
Posts: 1
|
 |
« Reply #510 on: September 01, 2015, 02:32:13 PM »
|
|
|
Good evening, this issue'm a little desperate, cable KKL 409. VAGCOM, I read the EPROM under code.
(program name) --bootmode 95040 -r -p 1 95040.bin
When writing the EPROM, everything OK least I get error verify 0x70101. the command is:
(program name) --bootmode 95040 -wp1 95040.bin
Anyone know why ?, what I can do?
It is a dead end.
A greeting
thanks for everything.
|
|
|
|
|
Logged
|
|
|
|
ing90
Newbie
Karma: +1/-0
Offline
Posts: 4
|
|
« Reply #511 on: September 11, 2015, 01:29:12 PM »
|
|
|
I have also a question to fault codes. I have 2 ECUs from a PSA V6 (ME 7.4.6), one is maybe broken, the other one should be ok.
Can anyone help me with this fault codes?
First:
D:\>v14 --bootmode 95160 -b 9600 -r -p 3 EEPROM.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 9600
Memory type: 95160, size: 2048
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... FAIL. (error=0x40F01)
Closing COM3
Second:
D:\>v14 --bootmode 95160 -r -p 3 EEPROM.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95160, size: 2048
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x40E01)
Closing COM3
The first EEPRom is a 95160, the second a 25C16. If the read/write is not possible, does anybody know, if I can change them (desoldering), even if they are not exactly the same? The size is identical...
Sry, I'm not so familiar with this "basic" electronic stuff and I do not find this fault codes in another post...
Regards,
Ben
|
|
|
|
|
Logged
|
|
|
|
ing90
Newbie
Karma: +1/-0
Offline
Posts: 4
|
|
« Reply #512 on: September 12, 2015, 03:31:44 AM »
|
|
|
Just as information:
I tried it out and it's possible to replace a 25C16 with a 95160 EEPROM. The engine runs.
Regards,
Ben
|
|
|
|
|
Logged
|
|
|
|
.
Jr. Member
Karma: +0/-3
Offline
Posts: 29
|
|
« Reply #513 on: September 14, 2015, 04:45:27 PM »
|
|
|
thanks for the tool argdub.  |
|
|
|
|
Logged
|
|
|
|
|
golfputtputt
|
|
« Reply #514 on: October 07, 2015, 10:19:05 AM »
|
|
|
I am having issues. I have version 1.40 and am using a vcds genuine hex+Can cable set to dumb mode. I also have a chinese Vag tacho cable I've tried too. Both are USB interfaces. The program isnt recognizing the port. Not sure if its my computer's fault or the program or my interface. Has anyone else ran into this issue?
Im getting:
Opening COM1 ... Unable to open comport. (error=0x20201)
Closing COM1
Any ideas?
|
|
|
|
|
Logged
|
|
|
|
jogtx16v
Full Member
Karma: +6/-1
Offline
Posts: 139
|
|
« Reply #515 on: October 07, 2015, 03:44:44 PM »
|
|
|
does your cables's are set to com1 in device manager ?
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #516 on: October 07, 2015, 03:47:03 PM »
|
|
|
If you are using RossTech you need the VCP driver to have it show up as a COM port.
|
|
|
|
|
Logged
|
|
|
|
naehkae
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #517 on: October 08, 2015, 10:01:08 AM »
|
|
|
Hello! I'm having problems reading my A6 C5 4.2l ecu. I am getting everytime error 0x01. I've tried v1.4 but then it gives error 0x07. I'm using blue KKL cable. C:\Users\juuho\Desktop>me7_95040 -r -p5 --OBD 95040.bin Ver: 1.31 Com Port: 5 Baud Rate: 10400 Opening COM5 ... OK Initiating communication ... OK ECU ID response: 4D0907558A 4.2L V8/5V G 0002 SoftCod: 05752, WSC: 02335 Reading EEPROM ......................................................................FAIL. (error=0x01) Closing COM5 Any help on this?  |
|
|
|
« Last Edit: October 08, 2015, 10:08:02 AM by naehkae »
|
Logged
|
|
|
|
jogtx16v
Full Member
Karma: +6/-1
Offline
Posts: 139
|
|
« Reply #518 on: October 08, 2015, 03:42:40 PM »
|
|
|
try to read in bootmode...
|
|
|
|
|
Logged
|
|
|
|
keirnbug
Newbie
Karma: +0/-0
Offline
Posts: 8
|
|
« Reply #519 on: October 31, 2015, 08:01:59 AM »
|
|
|
Works like a charm !
Thanks a lot !
|
|
|
|
|
Logged
|
|
|
|
mangusika
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #520 on: November 07, 2015, 12:05:12 PM »
|
|
|
Hi guys! i have problem with reading my me73h4  Anny sugestions? |
|
|
|
|
Logged
|
|
|
|
b4A4nowA6
Full Member
Karma: +1/-4
Offline
Posts: 117
|
|
« Reply #521 on: December 14, 2015, 11:42:44 PM »
|
|
|
I am having issues. I have version 1.40 and am using a vcds genuine hex+Can cable set to dumb mode. I also have a chinese Vag tacho cable I've tried too. Both are USB interfaces. The program isnt recognizing the port. Not sure if its my computer's fault or the program or my interface. Has anyone else ran into this issue?
Im getting:
Opening COM1 ... Unable to open comport. (error=0x20201)
Closing COM1
Any ideas?
I am having the exact same issues and my car is stuck in immo for some random reason. |
|
|
|
|
Logged
|
|
|
|
PLVSVLTRASPAIN
Newbie
Karma: +0/-0
Offline
Posts: 19
|
|
« Reply #522 on: December 16, 2015, 03:16:57 PM »
|
|
|
Hello,
I'm getting this message. Any help will be much appreciated.
Ver: 1.31
Com Port: 3
Baud Rate: 1040
Opening COM3 ..
Initiating comm
Closing COM3
OBDII CHina Cable
WIndows 7
Bench cheap set-up
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #523 on: December 16, 2015, 07:57:39 PM »
|
|
|
Post the cmd prompt log
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #524 on: December 16, 2015, 07:58:56 PM »
|
|
|
Hi guys! i have problem with reading my me73h4 Anny sugestions? Check and try setting the eeprom type and pin manually? |
|
|
|
|
Logged
|
|
|
|
|
