it's always been a problem,TO SAVE
it save flags and constants ok, but the MAF tables don't save or save erroneous data, I tried reloading the software and tried updating it....
tried different bins....
comments plz need to tune car!!!!
it save flags and constants ok, but the MAF tables don't save or save erroneous data, I tried reloading the software and tried updating it....
tried different bins....
comments plz need to tune car!!!!
Quote:
swaped xdf files around, same problemOriginally Posted by Ronny
sounds possibly the definition file may be wrong. Quote:
http://tunerpro.net/downloadBinDefs.htm
yes and yes Originally Posted by Ronny
Are you using one of these?http://tunerpro.net/downloadBinDefs.htm
been fine for at least a year
I put the software away for months only to come back to a glitch
will save constants but not tables
btw thanks for the help
can you delete the one you are using and downlaod a fresh one? Maybe it somehow was damaged/corrupted?
Quote:
okay say mismatched with ADS but the name is the same( 6E.xdf)Originally Posted by Ronny
can you delete the one you are using and downlaod a fresh one? Maybe it somehow was damaged/corrupted? I am not that smart on those questions. I use EBL and never deal with other XDF's. I think TP allows you to change the def file "extension" as in .xdf vs ?.
From TP site:
Does TunerPro support my ECM and code mask? Will you create a definition for me?
TunerPro supports a wide variety of makes, model, and year setups. Support of a particular ECM and/or make, model, and year is limited only by the availability of bin definitions for that particular setup. There are a variety of sources for definitions on the Internet, and I have links to some sources in the links section of this site and on the bin definitions download page. I am not in the habit of creating definitions. If the information is available for the definition to be created, the end use can create the definition. For more information on how to do this..
.ADS I believe is the datalogging file in TP-RT.
From TP site:
Does TunerPro support my ECM and code mask? Will you create a definition for me?
TunerPro supports a wide variety of makes, model, and year setups. Support of a particular ECM and/or make, model, and year is limited only by the availability of bin definitions for that particular setup. There are a variety of sources for definitions on the Internet, and I have links to some sources in the links section of this site and on the bin definitions download page. I am not in the habit of creating definitions. If the information is available for the definition to be created, the end use can create the definition. For more information on how to do this..
.ADS I believe is the datalogging file in TP-RT.
TGO Supporter
Quote:
it save flags and constants ok, but the MAF tables don't save or save erroneous data, I tried reloading the software and tried updating it....
tried different bins....
comments plz need to tune car!!!!
It would be a tremendous help if you could describe the symptoms. What exactly does "don't save or save erroneous data" mean? What data did you enter, and what data got saved?Originally Posted by slickfx3
it's always been a problem,TO SAVEit save flags and constants ok, but the MAF tables don't save or save erroneous data, I tried reloading the software and tried updating it....
tried different bins....
comments plz need to tune car!!!!
My guess: rounding error. You either entered too small a change for the table resolution, or a large enough change, and your change got rounded.
Again, explicit description of the expected and actual results is a required starting point for help with an issue like this.
Quote:
My guess: rounding error. You either entered too small a change for the table resolution, or a large enough change, and your change got rounded.
Again, explicit description of the expected and actual results is a required starting point for help with an issue like this.
http://forums.corvetteforum.com/c4-s...e-changes.htmlOriginally Posted by Mangus
It would be a tremendous help if you could describe the symptoms. What exactly does "don't save or save erroneous data" mean? What data did you enter, and what data got saved?My guess: rounding error. You either entered too small a change for the table resolution, or a large enough change, and your change got rounded.
Again, explicit description of the expected and actual results is a required starting point for help with an issue like this.
MAF tables are only afflicted, everything else will accept changes.
MAF tables will not accept any changes including the rounding.
I have tried teenie changes to one field and it will not save, I have tried larger entries and the same thing happens.
Sometimes when I hit save and reopen the table the entries change, not to what I have entered but to something else and not to all the fields.
I have reinstalled the software. I have gone into the raw as per Corvette forum comments and changes were savable in raw.
still stuck.
TGO Supporter
email me the bin, definition, and precise repro steps. also send me info on what version of tp you're using. you can figure that out via help->about.
Quote:
what does precise repro steps mean?Originally Posted by Mangus
email me the bin, definition, and precise repro steps. also send me info on what version of tp you're using. you can figure that out via help->about. Your email please and Thanks.
I noticed a similar issue the other day after a comment on the Tuner pro site.
I noticed that if I change a value in a table, say VE table, then close the table, where I'm propted to apply changes, click yes, then save the bin, the changes do not take effect.
If I make the change in the VE table, then hit enter to move the cursor to another cell in the VE table, then close the table, clicking yes to apply changes and save bin, the changes take effect.
I was using $0Dv.175.xdf, and an $0D bin to test.
I think this might be related to some upload failed messages I am getting while trying to emulate. I wanted to wait until I had more data to replicate the problem, but this seemed like a good to time to add to the conversation. Build V5 6156, FWIW. I was trying to use this on a vehicle I hadn't tuned previously, so I'm not sure if this could be why I seem to be having a bit of difficulty tuning it. My other car is not currently on the ground, so I can't test it right now to very emulation works with it.
I noticed that if I change a value in a table, say VE table, then close the table, where I'm propted to apply changes, click yes, then save the bin, the changes do not take effect.
If I make the change in the VE table, then hit enter to move the cursor to another cell in the VE table, then close the table, clicking yes to apply changes and save bin, the changes take effect.
I was using $0Dv.175.xdf, and an $0D bin to test.
I think this might be related to some upload failed messages I am getting while trying to emulate. I wanted to wait until I had more data to replicate the problem, but this seemed like a good to time to add to the conversation. Build V5 6156, FWIW. I was trying to use this on a vehicle I hadn't tuned previously, so I'm not sure if this could be why I seem to be having a bit of difficulty tuning it. My other car is not currently on the ground, so I can't test it right now to very emulation works with it.
TGO Supporter
Quote:
Your email please and Thanks.
See the TunerPro web site. Example of precise repro steps:Originally Posted by slickfx3
what does precise repro steps mean?Your email please and Thanks.
1) Open TunerPro RT v5.00.1234
2) Open 6E.xdf (attached to this email)
3) Open mybin.bin (attached to this email)
4) Open the "MAF table #1"
5) Change the cell in row 3 from "0.10" to "1.52"
6) Click "save" button in the table editor toolbar
7) Re-open the table.
Expected: "1.52" appears in row 3
Actual: "0.10" still appears in row 3.
I'm going to have to re-write my post. LOL 

TGO Supporter
Quote:
I'm not worried about you. You know how this works, and how to contact me. =) Originally Posted by Six_Shooter
I'm going to have to re-write my post. LOL
And hopefully you'll fire me an email with more details (and a bin/XDF) so I can easily investigate. You know me - the faster and easier I can replicate the issue, the faster I can fix it.
Quote:
And hopefully you'll fire me an email with more details (and a bin/XDF) so I can easily investigate. You know me - the faster and easier I can replicate the issue, the faster I can fix it.
I know, which is why I've been holding off, until I could find exact replication steps. Originally Posted by Mangus
I'm not worried about you. You know how this works, and how to contact me. =) And hopefully you'll fire me an email with more details (and a bin/XDF) so I can easily investigate. You know me - the faster and easier I can replicate the issue, the faster I can fix it.

Quote:
1) Open TunerPro RT v5.00.1234
2) Open 6E.xdf (attached to this email)
3) Open mybin.bin (attached to this email)
4) Open the "MAF table #1"
5) Change the cell in row 3 from "0.10" to "1.52"
6) Click "save" button in the table editor toolbar
7) Re-open the table.
Expected: "1.52" appears in row 3
Actual: "0.10" still appears in row 3.
Sorry but I still don't get it, I tried to contact you in your website under bug reporting but the page don't load, trying for days...Originally Posted by Mangus
See the TunerPro web site. Example of precise repro steps:1) Open TunerPro RT v5.00.1234
2) Open 6E.xdf (attached to this email)
3) Open mybin.bin (attached to this email)
4) Open the "MAF table #1"
5) Change the cell in row 3 from "0.10" to "1.52"
6) Click "save" button in the table editor toolbar
7) Re-open the table.
Expected: "1.52" appears in row 3
Actual: "0.10" still appears in row 3.
Thanks for the help.
