You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over the last few days, we have received a small number of reports regarding the in-flight stability of the M600/Pro 1.0.1.60 firmware. We're currently investigating this issue, but in the meanwhile we've pulled the firmware from DJI Assistant. Here's how this might affect you:
If you are already on 1.0.1.60, you will be prompted to unlock the drone each time from the Go app before you fly. You will be able to downgrade firmware to 1.0.1.20.
If you are on 1.0.1.20, you can continue to use OSDK 3.2 with this firmware. You will not be given an option to upgrade to 1.0.1.60.
We realise that the change of APIs for OSDK 3.2 --> 3.3 means this downgrade advisory is a problem for your code, so to mitigate this we're working on a version of OSDK 3.3 that will be compatible with the 1.0.1.20 firmware. This version will keep the same interfaces, topics and services as OSDK 3.3, but newer features such as high-frequency telemetry and hardware sync will be unavailable. This version should be out by the end of next week. We apologize for the churn in firmware, and hopefully this backward compatible SDK will go some way towards ensuring everyone is flying a flight-worthy firmware without much change in your codebase.
If there are any follow-ups, let's continue the discussion at dji-sdk/Onboard-SDK#188 to keep all the talk consistent.
The text was updated successfully, but these errors were encountered:
Hi all,
Over the last few days, we have received a small number of reports regarding the in-flight stability of the M600/Pro 1.0.1.60 firmware. We're currently investigating this issue, but in the meanwhile we've pulled the firmware from DJI Assistant. Here's how this might affect you:
We realise that the change of APIs for OSDK 3.2 --> 3.3 means this downgrade advisory is a problem for your code, so to mitigate this we're working on a version of OSDK 3.3 that will be compatible with the 1.0.1.20 firmware. This version will keep the same interfaces, topics and services as OSDK 3.3, but newer features such as high-frequency telemetry and hardware sync will be unavailable. This version should be out by the end of next week. We apologize for the churn in firmware, and hopefully this backward compatible SDK will go some way towards ensuring everyone is flying a flight-worthy firmware without much change in your codebase.
If there are any follow-ups, let's continue the discussion at dji-sdk/Onboard-SDK#188 to keep all the talk consistent.
The text was updated successfully, but these errors were encountered: