Results 1 to 2 of 2

Thread: VE Low Altd Table

  1. #1
    Potential Tuner thahemp's Avatar
    Join Date
    Jan 2014
    Location
    Derby, KS
    Posts
    6

    VE Low Altd Table

    In everything I have read about SD tuning the E38, the VE low altd table is always RPM vs. MAP. Is there something I missed? Mine is RPM vs. TPS. I'm going to switch to EQ<>VE 4 and use it to modify the data directly. I took a first stab using Bluetorp's method, which is to create the VE table with EQ<>VE, then import it into the low altd table for manipulating. I ended up with a stumble in 4th gear with TPS > 50% around 2000RPM. I think it's because the TPS columns don't match the MAP columns that the table was created for?

    Here is what my low altd table looks like. What am I missing here?

    lowaltd.png
    01000111011011110110111101100100001000000110110001 11010101100011011010110010000001110111011010010111 01000110100000100000011101000110100001101001011100 110010000001101111011011100110010100100001

    x = ac97968bd3df8f968c8cd3df998a9c94d3df9c8a918bd3df9c 909c94df8c8a9c949a8dd3df92908b979a8ddf998a9c949a8d d3df8b968b8cd1
    x = ~x

  2. #2
    Potential Tuner thahemp's Avatar
    Join Date
    Jan 2014
    Location
    Derby, KS
    Posts
    6
    Nevermind I figured it out. You can't use HPT to massage the virtual table from EQ<>VE if you have an E38 tune open. I had to open up the E40 sample tune and use the low altd table from there to do my editing and smoothing.
    01000111011011110110111101100100001000000110110001 11010101100011011010110010000001110111011010010111 01000110100000100000011101000110100001101001011100 110010000001101111011011100110010100100001

    x = ac97968bd3df8f968c8cd3df998a9c94d3df9c8a918bd3df9c 909c94df8c8a9c949a8dd3df92908b979a8ddf998a9c949a8d d3df8b968b8cd1
    x = ~x