MicroSquirt.com read only forum (Jan.15,2018)

I am running a 2007 Yamaha Phazer on a Microsquirt module

I am setting it up using Tunerstudio, i cannot get it to spark, I'm assuming this is because i am not sure what my ignition settings are supposed to be. I contacted Yamaha to see if they could help but they will not release any information to me. All i know at the ignition is controlled by a Digital TCI igniton system with coils on the spark plugs, rising edge ignition input capture, going high spark output, The engine is an oddfire. IF you need any other information to help me i can give u everything i have.

Thanks

What kind of COPs are they? The Module can't control 2-wire "dumb" COPs; you'll need to add high energy driver transistors like the BIP373.

i do have high energy drivers. The engine was running on a previous version of the firmware. but now after i had updated it and put all the settings back in and it wasn't working at all. After a few frustrating days i went back and reinstalled the old firmware i was running but now it wont spark with the exact tune i had before. I cant figure out what is wrong with it and why it doesn't fire on the exact firmware with the exact tune. I noticed it has no rpm reading anymore so im assuming that is why there is no spark because it doesn't think the engine is turning. I unplugged the coils when i did the firmware so i don't think it has to do with messing up the coils. Not sure where to go from here.

You are correct in that it won't fire anything unless you get rpm. So forget about fooling with coils until you get rpm. Something got messed up in either your wheel configuration or something changed in the engine VR wiring. Look carefully at all the variables and see if anything looks fishy. Think about what has changed since it last worked. WShen you downloaded the code did it say "verification succeeded". When you first went into TS after the download were there error messages.

I Have RPM reading now. But the engine still wont fire. I checked for spark and both coils are producing a spark. When i did a datalog I noticed that the "Engine" was at 1 while it was off then when i turned the engine over it increased to 3 and the RPM reading was working. Every second or so it would go to 0 and the rpm would not have a read out causing it to stop firing. Ive attached the data log as well as the tune. Maybe you can see where i went wrong.

The msq looks ok and not like it got corrupted. The problem from the datalog is that it is missing tooth detections, so it keeps losing sync. You cn tell this by looking at the trigger+/- column. At the end of every rpm sequence it counts down, meaning it missed a tooth detection. So if it worked before and you have checked the settings, then most likely something changed in the VR circuit, or is it a change in temperature, for example it last worked in summer and now its winter and it doesn't work.

The only thing that looks fish is that the dwell goes to -0.1 on most sequences where you get brief syncs. I have never seen that before. One thing I can think of is that there are negative battery spikes, but this would, from your dwell correction table, only drop it by 0.9 ms. The other possibilty is that the trigger angle configuration is wrong and there is insufficient time to dwell because it starts too late. But if it worked with the same configuration before, then it should work now. Note this has nothing whatever to do with the condition of your coils. The ecu doesn't even know if you have coils attached. That won't affect the dwell calculation. So we are back to the trigger wheel circuit.