MS extra siamese sequential tune (msq) to start with
Turbo Mini Forums

http://www.jbperf.com/

Apologies Jean, I was going from memory rather than digging up the old thread...

Before the 90 degree BTDC is what I have done anyway (as per the plot earlier) but I guess if the standard fuel pump lobe is 30 degrees BTDC it must be a case of setting the sensor gap small so the rising edge is detected very early ???

Schrödinger's cat - so which one am I ???

Saul Bellow - "A great deal of intelligence can be invested in ignorance when the need for illusion is deep."
Stephen Hawking - "The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge."

Best wishes to everybody on the forum.

Perhaps a silly question but does anybody know how I can get an Y axis to the graphs of megalogviewer? And is it possible to display only two graphs?

The Y axis should auto scale to fit the graph,

You should be able to have 4 graphs, each with 3 traces, on the left of the screen you should have some coloured tabs labled quick view, click on those and pick a trace. if they are not there in the "view" menu check that "Hiding field select" is not ticked.

Also dont upgrade to the lastest version, it will lock it so it cant be used.

As I am new to megasquirt and all other software I have the latest version of megalogview installed.

I was hoping I could put a scale beside the Y axis as that would make the graphs easier to read when I post them on the forum.

Things are slowly getting a little bit better at idle now but I have an anoing problem.
I am having an erratic signal that causes a loss of sync I cannot put my finger behind it at the moment the VR signal looks very clean and the rising edge of VROUT is at the zero crossing of the down going slope of the VR signal as it should be. I have both pots turned fully ccw.
The cam signal also looks very clean and is about 15 crank degrees wide. It occurs 90 degrees before the missing tooth so that should also be oke.
I have all noise filters switched off at this moment.
Does anybody have a clue?

With the Megalogveiwer, the best thing to do is to set the Y scale minimum and maximum to something reasonable. Particularly, the AFRs so you can see exactly when they are equal.

You may want to increase the setting of R56. Also turn on the noise filtering.

Saul Bellow - "A great deal of intelligence can be invested in ignorance when the need for illusion is deep."
Stephen Hawking - "The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge."

Check the obvious first, ie, VR sensor gap to toothed wheel - not just at one point but several to make sure the wheel is concentric (on my plot you can see the wheel runs off-centre a little bit...).

Your cam signal seems fine, mine is 35 degrees wide and still before the missing tooth and works fine.

I would experiment a bit with the VR pots. I have R56 at 0-2 turns on the engine (but a lot more on the JinStim) and R52 at about 8-10 turns on both engine and JimStim.

Can you post a plot of VROUT ???

Schrödinger's cat - so which one am I ???

Where can I set the Y scale in megalog viewer?? Can’t find it in my version I am running version 2.958.

I will post a plot of the VR signal in about 1 1/2 hour I do not have a camera at the moment.
To which values should I set noise filtering?

Will

I'm using version 2.958.

Under "Calculated Fields", select "Fixed fields Max and Min". You can then select "Add....." then you type in the field name say "AFR" and set the scale limts.

Saul Bellow - "A great deal of intelligence can be invested in ignorance when the need for illusion is deep."
Stephen Hawking - "The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge."

Can't answer about MegaLog (mine uses TechEdge logging) but I would start with the noise filtering at the default settings (which I assume is none as I've never changed anything in those settings) and check the other basics from there.

It's my personall view that you shouldn't try to "filter" out a problem unless you know one really exists, if that makes sense.....

Schrödinger's cat - so which one am I ???

Here are two shots of my VR signal together with the VRout signal.
GND level is scope centre line. The max PP VR level is 8.7Volt (when disregarding the missing tooth level) where the minimum PP level is 7.3 Volt so it is a little bit of centre but not much.
The VR out signal is 3.9V.
Signal seems oke to me but I must say this is the first one I ever saw so that does not mean that much.
I will try to get the sync/ready signal to trigger the scope to see how the signal looks at the moment I loose sync (don’t know if this is possible yet).

Regards Will

Now with the two pictures

I do not know what is going wrong but I can not at the attachments??

Edited by gemertw on 2nd Jan, 2010.

Try hosting them on photobucket or similar and just doing the [img ] [/img ] links (without the spaces).

Schrödinger's cat - so which one am I ???

I can see two pictures.

The waveforms look fine to me.

Saul Bellow - "A great deal of intelligence can be invested in ignorance when the need for illusion is deep."
Stephen Hawking - "The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge."

As mentioned the wave forms are ok but which edge are you triggering from? If the square wave is at the CPU then you need to trigger on the rising edge. Using the falling edge will not work correctly.

Jean

http://www.jbperf.com/

[IMG]
http://s758.photobucket.com/albums/xx223/g...l1.jpg&newest=1[/IMG]


OH WELL !! THAT DIDNT WORK THEN .
AHAHAHAAAAA ...HA , THIS DID ..

Edited by robert on 2nd Jan, 2010.

Medusa + injection = too much torque for the dyno ..https://youtu.be/qg5o0_tJxYM

From what's on view it looks as if it should be correct at the missing tooth as well but it would be worth altering your timebase to get the missing tooth in view on the scope and comparing it to the picture at the bottom of this page to make sure the longer square pulse is where it should be.

http://www.megamanual.com/ms2/wheel.htm

Are you set as rising or falling edge in TS - you implied in an earlier post you have it the opposite to mine because of reversed VR polarity - apart from altering the setting in TS or swapping the VR sensor wires, I believe that using VROUTINV jumpered to the CPU (instead of VROUT) should also reverse it. As I said earlier, I went through a load of Ford wiring diagrams to get the polarity right as I didn't want to alter the default setting (going high) in TS or use a non-standard jumper configuration.

Schrödinger's cat - so which one am I ???

Will, are you sure that it is an ignition issue causing the loss of synch.

When I last upgraded the code on the 998, I had problems with getting it to idle. It was caused by AE coming in due to a dirty TPS signal. The affect of the AE was so violent, the engine would kick and synch would be lost. It was caused because all AE settings from the previous set up needed increasing by a factor of 10.

Just check that you are getting a steady pulse width at idle.

Saul Bellow - "A great deal of intelligence can be invested in ignorance when the need for illusion is deep."
Stephen Hawking - "The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge."

And as I mentioned earlier, don't forget to check the obvious, ie, sensor to wheel gap. If the gap is wrong the output quality is quite speed dependant.

ie, do you lose synch as the engine speed rises ???

If it is potentially another signal causing the problem as per Paul's TPS example, just swap the dials around in TS to look at all the other inputs to see if they are stable.

Schrödinger's cat - so which one am I ???

Hi I will try to answer most questions,
I am triggering on the rising edge I already had changed the polarity of my VR to get all signals right. The second picture you can view thru the photobucket link gives the VR signal at the missing tooth point.
The loss of sync does not seem to get worse at higher RPM it occurs equally at idle as at around 4000RPM.
I am not sure if it’s an ignition problem what I see in megalog viewer is that the RPM drops to zero together with dutycycle the longest time that RPM stays zero that I have seen so far is 0.2 sec. Most of the time the problem occurs RPM drops to zero for just one sample. I will try to attach a plot.
Paul, do you mean after start enrichment with AE? I already tried reducing after start enrichment to zero to reduce the side effect of the problem because after the drop in RPM after start enrichment kicks in and disturbs the afr this did reduce the effect of the loss of sync but the problem stayed.
I will check my TPS signal as well as all other incoming signals.

Regards Will,
P.s. I have to my take girlfriend out for a walk so I am not able to test further before this evening.

Attachments:

11.27kb

That looks as though the VR sensor is losing the signal at odd times.

I would turn on the noise filtering if you haven't allready.

I also have to take a walk in the frost this afternoon.

EDIT: Odd that the MAP signal also drops.

Edited by Paul S on 3rd Jan, 2010.

Saul Bellow - "A great deal of intelligence can be invested in ignorance when the need for illusion is deep."
Stephen Hawking - "The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge."

Schrödinger's cat - so which one am I ???

I'm thinking that there could an issue with the board power supply or earthing.

Is everything earthed at the same point?

EDIT: Have you calibrated the TPS? only it is not showing on the above plot although it is selected twice.

Edited by Paul S on 3rd Jan, 2010.

Saul Bellow - "A great deal of intelligence can be invested in ignorance when the need for illusion is deep."
Stephen Hawking - "The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge."