-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Announcement] M600/Pro Firmware Downgrade Advisory #188
Comments
…c bugfixes, closes #189 and some Qt sample issues.
…c bugfixes, closes #191 and some Qt sample issues.
Hi everyone - M600 FW 1.0.1.20 can now be used with the latest OSDK 3.3 release and OSDK ROS 3.3 release. Thank you for your patience! |
Hi, how to go back to 1.20? 1.60 make alot of troubles |
@eagleman111 - you can downgrade through DJI Assistant 2. To help us understand your issues better, could you tell us some specifics on 1.60 that is causing trouble? |
flight instability. |
I tried the updated SDK and ROS SDK 3.3 for 1.0.1.20. I am getting a run error of [dji_sdk-2] process has died [pid pid, exit code -11, cmd /path/to/folder/devel/lib/dji_sdk/dji_sdk_node __name:=dji_sdk __log:=/path/to/log/file.log]. Is there a way to fix this without having to clean my system? |
This is what you see with Assistant 1.1.6. Could you report back with what you see? |
worked. however there is no more notification of 1.60. is this normal? |
M600/Pro firmware 1.0.1.65 was released on 10/24, this fixes the instability observed in 1.0.1.60. It is otherwise identical to the 1.0.1.60 firmware, and all code should work seamlessly across the transition. |
Guys, I have a big problem, |
Please hit the button in the top right corner for Assistant 2, that will help you refresh the firmware list. Only the 1.65 firmware should be seen. If that is not the case, please attach a screenshot and we'll help you resolve the issue. 1.20 firmware has not changed at all since the last time it was available, so it is likely that the root cause of your instability is lying elsewhere. |
so how to fix root issue? |
no help? |
@eagleman111 please open a new GitHub issue with some details regarding your issues, so that we are able to assist you. Please include the following information, along with any other specifics that you can give us:
|
is it possible to downgrade from 1.65 to 1.20? it doesn't seem to offer it as an option with assistant 2 (v1.16) |
Hello, I was recently forced into upgrading my M600. I believe the DJI Go app or controller was not letting me fly until I did. I upgraded to what I thought was the most recent about a week or two ago so V1.00.01.65, and it now lets me fly the drone in P-mode. Unfortunately my onboard computer with OSDK 3.2 for ROS is totally messed up. The SDK activates successfully but all of the messages are corrupt. The positions coming in, the rc_channels, pretty much everything has incorrect values. Now, I would like to downgrade to 1.20 but Assistant 2 v1.17 has no options to downgrade. Please let me know what the best way to downgrade is? |
[Mirror of dji-sdk/Onboard-SDK-ROS#146]
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 interface and APIs 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.
The text was updated successfully, but these errors were encountered: