Will not sync

[OrangeAlpine]

MS3X will not sync with stim or engine cranking. Tach works with both sources. Using 1.3 firmware. The engine is a Ford Duratec I4, using a 36-1 trigger wheel with single tooth cam wheel.

Data log (trigger) results in empty file, even though I can see the graph which disappears in a few seconds.

Bill

[OrangeAlpine]

Forgot to mention the engine uses a VR sensor and the MS is prebuilt, 3.57 board from DIY.

Bill

[billr]

Have you tried getting a composite or tooth-time log; or logging by changing ignition mode from "toothed wheel" to "log crank/cam"?

[OrangeAlpine]

Bill, I don't understand exactly what your getting at or what to do. I changed the Ignition Mode to "Log Crank & Cam". No other changes. Lost the tach on the stim.

I can be a bit thickheaded at times.

Bill

[billr]

Okay, you have tried "log crank and cam", have you tried the other logging, in the Diagnostics tab of Tuner Studio (TS)?

[jsmcortina]

Bill, I don't understand exactly what your getting at or what to do. I changed the Ignition Mode to "Log Crank & Cam". No other changes. Lost the tach on the stim.

What do you mean by "Lost the tach on the stim" ?

The "Log crank and cam" spark mode is designed to be used with the composite logger so that a recording of the crank and cam signals can be created. It will always give zero RPM by design.

EDIT: Also, don't bother with the Trigger logger, it is the least useful of the loggers. Use the Composite logger.

James

[OrangeAlpine]

Okay, a composite log as requested. Data taken while on the stim. By "lost the tach", I mean the tach went to zero.

I would like to take the opportunity to upgrade myself from "can be a bit thickheaded at times" to just "thickheaded".

Bill

[billr]

Just a guess... have you tried "falling edge" for ignition input capture? Tried reversing VR leads for both rising and falling edge capture?

[OrangeAlpine]

No, when it refused to sync in the car, I went to the stim, thinking that if it won't sync there, (and it won't) messing with the wiring/sensors is rather futile.

Is there a flaw in that logic? Remember, I am a newb and at this point, there is just way too much that I don't know!

Bill

[billr]

I don't have a Stim, so can't help you on how that signal is handled.

[grom_e30]

is there meant to be a cam signal there?

[OrangeAlpine]

No. The stim was setup for a 36-1 wheel. The engine is setup with crank and cam, stim was not.

Bill

[jsmcortina]

Your MSQ is configured to require a cam signal, so unless you give the Megasquirt a cam signal you won't get full-sync.

However, you don't actually need the cam signal i.e. you are configured for wasted-COP and have non-sequential fuel.

So, if you want to stay with wasted-COP and non-sequential fuel you could change "Dual wheel with missing tooth" into "Single wheel with missing tooth" and not worry about the cam signal.

James

[OrangeAlpine]

Unfortunately, it still will not sync. Turned off the VVT (which I want to use) and set ignition to single 36-1 wheel, kept the wasted COP and non-sequential injection.

Bill

[jsmcortina]

What does a tooth log look like?

See http://www.msextra.com/doc/general/toot ... mples.html for examples.

The image under the text "Tooth log of 36-1 wheel on V8 running " is what you should be seeing.

The image under the text "Tooth log of 60-2 showing incorrect VR sensor wiring" shows a miswired sensor (or capture polarity.)

James

[OrangeAlpine]

Do you want this from the stim?

Bill

[jsmcortina]

Start with the stim yes. The composite log looks fine, there is no reason not to get RPM-sync.

James

[OrangeAlpine]

Looks very much like the "Tooth log of 36-1 wheel on V8 running " Very even tooth pattern.

Bill

[OrangeAlpine]

Switched Ignition input cature to falling edge. Did not sync. Switched back to rising edge and made this tooth log while on the stim.

Bill

toothloggerfile.csv

[jsmcortina]

So that's all fine.

Remember that the input capture edge won't necessarily be the same on the stim as on the car.

James