Why I hate VZ V6 ECUs...

[mattyjf01]

Probably the ones you are saying are dead or no comms are what im refering to (Maybe)

[jxx]

Simple test for no comms, no start.... basically any issue with the damn things, pour boiling water over the ecu and 99% of the time they come back long enough to communicate/do something/start/stop missfiring, sending the dash haywire.......

[jxx]

Seems everyone hates these ecu's, even scantool companies.

Latest snap-on release won't link them, worked on previous versions and hopefully issue fixed by next update.

[Tazzi]

Its only taken 4 years for me to come back to the VZ V6 engine computers, and you know what, I still hate them

But, at least there is now a better solution to keep them moving for replacement ECUs.

I have had several workshops complaining the VZs being unavailable for flashing with GMs online system, so I made it a priority to add it into the new program I have been working on instead of having them sent in for flashing.

No more techline, just need a security code (Which can be read from a PIM using an eeprom programmer, or the original ECU), and a few minutes to flash them.

[Holden202T]

thats a good win!

[VX L67 Getrag]

FERMEC tool for the win, I use it just copy security data off orig & reset replacement ecu & then paste security data & done!

[Tazzi]

Yeah thats one way of doing them!

I tend to see alot of no communication ECUs, so you can't extract the original security information to put into a replacement.

The PIM is pretty simple to remove and read the eeprom to get the factory immobilizer code. Then its a 1 click process to reset and security link in the new application.

[The1]

Well done mate, that's a fancy program! Just need vats off now, im sure it'd be in the BDM read somewhere.