Hi members,
I wanted to ask if anyone else is experiencing the same issues we're having with our KESS3.
Our shop uses Autotuner, Flex, and KESS3. About four months ago, we decided to add the bench/boot protocol to our KESS3 since this tool is primarily used for onsite work.
However, we're now encountering problems when trying to read a "modified" ECU. Even if the modification is as simple as a DTC delete done with our own tool (flex or at), the process ends with a checksum error. Alternatively, we sometimes receive a "file integrity check fail -1" error.
Whenever this happens, we need to open a ticket with support to correct the checksums and provide us with an original file for comparison. Unfortunately, support has been of little help, as they continually push us to purchase the Online Backup Manager.
We're now considering selling the tool altogether because the company has become increasingly focused on monetization in recent years.
Has anyone else faced similar issues when reading a modified ECU with Kess3?
Bookmarks