Results 1 to 5 of 5

Thread: Standard Exchange Format

  1. #1
    Senior Tuner
    Join Date
    Nov 2002
    Location
    Central Florida
    Posts
    2,503

    Standard Exchange Format

    Would really like to see HPTuners come out with some
    means of cross-platform (but same powerplant) .bin
    sharing. Because we can't read different-year, model
    .bins there is a real impediment to tune-sharing. If the
    data were exported to a "standard cal database" form
    and importable from same, something divorced from
    the lower-level details of PCM organization / segmenting
    or whatever, that would really be spiffy. And if this
    database happened to be Excel based, one worksheet
    per editor tab or whatever, that would be spiffy with
    extra cheese. But some sort of cal-data-only meta-file
    that would let the 'Vette guys "talk to" the F-body guys,
    etc.

    Seems like this would be doable and a real bonus to the
    user community. The import/export would be unique to
    vehicle type or group but I reckon you guys have the
    map already and it's mostly the grunt detail work of
    export and import "macros" after defining the superset
    database.

  2. #2

    Re: Standard Exchange Format

    Quote Originally Posted by jimmyblue
    Would really like to see HPTuners come out with some
    means of cross-platform (but same powerplant) .bin
    sharing. Because we can't read different-year, model
    .bins there is a real impediment to tune-sharing. If the
    data were exported to a "standard cal database" form
    and importable from same, something divorced from
    the lower-level details of PCM organization / segmenting
    or whatever, that would really be spiffy. And if this
    database happened to be Excel based, one worksheet
    per editor tab or whatever, that would be spiffy with
    extra cheese. But some sort of cal-data-only meta-file
    that would let the 'Vette guys "talk to" the F-body guys,
    etc.

    Seems like this would be doable and a real bonus to the
    user community. The import/export would be unique to
    vehicle type or group but I reckon you guys have the
    map already and it's mostly the grunt detail work of
    export and import "macros" after defining the superset
    database.
    I agree. This would help tremendously.

  3. #3
    Advanced Tuner Screamn03's Avatar
    Join Date
    Feb 2004
    Location
    Vacaville, CA
    Posts
    832

    Re: Standard Exchange Format

    I agree. This would help tremendously.
    TTT
    -Michael Rudolph-
    2003 Redfire Cobra
    Eaton Powered to a:
    11.301 @ 129 1.68 60' MT DRs
    11.85 @ 124 1.90 60' street tires

  4. #4
    Advanced Tuner
    Join Date
    Apr 2004
    Location
    Bakersfield, CA
    Posts
    592

    Re: Standard Exchange Format

    While I agree it would be cool to be able to read other bin files, does LS1Edit let you read bin files other than your own? If not, at least we have the ability to share tunes across a whole model year instead of being locked to our own bin file. We have it so much better than the Edit people it's sick.
    Eric - 01 Silverado 5.3 ECSB
    ET: [email protected] 1.77 60' 5200 lbs

    Crappy website about my truck

    My Myspace page
    Usually contains explicit material (language, etc..)
    It's Peanut Butter Jelly Time!

  5. #5
    Advanced Tuner Screamn03's Avatar
    Join Date
    Feb 2004
    Location
    Vacaville, CA
    Posts
    832

    Re: Standard Exchange Format

    We have it so much better than the Edit people it's sick.
    -Michael Rudolph-
    2003 Redfire Cobra
    Eaton Powered to a:
    11.301 @ 129 1.68 60' MT DRs
    11.85 @ 124 1.90 60' street tires