Recent Posts

you can try the open source tool and post full screen output:
http://nefariousmotorsports.com/forum/index.php?topic=18686.msg164642#msg164642
ME7BootEeprom 9600 -read -SSC 1 Port4 Pin7 512 eeprom.ori
ME7BootEeprom 9600 -write -SSC 1 Port4 Pin7 modified.bin

on read you can use decimal 512 or 0x100 as size indicator

Thanks this worked without fail.

readout looks good to me, try to use eeprom immo tool to verify checksums

you are correct I was thinking the memory chip.

it is confirmed to be a 95160.

updated imgur link.

Here is what I Read does it look right?

None of your photos contain the EEPROM chip, it's on the other side of the PCB iirc.

I am not sure I have seen conflicting information on this chip that it might be 95040 because its early?

2006 07K Beetle Manual Transmission

0 261 208 869

See Photos

https://imgur.com/a/1jFQ4I7

S4wiki lists what needs to be done for rear o2 delete:
https://s4wiki.com/wiki/Tuning#Cat_and_O2_complete_removal_and_DTCs

The CWKONLS and CWKONABG mods are not required, but in addition to that paragraph ESKONF also needs to be modified to remove the rear o2 heater dtc.

Recently installed greens I had laying around since I was replacing the intake manifold gasket anyway.

Getting a rich code now (obviously) as well as an intermittent rear O2 fault.  Which doesn't make sense since I bought the "tune" when I was already catless.  Figured that would have been completely coded out.

The rich code is obviously because your front O2 is still functioning (it shoud be!) and the greens put more fuel out per millisecond of activation. Coding out the rear O2 is much more work than disabling the setting of the DTC for a catalist efficiency, which in all likelyhood is what was done on your tune. This obviously requires the rear O2 to still be physically in the car and electricly connected up and functioning. The DTC you are getting is related to the rear O2 having intermittent connectivity problems or actually malfunctioning. I wouldn't bother myself to try and code it out and just replace the rear O2 sensor and check the connectivity.

From the log i only see that the chip select is not the problem, please write which ecu you are using and if known the eeprom chip type on it.
MH-Auto states on this ME7.1.1 Ecu is a 95160 eeprom so you need to adapt the call line. 95160 is type 0 and size needs to be 0x800 for full read, if there are only zeros or FF´s in upper half you can use 0x400

read: ME7BootEeprom 9600 -read -SSC 0 Port6 Pin3 0x800 Read.ori
write: ME7BootEeprom 9600 -write -SSC 0 Port6 Pin3 immoOff.bin

the driver used for read and write 95040/5P08C3  against the 95080-95320 is different. please read again, your readout is wrong, if you read with a 95160 with type 1 the readout has an extra byte like ff on start of each line. i will do it on an me7.1.1 in the afternoon and post logs

Still Doesn't want to write anything




C:\Users\ericg\Desktop\me2024>ME7BootEeprom 9600 -read -SSC 1 Port6 Pin3 512 ReadagainafterWRITE.ori

BootMode EEprom Tool for me7 Variants inspired by ArgDub , 360trev and Gremlin
***********

-read  baudrate:  9600
 eeprom type is 95040 or 5P08C3
 size:  0x200
C16x SSC is used
Waiting for K+Can or KKL Adapter (plug in USB if not done!!)
using  COM3

this is bullshit, so there's no way it could be written down

Hello, I am attempting to run an audi a5 b8 2.0tdi caha manual transmission ecu in a petrol Q5 with the 8 speed tiptronic driven by a us spec cjaa. I have the engine installed and running fine already

Using the funktionsrahmen I have changed trans type, gearbox intervention, engine type and a variety of other data fields in the ecu but I am still getting p0614.

There is this post from a Belarusian individual that made it work with a 3.0t to 4.0t swap but not much information is there.
https://www.drive2.com/l/560647852024397875/
(If your in here help me out please)                                                                                                     

I keep getting error 31/out of range in vcds when trying to code it to automatic.
Maybe I am missing something?

From what the FR says this is possible within the ecu it just needs turned on.

Unfortunately I don't have access to a programmer capable of pulling the trans file so I am at the mercy of just smudging the communications data.

any insight is appreciated.