Golferlukes megasquirt... take two
#24
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.
So I tried reloading the msq, heres the errors I get
Any ideas?
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.
So I tried reloading the msq, heres the errors I get
Any ideas?
#25
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.
"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.
#27
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)
#28
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
"conflict with tacho output"
EDIT:
Checked tach output and my settings are
tacho output enabled: on
output on: IGN (js10)
Speed: normal
#35
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
BTW: http://www.diyautotune.com/tech_arti...dio_how_to.htm
#40
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 **** 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.
Update: Ok so I got it to be like it's supposed to and started her up, turned over first time! Ran like **** 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.
Last edited by Golferluke; 01-26-2011 at 05:12 PM.