Did you do a factory reset?
And don't touch SC when plugging in? (step 3 and 4)
Also, you might try first uninstalling/reinstalling Assistant first and using the provided DJI USB cable.
Yes, I tried all of & still a no go
Did you do a factory reset?
And don't touch SC when plugging in? (step 3 and 4)
Also, you might try first uninstalling/reinstalling Assistant first and using the provided DJI USB cable.
Success!
Factory reset completed.
SC updated to newest .0650.
Assistant 2 working.
Method I did:
1) Reformatted SD card
2) Factory reset
3) Start DJI Assistant 2
3) Turn on SC (USB debug is on by default. If not, turn it on) and plug into computer
4) DON'T select USB transfer method/charging - don't touch the SC!
5) It will 'bing-bong' twice, and DJI Assistant 2 will now show SC
6) click the SC, and on the version screen, select .065 refresh
7) It will do it's thing, pausing awhile at 16%, and at 98% then will reboot 2x
8) will then come up with 100% complete
I tried so many things.
Last thing I did was uninstall Assistant and remove all registery entries.
No luck.
Interesting thing:
RM500.cfg file location changed to: Internal shared storage\encrypt
and reads:
<?xml version="1.0" encoding="utf-8"?>
<dji>
<device id="rm500">
<firmware formal="01.00.0650">
<release version="01.00.0650" antirollback="1" antirollback_ext="cn:3" enforce="0" enforce_ext="cn:0"
So, seems the .cfg file reading .0560 is part of the problem with failed updates.
My first SC failed update, when then doing the Litchi install, the SC popped up a message something like you said 'package installer closed'.I updated mine and everything went just fine. 100% completed and after connecting to the M2P everything still looks good.
BUT then I tried to install Litchi (update) and guess what the PACKAGE INSTALLER keeps stopping. I tried other application packages NO LUCK!
It looks like DJI (intentionally?) broke the package installer. I downgraded to the previous version - everything looks good and the installer works fine on the old version.
Has anyone tried this after the update? Am I the only one running into this issue?
1) reformat: Settings / Storage - SD Card - FormatingCapt’n I just got off the phone with DJI & they want me to send in my SC. I don’t really want to do this. I’m going to try your method again but I have a couple of questions.
1. Reformat the SD card. What is this & how do I do it
2. USB debug is on by default. How do I check this?
Thanks for your time
Just as a sideline question, I do not want this update so how do I prevent all future updates of any kind on my smart controller when near a wifi connection like at home?
The flight records are now saved to Internal memory even if you have 'save to SD card' setting:I successfully updated to 650 using Assistant. Everything seems to be okay with one exception. AirData HD Sync no longer, well, syncs. I verified that the Token is good. Have WiFi connection. Press Sync and it says it synced. But the Total Files Uploaded does not change, nor do my recent flights appear on AirData. Any ideas?
The flight records are now saved to Internal memory even if you have 'save to SD card' setting:
Internal shared storage\DJI\dji.go.v4\FlightRecord
If you want to have them sync,
in the SC file manager, browse to that location/file(s), long press it, and move (or copy) to:
SD card\DJI\dji.go.v4\FlightRecord
Now it will show up on the home page flight records and can be synced
You can go to Display in the Main Settings and change the screen timeout to a max of 30 minutes, I believe. You can also keep tapping the darn screen. Good luckWhile trying to update the smart controller using assistant 2, when the update gets to 16% the controller shuts off. I've tried several times with different computers.
Thanks eran - but another NEW update 1/16 may have 'fixed' the log location problem?We're working on an updated version of the Airdata app to accomodate this change in the DJI firmware, so you won't have to do this manually. It should be ready in the next day or two.
Thanks for letting me know about the new update from today. I don't see it available on our device here yet. Do you know what version is it?Thanks eran - but another NEW update 1/16 may have 'fixed' the log location problem?
Might check that out.
Its the same version number, just a new date 1/16.Thanks for letting me know about the new update from today. I don't see it available on our device here yet. Do you know what version is it?
Either way, our update should accommodate both cases.
We use essential cookies to make this site work, and optional cookies to enhance your experience.