pcmhacking.net

antus wrote:The protection is optional, but a lot of tuners think they need to protect their tunes. some because they are worried about people copying the tune, some because they are rubbish tunes and dont want to be caught out.

Oh right, I thought this was manafacturer protection.

antus wrote:The protection is optional, but a lot of tuners think they need to protect their tunes. some because they are worried about people copying the tune, some because they are rubbish tunes and dont want to be caught out.

Ahahahahahahhahahahahhahahahaahhaha... the last one.. the last one..!

Tazzi wrote:

antus wrote:The protection is optional, but a lot of tuners think they need to protect their tunes. some because they are worried about people copying the tune, some because they are rubbish tunes and dont want to be caught out.

Ahahahahahahhahahahahhahahahaahhaha... the last one.. the last one..!

You should see some of the shit people pay big bucks for. Guess work at best!

Back on the subject of vin changing, I found a BA that had no VIN today & everything was communicating happily supposedly but it had fan running constantly so I thought I'd better cross all bases & tried applying the VIN to ecm & had the checksum error E1639 for VID.

So I spent way TOO long trying to correct the sum myself with advice from rolls all to no avail, so I knew HPT 2.24 could write VIN but it said the OS was incompatible with VIN so the file I wrote to controller with incorrect checksum with rolls's tool when I read it back with HPT 2.24 it asked to correct it(warning it may not be correct) so I said yes & BINGO it had the right checksum & wrote that back & all was good in the world! But HPT 2.25 onwards didn't pick up there was a checksum error with that block!

VX L67 Getrag wrote:Back on the subject of vin changing, I found a BA that had no VIN today & everything was communicating happily supposedly but it had fan running constantly so I thought I'd better cross all bases & tried applying the VIN to ecm & had the checksum error E1639 for VID.

So I spent way TOO long trying to correct the sum myself with advice from rolls all to no avail, so I knew HPT 2.24 could write VIN but it said the OS was incompatible with VIN so the file I wrote to controller with incorrect checksum with rolls's tool when I read it back with HPT 2.24 it asked to correct it(warning it may not be correct) so I said yes & BINGO it had the right checksum & wrote that back & all was good in the world! But HPT 2.25 onwards didn't pick up there was a checksum error with that block!

That method has not yet worked for FG ECUs for me yet, for the BA 3.2HPT wants to em write the vin to the ECU before you even get to read the file if the checksum is not correct. 2.24 won't read all BA ECUs operating systems tho I have a Territory one here that 2.24 won't touch, 3.2 will if you manually select the ECU type. Have you had the vin change with HP work it's never allowed me?

Couple of files

Interesting ecu read on the FG no vin located
FG Auto a friend purchased it from evilbay wonder if someone else has written to it, or it was a dealership ecu replacement or something

APS-234 Turbo 6 spd
https://www.dropbox.com/s/9vfx4aw5rlhsd ... n.bin?dl=0

and this is a 6 spd BF
ASU-221
https://www.dropbox.com/s/63f1nlkcy29sf ... o.bin?dl=0

Probably a ford spare part. Pretty sure they have a blank vim

Yeah I think that's what had happened with the ba I had in yesterday or more so I think they flash updated it with blank vin, not sure why all the other modules didn't have communication issues as normally if the vin doesn't marry they won't all work together!

VX L67 Getrag wrote:Yeah I think that's what had happened with the ba I had in yesterday or more so I think they flash updated it with blank vin, not sure why all the other modules didn't have communication issues as normally if the vin doesn't marry they won't all work together!

Maybe someone already did the PATS disable procedure? I think there is an official pats disable that will make it work.

PtDiag has some interesting functions regarding that stuff

In case anyone was wondering this is how you remove the case on your PCM. FYI it is not going back on once you take it off lol. Bent the fuck out of it with a screwdriver. I think if you used a heat gun you could possibly melt the high temp glue off and remove it with a knife without damaging it if you were so inclined.