essb00

Something like this (this setup has not been fine tuned).

It would be a guessing game without any lambda/AFR reading... but it would be mostly lean as it stalls after touching the throttle. Get a lambda controller connected and configured in the tune file.

@Hadzhonda: It does not matter what the signal wave form looks like. What matters there is how the ECU would interpret the signal --- and the ECU actually reads the frequency of the rise/fall of the signal via a DI.

Ohh... I thought it is just the screen refresh rate that's affected by it... I thought PCLink would still log 40Hz (default/max) no matter what the display refresh rate is...

@atlex - The 'Hz' is the data refresh rate of the PCLink screen you're looking at only, it does not affect the logging Hz.

Post a copy of your tune file & PC log when starting from cold to normal operating temp.

AEM 30-0334 only outputs OBD-II PIDs, not like the 30-0300 which is connecting via AEMNet (actually, they seem to be the same device, just different firmware). Your best bet to make that work is to connect it using the 0-5V analog output and connect it to an unused analog input of your Link ECU. ....at 72% ethanol, the approximate stoich is about 10.6:1, so seeing 11:1 on your AEM gauge proves it is leaning out. You've got to fix the items pointed out by AdamW.

Other than the overrun fuel cut, there was no other limiter activated on that log. However, there is no lambda recorded on the log (you have selected Link CAN on Lambda 1, but it seems your AEM UEGO is not sending lambda readings to CAN), so it cannot be told if it was lean or rich before/after the actual 'misfire'.

Tacho also has to be driven by PWM, basic fuel pump relay can be driven by CAN aux --- but since that is something critical that would cause a no-go whenever there's something up with the CAN switchboard or the CAN bus itself, I would personally want that driven by ECU aux.

Post a log from cold start to fully warmed up. Trig2 has got some big noise spikes, though on the scope not reaching the arming voltage.

For most CAN expansions, the aux outputs are basic low current on/off triggers that cannot drive PWM... Unless the CAN expansion is a PDM (power distribution module) --- which would be overkill for what you just intended. You can assign the boost control solenoid on one of the AtomX's aux output for PWM, and then whatever you have there before that's just triggered on/off can be re-assigned to a CAN aux of something like ECUMaster CAN Switch Board V3.

Pls post a copy of your tune file, plus PC log with all the issues you have described above.

Too many issues there... Notable ones are: - Trigger errors - AFR Target Table --- must be rpm vs MAP or MGP. - Ignition table --- should be rpm vs TPS (since your engine is on ITBs). - Idle Speed Control --- incomplete setup - Overrun Fuel Cut --- not setup - Accel Enrichment --- not setup - Knock control --- incomplete setup Sorry but with the way that tuner has so far done things there, I don't think he will do any better. You need to find another tuner...

I can see on that tiny pic that both Trig 1 & 2 are wired with incorrect polarity. Just interchange the wires for each reluctor.

^Again, nothing captured but noise. If you say you clicked capture while cranking, then next to check would be your wirings. Can you make a rough sketch how you have the crank/cam sensors wired?