|
mister t
|
 |
« Reply #30 on: December 28, 2016, 02:51:47 AM »
|
|
|
Downloaded the whole 800GB package yesterday.
Not very much useful information in it in my opinion.
Lots of already known DAMOS resp. OLS Files.
Some internals incl. tools (useless w/o hardware), mails, etc.
But not even a single one FR.
I respectfully disagree. This DAMOS pack has all of the N/A V8 files (i.e. B6/B7 S4 4.2 V8, RS4 4.2 FSI, it even has a close relative of the 3.0 V6 DAMOS if you look under the 4DOxxx559x files). It also has a ton of the most recent MED 17.5 DAMOS files which are not found in the usual DAMOS downloads. |
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #31 on: December 28, 2016, 07:46:44 AM »
|
|
|
I respectfully disagree. This DAMOS pack has all of the N/A V8 files (i.e. B6/B7 S4 4.2 V8, RS4 4.2 FSI, it even has a close relative of the 3.0 V6 DAMOS if you look under the 4DOxxx559x files). It also has a ton of the most recent MED 17.5 DAMOS files which are not found in the usual DAMOS downloads.
Ive been through an number of the .a2l files for the me9,1 and none of them line up properly, so I would suggest dont take the values as gospel! |
|
|
|
|
Logged
|
|
|
|
|
gman86
|
|
« Reply #32 on: December 28, 2016, 08:18:34 AM »
|
|
|
Ive been through an number of the .a2l files for the me9,1 and none of them line up properly, so I would suggest dont take the values as gospel!
Can you give an example of a dodgy one? Are you using the included .S19? |
|
|
|
|
Logged
|
|
|
|
metronet
Full Member
Karma: +5/-0
 Offline
Posts: 73
|
|
« Reply #33 on: December 28, 2016, 11:14:38 AM »
|
|
|
it even has a close relative of the 3.0 V6 DAMOS if you look under the 4DOxxx559x files
I went through the 4E0910559E file (A4W5E_2g.A2L) and can confirm the addresses line up. According to ETKA it is for a 2004+ D3 A8 with ASN engine code in Mexico or "rest of world". (Note: corrected the ECU part#) |
|
|
|
« Last Edit: January 04, 2017, 10:32:19 AM by metronet »
|
Logged
|
|
|
|
|
littco
|
|
« Reply #34 on: December 30, 2016, 04:26:30 AM »
|
|
|
Can you give an example of a dodgy one? Are you using the included .S19?
I have seen a couple of people post up map references based on the .a2l's which aren't correct. Now I have to admitt I'm not sure how you use the included .s19 as well.. |
|
|
|
|
Logged
|
|
|
|
|
gman86
|
|
« Reply #35 on: December 30, 2016, 04:29:32 AM »
|
|
|
I posted up an incorrect map address for an 8P0907115AP file, but hadn't appreciated that the different sw ver numbers didn't line up properly (quite unusual in MED9). Once I double checked the offset, it was fine.
If you're using WinOLS, you can drag it straight in as a new project. Or when you create a new project, you can use a standard binary dump, or a Motorola-Hex (*.s19) file. That's the format these files are supplied in.
|
|
|
|
|
Logged
|
|
|
|
|
Jerry Tunin
|
|
« Reply #36 on: December 30, 2016, 10:47:01 AM »
|
|
|
I posted up an incorrect map address for an 8P0907115AP file, but hadn't appreciated that the different sw ver numbers didn't line up properly (quite unusual in MED9). Once I double checked the offset, it was fine.
If you're using WinOLS, you can drag it straight in as a new project. Or when you create a new project, you can use a standard binary dump, or a Motorola-Hex (*.s19) file. That's the format these files are supplied in.
There are lots of file extensions I'm not familiar with. Could anyone shed some light on what each of these extensions are for? SW BOSCH\Serie\ME7.5\X505P\24HG_1\4B0906018CM\0008: 0008.7z 1037378160.CNT 1037378160.mcs 20050803.log 24HGCM8g.A2L 24HGCM8g.hex 24HGCM8g.mcs 24HGCM8g.raw 24HGCM8g_PED.log 24HGCM8o.hex 4B0906018CM_0008.sgm 4B0906018CM_0008.sgo Bat_030.bat cntbat_003.bat fill.txt fillCop.bat LCT_vorb.log PatInf_g_1037378160.txt ped.log Ped_030.ped sgm2sgo.log TOFLOW.TXT X24hG08g_doc.cmp |
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #37 on: January 03, 2017, 11:23:55 AM »
|
|
|
I posted up an incorrect map address for an 8P0907115AP file, but hadn't appreciated that the different sw ver numbers didn't line up properly (quite unusual in MED9). Once I double checked the offset, it was fine.
If you're using WinOLS, you can drag it straight in as a new project. Or when you create a new project, you can use a standard binary dump, or a Motorola-Hex (*.s19) file. That's the format these files are supplied in.
Got it working.. |
|
|
|
« Last Edit: January 03, 2017, 11:39:50 AM by littco »
|
Logged
|
|
|
|
|
mister t
|
|
« Reply #38 on: January 03, 2017, 12:15:58 PM »
|
|
|
I went through the 4D0907559E file and can confirm the addresses line up.
According to ETKA it is for a 2004+ D3 A8 with ASN engine code in Mexico or "rest of world".
Yeah, a 3.0 V6 definition has been incredibly elusive. I remember when I started my own definition project on that one, absolutely no one could provide me with a definition file from that engine family. I ended up patching a functional one together using mainly Porsche V8 ME 7.1.1 and VW VR6 ME 7.1.1 files. Having said that, I'm kind of glad that I had to make my own definition files for both the V8 and V6 before finding these. I've spent so much time looking at raw hex dumps that I can find all the maps I need in just about any ME 7 file in my sleep now lol. |
|
|
|
|
Logged
|
|
|
|
|
ktm733
|
|
« Reply #39 on: January 03, 2017, 04:05:56 PM »
|
|
|
I went through the 4D0907559E file and can confirm the addresses line up.
According to ETKA it is for a 2004+ D3 A8 with ASN engine code in Mexico or "rest of world".
I don't think I would try tuning this ecu if I were you. |
|
|
|
|
Logged
|
|
|
|
metronet
Full Member
Karma: +5/-0
Offline
Posts: 73
|
|
« Reply #40 on: January 03, 2017, 11:10:13 PM »
|
|
|
Having said that, I'm kind of glad that I had to make my own definition files for both the V8 and V6 before finding these. I've spent so much time looking at raw hex dumps that I can find all the maps I need in just about any ME 7 file in my sleep now lol.
Good for you! It's definitely been a good learning experience for me as well. It's just that the learning curve is so deep! lol I don't think I would try tuning this ecu if I were you.
Ah... Gotcha. Just out of curiosity, is it a very different setup in terms of the hardware...? Thanks! |
|
|
|
|
Logged
|
|
|
|
hopsis
Full Member
Karma: +13/-4
Offline
Posts: 174
|
|
« Reply #41 on: January 04, 2017, 12:06:56 AM »
|
|
|
Without cluttering this thread any more, ASN is a 3.0 V6 (horrible engine to tune) but 4D0907559E is a S6 6MT 4.2 ANK (little less but still quite horrible to tune) binary. Something doesn't add up.
|
|
|
|
|
Logged
|
|
|
|
|
KasperH
|
|
« Reply #42 on: January 04, 2017, 07:03:02 AM »
|
|
|
anybody willing to upload all the 06a906032hn files so i can analyse them and pick thm apart?  Thanks in advance. |
|
|
|
|
Logged
|
|
|
|
metronet
Full Member
Karma: +5/-0
Offline
Posts: 73
|
|
« Reply #43 on: January 04, 2017, 10:30:27 AM »
|
|
|
Without cluttering this thread any more, ASN is a 3.0 V6 (horrible engine to tune) but 4D0907559E is a S6 6MT 4.2 ANK (little less but still quite horrible to tune) binary. Something doesn't add up.
No, you're right. 4D0 is for the C5 chassis. The damos I looked at is 4E0910559E (A4W5E_2g.A2L). I am not sure which one mister t was referring to now lol... |
|
|
|
|
Logged
|
|
|
|
metronet
Full Member
Karma: +5/-0
Offline
Posts: 73
|
|
« Reply #44 on: January 04, 2017, 11:14:56 AM »
|
|
|
Also it seems like the A8 fitted with the 3.0L (ASN or BBJ) has no quattro, FWD only?
|
|
|
|
|
Logged
|
|
|
|
|
