pgmfi.org

OK - I have been doing my research, troubleshooting and here's my missive:

Matt (AKA The Acid Beaver...and "the man who is wise in the ways of Science" - ) has been helping through some of the subtleties of this and we have gotten to this point; now it is time for broadening the reach for help. I am a EE/ME/CS and I can provide detailed feedback to good questions; as well, I build my own motors, transmissions and cars.

PR4 OBD0 ECU - brand new Ostrich, brand new 14point7 wide band, brand new narrow band O2, TE 3.2.2 and ECU Control loaded in my Winblows 7 laptop. I have downloaded all of the latest versions of code, drivers and BIN (my BIN is based off of NG63). The stock O2 is feeding the ECU.

I cannot for the life of me get ECU Control to work inside of TE - the stand alone version of ECU Control communicates with the ECU, although the gauge does not show the A/F mixture...but on the data logging page it shows the mixture in the bar graph? And it will not let me save the data log file...$hi!...

The motor: D16A1 (in an 87 CRX)
fresh build @ 800 miles
reworked head, shimmed valve springs, decked head 0.060", good port job, un-shrouded valves, decent camshafts
0.5mm overbore P29 pistons
RSR 4-1 SS header
ZC IM with a bored B18 TB, 390cc injectors running E85 as fuel (the 240cc injectors could not handle WOT at high RPM)
ARP hardware through out


So, stand alone ECU Control works, so COM settings are right and the USB/TTL converter works, the BIN has the code in it to communicate and I get data back. Could this by a Winblows 7 issue? Any reason that I cannot save the data log file that is obvious (could be operator error - I am not above being told so...).

Last issue, fuel cut is at 7,000 RPM regardless of the fact the the ECU Extra Tables are set at 8,000 RPM...weirdness caused by the PR4 or is it because ECU Control will not load through TE? (I did get auto detect for fuel multipliers turned on as it limited the fuel to 10.85...thanks again 'Beave...).

Anything else that I can answer, anything that is suggested that I try, a 4x4 upside the head - let me know, I will guinea pig to help this along.

Thanks for any input!

Kirk

PS - last BIN attached...

EDIT - one last thing that I can think of, idle vacuum reads around 20 or so...so I know cam timing and valve lash/seal is good and I don't have any apparent leaks in the IM...

The fuel cut problem has nothing to do with ECU control not working properly. I have experienced similar problems with NG63 revlimits. Try NG62 for a temporary fix till you figure out what is going wrong with revlimiter values in NG63 (try not altering the cold rev limits).

As for the ECU control, It’s a common problem and I had it many times trough different PC setups but still I don’t exactly remember what I have done to make it work.
First of all make sure you have downloaded the latest versions ofTurboEDIT and ecu control
Then, before installing the ecucontroll plugin, make sure you have all resource files needed.
ecucontrol resource files
Turbo EDIT Resource Files 1 of 2
Turbo EDIT Resource Files 2 of 2
[resource files for Turbo EDIT sould be included in the full installer package… but download them again just in case]
And then comes the tricky part… I don’t remember where exactly you put all these files. I did a search on my system (win7 64bit) and I see that I have put them in the TurboEDIT install folder and in both system32 and sysWOW64. Probably I put them any ware in my effort to make this work… and it worked (after the 10th try)
On a more serious note, maybe those files need to be registered as fastcrxsi90 mentions in the post I have linked above… which I didn’t do, so maybe that’s the cause I also had a hard time to make ecucontrol pluging work.
Also if you already have in your system some of those files, consider not replacing them to avoid any possible problems with other programs that may use these specific, allready installed, file versions.

Standalone ECU controll sould work ok, but in my case it doesn't seem to work properly with latest NG codes or win7 or my hardware. (no idea realy)

I will give this a shot - I have a virgin copy of the NG63 that I can cut and paste my fuel/ignition maps into.



I followed the steps for the Ecu Control - download to a directory and then manually registering them...once I did that I started TE and Ecu Control came up and ran after I loaded my BIN...I have now configured the Tables to match my car and saved the BIN. Reloading it brought back all of the values I stored - SCORE ONE FOR THE HOME TEAM!



I am a "change one thing at a time" trouble shooter as I want to know what triggers a fix...or just another step in a series of fixes. I will follow each of the next steps (I have already downloaded the files just in case) once I try out the new BIN tomorrow.

Many thanks for the pointers to the other threads. I will post back what has changed after more troubleshooting tomorrow.

Kirk

download the attached to any folder and rename from TE List.txt to TE List.vbs (forum wont let me post an actual vbs file). run the script file on your machine (double click)...im assuming win7 has windows script host and will let you actually run it. this script should take a minute to run but will create file named TurboEDIT Resource Files.txt (in the same folder as the script) that has a list of all registered files and locations. post that file back up so i can look thru it...

from my experience, if the echartcontrol.ocx file cannot be found it will not load and will give no messages.

i've also attached a few screenshots of the .NET software im working on that should be a fix for the vista/win7 crowd.

as far as the limiter goes, try pasting your maps into ng60/61/62 and see if the problem goes away or not. also, without being able to look at any logs...try to lower your cold/hot revlimit crossover temperature.

The data logging works after just performing the registration as described KAYND - those four easy steps got it up and running.

So, I just went out and did some logging - it seems that my fuel/ignition map put into NG63 base map logs a maximum RPM of 7328 - my tach pointer may be off as it was 7,000, give or take and eyeball. I set the cold temp to 5,500 - it found it until the engine warmed up.

I am guessing that to use the "dyno" function that you have to push the "graph" radio button in that screen?

I calibrated my TPS (it read -11 at first with the throttle closed).

There is a discrepancy between my wideband and the stock o2 sensor - I am guessing that I can run the wideband output into the input on the ECU replacing the stock o2 sensor? Any precautions or things that I should do to make sure that I am not causing harm to either the wideband or the ECU?

The speed indicator was as close as the radar could clock me, so it must be reading the "extra files" correctly - as well, the gear selector indicator works.

All-in-all - an awesome first experience! I thank everyone for the effort and energy that they have put into these programs. Now it is time to learn to tune well...

I turned off the o2 sensor and started making tweaks to my BIN - the worst spot(s) were in the -10 range between 2,500 and 4,000. I got them reasonably trimmed up in the first run (damn, it would be nice to have someone drive the car while I made tuning adjustments...pulling over to the curb every three minutes is a PITA!).

OK, last thought and question - how does one make the Autotune work? The "enable" is greyed out and the "disable" is checked. I know...RTFW!

Again, thanks for the input and help.

Kirk

Here you go...Kirk

I don't usually quote pics . . .



But . . .

Woah . . .

and I usually don’t post off topic. But... yeah! This looks good

correct, the red button will turn green and it should record a run between the start/end settings. the only issue is that the hp/torque calculations are way off. I had it working "correctly" at one point (one of the earlier releases), but somewhere along the line screwed up the calculations. support will be added to the new software...


turn off the narrowband under rom properties>general options in TE. in ecucontrol under O2 settings, select the misc. linear input and adjust the linear AFR/voltage settings to whatever you wideband output is programmed to. unplug the narrowband and wire the wideband output to pin C16 (if I remember correctly).


this was never actually coded as I am not a fan of making changes without reviewing the data first. if it would really help you, I can add a timer to make the calculated fuel map changes at a timed interval. otherwise, just right click the new fuel value table to update your fuel values.



more to come soon...

It logged numbers, but I do not think they are meaningful. I would be happy to look at that code and see what my feeble mind can draw back up from the dark ages of coding...my real strengths at the time that I did a lot of coding was in Assembler - so, I may not be much help...perhaps you can shoot me an e-mail off line? gt5pilot@yahoo.com





So, I hooked up my wideband to the o2 input, disabled the o2 sensor in TE and I got a Code 4 error in about 30 seconds and the car ran like shit. I need to figure that one out as in open loop I have a lean hole at -11 around 3,000 and I want to log many samples in those areas - with the narrow band connected and the o2 setting on you don't see it...so I know the map is off in that area. Any idea why it would throw a code 4?

Kirk