• The site migration is complete! Hopefully everything transferred properly from the multiple decades old software we were using before. If you notice any issues please let me know, thanks! Also, I'm still working on things like chatbox, etc so hopefully those will be working in the next week or two.

.HPT to BIN

flash it then as is, dont add your tune to it.

then read it with the new 3.0 software, it should be able to be worked on then for sure id think.

once that file is changed its changed forever so once its flashed, and re read, its there already changed forever.
 


Scottydoggs said:
flash it then as is, dont add your tune to it.

then read it with the new 3.0 software, it should be able to be worked on then for sure id think.

once that file is changed its changed forever so once its flashed, and re read, its there already changed forever.
Click to expand...


Thats what I was thinking too, I tried that and 1. car wont even start with the tune 2. I cant open it with 3.0 3. had to rewrite it with my old tune just for it to start.
 
Im going to try to start over again with stock bin and change serial and vin, hopefully I just fat fingered somewhere. Even tho I dont understand why the older HPT would still open it. Taking any suggestions lol
 


if theres a older version of htp in db try that one out. flash with that bin, if the car fires up it should read with the newest hp format.
 
It has something to do with tinytuner modifying the file. I rewrote the vin and serial tried a file with the cat tuning on and one where i didn't touch with tiny tuner. The stock file i rewrote and converted from bin to hpt loads just fine in 3.2 where the identical file with cat testing off throws this error. Making less and less sense as I go.... :th_scratchhead:
 
for fun, why i dont i send you a bin file. and try mine, maybe it has something to do with it being opened in dhp again that fixes the checksum issue.
 


Another thing I dont understand, when I changed the value of the checksum in TT it always reverted to something that looked like "7.793448E+08" when first opened the value is "255". Im pretty HPT will not work from a bin/hpt that has already been altered by other software and this checksum in TT is its way of knowing. Or at least the updated HTP
 
Tried again today, same results but I found after I flash the new bin to the pcm durring the no start condition im throwing a P0601 code - P0601 Chevrolet
P0601 CHEVROLET - Power Control Module Internal Fault

Anyone else ever ran into this problem?

Read more at: http://www.engine-codes.com/p0601_chevrolet.html
Internal Control Module Memory Check Sum Error

Read more at: http://www.obd-codes.com/p0601
Copyright OBD-Codes.com
Internal Control Module Memory Check Sum Error

Read more at: http://www.obd-codes.com/p0601
Copyright OBD-Codes.com
 


brick aroo.

pretty sure i got a 02 pcm sitting here. if you email me one of the bins with the vin changed i can see if dhp will flash it and keep the vin right.

ill let it go pretty cheap too. seems no one wants a 01-02 pcm these days lol
 
If I flash it with my old tune, one I didnt touch with TT it fires right up and no P0601. That still mean it could be bricked? I thought thats for non recoverable pcms.
 
its a checksum error, so maybe it just dont like the tt bin being flashed.

if it started up with no cel. id think your good to go still.

if it comes to it, i got this pcm here. i can kill the cat test, try to get it to take your vin right, 01 up seem to fight a vin change, but if the bin has the right vin it should take fine.

once you got it you read it with htp and you have your new file to work on in hpt.
 
You must log in or register to reply here.
Back
Top