Megamanual correct? (Next Pulse Tolerance)

This is the place to ask general MegaSquirt® questions if you are just getting started.
Please read the FAQ and MegaManual before posting. Also see the Forum Rules. Click this link for Purchasing information.
If you are looking for MS-extra or MS-3 information, please post here: www.msextra.com
Forum rules
Read the manual to see if your question is answered there before posting. Many users will not reply if the answer is already available in the manual.

If your question is about troubleshooting, configuration, or tuning, you MUST include your processor type (MS-I or MS-II) and code version in your post. If your question is about PCB assembly or modifications, you must also include the main board version number (1.01, 2.2 or 3.0).

If you have questions about MS1/Extra or MS2/Extra code configuration or tuning, please post them at www.msextra.com Such questions posted here will be moved to: a temporary MSextra sub-forum, where they will be removed after 7 days

The full forum rules are here: Forum Rules, be sure to read them all regularly.
Post Reply
Philip Lochner
Helpful Squirter
Posts: 96
Joined: Thu Feb 16, 2006 5:18 am
Location: South Africa
Contact:

Megamanual correct? (Next Pulse Tolerance)

Post by Philip Lochner »

The base ignition settings of Megamanual reads as follows:
Megamanual wrote:If a pulse is NOT received after X+PulseTol, a tooth is assumed to have been missed.
Should that not read: If a pulse is NOT received before X+PulseTol, a tooth is assumed to have been missed. ?
Best regards
Philip
'74 Jensen Interceptor Mk3 (MS-2 EFI, GPIO + GM 4L60e)
'80 Jaguar XJS 5.3L V12* (MS-2 EFI + dual EDIS-6)
and about 10 others.
grippo
Site Admin
Posts: 286
Joined: Mon Feb 16, 2004 6:55 pm

Re: Megamanual correct? (Next Pulse Tolerance)

Post by grippo »

PulseTol is a % tolerance, so the processor looks at the times between teeth or tach pulses, depending on mode, and applies the rule that the differences between the times must be within +/- pulseTol %. If the difference is too large, a virtual pulse is assumed to have occurred, and if too small, the pulse is rejected as noise. But, If they are outside the tolerance more than one time in a row, the processor begins the resynch process and rpm is set to 0.
Philip Lochner
Helpful Squirter
Posts: 96
Joined: Thu Feb 16, 2006 5:18 am
Location: South Africa
Contact:

Re: Megamanual correct? (Next Pulse Tolerance)

Post by Philip Lochner »

Thanks Al

That is how I understand it which is why I think a rewording of the manual might help:

Megamanual:
So if the time between the last two events is X, then if then next pulse occurs within X-PulseTol, it is rejected as a false trigger. If a pulse is NOT received after X+PulseTol, a tooth is assumed to have been missed.

Suggestion:
So if the time between the last two events is X, then, if the next pulse is NOT received after X-PulseTol and before X+PulseTol, a tooth is assumed to have been missed. If a pulse occurs before X-PulseTol or after X+PulseTol, it is rejected as a false trigger.
Best regards
Philip
'74 Jensen Interceptor Mk3 (MS-2 EFI, GPIO + GM 4L60e)
'80 Jaguar XJS 5.3L V12* (MS-2 EFI + dual EDIS-6)
and about 10 others.
grippo
Site Admin
Posts: 286
Joined: Mon Feb 16, 2004 6:55 pm

Re: Megamanual correct? (Next Pulse Tolerance)

Post by grippo »

The problem with your suggestion is that it assumes the processor is polling every microsec or so " did I get a pulse ?". In fact it doesn't do anything until it does receive a pulse via interrupt (but there is a timeout in case it doesn't receive anything for a relatively long time). Then it only rejects as noise if the received pulse is before X-tol. If it occurs after X+tol it doesn't reject as noise, it assumes a pulse was missed.

The algorithm isn't perfect, but its main purpose is not to correct for noise/ weak detection, it is to minimize the chance of ending up with an incorrect tooth count and not knowing it. That is why it resynchs pretty quickly if everything isn't right.
Post Reply