# # # # # ## ### # # ####
_______ |__ __| | | | | | | |_|
/\ / \ / /\ \ / ____ \ /_/ \_\
#### ## ## ## ## ## ## ## ## ####
## ## ## # ## ####### ##### ## ##
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: As my Genboard v3.3 seems to be installed (see MembersPage/JoelZernask), I will now try to dig through the configration. http://www.vems.hu/files/MembersPage/JoelZernask/config.txt http://www.vems.hu/files/MembersPage/JoelZernask/tables.txt Note that you will need to download the config.txt from the box!!! You do this by issuing Manmcd in a terminal program. The response is saved as config.txt. If you don't do this you will have to recalibrate the wbo2! No big problem but a waste of time. I took a look at the tables.txt file and it was named tables..txt which will make the mtt creation fail. Check the dates of the tables.mtt and config.mtt files. Maybe the right files was not uploaded to the VEMS v3. I have renamed it to the correct name. * I changed the name myself, so this could not be the problem. In any case I have updated the config.txt file to work with firmware 1.0.36 http://media.vems.se/code/VemsMT1.0.36.zip which is a development firmware. But it significant improvements over the old production firmwares and it has been used for some time. -Jörgen * OK, I extracted it to my VEMS folder. I'll follow the instructions in the readme.txt and during the process replace the content once more in the tables.txt file. ---- '''Something went wrong''' OK here's what I did: I downloaded the VemsMT1.0.36.zip and extracted it to my VEMS folder. Then I did just what was instructed in the README.txt file - I ran download_config.bat, then config.txt appeared in the VemsMT1.0.36/config folder, an empty .txt file. Tables.txt did not appear, I don't know whether it was supposed to or not. Anyway I copied the content of the above linked config.txt in the file and saved. I also made a tables.txt in the same folder with the content Jörgen provided. Then I ran generate_config.bat and .mtt files appeared to the VemsMT1.0.36/config folder. Then I ran upload_config.bat, and got a "Hello" from the ECU. Then I ran upload_config.bat and got some strange unreadable signs in the black window. Then I tried to start the MegaTune and got the following sign: http://pildid.audiclub.ee/joel/kuubik/error.jpg The audit.log file is here -> http://pildid.audiclub.ee/joel/kuubik/audit.log So what happened? What should I do now, can I repair it myself or should I send my ECU somewhere? ---- '''Trigger''' '''Primary-VR''' * NOT multitooth * VR sensor (VR primary-trigger HW used; rising edge configured) ** do we know the polarity ? * 4 trigger pins on the flywheel, 62BTDC each cyl '''Secondary-HALL''' * 1 Hall cam sync pulse overlapping the crank trigger pin occuring 62 deg before #1 piston reach TDC in it's work phase. ** '''Rising edge 77d BTDC''' - certainly this one is to be used, so configure rising edge ** Falling edge 47d BTDC. Use the other edge, not this ---- Here are the specs of my engine: * 1989 Audi PT 3,6 liter 32valve V8 * firing order: 1-5-4-8-6-3-7-2 * ignition type: wasted spark * coils: two 2*2 coil packs (Bosch 0 221 503 407) ---- '''Ignition''' Cylinders firing together are: 1 5 4 8 6 3 7 2 The coil packs are connected as follows: EC36-pin35 to Coil 1 EC36-pin33 to Coil 2 EC36-pin34 to Coil 3 EC36-pin36 to Coil 4 Therefore cylinders are wired as follows (see GenBoard/Manual/DigitalOut/Table for driver channel numbers): Cylinders 1 & 6 to Coil 1 to EC36-pin35 drive00 Cylinders 5 & 3 to Coil 2 to EC36-pin33 drive01 Cylinders 4 & 7 to Coil 3 to EC36-pin34 drive02 Cylinders 8 & 2 to Coil 4 to EC36-pin36 drive03 * ignchmax=03 (03..00) * IGNITION OUTPUTS TABLE: h[2]=03 02 01 00 03 02 01 00 ** going from index config.ignchmax downto 0, the drive00, drive01, drive02 and drive03 will be fired, in this order. This spark table can be used, right? http://www.ubernugen.com/vems/17octsparkmap1.jpg '''It's about right for a start but there are lots of redundant loadsites. You only need 20,30,50,70,90,105,130,150,170,190,220,255. Having 12 kPa sites from 20-100kPa will just waste time when tuning the car which is always bad. Bens current spark and fuel tables will be in the tables.txt file I'm preparing -Jörgen''' Be sure to get the base timing (trigger_tooth and igntdcdelay) right. '''Fuel.''' Again referring to Ben Nesbitt's information, adjusted for my specs: sequential fuel delivery for Audi 3,6 V8 PT engine firing order: 1-5-4-8-6-3-7-2 Bosch injectors 173cc Fuel map: http://www.ubernugen.com/vems/17octfuelmap1.jpg Constant for RPM calculation should be 1500 (8 cylinders), right? http://www.ubernugen.com/vems/fuel5.jpg Req fuel is 16,7 in my case (173cc injectors). http://www.ubernugen.com/vems/fuel6.jpg Here are Ben's trigger tables. How should I fill the first one on my 4 pins setup? http://www.ubernugen.com/vems/mt10.jpg This one should apply to me as it is. http://www.ubernugen.com/vems/mt11.jpg Is this h[0] table correct? http://www.ubernugen.com/vems/fuel2.jpg ---- '''Communication problems''' * by default (yours too, since you didn't require otherwise!) assembled v3.3 is shipped with RS232 on EC18pin14 and EC18pin15, see GenBoard/Manual/CommHardware (webshop text says same!) After repositioning of the wires (getting it bad first?) we managed to get the only "Success!" message from the MegaTune. * assembled and clamped v3.3 is preprogrammed. Used for testing (although the firmware could drive an engine, upgrade is recommended) * 2. But there was still no communication between the ECU and my PC. I have downloaded and unzipped firmware 1.0.23 and MegaTune r028. Follow the instructions in the zip to upgrade firmware 3. We installed the Bray Terminal to see whether the ECU is alive. (exited from MegaTune for that time of course!). The <0>'s kept flowing and flowing endlessly. * first, check your GND and GND5 connections !!! If you have a broken ground, or cigar-lighter groundloop to the notebook, that can result in similar * 9600 baud: Man command ** No Hello! sign came out after Man command, just the <0>'s kept running. * 9600 baud, but view in hex: 'A' command ** result ? * '''BootLoader test:''' 19200 : 'S', 'p', 'v' commands ** result ? If "AVREFI1", "S", 30 or alike, you are on the track, in bootloader, just exit TerminalProgram and upload firmware without "t" option to prog.pl or megaloader (using Ew instead of Etw flags) I suspect you maybe have started a firmware upgrade that disconnected in the middle or something. Don't worry, in the worst case powerup the ECM with the ECM's RS232 (pin2 and pin3) loopbacked, than remove the loopback and plug in the PC. Bootloader test should work now, and you can proceed from there. Hopefully the bad connection didn't damage the max232 or something. If you disassemble the ECM, don't clamp it back until: ** remove D100 if you use powerflyback and PWM-ing GenBoard/Manual/PowerFlyback/RemoveD ** change C103 to 1nF if using secondary trigger HALL : Manual/InputTriggerHardWare/ReplaceC ** set AREF=256 BuildProcedures/SectionThree (not required but recommended) '''This problem is solved - it was all caused by a wrong ECU-PC connection.''' ---- 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.