Aftermarket ecu in a vt v6

[charlay86]

Most of the VT V6 transmission stuff is the same as the VS, it is just offset a few bytes in a number of places. I have been meaning to put it all into an xdf but haven't had the time yet. Is there anything specific parameters that you are looking for to change?

[Jervies]

Mainly the shift times and line pressures, iv modded the one on my van and increased the overall pressure (i think lol) and its firmed up the shifts but i cant change the shift time so the ecu is constantly trying to pull back the shift times/pressures. I cant play with the settings on my turbo 6 yet as its stuiped kalmaker. The wolf ecu already has an e85 l67 tune on it so i think im gunna have a go at tunning myself, and change the ecu to one the realtime tunerpro setups

[charlay86]

Here is the desired shift time table locations.
If you could add them to the A5F XDF and post it back, that would be great.
These locations are for an A5F bin.
They are all 1x17 tables, with a conversion of "X/40".

Code: Select all

LOCATION: 0x2282
1-2 DESIRED SHIFT TIME vs TPS%
NORMAL MODE / LOW ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x2293
2-3 DESIRED SHIFT TIME vs TPS%
NORMAL MODE / LOW ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x22A4
3-4 DESIRED SHIFT TIME vs TPS%
NORMAL MODE / LOW ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x22B5
1-2 DESIRED SHIFT TIME vs TPS%
NORMAL MODE / HIGH ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x22C6
2-3 DESIRED SHIFT TIME vs TPS%
NORMAL MODE / HIGH ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x22D7
3-4 DESIRED SHIFT TIME vs TPS%
NORMAL MODE / HIGH ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x22E8
1-2 DESIRED SHIFT TIME vs TPS%
POWER MODE / LOW ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x22F9
2-3 DESIRED SHIFT TIME vs TPS%
POWER MODE / LOW ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x230A
3-4 DESIRED SHIFT TIME vs TPS%
POWER MODE / LOW ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x231B 
1-2 DESIRED SHIFT TIME vs TPS%
POWER MODE / HIGH ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x232C
2-3 DESIRED SHIFT TIME vs TPS%
POWER MODE / HIGH ALTITUDE
SHIFT TIME (seconds) = X/40

LOCATION: 0x233D
3-4 DESIRED SHIFT TIME vs TPS%
POWER MODE / HIGH ALTITUDE
SHIFT TIME (seconds) = X/40

[Jervies]

If i knew how to i would. Im willing to learn if someone wants to bang there head against a wall trying to teach me lol

[charlay86]

This will probably need to be moved to the A5 XDF thread, but I have updated this XDF to add the desired shift times.

[Jervies]

Thanks heaps ill give it a go tonight and see how it goes

[Jervies]

So iv got the dual ecu's up and running so far the problems iv ran into are that the vt ecu must think its not running or something because it wont hold 3rd and 4th as if its got no line pressure or the tps isnt working. Im also getting a ect unstable code as im only using the one temp sensor so ill prob have to install a second one. The other one is iv got a bit of a miss that iv got to try find now, i may swap the spark back to the vt ecu to try. Can i put a dummy load on the etc output to the dfi so the ecu thinks its working? Cheers

[charlay86]

The VT PCM will not be happy if something else is connected to its sensors, the change in impedance from having something else connected in parallel will cause all kinds of problems. You really need to double up on sensors for this to work.

[Jervies]

Yes im in the process i designing a complex dual pole tps ie gluing 2 together lol. A second colant temp is easy and i already have the wires for it in the loom. Iv still got to find out why im having problems with the trans slipping, every time i try hook up tunerpro it crashes :/ its all a bit of trial and error but hopefully what ill end up with is a bin to be able to run a second ecu like the wolf, haltech or even a 808 ecu. Could open up some mafless tunning for the vs vt vx vy range

[antus]

the crash on connect on VTs is a known problem, and one I have tried to solve without success It seems like the VT to VYs have the most data on the vehicle bus - more so than any american GM car of the same era and TP just cant cope with it.

The work around is to disconnect your BCM while tuning. By doing this you will take the data off the bus and TP can use it to talk to the pcm. You will loose the dash while the car is in this state and you will need to disable VATS to get the car to run. But you should be able to see the vehicle data inside TP and do the tuning. re-enable vats and reconnect the BCM when you done.