Megasquirt Forum Area is for discussing Megasquirt EMS

Megasquirt T1 not firing...

Thread Tools
 
Search this Thread
 
Old 10-02-07, 09:48 AM
  #1  
Happy Squirter

Thread Starter
 
dbgeek's Avatar
 
Join Date: Feb 2004
Location: Lyman, SC
Posts: 263
Likes: 0
Received 0 Likes on 0 Posts
T1 not firing...

I've been running the MS for about a year now, and I've run into a new issue - only T2 is firing. I can attest that trailing operated fine before, but I can't say when it stopped working.

Firmware 029y4

I've traced the wiring for trailing select, swapped plug wires, new plugs, swapped trailing coil/ignitor, and watched the LEDs (18 is less bright than 17 and 19).

I do not have access to a scope, which would have been my next route. Does anyone have any suggestions?

Thanks
Pete
Attached Files
File Type: zip
pete13b.zip (5.7 KB, 34 views)

Last edited by dbgeek; 10-02-07 at 09:51 AM. Reason: attached msq
Old 10-02-07, 01:31 PM
  #2  
Full Member
 
rx3_pp's Avatar
 
Join Date: Jul 2007
Location: Hamilton, NZ
Posts: 116
Likes: 0
Received 0 Likes on 0 Posts
aint it mant to be on 024s9 for wheel decoder routine under basic settings wheel decoder settings

try stim for wheel on your stimulator and see if all the spark output leds are firing if so check ignitors and coil

please get muay to confirm before trying mate
Old 10-02-07, 01:32 PM
  #3  
Full Member
 
rx3_pp's Avatar
 
Join Date: Jul 2007
Location: Hamilton, NZ
Posts: 116
Likes: 0
Received 0 Likes on 0 Posts
also if using stim for wheel diconect from car and coils completeley
Old 10-02-07, 01:45 PM
  #4  
Happy Squirter

Thread Starter
 
dbgeek's Avatar
 
Join Date: Feb 2004
Location: Lyman, SC
Posts: 263
Likes: 0
Received 0 Likes on 0 Posts
Thanks - I don't recall changing the wheel style, but apparently I did it on 2007/08/21 at 1643 All prior msq's had 024s9 ... but megatunix shows a good read on the wheel, so I doubt that is the issue.

I guess its time to yank it out and play with the stim a bit. Or not:

Originally Posted by muythaibxr
you won't get an rpm signal from the stim anymore after connecting error*'s board. That's just how it is.

Last edited by dbgeek; 10-02-07 at 01:58 PM.
Old 10-02-07, 03:03 PM
  #5  
Full Member
 
rx3_pp's Avatar
 
Join Date: Jul 2007
Location: Hamilton, NZ
Posts: 116
Likes: 0
Received 0 Likes on 0 Posts
yea i was just taking a stab in the dark start with the basics first then get into the heavy electronics
Old 10-02-07, 04:47 PM
  #6  
Rotary Enthusiast

 
renns's Avatar
 
Join Date: Oct 2001
Location: Ontario, Canada
Posts: 1,022
Likes: 0
Received 4 Likes on 4 Posts
If you've swapped coilpacks and see the same problem, then the issue is likely harness or the MS itself. The symptom you describe would occur if there is no trailing select signal arriving at the coilpack. An open in the circuit somewhere from the MS to the coilpack is one likely possibility. The other would be a problem with the drive circuit on the MS box.
Old 10-06-07, 06:33 AM
  #7  
Happy Squirter

Thread Starter
 
dbgeek's Avatar
 
Join Date: Feb 2004
Location: Lyman, SC
Posts: 263
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by renns
If you've swapped coilpacks and see the same problem, then the issue is likely harness or the MS itself. The symptom you describe would occur if there is no trailing select signal arriving at the coilpack. An open in the circuit somewhere from the MS to the coilpack is one likely possibility. The other would be a problem with the drive circuit on the MS box.
I've checked continuity from the LED in the Squirt through the harness to the connector at the coil.

How do I test the drive circuit? Would it make sense to cut the signal from error*s board to the opto-isolator so I can test on the stim?

On the other hand, how bad is it not to have trailing?

Thanks
Pete
Old 01-19-08, 02:05 PM
  #8  
Happy Squirter

Thread Starter
 
dbgeek's Avatar
 
Join Date: Feb 2004
Location: Lyman, SC
Posts: 263
Likes: 0
Received 0 Likes on 0 Posts
I've taken a few days recently to troubleshoot this issue. I verified continuity from MS to the coil, verified the operation of the transistor, and started looking at firmware again.

Also, if I ground the LED (-), then T1 only fires. This means that IGS-T doesn't seem to be properly functioning.

I back-dated to 029q2 - trailing operates properly.
029t - Trailing operates properly.

I'm now in the process of downloading and installing each version of "stable" firmware to find out where this "broke".

Has anyone else had this issue? I'm testing with a timing light to verify spark of ALL 4 plugs.

Pete
Old 01-27-08, 09:34 AM
  #9  
Happy Squirter

Thread Starter
 
dbgeek's Avatar
 
Join Date: Feb 2004
Location: Lyman, SC
Posts: 263
Likes: 0
Received 0 Likes on 0 Posts
Greetings,
I spent an hour last week flashing and using firmware with hand-loaded MSQs.
To create the 029w and 029y4 MSQs, I ran copyini for the appropriate version, imported the Spark, VE, and Trailing Split tables, and hand-entered all other values. Then I sat in the car and downloaded firmware and msqs, using a timing light to verify spark on each of the 4 spark plugs (Leading all worked, so I'll leave that out). Here are the results:

029t
Copyini, Downloadfirmware (with boot jumper- “upgrading from base”)
Load Pete t.msq
Audit.log shows no errors. T1 and T2 fire reliably.

029w
Copyini, Downloadfirmware (with boot jumper- “upgrading from base”)
Load Pete 029w fresh (import tables, hand-entered all other values)
Audit.log showed an error about freq_div = “INVALID”. T2 only fires.
I wasn’t particularly worried, as the goal is to go to 029y4. I also changed and saved over the file, so it may be moot.

029y4
Copyini, Downloadfirmware (with boot jumper- “upgrading from base”)
Load Pete 029y4 fresh (import tables, hand-entered all other values)
Audit.log shows no errors. T2 only fires.

029t
Copyini, Downloadfirmware (with boot jumper- “upgrading from base”)
Load Pete t.msq
Audit.log shows no errors. T1 and T2 fire reliably.

029y4
Copyini, Downloadfirmware (without boot jumper)
Load Pete 029y4 fresh (import tables, hand-entered all other values)
Audit.log shows no errors. T2 only fires.

029t
Copyini, Downloadfirmware (with boot jumper- “upgrading from base”)
Load Pete t.msq
Audit.log shows no errors. T1 and T2 fire reliably.

I am at a loss for what to check next. Any ideas?

Can someone running 029y4 verify their trailing spark with a timing light and post the MSQ?

Thanks,
Pete
(cross posted in msextra)
Attached Files
File Type: zip
Pete 029w fresh.zip (5.1 KB, 34 views)
File Type: zip
Pete t.zip (5.6 KB, 35 views)
File Type: zip
Pete 029y4 fresh.zip (5.1 KB, 28 views)
Old 01-27-08, 02:13 PM
  #10  
MegaSquirt Mod

 
muythaibxr's Avatar
 
Join Date: Sep 2004
Location: Maryland
Posts: 4,721
Likes: 0
Received 1 Like on 1 Post
I'm pretty sure something is wrong settings wise then, Over the past few weeks I was driving around on 029w and trailing worked fine, firing both on T1 and T2.

I'll have to take a look on the bench when I get a chance.

Ken
Old 01-29-08, 05:20 PM
  #11  
Happy Squirter

Thread Starter
 
dbgeek's Avatar
 
Join Date: Feb 2004
Location: Lyman, SC
Posts: 263
Likes: 0
Received 0 Likes on 0 Posts
I found the deviant setting. Thanks for the reminder to check everything This LED18 output setting was set to Fan Control - I can't say I've ever changed this one, but somewhere along the way, it or I did.

Trailing now works properly.

and there was much rejoicing...
Attached Thumbnails T1 not firing...-setting.jpg  
Old 01-30-08, 09:37 AM
  #12  
MegaSquirt Mod

 
muythaibxr's Avatar
 
Join Date: Sep 2004
Location: Maryland
Posts: 4,721
Likes: 0
Received 1 Like on 1 Post
Nice, good that you've worked it out then.

Ken
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Hayden111
New Member RX-7 Technical
10
12-05-12 07:17 PM
muibubbles
3rd Generation Specific (1993-2002)
76
11-09-10 05:16 AM
NAN777
3rd Generation Specific (1993-2002)
7
05-01-10 08:58 AM
NAN777
Power FC Forum
4
08-12-08 02:35 AM
TMadlem84
3rd Generation Specific (1993-2002)
37
05-11-08 01:38 PM



Quick Reply: Megasquirt T1 not firing...



All times are GMT -5. The time now is 08:56 PM.