[135Pats]

Originally Posted by secretsquirrel

I'm not sure why you'd say that. I know people get used to reading what they see often, but the procede logs are the only system that logs each value in its own chart. I have a much harder time reading JB or Cobb logs because you often have many values against a single chart. I think the biggest issue with procede logs is that some people don't zoom properly or highlight the section of time properly.

True, JB logs are the worst with every value transposed on the same chart for me it's best to just see it in a spreadsheet.

[Ænema]

Originally Posted by secretsquirrel

I'm not sure why you'd say that. I know people get used to reading what they see often, but the procede logs are the only system that logs each value in its own chart. I have a much harder time reading JB or Cobb logs because you often have many values against a single chart. I think the biggest issue with procede logs is that some people don't zoom properly or highlight the section of time properly.

This is just my opinion but i don't really like viewing any logs in graph form. At a glance if something is wrong it will jump out in a graph but i still prefer raw CSV files regardless of tune.

[cwarren]

Originally Posted by Ænema

This is just my opinion but i don't really like viewing any logs in graph form. At a glance if something is wrong it will jump out in a graph but i still prefer raw CSV files regardless of tune.

+1 on the graphs only give you part of the story imo... I have ran both jb and cobb and have never had any trouble with ready the graphs .but procede just is confusing to me and im not the only one. so in a nut shell more than likely the reason you get so little response on procede is most people have a tuff time reading them . bet you would get a much better response with the csv.

[KaiserN54]

Originally Posted by cwarren

This is just my opinion but i don't really like viewing any logs in graph form. At a glance if something is wrong it will jump out in a graph but i still prefer raw CSV files regardless of tune.

bet you would get a much better response with the csv.

well, e90post won`t let me post csv`s, so i post txt of them and people still ignore them. at least some are looking at them this time.

[JamesM3M5]

I quite like the Procede logs. Once you get used to selecting your data channel and hitting 'p' to rescale as needed, use the up and down arrows to zoom, it is similar to looking at other data logs from actual data logging equipment. I am currently looking into meth flow logs, and zooming in and out with multiple traces on different, yet time-synchronized graphs, is very helpful. Much like Motec. All traces on a single graph, like Aimsport, gets ugly quickly.

If you prefer a spreadsheet, well, then just open your spreadsheet with the .csv file directly.

I simply don't have time to even work on my own car, much less browse forums anymore. I'm sure others are either not online at all or at least not on many BMW forums in general due to the typical ass-hattery that tends to go on, unfortunately, in our circles, in many different BMW forums.

But I agree that your particular issue is injector or misfire related. Wildly varying AFRs points to misfire or dysfunctional injector. Varying but consistent AFRs points to an old sensor or some other single-bank problem such as an exhaust leak.