TunerPro User Forum

olafu

Hi,
Where is revlimiter value in Motronic M2.5 0261200191 ? Bin number 1267356243.
or M2.5 0261200185 bin 1267355632. If there is anybody who has any M2.5 XDF, i'm interested.

olafu

Yes. Lift this pin up from socket. Use short wires as possible. And 5V or 0V from chip socket. Use 1k pull-up, if you don't have on-on switch.

olafu

512k chip has one more address line compared to 256k chip. You need to switch this address line to 0V or 5V to change between upper or lower memory. It's not good to switch in running ECU, so i recommend to turn ignition off and wait 10 seconds before switching memory. You can find more detailed ins...

olafu

Live data is available from diagnostic "K-line" but any stock and practically any known tuning chips doesn't broadcast data except when requested. Transfer rate is quite slow, but might be enough, if you log only load and rpm. There is no any magical high speed realtime login, which allows...

olafu

I'm not a pop and bang guy, but this might help: http://forum.tunerpro.net/viewtopic.php?t=5245

olafu

In M50 engines the TPS / RPM based "Alpha N" map produces similar load signal like normal MAF based operation. So, this Alpha-N map affects to ignition also.
Fuel maps are still in use like normal MAF based operation.
I think this is similar in M3 ecu.

olafu

Header starts at 0x6F00, table starts at 0x6F0D. Problem is it's shared for coolant temperature sensor and air temperature sensor. Tables are identical between vanos engine and non vanos engine. I think M50B25NV has no air temperature sensor in MAF. Air temp sensor is located under intake manifold l...

olafu

There is no actual hysteresis in revlimiter. Only behaviour like it has. This is 413/623's revlimiter code, 506/965 has similar revlimiter, but it reads revlimit value from RAM (0x18A8), instead of reading it from ROM in 413/623. 506/965 program has also part which is used to read revlimiter values ...

olafu

You must to find way to disable ignition secondary current monitoring when using ignition cut in rev limiter. Otherwise you will get coil fault codes on random cylinder(s) and DME will switch their injections off. In dirty way you can ground DME pin 15, and you get fault code from secondary current ...

olafu

506 and 413 has differences in knock control parameters, because bore and stroke are different, but otherwise it's not a problem to mix these bins. Use 506 or 413 parameters depending on which engine you are using.

olafu

Any stock bins from -413 doesn't have this table or even function to use table based revlimiter.

olafu

This "Vanos dwell table" in XDF from Tunerpro site has nothing to do with vanos. It's injection timing table. M3.3.1 vanos can be full advanced or full retarded, it has no closed loop control like Siemens ecu in M52 engine. Vanos solenoid valve is also different design in M52 to suit close...

olafu

Please tell the ECU/DME number and the program number when asking definition.

olafu

Checked: XDF for -951.bin will mess the -548.bin file, because in -548.bin the checksum is in different address. Data end = 0x7BF7, store address = 0x7BF8. Looks like XDF for -951.bin fits at least partially, ignition tables and fuel tables seems ok, so change that checksum address and keep in mind ...

olafu

What XDF you are using to edit that bin? Chip number in this rar file was 1267356548.

olafu

But if your bin file has address spacing up to 0xFFFF it is 64kB file, so it couldn't never come out from a 256k chip.

olafu

What happens with no checksum correction in XDF? I tried to save .bin without any modifications and "BMW_dme405_soft951.xdf" will change the checksum anyway. So i think there is something wrong with checksum calculation, or there is something wrong with stock file "BMW_405_1740352_126...

olafu

Hi, It's not a problem to create new XDF item (as example new table), but it's problem how to recognize relevant parts of parameters. Ways to do it: 1. Disassembly program code and learn how things is done(maybe impossible), or 2. Try to find all parameters and systematically try to modify and look ...

olafu

Yes. Motronic pin 66 disconnected and 623 bin should work.

olafu

V8 software has similar problem than every six cylinder except US M3. I can't say which RAM address is surely unused in 404 or 413, but in US M3 ecu has the RAM address for rev limiter. It's vital for this launch rev limiter. So only bullet proof variable launch can be available for US M3 ecu.

olafu

Looks like this D9 is somekind of injection/ignition event counter or something like it. D9 starts from 0 and it counts to 255 in about 30 seconds@1000rpm and in 10 seconds @ 3000rpm... Doesn't roll over. It stays on 255 when it reaches it.

olafu

I think I found the same in a 413/623 bin: Individual cylinder correction at 0xD0FA ? There is 8 values at 128, but maybe just 6 are used? Cranking fuel enrichement at 0xDB93, a 5x1 table with ECT as descriptor, very close of cranking fuel table, scaling and datas are coherent with what I have in t...

olafu

Let's dig this thread up again. Vehicle speed dependent rev limiter in -965.bin It has two parts: Part 1 - Get rev limiter value from 2d table and store it in to SRAM: ROM:5B61 A1 86 00 1A ld INTMEM_1A, #86h ; Pointer loading for map lookup table (1) ROM:5B65 B3 01 7B 18 1C ldb INTMEM_1C, RAM_187B[]...

olafu

In some cases it would be useful, if there is possible to set several flags in one "XDF item", e.g. all 8 bits are in flag form at same "Flag/switch item". Every bit named/specified separately. Also some kind of switch panel would be nice, so you don't need to open every flag/swi...

olafu

You can try to find it, if you have diagnostic scanner which is capable to show if closed loop is active or not. I think the O2 bit is somewhere in 0x6B02 - 0x6B20. Plug o2 sensor back and let engine idle and warm up. So the closed loop o2 control switches on. Try to change those bytes to "00&q...

olafu

Looks like closed loop is active, but AFR should be around 14.7 then... :? I think M3.1 has similar "emission stage" flag than M3.3.1 has, but unfortunately anyone wasn't put it in the XDF file. If you got diagnosis scanner, you can see if closed loop is active. Those table values are fuel...

olafu

Tell more about your emulator..? Did you have green based "emulating" text at the bottom of Tunerpro window?

olafu

Hi guys! I have installed Garrett GT2860 on stock m50b25 NON VANOS and want to get 280 - 300 hp Compression ratio is about 9,7 with a 2 mm head gasket. From what I heard stock head gasket can stand 1.0 bar It runs now and drivable, however I didnt rev it more than 3000 RPM My boost controller is se...

olafu

Seems like that speed based rev limiter is only M3 (us and euro) thing. In M3.3.1 this is very simple difference and i think it is very similar in M3.1. 3.3.1 ecu's -965.bin has this one table for rev limits. Program picks rev limiter value from table and stores it in to RAM. Rev limiter part of pro...

olafu

Yes, seems right. With conversion "x-32768" those table addresses are correct... Maps also include more than just adjustments. This map starts from 7222, but in XDF you put start address 7234. CF 10 05 08 0A 0C 08 0B 0A 0A 09 0A 0C 0A 09 06 0A 60 8B 8A 8A 8F 8C 8C 8C 8D 8E 8E 8F 8D 8E 8C 8...

olafu

I think you can also move this map lookup table to make more space to increase size of existing tables.. 0x7DFC-7DFFF (FA 5C FB 34). FA5C tells to ecu where is start of the table (there is two bytes "self reference" at start of this table) and FB34 is first "blank" byte after che...

olafu

Yes, it is "the table of tables". F044, F064, F06C and so on are map addresses, but you must subtract them by 8000h, so you will find the maps from 7044, 7064, 706C and so on.

olafu

Yes, but last table address is in 0x7B2A. (so last table starts from 0x7A52, it's just before this map lookup table)

olafu

-599.bin: First table address founds from 0x7A5E "44F0" -> 0xF044 -> it has 8000h offset: First table founds from 0x7044.

olafu

Quotes from my tests: "with maf fault mode (alpha n) max rpm with internal rom: 7980rpm. :roll:" (without cam signal) "max rpm with internal rom: 8340rpm" (with MAF, without cam signal) I didn't test what happens when table sizes are expanded. Internal rom means that the test was...

olafu

0xDC73 - Coolant temperature dependent overrun fuel cut RPM. Fuel cut is active above those RPM values (x*40), when throttle is in "idle" position. Not very economy, but... By editing this table you can modify or disable overrun fuel cut.

Do you have emulator?

olafu

Bigger tables are slower to read. M3.3.1 reads first biggest axis values, and makes comparison again and again, until actual values are reached, then it makes interpolation. Fastest way out from table reading is when both axes are maxed out. If ecu goes too busy, it will reset itself.

olafu

http://www.villacarlota.net/volvo/motro ... %204.4.pdf
https://m44.fandom.com/wiki/M44_Wiki

olafu

I have TL866ii programmer. Works fine.

olafu

In theory it is possible to get BIN out from ecu through K-line, but easiest way is take EPROM-chip out and read it with eprommer. That way you can check the checksum and compare bin to original or other original one. There is several different stock chips in M3.3.1, depends on which car and engine ...

olafu

M3.3.1 calculates checksum after ignition is switched off, i think it is pretty last thing before the main relay is released. But if you put ignition back before calculation is performed, the fault code doesn't appear. Some chip tuners leaves wrong checksum for workshops etc.., for a sign of modifie...

olafu

Warning, these are for -413 ecu: Stock -413 ecu has (at least) three MAF plausibility limits, based by MAF table values*: - absolute flow minimum value (16bit) - absolute flow maximum value (16bit) - RPM dependent maximum flow value (looks like flow values divided by RPM). * Maybe there are similar ...

olafu

How did you copy that table? 402's -599.bin's XDF from tunerpro site has no conversion, but 413's -623.bin XDF has some conversion. Try to use "Show raw hex" (right click table and set "Show raw hex" on.) and then try to copy-paste. I'm never tried to change MAF sensor, but if -4...

olafu

Try to clear out what is those four tables: 0xE364, 0xE372, 0xE37E and 0xE378. At least one or two of those is lambda closed loop load switch off. I can't remember, i was noted all of those "closed loop related" but nothing more comments... Maybe copied from someone other's XDF as interest...

olafu

Parameter in 0xE06C (called "Target lambda" in several available XDF's) has nothing to do with closed loop control. It is similar fuel multiplier as fuel maps, and ecu reads it at every time just before or after fuel map reading(i don't remember).. 80h means multiplier is 1. It's 80h in ev...

olafu

DME part numbers and ROM numbers would help to get suitable XDFs.

olafu

Try to open that XDF with notepad. If it doesn't look like normal XDF file, you must download it again, but don't right-click and save as.. Try to download it in ZIP-packet. I don't know right way, but at least raw copy-paste from github works...

olafu

Hello again! I think i have some information for 0xE67E: code "ld SP+2, #xxxh" occurs repeatedly just before "lcall ROM_20C7" or "lcall ROM_20CD". It is pointer loading for 0xE67E map lookup table. If you want to find different parts of code by specific maps, you can ch...

olafu

Looks like those wot maps needs : - closed loop must be enabled (0xD00B bit2) - engine must be run in closed loop for a while.. few minutes? - throttle position goes over "WOT" switchpoint (WOT switchpoint table is in 0xD540-D543. RPM axis is hard coded in program. Table values are TPS raw...

olafu

I don't surely know, but WOT maps are propably in use only with closed loop active. Or something else will block it.
And about those lambda off maps, you must to clear out how it works, i can't help. Never tried to adjust them, only played with them by test.

Search found 186 matches