Thread: XDF files changing limits on its own?!

OK, so I need some help here guys. Randomly all of my XDF files are changing their limits, so I'll go in to say, change my TP scale, and suddenly I can't go over 128 where previously the limit was much higher and I had successfully set the top load scale above that point. Same with RPM scale, had it set to 8000 on my friends VE+T with TunerCode, and now suddenly the damn XDF won't let me go over 7000 without right-clicking on the item and selecting "edit parameter XDF info." I don't want to have to do that [again].

Why is this doing this? It's happened on my B13 XDF file, and today or yesterday it just happened to the TunerCode XDF my friend uses for the VE+T. I've even gone back and re downloaded again the same XDF for my car (B13, no TunerCode), and for some reason it still has the same limits set! I can't figure it out... I've never had random limits imposed like this, it makes importing over my load scales and fuel/timing maps very difficult and time consuming.

Any help would be appreciated it. I've re-installed software, re-downloaded files, and my desktop I'm on now just go formatted last week. I'm stumped, and getting pretty pissed off at this.

Screenshots to show what I'm seeing.




You can see where the RPM limit for the Fuel map and Timing map are different, and they didn't use to be. Also, on the fuel map, I can't go past 100, which makes entering values for closed-loop impossible. I'm getting similar results from the TunerCode file, however I am not posting a screen shot up of those in case there is any sensitive info to be revealed as far as addressing goes. Any ideas?

Nate

Evening bump. Nobody has any ideas? I refuse to think I'm the only person this has happened to...

This is the second time this has happened to me. I cannot explain it.

There is no way the file could automatically change itself. I did notice that Dave's preset numbers are are a little low for some applications, thus just raise them up and you will be just fine.

Remember to save the XDF!

I wouldn't think they would just change themself. But I have absolutely been using values above these imposed limits (not the ones I posted screenshots of, but for TP and RPM) up until a month ago when this first happened? I cannot explain it. I have no problem changing the stuff for my B13 XDF, but my buddy with his TunerCode stuff was just stumped, and I didn't want to go changing things on the TunerCode XDF before I came here and asked some questions.

Yeah, I can change it easily. My question was more just "why" and "how" this could have changed... I guess the world may never know. Sometimes I bloody hate electronics.

If you are having a problem with the TunerCode XDF, just send me an email and I'll help you figure it out.

Thanks,
Dave

Thanks Dave. It wasn't only yours, but I appreciate the support. Roger called me up yesterday saying it was happening on his machine and I checked it out, and it was exactly what mine did a month ago with my regular B13 XDF. When I get back to his machine, I'll probably just raise them up where it needs to be, but I may e-mail you and show you what I see just to see how it compares.

Ok I can think of one way it may be the computer's fault. If the file got corrupt (due to a failing hardrive most likely), then Windows might have recovered it from an earlier copy from a month ago.

Hm... my hard drive did just start acting up and failed last weekend. I suppose that could have been in? I think with dropbox you can find older versions of your files, I may try that and see what comes of it.

edit: double post

The issue is with the "High Range" limit set in the XDF. TunerPro limits the values that you can put in the cells to this value. Just increase the limit shown in the "Use High Range" field shown in the screen shots above and then "Save XDF" under the "XDF" menu, or click the "Save XDF" icon on the toolbar.

You can open the Edit XDF Parameter dialog by highlighting the table and hitting the F2 key, or right click and select "Edit Parameter XDF info".

The limits are set because TunerPro uses them to determine table cell coloring. If you don't want the cell coloring, you can just uncheck "Use Low Range" and "Use High Range". I have asked Mark to change this behavior in TunerPro.

Dave