Knock sensor and related parts

[doc_rock]

Moving my troubles out of introductions and here.
I've started working towards learning how this works, to try and get this car running right. It's never been 100%, but seems to have degraded over the last 3 years - granted a lot has changed on the car, and nothing to has changed on the efi.

It's a 730 ecm with a custom burned eeprom - that I don't know if it was burned to the car or an eBay purchase. I have however loaded the stock 730 bins from this site (90 y, 90 f 5.0, 90 f 5.7, s_aujp v6.0 and a manual transmission 5.7 conversion Dave w sent). The 5.7 conversion Dave sent ran the best of the burned chips, but was not as good as the custom burn i already had.
Running through various data logs, and trying to understand what all that means I've come up with more questions.
Hardware:
355 10:1 engine, forged and balanced crank, flat tops, gm lt4 hot cam with distributor gear, gm lt4 aluminum heads, roller valve train.
Car has brand new (<1000 miles) urethane mounts, timing set, balancer, exhaust gaskets and studs, plugs, wires, icm, coil, wires to coil and ecm, pickup coil, cap and rotor. Newish (<5000 miles) head gasket, map, o2, temperature sensors, transmission (t56 conversion) clutch, cross member and torque arm.
Base timing is set at 10 degrees which is as low as I can set it before the car dies with the est unplugged

Issues:
Continuous random misfire
Random Misfire under acceleration
Lack of power
Excessively rich exhaust (faint black smoke most times but nearly always burns your eyes)
Idling will slowly decrease until it can't run
Timing won't stay steady at steady rpm - I've always attributed this to timing light, but worth mentioning here
Random bucking and power drops at cruise on interstate
Usually after 8 minutes if driving it throws an ses light, but clears itself after another 10-12 minutes or a couple of shifts

Knock sensor: somebody here mentioned that exhaust banging around could set the knock sensor off.
How does the ecu react to an unplugged knock sensor?
Does it put it in limp mode, or just disable the input and throw a ses?
Does the knock sensor have any effect on fuel curve?

[84Elky]

Maybe a stupid question, but you are Speed Density, and not trying to run MAF with S_AUJP, right?

Need to post your .BIN and either a TunerPro .xdl log file or an exported .csv log file showing the issues you describe.

[doc_rock]

Maybe a stupid question, but you are Speed Density, and not trying to run MAF with S_AUJP, right?

Need to post your .BIN and either a TunerPro .xdl log file or an exported .csv log file showing the issues you describe.

It is definitely speed density. No maf, MAP sensor in the top of the intake over the number 2 cylinder. 1990 iroc, 1227730 ecm, originally ANFJ.
Let me organize the csv files and I'll get them posted.

[doc_rock]

S_AUJP is that bin and the log associated with it
The other is two log files from two roughly 30 minute drives.

[doc_rock]

These are logs from the chip that's in the car.

[84Elky]

Doc-Roc ---

DO NOT RUN YOUR ENGINE WITH THE BIN YOU POSTED!!!!

You have essentially taken the released v6 S_AUJP BIN and have only changed that shown below. Your bin on the left and released on the right. None of the spark, VE, etc. values in the Bin can be used as released. Most are merely examples to complete a table of data. A BIN contains a calibration that contains items which must be in accordance with the engine. They are edited with the XDF. And with your engine, and the v6 calibration, I'm surprised it even runs. MUST learn how to tune and enter appropriate values. More later, but DO NOT use the v6 BIN without making calibration changes!!!!!!
Capture.GIF

Elky

[doc_rock]

No problem. I'm back on my original chip/bin.

[84Elky]

More ---
My recommendations. In order to use S_AUJP, or any other bin, you have to have a good "starting point" calibration (the data the code uses which is edited with the XDF file). Without that, no need to start engine or log.
1. If you don't have a Moates HDR6 adapter, go here and buy one ($10). It will allow you to extract a .BIN file from a chip using TunerPro:
http://www.moates.net/hdr6-memcal-re...der-p-246.html

2. Install the custom eeprom and extract the BIN on there to a file. This is your "starting point"

3. Once you have completed step 2., you now have a calibration that needs to be transferred to S_AUJP. Go to the link below and download S_AUJP v6-4.zip and carefully read Appendix A of the "Must Read Me . . ." file:
https://www.thirdgen.org/forums/diy-...ml#post6345030

4. Follow the instructions to use a Hex Editor to copy the calibration from the custom bin to S_AUJP. Save the now-calibrated s_AUJP bin. You now have a starting point bin with a calibration that somewhat works.

5. Log this bin. But DO NOT hot rod it. Just do some gentle accelerations in each gear and some constant RPM/TPS periods of 15-20 seconds. At this point, no need to exceed 2500 RPM at any time.

6. Post up that log. It can be used to determine what needs to be changed to go to the next step.

HTH, Elky

[stew86MCSS396]

Maybe a stupid question, but you are Speed Density, and not trying to run MAF with S_AUJP, right?

Need to post your .BIN and either a TunerPro .xdl log file or an exported .csv log file showing the issues you describe.

@84Elky Can you take a look at Docs .csv log file of the one he says runs the best post #5..."Im not a smart man.." but it seems like it may be a open loop bin. Last time I did anything with '7730 was back in '05...

[84Elky]

@84Elky Can you take a look at Docs .csv log file of the one he says runs the best post #5..."Im not a smart man.." but it seems like it may be a open loop bin. Last time I did anything with '7730 was back in '05...

The logs you reference do indicate OL, but the underlying issue is we don't know the source of the data being provided, if OL was intended (unlikely without using S_AUJP), etc. That's why I ignored them.

This appears to be a classic case of a "tune" being provided and it being used without any idea of what it contains. I've seen situations where inconsequential changes were made to a factory calibration and it was called a custom tune (fan on/off temps, TCC lock MPH, etc.). Happens all the time. Once the extracted bin file is available, progress can be made. Bottom line, it's impossible to radically modify a computer controlled engine and expect it to properly run without personally changing the parameters necessary for the desired performance.