- Joined
- Aug 7, 2013
- Messages
- 10,825
- Reaction score
- 5,701
Firstly, apologies for the long post......
It seems to me that after reading this forum and RC Groups and DJI user forums there is one common concern that keeps coming up time and time again and that is the unexpected drop into Atti mode that can catch people unaware. Caused, we understand by an over zealous compass sensitivity/error setting that drops the Inspire immediately into Atti mode.
Yes, we all should/can fly in Atti should the need arise but the problem is the unpredictability with the way the bug manifests itself. If we were to fly at the bottom of a canyon say, then logic dictates that GPS reception could be sketchy at best so the user could choose to fly in Atti. The problem is the flight dynamics of the aircraft change radically as the Inspire drops in and out of Atti and this doesn't make for a relaxing flying experience (especially in gusty conditions.
Now, I KNOW that firmware releases are not under the control of Ed or Blade and I KNOW that they have no influence on when they will be released and I KNOW that they do not write any of the code but....... @Tahoe Ed and @blade strike you guys HAVE been testing a beta version of the firmware that directly addresses the GPS/Compass issue for some time and you DO have direct access to DJI so the question is one of communication to the end user
My question to you guys is what is the current situation regarding the next firmware release that addresses this very problem? DJI MUST have a timeframe/project timeline for this.
If DJi are trying to implement all sorts of new features and bells and whistles in the next release then why not do an interim release (like they did with .17) to at least fix the Compass/GPS issue which they have presumably solved?
Please don't answer the the question with "Soon" or "We hope very soon" as that wears a bit thin after a while.
Maybe you could explain exactly what is holding things up at DJi China R&D in the roll out of either an interim or full release? Or maybe explain the process a little clearer so that us (the end users) can understand what the delay in getting this very real problem fixed is?
Please do not take this as a DJi bashing post, it is a genuine request for an understanding into the workflow/process of getting a widespread problem looked at, fixed and out to the consumer.
Thanks guys....
It seems to me that after reading this forum and RC Groups and DJI user forums there is one common concern that keeps coming up time and time again and that is the unexpected drop into Atti mode that can catch people unaware. Caused, we understand by an over zealous compass sensitivity/error setting that drops the Inspire immediately into Atti mode.
Yes, we all should/can fly in Atti should the need arise but the problem is the unpredictability with the way the bug manifests itself. If we were to fly at the bottom of a canyon say, then logic dictates that GPS reception could be sketchy at best so the user could choose to fly in Atti. The problem is the flight dynamics of the aircraft change radically as the Inspire drops in and out of Atti and this doesn't make for a relaxing flying experience (especially in gusty conditions.
Now, I KNOW that firmware releases are not under the control of Ed or Blade and I KNOW that they have no influence on when they will be released and I KNOW that they do not write any of the code but....... @Tahoe Ed and @blade strike you guys HAVE been testing a beta version of the firmware that directly addresses the GPS/Compass issue for some time and you DO have direct access to DJI so the question is one of communication to the end user
My question to you guys is what is the current situation regarding the next firmware release that addresses this very problem? DJI MUST have a timeframe/project timeline for this.
If DJi are trying to implement all sorts of new features and bells and whistles in the next release then why not do an interim release (like they did with .17) to at least fix the Compass/GPS issue which they have presumably solved?
Please don't answer the the question with "Soon" or "We hope very soon" as that wears a bit thin after a while.
Maybe you could explain exactly what is holding things up at DJi China R&D in the roll out of either an interim or full release? Or maybe explain the process a little clearer so that us (the end users) can understand what the delay in getting this very real problem fixed is?
Please do not take this as a DJi bashing post, it is a genuine request for an understanding into the workflow/process of getting a widespread problem looked at, fixed and out to the consumer.
Thanks guys....
Last edited: