Insite 8.7 and newer incal problem?

[68shifter]

Hello. I have Insite V8.7 and about a month ago my old incals stopped working. From my understanding something with the date/outdate. I installed the new ones but they only work with 8.8 I was hoping someone may have a work around, or old files I could purchase/reload etc.

Insite came pre-loaded on my laptop and the company I bought from has been less than helpful with this. Thanks

[Rawze]

I got tired of the Insite bulls$it of 'file has expired' crap, and it deleting files on you years ago....

I have not used Insite to flash Incal(factory calibration) files for many years now.

Here is the process that I use when I need to flash a factory file into an ECM ...

== I ALWAYS make a full back up of the old program with the Calterm software, just for reference and if anything goes wrong, etc. so that the ecm can always be brought back to that point no matter what. I do this even if its the wrong program.. or a bad delete... does not matter. I ALWAYS ALWAYS make a full backup FIRST before making any changes to that ecm.

== Next ... Note the engine ser# and the vin#. Copy-paste them into a notepad text document temporarily or take pic of them.. something. You will need them at the very end.

== I use the Insite software to make a work order, and then a template. This backs up essentially only the vehicle-specific settings like odo history, trip info, cruise control buttons/ engine brake buttons, and other vehicle specific / dash network addresses. I.E.> An 'ecm template' in Insite backs up all the important stuffs for only the vehicle itself. These settings will NOT be contained in a newer/factory/incal file. if you don;t back them up separately, they will all get lost.

== I then de-compress the incal/new factory file with 7-zip (using the proper password) and then flash the new file in with the Calterm software. CT does not care how 'old', new, etc. the file is or anything else. It simply will flash any file you throw at it into the ecm without question. This way I can put in a file from most recent, or a file from 10 years ago if I want to. No mussy-fussy.
NOTE: I do NOT check those 2 little check-boxes to save-restore parameters, etc. ... because Calterm is horrible at this, and this can corrupt the file.

== After flashing the new file in with CT, I then switch back to Insite and restore the work order/template. This restores all of the vehicle specific settings, odo, trip history, button addresses, etc.

== What does NOT however get transferred when doing things this way is that the engine ser# and the vehicle vin# are not restored. Those 2 things, you have to type back in via Insite software by hand, or (copy-paste, if you had saved them in a note-pad text), once your all done .. and then and save changes.


NOTE: Factory calibrations (Incal fales) will run a special code the first time the ecm is run to clear out old memory, etc... so I run/idle the engine for 10+ minutes so that it can do this in the background uninterrupted, and do its initial data erase/collection etc. in the background. It gives time for everything in the programming to establish itself and settle. It takes up to about 8 minutes, so I give it 10.

== I then take a second ecm back-up of the now established, and fully completed new program using the CT software. This is so that I don't have to go thru the flashing process again if I ever want to restore this program in the future. I can also make copies of this new backup to edit, or do whatever I want to it later on.

- That is how I have done it for 10+ years now and have never had any issues.

here it is explained again in a slightly different way: https://rawze.com/forums/showthread.php?...1#pid80171

[Bengy88]

Yup I do it the same way Rawze does.

Nope, the newest incals won’t work with 8.7 at all. Someone can alternatively step back to the June 2023 incal disc, and with the proper date changes, the date of the incals, and they will then work with 8.7 again.

It is recommended to always try to use the latest incal tho, to keep the engine software as up to date/bug free as possible instead of doing things this way too much.

[Lunchtime92]

(01-04-2024 )Rawze Wrote:  I got tired of the Insite bulls$it of 'file has expired' crap, and it deleting files on you years ago....

I have not used Insite to flash Incal(factory calibration) files for many years now.

Here is the process that I use when I need to flash a factory file into an ECM ...

== I ALWAYS make a full back up of the old program with the Calterm software, just for reference and if anything goes wrong, etc. so that the ecm can always be brought back to that point no matter what. I do this even if its the wrong program.. or a bad delete... does not matter. I ALWAYS ALWAYS make a full backup FIRST before making any changes to that ecm.

== Next ... Note the engine ser# and the vin#. Copy-paste them into a notepad text document temporarily or take pic of them.. something. You will need them at the very end.

== I use the Insite software to make a work order, and then a template. This backs up essentially only the vehicle-specific settings like odo history, trip info, cruise control buttons/ engine brake buttons, and other vehicle specific / dash network addresses. I.E.> An 'ecm template' in Insite backs up all the important stuffs for only the vehicle itself. These settings will NOT be contained in a newer/factory/incal file. if you don;t back them up separately, they will all get lost.

== I then de-compress the incal/new factory file with 7-zip (using the proper password) and then flash the new file in with the Calterm software. CT does not care how 'old', new, etc. the file is or anything else. It simply will flash any file you throw at it into the ecm without question. This way I can put in a file from most recent, or a file from 10 years ago if I want to. No mussy-fussy.
NOTE: I do NOT check those 2 little check-boxes to save-restore parameters, etc. ... because Calterm is horrible at this, and this can corrupt the file.

== After flashing the new file in with CT, I then switch back to Insite and restore the work order/template. This restores all of the vehicle specific settings, odo, trip history, button addresses, etc.

== What does NOT however get transferred when doing things this way is that the engine ser# and the vehicle vin# are not restored. Those 2 things, you have to type back in via Insite software by hand, or (copy-paste, if you had saved them in a note-pad text), once your all done .. and then and save changes.


NOTE: Factory calibrations (Incal fales) will run a special code the first time the ecm is run to clear out old memory, etc... so I run/idle the engine for 10+ minutes so that it can do this in the background uninterrupted, and do its initial data erase/collection etc. in the background. It gives time for everything in the programming to establish itself and settle. It takes up to about 8 minutes, so I give it 10.

== I then take a second ecm back-up of the now established, and fully completed new program using the CT software. This is so that I don't have to go thru the flashing process again if I ever want to restore this program in the future. I can also make copies of this new backup to edit, or do whatever I want to it later on.

- That is how I have done it for 10+ years now and have never had any issues.

here it is explained again in a slightly different way: https://rawze.com/forums/showthread.php?...1#pid80171

Where does someone get the (proper password) in order to decompress these incal files using 7zip??

[Colter]

Another thing just to mention in regards to Insite 8.7 is it will not connect to the new X15 2450E which are in the 2025 and some late model 2024 trucks. (Another annoyance is Paccar products (KW/Pete) as of 2023 require Davie4 for all chassis diag/functions)

If you have the ability to have a second laptop with Insite 8.9/9.0 you can use that for all factory flashes/updates and then pull your file as per Rawze's procedure. There are also method's for using new Incals in 8.7 but if you need to hook up to a new truck it won't do it.

This software compatibility issue is getting worse and worse and costs for maintaining up to date software in a shop setting is getting higher and higher, which ultimately means the cost gets passed on or the shops ability decreases

[Rawze]

(09-08-2024 )Lunchtime92 Wrote:  ...
Where does someone get the (proper pw) in order to decompress these incal files using 7zip??

stuff like that are discussed on my mumble forum.
ref: https://rawze.com/forums/showthread.php?...63#pid2163