Ran into another little problem, is there good place on nbs to run the map line?

Wideband is in!

Yup, much thanks to Ian! Now I just have to control the alternator and figure out how to run the map hose.

It finally was above freezing and not raining so I got some stuff done. Ran the (correct) map hose. Turns out where the harness goes through the firewall theres a rubber seal around the wires so I took a broadhead and poked a hole then just poked the hose through. After that I wired the wideband to the harness (with a quick disconnect so I can disconnect it if i'm running the stock ecu.) I also plugged in my gm iat sensor.

Anyways... should be ready to go now so I unplugged my cops, (don't know if its necessary but the whole reason I have cops is because I melted my coils messing with my original megasquirt) plugged in my megasquirt and hooked it up to my computer but somethings definitely wrong. The tach shows 65k and the tps doesn't register changes. I took a few screen shots to show whats going on.

Heres what happens when I try to do calibrate the tps.
http://farm6.static.flickr.com/5094/...0a72c8d7_b.jpg

So I tried reloading the msq, heres the errors I get
http://farm6.static.flickr.com/5132/...1c72b2b4_b.jpg
http://farm6.static.flickr.com/5055/...85efb5d8_b.jpg

Any ideas?

65k rpm indicates config error, try the following... tuner studio doesn't always show errors like it should...

"If you are seeing 65535 rpm, but no message, go to Communications and Mini Terminal. Then turn your Megasquirt off then back on again. You will see a message displayed telling you why the code found a problem with your settings."

http://msextra.com/forums/viewtopic.php?f=101&t=31532

Also, in your screen shots the 'Config error' indicator is lit up.

comes up with "d a 43 6f 6e 66 6c 69 63 74 20 77 69 74 68 20 54 61 63 68 6f 20 4f 75 74 70 75 74"

What does that mean?

hmm... is the baud rate right in the terminal? I've never actually tried doing it that way, I've always managed to save/exit restart tuner studio maybe plug the serial cable in while tuner studio is running and get it to actually spit out the error... if that doesn't get it you might do is just go through all the settings and see if anything is using the same pin, in my experience thats always what the problem is. (i.e. check generic outputs aren't trying to use the same pin as a spark output or something like that)

Ok well it seems to crash tunerstudio when I do that, after logging off and logging back in, restarting tunerstudio and then powercycling the ms on the main screen it comes up with
"conflict with tacho output"

EDIT:
Checked tach output and my settings are

tacho output enabled: on
output on: IGN (js10)
Speed: normal

js10 is normally the cam input signal on ms2 and ms3 when using the v3.0 board... what does the diypnp manual say about tach output?

are you sure you set tuner studio to microsquirt module? (under project preferences)

I think I just selected the other box and loaded the ini

I can't find anything about the tach output pin

err.. maybe i'm thinking of the wrong thing, where can I check that?

btw my buad is 115200

well I turned off the tach output and then turned it back on and now the tach is 0 and tps is working. Idk, crazy i'll hook up my coils and try to crank it i suppose?

You also have to make sure you load the microsquirt firmware and not the regular ms2 firmware.

argh, i power cycled it and its back to like it was. I'll check what firmware i loaded, I just loaded the 3.1 you posted a link to, didn't realize there were different ones. DOH!

EDIT: omg i'm an idot... loading correct firmware now...

I think that with the right firmware and project settings it oughta show up as 'tach out' and not js10, but I can't get tunerstudio to start for some reason to double check that.

BTW: http://www.diyautotune.com/tech_arti...dio_how_to.htm

Thanks I think that did it but now my battery's dead lol, gotta head to the gym, i'll charge it while i'm there and probably try it tomorrow when i'm not freezing my balls off lol.

Word, that happens :)

whatever firmware you flashed it with is NOT correct.

Ya I when loading the firmware I was following diy's instuctions and not really paying attention, ended up pressing "1" instead of "2" for microsquirt. Got it fixed now.

Ok now more issues, if I flash the firmware and load the msq it's fine but if I powercycle the ms it goes back to having the conflict with tacho output error. How do I check to see what my outputs are to find the conflict? If I go to output port settings output or js10 isn't even in there.

Update: Ok so I got it to be like it's supposed to and started her up, turned over first time! Ran like shit and wouldn't idle but it started lol. Afrs stayed at a constant 16.9 then I remembered I hadn't calibrated the o2 sensor. I think it was dumping fuel in causing it to run horrible.