Are you saying this because it doesn't beep, or because you verified that the firmware logs have not been appended to since your more recent upgrade? My logs continue to grow, each time saying nothing needs to be updated. And as such, does not beep either. Double check.
All right - I think you're starting to make a believer out of me!!
Removed the card from the Phantom and stuck it in a reader.
In my root dir there are two files - a .txt. file and a .bin file.
The .bin file is, of course, the latest update version executed on my craft.
The .txt contains more info than I thought it might and tends to concur what
you're telling me.
It looks like each time I fly, when the P3 comes on, it compares the firmware to the .bin file version and decided it's already the current version and there's nothing to be done.
Someone at DJI truly familiar with the situation would have to address this, because I'm still somewhat confused. Here's a scenario - DJI says to download the new firmware (not now, of course, but when another one becomes available) and make sure the .bin file is in the root directory, then make sure controller is off, turn on P3 and proceed with the update.
However, it almost appears that what's happening is it's checking every time you execute the proper starting sequence for the Phantom, i.e., turn on the controller first, then turn on the P3. If seemed like the update process is executed ONLY when the P3 is turned on with the controller turned off. However, that doesn't explain why it appears to be "checking" the firmware every time you start everything.
For it to check every time and try to enter the update sequence is not logical - the normal startup calls for the controller to be on first - during the normal update, they tell you not to have the controller on at all.
I gotta give you credit - I can understand your intrepretation of the data, but not the why! And, seriously, I do appreciate your being insistent/persistent - and without being rude! Thanks.