Welcome to the SR20 Community Forum - The Dash.
Register
SR20 forum logo

Thread: COP for standard fwd ECU!

+ Reply To Thread
Posts: 21-24 of 24
2017-07-14 09:28:28
#21
Originally Posted by thejaredhuang
Sorry kinda noob, so do I still need the CAS from the P12 for this to work? I would be putting it on a USDM B13/B14 motor.


You can use whatever!

Distributor(90-93), Distributor(with coil inside[94-99]), CAS,

All will work. Just keep in mind that the code contains a section where you specify what trigger wheel you use. Per default it is using the settings for SR20DE Distributor(year 1990-1993). If you want help on how to modify it for some other type of teeth count, just message me. There should be info on this aswell on the github page.
2017-08-08 17:25:12
#22
Cool deal, you are the man! If anyone hasn't tried this on a stock ecu turbo car I'm up for testing it. (building one as we type)

Question for Dala the great: Is there anyway to get the ignition timing output from this since you are already picking up the CAS information? I only ask because the 2000+ ECU's will not talk through the OBDII for that info very well. If you can get them to talk they are too slow to update.
Last edited by Y2KG20 on 2017-08-08 at 17-34-58.
2017-08-12 17:48:42
#23
Originally Posted by Y2KG20
Cool deal, you are the man! If anyone hasn't tried this on a stock ecu turbo car I'm up for testing it. (building one as we type)

Question for Dala the great: Is there anyway to get the ignition timing output from this since you are already picking up the CAS information? I only ask because the 2000+ ECU's will not talk through the OBDII for that info very well. If you can get them to talk they are too slow to update.


Yeah you theoretically could get a timing readout from the Arduino by modifying the code to store when IGN happens and count the amount of CR pulses since last CP pulse.

However, getting this done might not be easy. In my code I stop counting CR pulses after startup to save resources on the Arduino. The triggerwheel Nissan used has so many holes in it (360!), so it takes so much CPU time to get interrupted so often. Then we also get the firing spark interference that could collide with this interrupt, so this approach might not be feasible.

Say this wasn't an issue, then there would be another issue of getting the timing displayed to the end user. Serial printouts via USB also take up resources. I have no idea how good/bad the program would work with simultaneously outputting spark and serial data. Having an LCD could maybe be less resource intensive, but I can't remember which is better atm.

If you still want to try a timing readout, I could assist with writing a base application. I would still recommend to first convert to COP, and later on add the timing readout when COP is working like it should.

EDIT: Another idea would be to have a separate arduino to only do timing readout. Then there would be no danger involved. Hmm..
2017-08-13 14:38:59
#24
You could connect the 360º signal to the input pin for the 16 bit Timer/Counter1 and program the counter to generate an interrupt after so many crank degrees.
+ Reply To Thread
  • [Type to search users.]
  • Quick Reply
    Thread Information
    There are currently ? users browsing this thread. (? members & ? guests)
    StubUserName

    Back to top