I would like to order the ECU for our new project. Golf2 with swapped R32 engine from Touareg (engine code BMV). Harness, config and tuning of the engine is not a problem for me, but we need help with CAN communication with standalone DSG gearbox control unit from company HTG-Tuning.
I was talking with HTG and they say that they are able to implement all CAN protocol types to their GCU.
See AimCanBusMessages for CAN-ID and data-content:
GCU needs these data via CAN:
Let's start with most basic data:
A) from ECU to GCU:
- RPM
- PPS (or TPS if only mechanical throttle body is installed on engine)
- MAP
- Launch Control active
- actual calculated torque
- when no fuelcut, approximately proportional to MAP*(1-igncut)
- it's extra signal, GCU can be fully functional and performing without this value - it's controlled then by different method
B) from GCU to ECU (any specific CAN-ID and exact data content ?):
- driven gear
- upshift request (to perform gear cut)
- downshift request (to perform blip)
- output speed
- trans temperature
- If VEMS ECU should receive some data from the CAN-bus CAN-frames, that needs to be specified (CAN-IDs, data content).
Later we can extend this set with additional data like Slip % or other.
My questions are: Can i did this with ecu ordered with 2 serial ports and your AIM to CAN adapter? If i understand it right, CAN adapter must be programmed before purchasing. Can you please tell me if some of pdedefined dash CAN protocols (for BMW or Audi) can provide data which GCU needs?
- the AIM protocol has the data, see AimCanBusMessages
- so HTG can find datas which they need?
- The aim2can module also sends data to VEMS ECU, notably wheelspeed and analog channels. If VEMS ECU should receive some data from the CAN-bus CAN-frames, that needs to be specified (CAN-IDs, data content).
Maybe this thread also will help another customers which wants to use VEMS with DSG gearboxes. HTG-Tuning are really friendly and innovative company which looks like someone who wants to make a new cooperations. Since dsg geafboxes are very popular now, i think here is the chance to open new markets and find new customers for Vems ecus.
ECU Specifications:
2+6 Ignition Channels (6 Coils with logic level + 2 IGBT for VVT)
2x VVT solenoids (want to use 2 IGBT channels for driving VVT solenoids)
1x VR crank
2x Hall cam sensors (so need third trigger)
1x PWM idle valve (want to use spare injector channel)
1x PWM solenoid for Variable intake (Spare injector channel)
1x WBO2 LSU4.9
1x Wheel speed input (speed info for DSG or traction control)
No knock
1x EGT (just for sure...maybe turbo conversion in future)
1x 400kPa internal MAP (just for sure)
1x ETC module (best internal in ECU)
2x COM port (1 for tuning via Vemstune, 1 for Vemsdisplay or in future for CAN module for DSG communication)
1x RS232 to CAN module with AIM protocol option
1x RS232 to BT module
Engine electronical components specifications:
-Ignition:
Coils 1.970.434 = AUDI OEM 022 905 100 P, active coils. Pinout (direction from flat end to round end of connector): Pin 1 = GND, Pin 2 = GND, Pin 3 = +12V, Pin 4 = Signal from ECU
-Injection:
Bosch Injectors, high-impedance, about 390ccm
-VVT:
2 solenoids (1 for intake, 1 for exhaust), 2pin, resistance: 10-18 Ohm
-Sensors:
Crank: 60-2 teeth wheel, OEM Nr. 021 906 433 E, VR type, 900 Ohm, Pinout (from flat end): 1=shield, 2=GND, 3=OUT signal
CAM1: (2 short + 2 long teeth wheel on each CAM), OEM Nr. 06A 905 161 A, HALL type, Pinout (from flat end): 1=+, 2=OUT, 3=GND
CAM2: same as CAM1
O2: WBO2 Bosch LSU4.9
TPS: for now TPS from mechanical TB, for future we want to installing ETC
Water temp: OEM 06A 919 501 A, NTC (don't have any other info)
Last question:
Do you have any trigger option in VemsTune for these engines?
I don't have checked yet the position between CAM and Crank wheels (i'll check it).
This is how triggerwheels for Trigger2 and 3 looks like:
I did lot of r32 with vems, trigger works good. Contact me over facebook( damir muha)
Also i'll soon test that controller on 1.8t 20v with dq500 gearbox