NefMoto > Noob Zone > Noob Questions (Moderator: turboat) > Questions about reading/flashing ME7.1 VR6
Pages: [1]
« previous next »
Author Topic: Questions about reading/flashing ME7.1 VR6  (Read 1344 times)
Marshmallow5555
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« on: June 20, 2024, 10:45:51 AM »
Hello, I've been browsing this forum for quite some time and I think I'm just about ready to finally actually pull the ecu data from my 12v VR6 Jetta (VAG NUM 021 906 018m, ME7.1 G 6760) but I still have a few questions before I do.
I have already read, written, and flashed 5 different tunes on my EDC15 ALH TDI using a MPPS v18, and had originally thought that it would be the same process for the me7.1.
I've ordered a KKL 409.1 FTDI cable to use the Nefmoto software for this because it seems to be the better option for the ME7, as when I try to read just the ECU ID with MPPS, it just says "NO DTCs FOUND"Huh but for some reason if I select ME5.9 as the ecu it pulls the ID telling me its a 7.1?
 I have a real Ross Tech (HEX V2) that I trust and that's where I got the ME7.1 G 6760 ID. So here are my questions:

Do I need to use Bootmode to read/flash an ME7.1 ECU?

Do I need to disable the immobilizer to make changes to the ECU file? or How important is it that I have a copy of my EEPROM? ( which I would assume would then require bootmode anyway)

Does anyone have any experience using the nefmoto software for the 12v VR6? (as its not listed in the tested section of the software)
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2796
« Reply #1 on: June 20, 2024, 11:13:28 AM »
Quote from: Marshmallow5555 on June 20, 2024, 10:45:51 AM
Hello, I've been browsing this forum for quite some time and I think I'm just about ready to finally actually pull the ecu data from my 12v VR6 Jetta (VAG NUM 021 906 018m, ME7.1 G 6760) but I still have a few questions before I do.
I have already read, written, and flashed 5 different tunes on my EDC15 ALH TDI using a MPPS v18, and had originally thought that it would be the same process for the me7.1.
I've ordered a KKL 409.1 FTDI cable to use the Nefmoto software for this because it seems to be the better option for the ME7, as when I try to read just the ECU ID with MPPS, it just says "NO DTCs FOUND"Huh but for some reason if I select ME5.9 as the ecu it pulls the ID telling me its a 7.1?
 I have a real Ross Tech (HEX V2) that I trust and that's where I got the ME7.1 G 6760 ID. So here are my questions:

Do I need to use Bootmode to read/flash an ME7.1 ECU?

Do I need to disable the immobilizer to make changes to the ECU file? or How important is it that I have a copy of my EEPROM? ( which I would assume would then require bootmode anyway)

Does anyone have any experience using the nefmoto software for the 12v VR6? (as its not listed in the tested section of the software)






You should be able to read and write it with mpps without an issue vw>golf>2.8 me7.1. Really it does not matter what you pick under vag me7 it will still read it. its default is vag 400bb/800bb. Nefmoto should be able to read it out but to be honest you are better off with mpps. Mpps will do boot mode too, check under the generic tab>vag> AM28F400. Sometimes if the ecu was tuned before you will not be able to read the tune out that is in it, if that is the case you will need to bootmode it. Anyway, it would be in your best interest to get comfortable with a bench flash setup and getting the ecu in bootmode. At some point you will need it. Its as simple as forgetting to update the checksum and mpps does the checksums too so that's nice
« Last Edit: June 20, 2024, 11:15:44 AM by _nameless » Logged
Giving your mom a tuneup
Marshmallow5555
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #2 on: June 20, 2024, 11:50:40 AM »
Quote from: _nameless on June 20, 2024, 11:13:28 AM
You should be able to read and write it with mpps without an issue vw>golf>2.8 me7.1. Really it does not matter what you pick under vag me7 it will still read it. its default is vag 400bb/800bb. Nefmoto should be able to read it out but to be honest you are better off with mpps. Mpps will do boot mode too, check under the generic tab>vag> AM28F400. Sometimes if the ecu was tuned before you will not be able to read the tune out that is in it, if that is the case you will need to bootmode it. Anyway, it would be in your best interest to get comfortable with a bench flash setup and getting the ecu in bootmode. At some point you will need it. Its as simple as forgetting to update the checksum and mpps does the checksums too so that's nice

Thanks for the fast response, Ill just send it with MPPS using the "2.8L 12v BOSCH ME7.1.1 K-Line" option then and see if it will read. As far as I know it hasn't been tuned, just an old lady that owned it before me.
I had never even noticed the generic tab before, thanks for bringing that to my attention. Ill look into putting together a bench for it soon too.
Also I've been using the MTX checksum tool for TunerPro RT so hopefully we don't have any problems there anytime soon.
Logged
Marshmallow5555
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #3 on: June 20, 2024, 03:56:37 PM »
So I tried a read using the "2.8L 12v BOSCH ME7.1.1 K-Line" option in MPPS, and it was unsuccessful.
The read quit itself, said "Unknown Error" and printed out blank hardware and software numbers in the ecu data section.
Is there something I could have done wrong? Again I'm 99.9% certain this car is not tuned, bone stock from a dealership when I got it.
Should I take it out and throw it in boot mode or should I wait until the KKL arrives and try to read it through OBD again with NefMoto?
Logged
Marshmallow5555
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #4 on: June 20, 2024, 04:50:14 PM »
So I ran it again as a 2.3 VR5 and it read just fine, so now I got my .bin. The XDF I have from ddillenger is close enough to my bin so I should be able to edit it to make it work
thanks for the help.
Logged
gremlin
Hero Member
*****

Karma: +194/-9
Offline Offline

Posts: 649
« Reply #5 on: June 21, 2024, 08:40:39 PM »
Quote from: Marshmallow5555 on June 20, 2024, 04:50:14 PM
, so now I got my .bin.

The attachment contains the source file (bin) extracted from the dealer update flash container (SGO file).
You can compare it with the bin file obtained from your ECU to check for intact original contents.
Logged
Marshmallow5555
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #6 on: June 29, 2024, 04:41:11 PM »
Quote from: gremlin on June 21, 2024, 08:40:39 PM
The attachment contains the source file (bin) extracted from the dealer update flash container (SGO file).
You can compare it with the bin file obtained from your ECU to check for intact original contents.
Hey sorry I didn't see this earlier, went on vacation. thanks loads, ill compare them soon.
Logged
Marshmallow5555
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #7 on: June 30, 2024, 12:30:55 PM »
I've compared the two bins and they are exactly the same as far as I can tell,
but I still have a few maps messed up in this xdf file im using
(I got it from a thread where ddillenger posted it and modified it to work with these bins).

so now that im looking at all of these maps here, im a little confused at to what VARDEF is
(as its not mentioned in the glorious s4 tuning wiki), and what the column axis should look
like for LAMFA, right now the RPM row axis seems right but the column axis (which should be
requested torque if I understood the s4wiki correctly) seems off. Right now it goes from 29.77
 to  108.20 with 6 columns? if its requested torque this wouldnt make sense because KFPEDs
highest returned value is 60.724(unless this is wrong too?).
Logged
gremlin
Hero Member
*****

Karma: +194/-9
Offline Offline

Posts: 649
« Reply #8 on: June 30, 2024, 03:02:56 PM »
Your LAMFA is wrong defined. Right definitions see below picture.
% axis is mraf_w value - relative driver request torque from CCS (cruise) and pedal.
It's not equal mrpeds_w value taken direct from KFPED map.

The fixed value VARDEF contains a programmable default variant.
This default variant is used if the variant stored in the EEPROM is recognized as invalid.
The recognized variant is invalid if it cannot be found in the internal table (regardless of what is in the VARTAB table.)
VARDEF = 00031 @ $12038
VARTAB (map 16x1) @ $1D138
« Last Edit: June 30, 2024, 03:20:34 PM by gremlin » Logged
Marshmallow5555
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #9 on: June 30, 2024, 05:05:54 PM »
Quote from: gremlin on June 30, 2024, 03:02:56 PM
Your LAMFA is wrong defined. Right definitions see below picture.
% axis is mraf_w value - relative driver request torque from CCS (cruise) and pedal.
It's not equal mrpeds_w value taken direct from KFPED map.

The fixed value VARDEF contains a programmable default variant.
This default variant is used if the variant stored in the EEPROM is recognized as invalid.
The recognized variant is invalid if it cannot be found in the internal table (regardless of what is in the VARTAB table.)
VARDEF = 00031 @ $12038
VARTAB (map 16x1) @ $1D138


Thank you very much, I fixed the XDF and this lambda table makes MUCH more sense now.
While I dont exactly understand what you mean by variant here, Id assume this just has to
do with the immobilizer then? do I really need to worry about the immobilizer or the VARDEF/VARTAB values if I'm just
doing tuning for some light mods? I also included a screen shot of the updated LAMFA and VARTAB/VARDEF tables I just defined as it was not
included in this XDF prior and I'm still very new to all of this.

side note: surely a .90 lambda from the factory is a little lean right?
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 09, 2024, 09:47:20 AM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.023 seconds with 16 queries. (Pretty URLs adds 0.004s, 0q)