Microsquirt LS1 Sync Loss Issues

[Moody]

Start a new topic then.

James

Haha James I will, my first post here was to the OP. I have a couple things I'm gona try or test before I start a new thread....


Sent from my SCH-I545 using Tapatalk

[PeakAlpha]

I don't think wiring is your problem because I have exactly the same problem with my microsquirt install but I'm using a vr sensor. Must be setting issue? I didn't have this problem when I was fuel only setup....

Sent from my SCH-I545 using Tapatalk

I am beginning to think that you are correct. I have been slavishly reading the manual and posts in the support forum related to this issue and noticed that my ignition input capture setting is currently set to "falling edge", and according to the manual it should be set to "rising edge". I came across this reading several other threads related to this issue (http://www.msextra.com/forums/viewtopic ... 01&t=47361), and a post in yet another related thread by the author of the first thread here (http://www.msextra.com/forums/viewtopic ... 2&start=20). Put simply, this is apparently important and will piss off the computer if it is set wrong.

I have been making changes to the wiring etc.. here and there with no success. I have an autocross this Saturday, and I am planning on running the computer with a rising edge input capture. Hopefully this solves the issue. I will report back about any change in the problem. Thanks to everybody for their helpful suggestions so far. Keep them coming if you think you have a good idea! Moody, if you figure out your problem let me know. Hope this helps.

[PeakAlpha]

Alright guys. I have been messing with the car a bit today, and tried out my theory with setting the input capture for the crank signal to "rising edge". Now I am officially confused. I have attached a picture of my Ignition settings, as well as a recent data log with the ignition settings set up exactly how they are in the picture. It seems that I am indeed getting a crank signal. And from what I can tell, the tooth pattern that the computer is interpreting looks exactly how it should as depicted at the top of Page 132 of the Microsquirt Hardware manual. Trouble is, the computer is indicating that it is not sync'd, even though the signal appears in the composite log exactly as it should! What the hell? Car will not start and the tachometer is not indicating that it is picking up any signal at all. Do I have a misplaced setting somewhere? Please let me know what I am doing wrong here.

[jsmcortina]

Do your settings and wiring match the manual exactly?

I see that you have JS10 as Spark A, you almost certainly don't want that.

James

[Moody]

Your firmware doesn't look right, it's not the same as the firmware I have loaded into my microsquirts....

Sent from my SCH-I545 using Tapatalk

[jsmcortina]

Your firmware doesn't look right, it's not the same as the firmware I have loaded into my microsquirts....

Ooh - GOOD CATCH. Yes, that looks to be the MS2 version of the firmware which won't work correctly on a Microsquirt.

James

[PeakAlpha]

So, it looks like the latest version of the firmware is "MS2/Extra 3.4.2 release Firmware". Just to confirm, I should be running that version with the Microsquirt, correct?

[jsmcortina]

Yes, but you must choose the Microsquirt version when loading the firmware.

James

[PeakAlpha]

Alright, so I installed the new firmware. I chose the "Cased Microsquirt" option since I have a Microsquirt V3 in a black plastic case that I purchased from EFI Source (listed as an "LS1 24X modified Microsquirt V3" on my receipt from 2014). So, my first question is, that is the correct selection, is it not? Second, I chose to do the jumperless reflash (I assumed this was A-OK since I have a nice cased version and this wasn't an initial firmware install?). Everything went okay, had some weird error messages pop up initially when I turned everything back on, but played with the settings a bit and it stopped freaking out. Now when I am cranking the engine, I am getting no tach signal at all with "rising edge" or "falling edge" selected. At first, I had a lost sync error (#2, missing tooth). After I changed something and cycled the ECU, it came up with an error that I had a conflicting tach output setting, and I went in and changed it from IGN1 to TACHO like it is currently wired for. Now, I am not getting sync loss errors when I crank.

My ignition settings should be in my attached .msq file. I have the IGN1 wire attached to my Spark A coils (four sets of 2). Do my coils have to be plugged in to read rpm properly? I imagine that is why the ignition settings ask for my Spark A output pin?? I just realized that I left them unplugged while I was reflashing the uS and have not plugged them back in when I was messing with all of this stuff, so that may be the root cause of not reading rpm. I believe most of my settings transferred over from the old version, but I am nervous to plug coils and injectors back in in case the computer freaks out and floods my intake manifold and blows fuses, etc... Anyway, is there any way I can ask somebody to have a quick glance at my settings and make sure I'm not going to fry anything by plugging my coils/injectors back in? Sorry for the (probably) stupid questions. I am trying to learn this stuff as quickly as possible, but I am a natural Mechie and not a Techie unfortunately for the people who are cringing reading this thread.

One final thing, I am still getting some strange behavior with the rising edge configuration as opposed to the falling edge. Reading the falling edge (see log below), I am seeing a good signal. Same with the rising edge, but the goofy little red spikes show up at every edge of the square-wave signal. Not sure what that is about. Anybody got any ideas?

[jsmcortina]

If you are seeing sync-loss reason #2, you don't have LS1 selected as the ignition mode. Please re-check your settings.

James

[PeakAlpha]

d*** you work quick James! Haha, yep after I power cycled my ECU, that error disappeared.

[jsmcortina]

See the image on this page:
http://www.msextra.com/doc/pdf/html/Meg ... .4-47.html
James

[PeakAlpha]

See the image on this page:
http://www.msextra.com/doc/pdf/html/Meg ... .4-47.html
James

Alright, so it looks like I am in fact losing sync then according to my composite logs above in my latest long post, or at least I am not getting any sync in the first place? I am not getting a cam pos signal since I am running wasted spark with no cam sensor, so that makes perfect sense. The image above simply shows a bunch of turquoise spikes. Why am I recording the square wave signal consistent with the LS1 24 tooth wheel in my composite log?

[jsmcortina]

The LS1 signal needs to see both "edges" of the input signal.

James

[jsmcortina]

The "Falling Edge" shows that the ECU is getting sync and all looks good.
The "Rising Edge" shows that the ECU never syncs.


James

[hybrid]

Output to the coils has no bearing on whether you see a crank signal (as you have no doubt found out now).
You are doing the right thing to have the injectors and coils powered off until you know your ignition capture is good to go.

[PeakAlpha]

Output to the coils has no bearing on whether you see a crank signal (as you have no doubt found out now).
You are doing the right thing to have the injectors and coils powered off until you know your ignition capture is good to go.

Thank you for confirming that for me hybrid, I appreciate it.

So, quick update, I have been messing with the car again tonight and I noticed a few things. My coolant and intake air temp sensors are now both reading 0 F, which does not make any sense. These were working just fine before the firmware update. What the heck is going on here? I feel like this has got to be the wrong version of the firmware or something. And on top of that, my composite logs are now showing no sync with falling edge, as well as rising edge. Oh, and my fuel pump is not priming anymore when I apply power (this actually was working yesterday post-firmware update. Not sure how I am suddenly going backwards here. Doesn't seem to make any sense. Anybody got any suggestions?

[Moody]

Can you post new msl?

Sent from my SCH-I545 using Tapatalk

[PeakAlpha]

Current .msq file attached. I also attached a couple of composite logs and a tooth log that I took from tonight. Not sure how to make sense of the tooth log yet or if it will be helpful. But there it is.

[PeakAlpha]

And here is the tooth log that I took as well.