1
on: Today at 09:09:38 AM
|
||
Started by Pendrak - Last post by EanDem | ||
Here you go
|
2
Noob Zone / Noob Questions / Re: 8D0907551K Adapt charge control to the increased waste gate cracking pressure
on: Today at 08:47:55 AM
|
||
Started by M.Mischler - Last post by prj | ||
On quick look at last image looks OK. Sorry, but too much stuff to read and too little time.
|
3
on: Today at 07:12:11 AM
|
||
Started by jensen - Last post by jensen | ||
Break free from traditional dating norms and embrace the best in casual connections.
Looking for a one night partner. No continuation. Real-life Girls Unsurpassed casual Dating |
4
Noob Zone / Noob Questions / Re: 8D0907551K Adapt charge control to the increased waste gate cracking pressure
on: Today at 07:06:53 AM
|
||
Started by M.Mischler - Last post by M.Mischler | ||
Convert the map and your base boost to a pressure ratio and populate accordingly. To be sure that I understand you correctly, I'll ask you with specific calculation steps: To calculate the values for 600-970 hPa at 3500 rpm, I proceed as follows: I use the original value at 3500 rpm and 1010 hPa. So the value is 1540.4688 mBar: Now I calculate the pressure ratio by using my new base boost, in my case 1770 mBar at 1010 hPa and 3500 rpm. This results in a pressure ratio of 1770 / 1540.4688 = 1.14900088. Now I calculate all values for 600-970 hPa at 3500 rpm by multiplying the original values with the pressure ratio. The result: 921.0938 * 1.14900088 = 1058.3376 1074.5703 * 1.14900088 = 1234.6822 1151.3281 * 1.14900088 = 1322.877 1228.0859 * 1.14900088 = 1411.0718 1304.8438 * 1.14900088 = 1499.2667 1381.6016 * 1.14900088 = 1587.4614 1484.0625 * 1.14900088 = 1705.1891 If I want to calculate the values at 1750 rpm, I calculate the pressure ratio again. In my case 1150 / 1293.0469 = 0.8893722 Now I calculate all values for 600-970 hPa at 1750 rpm by multiplying the original values with the pressure ratio. The result: 921.0938 * 0.8893722 = 693.88403 1074.5703 * 0.8893722 = 805.4725 1151.3281 * 0.8893722 = 861.23196 1228.0859 * 0.8893722 = 917.02619 1304.8438 * 0.8893722 = 972.82033 1381.6016 * 0.8893722 = 1026.3911 1484.0625 * 0.8893722 = 1102.8216 And so on and so forth. Is that correct? |
5
on: Today at 06:31:00 AM
|
||
Started by C5AudiGirl - Last post by prj | ||
06 A6 4.2 is a ME7, what does EDC17 have to do with it?
|
6
on: Today at 05:55:27 AM
|
||
Started by C5AudiGirl - Last post by C5AudiGirl | ||
I am having no luck accessing an 06 A6 4.2 ECU. I can use cheap software such as bag commander to access it but I'd like to be able to pull the eeprom and disable the immo. Any advice on how to do this for a EDC17 ECU?
|
7
on: Today at 05:25:16 AM
|
||
Started by Pendrak - Last post by Pendrak | ||
Hello guys,
Are you able to help with unpacking this DQ250 Cxx SGO file to .bin? Thanks |
8
on: Yesterday at 11:18:48 PM
|
||
Started by Polo35580 - Last post by Albertoak | ||
Hello I'd like to share a python script I wrote to convert a damos (A2L) to fit a new dump. I wrote it in python to allow everybody to improve it. (and check there is no worm in it) You can imagine that the damos need to be as close as possible of the new dump. I mean same hardware but different software is ok but it's not applicable with different hardware. The script use a valid damos/dump couple in entry and a new dump to produce a new damos file. Supported ecus: ME7.5, MED91, EDC16U34, MED17 and SID208. The format of the dumps can be Intel Hex, Motorola S19 or Binary. The size must be 1024kb, 1504kb, 2048kb or 4096kb. It's possible to add support to new ecus by adding a new ecu definition in the script. For that the script contains a supportedeculist variable which hold ecu definition dictionaries. Ex: # MED17 - 0x80045320 "ecu" : "MED17", "cpu" : "TriCore", "addresslen" : 10, "addressstart" : '0x80', "addressformat": '0x80%06X\n' Meanings: # "ecu" : Ecu string found in A2L MOD_PAR entry (Ex: ECU "MED17") # "cpu" : Cpu type string found in A2L MOD_PAR entry (Ex: CPU_TYPE "TriCore") # "addresslen" : Length of address string in A2L CHARACTERISTIC records (Ex: 0x800574D8 -> 10) # "addressstart" : Sub string to remove to obtain an hex address where data can be found in dump file (Ex: 0x800574D8 -> '0x80') # "addressformat": Format use to rebuild an address line where 6 is the len of hex address without addressstart (Ex: 0x800574D8 -> '0x80%06X\n') The script will ask for an ecu and cpu type if there is no MOD_PAR entry in the A2L. Here is how the script process: - Read the damos file and create an address table - Read the original dump - Read the new dump - Correct the address table by searching best match pattern from original dump in new dump using dycothomic search method from original address - Linearize the address table - Create a new damos using the address table And here the command line to execute it: Code: python correct-damos-address.py DamosFile.A2L OriginalDump NewDump It take less than 10 minutes to correct most damos on my computer. There may be some mistakes due to linearization but it work pretty well in most case. Feel free to test it and report if it fit your needs. Edit: Update script to version 1.1. # ChangeLog : v1.0 - Original release # - Add MED17 Ecus support # - Add Intel Hex dump support Edit2: Update script to version 1.2. # ChangeLog : v1.2 - Add ME7.5 Ecus support Edit3: # ChangeLog : v1.3 - Add MED9.1 Ecus support # - Add EDC16U34 Ecus support # - Add Motorola S19 dump support # - Add supported ecu list to allow adding ecu type (See "Supported Ecu List") Edit4: # ChangeLog : v1.4 - Rewrite Intel Hex and Motorola S19 support to handle address bases # - Add SID208 Ecus support Best regards Polo Hello mate. I have modified the script to be able to make corrections in Ford's ME 9.0 ECU. in case you want to update the first post. I upload said script. greetings!!! # ME7.5 - 0x8574D8 "ecu" : "ME7.5", "cpu" : "S80166", "addresslen" : 8, "addressstart" : '0x8', "addressformat": '0x8%05X\n' }, { # ME9.1 - 0x1C9A02 "ecu" : "MED91", "cpu" : "GoldenOak", "addresslen" : 8, "addressstart" : '0x', "addressformat": '0x%06X\n' }, { # ME9.0 - 0x1C9A02 "ecu" : "ME90C", "cpu" : "GoldenOak", "addresslen" : 8, "addressstart" : '0x', "addressformat": '0x%06X\n' }, { # MED17 - 0x80045320 "ecu" : "MED17", "cpu" : "TriCore", "addresslen" : 10, "addressstart" : '0x80', "addressformat": '0x80%06X\n' }, { # EDC16U34 SIO - 0x1C2030 "ecu" : "SIO", "cpu" : "SilverOak", "addresslen" : 8, "addressstart" : '0x1', "addressformat": '0x1%05X\n' }, { # SID208 - 0xA0200AD4 "ecu" : "SID208", "cpu" : "TriCore", "addresslen" : 10, "addressstart" : '0xA0', "addressformat": '0xA0%06X\n' |
9
on: Yesterday at 02:58:49 PM
|
||
Started by fredrik_a - Last post by prometey1982 | ||
use a top hat from a pump that doesnt have the regulator and use a referenced fuel pressure regulator on the Rail so it'll scale 1:1 with boost if you're going for a higher power non decos car In such case he needs to set fuel pressure correction map FRLFSDP to 1. But he doesn't have address of this map)Although address of this map in 40LPHJ software is 0x23842 |
10
on: Yesterday at 02:40:56 PM
|
||
Started by fredrik_a - Last post by prometey1982 | ||
Thank you! Your KVB addr is 0x1F7FE, KRKTE - 0x23858 and TVUB - 0x15FEASorry for the late follow-up, I´ve not had much spare time lately but I tried this one out in the car and it did not work well. So I decided to go to the dealer and get the ECU updated. Software went from 30653124B 40LKMA.A2L to 30729127A 40LPHJ.A2L, Most annoying part is that I cannot see KVB in this version either I have attached binary read from the ECU after the update |