vcm 3.0 how to change vin in new software?

[energetic motorsports]

I was wondering if there is a way to change vin in new software?

[CCrunner84]

They haven't added it to 3.0 yet, it's hopefully on the todo.

[Bill@HPTuners]

Likely won't make 3.0, probably 3.4 or later, the problem is the vin change feature only works on about 5% of the vehicles we support so support receives alot of emails asking why the vin change feature doesn't work on ford or dodge or oddball gm's where it just doesn't work on.

[The Alchemist]

So would I in the future be able to put my correct VIN into my 2000 Fbody while running a 3-bar OS from a 2002 fbody?

[La RPM]

So would I in the future be able to put my correct VIN into my 2000 Fbody while running a 3-bar OS from a 2002 fbody?

This would be awesome.

[Frost]

Likely won't make 3.0, probably 3.4 or later, the problem is the vin change feature only works on about 5% of the vehicles we support so support receives alot of emails asking why the vin change feature doesn't work on ford or dodge or oddball gm's where it just doesn't work on.

Have to maintain multiple version installs though over something that is perceived as small. Many people use that feature daily for the platforms that it did/does work for.

[LSxpwrdZ]

Have to maintain multiple version installs though over something that is perceived as small. Many people use that feature daily for the platforms that it did/does work for.

I agree. The licensing on 3.0 is still dicey on Gen3 GM applications as well. I have multiple customers that I've emailed tune files to that prompt to re-license now due to the OS or VIN changing even though the VCM ID is still clearly the same which is ALL that 2.24 used to license a Gen3 application to.

[Keith@HPTuners]

A few people have e-mailed us regarding 2.24/3.0 licensing, and have ultimately exposed a few bugs in the 2.24 licensing system. My guess is these people have changed their VIN using a 3rd party tool.

The 3.0 licensing issues that exist now are for VIN's that are incorrectly identified, or are not being grouped with a vehicle type that they should be grouped with.

[GHuggins]

So how would one fix this?

[Keith@HPTuners]

Fix what?

[LSxpwrdZ]

A few people have e-mailed us regarding 2.24/3.0 licensing, and have ultimately exposed a few bugs in the 2.24 licensing system. My guess is these people have changed their VIN using a 3rd party tool.

The 3.0 licensing issues that exist now are for VIN's that are incorrectly identified, or are not being grouped with a vehicle type that they should be grouped with.

So is licensing fixed for 3.0 to match how it was in 2.24?