cewrx7r1

iTrader: (2)

Kyle and I just started using the new MAPWATCH function on the newest release of the DATALOGIT software. We are using a M&W UEGO 5 wire linear O2 sensor with it for Accurate AFRs. Using the resulting plotted AFRs on the NxP graph, is the greatest thing/improvement of the datalogit. Before it was very labor intensive to take a log file and convert to graphs using Excel, and then they were not that easy to use.

This solves all those problems. Plus you can also plot most of the log input parms.

artguy

cheers to that...fd racer and I are doing the same thing and it literally made life easy in the tuning dept...we got five times the amount of work done the other night with the mapwatcher as we did the previous two tries without.

finally POWER to the people! the userfriendly aspects are amazing.

Its a challenge to fill the map while driving around on the street...we used the freeway exits and entrances here in LA as our stomping grounds...

just curious...chuck..would it be alright to see your mapwatcher readings?? It would be a good teaching tool I think..for all of us to see the curve of your afrs and what your readings are.

thanks ahead of time...


j

cewrx7r1

iTrader: (2)

It is not really worth the trouble to post them because they will be different for every engine setup, even those very close to each other. You would need all the following: my engine mod list, PFC base fuel maps and correction maps including PIM changes, timing maps, and injector setup map.

What I can say is: if a cell was lean or rich, I changed that exact cell and it seemed to affect only that cell. A very close 1 to 1 relationship of cell reading and where to make the change. I made 3 back to back runs, modified any OUTLIER AFR readings to be closer to the two adjacent readings, took the three graphs of AFR averages, and then averaged them into one graph.
An outlier is a reading way outside the norm of the surrounding readings. Here is a simple example of AFRS:
11.3,11.2,12.1, 11.3,11.2. See that strange 12.1 in the
list, it is an outlier because of being way outside the norm and thus is an error reading. I would change it down to 11.3, the leanest of the two adjacent readings or esle delete that complete row of data.

If (P17,N10) and (P18,N10) were both rich and both were leaned out by 2%, the resulting AFR change was not linear. This is expected because the base fuel map for those cells are very different. I ended up with more fuel in some P17 columns than in the P18 cell below them. After I finish my P16 thru P19 row AFR fixes, I will use the new feature to transcribe the corrections to the base map so that my correction map will be 1.00 for easier future changes.

FD Racer

Hell yeah....the map watcher is awsome. Too bad the forum crashed...we lost some good post about the map watcher.

Chuck,
How about posting you latest (.dat) file from the datalogit? Just for observation of course, I completely agree with you on the whole different motor thing. And maybe your AFR readings on the map watcher from a good log? Maybe I'll PM you my email address if you'd prefer.

artguy

thanks for the info there...I was noticing the odd readings at times...fd racer and I checked to see how many times those cels were sampled. the error readings were often in cels that were sampled only one time.

I was thinking it would be good to see the afr map...not the inj map...correct me if I am wrong but we are all shooting for an 11.2-11.5 ratio or somewhere there abouts..with leaner numbers at vacuum and possibly a little richer up top. ..at least that is how we were doing my maps.

I thought it would be good to see the afr pattern on your maps...I do understand that your inj map numbers will be different due to your mod differences.

am i wrong to think that? should we not be going for similar afr patterns throughout the power band??

We have been transcribing the numbers to the base map after each run...starting at 1.00 definitely makes it easier to keep track of what you are doing.

j

cewrx7r1

iTrader: (2)

Here is an edited log file, the past peak rpm readings have been removed and the outliers fixed.

The column AN1 Wide is the UEGO AFR reading. Use Excell to view this file in true column format. The EXCEL version is too large for me to post it here.

artguy

thanks chuck...will take a look in a bit!!!!

getting ready to do some more tuning with fd racer...had some grounding probs and am concerned that the afrs are not correct...will add more grounds and double check.

seeing your afr setup will help...

thanks again

j

cewrx7r1

iTrader: (2)

Here is the txt file as a plot of AFRs.

cewrx7r1

iTrader: (2)

My maps.

FD Racer

Thanks Chuck!

While your at it, can we get a ".dat" file too?

Thanks

-Ray

cewrx7r1

iTrader: (2)

I do not have a dat file as the new software as we are using it does not create it anymore. It creates the TXT file which MAPWATCH uses. Use Excel to read the TXT file and edit it save it back as TXT. My 14psi runs had good AFRs in the 11.4 range while the 12psi runs had higher 11s. I am working on both 17 @ 18 rows to run mid 11s.

Goblin

I'm very excited about this feature (my Excel sheet took about 15 minutes to crunch my data into the same format... so much for my Excel programming skills...), but I've not downloaded it yet (still installing MSD).

Two questions.

Does it appear to map properly? The N/P numbers used to be off in one direction or another. Are they still, and are those numbers being used to generate ths data, and then do I have to correct for that when modifying the fuel correction maps?

Has the voltage to AFR conversion equation been expanded to a higher order poly? I could never get it to work right before, and wound up converting the raw voltages with a fifth order poly in the Excel sheet I used to generate the AFR map. Even when I would try the linear mapping it didn't work particularly well.

And, glad to see you back on the forum, Chuck. We've been worried about you.

cewrx7r1

iTrader: (2)

The maps are 20 X 20 and we think of 1- 20.
Evidently the PFC uses 0 - 19 and that caused the misplacements. The MAPWATCH corrects this but if you look at the raw data, they are still low by a count of 1 for my runs.

FD Racer

yes of course, but what I meant was the .dat file from FC edit, not the Map watcher.... my bad.

cewrx7r1

iTrader: (2)

We have not done a "READ" of my PFC to create a DAT file in over 6 months so it is outdated. Thus I do not have it as of today.

FD Racer

yeah i know how it goes....thanks anyways

yodaddy

i've been reading this thread and getting really excited to get a datalogit, but i have a couple of questions. with the mapwatch do you need a separate a/f meter or do you just use the datalogit as the meter? and do you have to run a separate wire for the wideband or do you just plug it in to the stuck plug? last one, do you need to have another o2 bung welded on to your dp or does the wide band replace the stock sensor. thanks for the help and i will appreciate any info you have.

artguy

you need a bung and a wideband...at least that is what we are using

j

cewrx7r1

iTrader: (2)

You can plug a wide ban into the stock bung and then into the DATALOGIT.

Our Houston test group uses a M&W UEGO 5 wire wideban with a tailpipe adapter if the regular bung is too hard to get to when hot. This makes it easier to switch between cars within 30 minutes of each other.
This wideban connects first to it's own controller/calibration unit before being connected to the DATALOGIT or PFC. With it in the taipipe holder, it leaves the stock bung free for use to plug our Greddy EGT into it.

The only drawback is that the UEGO cost about $1300. That is why 5 of us bought it together as a "test group".

yodaddy

sorry if i sound stupid but i don't know too much about this yet. can they diy be plugged into the dataloggit or does it just sit by itself.

i just reread your post on the control unit and have another question is that just the UEGO that needs a controller or do all o2 sensors need a controller/ callibrater before they plug into the dataloggit? what i'm getting at is i want to by a wideband sensor and plug it straight into the dataloggit. is that possible?

cewrx7r1

iTrader: (2)

The UEGO controller/calibrator is what makes it so linear and accurate. You get what you pay for! Some do not have it, they are not as accurate. We use the 5volt output to the DATALOGIT, not the 1 volt like a stock O2 sensor.