help, u7165 xvap2n2

bgreb01 · Post by **bgreb01** » Fri Jan 16, 2009 11:26 pm

Hope someone can help me out, I have a 2004 f250 6.0 and the u7165 tuner v.9r05 and a calid of vxap2n2. Cannot use the tunes because of major surging above about 2000 rpm I have been to the sticky for the updated tunes that are supposed to help with this and downloaded them. I then use the ds downloader program to try and load them on the programmer the problem I have is when I go to send the file to programmer and it asks for the original backup, I direct it to the backup file created and when I press the open to proceed it says the calid does not match. The error message shows the calid for my backup as vxap2n2 and the tune calid is blank? I have read as much as I possibly could before posting including all the instructions given, I am probably screwing something up but just cannot get to the bottom of this. I am not a computer guy so this may be the issue. Verry sorry if this has already been answered and I am an idiot but man I want to go play and this is really holding me back, the rice burners could take me and thats not cool....... Let me know if I have left any needed info out,Thanks.

Post by **sohfast94** » Mon Jan 19, 2009 11:50 am

Post your original backup... I'll see what I can do.

bgreb01 · Post by **bgreb01** » Mon Jan 19, 2009 12:59 pm

Here you go. I retried this morning from the begining to get you exact info. Had to laod a tune from the predator to be able to get the original backup file. I then went to send tune to tuner, I clicked on the tune that I took from your sticky to correct issues and this is what happened.
XML parsing error: not well formed (invalid token) at line 1. I proceeded and chose to locate my backup tune where I saved it and when I selected it this warning came up.
ORI File Warning
the calibration identification of your original backup file does not match that of your tune file. The tune file calid is and the backup file is vxap2n2. Please either find the correct original backup for this tune, or use an original backup file downloaded from the tool to create a new tune.
I then get pushed back to the original screen of the ds downloader.
As requested I will post my original backup, I apreciate the very rapid respone this morning. Cannot wait to be kicking butt again, my warranty is now up so I do not see any more trips to the dealer to mess up my computer, Thanks Again..........

Post by **sohfast94** » Mon Jan 19, 2009 1:35 pm

As requested... This should make the POWA!!!

A word of advice. Do NOT tow with this file.

bgreb01 · Post by **bgreb01** » Mon Jan 19, 2009 2:31 pm

I have tried this as a tune and the same problem as before. Is this a tune file or is this a replacement file for my backup? I tried it using it as a backup and using the tune file from your sticky and it loaded a tune to the predator that came with many errors, I have now erased it from the tuner because I am thinking the file you gave me was a tune and not a backup. I thank you again for your time....

Post by **sohfast94** » Mon Jan 19, 2009 2:47 pm

No the file I just posted is a tune... Click send tune to tool in DSDL and it will load. Then you'll have the option to select custom tune on the predator and load that file.

bgreb01 · Post by **bgreb01** » Mon Jan 19, 2009 3:02 pm

Still no luck, as soon as I select the tune to send it gives me the xml parsing error: not well formed (invalid token) at line 1.
if I press to continue I end up with the same error I was getting before with the calid and then it puts me back to the beginning? Is my ds downloader program missing something? I will try uninstalling it and re-install it just in case.

bgreb01 · Post by **bgreb01** » Mon Jan 19, 2009 3:17 pm

Just uninstalled and re-installed the downloader and tried to send tune and same errors as before? What is the xml parsing error? This is the first error I get is this affecting the rest?
xml parsing error: not well formed (invalid token) at line 1.

2nd error
ORI file warning:
the calid of your original backup file does not match that of your tune file.
Is my backup not loading on to the predator correctly?
Here are screenshots of the errors.

Post by **sohfast94** » Tue Jan 20, 2009 9:35 am

re-read your original backup out of the tool and I'll make the file again....

bgreb01 · Post by **bgreb01** » Tue Jan 20, 2009 12:43 pm

Here we go, hope this will help. Thank You.

Post by **sohfast94** » Tue Jan 20, 2009 1:05 pm

Emailed.

bgreb01 · Post by **bgreb01** » Tue Jan 20, 2009 1:52 pm

Hot Damn, e-mailing the tune made all the difference. Loading the tune on truck now, I will re-post when I have driven it and verify the non-surging. To anyone looking to buy a Diablo these guys WILL take care of you........
Thank You. Going Dodge hunting now.

help, u7165 xvap2n2

help, u7165 xvap2n2

RE: help, u7165 xvap2n2