## ### ## ## ## ## ## ###
# # # # # # # # ## # # #
___ ( _`\ | ( (_) | |___ | (_, ) (____/'
|\ /| | ) ( | | | | | | | | | | | | | | (___) | (_______)
# ## # # # # # ###
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: Details: 1993 Audi 80/90 Quattro 1997 Audi A8 4.2 liter V8 engine with sequential injection and coil-on-plug ignition. Using a 60-2 trigger wheel on the crank with a (I think) VR sensor from the 1993 12v V6 and the stock A8 4.2 cam position sensor (Hall). http://www.ubernugen.com/vems/4.2installed1.jpg **************************** 28 September 2005// Ok, I got my wiring hooked up and the board says Hello Here are the steps I have just taken with the new software. I will now head over to the car and see what happens: 1) Erased everything on the hardrive having to do with mt/vems (Vems ECU still has .18 firmware on it). 2) downloaded firmware .18, firmware .18 ignition dual output files, mtr024, mtr025 ini. 3) unzipped mtr024 and mtr025 ini. Replaced the r024 .ini with r025 .ini in MegaTune2.25b602/mtcfg folder 4) unzipped firmware .18 and .18 dual ignition output files, inserted dual ignition files into firmware .18 directory 5) deleted the .15 firmware native to the the megatune folder and replaced with the new .18 firmware folder. 6) deleted the pre-existing config.mtt and tables.mtt files in the firmware/ect folder 7) converted the existing config.txt and tables.txt to .mtt files with: perl bin\make_table.pl tables.txt tables.mtt perl bin\make_conf.pl global.h config.txt config.mtt And put them in the firmware/etc folder 8) now I am ready to burn the firmware to the VEMS ECU again, right? I don't see why it would be needed, if you already have the newest (1.0.18 at this time). You can verify first. (but burning again is not a big deal either) IT WORKS!!! * Now that we know how to wire the CPS I just need to somehow see where it is with the crank at TDC? Still a little fuzzy on what I am looking for there... ** after the sensor sees the first tooth after the missing tooth (gap), count the number of teeth to the first TDC event. Place a wire in a sparkplug hole if you are unsure about cylinder position. With a manual gearbox, use gear5 so the engine can be moved easily by rolling the car a little. ---- '''IGN_DUALOUT''' (ben writes) This info below is a little fuzzy to me. Is this a hack so I can run without the second trigger wheel for a while? I guess we might as well make it go with wasted spark if possible since it sounds like I need to make a new trigger wheel for the cam. (/ben) On Jorgen's request, Marcell compiled a firmware with IGN_DUALOUT: http://www.vems.hu/files/Firmware/release/v3_firmware_1.0.18_IGN_DUALOUT.zip I added the note to GenBoard/UnderDevelopment/FirmwareChanges that MegaTune vemsv3.ini needs a small change. With the old definition of "42 bytes of runtime-vars", MegaTune will beep like hell. It is untested (but compiled with the same compiler as other releases, that all passed testing). IGN_DUALOUT means, that * in h[2] you configure channel 01, and 00 is also fired at the same time. * in h[2] you configure channel 03, and 02 is also fired at the same time. * in h[2] you configure channel 05, and 04 is also fired at the same time. * in h[2] you configure channel 07, and 06 is also fired at the same time. So a sane configuration is: * ignchmax=03 * h[2]=01 03 05 07 01 03 05 07 With a 60-2 wheel, and another_trigger_tooth=0x0F (decimal 15) only the first four element of h[2] is actually used (but with IGN_DUALOUT, each fires 2 channels). Eg. if you configure trigger_tooth=03, * timed from tooth 3: ch7 and ch6 * timed from tooth 18: ch5 and ch4 * timed from tooth 33: ch3 and ch2 * timed from tooth 48: ch1 and ch0 are fired. The exact time is (ign_tdcdelay/2 - actual_ignadv) crankdegrees after the tooth. ( ign_tdcdelay is 0.5 degree resolution, but MegaTune does the conversion for you IIRC) * Does this mean that I'm not using tooth #2 anymore? Please clarify... ** you can configure any trigger_tooth you like. According the image on MembersPage/BenNesbitt/InputTrigger you're still triggering from teeth 2,17,32,47 and assume that TDC is 60 degrees later (that is teeth 12,27,42,57) ---- Fill in these pages with all the required info and watch your config be pretty much built for you MembersPage/BenNesbitt/IgnitionPage MembersPage/BenNesbitt/WBsensor MembersPage/BenNesbitt/FuelPage MembersPage/BenNesbitt/InputTrigger MembersPage/BenNesbitt/IdleControl MembersPage/BenNesbitt/SensorPage MembersPage/BenNesbitt/ConfigPage 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.