For any discussion not specifically related to your project
User avatar
By turbonetics
#44550
Hello
Does anyone know what resistor specs should be for runing bip373 in wasted spark? Defaults should be 160ohm,but it seems that car misfire somethines? Any thoughts ? :)
By LAV1000
#44558
Just feel if something gets hot, bip373 and coil.
If you trigger the BIP373 now whit 5Vdc you might try 12Vdc

please post your settings (msq) dwell might be to long.
User avatar
By PSIG
#44603
We don't know where the firing failure is, so diagnostics. I would start simple, by first determining if the "misfire" is occurring before or after Speeduino. Use a 'scope, digital analyzer, or even a timing light to confirm if any spark plug firing sparks are actually missing. If they are all good, then it is more likely HV circuit condition (damaged connection, coil, wire, spark plug, etc) or fuel-related.

If some sparks are missing, then work backwards to find if the coil driver signals are all reaching the ignition coils. If signals to coils are all there, then likely connections, coil driver or settings are bad.

If signals to the coil drivers are missing, and connections are good, then test for trigger inputs to Speeduino. If signals are all perfectly good, and of proper polarity, it is either a settings issue in Speeduino or a board issue.

This last one is very dependent on your sensor types, input conditioner (if any), and settings to use those properly. For example, if you have two VR sensors, then both Trigger Edges should be the same (Rising or Falling) depending on the conditioner used. Missing-tooth wheels should be reading the teeth falling edge signal, and settings made for that. This can be confusing, so please post your sensor types, conditioner used, and jumper settings. A tooth log could also be useful.

In this example I worked backwards from the spark plugs to the input sensors, however you can start at either end of the process (input first or output first), but don't skip any testing in-between. The concept is to test if (in->out) operation is good until it goes bad, or (out->in) it's bad until it's good. This is a way to locate and confirm (diagnose) the source of issues. Each test brings you closer to the real problem without guessing. Good luck!

David
hints & kinks

I have been working on things over a year or so or[…]

I thought that spare ULN pins were configurable fo[…]

Problems loosing sync

Note that some VR conditioner circuits and chips d[…]

connection on board?

me again. I'll probably be on here frequently f[…]

Still can't find what you're looking for?