pcmhacking.net

You won't use the oseplugin if using another kind of emulator just use tunerpro serial I/o plugin to log and whatever suits your emulator in the other emulation tab.

delcowizzid wrote:You won't use the oseplugin if using another kind of emulator just use tunerpro serial I/o plugin to log and whatever suits your emulator in the other emulation tab.

I have not been able to get the tunerpro plugin to data log on the 12P code. Or rather ... when I use the OSE plug in ... it just works and rather flawlessly i might add. The tunerpro plugin with the old '165 was always plagued with problems where it worked and would not work.

I'll give it another go. Need to be patient.

Mark.

You probably need to click on the rs232 echo box in the adx the oseplugin would of been handling the echo setting

Hi Mark! Just found my way to the end of your thread hoping to see a happy ending.

First, I have the APU1 as well and have been using it to tune a few vehicles over the last couple years. Let me tell you that this thing is a pain in the ass! It's been glitchy from the start and Ive finally had enough and went back to the Ostrich and ALDU1. My latest project is a sunbird turbo GT with the C20GET, aka LT3, with a GT2871R turbo and intercooled. The APU would randomly shut off the engine in emulation mode and was not predicable at all. Thought I blew up the engine once when it shut off the engine at 18psi boost. So your latest issue might be the glitchy APU.

That being said Ive been tuning the engine with code 59......and I absolutely hate it. Fuel control is erractic and inconsistent, or maybe im just being too picky. Tuning open loop and the air temp correction doesn't operate, well at least not the defined IAT table. So I am switching to 12P.

Im looking for ways to control the factory N.O. wastegate solenoid and was wondering if you were able to get your flex table to control the boost somewhat accurately? My main complaint with 59 is no matter what I change it will allow the boost to spike before reducing WG DC. The WG DC table is only 2D and even if I rigged it to run open loop it would still not be as accurate as a MBC.

Cool project!

If your interested I have a tuned (well almost) 12P on a 2L Mitsubishi engine running 440cc injectors and knock sensor. If your interested I can post it up for you to have a play/look at.

Absolutely! Thank you sir

It still runs lean under high boost.

Charlescrown wrote:If your interested I have a tuned (well almost) 12P on a 2L Mitsubishi engine running 440cc injectors and knock sensor. If your interested I can post it up for you to have a play/look at.

Hey Charles,

What knock board are you using? I wasn't aware of any for a 4 cylinder, only the V6 & HSV V8 to suit a 165 ECU.

Thanks.

Chuff

I got a couple of memcals from the US out of Sunbirds but I also have one with a V6 knock board and in my opinion they work equally as well. Most will disagree but that's the fact.

Thought Id post an update. The Duke has run well with the 12p code. Apart from making a new exhaust manifold that can withstand the turbo heat, not much for maintenance. Also a turvo needed a tighter plug gap. Yesterday was track day and the duke ran its best of 14.8 at 93mph. This is with 3.08 gears in a 2800lb short box s10 truck. Boost was in the 15 to 16 psi range.

12p has brought so much life to this little truck. I get a kick outta telling people its a stock computer original to the truck.

The one thing Id like to add is a knock sensor. The circuit is easy and the ecm factory had one. Id need to add in to one of the extar inputs and see if i can get a count. We had essentially 100 octane yesterday but id guess there was a knock or two.

Future plans are to build a stroker version of the 2.5 using a 3.0l crank. And maybe find a super duty head.

Mark.