Gear head efi
Thread Starter
TECH Apprentice
Joined: Sep 2011
Posts: 301
Likes: 5
From: Miami Beach, Florida
Gear head efi Any LT1’ers have a gear head efi account?Reason I ask is I starting data streaming and need an expert that knows what they are talking about.
plus that site keeps saying I do not have permission to access anything.
plus that site keeps saying I do not have permission to access anything.
Thread Starter
TECH Apprentice
Joined: Sep 2011
Posts: 301
Likes: 5
From: Miami Beach, Florida
specific directions on the differences on bin files, xdf, adx, cvs, and ads files and when & how to use them. Plus the appropriate files. Trying to scan, data stream and data log the car. No tuning as of yet. I have tuner pro RT & eehack. Tuner pro’s website and a couple threads on here are someone helpful but I need dummied down info. Eehack has basically no directions on their site.
plus I’m a long time Mac user & comfortable with Mac. Bought a windows 10 laptop just for the scanning & tuning purposes.
plus I’m a long time Mac user & comfortable with Mac. Bought a windows 10 laptop just for the scanning & tuning purposes.
You may need to have your account over there approved/ unlocked for first use. Been a long time since I joined over there but message an admin if all else fails. There are a couple of dynamite threads on EEHack and FlashHack and the accompanying XDF file, all written by the same guy, Steve Haslin.
BIN = the tune file itself. 128kb of hexadecimal data for an OBD I LT1 PCM. Hexadecimal means 16 characters: 0 1 2 3 4 5 6 7 8 9 a b c d e f Hexadecimal explained
XDF = a BIN definition file that translates hex data into tables. Changing a value in TunerPro writes modified hexadecimal back to the BIN file when you save the change and then save the BIN.
ADX = a definition file for datalogging. Select > ADX > log > save log > view log > get insight
CSV = Comma Separated Values (file). Raw sort of spreadsheet with values literally separated by commas. Excel shows it in cells. Notepad would show you the commas if you opened such a file in Notepad.
ADS = older datastream (logging) definition file.
Use EEHack to acquire the BIN file from the PCM. If you can do Mac, you can navigate the menu. FlashHack is the newer tool that handles the reading and flashing after changes are made to the BIN. Flash functionality was removed from EEHack. EEHack is also a great logging tool. Scan94-95 is a nifty real-time 'what's going on' tool for quick visual insight into your running vehicle.
Use the EEX XDF definition file for TunerPro. Current version is 4.1 I think. Each parameter has a comment above it when you hover, explaining to some degree what each is for. Tables, constants, flags (and patches) in the case of EEX.
BIN = the tune file itself. 128kb of hexadecimal data for an OBD I LT1 PCM. Hexadecimal means 16 characters: 0 1 2 3 4 5 6 7 8 9 a b c d e f Hexadecimal explained
XDF = a BIN definition file that translates hex data into tables. Changing a value in TunerPro writes modified hexadecimal back to the BIN file when you save the change and then save the BIN.
ADX = a definition file for datalogging. Select > ADX > log > save log > view log > get insight
CSV = Comma Separated Values (file). Raw sort of spreadsheet with values literally separated by commas. Excel shows it in cells. Notepad would show you the commas if you opened such a file in Notepad.
ADS = older datastream (logging) definition file.
Use EEHack to acquire the BIN file from the PCM. If you can do Mac, you can navigate the menu. FlashHack is the newer tool that handles the reading and flashing after changes are made to the BIN. Flash functionality was removed from EEHack. EEHack is also a great logging tool. Scan94-95 is a nifty real-time 'what's going on' tool for quick visual insight into your running vehicle.
Use the EEX XDF definition file for TunerPro. Current version is 4.1 I think. Each parameter has a comment above it when you hover, explaining to some degree what each is for. Tables, constants, flags (and patches) in the case of EEX.
