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

Ok thank you. I checked for spark last night and it is firing (I took a nice shock in the process). I have no real way of timing the engine with a timing light or anything but I have a solid model of my flywheel/trigger wheel and that his how I am coming up with my trigger offset number.

You had me until you said circuit jumper. Am I supposed to have something on the board jumped? On the module I am using pin 23 & 25 for the stock vr sensor. That is all I have done to the module regarding the vr sensor. The engine has ran before so I assume it is correct but that was on the old code.

Still no start. While I am cranking my ignition advance is showing -10 degrees. I have moved my trigger offset around by ten degrees forwards and backwards and I still get the same thing. Some times I get -5 degrees. I have reread everything and triple checked all of my trigger settings and I am still getting nothing.

I cant upload my data log because it says the file is to big. Darn

If you are connecting to the vr circuit you are ok unless the sensor is incompatible with this circuit and there needs to be some compensation like diodes, resistors, capacitors, people have done all sorts of things. So you might check into that looking for vr/ noise problems on previous posts, especially read anything Bruce has posted on this.

You can reduce the size of the datalog by editing it in Excel and throwing out what is a repeat or just sitting there waiting for the starter to cool. There is no gain in logging 20 starting sequences - 2 or 3 are more than sufficient.

Looking at your previous data log, you have some noise, but it isn't overwhelming. Many people have this much noise but are able to achieve combustion and have the engine get past cranking rpm and the noise goes away. Are you sure it is getting enough fuel to have combustion. If it is sparking it should ignite the fuel unless the timing is way off. If you see -10 deg in TS, it doesn't mean anything - you will always see what you put into it,the ecu has no way of measuring when spark occurs, so you can only be certain timing is correct by measuring it.

Ok well thanks a ton for all the help and tips. I guess my setup isnt too far off. Ill go ahead and look at my setup and do some more fine tuning.

Thanks again for the help. You all are always so helpful.

Well it turns out my spark plug was bad. I made the mistake of only checking spark at the wire and not at the plug. Swapped out plugs and she fired right up!! And turns on with every push of the button! BUT NOW I think the ecu may have lost its flash. Because now when I turn it on it just cycles the fuel pump over and over again :/

Somehow your data got corrupted. I would save the existing setup to an msq file, but I wouldn't trust it. Then I would reload the code, then use an msq from when I knew everything was uncorrupted and make any changes by hand. If that starts up then save it as your new baseline msq so you can always get back to this known good msq. As you progress you can save more baseline msqs.

We have found that one way to cause things to be corrupted is to try to change things like the number of teeth or no. of cylinders while the engine is running. First off, this can be dangerous to your engine. The code performs some initialization of variables when it first comes up so it won't have to recalculate them every time - this saves a lot of cpu load. If you change them while the engine is running OR try to run the engine after changing them, bad things can happen to either your engine or flash. We are working on trying to better understand the mechanism for this, but the procedure for changing variables where a reboot is required(marked in red on the TS menus) is to stop the engine (or stimulator), make the changes, then reboot. The variables involved here are primarily major engine parameters, not tuning variables which are meant to be changed while the engine is running. So for example, you can change the ve table while the engine is running, but you can't change the number of cylinders or wheel teeth. These should be set once at the very beginning, the ecu rebooted, and left alone after that.

Ya thats what I figured :/ I guess I will head to the shop in a few and reflash it.

The ECU stopped working while I was in the middle of changing my AFR table and EGO control. The engine turned off and my computer went to a blue screen then restarted. Thats when the file got corrupted and started cycling the pump.

I have noticed that while tuning the ECU it messes up my computer. While I have the software open, atleast once throughout a tuning session my computer goes blue screen and then restarts it self. This only ever happens while im using it with the microsquirt.

Reflashed the ECU and it fired right up