_ ( \ | ( | | | | | | | (____/\ (_______/
## ## ## ## ## ## ##### ## #####
______ | ___ \ | |_/ / | ___ \ | |_/ / \____/
____ / ___| \___ \ ___) | |____/
___ | _`\ | (_) ) | , / | |\ \ (_) (_)
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: I found the settings i can read RPM and i have IGN out drriving , but the RPM is fluctating . http://vems.hu/files/Norbitron/lotus/triggerlotus.jpg * [http://www.vems.hu/files/Norbitron/v3.3_u022058-2022-04-08-16.21.23.triggerlog triggerlog] Investigating trigger setting for '''Lotus 6+1 trigger wheel.''' * currently no camsync Please see MembersPage/CustomExtraTooth (but also similar to Honda extrapulse and shortgaptrigger below). ---- '''Config guidelines''' Starting from Honda K20 * Extrapulse = enabled ** strig_validation=08 only extrapulse, nothing else (no cam_check_pol ) * tooth width = 60 (not 30) * next trigger tooth (distance) = 3 (not 6) * reference tooth= 0 3 0 3 (not 0 6 0 6)... Neglect VT warning... * advanced filtering=enabled (1/4 of values below will be effective ??) ** normal rel min=12.5% max=119% (3.1 - 30% for extrapulse case ? So 3.1 ..30% will be '''considered SHORT, and detected as extrapulse''') ** missing rel min=175% max=300% (44-75% for extrapulse case ? So 85..100% normal tooth will look LONG) '''Relevant, but uncertain''' * primary_trigger=1B ** rising edge (good for VR) * secondary_trigger=43 (not 02) ** camsync disabled ---- Sounds like * InputTrigger/ShortGapTrigger - The fiatstilo bit must be enabled for both primary_trigger and secondary_trigger. ** multitooth advanced filter (you can tweak these advanced filter tresholds): ** neglect longer gaps (150 .. 200% relative), and trigger on the shorter gap (appr 30 .. 34% relative). primary_trigger=29 (decimal 41) tooth_wheel=02 The following seems to be the key to get it work: toothrel_normal=01 (normal tooth: 16 .. 100% '''Really tried 40..50% or so ?)''' toothrel_missing=F0 (missing tooth: 125 .. 300%) ---- * nr of tooth on wheel=06 ? (full engine cycle=12 tooth) * tooth_width = 60 crankdeg (angular width of tooth... NOT 180, of course) * Next_trigger_tooth=03 * trigger tooth=01 (00 or 02 would likely work also) --- '''similar to Honda K20 2005+ but less teeth''' I tried the honda '''k20 12+extra trigger settings''' but not read RPM, no ignition. ** with what changes ? ** Exact .vemscfg ??? ---- '''Logs''' * http://www.vems.hu/files/Norbitron/noadvfilter.vemslog with advanced filtering * http://www.vems.hu/files/Norbitron/advfilter.vemslog -without filtering * http://www.vems.hu/files/Norbitron/adv%20filter.vemscfg -vemscfg The car is still not started up. ---- '''Should be possible to configure (no firmware mod needed)''' * InputTrigger/HondaFTwentyTrigger ** says the extrapulse is after the normal (10,20 not 20,10) ** also mentions 120, 120, 40,80, 120, 120, 120 which is similar pattern ** 60, 60, 15, 45, 60, 60, 60 is about right ? Please confirm, check triggerlog. Or maybe * InputTrigger/HondaKTwentyTrigger would be easier starting point ? Either way, just need some tweakinf anyway ---- http://www.vems.hu/files/Norbitron/fly.jpg To compare the exact position of the extra pulse to TDC is very hard because the engine is rear mounted. Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.