Pat Cusack
lvl.1
Australia
Offline
|
I also ran into these issues with the aircraft not recognising the firmware file on SD card.
It was simply the wrong file (update for Inspire, not Inspire Pro). Two years in, after a dozen updates, missed this detail. Doh!
The clue is in previous update logs. You can see the FC version for your vehicle in previous entries. If the prefix in the firmware file doesn't correspond with your FC# in these logs, that will be the problem.
In DJI's defence, that much is at least consistent. The naming convention for these files is absurd - but at least it's consistent!
That said: Part of the reason we all panic when this stuff goes awry is the shocking track record for these updates. The documentation is sketchy at best, and it's always a punt in terms of the deployment pipeline. I only fly occasionally, but other people are relying on schedule. Local supplier to industry suggested 'Just fly' - rather than risk another firmware episode the night before.
The points made here about safety regime and operational compliance pretty much rule out the use of this kit anywhere but China. You simply can't comply with first world statutory stuff for aircraft. It's a very, very expensive toy that's simply intractable around commercial statutory requirements/schedule. The only way to comply is not accept DJI fiddling around with the stack *two years in*, and fly the-devil-you-know. This means no warranty, but that sure beats arriving on set with your d*** in your hand |
|