Email me both bins, appropriately labeled so I know which works and which doesn't.

 

Send me an email and I can reply. I dont have your address.
z666wright@yahoo.com.

 

I should add, I am datalogging with Datamaster. Tuning with Tunerpro RT. Tunerpro RT rocks.

 

First page on tunerpro's website, click on the contact button - that's his email. I'd also be interested in seeing both bins. PMing you my email.

 

Sent to both. Hope they work.

 

Both files are identical (as I would expect). If one works, both should work.

However, I noticed that you haven't disabled the checksum. I highly recommend that you do so if you're going to be emulating, and even if not, to reduce the possibility of the checksum getting in your way.

 

How would the checksum get in your way? First time I've ever read of anyone suggesting to disable it.

Thanks,

 

More reading says me!

1) During emulation you make changes. (In this situation the checksum is not updated)
2) Your turn the key off (for 15+ seconds)
3) You turn the key on and try to start car
4) Car is in limp home mode.

Why? Because the bin in emulation memory has an invalid checksum, due to the changes you made.

To remedy the situation, you can:

a) disable the checksum
b) save the bin to file (which causes the checksum to be updated) and then re-upload it to the emulator

In the latest build of TunerPro, I got rid of the running checksum emulation mode because it, too, caused a lot of frustration for many people.

 

Thanks guys. I will try this again tomorrow. I hope you guys know, I am not complaining. Trying to help actually.
Also very interested in using the FAST wideband functions added in the xdf. Pretty sure I'll need help on that.

 

LOL...yah...more reading. Why do you think I'm here?

You just described a problem I have a lot...but never have figured out what is going on. Thanks for the edumacation.


I'm over on Tunerpro's site registering for the forum....first I even realized there was a forum there as well.

 

Not emulating. I'd be screwed if it went limp home. Burning E85 it wont even run on limp home programming. Just using Moates Burn2. I'm not that good at this, I actually have to think a while before making changes.

 

Not just e85 LOL, my 406 won't run in limp home either.

 

Both look identical to me as well. Though both have an item changed from the stock ARAP bin at 3FFF? Dunno what's there.

I did notice, just for giggles, that you didn't change the Stoich AFR. Since the stoich AFR for E85 is waaaayyyy richer than for the regular 10% ethanol fuel it may be a worthwile spot for you to start.

 

Just updated the XDF again. Was playing with the TCC lock and unlock tables and the numbers weren't making any sense. Looked it up in the hack and noticed that the tables in that were labeld tcc *** vs %tps in the xdf were labeled vs %load in the hack. Looking at the unedited points %load seems to make more sense in my head for what they are looking at so I changed it.

 

Stoich is stoich. Or Lambda. 14.7 is just a number to represent that. I can switch the Fast wideband from gas to alcohol and it will go from 14.7 to around 6. It doesnt really know the difference. Been running the E85 for 4000 miles. Had a good tune for winter blend, now switching to summer blend. And of course, looking for a little better ET. And still learning new stuff in general.

 

I was more referring to the pw calculation referenced here
https://www.thirdgen.org/forums/diy-...scellanea.html
in order to richen up the mixture for E85. Now of course if you have put in bigger injectors you may not need to mess with that number as the larger injectors will provide the extra fuel since you haven't modified that number.

 

Now I have more reading to do. The bin I sent you is working pretty well according to the wideband and Datamaster. I have compensated for the extra fuel needed with pressure and a couple tweaks in the tune that you probably did not notice. This is an ongoing experiment so I am always making very small changes. I would really like to take the time to make the FAST O2 show up on the datalog using your XDF. Not sure if that will happen any time soon. If it stops raining, I want to try some things at the dragstrip too. Too many projects, not enough time and $$$.

 

Good news. I edited a bin and burned a chip using the expanded XDF. Datalogged just fine. Still cant figure out what was up yesterday.

 

the links in this thread are dead... would like this expanded $6E adx file.

 

Sorry, I dont have it any more. Had to replace my hard drive since then.

 

dang well i thank you anyways.

if anyone else has this saved hit me up!

 

Here it is from this thread. Change the extension from .txt to .xdf

RBob.

 

The one I use is located here:

http://gearhead-efi.com/gearhead-efi...E_expanded.xdf

It's 237 KB. Judging by the size it has more parameters defined than any other $6E I could find.

GD

 

U guys are da bomb. Stop by for a beer and a bratwurst later.

Kent

 

Can't go by the size of the file. For V5 of TunerPro Mark wrapped the XDF file parameters in XML. That in itself makes the file larger.

RBob.

 

That would indeed do it. I wasn't aware that the older ones weren't using XML. With a variety of files available I just picked the biggest hoping it would be the most complete. The one that comes with TunerPro is severely lacking.

GD

 

Just when I think I'm getting better at tuning and decided to purchase the Ostrich 2.0, I came across this thread and downloaded the expanded 6e.xdf. I see new tables that I don't have a clue what they do. My learning curve just got a bit steeper. I did see a table for low pulse width injector correction that is not in the standard 6e.xdf. How did you guys learn this stuff? Is it just trail and error. Is there a sticky for the expanded 6e.xdf?

 

You can simply go through the hac.... The disassembled and commented assembly language code for the $6E. It's over on gearhead-efi under the 1227165 sticky. This tells you the address and basic composition of every table, scalar, and flag. You can then add any or all of them that you desire to the definition within TunerPro. I added the scalar for crank max injector PW recently for example. It's not in any of the defs. Once you know the memory offset and the calculation used to make it a real world value it only takes a few clicks to add it in.

That said, most of everything you would ever need is already there. Some items of curiosity aren't but don't need most of them.

GD

 

Thanks GeneralDisorder. I agree, most of what I would ever need is probably already in there. Anything more would be over my head anyway. I plan on getting a wideband O2 soon and will use the ARAP_wideband bin that another member has provided in another thread. I believe the ARAP_wideband bin uses pin D8 for the O2 sensor analog output. Is the expanded_6e.xdf compatible with the ARAP_wideband bin?

 

I found an expanded $6E and $32B on my old laptop.

 

Good thread