Project Page Home
My name is Anton, I'm 18, live in Helsingborg Sweden and I'm building a '94 Audi 80 Quattro. It originally has a 2.3L 10v N/A engine in it but I'm building a turbo converted 2.3L 20v to put in it and a GenBoard v3.3 to run fuel injection, boost control and distributorless ignition. I'm doing this partly as a school project, by myself.
This page will be mostly about the VEMS related parts of the project, check my page at motorgeek.com for an overview - http://www.motorgeek.com/phpBB2/viewtopic.php?t=8757
My biggest inspiration for this project is Javad Shadzi and his car, http://www.80tq.com/20vtMotor.html
See InternetHorsePower - Not sure why you made this comment but, Javad is the owner of http://www.034motorsport.com and he's well known in the Audi tuning circuits. He's very professional and I have no doubt that his numbers are genuine, he knows and lets us know exactly the factors playing in to his dynoing numbers. See http://www.motorgeek.com/phpBB2/viewtopic.php?t=8814 - Anyway this isn't very relevant since I'm not bulding the engine to make huge HP numbers, I just want a good mechanical basis to apply the GenBoard to.
Sections
MembersPage/AntonLilja/PreviousProblems
MembersPage/AntonLilja/Assembly
Hooked up serial, keyboard and LCD.
- serial number 303, sent out on 2005-07-09 (among the first 5 v3.3 - these had no R181 PNP-ed)
- apparently you assembled yourself: confirm R181 has been soldered (100 .. 180k) according to the note you received from the shop: If using VR on primary trigger, please check R181 100k (0805 size SMD)resistor at LM1815 pin7. (min 47k, max 180k; 100k recommended: you can find 100k in rescue kit marked as 104 ).
- R181 is connected to LM1815pin7, so NOT the two pads right next to LM1815 pins 6 & 7 (which is the 3 pin header connected to LM1815 pin5, leave that 3 pins open!)
- You do not actually need the R181 resistor when using HALL as primary, but recommended to install it anyway to avoid future surprise (if using VR later). Anyway, have a note about this in the logs (or trigger related notes) that you write for your ECM.
- believe it or not, I independently copied the old R181 note (we even had an edit conflict when I saw your question and added more info on the pin).
- remove D100 if you use powerflyback 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)
- apparently you assembled yourself: confirm R181 has been soldered (100 .. 180k) according to the note you received from the shop: If using VR on primary trigger, please check R181 100k (0805 size SMD)resistor at LM1815 pin7. (min 47k, max 180k; 100k recommended: you can find 100k in rescue kit marked as 104 ).
The above is not related to MegaTune (version/comm) problem.
Questions
Q: I'm following MembersPage/PhatBob/UserGuide and I've connected and powered up the board to the computer.
- the keyboard/lcd works
- I can work the menus in terminal, say "Man" in TerminalProgram or in the mini-terminal in MegaTune, but when I try to test the connection through Communication Settings it says "No Response!". The settings are as in the userguide.
before trying megaTune
- right after reboot (after powerup, default is binary megatune communication mode)
- tried: no success
- if you can use the menu commands, it's in "Man" mode in which you will NOT be able to connect for normal MegaTune logging / tuning. Try "bye" (again), maybe you need to close the terminal window, etc...did you say "bye" in TerminalProgram (or terminal window) and received "Bye" from the ECM ?
- tried. But: was the "Bye" answer visible ? - Yes it was.
- MegaTune, firmware version ?
- VemsMT1.0.30rc3.zip
- firmware version is 1.0.13
- mdv : "2005. júl. 5., kedd, 21.13.00 CEST"
- mdV: "1.0.13"
Solution: These are incompatible. Either
- find an old MegaTune release matching your firmware (unsupported. the shipped firmware is ment for testing )
- or upgrade firmware. The firmware bundled with the MegaTune is often a good bet (but read GenBoard/UnderDevelopment/FirmwareChanges anyway).
- Try another serial cable?
- Does NOT seem to be a problem in your case
- Another computer?
- this can work, if the other computer has a MegaTune installed that is compatible with your firmware ;-)
- MegaTune install location:
- nope, MegaTune is not picky on the install location. This allows you to have several versions installed (eg. always have one -operational- for each install, eg. your customer's cars too)
Thank you for the solution!