### ## ## ## #### ## ## ####
______ | ___| | |_ | _| | | \_|
#### ## ## ## ## ## ## ####
___ ( _`\ | ( (_) | |___ | (_, ) (____/'
## ## ##### ## ## ## ## #####
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: || [http://www.vems.hu/wiki/index.php?page=MembersPage%2FKarolyBakostrigger Trigger]|| [http://www.vems.hu/wiki/index.php?page=MembersPage%2FKarolyBakosconfig Config and tables ]|| [http://www.vems.hu/wiki/index.php?page=MembersPage%2FKarolyBakosquestion Q & A]|| ---- 2007-09-09 1.1.27 works well I can make spark everywhere :) Q. : The pulse width always 1.6ms or less ( with firmware 1.1.27 ). The used config is the same with 1.1.23. (with 1.1.23 and the same config and tables I get the right pulse width -around 15-20 ms for crank -). What could be wrong? A : Did you update the vemsv3.ini in your current Megatune directory to version supplied with the firmware distribution e.g. in \firmware_1.1.27\doc\megatune\vemsv3.ini ? Pulsewidth variable was changed a bit in 1.1.27 (higher resolution). - DB *It was my fault, problem solved. THX ---- 2007-09-19 The engine is runing. Both VR sensor needed 15kOhm pullup. Q.:Problems with spark advance -tested between 800-1200rpm- . Engine runing, LCD (Megatune too) shows the right advance angle, but I get spark around the rigtht (plus-minus 5-10 degree or more). I tried with signalgen too . Scope1: crank signal(stimulated with signalgen around 1000rpm) with one of the ignition channels. http://www.vems.hu/files/MembersPage/KarolyBakos/netre01.JPG Those pins looks not too good for me, but disappear without the wastedspark coil. Scope2: two ignition channel together -EC36pin34 EC36pin36- (stimulated with signalgen around 1000rpm)easy to see the difference between the pulldowns http://www.vems.hu/files/MembersPage/KarolyBakos/netre02.JPG ----- 2007-09-25 Az elogyújtás értéke a fent látható módon változik a dwell értékével együtt (scope2). Ugyanazzal a (Signalgen által produkált) wav-val hajtva véletlenszeruen: *vagy a fentlátható hibás értékeket produkálja ( trafó töltésének kezdeti idopontja OK -a beállított elogyújtás és dwell értékéhez képest- viszont a kisütés idopontja elcsúszik)(scope2) *vagy tökéletesen megy a megadott elogyújtás és dwell értékkel. (Scope1) *1200-1500 rpm-rol indulva mindíg stimmel a gyújtás *ha 200 rpm-rol indul teljesen véletlenszeruen produkálja a hibát. * Suspect: "when dwell is timed from the same tooth as spark". ** This only happens at low-RPM with low toothcount (such as 8-1, 4-1) ** for higher RPM, the same (eg 3 msec) dwell is greater angle. Check where, relative to given tooth the spark is timed from, and the dwell-start. Can you confirm ? ----- 2007-10-03 36-1 es konfig tesztelve signalgennel produkált wav (m351). A fenti problémát produkálja rapszódiusan 800 1/min -ig, ám utána minden esetben helyreáll és megfelelo helyre kerul a gyujtás. DWELL 11.4 és 5.4 között: http://www.vems.hu/files/MembersPage/KarolyBakos/36-1_bad_measurea1rpm1020.JPG http://www.vems.hu/files/MembersPage/KarolyBakos/36-1_bad_measurea2rpm1020.JPG A 8+2 es konfignal, ha nem stimmel a gyujtas a mérések alapján 1600-2100 1/min feletti fordulaton a megfelelo helyre kerul. Can you check how it behaves with forced ignadv ? like mda28 for 10 degrees. Does the minimum RPM of good operation change as the forced ignadv is changed ? ----- 2007-10-04 The problem is still the same. Forced 10 degrre of advance with mda28. The rpm around 400-500 1/min. http://www.vems.hu/files/MembersPage/KarolyBakos/36-1_mda10.JPG I get the right advance after the rpm of 800 1/min. http://www.vems.hu/files/MembersPage/KarolyBakos/36-1_mda10_good.JPG 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.