New flash tool

I was never totally happy with EEHack’s built in flash tool so I’ve been spending a lot of time working on a new one.  If you have an LT1 check it out.  It’ll support other ECMs some time this decade.

12 thoughts on “New flash tool”

  1. Do you have any recommendations on cables? Best vendors, what to look for etc? I have an OBD1 cable from many years ago from but was told by PCMperformance that it’s only a data cable. It will connect to $EEhack to monitor but will not show pull anything up in Flashhack or TunerPro to collect a base bin file.
    I’m currently waiting on another a new one from them that they make in house. Been scouring looking for them but just not much info on what works (and why) and what doesn’t.


    • there is no such thing as ‘only a data cable’

      you should ignore any advice regarding cables from the people that told you that

      the communications necessary to get engine data of any kind, reset codes, or reflash the ecm are exactly the same as far as the cable is concerned

      a cable that can datalog should also be able to reflash or do anything else my software does

  2. I am getting help with writing tunes for my 97 SS. I changed the OBD2 to a OBD1. I was told to use the flashhack to read calibration for the stock tunes. I went through the process and it pulled 64.0 KB. I was told it needed to be 128 KB. I’m not sure why it was only pulling the 64 KB. Any advice on this issue?

  3. Thank you for your quick response. I do not know much about this stuff-So bear with me. TunerCat is for tuning and not data logging. DataCat is for logging. DataCat uses a .dcf file and TunerCat uses a .bin file Can these be changed to work with Trimalyzer. Thank you!

Leave a Comment