Engine Performance This section is for discussion on all engine building related questions.
Sponsored by:
Sponsored by: KPower

Significant Spark Latency - COP or FM36-2??

Thread Tools
 
Search this Thread
 
Old 04-19-2014, 10:00 AM
  #1  
Junior Member
Thread Starter
 
speedengineer's Avatar
 
Join Date: Dec 2012
Posts: 79
Total Cats: 5
Default Significant Spark Latency - COP or FM36-2??

So my new engine has both toyota coil on plugs and the FM36-2 trigger wheel running on a MS3. Fyi, it's a naturally aspirated engine.

Order of things I did:
1) Set base timing at idle with a timing light
2) Tuned engine on dyno, noted that it took a LOT of commanded spark at the high rpms to reach max brake torque timing, around 35 degrees advance on gasoline, about 6 more than normal.
3) Rechecked base timing with a timing light, but this time free revved it up to 6k rpm - Timing was retarding around 5 or 6 degrees up there!
4) In tunerstudio I set the spark latency to 140 microseconds, and this corrected the issues so timing holds constant throughout the rev range.

But, I was wondering if anybody else has noticed this issue, I'm trying to figure out if it's due to the coil packs (probable) or the FM trigger wheel (possible). Thoughts?
speedengineer is offline  
Old 04-19-2014, 10:06 AM
  #2  
Junior Member
Thread Starter
 
speedengineer's Avatar
 
Join Date: Dec 2012
Posts: 79
Total Cats: 5
Default

Also, does anybody know what determines coil pack latency? Would a lower supply voltage at the coil cause it to discharge with a longer delay? I wouldn't think so?? I didn't install the capacitor for the COP, but have set my dwell using 'dwell by table' in tunerstudio so I can bump the dwell up to 3ms at high RPM to help account for any voltage loss as it pertains to stored coil energy.
speedengineer is offline  
Old 04-19-2014, 10:54 AM
  #3  
Elite Member
iTrader: (10)
 
Reverant's Avatar
 
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,976
Total Cats: 355
Default

How did you check the timing while free revving? Did you lock the timing at 10* and just revved it and checked with the timing light?
Reverant is offline  
Old 04-19-2014, 11:04 AM
  #4  
Elite Member
 
JasonC SBB's Avatar
 
Join Date: Jul 2005
Posts: 6,420
Total Cats: 84
Default

Originally Posted by speedengineer
Also, does anybody know what determines coil pack latency? Would a lower supply voltage at the coil cause it to discharge with a longer delay?
It does but a tiny tiny amount, like less 0.1* at 6000 RPM.
JasonC SBB is offline  
Old 04-19-2014, 11:19 AM
  #5  
Junior Member
Thread Starter
 
speedengineer's Avatar
 
Join Date: Dec 2012
Posts: 79
Total Cats: 5
Default

Originally Posted by Reverant
How did you check the timing while free revving? Did you lock the timing at 10* and just revved it and checked with the timing light?
Timing was locked down to 10deg for all the timing tests
speedengineer is offline  
Old 04-19-2014, 11:19 AM
  #6  
Junior Member
Thread Starter
 
speedengineer's Avatar
 
Join Date: Dec 2012
Posts: 79
Total Cats: 5
Default

Originally Posted by JasonC SBB
It does but a tiny tiny amount, like less 0.1* at 6000 RPM.
Thanks, good to know!
speedengineer is offline  
Old 08-04-2014, 05:48 PM
  #7  
Newb
 
amptramp's Avatar
 
Join Date: Nov 2010
Location: Mississauga Ontario Canada
Posts: 29
Total Cats: -9
Default

Do you have your signal running the right polarity? The COP would burn out quickly if you try to invert the dwell signal, but your crank sensor signal may be the wrong polarity, firing from the trailing edge rather than the leading edge. There is a selector in the ECU to use positive or negative polarity. This could account for a consistent spark retard.
amptramp is offline  
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Erat
Miata parts for sale/trade
17
02-17-2016 04:22 PM
The Gleas
MEGAsquirt
3
10-01-2015 09:30 AM
FrankB
Miata parts for sale/trade
6
09-30-2015 11:48 AM
compuw22c
MEGAsquirt
0
09-14-2015 06:08 PM



Quick Reply: Significant Spark Latency - COP or FM36-2??



All times are GMT -4. The time now is 10:52 AM.