TunerPro V5 Beta

[Jayme]

yeah its a problem with 2 equasions in the definitions.. they were invalid and I guess the new equasion engine didnt like them.

try these

OSE_$12P_v1.08_fixed_tp5_defs.zip

(30.56 KiB) Downloaded 310 times

[vn5000]

Cheers ,thanks for that Jayme.

[antus]

Even though the problem was invalid data in the adx, Mark has confirmed the crash is fixed for the next build.

[yoda69]

5.00.7045.00 (BETA) (9/04/10): http://www.tunerpro.net/beta/Builds/Set ... T_v500.exe

Fixed issue with table editor scratch buffer being undersized for complex table layouts (those that use more complex major and minor strides)
Fixed crash when setting ADX equation to hex constant, or when using long variable names
Moved Recent Defs in the Acquisition menu to the position above the first separator
Fixed issue where ADX lookup tables set to output anything other than floating point weren't being loaded from file correctly

[yoda69]

And another update, coming thick and fast at the moment

5.00.7066.00 (BETA) (9/06/10): http://www.tunerpro.net/beta/Builds/Set ... T_v500.exe

When playing back a data acquisition log, if TunerPro is connected to vehicle, monitoring will first be stopped
Fixed xdf address variable type, where data sizes other than 8 bit weren't being persisted
Fixed issue where XDF table per-cell equation variables were not being properly parsed
Fixed issue when recording a second log in the same instance of TunerPro, where the second log's first packet start time is incorrect, leading to a log file that won't play
Fixed ADXValue editor issue where selecting between values with the conversion tab active resulted in ADXValue variables becoming corrupt

[charlay86]

Expect some more too... for some reason when ever I fiddle with interesting things they always seem to break

[charlay86]

Another one:

TunerPro RT

5.00.7174.00 (BETA) (9/20/10): Download

* Added ability to patch bin files from Motorola S-Record files (*.S19, etc), via the File->Patch Bin menu item
* By default, data acquisition logs are exported in their entirety. Optionally, you can selectively export specific objects
* Increased max ADX command byte string (number of bytes in the command) to slightly over 500 bytes
* Fixed bug that caused changes to variables to not propagate through function calls in XDF expressions (breaking the IF function, most notably)
* Fixed crash in ADX histogram editor when browsing for X or Y axis object and not selecting anything
* Fixed bug where comparing data for XDF parameters that use the output from other objects was using the original data instead of the compare data
* Fixed bug where address variables/functions were pulling data from the edit buffer instead of the comparison buffer when comparing bins in xdf parameter editors
* Fixed bug in XDF Table Object Editor where apply button wasn't enabled after editing a row/col internal definition expression
* Fixed issue in color preferences where color buttons weren't updating properly

[Jayme]

thats an old release theres another new one now.

[The1]

anyone else having the same problems i am? I change the values in some tables, even in hex and it just changes it to FF all the time. I have reported it to TP just incase it's an issue, just started with the last version.

[yoda69]

Which tables are you changing?
If it is anything to do with the MAF tables, it is a known problem but not related to TP but rather the way GM did there MAF's.
What xdf and what table is the problem in?

yoda69