Anybody?
I don't have a Cobb AP (OpenECU user here), so I can't tell you how the map is setup. It could be that they setup the AF Learning table to not make corrections for WOT / OLF.juniebugs said:^ It's been about 100 miles. After looking at other datalogs for 2.0t's the zero A/F learning 1 value seems to be common under 100% throttle. Was just a little curious.
Very good information right here. I'm knew to EM (as you can tell by the off-the-shelf map) but I will be reading up. I would eventually like to go open source once my confidence and knowledge grows. Thanks everyone.I don't know if Cobb is just showing you that it wasn't used, or if it is saying the value is actually 0. The A/F in that cell will not be used in the WOT load range on any map Cobb or otherwise. Only the D cell (#4 in Cobb?) is used for WOT. From my understanding it doesn't try to learn anything for higher loads, it just throws that D cell at everything above (i.e. you are well above the load range that caused learning in that cell when you are WOT). I'm not sure if htat part is true for all years etc., but the A cell (#1) definitely is never used at WOT. It should learn a correction for that cell after a little while idling. If you had a tactrix cable you could just run learning view and see the stored values. I'm not sure how you would do that with Cobb. Some maps will disable learning in the D cell I think to keep WOT A/F stable (although it isn't actually stable anyways) but there should be no reason to disable the A cell.
I'm not familiar with Cobb's datalogger. Do they have multiple AF Learning 1 values (like with Romraider) or just a generic value (whatever the AFL is for that cell)? I know with Romraider, it's AF Learning #1 A, #1 B, #1 C, etc...mycologist said:I don't know if Cobb is just showing you that it wasn't used, or if it is saying the value is actually 0. The A/F in that cell will not be used in the WOT load range on any map Cobb or otherwise. Only the D cell (#4 in Cobb?) is used for WOT. From my understanding it doesn't try to learn anything for higher loads, it just throws that D cell at everything above (i.e. you are well above the load range that caused learning in that cell when you are WOT). I'm not sure if htat part is true for all years etc., but the A cell (#1) definitely is never used at WOT. It should learn a correction for that cell after a little while idling. If you had a tactrix cable you could just run learning view and see the stored values. I'm not sure how you would do that with Cobb. Some maps will disable learning in the D cell I think to keep WOT A/F stable (although it isn't actually stable anyways) but there should be no reason to disable the A cell.
Like you, I only know the situation with Romraider. I was confused about the same thing.I'm not familiar with Cobb's datalogger. Do they have multiple AF Learning 1 values (like with Romraider) or just a generic value (whatever the AFL is for that cell)? I know with Romraider, it's AF Learning #1 A, #1 B, #1 C, etc...
I know you had a Cobb AP at one point; wasn't sure if you'd played with datalogging...mycologist said:Like you, I only know the situation with Romraider. I was confused about the same thing.
You, Rick, Bill, Ron, and I all are OpenECU. We need someone familiar with Cobb tuning on staff...mycologist said:V1 - the cord worked with Romaider though lol. It also didn't lock out your ECU etc. etc.