While datalogging and running multiple highway mode bins and playing with settings I found something interesting.

Fuel Data Value on Datamaster.

Runs at roughly 445, when I was invoking highway fuel it would drop to 405 and remain until it kicked out.

Is this any relation to the cumulitive fuel and distance in the ALDL stream as Rbob has suggested?

And if so, is my understanding of it correct. Higher number equates to more fuel and a lower number equated to less fuel used?

Any help here would be appreicated, looking for a good repaetable method to measure fuel use without driving myself insane.

later
Jeremy

 

The 445 and 405 values are the FA ratios being commanded by the ECM.

6553.6 / 445 = 14.7 AFR

6553.6 / 405 = 16.2 AFR

RBob.

 

Wel, darn!

Just when I thought I found soemthing useful lol

oh well

When I'm at the pow wow I'm standing next to u the whoe time and hopefully absord some brain power thru osmosis. :-) lol

edit: dug it up in their docs too :-(

later
JEremy

 

RBob - do you know of anyway to change what values are available or can be changed inthe DM views? In other words. any way to display the "fuel pump voltage" in DM with a $8D/730 setup in DM? Reason I ask is I'm using that particular field for my WB input. Works in TUnerPro with my ECU mods, but for some things DM datalogging is more "friendly" IMO....

Just thought I'd ask.....

 

Yep, it's the calculated fuel value. I try to have the calculated value match the actual a/f reading, when possible.....

 

I meant I wanted to display something else in this field....

 

I get the cumulative fuel counter out the ALDL by modifying the ALDL data steam in the bin. Location 0x0130 and 0x0131 on AUJP.


example log (I use a modified copy of Craig's old E6, followed by a Tcl script to clean up the log to show what I want)
<code>
RPM,TPS%,MPH,MAP,MAT,CTS,SA,BPW,INJ%,WBO2,AFR,DISTANCE,FUEL,TIME
1850,12,57,40,18,141,41.1,2.747,8.5,16.3,14.8,2,35256,248
1875,12,57,40,18,141,41.1,2.701,8.4,16.6,14.8,5,35272,249
1850,12,57,42,18,141,41.1,2.823,8.7,16.6,14.8,9,35288,249
1875,12,57,42,18,141,41.1,2.823,8.8,16.8,14.8,12,35304,249
1900,12,57,42,18,141,40.8,2.869,9.1,16.6,14.8,15,35320,249
1875,12,57,42,18,141,41.1,2.869,9.0,16.6,14.8,19,35336,249
1875,12,57,42,18,141,41.1,2.853,8.9,16.6,14.8,23,35352,249
1900,12,57,42,18,141,40.8,2.869,9.1,16.6,14.8,26,35376,249
1900,12,57,42,18,141,41.1,2.869,9.1,16.3,14.8,30,35400,249
1850,12,56,42,18,141,41.1,2.899,8.9,16.3,14.8,33,35432,249
1850,12,57,42,18,141,40.8,2.869,8.8,16.3,14.8,37,35448,250
1875,12,56,42,18,141,40.8,2.869,9.0,16.3,14.8,40,35464,250
1875,12,57,42,18,141,40.8,2.853,8.9,16.3,14.8,44,35488,250
1875,12,57,42,18,141,40.8,2.853,8.9,16.3,14.8,47,35504,250
1875,12,57,42,18,141,40.8,2.869,9.0,16.3,14.8,50,35528,250
1900,12,58,42,18,141,40.8,2.853,9.0,16.3,14.8,54,35544,250
1875,12,57,42,18,141,40.8,2.869,9.0,16.3,14.8,57,35560,250
1875,12,57,42,18,141,41.1,2.853,8.9,16.1,14.8,61,35576,250
1900,12,57,42,18,142,40.8,2.823,8.9,16.1,14.8,65,35616,250
1900,12,57,42,18,142,40.8,2.853,9.0,16.3,14.8,69,35632,251
1875,12,57,42,18,142,40.8,2.853,8.9,16.3,14.8,72,35656,251
1875,12,57,42,18,142,40.8,2.869,9.0,16.1,14.8,75,35672,251
1875,12,57,42,18,142,40.8,2.823,8.8,16.3,14.8,79,35688,251
1875,12,57,42,18,142,40.8,2.869,9.0,16.3,14.8,82,35704,251
1875,12,57,42,18,142,40.8,2.853,8.9,16.1,14.8,87,35728,251
1900,12,57,42,18,142,40.8,2.869,9.1,16.1,14.8,90,35760,251
1875,12,57,42,18,142,40.8,2.853,8.9,16.3,14.8,94,35784,251
1875,12,58,42,18,142,40.8,2.823,8.8,16.3,14.8,97,35800,251
</code>


Fuel counter is 544, distance is 95.

 

The cumulative distance and IP PW are already in the stock $8D ALDL stream. No need to modify it.

RBob.

 

Oh. I feel stupid now. I was wondering what the IP in IP PW stood for in the hack's label for those ALDL bytes. It just dawned on me... Instrument Panel.

 

Vernw,
You might want to try the "custom" data item on the "view" menu.
Lets you add an item with custom calculation.
I don't know if it's in the std version, I saw it when playing with the beta.

 

JP --- I've got legally licensed (I bought it) Datamaster 8D version 3.4.1 (build date 01-Dec-2001) for the 90-92 F cars (a100).

What is this beta version you mentioned? I don't have the "customize" option under the VIEW on this version.

However, I will say that what you referred to is exactly what I'd love to find! Any suggestions where I can find this Beta?

 

It was on the site software page(under beta) See if you can get it registered to use with your licence. If not you still get the 20 free times. Mine are all gone seemed to work, I didn't see anything that would indicate a problem. The histogram is nice with cell hit counts etc. I'll probably be getting it if they release it as a proven application.
the download file name is the same but it installs with the name "beta" so you should be able to put them both on the laptop and run separately.

Still there : http://www.ttspowersystems.com/DM_Beta_Software.htm

 

Just downloaded it, Thanks! Did you have to change your ALDL cable like they talk about?

 

I really don't remember doing anything special although I did use it with my Autoprom in "passthrough" mode.
It has a built in switch for putting the 10K but I don't remember if I needed to put it in that position or not (it was in the fall) Haven't done much yet this year, mostly TP & new XDF.
If you wanted to try it and find that you need to do it you could put the resistor across the ecm pins so you don't mess with the cable assembly.
I don't know if that would be easier than adding it to the cable at least until you can confirm that it is needed.

 

THANKS!!!