![]() |
OP2 logging discussion
Hi everyone,
The EcuFlash thread is getting pretty cluttered, I'd like to fork off the OP2 standalone logging discussion before it becomes impossible to find the information I (and hopefully others) need. I'll do my best to update the main post with useful information as we go along. Here is my work-in-progress logcfg.txt file. Here is a B01c logcfg.txt provided by Steve99. Use this if you're running an OFT 2.xx map. TD-D's initial list of addresses: Code:
E_AF_Correction_1_2byteExtExt_E82 FFF89B48 |
Reserved for additional info.
|
I have been trying to find the correct MAF reading in CFM, so far I've tried two and while the outputs correlate with eachother, they are not identical. They follow the trend I expect but they seem like they are reading low, I would expect more airflow given the condition.
Here's my log, more or less flat-foot in 5th gear on the highway: http://datazap.me/u/adriang/ots-stag...7&zoom=239-430 "maf default" is the default address from the sample logcfg.txt: Code:
paramname = MAF_default Code:
paramname = MAF_TddWith @Td-d's help I see now that the AFR as listed above is the LAMBDA value, and we can get the ratio by multiplying the provided value by 14.7. This math can be applied on the OP2 directly, as such: Code:
paramname = AFRI've confirmed now with the correct data type that gear and gear_calculated work. Thanks Td-d for clarifying that they are 8 bit values. Funny enough, one reads neutral as 6, the other reads neutral as 0... It is my understanding that reading the RAM parameters is much faster and more efficient, using gear at 0xFFF895D9 is my preference. Code:
|
Gear parameter is not float - it's 8 bit.
I.e. databits = 8 There's a great utility called logcfg.exe that will autogenerate a logcfg.txt file for you from the Romraider definitions. https://dl.dropboxusercontent.com/u/3099895/logcfg.exe |
Quote:
|
Quote:
Code:
E_Knock_Correction_Advance_4byteExt_E43 FFF8B0AC |
hello fellas.
I used the logcfg file in the first post and it logs and works great. However, I notice that I am missing MAF Voltage. Any idea why? I've tried a few different log cfg files that work but none log MAF Voltage. Any help is appreciated, thanks. |
Quote:
;paramname = MAF_Voltage ;paramid = 0xFFF842AC ;databits = 16 ;scalingrpn = x,0.000076293945,* remove the ; and it should work fine its same address as G rom and wrks fine for me paramname = MAF_Voltage paramid = 0xFFF842AC databits = 16 scalingrpn = x,0.000076293945,* |
Quote:
|
I'm using the a01c version of the oft 1.59 tune. The Commanded AFR address appears to be incorrect for this particular combination. Any idea what it is?
|
Quote:
have you tried paramname = AFR_Commanded paramid = 0xFFF8A974 isfloat = 1 scalingrpn = x,14.7,* else you will have to ask Td-d If your doing MAF scaling use the VGI utlilty as it imports your OL fuel table from Romraider so you don't need to log Commanded AFR just measured AFR and the utility does the rest see here http://www.ft86club.com/forums/showthread.php?t=64790 |
Quote:
Quote:
Commanded AFR = 14.7 - (14.7 * x) in RPN I think that would be this: Commanded AFR = 14.7,14.7,x,*,- I'm not sure if this is the correct notation for this formula or not. Also, I came up with this for throttle plate percentage. I think it's correct. Quote:
|
Quote:
That scaling for AFR works for me on G rom, usually just the address changes and scaling are same. |
Try this:
FFF8DBD0 Ram_Fuel_Air_Commanded |
| All times are GMT -4. The time now is 03:28 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by
Advanced User Tagging v3.3.0 (Lite) -
vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.