ALDL ECU's

[Tazzi]

Your assuming the scrolly bar is working correctly haha. Iv got to sort out a few little bugs first. But.. I think I should be able to add something like that in easy enough. Just need to do a:
if scroller.location = scroller.max
AutoScroll = true
else
AutoScroll = false
endif

[Tazzi]

Went for a good 15min drive, works like a charm! Can save and reload sessions happily!

Good to watch it on the graph view and see how it all changes.

[Tre-Cool]

slightly off topic, but does anyone know if it's possible to reprogram a vt-vx pim to a vy? I have a bunch of vx ones but I need them to talk to vy dashes.

part numbers are different but I would think the underlying eeprom is the only thing that changes?

[Tazzi]

slightly off topic, but does anyone know if it's possible to reprogram a vt-vx pim to a vy? I have a bunch of vx ones but I need them to talk to vy dashes.

part numbers are different but I would think the underlying eeprom is the only thing that changes?

Not that I know of. To be honest, I thought the PIMs were interchangeable? Didnt realise they were not.
What happens when you install a VT-VX PIM into a VY?

What sort of errors pop up? Have you chucked an ALDL cable onto the OBD2 port to see the 'difference' between when either a VT-VX pim is installed to a VY?
Same goes for an ELM cable.. tried popping one of those on as well and try monitoring the chatter over VPW (LS1 protocol) and see what the difference is.

I doubt simply changing the eeprom will be enough, its probably a matter of they have completely different firmwares, which only 'expect' to see certain data.

From what I understand.. the PIM works like this:
ALDL Data <-> PIM <-> ECU (Engine Data)

And the data is changed back and forth between them. So I would say.. using a different PIM, means the PIM might actually send the 'converted' data slightly different. I know that a VY dash cannot work happily in a VT/VX as the ALDL comms is different which sets off alarms.

[Tre-Cool]

well the os/calibration on the ecu doesn't seem to make any difference with any bcm, but if you use a vt-vx pim with a vy dash you get errors for stuff that isn't even plugged in on the bcm.

put a vy pim in and the problem disappears.

im basically using the bcm's as an interface to the dash clusters for ect, tacho & vss.

[Tazzi]

well the os/calibration on the ecu doesn't seem to make any difference with any bcm, but if you use a vt-vx pim with a vy dash you get errors for stuff that isn't even plugged in on the bcm.

put a vy pim in and the problem disappears.

im basically using the bcm's as an interface to the dash clusters for ect, tacho & vss.

Alright then it would be what I said. The vt/vx PIM do not convert the data OBD2 data to ALDL the same. The cluster then doesnt understand what is being sent over ALDL.

When I mimic my cars communication to the cluster outside of the car, it works without any errors
So It has to be how the PIM is converting the data across. Would be able to identify the difference between the two devices by logging them

Cant imagine there really is a way to fix this, apart from maybe building your own 'middleman' between the PIM and cluster to convert the vt-vx data to the vy equivalent?

[Tazzi]

; -------------------------------------------------
; -- Logged If CTS, MAT, VATS or Ref Pulse Fault --
; -------------------------------------------------
L8AE8: .word L01D4 ; CTS - CTS A/D
.word L00AB ; Battery A/D Voltage
.word L01D9 ; MAT - MAT A/D value
.word L0327 ; KPH - Road Speed for Fault Analysis

; -------------------------------
; -- Logged If O2 Sensor Fault --
; -------------------------------
L8AF0: .word L032A ; O2 - o2 A/D for Fault Analysis
.word L02BE ; C/L - Current BLM
.word L02BA ; C/L - Current INT
.word L0329 ; TPS - TPS A/D for Fault Analysis

; ---------------------------------------------------------
; -- Logged If TPS, MAP, PROM, Batt Voltage or A/D Fault --
; ---------------------------------------------------------
L8AF8: .word L0329 ; TPS - TPS A/D for Fault Analysis
.word L0328 ; MAP - MAP A/D for Fault Analysis
.word L00AB ; Battery A/D Voltage
.word L02BE ; C/L - Current BLM

; ----------------------------------------
; -- Logged If IAC Fault or Vacuum Leak --
; ----------------------------------------
L8B00: .word L0329 ; TPS - TPS A/D for Fault Analysis
.word L02CE ; IAC - Requested IAC Position
.word L0371 ; IAC - Current IAC position
.word L0059 ; Flags...
; Bit 0 1 = Idle Run-Away Flag, Set If Idle RPM Exceeds Desired and Upper Threshold
; Bit 0 1 = Torque Management, gets set when trans is shifted into Drive
; Bit 0 2 = Trans in Park or Neutral when set
; Bit 0 3 = Stall Recovery Mode
; Bit 4 1 = Waiting For IAC Motor To Reset
; Bit 5 1 = A/C Status Change Bit
; Bit 6 1 = Throttle Crack Flag
; Bit 7 1 = Closed Loop Idle Control (Closed Throttle)

; ----------------------------------------------------
; -- Logged If EST, Bypass Or Fuel Starvation Fault --
; ----------------------------------------------------
L8B08: .word L0327 ; KPH - Road Speed for Fault Analysis
.word L005A ; EST Flags
.word L0328 ; MAP - MAP A/D for Fault Analysis
.word L032A ; O2 - o2 A/D for Fault Analysis

; --------------------------------------------------
; -- Logged If Speed Sensor Or Knock Sensor Fault --
; --------------------------------------------------
L8B10: .word L0328 ; MAP - MAP A/D for Fault Analysis
.word L0327 ; KPH - Road Speed for Fault Analysis
.word L01D4 ; CTS - CTS A/D
.word L01D9 ; MAT - MAT A/D value

L8B18: .word L02D4 ; Sync - Cylinder # Counter
.word L01D4 ; CTS A/D Voltage
.word L0327 ; KPH - Road Speed for Fault Analysis
.word L00AB ; Battery A/D Voltage

L8B20: .word L00AB ; Battery A/D Voltage
.word L00AB ; Battery A/D Voltage
.word L01DC ; A/D reference voltage
.word L01DB ; Injector voltage

L8B28: .word L01D4 ; CTS A/D Voltage
.word L00A4 ; PRNDL flags
.word L0327 ; KPH - Road Speed for Fault Analysis
.word L00D9 ; Requested gear

L8B30: .word L0328 ; MAP A/D for Fault Analysis
.word L0327 ; KPH - Road Speed for Fault Analysis
.word L00A7 ; Trans Temp A/D
.word L00D9 ; Requested gear

L8B38: .word L00A0 ; Status Word 5
.word L00D9 ; Requested gear
.word L008C ; TCC Mode Word Flags
.word L008B ; 3-2 Downshift Flag Word

L8B40: .word L00D9 ; Requested gear
.word L0327 ; KPH - Road Speed for Fault Analysis
.word L032C ; Filtered Transmission Slip x4 For Fault Analysis
.word L0329 ; TPS - TPS A/D for Fault Analysis

L8B48: .word L00A1 ; Shift Pattern Word
.word L00D9 ; Requested gear
.word L032D ; Commanded Force Motor Current
.word L032E ; Average Force Motor Current

L8B50: .word L037F ; 1-2 pressure ADAPT
.word L0390 ; 2-3 pressure ADAPT
.word L03A1 ; 3-4 pressure ADAPT
.word L00DC ; Time Of Latest Shift

; ------------------------------
; -- Logged If Engine Stalled --
; ------------------------------
L8B58: .word L0327 ; KPH - Road Speed for Fault Analysis
.word L0329 ; TPS - TPS A/D for Fault Analysis
.word L0371 ; IAC - Current IAC position
.word L0059 ; Flags...
; Bit 0 1 = Idle Run-Away Flag, Set If Idle RPM Exceeds Desired and Upper Threshold
; Bit 0 1 = Torque Management, gets set when trans is shifted into Drive
; Bit 0 2 = Trans in Park or Neutral when set
; Bit 0 3 = Stall Recovery Mode
; Bit 4 1 = Waiting For IAC Motor To Reset
; Bit 5 1 = A/C Status Change Bit
; Bit 6 1 = Throttle Crack Flag
; Bit 7 1 = Closed Loop Idle Control (Closed Throttle)

[/code]

Just realized that the freeze dtc tables on the VR dont match that of the newer models.
Need to map out which fault codes go to which table. From what I see theres about 15 tables I think.

The routine has been coded up, just need to enter the corresponding table for each fault code. And a simple lookup table to return the freeze data.

[VL400]

So It has to be how the PIM is converting the data across. Would be able to identify the difference between the two devices by logging them

Cant imagine there really is a way to fix this, apart from maybe building your own 'middleman' between the PIM and cluster to convert the vt-vx data to the vy equivalent?

Yeah the data stream is different, VY added an extra byte before the payload data to define how many bytes there are in the frame. A few other changes, but that one byte offset is why it sends everything wacky.

[Tazzi]

All done!

Iv double checked all the calcs, and checked all the graphs load correctly and also replay data. Now all I need is people willing to try it out

[0081(2)]

I have a VY V6 with a l67 conversion running the flash PCM and happy to help with testing if needed