NefMoto

Since attempting a tune I've had some timing CF's so I've been told to log the bits associated with torque intervention/anti judder.

I found a thread where phila_dot uploaded a list of the bits to log. Some of these don't appear on my .cfg file that me7logger kindly spits out for me. I wondered if i could just add them to the .cfg file? I've attempted to add them but not sure if it'll work.

Attached is the list from phila_dot (thanks!) and my new .cfg file with them added. If its possible to just add them - have I done it correctly? If its not possible how can I log these bits so i can try and identify what is causing the CF's

I didn't want to just numb KFDMDARO and run loads of logs and then just assume that it's sorted it.

Mbox extras here

https://github.com/nyetwurk/ME7L/tree/master/ecus

You must also add them to the .ecu file. Use the ram addresses on nye's page :P

the ecu files i use

http://files.s4wiki.com/ME7L-ecu/

Thanks a lot guys,

I'll attempt to add them to the ECU file and then create a .cfg file with the new bits that nyet posted. Not sure how limited I am with me7 logger but I'll try and log all the ones related and hope to see if it's that causing the issue.

I haven't modified IOP in my tune, I am requesting more load than standard via LDRXN and I have also enriched via LAMFA. Could IOP be the reason I have torque intervention?

You need to log TI first and find the variable that's causing it.

I'm in the process of adding the new variables to the .ecu file and as far as I'm concerned I've done it properly :) though im a bit unsure which file format to save it as, when I click 'save as' on the notepad I get some form of warning about it being saved properly. I have the options to save it as ANSI, Unicode, Unicode big endian or UTF-8.

ANSI was the default but I'm not sure if this is correct. I'm also unsure if it matters if I have some duplicates in my .ecu file I'll try my best to check but there is a chance I could unknowingly have a duplicate - does this matter?

I'd really like to do some more logging soon to try and find the reason for the timing pull and I can start to make some minor timing changes  ;D

utf8 or ansi are your best bet

Thanks nyet  :)

I'm just pasting in the info from the link you sent of m box extras into the .ecu file and the same for the .cfg file, do i need to remove the map addresses when pasting the variables into the .cfg file or will that not matter  ???

I'ts taking me ages to remove the map addresses after I've pasted them into the .cfg so if I don't need to remove them i don't want to be lol

Thats what scripting is for :P

Learn perl or python or sed or awk

Sorry, I have limited sympathy :)

Why not just use these as is?

http://files.s4wiki.com/ME7L-ecu/8D0907551M-typical.cfg
http://files.s4wiki.com/ME7L-ecu/my_8D0907551M.ecu

Got myself a raspberry pi so I'll try my hand at python eventually  :P

I appreciate the help and do try to take on all the info that people give me, though I'm a massive noob but trying my best to not ask dumb questions.

If I'm able to use them that would be a lot easier, i wasn't sure if it mattered that my ECU is different though? 06A 906 032TL is the one i have.

If those will work then i'll use them, i also notice you have a .cfg and .ecu for a 06A 906 032LP on github - not sure if thats a better option?

thanks again

Obviously the RAM locations are different.


You'll have to find the RAM locations if you haven't already.

Ah right, no where near as simple as I had hoped!

I think at the moment finding the RAM locations is going to be way out of my capabilities unfortunately. I only have the two files below with the basic stuff in that ME7info finds which has been great so far but i don't have the variables for TI.

I think the only real way for me to see if these timing corrections are because of TI would be for me to numb it slightly and see if the corrections go and take lots of logs so I can be sure its gone, if i never learn to add variables. I'll do some searching, hopefully someone on here has been through a similar problem.

Ti is injection timing, so can we not make this anymore confusing by making up new acronyms.

If zwist == zwsol it's torque intervention, else if zwist == zwbas it's not.

Sorry for being confusing Phila_dot and thanks for the reply.

That's made sense to me and I'll go and log that tomorrow evening, hopefully ill get to the bottom of it then.

thanks  ;D

Looks like torque intervention until around 5250 revs. must look at stage 1 thread for ideas lol