sporkcrx

Awesome! It works

Chris Harris

Looks good...I am almost ready to start helping you beta test...very very soon. Although I am having some trouble locating a low profile ZIF to solder in to my PR4. The xtronics and chips are on the way tho.

A question I dont know if you have planned in the works. Anything in the works for tuning with correction Maps? Specifically decel enlenment?

I cant wait to help and be a part of all of this soon!

- Chris

TurboEF9

If you mean using the datalog to correct fuel enrichment. Yes. It's planned, and already in the works and being tested.

We're (www.PGMFI.com) has to develop a ROM with 16-bit serial communication routine, or something. But that's outside the scope of this board. But the ROM is in the works.

Platty9

hey what would it take to start running this from scratch. i am very unfamiliar with these setups and i need the info. does it work on obd2 97 civic ex. soory i don't know ---- but thanx for any help

TurboEF9

TurboEDIT works soley with OBD0 (excluding PR3/PW0) ECUs.

Sorry.

Chris Harris

Im still not completely sure i "understand" the fuel multipliers.

I took Ben Strader's (tunes Mike Lasky's and many others cars) basic tuning seminar. He covered most of the major $$$$ players inclusing Motec, Autronic, Accel DFI Gen 7, FAST...blah blah blah.

The one thing that is very common among those are the additional "correction maps" that work behind the main fuel tables and ignition timing maps. The correction maps control such things as the decel curve (when letting off the gas and cruising, then the quick snap back on the throttle). I know this is a rom problem but that ideally would be corrected in the editor.

I dont know how familiar you are with the software of some of the major players out there...and I understand everything shall come in time.

Maybe I should just be talking to blundar to see if I can help in any way?

Thanks again...

thermal

I guess I should consider an EF/OBD0 for my next project car.

Mad props on this program!!!!!!!

TurboEF9

Not that you'll have to worry about if you're using TurboEDIT because TurboEDIT can AutoDetect Fuel Multipliers based on the values the users enters into the map!!

Fuel multipliers are easy to understand, however.

All they let you do is calculate a value through loss of resolution.


For example, the multiplier will be 0 - 4, and the data bit will be 0x01 - 0xFF (1 to 255). Range on multiplier 0 goes 1.08 to 2.3 when calculated in the fuel pulse width equation. The incrementation when using multiplier 0? 0x01 = 1.08, 0x02 = 1.08, 0x03 = 1.09 0x04 = 1.09.

Lose a bit of resolution, to go to multiplier 1, and you now get a range of 1.08 to 3.52 But the incrementation with multiplier 1 is now 0x01 = 1.08, 0x02 = 1.09, 0x03 = 1.10, 0x04 = 1.11 and so on until you get to multipler 4.

Incrementation of multiplier 4? 0x01 = 1.08, 0x02 = 1.15, 0x03 = 1.23, 0x04 = 1.31!

See how each multipler has it's own range, and with a bit of overlap, multipliers can be mixed and matched with no problem at all? YES!

I hope this clears up the mystery of multipliers. Bottom line? All they do is let you have a wider range of values.

sporkcrx

*hand flying over head making airplane noise*

Chris Harris

that was a great explanation...i understand much better now.

But im glad Turbo Edit has the Auto Fuel Multiplier feature.