mikel wrote:This is an issue where the DB you downloaded was not perfect and the tool discarded it after it installed it, likely a wifi issue.
Simply run the updater again to replace the missing file.
As for the speedo issue, it seems you are reloading the last custom tune and not resetting the parameters, so you are reapplying the tire/gear change to the already modified file, which is always going to be an issue.
Choose the option to reset params or go back to stock then reload the tune with no changes.
if the forum is not quick enough for you, it should no tbe the first line of support, phone, or email is the best way to reach us in a timely manner.
Alrighty so here goes...
First I do NOT use wifi... Only Cat5 Hardwired at GB speed to my PC then USB 2.0 to your device.
I did "try" to reload the stock tune (return to stock) as my original post said but the Speedometer was still not working correctly. That's when I looked at the info file and saw that the Ford db was "missing".
I think I might have found the issue after re-running the update and looking closely at the adjustable parameters. There seems to be some issue when changing tire size. (tire by size I don't think my device even had prior to the update, it use to only have tire revs per mile) so I can only guess that the revs per mile value is stored and somehow not flagged as a "modified" parameter.
I was able to re-run the update and copy the original stock tune backup over the devices original backup and then revert that. Then I was able to install my own tune (not touching tire size at all) without speedometer issues.
mikel wrote:I reply to 1000s of posts here, if I miss one now and then, I apologize, but I never did anything to wrong you personally, and I feel I do a great job of supporting others here who have questions about our products.
Yes you do and it was not intended as a personal affront to you either.
Think about if your software development/deployment folks did their job a little better you wouldn't have near as many issues that require your attention after the fact.
The "corrupt" DB issue should/could have been validated and caught before the installer finished and then re-downloaded during the process thus not causing an end-user (customer) issue.
The same is true for the updates running over the top of some peoples still installed tunes... if the license is in use (or the original backup file exists) um maybe don't allow the update to start? Prompt the user to revert to stock before installing/applying the update?
I will lay odds those are a couple of pretty common issues you end up having to address (for all makes/models) after the fact and after the customer has been exposed to what looks to them to be shoddy workmanship...
Trust is easily lost and very hard to gain back.
