Originally Posted by
kur4o
After 6 months of silence, I thought this project was dead, . Or mutated to a commercial release.
And now it exploads. You should have gotten some strong motivation to finish the job.
I read about that checksum issue you had, and it got me a little worried, how stable is the whole thing.
I hope you know what your doing and the final product be worry free.
Is there anytime soon a OS change option added. That is what matters most, since dimented tool can do a cal data write already.
Do you have any plans to make the tool complete with some datalogging and realtime control. Analizing the trim logs will be nice addition.
Some guys here have huge experience with similar products for earlier GM controllers and can be of big help to you.
I also ripped the GM block logging, modes 3A and 3B, and realtime control Mode AE. This works a lot faster than any of the available logging tools available now.
Keep up the good work and get for the community a nice and useful tool.
The project was never dead, we just had other things come up in our lives that took up too much of our time. All of us are doing this in our free time, so when we don't have free time, we don't have progress.
The checksum issue was a problem with the XDF that I was using, not with PCM Hammer itself. The contents of my .bin file were written to the PCM correctly!
I think the app is good, but the only way to know that it is good is to have a lot of people try it, and prove that it is good. As we have more proof, we can all have more confidence in it.
We also want to add some features to the app to prevent users from making mistakes, like mixing incompatible files, or flashing when the voltage is too low.
It is good enough to use it to reflash PCMs that are on a workbench. Those of us who are working on the app have done that a lot.
It is good enough to use it on a car that isn't one that you need to get to work, or to get groceries. I got that confidence after successfully flashing my car three times.
When we have a LOT more reports of successful in-car flashes, that will give me the confidence to recommend using it more widely. That will also give me the confidence to add support for OS flashing. It will require only tiny changes to the code. I just don't want to make those changes until I have more confidence. Recovering from a bad calibration or checksum flash is relatively easy, but recovering from a bad OS flash is hard.
Bookmarks