VE table display in RT Tuner vs. Tuner Pro
Thread Starter
TGO Supporter
iTrader: (2)
Joined: Mar 2004
Posts: 777
Likes: 0
From: Fairfield, Ca
Car: 1991 Firebird
Engine: 355 TBI
Transmission: WC-T5
VE table display in RT Tuner vs. Tuner Pro
Viewing my lower VE table in these two apps show different values (subtle in some cells, downright wacky in others). Am I missing something here ? does Tuner Pro factor in other value(s) ?
here is the table in TC's RT Tuner :
and in Tuner Pro :
here is the table in TC's RT Tuner :
and in Tuner Pro :
Moderator
iTrader: (1)
Joined: Mar 2002
Posts: 18,432
Likes: 233
From: Chasing Electrons
Car: check
Engine: check
Transmission: check
Re: VE table display in RT Tuner vs. Tuner Pro
Originally posted by adambros
Viewing my lower VE table in these two apps show different values (subtle in some cells, downright wacky in others). Am I missing something here ? does Tuner Pro factor in other value(s) ?
here is the table in TC's RT Tuner :
and in Tuner Pro :
Viewing my lower VE table in these two apps show different values (subtle in some cells, downright wacky in others). Am I missing something here ? does Tuner Pro factor in other value(s) ?
here is the table in TC's RT Tuner :
and in Tuner Pro :
RBob.
Thread Starter
TGO Supporter
iTrader: (2)
Joined: Mar 2004
Posts: 777
Likes: 0
From: Fairfield, Ca
Car: 1991 Firebird
Engine: 355 TBI
Transmission: WC-T5
good pickup ! after comparing the two, cant believe i didnt catch that one 
I am using the 8746jonprevost61h.ecu . . . maybe jon or mark s/be notified as this was the public ecu for download on TunerPros site ?
thanks,
~alex

I am using the 8746jonprevost61h.ecu . . . maybe jon or mark s/be notified as this was the public ecu for download on TunerPros site ?
thanks,
~alex
Thread Starter
TGO Supporter
iTrader: (2)
Joined: Mar 2004
Posts: 777
Likes: 0
From: Fairfield, Ca
Car: 1991 Firebird
Engine: 355 TBI
Transmission: WC-T5
-- so (here i go again, thinking . . . ) wouldn't it be a relatively easy fix -- e.g. transposing the axes ? or is there something else . . .
/* Table 25: Main Fuel Table #1 %Volumetric. Effeciency. */
{
/*startAddr =2B1,
/*columns =9,
/*rows =8,
/*elementSize =1,
/*bitMask =0,
/*offset =0.000000,
/*mulOrDivOrBit =0,
/*factor =0.390625,
/*map_name =Main Fuel Table #1 %Volumetric. Effeciency.,
/*ylabel =RPM,
/*yaxis =400 800 1200 1600 2000 2400 2800 3200 ,
/*xlabel =MAP (Kpa),
/*xaxis =20 30 40 50 60 70 80 90 100,,
};
/* Table 25: Main Fuel Table #1 %Volumetric. Effeciency. */
{
/*startAddr =2B1,
/*columns =9,
/*rows =8,
/*elementSize =1,
/*bitMask =0,
/*offset =0.000000,
/*mulOrDivOrBit =0,
/*factor =0.390625,
/*map_name =Main Fuel Table #1 %Volumetric. Effeciency.,
/*ylabel =RPM,
/*yaxis =400 800 1200 1600 2000 2400 2800 3200 ,
/*xlabel =MAP (Kpa),
/*xaxis =20 30 40 50 60 70 80 90 100,,
};
Trending Topics
TGO Supporter
Joined: Jan 2000
Posts: 1,861
Likes: 0
From: In your ear. No, the other one.
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
I just researched this a little more. Turns out some tables are populated by column rather than by row (where row population is much more common).
The only way to accomodate this with the ECU format is to exchange rows and columns (put RPMS in the columns and MAP in the rows). Unfortunately thats not the only ECU shortcoming - you won't have enough characters in the column headings to fully list the RPM values. =(
This will change in the next release of TunerPro.
The only way to accomodate this with the ECU format is to exchange rows and columns (put RPMS in the columns and MAP in the rows). Unfortunately thats not the only ECU shortcoming - you won't have enough characters in the column headings to fully list the RPM values. =(
This will change in the next release of TunerPro.
Thread Starter
TGO Supporter
iTrader: (2)
Joined: Mar 2004
Posts: 777
Likes: 0
From: Fairfield, Ca
Car: 1991 Firebird
Engine: 355 TBI
Transmission: WC-T5
Originally posted by Mangus
I just researched this a little more. Turns out some tables are populated by column rather than by row (where row population is much more common).
The only way to accomodate this with the ECU format is to exchange rows and columns (put RPMS in the columns and MAP in the rows). Unfortunately thats not the only ECU shortcoming - you won't have enough characters in the column headings to fully list the RPM values. =(
This will change in the next release of TunerPro.
I just researched this a little more. Turns out some tables are populated by column rather than by row (where row population is much more common).
The only way to accomodate this with the ECU format is to exchange rows and columns (put RPMS in the columns and MAP in the rows). Unfortunately thats not the only ECU shortcoming - you won't have enough characters in the column headings to fully list the RPM values. =(
This will change in the next release of TunerPro.
-- and may my registration and generous donation serve as a virtual 'kick in the pants'
TGO Supporter
Joined: Jan 2000
Posts: 1,861
Likes: 0
From: In your ear. No, the other one.
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
Originally posted by adambros
-- and may my registration and generous donation serve as a virtual 'kick in the pants'
-- and may my registration and generous donation serve as a virtual 'kick in the pants'
Thread
Thread Starter
Forum
Replies
Last Post





