Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

uhmmm I don't see the boost retard feature..I see only where I can scale a region by percentage...maybe I'm blind :( I'll try to look harder...

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

I have one more question Can I only use 450cc injectors when using the boost code??? anything about Fuel recurve?

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Well I'd really like to see the addition of editing the stock correction maps...but I figure that is work that has to first be done on the ROM, correct?

I think this may help us get rid of that nasty jerk I hear about.

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Semenos:
Those features are coming out in 1.20.. it should be released in two weeks.

xenocron:
You can already edit stock maps. :-/ Stock maps are contained in the PGMFI_ROM-NA.bin ROM. Those are the stock maps of a PM6.

If you need something for your B18A1, just import the stock PR4 maps.

If this doesn't fix your situation, I don't believe I understand what you mean by editing the stock correction maps?

As far as the jerk in OBD0 boost, it is being actively pursued.

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

ohhh nice looking forward to it.
I'm getting my Batronix EPROM this week.
Will do sum NA tuning first iwth my 450's ;D

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

By stock correction maps, I mean the maps that the ECU goes too for changes not handled by the main fuel and timing tables. Correction maps are used by the ECU for changes in Outside Temp, Elevation, the Decel Enlenement Curve and a few others I cant remember. Look at a standalone like Autronic, Haltech and Accel. Along with their main fuel tables, there are other tables to go in and play for very specific occurances that the ECU recognizes.

I personnally believe that if we can find and tap into these maps (which Honda spent $$$ building & tuning), that will take care of problems such as the jerk. It wil also mean not putting in a different chip for Open Downpipe, Drastic Temp Changes, etc.

Is what Im saying clearer? I have a rough time with wordage sometimes...I think I tend to confuse myself occasionally. ::)

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

I don't believe Honda's work quite that same way. Take the PM6 for example. There is only one set of maps. Yes, the PR4 has 3 ignition and 2 fuel, but so far, we have only found that the PR4 uses the first map of each section.

As far as "correction", the operation is done in closed loop. This section of operation is still foggy, and we're working on cracking that. Closed loop uses a few things including O2, *and* the static fuel and timing tables.

But, as far as I have looked into the actual source code for the current ROMs being used, there are only one set of tables. The static tables. :-/

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Hmmm...you quite possibly are right...hell you know way more about all of this than me. I am just speculating of course.

Think of it like this though...you think Honda developed different maps for cars they were going to sell in Denver as opposed to Florida? Not bloody likely, besides closed loop only can correct up to 5% tolerances or something like that Ive heard...go beyond and that and I think it would throw a code or go completely into open loop, which is what it does at WOT, right? And closed loop is only for emissions, not for drivability reasons so there needs to be some other maps in there somewhere. (Again, all speculation)

I'd really like to be able to help you, Blundar and anyone else working on this "crack" of the honda ECU as you put it...however, i have no real coding or cracking talents. So if there is any way I could help, someone please let me know.

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Hrm, I hadn't heard about the 5% thing before.

How I understood closed loop in a Honda to work is that it gathers the O2 signal voltage, and with the static tables as a base, it calculates the pulse duration.

This would allow for correction in Denver and Flordia because the car would be using a different portion of the static maps based on the atmosphereic pressure. This value would greatly effect manifold pressure, thus "changing" the portion of the map for the elevation the vehicle is running..

This is just how I understood it to be.. this could be very wrong.

Can anyon confirm one way or another?

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

What would happen at WOT in Florida vs. Denver when the ECU goes into Open Loop? The florida guy would be running much leaner most of the time. After years of that either the Denver guy would have issues of running rich (bad plugs, engine troubles, clogged CAT, bad O2) or the Florida guy would have durability issues from running leaner...is my guess.

I say 5% because I heard that somewhere and also on a Honda a narrow band O2 (which is what is reporting to the ECU correct?) is very limited in its accurate operating range. I would guess that the Honda ECU automatically goes into Open Loop when it knows that the ECU is out of its accuracy range. Although, why does a Honda automatically dump tons of fuel into the engine when an O2 sensor gets clogged and goes bad...hrm?

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

No, that is why the maps have such a wide range.

They would both have the proper fuel settings for the stock engine. Why? Because of atmospheric pressure differences. These differences would put the person in a different part of the map even at wide open throttle. The person in denver would have less pressure in the manifold. Less pressure means less air per cubic inch. Less air would require less fuel, and the stock map is tuned for compensate so.

If you use the latest version of TurboEDIT and hook up the MAX233A and watch the map trace in the datalogger, you can see exactly where the ECU is pulling fuel values from, even in open loop. You'll notice it doesn't use the whole map. Based on your region, I could be using different cells than you would because of the pressure. Thus, my fuel requires are different, the a fully tuned map will compensate for that.

When tuning, you don't *normally* tune the whole map. You just tune where the car operates from. This is the reason I wrote hte map trace. More accurate tuning.

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

you guys have me lost all i want to do is download a chipso that i can drive everywhere because i live in jersey with a lot of changing weather & elevation (ex.nj shore=sea level pa hi elevation cool weather) is this system adaptable to the changes or should i do an afc hack in my situation i prefer turbo edit for launch control reasons in other words is te user friendly i dont know what ill be getting into i tried to learn the tech stuff but i cant understand it help

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Heh, you can tune a map to funcitno in your conditions. It'll be OK..

You can use TurboEDIT.. :)

I actually used an NA PGMFI ROM with TurboEDIT that I tuned for use with my V-AFC. It's all good..

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Parker...by what scale would i have to change that NA rom to run 450cc injectors.

Is it simply 240/450 (.5333) scaled down in all columns?

GD used to have a button for recurving for injector sizes...but with your area scaling it would be the same.

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

No, there is no feature for injector recurve in TurboEDIT as of version 1.18. Monday, version 1.20 will be released which will have Boost Retard per PSI for the ignition map, and Fuel Injector recurve.

...so stay tuned. ;D

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Nice man...I just made my adaptorboard I'm buring bin's like crazy and testing them hehehe ;D

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

ok ithink i am eadto get this show on the road TURBO EF9 i will send you my pr4 when i find a spare one i need adresses & exact prices for the service(socket my ecu + burn 2 chips)

Re:www.TurboEDIT.org by TurboEF9 (Current version: 1.18)
 

Just e-mail me (jparker@driftkids.com) and I'll give you all the information you need..

Re:NEW VERSION RELEASED! www.TurboEDIT.org (1.20)
 

Current Version: 1.20

Available for download at http://www.TurboEDIT.org

Release Notes:

Datalogger development will continue once I get this pesky engine in my car. Small bit of trivia, I haven't had a running Honda during the entire time I have been developing TurboEDIT! Pesky D series rod bearings didn't feel like playing with 10psi at 8000rpms. :)

Added the ability to see what hex addresses certian data is being loaded from, and the code base that the ROM has been derrived. This information coinsides with the ROM addresses display.

Ignition retard for boost is done! HOO-RAH! Now you can scale your ignition map by a set number of degrees as boost increases. Note: This option is only available when a boost ROM is lbeing edited.

Fuel recurve is being lame. I can't seem to create a happy equation. Everything I do ends up flattening the fuel curve which makes it rich on both low and high end. Mid-range scales great. This only effects people who want to use 450cc injectors on thier NA setup. Have patience, the feature is coming.

Re:NEW VERSION RELEASED! www.TurboEDIT.org (1.20)
 

Nice man...you're pretty fast.
Gonna check it out

Re:NEW VERSION RELEASED! www.TurboEDIT.org (1.25)
 

Latest version: 1.25

..minor error handling with the Boost Retard (scaled too far would cause an error).

I also got frustrated when I opened so many windows so I wrote a taskbar feature. Now you can use this to find the windows you want, quicky and easily. You can also enable/disable it if you want the original look. :)

.
 

I'm going to stop posting information about the latest version details here..

Latest Release: 1.26

I've setup a mailing list where questions can be asked, and post to the Support website on http://www.TurboEDIT.org .
Which will also have the latest information in TE/OBD0 development.

Anyway, sign up there, and direct your e-mail to support@turboedit.org and it will go to everyone on the mailing list so we can share ideas, and tunes, and bug fixes, and you can get the latest information without me having to post on every forum. :-D

Hehe..

Re:www.TurboEDIT.org - v1.27 ..now with PR3/PW0 Support!
 

..update.. 1.27

- BEgan PR3 and PW0 support.. (Can now edit high/low cam tables.. will continue refinining support)
- Advanced Open (Under File Menu)
- More Addresses Viewable (From ROM Properties)
- Rewritten ROM Verification Routine (so TE doens't get confused about which ROM it's opening)
- minor bug fixes (Boost REtard for secondary maps, Advanced Mode Window not clearing taskbar icon when closed, yada, yada, yada..)

Re:www.TurboEDIT.org - v1.27 ..now with PR3/PW0 Support!
 

blang blang.

Re:www.TurboEDIT.org - v1.28 ..now with PR3/PW0 Support!
 

..1.28..

- Advanced Mode support increased for PR3/PW0 math.
- BHG wanted minimize to taskbar.. Windows style, so I did that. :P
- Did a "Save As" routine so you don't have to overwrite your original ROM.
- probably some other little thigns.. blah..


BLING BLING!!

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

..1.29..

- PM7 support
- Fixed pesky bug in rev limit math due to the addition of the PR3 ECU.

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

i've got 1.29 TE software and if i open one of the standard pgmfi boost bins(boost or beta-boost) and try to change any value for rev limit hot/cold, launch, or idle and i get a runtime error '13' type mismatch and then the software closes when i hit OK

side note: any way to set this up on an 89 crx si ecu? i don't think there is, but i can't keep up with all the changes

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

Oops! This seems to be another glitch due to the addition of the PR3 ROM.

I'll fix this tonight when I get home, and post a new version. Sorry for the inconvience.

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

All fixed. Sorry for that.. I was verifying the wrong address cell in my array. So when a ROM Without VTec was loaded, think it had VTec, and try to calculate the RPM, thus, failing.

So! IT's all fixed. Just need to change a cell number. :) Hhehehehe.. sorry about that..

Anyway, redownload 1.29.

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

it's working fine now for me. thanks. now i just need an ecu and chip burner to try it on, oh and boost... lol

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

anyone tried the beta boost dual maps yet? just curious how it is working. the maps are a little hard to read, since its showing vac to 9.5 boost on all the maps. maybe thats because its beta?

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

No, that is because I don't know what the scale is.

..no one has really worked witht he bin.

Re:www.TurboEDIT.org - v1.29 - ..now with JDM PM7 (ZC ECU) Support!
 

so it didn't support the PM7 at first??
What is the difference between the PM6 and PM7 ECU??

Re:TurboEdit 1.29
 

Jason or Dave/blundar(if you are keeping tabs on this thread),

What are the ways someone can help "better" the rom? I know very little about programming although I understand the concepts(somewhat) I have no extensive working knowledge of the syntax of any of them.

Besides being a Guinee Pig and testing buggy code...how else can I help development?

Dave I know you have a G2 teg and so do I...PR4 code is 1st on my list to help with...

Re:TurboEdit 1.29
 

hey guys can you give me some help, I have a 93 civic. I have no idea what ODB version it is, can I use turbo edit for it? thanks

Re:TurboEdit 1.29
 

It's OBD1..

..no, you can't use the current verison 1.29, but a little birdie told me you will be bale to use 2.0. :-X

Re:TurboEdit 1.29
 

thanks bud, and thanks to your birdie. Dman I can not wait to chipp my ecu.

Re:TurboEdit 1.29
 

So i'm guessing you are still working on this? because there hasnt been any updates since the bullshit went down.

Re:TurboEdit 1.29
 

Ya.. I'm still working on it. I haven't had anyone reporting issues. :-D (That's a good thing on my side)

I'm working on a TOTAL rewrite of the code. It should be finished in the next two weeks. This will be version 2.0. Very modular (yet another good thing for me). This will also include OBD1 support. This new setup will also make it easier to add features, and reimplement the datalogger (and also continue dev of that).

Speaking of the datalogger, as soon as I figure out this electrical problem with my car, it will be the primary focus of development for TE.

I have not had a car the entire time I've been writing this software.. I'm very excited to *FINALLY* be running a TE ROM myself. :P

Re:TurboEdit 1.29
 

SPiffy, just keep us updated. Good work btw i'm currently using TE