Sorry if this has been answered..
Will there be a problem making changes to a PCM that has already been modified with LS1edit or other software?
Printable View
Sorry if this has been answered..
Will there be a problem making changes to a PCM that has already been modified with LS1edit or other software?
Our product is designed to work with VCM's/PCM's as they come from the factory. We can't gaurantee our product will work on PCM's that have already been modified.
We have demo'd our product at many tunershops though, and we have had no problem re-editing vehicles that have already been modified with the LS1 Edit software.
I hope this answers your question. :)
- Keith
I guess the issue would be if there are changes to
PCM params that "VCM Suite" doesn't read or write.
That, and any kooky OS fiddling. Do other tools do
that?
Does "VCM Suite" do a full memory block read /write
(some tools I think only write back selected params)?
Or are there known "not read" or "not written" PCM
params? If so will they be documented for the users
and/or be added to "coverage" later?
And for the poor bastards who got a mail order tune
that they can't do anything with, can "VCM Suite"
at least do a "stock data file reflash", if not a read /
write of a "locked" program? I can see (barely) the
issues with modifying "protected" programming but
being able to just flush it shouldn't be any kind of
"intellectual property" issue.
The STD version reads the entire flash and writes the calibration section only on multi-segemented (ie 99+) PCMs. The Pro version allows entire flash writing.
As long as the seed/key, VIN #and OS # have not been messed with you will be able to read/write any PCM you have licensed.
It is not possible really to just write the changes back on their own, because the flash chip actually requires you to erase and then rewrite the data. So you can;t just rewrite the data for the Spark table for instance, you have to erase and then reflash the entire CAL section...
The main page of your web site says there is no difference between the two version and in this thread you say they do or can write the PCM differently.
So, are they different (beyond the number of cars they can tune) or are they not?
Thanks.
BB, can you link me to where it says there is no difference in the flasher program? I am unable to find it. If it says such, it is a typo.
I think BB is talking about the order page http://www.hptuners.com/order.php that has the following text:
VCM Suite is split up into 2 main packages. VCM Suite Standard which supports 1-2 vehicles and VCM Suite Pro which supports 3 or more vehicles. There are no differences in the packages other than the number of vehicle types you can reprogram.
Ahh thanks for the heads up. I'll have to fix that.
Quote:
Originally Posted by gameover
OK, I have a question about this bit. I have a spare PCM
that I had the dealer reflash to my VIN. That's what I'm
currently driving around with; the stock PCM is indoors.
So on my in-car PCM, the VIN# has definitely been
"messed with", and I couldn't tell you about the OS
(don't know the original donor vehicle) or the seed/
key stuff.
Predator checks just VIN and works fine with this reflash
PCM. What would the issues be with programming this
PCM vs my stock PCM?
(Hint: right answer = "no problem") ???
Also, does the "no difference between std & Pro except
number of vehicles" really hold true, or is the Data /
Data + OS flashing distinction also there?
If the dealer has reprogrammed your spare PCM to your VIN, not only do they change the VIN but the rewrite the entire VCM/PCM as well so you would have the correct OS ID as well. It wouldn't be an issue.
The standard version allows you to reprogram the calibration section only.. which is your standard programming approach. It doesn't restrict you from any area of modification.
The Pro version allows you to rewrite the entire VCM/PCM including OS.. For example, if you have a 99 Y body PCM with the electronic TB but wish to use the PCM in a 00 F-Car, you can reprogram that PCM with an 00 F-Car binary and now have f-body code that supports the cable throttle.