EDIS SAW problem

[rickb794]

How is changing the timing calculation going to affect synchronization?

Changing the timing schedule is an output, how can altering an output affect an input?

Miss wired or bad software....

[jsmcortina]

My issue now is when I try and save a log, it looks normal, box pops up, and I click save, and its pointing at the same folder where my other logs are. But when I go to find them, they arent there. Could it have anything to do with not creating a new MSQ?

What are you using to look for them to decide they "aren't there" ?
The files you have posted here appear to be tooth logs, not regular datalogs.
Both have their own uses.

-Tooth/trigger/composite logs are great for understanding tach input problems and lost sync etc.
-Regular datalogs (Datalogging->Start) captures all engine parameters and is used to diagnose just about everything else.

James

[Beau M]

I'll try again. When I said they weren't there, I meant when I navigate to the folder where TS was saving the logs, the logs thought I had created were not present. I know this is all user error, but it would be more intuitive (I think) to move the checkbox to save a log in front of the start/stop buttons. The way it reads now, you start logging, stop logging, then save what you captured to a file by clicking on that box... which isn't how it works according to the tutorials.

I thought I was getting a complete datalog, I will play around with it some more today sometime. Thanks for hanging in there, I promise I'm not totally dumb.

How is changing the timing calculation going to affect synchronization?

Changing the timing schedule is an output, how can altering an output affect an input?

Miss wired or bad software....

I don't know, I'm just doing what others are suggesting, fumbling through it. I wish it was miss wired, but I have gone over the wiring tens of times. Where should I start for my issue? By bad software, do you mean the firmware or TS? I don't understand how the firmware can "go bad" so often and need a re-flash.

[SymTech Laboratories]

Why? The fixed advance setting was added for just that purpose so you can leave your table alone.

You're right, our mistake.

[SymTech Laboratories]

I'll try again. When I said they weren't there, I meant when I navigate to the folder where TS was saving the logs, the logs thought I had created were not present.

You can change the folder where the current log will be saved by simply selecting a different folder when you click "Start Logging". Saving them to your desktop can make finding them a little easier.

By bad software, do you mean the firmware or TS? I don't understand how the firmware can "go bad" so often and need a re-flash.

He probably meant a bad setting. Corrupt firmware is rarer than it seems. Flashing the ECU is just an easy way of starting over from scratch and making sure you're using the most up-to-date firmware.

[jsmcortina]

Taking a regular datalog is covered in the forum Help page here -> http://www.msextra.com/doc/general/forum_posting.html

James

[Beau M]

Yep, user error. Instead of using the datalogging tools under the diagnostic tab, I used the ones at the top of TS, and took a complete datalog. Hey, only took until page 2 right? So, here is an actual full log and my current MSQ. I had to give it some throttle to keep it running, but it idled on its own after a few seconds. This is with "use table" enabled.

Thanks again!

[SimpleSimon]

Have noticed in your MSQ that you are in Ignition Settings (going low 'normal') rather than (going high 'inverted') necessary for EDIS any reason?

[Beau M]

The good news is I got my fan working. As for the EDIS... I'm throwing in the towel. I am switching to LS1 coils controlled by the squirt.