pcmhacking.net

Posted: **Tue Mar 24, 2015 2:32 pm**

Realized that information didnt quite make as much sense as I thought it did initially.

.byte   0xF4         ; Outgoing Message ID - ECM

The outgoing ID should be F5 right? It is for the VS V6 I have here?

Also, mode 1 table 3 doesnt match up with that information. Since mode 1 table 3 is used in the TunerPro definition files where bytes 0x20 to 0x29 are the fault codes stored in bit arrays.

Unless Iv completely over looked something! Then I dont think mode 1 table 3 works for freeze data?

This is the frame I get back for table 3:
F5, 80, 1, 0, 0, 0, 97, 2, 1, 12, 0, 0, 0, FF, 4, 0, 0, 68, 51, FF, 1, 67, 7F, FD, 7D, 80, 80, 80, 6, 0, 0, 0, 0, 0, 0, 0, C0, 80, 2, 0, 20, 40, 2, 0, 0, 98,

If there is 4freeze frames stored and each utilize 10bytes total of information, then there isnt enough room

Code: Select all

   ;   44   1       - Malf Code Number
            ;   45   2       - Occurence Counter
            ;   46   3       - Ignition Cycles Since Code Last Logged
            ;   47   4       - 1ST Data Parameter
            ;   48   5       - 2ND Data Parameter
            ;   49   6       - 3RD Data Parameter
            ;   4A   7       - 4TH Data Parameter
            ;   4B   8       - Engine RPM Parameter
            ;   4C   9       - \ Engine Running Time Parameter (2 Bytes)
            ;   4D   10       - /

Posted: **Tue Mar 24, 2015 10:47 pm**

What I posted was from 11P, so a VR V6 and V8 auto. Same frames for VS V8 auto (though not series 3 MAF).

If your working on defining a VS V6 then yes it would be device ID F5, and its mode 1 message 7 instead of message 3.

Posted: **Wed Mar 25, 2015 1:56 am**

VL400 wrote:What I posted was from 11P, so a VR V6 and V8 auto. Same frames for VS V8 auto (though not series 3 MAF).

If your working on defining a VS V6 then yes it would be device ID F5, and its mode 1 message 7 instead of message 3.

Ahhhh right. I figured it must of been message 7. Will start coding it all up, so that at least it parses the custom variables depending on the fault code. Will suss out the custom vars afterwards unless they match that of the flash ecus , vx and vy.

Posted: **Mon Mar 30, 2015 4:16 pm**

Ahh bummer, I think Iv confused my self again staring at the frames for too long. Im currently doing the VS and VU/VX/VY freeze frames.. and Im lost on how to define what the freeze data fault code is...Ill grab some examples of current workings once im back
*Edit

F7,95,01,16,00,00,01,13,

Alright.. so from what I understand, the first fault there for be P0113? Or will it be the decimal value of that?.
Im working off that the fault code is displayed as its hex representation. I guess Ill see if it makes sense when I do the first read!

Posted: **Wed Apr 15, 2015 2:42 pm**

Sooo Iv been putting away in the background putting a dedicated application together for the ALDL ecus. Which has (hopefully) helped me understand the difference between them all.
After going through all the adx definitions and information I can find.. so far Iv found...

VR V6/V8 use same definition
VS V6/VS V8 'can' use same definition
VT V6/5.0L V8 and all S/C vehicles use the same definition (based on what I understand of: A5 Engine and trans TP5 v105.adx
VU/VX/VY flash V6 use the same definition

Only thing Im stumped on.. is what do VS Series3 V8's use? Are they still the same as the VS definition? I keep reading they are different but based on the provided definition file there not different?: VS 3 A6 Engine and trans TP5 v104.adx

Interesting to see that not a whole lot changed between them all.. they all grab similar information between all the models.. some parameters missing or new things added.

: AVD.png (84.03 KiB) Viewed 5251 times

Currently, I have it setup so that all the front gauges can be simply "right-clicked" and changed. Including colour schemes ect which will save for next times use. Each vehicle type (VR,VS,VT) will all have separate "saves" for the gauge setups.

The freeze data is a work in progress. Iv got routines down for VU,VX,VY (And hopefully VS and VT if they are the same but different Device ID). And the module details is still a work in progress... got no idea how to address this on VR and VS.. hopefully they do something similar?

Tazzi over and out!

Posted: **Wed Apr 15, 2015 3:02 pm**

VS Series3 V8's are the same as the VT but use a VS BCM

Posted: **Wed Apr 15, 2015 3:23 pm**

kojab wrote:VS Series3 V8's are the same as the VT but use a VS BCM

Cheers for that!

Posted: **Wed Apr 15, 2015 3:33 pm**

Looks good

Tazzi wrote:VS V6/VS V8 'can' use same definition

A VS V8 should be using the same def as VR V6/V8.

Posted: **Wed Apr 15, 2015 10:09 pm**

VL400 wrote:Looks good

A VS V8 should be using the same def as VR V6/V8.

So the standard VS V8 (Not S3) will be the same VR V6/V8? And the S3 will be the same as the VT but use a VS BCM (So no heartbeat!)
On The1's enhanced bins page, there is a VS V8 5.0L bin.. and that seemed to match up well with what the VS v6 had. Ill have to go double check the VS stuff again.

Its a simple change in the program to direct the VS V8 down the VR routine.. just want to be certain is all!

Posted: **Wed Apr 15, 2015 10:33 pm**

VS V8 Series 3 is much like VT, even though the code is $A6 VS will only work on VS PCM and VT on VT.

pcmhacking.net

ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's

Re: ALDL ECU's