22.06.18
Homemade Genboard V3.8b SN:11034
I changed IGN ch-00,-01,-04,-05 and -06 to Logig Level outputs, on the bench all work well. Installed on the car, no ignition on ch-01 and ch-06. With my DVM i can measure the logic level output signal on both connectors. It seems that the signal it´s not strong enough. I use dwell 3,2. You have any idea what happen? Logig Level config you see on the picture below.
I want to use analog ch.0, ch.1, ch.2, ch.5, ch.6 and ch.7 for DBW (PPS1, PPS2 and TPS2), ALS, LC and Mapping switch. Can you check the picture below, if the wiring is correct?
07-02-2018
New order Genboard V3.9:
Audi AAN Install with Hall/Hall,
Options:
- 3*analin, preferrably no pullup for DBW/ETC
- 2* EGT
- ALS
- Launch Control
- Shift Cut
nalog input Multiplexer not needed.
- 3+2 analog and 3 on/off inputs (<= 8)
- 8 mcp3208 analog inputs can be used, even with older fw
- not needed here, but for some on-off features some digital inputs can be used (3d trig, 2nd wheelspeed ?) in new firmwares (to free up more analog inputs for oil pressure, fuel pressure, more EGT, ...)
______________________________________________________________
22-09-2017
New Genboard v.3.8b SN: 15516 Homemade:
Bootloader Problem: After assembling the Genboard (AAN/Auditrigger), i tested the VEMS just with GND (EC36/5+21+22+26+32) and 12V+ (EC36-23+25) connected, nothing more connected.
- All runs normal and i load my config file.
- After the config,i start to load newest firmware, during upload comes a fault message and the upload broke up.
- indicates firmware upload was interrupted
- usually bad RS232 (or RS232 ground missing, or other ground problem. Tried with notebook running on battery (NOT from AC ) ?
- I tried to upload a lot different firmwares, but after 0,2% always it brokes up with the message "Firmware upload has been cancelled"
- kindof expected if the RS232 setup is bad
- I loopback the board with a jumper set between DSUB9 pin 2+3, but no help
The RS232 (or the RS232 ground) is first suspect. Even if it mostly seems to work in VemsTune (logging), which tolerates worse RS232 cable/setup than the bootloader fw upload. New bootloader is unlikely to fix it.
-RS232 GND checked and all other GND checked again - all Good, better GND it´s not possible!
-Tried to connected with Notebook running on Battery - no help.
-Tested another Laptop with new installed VEMStune - still no connection.
-I used the Terminalprogramm, but i can´t see any communication.
-I have another v3.8b Genboard with SN:11034,the Board its completely identical configurated like SN:15516. I tested it on the same Bench, with the same FTDI Adapter and Laptop. I sucessfully Update the firmware from 1.2.31 to 1.2.38. The bench, Laptop and Adapter its not the problem.'''
- Some installers use EC18/17 as RS232 ground for convenience, which is usually GND, but EC18/17 can be 2nd heater FET output (set up for 2nd WBO2, or just a generic output, even without 2nd WBO2)
- that is the usual cause of "loom/RS232 works with all, but not with a certain ECU"
- Might not be the case here. Do you have ISP ? Either avrdude compatible USB or Parport + 5 wires -c ([alf] or bsd, stk or dapa pinout, either is OK just use the correct avrdude -c ... option).
- more info in priv
I build a new AAN Genboard V3.8, with Hall/Hall setup.
For ignition I want to use 5 Logic Level Outputs
- I connect the gate withe the output and soldered a second 510 Ohm resistor parallel to the other 510 Ohm resistor.
- sounds good
- If i measure now the Logic Level Outputs, than i have all the time 2,5V
- sounds like some PWM-ing is configured and it oscillates between 0V and 5V (DVM showing "mean" / average value)
- and in the Ignition Test Mode, the Voltage jumps only from 2,5v to 2,7V.
- It is possible that i destroy the 74HC259 Chip?
- yes, possible.
- Try to disable ignouts first (in config), and configure misc2 to ignch0 / ignch0 inverted (switch back and forth: that is a very good test you can easily do with a DVM!)
- The ignout pulses are VERY short, you cannot measure with DVM (you can see on a scope if properly using the scope advanced triggering features: you can see on a LED connected between output and GND, with 270 Ohm series resistor => much easier )
Solved!!! Now i used a scope for Testing. On the end i found a weak GND wire inside the car loom.
Home build AAN from Genboard v3
Soldering:
Reenforce soldering on TO-220 componets's GNDs, they really weak at this time.
IAC:
A shottkey diode will need from JPT55/4 (EC36/6) to the flyback JPT55/37, cathode face to JPT55/37 (Solder the diode's cathode to the anode of the 30V flyback diode, this is the easiest way.)
Ignition:
Remove all FET witch is in the place of an IGBT and solder an 510Ohm(1206) parallel with the soldered 510Ohm(0805). After this connect the gate with the output in the place of the removed TO-220 component.(Wire the signal from the two resistor to the Econoseal pin.) You need to do this only on outputs used for ignition.
Insulating:
Stick the teflon sheets to the metal case, this way the components will insulate from the case as well as from each other. In the end recommended to make insulation test with a lamp. Connect one pin of the lamp or anode of a led to +12V, other pin or cathode to the metal case. Start to test the injector outputs in VemsTune one by one. If the lamp or led ever lights up, the insulation is bad. You need to fix it.
WBO2: If you not reuse or add wires to the factory harness, it won't work as it connected now.
Both of the controllers has factory AAN configuration, if you ever miss them up you can download or we can send you.
Note that since 2015, there exists dedicated VEMS "v3.9" mainboard for Audi AAN motronic55 harness pinout. It's cleaner install for any mot55 harness (but it has no stepper chip, and fits in longer box: AAN PCB is 110*160mm instead of 98*160mm). Otherwise same (hw, firmware, sw) as genboard v3.8
- the midopa (middle LM2902 or LM224, labelled LM324 on schematic) is NOT needed, and NOT populated, it's only useful in very special setups (differential input). (could be used to amplify non-GND referenced signal, or to amplify non-insulated K-thermocouple signal).