Incorrect AFR at WOT Help!!

[glock-coma]

Glad you got everything squared away.
Good job reading the logs and diagnosing the problem ajpturbo.  You are very valuable to this forum.

 

[BiGMaC]

Glad you got everything squared away.
Good job reading the logs and diagnosing the problem ajpturbo.  You are very valuable to this forum.

Ditto^^^
Glad it's fixed... Good job ajpturbo!

 

[ZSHO]

Great to hear it was a smooth process and your issues were resolved without anyone mentioning or condemning any such tuning company's credibility.makes me wonder to say the least.mmmmmmm.  Z

 

[SHOdded]

Well, not to belabor the point, but in this case:

a) the data available was logged
b) the logged data was made openly available for analysis
c) analysis said the issue was with hardware, as made obvious from the data

So why would the tuning company be blamed?  Having data openly available does help to build statistics for reliability, MTBF, etc. for the platform.  Isn't that desirable?  This is how we know that bank 2 O2s are more prone to failure or there are leaky injector issues or hoses/hoseclamps are subject to coming loose/splitting on the EBs.

Granted, it IS easier to make the tuning company the fall guy when the data is in a "black box" where we cannot see within/analyze.  As these vehicles age, and service histories remain unknown, having datalogging as an option is invaluable.

IIRC, the MyCal device does have logging capabilities, but not sure it could be accessed by the owner/enduser due to the proprietary nature of the information collected therein, as stated by LME.

 

[ZSHO]

Well, not to belabor the point, but in this case:

a) the data available was logged
b) the logged data was made openly available for analysis
c) analysis said the issue was with hardware, as made obvious from the data

So why would the tuning company be blamed?  Having data openly available does help to build statistics for reliability, MTBF, etc. for the platform.  Isn't that desirable?  This is how we know that bank 2 O2s are more prone to failure or there are leaky injector issues or hoses/hoseclamps are subject to coming loose/splitting on the EBs.

Granted, it IS easier to make the tuning company the fall guy when the data is in a "black box" where we cannot see within/analyze.  As these vehicles age, and service histories remain unknown, having datalogging as an option is invaluable.

IIRC, the MyCal device does have logging capabilities, but not sure it could be accessed by the owner/enduser due to the proprietary nature of the information collected therein, as stated by LME.

Thank you for sharing your insight and perspective but unfortunetly i beg to differ.  Z

 

[SHOdded]

Perfectly a-ok :thumb:

 

[FoMoCoSHO]

So can you data log with the mycal or not?

 

[ecoboostsho]

There was an "original" version of the mycal that had a much fancier screen and allowed datalogging but I don't believe the current mycal is capable of data logging by design. 

That said I recommend that everyone should datalog...while I use Torque for my gauges but my recommendation for logging would be to check out forscan.org and do a couple of baseline runs when your car is healthy to establish some norms...then if something goes awry you can datalog again and look at the differences which may lead to a diagnosis of the issue at hand.

 

[SHOdded]

There was an "original" version of the mycal that had a much fancier screen and allowed datalogging but I don't believe the current mycal is capable of data logging by design. 

Thanks for the clarification, ecoboostsho!

 

[FoMoCoSHO]

Huh.

Data logging wins again!

 

[curry67]

i have seem to be having problems with my o2 sensors aswell but i also have a knock issue so seeing your logs with 0 a max makes me depressed lol

 

[SHOnUup]

Datalogging, great for pinpointing issues gone wrong.

Rich

 

[ajpturbo]

i have seem to be having problems with my o2 sensors aswell but i also have a knock issue so seeing your logs with 0 a max makes me depressed lol

Fix your O2 sensor and go from there...these systems are so complex and dependent of other things u could have a multitude of things going on...for instance there are spark and fuel modifiers for lengths of time spent at various afr's....so if the afr is at a certain amount for so long it may see fit to modify spark or fuel. These compensations will be on top of base tables......fix the sensor as I thought we identified that issue at least earlier....I'm losing track..can remember if that was u or brewer

 

[curry67]

Got some new fuel from different top tier brand knock as high as 7 now. The afr2 went to 0 a few times bit otherwise it appears to be working.

Sent from my SM-N910W8 using Tapatalk

 

[FoMoCoSHO]

Got some new fuel from different top tier brand knock as high as 7 now. The afr2 went to 0 a few times bit otherwise it appears to be working.

Sent from my SM-N910W8 using Tapatalk

My AFRs randomly go to zero and both cars behaved the same.

 

[curry67]

Got some new fuel from different top tier brand knock as high as 7 now. The afr2 went to 0 a few times bit otherwise it appears to be working.

Sent from my SM-N910W8 using Tapatalk

My AFRs randomly go to zero and both cars behaved the same.

so it going to 0 randomly for a few seconds is ok?

 

[ajpturbo]

Got some new fuel from different top tier brand knock as high as 7 now. The afr2 went to 0 a few times bit otherwise it appears to be working.

Sent from my SM-N910W8 using Tapatalk

Sometimes data stream can get disrupted  and you will see 0 for a split second but it shouldn't happen very often....So if it went to 0 a few times then I don't know if I would say It appears to be working ....Doesn't sound good...I forget, did I look at one of your logs?

Just saw your new post....But NO! a few seconds is not ok....A tiny blip is the data stream being lost

 

[FoMoCoSHO]

Got some new fuel from different top tier brand knock as high as 7 now. The afr2 went to 0 a few times bit otherwise it appears to be working.

Sent from my SM-N910W8 using Tapatalk

Sometimes data stream can get disrupted  and you will see 0 for a split second but it shouldn't happen very often....So if it went to 0 a few times then I don't know if I would say It appears to be working ....Doesn't sound good...I forget, did I look at one of your logs?

Just saw your new post....But NO! a few seconds is not ok....A tiny blip is the data stream being lost

AJP's explanation is what I have experienced running Torque, Dashcommand, OBDLink, etc......

 

[curry67]

https://drive.google.com/file/d/0BzPC7uX6FB_AUkZtV01FNzVQWU0/view?usp=sharing

 

[ajpturbo]

Got some new fuel from different top tier brand knock as high as 7 now. The afr2 went to 0 a few times bit otherwise it appears to be working.

Sent from my SM-N910W8 using Tapatalk

Sometimes data stream can get disrupted  and you will see 0 for a split second but it shouldn't happen very often....So if it went to 0 a few times then I don't know if I would say It appears to be working ....Doesn't sound good...I forget, did I look at one of your logs?

Just saw your new post....But NO! a few seconds is not ok....A tiny blip is the data stream being lost

AJP's explanation is what I have experienced running Torque, Dashcommand, OBDLink, etc......

My old mustang was terrible, I think because of the cave man processor..The more items you log the worse it is. SOme PID's take more memory or something like that....I think its like bandwidth...SOme PID's require a lot of it...Or sampling rate I dunno....I notice better quality logs when I reduced the amount of paramters I log