NefMoto

The following translated modules are now on the Nefmoto wiki and also in a single indexed PDF file with a note on which aspects of tuning each is relevant to (attached to this post).

ARMD 10.40 (Torque-Based Anti-Jerk Function)
ATM 33.50 (Exhaust Gas Temperature Model)
ATR 1.60 (Exhaust Gas Temperature Control)
BGSRM 17.10 (Cylinder Charge Detection, Intake Manifold Model)
FUEDK 21.90 (Cylinder Charge Control [Calculating Target Throttle Angle])
GGHFM 57.60 (MAF Meter System Pulsations)
KRDY 17.120 (Dynamic Knock Control)
KRRA 15.130 (Knock Control with Individual Cylinder Retard)
LAMBTS 2.120 (Lambda for Component Protection)
LAMFAW 7.100 (Driver's Requested Lambda)
LAMKO 9.80 (Lambda Coordination)
LDRLMX 3.100 (Calculation of LDR Maximum Cylinder Charge rlmax)
LDRPID 25.10 (Charge Pressure Regulation PID Control)
LRSHK 9.20 (Continuous Post-Catalyst Lambda Control)
MDBAS 8.30 (Calculation of the Basic Parameters for the Torque Interface)
MDFAW 12.260 (Driver Requested Torque)
MDFUE 8.50 (Setpoint for Air Mass from Load Torque)
MDKOG 14.70 (Torque Coordination for Overall Interventions)
MDZW 1.120 Calculating Torque at the Desired Ignition Angle)
RKTI 11.40 (Calculation of Injection Time ti from Relative Fuel Mass rk)
SLS 88.150 (Secondary Air Control)
ZUE 282.130 (Fundamental Function - Ignition)
ZWGRU 23.110 (Fundamental Ignition Angle)

Thanks Doug!  Are you fluent in German?  Also, what are KFPU, KFPUKLP1, KFPUKLP2 and KFPUKLP12?

In the module it says:
KFPU   – Pulsations map
KFPUKLP1 – Pulsations map with active adjustment element 1
KFPUKLP12 – Pulsations map with active adjustment elements 1 and 2

But I'm not sure what those are exactly.  Perhaps I don't have access to them in Maestro.

Doug, any chance i can dissuade you from continuing to use word format, and get you to put it somewhere with better revision control, portability, indexability, and searchability?

Having 3 zillion versions of different word documents floating around (with no tracking of changes, or centralized location/url etc) is really very suboptimal.

Not that we don't all appreciate your efforts (we do)... but I find this very unwieldy :(

O.k. What do you guys suggest? I can do Adobe PDF easily.

Please bear in mind that it takes many hours effort even with the aid of Google Translate to get a good translation so I'm not particularly open to any other format that requires significant additional work. Translating these modules is interesting and is expanding my knowledge but are keeping me from a labour of love: Michael Rohde & Jens-Peter Sirup's book on the Mercedes-Benz W123.

I'm not fluent in German, just reasonably well-schooled in the nuts and bolts of modern languages, I suppose.

I'm not sure what KFPU, KFPUKLP1 and KFPUKLP12 are actually. Worryingly, I couldn't find them in any of the fully-defined files I have. :-\

I will delete any Word documents and stick with PDF from now on.  ;)

Doug

Word is fine to start with; just hoping we could eventually centralize it in the wiki, or even docbook under svn/git or whatever

not a fan of google docs. like you said, thats even harder to use than a directory full of .doc files :)

I can offer hosting space... if you are the only one editing the docs (for now), it would make sense to just keep them in word format. I can even host it under a domain name of your choice (assuming you pay for the domain name :)

I just really dislike attachments on a msg board as an archive method...

email me nyet at nyet dot org if you want to take it there also.

I don't have any problem with anyone on here uploading any material I've made available to this site's Wiki.

I have my own prejudices on wikis after contributing factually correct, official, well-researched information on two places I've worked at to Wikipedia itself only to find that (a) Wikipedia plastered a big warning on it stating that the information appeared to be copied from elsewhere and (b) other users come along and fiddle or tinker with it.

I don't want my output fiddled or tinkered with, especially translations. If it's incorrect or inappropriate, tell me and I'll correct it personally. Surely that's the best way to keep tabs on revisions?

TTQS

Absolutely. If you are the only one making revisions, then a wiki is pointless!

IMO all you need is hosting space so you don't have to put up attachments to a post in an obscure thread :)

Bump.

LDRPID 25.10 (Charge Pressure Regulation PID Control) added 8th August 2011.
Minor correction to GGHFM.

I've had to put a lot of extra manual effort into LDRPID, but in a small number of instances, there might be better translations. Please feed back any suggested improvements if you notice any. Also, feel free to update the Nefmoto wiki with this info. I don't have the time I'm afraid.

Regards.

TTQS

BTW this is what subversion/git is for :)

Cool. I must be like a Stegosaurus or something because I've never heard heard of svn/git.

I'm sure somebody will fix something better up eventually but I've reached "The Outer Limits" of my abilities.

TTQS

Revision control is as old as the hills... certainly predates MSWord

1982 - rcs
1986 - CVS
1994 - bitkeeper
2000 - subversion
2005 - mercurial
2005 - git

Microsoft was obviously blissfully unaware of how nice it is to keep documentation under revision control when they "designed" MSWord.

AWESOME. Thank you Doug. ATM looks like it took quite a bit of effort!

Request: more of the MD blocks :)

Specifically, fast and slow path torque intervention.... MDZW, MDKOG, and the mother of all things timing, ZUE

Thanks.

Yes, ATM must have took a week or so on and off. I'll do my best with other requests.

I tried to modify the Nefmoto wiki with a view to transferring these to that format, however I received an error message telling me that I wasn't in the group 'Users'. I've e-mailed Tony to see what can be done but until it gets worked out, I'll have to stick to PDF.

TTQS

Bump.

MDKOG 14.70 (Torque Coordination for Overall Interventions) added 23 August 2011.
MDZW 1.120 Calculating Torque at the Desired Ignition Angle added 25 August 2011.
ZWGRU 23.110 (Fundamental Ignition Angle) added 25 August 2011.

I'm not sure I'll have time to translate many more this year, although I am enjoying the endeavor. I'm on vacation for two weeks then I'll have about two months of studying in my spare time for work.

TTQS

Once again, thank you so much!

The only "important" one left on my list now is ZWGRU..

Take a break Doug!  :D And thanks for your efforts!!!

I've put most of these in the Nefmoto wiki now but I didn't realise due to my Cretacious period understanding of computing that there are so many flavours of wiki mark-up language. The Wikipedia format seems the most reasonable.

I'd like to contribute MDFAW and LDRLMX which are all relevant to understanding the torque model better. I'll see what I can do...

TTQS

FUEDK 21.90 (Cylinder Charge Control [Calculating Target Throttle Angle]) added 19 September 2011.

TTQS

MDFAW 12.260 (Driver Requested Torque) added 23 September 2011.

LDRLMX 3.100 (Calculation of LDR Maximum Cylinder Charge rlmax) added 6th October 2011 as attached PDF and also to the Nefmoto wiki.

This module covers LDRXN and KFTARX so is useful background reading for tuning these parameters which are covered in the S4 wiki.

TTQS

Doug, you're the man when it comes to actually understanding these modules!

Nye and Matt, after seeing all of these posted for a while without even a hint of repercussions, I guess I got unnecessarily paranoid about posting those translated full versions with my name next to them.  I'm don't mind now, and I'm curious if my efforts are actually being beneficial for anyone.  Do any of you guys use my full translated versions much?  Is there any way to tell how many times they've been downloaded?

And to any newer people who have yet to find this thread, who might want to do automated google-translate, you would likely not get much better/different of a translation than from the full translated documents, because both of the methods that I used to translate it utilized google-translate as a part of it.  Just a heads up FYI so that other people who aren't using a "human touch" don't unnecessarily waste their time doing the same thing.

Time for me to put some of this study material to use!

thanks for all your hard work :) make me a better tuner

Thanks for your kind words. I was reluctant to spend so much time on it, but good though Google Translate is, I honestly didn't feel that the unfiltered output was clear enough for people to use as it came; particularly since there seems to be quite a number of Nefmoto users whose first language isn't English. I.e., garbled technical English is going to be potentially just as difficult for them to interpret as the original German.

I also tried to apply some general technical/engineering understanding to the situation to perhaps help get a clearer translation than a raw verbatim German to English. That's what took the extra time...

Now that my studying is over, I will try to find some time to translate a few other key modules. I want to learn about idle control and that seems to be a relatively popular topic for discussion too.

Doug

Bump.

LAMFAW 7.100 (Driver's Requested Lambda).doc added 3rd December 2011. I'll have a look at the modules covering idle control next unless there are any special requests.

TTQS

Bump.

MDFUE 8.50 (Setpoint for Air Mass from Load Torque) added 25 December 2012. Next up will be SLS 88.150 (Secondary Air Control) for master_j.

TTQS

It's really great to have you back translating my friend! Thank you my friend for all your hard work. Merry Christmas/Happy Holidays.

Thanks Rob. Much appreciated. Now that I no longer have to learn Company Safety Rules, I can go back to more rewarding pastimes. There's always some nugget of information to be extracted from the good old ME7.x funktionsrahmen! The big boys might have moved on to MED9.1, MED17, SIMOS 8 or whatever, but the panel beaters, spanner w@nkers and drip tray men at the bottom rung of the tuning ladder can still feed on crumbs from the rich mens' tables. KWIM? ;)

Happy Christmas, New Year and best wishes. I hope Nefmoto grows even more in 2012.

TTQS

Bump.

SLS 88.150 (Secondary air control) attached to this post and here

http://nefariousmotorsports.com/forum/index.php/topic,1306.msg12227.html#msg12227

and on the Nefmoto wiki.

TTQS

Bump.

BGSRM 17.10 (Cylinder Charge Detection, Intake Manifold Model) added to Nefmoto wiki which is relevant to the following thread on recalibrating KISRM when changing overall engine displacement or intake manifold volume:

http://nefariousmotorsports.com/forum/index.php/topic,1312.msg12204.html#msg12204

TTQS

Awesome work. :)

Thanks Tony. I'm pleased to know that it's appreciated. I feel I still need to cover a lot more of these because I don't fully have a handle on all the subtleties of lambda control. Best endeavours though...

TTQS

I appreciate it too! Excellent work, as usual

http://nefariousmotorsports.com/forum/index.php?topic=1353.0title= (http://nefariousmotorsports.com/forum/index.php?topic=1353.0title=)


Add to WIKI?

Most definately. Exposed to search engines!

yup thanks for all the hard work Doug

Done.

TTQS

Bump.

LAMKO 9.80 (Lambda Coordination) added 07 January 2012. Also on Nefmoto wiki. Relevant to the following topic on use of LAMFA versus LAMBTS for tuning high load/WOT AFR.

http://nefariousmotorsports.com/forum/index.php?topic=141.0

TTQS

Nice!

Bump.

LRSHK 9.20 (Continuous Post-Catalyst Lambda Control) added 10th January 2012 and on the Nefmoto wiki to assist with understanding the integration of both pre- and post-cat lambda control if experiencing a malfunction on either system.

http://nefariousmotorsports.com/forum/index.php?topic=524.msg3961

TTQS

very nice :) Thank you

Hey, TTQS!

Are there any chapters dealing with Post cat o2 sensor heating? I've disabled post o2 correction, now my front sensor doesn't jerk around, but I still have limp (with zeroed out P1114 and P1118 from error class table). When I plug in my post cat o2 sensor (with fouler) I have no problems, but if I disconnect it I get limp. There has to be something with the heating of o2 sensor... Could there be situation like this: ECU checks o2, finds that it is disconnected sets LIMP and only then stores P1114; P1118 errors? So basically If I zero out error classes they are only not saved in memory, but the check is still performed?

Hi.

My first thought was that if post-cat lambda monitoring is deactivated, then I don't see why the probe heating should be causing a problem, but you could have a look at:

DHLSHK 4.50 Post-catalyst probe heating diagnostics starting on page 502
DHLSHKE 1.10 Post-catalyst probe heating end-stage diagnostics starting on page 505

I haven't translated them or attempted to analyse them in any way yet. Let me know what you find, or if you feel that a translation would be beneficial. I might not be able to do it for a while though due to work being heavy at the moment.

Regards.

TTQS

CDCHSH BLOKNR KL codeword CARB: lambda probe heating catalyst behind
 CDCHSH2 BLOKNR KL codeword CARB: lambda probe heater after catalytic converter; (Bank2)
 CDTHSH FW codeword tester: lambda probe heating catalyst behind
 CDTHSH2 FW codeword tester: lambda probe heater after cat, Bank 2
 CLAHSH FW error class: lambda probe heater after catalytic converter
 CLAHSH2 FW error class: lambda probe heating 2 behind Kat
 FFTHSH BLOKNR KL table environments heating lambda sensor downstream catalyst
 FFTHSH2 BLOKNR KL table environments heating lambda sensor behind cat bank 2
 FRINH1 TKATMF KL multiplicative factor for RIN setpoint behind Kat
 FRINH2 TKATMF2 KL multiplicative factor for RIN setpoint behind Kat
 KFRINH TKATMF PHLSNHF KF map for Nernst-impedance behind Kat
 KFRINH2 TKATMF2 PHLSNHF2 KF map for Nernst-resistance behind catalytic converter bank 2
 FW TADHMN lower temperature threshold for the diagnosis heater
 TADHMX FW upper temperature threshold for the diagnosis heater
 Total time errors TSFHSH FW: lambda probe heating catalyst behind
 Total time errors TSFHSH2 FW: lambda probe heater after catalytic converter, bank 2
 TVRI FW delay time for Ri-error after error amplifier
 TVRIF FW delay time for fault-Ri
 UBDLS FW battery voltage threshold for release of the probe diagnostics
 UBDLSMX FW upper battery threshold voltage for the sensor diagnosis
 ZKARIH FW Filter time for dynamic simulation of ceramic temp. from exhaust gas temperature. catalytic converter h.
 ZKPRIH FW filter for dynamic simulation of the ceramic probe temp. from electric heating catalytic converter h.


------------------------------------------------------------------------------
Maybe you could tell me what does CODEWORD TESTER MAP? I have found it in my bin but it has have weird value of decimal 14
 CDTHSH FW codeword tester: lambda probe heating catalyst behind

Also in funktionsrahmen there are always used CARB error codewords. I have never found them anywhere in my bin. Do they exist?

I'm thinking just to shortconnect this function by setting TADHMN very high... What do you think? ;)

BTW: CWDLSU and CWKONFLS are very interesting. Looks like they deal with postcat o2 sensor but I don't know their possible values

I'm not generally very well clued up on all these code words, sorry.


It looks like the tester code CARB function (DCDC 2.10) converts the error path identifier dfp output to the OBDII scan tool (OST) in modes 3 and 7 into the SAE standard J2012 format. "Each of the four types of errors is assigned its own value. It is necessary to perform this conversion at the project-specific level depending on equipment and customer philosophy".


Seems reasonable, if you think that deactivating probe heating diagnostics might cure the problem.

TTQS

This should be in another thread, but you have zeroed CDHSH and CDHSHE?

So rear O2's plugged in and everything's good, rear O2's unplugged = limp mode?

Yes and yes. It is a SOFT LIMP though (about 30% loss of torque).

BTW: I thought that zeroed out CDHSH and CDHSHE can't save DTC, but they do (unless you ofcourse zero them out in error class table). One of these are responsible for soft limp: P1114 and P1118.

I have split this thread from

http://nefariousmotorsports.com/forum/index.php?topic=555.msg4343#msg4343

KRDY 17.120 (Dynamic Knock Control)
KRRA 15.130 (Knock Control with Individual Cylinder Retard)

added 2nd May 2012 and on the wiki.

Knock is fundamental to high load and WOT calibration so it seemed reasonable to have a go at translating these. KRRA is 80-85% covered in the English Alfa ME7 funktionsrahmen. KRRA was generally tough going but there are a few nuggets in there such as the recommended margin to the knock limit (3 °crank).

TTQS

Thanks so much TTQS

I can't tell you how valuable your translations have been.

Ok. This is going to sound crazy.

TTQS, can you do ARMD next :)

TIA

O.k., I'll take a look. The two knock modules have been 'in my inbox' for at least two months due to work pressures so I was looking to scale back my efforts anyway, but no reasonable request will be refused...

I will reissue the PDF shortly due to correction of errors in KRRA that actually changed the sense and would cause confusion. I'll make sure the wiki text reflects the changes too.

TTQS

Yea i noticed a few "not"s that should be "now"s?

is that what you are referring to?

No, more serious than that. "away from advance" instead of "towards advance" even when the English funktionsrahmen had "towards advance" but I convinced myself otherwise! It doesn't help when nach can translate as after, towards, past, to, on, post-, following, for, by or under, etc. and you have a two month break between starting a document and completing it.

TTQS

for example, in BBMDEIN


and in MDBEG


the "not"s in both of those i find a bit weird...

the first sort of make sense.

the second... i'm not sure what it means ..

In the second case, that makes sense, i.e. monitoring is activated if there is an incorrect conversion to actual torque.

TTQS

TTQS, maybe you've read the MDVER chapter? I can not understand one thing: Is it for limiting torque so your wheels wouldn't slip (as Engine Drag Torque Control) or is it another torque calculation function?  ???

If I read it right, its for calculating engine losses due to temperature, climate control load, etc.

Thanks :) So finally I've fixed my problem with torque model :D

P.S> Maybe someone could tell me more info on these maps from RKTI section:

ZTSPEV - (from english f-rahmen "Time constant for forming the coil temperature of an injection valve") So this is time constant for actually calculating coil temperature or (from translated modules "Time constant for filtering evtmod taking tvu-control into account") intake temperature??? If it's intake temp why it is "calculated" instead of just using intake air temp sensor?

PVMITIBGR - (from translated modules "Proportional gain factor for torque limitation through continuous wave injection") So is this limitation when theoretical injection time > maximum injection time? Or is this something else? Also what type of value is this? percentage (in my ori file value is "2.4")?

KMITIBGR - (from translated modules "On-slope factor for the integration of dtimx_w through torque limitation") Is this the same as PVMITIBGR? I can't understand if this is limiter (when theoretical injector time > max injector time) then what type of value is in it? percentage also?

ARMD 10.40 added 22nd May 2012 to PDF file and Nefmoto wiki as requested. This was 90-95% the same content as the English language Alfa funktionsrahmen with some tidying up of the syntax and correction of a few errors.

All references to 'indexed torque' should now read 'indicated torque'.

TTQS

THANK you as usual, sir.

Great work!

Does there still exist a german version?

The German PDF file is still here:

http://nefariousmotorsports.com/forum/index.php?topic=400.msg2633#msg2633

and an English language PDF file for a normally-aspirated Alfa Romeo project is here:

http://nefariousmotorsports.com/forum/index.php?topic=1883.msg10355#msg10355

TTQS

Ah, yes! Its awesome.

I saw before and looked over it.
Now I see, that this example of 1,8T ME7 works the same as the S4. Its a "boost-based" load working ?!... (see on FB LDRUE)

Older 1,8T didnt. They were Air mass based.

While I don't know nothing about the ME7 stuff (yet), I am
a) German
b) Engineer
c) Know the 1.8T, 2.8 and 2.7T hardware

More than happy to help decipher techno German..

email what you need some Kraut insight on:

regulatorfix@gmail.com

I have manually translated a few sections, mostly complete. I did my best to fix grammatical/structure errors but I am not fluent in german. Just posting this up in case anybody doesn't want to plug away at translating.