K20 Mini

iTrader: (2)

So you didn't have to change anything? I am definitely lost. The afm is removed and I have the GM IAT wired into the factory IAT harness. The how to on DIY's website didn't say anything about jumping any wires, at least I don't think it did. I will go back and double check. I was a little lost on wiring the IAT because all the how tos I read said to use the third and fourth wires in the afm harness for the IAT, and NB's have a separate IAT sensor and only a three wire afm. Even on DIY's site it shows a five wire afm.

Would you be able to try the DIYPNP in a car?

edit: also,the other car I tried it in was all stock with the afm plugged in.

miatauser884

iTrader: (11)

Would someone look at my log. I've got a no start situation with a msq that worked in the past. I adjusted fo rthe 750cc injectors with req fuel.

Ben

iTrader: (33)

Composite log looks perfect.

miatauser884

iTrader: (11)

Thanks. After troubleshooting for most of the day, I realized it had to be timing related. I had spark and fuel. Then I realized that everything could still look good and be off if I had the cam timing wrong on the intake where I have an adjustable cam gear. Sure enough, Cam was timed wrong. Good thing it is not an interference motor.

Ben

iTrader: (33)

Glad you figured it out. Intake cam off on a 1.8 wouldn't show up on a composite log. Exhaust cam or crank off a tooth would show up, but it wouldn't be obvious--you'd need to know what you're looking for.

miatauser884

iTrader: (11)

I had to adjust my CAS all the way to the limit of adjustment to set my base timing at 10 degrees. Does this sound like I may be off a little when redoing the timing belt and cam position, or is it the nature of the beast?

I'll stop posting in this thread since I'm straying from the main topic

Ben

iTrader: (33)

I would probably be more comfortable putting the cas somewhere in the middle and adjusting the trigger angle of the ECU in tunerstudio.

K20 Mini

iTrader: (2)

Well, I have new problems, before I can get back to my old problems. As far as I can tell, my MS has 3.0.3s firmware on it now. And the startup maps on DIYautotune are for 3.0.3r or H I can't tell anymore, so if I try to load one it tells me the signatures do not match and gives me a page of errors if I load it anyway. So should I try to reflash the firmware to 303r because the file worked with it. Or does anyone have a 303s tune they will share with me to try?

miatauser884

iTrader: (11)

No, just direct tunerstudio to the new firmware file. You will have to create a new session which means reconfig for wideband, water, air temp., and tps.

K20 Mini

iTrader: (2)

Gotcha, All is good with that now, but I can't figure out why I am at 65,000 rpm, everything looks like it should (to me at least). Are there some ignition settings somewhere outside basic setup?

Ben

iTrader: (33)

You have a software configuration error. An output is assigned two different things at the same time, and the processor doesn't know what to do. Open Mini-Term (inside TunerStudio), power off and power on again. Mini-Term will give you a place to look.

K20 Mini

iTrader: (2)

Alright, It gave me tacho output error under ascII and a string of numbers on hex and decimal. What do the numbers mean? Do you need me to post them? There are two settings that say tacho output in TS, one is spark A output pin, which I have set to D14 and the other is under extended and says tach output on JS10.

Zaphod

Where have you got the first Tach output setting (Spark A...?) - the one under Extended should be correct though I am using "Tachout" on this...

(I think this is what you also should be doing) - because for the Microsquirt there shouldn't be a JS10 available for the Tach output.

Please have a look in your project properties - there should be

Microsquirt full - deactivated
Microsquirt Module - activated

What firmware are you running? Are you sure you loaded the correct ini in your project? (Because it looks to me like you loaded an MS2Extra-INI not an Microsquirt-INI)

Greets

K20 Mini

iTrader: (2)

Spark output A is set to d14. Microsquirt_full is deactivated and microsquirt_module is deactivated. I am using some files Brain gave me right now. I will try to post them.
INI isn't a supported file, I guess. I am pretty sure it is a MSIIextra INI. So should I change mircosquirt module to activated? Or which microsquirt file do I need?

Ben

iTrader: (33)

When loading firmware, you need to make sure that you load microsquirt code when prompted. When setting up your project in TunerStudio, make sure that microsquirt full is deactivated and microsquirt module is activated.

Zaphod

The firmware INI is the same for MS2Extra and Microsquirt now since 2 or 3 versions. So you just have to load the (latest is 3.0.3t) INI in your project.

And as Ben said, when you flash the firmware to the DIYPNP make sure you choose Microsquirt and set Microsquirt Module to Activated.

K20 Mini

iTrader: (2)

Holy cow, it runs!!! Barely!! Now I just have to find a table so it will run with the 550s. Also, it doesn't seem to see the wideband, no matter what settings I put in the reading doesn't change. Any thoughts? I have a lc-1 and I have tired the default and have manually entered the setting from the LC-1.

K20 Mini

iTrader: (2)

Alright, even leaned out a bit it still dies about every 10 seconds. Also, I seem to be producing 20 volts at about 2300 rpm.