Welcome to the 2GNT Forum! Interested In Advertising with 2GNT?
Home | Site Background| Info&Specs| Mods & Tech Info | CAPS | Part Reviews | Donate | 2GNT Stickers |
Search Printer-friendly copy Email this topic to a friend 5 Users in Chat
Top 2GNT Technical Performance/Engine Engine Management Systems & Controllers topic #5861
View in linear mode

Subject: "RE: No crank signal from megasquirt" Previous topic | Next topic
Tired2Sep-16-14 12:07 PM
Member since Sep 23rd 2012
124 posts,
Click to send email to this author Click to send private message to this author Click to view this author's profile Click to add this author to your buddy list
#5875, "RE: No crank signal from megasquirt"
In response to In response to 5


          

I think he is going for sequential injection, which needs a cam sensor to know which injector(s) to fire.

Will your report back power increase or drive-ability, etc?

I've read going sequential can get you a bit more power but only if you really tune it in properly.

I'm on MS2, so I don't have the IO headroom for Sequential, but it would be good to know if it is worth the trouble.

  

Report This Post to Admin Printer-friendly copy | Reply | Reply with quote

No crank signal from megasquirt [View all] , Dstach, Aug-25-14 08:10 PM
  RE: No crank signal from megasquirt, Dstach, Aug-25-14 08:37 PM, #1
RE: No crank signal from megasquirt, Gruff511, Sep-03-14 12:17 AM, #2
      RE: No crank signal from megasquirt, Dstach, Sep-03-14 06:12 AM, #3
           RE: No crank signal from megasquirt, Tired2, Sep-12-14 12:36 PM, #4
                RE: No crank signal from megasquirt, eclipse982nrRST, Sep-16-14 10:00 AM, #5
                     RE: No crank signal from megasquirt, Tired2, Sep-16-14 12:07 PM #6
                     RE: No crank signal from megasquirt, Dstach, Sep-16-14 04:49 PM, #7

Top 2GNT Technical Performance/Engine Engine Management Systems & Controllers topic #5861 Previous topic | Next topic
Powered by DCForum+ Version 1.2
Copyright 1997-2003 DCScripts.com

I generated this page in 0.051265954971313 seconds, executing 14 queries.