Seeing 2-3 degrees difference in timing mp vs log.
Sep 11, 2012, 01:49 PM
#1
Seeing 2-3 degrees difference in timing mp vs log.
What would cause this other than the iat trim table which I have zeroed? 2 byte to 1 byte is set properly and I'm on sd 2.0 with 1:1 kpa load
Actually have you ever seen log resolution place the wrong timing adv vs load while loging?
Actually have you ever seen log resolution place the wrong timing adv vs load while loging?
Sep 11, 2012, 02:31 PM
#2
This is most likely your issue.
Your logging 1byte load (or 2byte load with LOAD_RAW as the address) and basically logging LOAD_RAW. Now RAW load works most of the time, but the timing and fuel map in 8859 V7 actually follow Load_Baro_n_Temp_Compensated, which at times can be different.
Solution is to configure 2byte load to log Load_Baro_n_Temp_Compensated and log both the newly configured 2byte load and 1byte load.
Your logging 1byte load (or 2byte load with LOAD_RAW as the address) and basically logging LOAD_RAW. Now RAW load works most of the time, but the timing and fuel map in 8859 V7 actually follow Load_Baro_n_Temp_Compensated, which at times can be different.
Solution is to configure 2byte load to log Load_Baro_n_Temp_Compensated and log both the newly configured 2byte load and 1byte load.
Sep 11, 2012, 07:19 PM
#5
This is most likely your issue.
Your logging 1byte load (or 2byte load with LOAD_RAW as the address) and basically logging LOAD_RAW. Now RAW load works most of the time, but the timing and fuel map in 8859 V7 actually follow Load_Baro_n_Temp_Compensated, which at times can be different.
Solution is to configure 2byte load to log Load_Baro_n_Temp_Compensated and log both the newly configured 2byte load and 1byte load.
Your logging 1byte load (or 2byte load with LOAD_RAW as the address) and basically logging LOAD_RAW. Now RAW load works most of the time, but the timing and fuel map in 8859 V7 actually follow Load_Baro_n_Temp_Compensated, which at times can be different.
Solution is to configure 2byte load to log Load_Baro_n_Temp_Compensated and log both the newly configured 2byte load and 1byte load.
the adresses you provided, which is wrong in 8859etc and I should be using the tephra 2byte to 1 byte the same, except correct the adresses. but the conversion scheme built into the tephra for 2.>1 is ok, just wrong adresses? MUT41 is the request id I have for 2>1byte.
JB, Im using GMIAT on sd2.0. . i will 0x03 myself here asap.
attatched a quick pic, in my logs it seems to hold a lot of timing out to peak load, usually 2 or 3 degrees where I normally have 0-1
3500, 266 load is clearly 1* in the table. I get 3. 3750 Im getting 2* when Im looking for zero.. I have been pulling timing to try and rectify the problem but it seems like before I go to far I think something is up.
Last edited by 211Ratsbud; Sep 11, 2012 at 07:33 PM.
Sep 11, 2012, 08:49 PM
#6
have you tried logging TimingMap?
similar to AFRMap whereby it tells you the timing it is targeting at that point.
on my ROM (88580014 - ADM Evo IX) it is MUT 33 - 6D67. EvoScan formula is x-20 just like normal timing.
cheers
similar to AFRMap whereby it tells you the timing it is targeting at that point.
on my ROM (88580014 - ADM Evo IX) it is MUT 33 - 6D67. EvoScan formula is x-20 just like normal timing.
cheers
Sep 11, 2012, 08:58 PM
#7
the adresses you provided, which is wrong in 8859etc and I should be using the tephra 2byte to 1 byte the same, except correct the adresses. but the conversion scheme built into the tephra for 2.>1 is ok, just wrong adresses? MUT41 is the request id I have for 2>1byte.
I didnt really understand what you said. But all you need to do is configure your MUT table 00 and 01 to read 2byte load, compensated. I checked and the correct addresses you need to use are.
2byte load
MUT 00 = 6B46
MUT 01 =6B47
When you log this 2byte load and log 1byte load, you will notice that the 2byte load is 20-30 less the 1byte load and it is what the timing map is following.
Last edited by Boosted Tuning; Sep 11, 2012 at 09:09 PM.
Trending Topics
Sep 12, 2012, 10:16 AM
#10
Any idea how to change the v7 load so it reads the correct load for fuel and timing?
Last edited by 211Ratsbud; Sep 12, 2012 at 10:20 AM.
Sep 12, 2012, 10:47 AM
#11
Tephra 1 byte load is actually 2 byte . I was asking if the addresses you provided would be in the same location which the the v7 2-1byte is pulled from thereby making you log the correct load . But in the last post you clearly stated to log load normaly used in v7 which is 2 byte converted to a one byte number then unconverted by your logger, and another 2 byte load which is compensated.
Any idea how to change the v7 load so it reads the correct load for fuel and timing?
Any idea how to change the v7 load so it reads the correct load for fuel and timing?
Usually keep logging 1byte and then just use 2byte to log compensated load. I would guess, if you want 1byte to read the compensated load, then you put the addresses I gave you in the MUT table at spots 41 & 42.
But like I said and for testing purposes, its best to continue logging 1byte load and just also log 2byte load that has been configured to log compensated load. Then you have them both and can check out the differences, etc. Then after making sure your car is follow compensated load, then you can configure 1byte load to read compensated load.
Last edited by Boosted Tuning; Sep 12, 2012 at 10:50 AM.
Sep 12, 2012, 07:37 PM
#15
And that's not the problem the two loads are within the same timing cells .. Edit in a hurry I put one address right and 01 in wrong.. So I saw the error while logging and switch to jot's thread addresses ,, I'll try the ones you have listed again and double check my entry this time .. Sorry for confusion I appreciate your help
This thing s dead set on 2* at peak load, which knocks like a mother****er sometimes! I have zeros in those cells!
This thing s dead set on 2* at peak load, which knocks like a mother****er sometimes! I have zeros in those cells!
Last edited by 211Ratsbud; Sep 12, 2012 at 09:51 PM.