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 1 User in Chat
Top 2GNT Technical Performance/Engine Engine Management Systems & Controllers topic #4112
View in linear mode

Subject: "RE: V3.0 No tach spikes" Previous topic | Next topic
VelocitaPaolaDec-01-08 12:52 PM
Member since Jun 13th 2005
626 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
#4175, "RE: V3.0 No tach spikes"
In response to In response to 12
Dec-02-08 12:36 AM by VelocitaPaola

          

Terry,

I found the page to which I believe you're referring:

http://www.msextra.com/manuals/MS_Extra_Ignition_Hardware_Manual.htm#msdout

You're over-thinking why they suggest using the internal ignitor with the v3.0... the simple reason is that the v3.0 board was equipped with one whereas the v2.2 board was not.

In other areas of the manual, specifically where multiple outputs are required to trigger a multi-channel ignition box, internal ignitors are forgone in favor of the same configuration the v2.2 board would use for a single channel.

The v3.0 board is really designed rather well, so I still suspect the problem may lay within the circuit configuration and not the physical layout. The only differences between the v2.2 and v3.0 boards that I see are the LED driver transistors. The v2.2 board uses 2N2222A transistors, which have a higher collector current rating than the v3.0 board's 2N3904 transistors. Either way, this difference shouldn't cause a problem.

If you've run a jumper directly from the cathode of D17 to the DB37 connector, I recommend adding a 1k ohm pullup resistor if you haven't already. If that doesn't work, try adding a 330 ohm resistor inline between the LED and DB37 connector to limit current and thwart any possible loading affects.

Let me know if either of these solutions work...



-----------------------------------------

-Paul

Service Manuals and Guides

  

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

V3.0 No tach spikes [View all] , AdministratorStar Turbo Talon, Oct-07-08 10:10 AM
  RE: V3.0 No tach spikes, Moderatorteklein, Oct-08-08 04:29 AM, #1
RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Oct-30-08 04:04 PM, #2
      RE: V3.0 No tach spikes, VelocitaPaola, Nov-18-08 07:03 AM, #3
           RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Nov-25-08 03:50 AM, #4
                RE: V3.0 No tach spikes, VelocitaPaola, Nov-25-08 01:06 PM, #5
                     RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Nov-25-08 02:43 PM, #6
                          RE: V3.0 No tach spikes, VelocitaPaola, Nov-25-08 04:15 PM, #7
                               RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Nov-25-08 06:47 PM, #8
                                    RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Nov-29-08 06:59 PM, #9
                                         RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Nov-30-08 08:07 PM, #10
                                              RE: V3.0 No tach spikes, VelocitaPaola, Nov-30-08 08:47 PM, #11
                                                   RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Dec-01-08 11:58 AM, #12
                                                        RE: V3.0 No tach spikes, VelocitaPaola, Dec-01-08 12:52 PM #13
                                                             RE: V3.0 No tach spikes, AdministratorStar Turbo Talon, Dec-02-08 08:24 AM, #14
                                                                  RE: V3.0 No tach spikes, VelocitaPaola, Dec-02-08 12:28 PM, #15

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

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