VT 5.0 ADX

[yoda69]

Try this one, I stuffed something up earlier but did have it working fairly well at one stage, haven't got a VT V8 to play with at present.

VT_$A6_v1.0.adx

(105.69 KiB) Downloaded 509 times

NOTE: This is for TP5.

Best thing to do is set up a connection command macro that listens for silence and disables chatter, the a monitor command macro that sends the command and waits for a reply, and a disconnect command that enables chatter.
This one may need a bit of tinkering, but may be closer than where you're up to.
There are a few things wrong regarding AC pressure and possibly a couple of other things, but the main ones should be OK.

Still working on the $A6 Variant C/E xdf update, will hopefully be able to add most of the stuff I've found for the V6 $A5 ones as they are fairly similar in a lot of areas.
If you manage to update the adx, please post it back up here.

Thanks,
yoda69

[vn5000]

Thanks for that YODA 69
Sure will save me a lot of time.
Ijust took it for a drive while datalogging with the adx ive made - man what a strange animal these things are .Started engine without tp5 connected and all lights go out , but about 5 sec after connecting check eng light comes on ,cooling fan comes on ,air bag light comes on and after driving 5 min temp guage not moving but all other guages working + aldl data saying engine 85 deg.Then when i got home i disconnected tp5 with engine still running and after 5 sec temp guage starts reading correctly ,check engine light and air bag light both go out,and engine ran fine the whole time.What the fxxx.
thanks again yoda , ill give your adx a go and get back to you . Also thanks for sorting the xdf .
VN5000

[Holden202T]

the interface stops the communication on the data bus ...... thats why you have those issues .... vl400 might be able to correct me but i think the no echo board fixes that issue ?

also i dunno how similar it is but i've been logging my mates vs v8 and using $12 adx (not $12P but normal $12 GM).... all the engine data seems to be right for me ?

[vn5000]

Hi Holden 202
I actually used a vs v6 adx made by you for scannerpro as a base to start with .But no matter what i tried i could not get it to connect properly. I eventually got it to connect using the commands to stop chatter that Jayme posted and a lot of the data stream matched. I could be wrong but it appears that in commys vn -vs you need to dissable chatter from ecm , but for this vt you need to stop the bcm chattering ,it wont even shut up with the ign off.I have used std $12 adx to on vr auto and vs v8 man with success but it wasnt going to happen with this vt.
You mention hook up a max 232 full duplex board ,sounds like a good idea ,but can you have it working at the same time as std single wire -as you say vl400 would prob know.
Also i tried Yodas adx he posted and all seems good -thanks Yoda

vn5000

[Holden202T]

the vs v6 adx is for scanner pro and all the connection commands are not right for TP5 .....

if you use a full duplex max232 why do you need the single wire ?

i'm pretty sure the bcm keeps talking till you lock the car.

[vn5000]

I knew it was a scannerpro adx , i mainly was using it for what went where in in data stream ,and changed all the commands to suit tp5 ,and then it connected to tp5.
If you had laptop connected to max232 duplex board wouldnt the bcm and dash still need to read data from single wire as well.What i wsa saying is can the uart be used to control both at same time.

[VL400]

Not sure what interface your using, but if its a max232 full duplex board it knocks the comms totally like holden202 as saying - even VATS will fail to disarm. Its not a good way to wire a comms board and may damage the SXR chip in the PCM. If its a normal one wire ALDL interface over the vehicle data interface you will have the dash going screwy until normal comms are restored.

In VT and later vehicles the BCM is the bus master so you need to disable the chatter on it instead of the PCM - the $F1,$56,$08,$B1 command. The VT-on BCM has a message schedule for the various devices. Following the heartbeat frame is the largest amount of time in the message schedule, so the correct way is to time your data requests to only happen after the heartbeat frame. You may even be able to leave the chatter enabled if requesting small messages from the PCM, but have not tried this.

[delcowizzid]

ive been using yodas vt a6 v1.0 adx for a few weeks seems to work pretty good cranking flag must be engine run flag not crank its off when engines off and says yes when running.heres a few logs from the car its not long had some cheap universal o2 sensors fitted and it seems they have died while tuning log1 is last week pre tuning ive just been out today finding out why the car looses all power and wont gain revs stumbles away and then comes right thought the pump had died. fuel trims pegged at 25 o2 sensors low mv and every now and then they jump high no crosscounts dead as a dodo must be so rich its missing and farting LOL.o2 sensors with cold engine and engine not even started jump from 30mv to 450mv instead of just staying at 450mv solid and after going for a drive and parking up does the same thing ,time for some genuine sensors i think

1st log.xdl

before tuning

(315.01 KiB) Downloaded 394 times

log2.xdl

first sign of dieing sensors

(118.82 KiB) Downloaded 361 times

home.xdl

dead

(618.67 KiB) Downloaded 365 times