You can change the style the forum displays by selecting your preferred style at the bottom left of the site.
We have made an enhancement so that old threads should now link from search results to the correct thread. This is not yet in place for single post links
Mine does that as well but has no implication to the engine. Its just a small glitch of vems. Fueling and engine works fine so its just psychological. I'm not worried
Mine does that as well but has no implication to the engine.
To be fully correct - the implication is reduced ignition angle precision.
Of course on a practical level it can be OK, but it is not fully correct to say that "it does nothing at all".
Vems records a trigger error in the log but it causes no ignition timing changes- delays- obstructions- misfires- or any other word you can think of. The precision you are referring to is not causing any performance issues either.
At that rpm and timing/fueling of there was a true problem there my engine would have been in shreds by now
Vems records a trigger error in the log but it causes no ignition timing changes- delays- obstructions- misfires- or any other word you can think of.
It can not run without trigger. A trigger error as I understand is an edge that is not recognized. It can be interpolated, but there is momentary loss of precision.
Of course this is probably handled safely and timing is late rather than early.
So I disagree with you in theory, but I agree that if it is one or two teeth skipped, then there is probably not a really measurable difference there from the standpoint of the practical working engine.
Vems records a trigger error in the log but it causes no ignition timing changes- delays- obstructions- misfires- or any other word you can think of. The precision you are referring to is not causing any performance issues either.
At that rpm and timing/fueling of there was a true problem there my engine would have been in shreds by now
I cannot be more clear than that.
sent with Nokia 6210
I had same on original setup and that was no problem car was running fine.With 7a flywheel, that was really bed till I'm not put sensor closer ant download 1.2.2 firmware now no any errors at all.That can try people who have this problem
It can not run without trigger. A trigger error as I understand is an edge that is not recognized. It can be interpolated, but there is momentary loss of precision.
Of course this is probably handled safely and timing is late rather than early.
So I disagree with you in theory, but I agree that if it is one or two teeth skipped, then there is probably not a really measurable difference there from the standpoint of the practical working engine.
I agree... and the trigger error makes me sick it feels like a missfire for a millisecond
My sensor has been so close that during a manual rotation of the crank it touched ad broke it. So I know its not the sensor. In my case it may be the fact that I had to weld a larger pin and it may be slightly larger than it should. But it works and I haven't given it a second thought.
By the way, I don't understand the logic of divide by 27 when the developers say use 9. how do you end up choosing which one? At random?
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Tweet
it feels like a missfire for a millisecond
Comment