I wish there was some kind of edit, ANY kind available with FRDS or Forscan, that could trigger an FRDS module scan to recognize something being "off" on a module and cause FRDS to render the latest update as available.
Or put another way, too bad the update library becomes unavailable in FRDS...
You can repeat the USB procedure on the truck if you still have the files. But FRDS does a scan and if it thinks the module is up to date, it removes the update from the list so I don't think you could initiate a fresh download.
Believe me when I say I initiated the USB update 10 times. :)
Again, in less densely populated areas, especially states like Texas, driving 100 miles is nothing unusual. Houston is a metropolis of 6+million and nothing is unusual about a daily commute of 50 miles one way.
Hmmmm. Maybe that explains the huge Pick-up truck ratio in places like I have spent my 6 decades. But I think there's more to it than that. Pick-up trucks are like a Camry in Texas. It's comfortable. It's roomy inside and can accommodate adults in any seat, as well as easy entrance and egress...
According to his profile, he doesn't have a 2021 truck yet, although he might and hasn't updated yet, kinda like Ford? :)
I'd be willing to PayPal him for his 48 hour FRDS license if it would FIX his broken truck and bring him good cheer!
Go ahead and guess. Extend out for a few years just based on your gut. I'm curious.
I'm not objecting to optimistic views of Teslas future, but I have to wonder if you are serious about taking Covid Era reductions in production for manufacturers like Ford and GM and extending that out to...
Don't know exactly what the "numbers" are for the demand for EV trucks, but I do believe that for the next few years the demand outstrips the supply.
So we can debate the politics and the grid all we want, but the thread was about the demand.
I love you guys!
I have in fact looked at the module/software-P/N grid in FRDS. But I remember thinking that I don't know how to map that to anything meaningful to me. Which is really me just being too lazy to build a spreadsheet myself and populate it with every data point possible.
Thinking outside the box.....
Wonder if there is a Forscan or FRDS routine of some kind that is a "type of reset" that is different than the power/forward-seek soft reset.
Or perhaps a Forscan restore of the APIM from the original As-built file. Anything that would shake things up.
Or IS it...
There IS one thing that can be different from one truck to the next regarding APIM update..... The starting point.
Even if you had 2 identical APIM modules, hardware wise, they could be running on different software, thus behaving accordingly.
I wonder if we have enough data collected to...
Agreed. Completely.
My labeling the sticks was because I had 2 identical brand new sticks, one for APIM and one for TCU. The label was just to keep it straight AND to start with either if I couldn't get the other to succeed.
I think that whatever word you use as a label when formatting you WILL see that label on the Sync screen twice. Once upon recognition it is there, and once for indexing. It does not show the label when indicating the update has began.
But I admit that the first time Sync said "Indexing APIM"...
I tried to overcome the restart-loop by formatting the stick the slow way. Made no difference.
And I tried 3 different brands of sticks all quick formatted WITH label "APIM" and they all initiated the update within seconds of inserting the stick.
Sync would show at the upper left hand corner...
What's so strange is that if we purchased 10 pc's of the same make/model, and then proceeded to prepare all 10 for deployment, we would almost guaranteed have identical out-of-the-box experiences, including getting them all updated to the latest build/updates.
Yet with our trucks, I can stick...