Wod
Newbie
Karma: +0/-0
 Offline
Posts: 3
|
 |
« on: July 11, 2021, 11:08:08 AM »
|
|
|
Hey guys, Its been a few years since i even touched 1.8t. Now when i did that was MED9 series, My friend has MED7.5 and so I now have the LAMFA map. However I cannot make sense of the values, could someone refresh my mind for me please? It says values are Lambda but they are clearly not. I simply wish to use his AFR gauge to calibrate fueling at full load is all.
Thankyou and best wishes
|
|
|
|
|
Logged
|
|
|
|
|
BlackT
|
|
« Reply #1 on: July 11, 2021, 12:21:15 PM »
|
|
|
512kb ECU? I never dig too much in it, but from my point of understanding it use BTS all time
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #2 on: July 11, 2021, 12:21:48 PM »
|
|
|
That map definition is wrong, or it is just set with very high values to remain entirely disabled.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
overspeed
|
|
« Reply #3 on: July 11, 2021, 02:14:51 PM »
|
|
|
Wrong adress, and values skyhigh are to disable
|
|
|
|
|
Logged
|
|
|
|
|
Sandstorm3k
|
|
« Reply #4 on: July 11, 2021, 11:35:32 PM »
|
|
|
I need to look in my addresses later, but it's definitely what 512kb LAMFA should look like. But i believe it's not in the right order. It's somewhere on the forum aswell.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #5 on: July 12, 2021, 10:50:02 AM »
|
|
|
I need to look in my addresses later, but it's definitely what 512kb LAMFA should look like. But i believe it's not in the right order. It's somewhere on the forum aswell.
If it does prove to be the right location, all values >1 mean LAMFA is disabled in that region. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
BlackT
|
|
« Reply #6 on: July 12, 2021, 11:11:54 AM »
|
|
|
I see this on few 512 kb ECUs and it is stock stock. They use BTS for fueling
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #7 on: July 12, 2021, 12:04:18 PM »
|
|
|
I see this on few 512 kb ECUs and it is stock stock. They use BTS for fueling
Makes sense to me. is TABGBTS ignored? if so this relates to another issue a member was seeing (don't have link handy) |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
BlackT
|
|
« Reply #8 on: July 12, 2021, 12:47:29 PM »
|
|
|
Makes sense to me. is TABGBTS ignored? if so this relates to another issue a member was seeing (don't have link handy)
I never dig too deep into those 512 kb . It is not worth it when conversion to WB is cheap and easy |
|
|
|
|
Logged
|
|
|
|
Wod
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #9 on: July 13, 2021, 11:17:41 AM »
|
|
|
Thankyou for the help guys, you was correct. Address was wrong by one byte. Also correct that MAX VALUE is ignored, I verified this myself after suggestion by changing MAX VALUE's.
By the way, don't try to write with Galletto1260 to 29F400BT. It reads perfectly fine but will not write.
Writing InitilizationOK
Seed key... OK
Erasing...Flash:29F400BT
OK
Start writing...ERRORE WRITE
ERRORE WriteBlock 10000
Cheap MPPS cable worked perfectly for the job and made recovery without boot mode (Thankfully).
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #10 on: July 13, 2021, 11:29:30 AM »
|
|
|
The clue is the address is odd (ends in 0xF) and i believe its a 16 bit map.
16 bit maps should always be 16 bit aligned.
This is a bug in whatever is being used to convert A2L/Damos to winols.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Wod
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #11 on: July 13, 2021, 11:35:00 AM »
|
|
|
The clue is the address is odd (ends in 0xF) and i believe its a 16 bit map.
16 bit maps should always be 16 bit aligned.
This is a bug in whatever is being used to convert A2L/Damos to winols.
That would make sense, is this bug just regarding LAMFA and its X axis because I imported about 26 maps in total and they came out perfectly defined? |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #12 on: July 13, 2021, 11:41:56 AM »
|
|
|
Yep. I believe there is something buried somewhere in the definitions where the map location may or may not include the signature byte.
WinOLS is picky about this, but something in the A2L/Damos definition makes it less so.
I have not had the time to investigate more thoroughly, but it only happens on a few maps.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
TeknoFi
Full Member
Karma: +1/-3
Offline
Posts: 85
|
|
« Reply #13 on: August 13, 2022, 05:38:06 PM »
|
|
|
Hey guys, Its been a few years since i even touched 1.8t. Now when i did that was MED9 series, My friend has MED7.5 and so I now have the LAMFA map. However I cannot make sense of the values, could someone refresh my mind for me please? It says values are Lambda but they are clearly not. I simply wish to use his AFR gauge to calibrate fueling at full load is all.
Thankyou and best wishes
Hello, i have same identical looking map in my 1.8T lamfa map. as mentioned above, moving one byte should fix definition file in that regard. I'm just making sure that after the correction, the content of your 0.0 line has moved to the last line 98.4? so this is correct if it is moved there? I also assume (like said before) that those 1.9923 in other rows are completely normal, i.e. disabled, but they could possibly be enabled (1.00 for example). |
|
|
|
|
Logged
|
|
|
|
|
