RichJ53 Posted at 2017-7-13 07:16
Hi Donnie

Yes, the DJI goggles are worth the money! They are much nicer than my Fatshark Dominators HD goggles and cheaper.

Hey Donnie, Where is tis flying field located? Where is the link? I want to approach our city to build one just like this. I thank you in advance for your assistance. Cordially

Kiffkool Posted at 2017-7-14 09:27
Donnie ,
Is the consensus that this FW is good to go then ? The apps have updated automatically but i have yet to update the H/W ..can i fly as usual ?
Chris.

Yes , I would update in this order if you have not done so yet.

do the Ac first then The RC. , then the New  Go app last

that is how I am going to do it .

donie

New firmware, everything is OK I had zero problems and everything works! Safety First! Ken.

Citation Posted at 2017-7-14 13:16
Hey Donnie, Where is tis flying field located? Where is the link? I want to approach our city to build one just like this. I thank you in advance for your assistance. Cordially

Link to Club

we built this field about 28 years ago and lease the land from the county.

Rich

After more than a year hiatus from my Inspire 1, I decided to break it out again and get back to flying.  First thing I did was try to update the firmware, but I keep getting a failure.  I may have made the mistake of formatting my SD card on the computer (not from the camera) and loading it with the latest all in one FW v01.11.01.50 from v1.04.00.10.  I am unable to reformat in the camera because my RC won't even connect with the Inspire 1.  What options do I have??

I can't stress IMU cal enough. Don't forget to do it. After the update I noticed gyroscope mode was at 0.10. Not sure if the .10 is enough to crash the Inspire. Just in case, I ran the IMU cal once. Allowed it to sit turned off so it can cool for 10 min. Then performed the IMU cal a second time to be safe. Now the gyroscope mode is at 0.00 and acceleration is at 1.00 and fluctuates from 0.99-1.01.

Ouch... Got my second hand Inspire 1 v1 this morning.  Previous experience:
PH1, PH Vision + V2, PH3Pro, P4 were at least the P3Pro has been upgraded a couple of times and the P4 once.


The following happened:

- Seller said it had been flown 2 weeks ago. (Not by him though)
- Start all up. Video link was alternating "Weak link" and "image loss"
- After checking cables and rebinding the RC I had a look at the versions installed.

AC 1.11.01.50
RC 1.6.0+
App 3.1.12

- I upgraded  the app to the very latest as per today
- I upgraded the RC to the latest as per today.

The lost and weak video link were gone and all looked very OK except it complained the AC FW needed an upgrade.
I checked the AC version and it said "Version unknown. Camera says 1.10.01.40

- Formatted the SD card in the AC and downloaded the latest firmware
- With he RC off I started up the AC. It goes to the "updating AC noise and runs for about 4 minutes then there is a continuous sound, and the LED at the back is continuing flashing yellow.
- The upgrade log just says:

========== 2014.01.01 00:00:07 remo-con disconnect======
Packet: WM610_FW_V01.11.01.50.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

- AC FW still says "unknown version"

I have given the update over 20 minutes but the result is the same.

What's next?

Is there a lower FW available somewhere to try out with for example?
Should I try updating with my other X3 camera which I use to my Osmo or will that maybe brick something.
Should I try upgrade the camera separately in my Osmo or will that brick anything?

Best I think would get the hands ov some earlier version FW.. or?

Thanks for any input!  (Have been spending 4h with this and was supposed to try it out in the air..)
half an hour later:

Found a previous version. Failed after 4 mnts too:

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.10.01.40.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.


uoch...


10 minutes later:

Found this thread about "version unknown":

https://forum.dji.com/thread-77919-1-1.html

Is it a DJI server problem?   Supposing my bird won't upgrade to the same version or the version below..

Håkan K Posted at 2017-7-15 03:48
Ouch... Got my second hand Inspire 1 v1 this morning.  Previous experience:
PH1, PH Vision + V2, PH3Pro, P4 were at least the P3Pro has been upgraded a couple of times and the P4 once.

Ok  I am a bit confused , in one sentence you say you are Now updated and then further down it says you are trying to update ?  

It looks to me like you are updated, now can you start the motors from the AC from the Rc transmitter and are you getting data from the AC ?

If NO , you may need to re link the AC to the RC .  You can do this via the Go app in remote control settings .

If you wish , you could rollback the AC to the previous FW  ( In sequential order ). so this would be version 1.10). I believe that is still on the firmware page .

Do Not update camera via OSMO

Are you using the X3 camera currently and is it the same one you did the original update with ?
Heere is a link regarding any video issues

Video Transmission issues with X3 or X5 ? Try These Suggestions !
also link to my tips page with Link instructions

Tips for Load NEW firmware to RC and AC- Insp. 1 Phantom ADV & PRO


Let me/us know

donnie

Donnie * Posted at 2017-7-15 04:34
Ok  I am a bit confused , in one sentence you say you are Now updated and then further down it says you are trying to update ?  

It looks to me like you are updated, now can you start the motors from the AC from the Rc transmitter and are you getting data from the AC ?

I updated  the RC. And trying to update the aicraft and there it fail. When I start all up it seems to work OK. Except saying  firmware in AC need to be updated. I haven't tried to spool up the motors but I will after having read your link.  A question. If I have the latest FW on SD card and start up the AC., what is supposed to happen then? As it is now it appears the update  procedure starts and goes on for about 4 mnts but then just a looooooong never ending noise..

Came to the part using the drop down to select FW from your link. Is it maybe this I should use: WM610_FC350Z_FW_V01.11.01.50.zip having a X3 camera? The one I downloaded first was just the one I saw on the page....

Edit:

No I have the correct one for X3, the one on he first page says:

Inspire 1 Firmware v01.11.01.50 (X3)


If attempting to downgrade and see if the AC FW stop updating as with the latest version. I should be able to just load Inspire 1 Firmware v1.10.1.40 on the SD and start up the AC? That was what I attempted to do but the upgrade seems to fail in the very same way.

Updated my inspire 1 and 2 controllers with 5 batteries all appears to be fine. Going to also calibrate the IMU

Håkan K Posted at 2017-7-15 04:47
Came to the part using the drop down to select FW from your link. Is it maybe this I should use: WM610_FC350Z_FW_V01.11.01.50.zip having a X3 camera? The one I downloaded first was just the one I saw on the page....

Edit:

Tried these but exactly the same issue and about 4 mnts into the process..


========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.10.01.40.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.


========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.09.01.30.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

Ok. The full lok looks like the following:

[00006763]========== remo-con disconnect. boot(15) ============
[00006845]Packet [C:\WM610_FW_V01.11.01.50.bin] detected, card sn [0x834b84b1].
[00006929]Packet upgrade start...

[00007032]Packet checking...
[00007121]Packet vlink 01.11.0150 <-> 01.11.0150.
[00007210]Record vlink 01.08.0100 <-> 01.07.0090 (flow = 0).
[00007338]Done.

[00007420]Version checking[1]...
[00007531][04 00][00] v1.30.1.43 -> v1.30.1.43
[00007622][08 00][00] v2.14.9.42 -> v2.14.9.42
[00007709][01 00][00] v2.70.5440 -> v2.70.5440
[00007792][01 01][00] v2.70.5440 -> v2.70.5440
[00007912][03 05][00] v34.1.0.5 -> v34.1.0.5
[00008032][03 06][00] v2.4.20.50 -> v2.4.20.50
[00008272][05 00][00] v3.0.6.2 -> v3.0.6.2
[00008362][09 00][00] v5.0.0.0 -> v5.0.0.0
[00008471][11 00][00] v3.9.0.0 -> v3.9.0.0
[00008612][12 00][00] v1.11.0.0 -> v1.11.0.0
[00008733][12 01][00] v1.11.0.0 -> v1.11.0.0
[00008872][12 02][00] v1.11.0.0 -> v1.11.0.0
[00008992][12 03][00] v1.11.0.0 -> v1.11.0.0
[00009138][15 00][00] v1.1.2.0 -> v1.1.2.0
[00009253][17 00][00] v0.0.0.0 -> v1.1.0.8 need upgrade.
[00009352][17 01][00] v0.0.0.0 -> v2.0.1.6 need upgrade.
[00009443][19 00][00] v1.0.8.96 -> v1.0.8.96
[00009526]Done.

[00011623]Waiting for user confirm...
[00021711]Timeout, start upgrade automatically.

[00021838]Firmware upgrading[1]...
[00021931][17 00] Firmware upgrade start...
[00054405][17 00] Firmware upgrade finished successfully.
[00054495][17 01] Firmware upgrade start...
[00077602][17 01] Firmware upgrade finish failed (step = 5, err = 0x21, sum = 0x94b8).
[00087683]Done.

[00087763]Version checking[2]...
[00087850][04 00][00] v1.30.1.43 -> v1.30.1.43
[00087934][08 00][00] v2.14.9.42 -> v2.14.9.42
[00088018][01 00][00] v2.70.5440 -> v2.70.5440
[00088102][01 01][00] v2.70.5440 -> v2.70.5440
[00088225][03 05][00] v34.1.0.5 -> v34.1.0.5
[00088344][03 06][00] v2.4.20.50 -> v2.4.20.50
[00088465][05 00][00] v3.0.6.2 -> v3.0.6.2
[00088555][09 00][00] v5.0.0.0 -> v5.0.0.0
[00088665][11 00][00] v3.9.0.0 -> v3.9.0.0
[00088804][12 00][00] v1.11.0.0 -> v1.11.0.0
[00088924][12 01][00] v1.11.0.0 -> v1.11.0.0
[00089064][12 02][00] v1.11.0.0 -> v1.11.0.0
[00089184][12 03][00] v1.11.0.0 -> v1.11.0.0
[00090147][15 00][00] v1.1.2.0 -> v1.1.2.0
[00090245][17 00][00] v0.0.0.0 -> v1.1.0.8 need upgrade.
[00090365][17 01][00] v0.0.0.0 -> v2.0.1.6 need upgrade.
[00090456][19 00][00] v1.0.8.96 -> v1.0.8.96
[00090535]Done.

[00090618]Firmware upgrading[2]...
[00090709][17 00] Firmware upgrade start...
[00126803][17 00] Firmware upgrade finish failed (step = 3, err = 0xaa).
[00136886][17 01] Firmware upgrade start...
[00179468][17 01] Firmware upgrade finish failed (step = 2, err = 0xaa).
[00189612]Done.

[00189688]Version checking[3]...
[00189775][04 00][00] v1.30.1.43 -> v1.30.1.43
[00189870][08 00][00] v2.14.9.42 -> v2.14.9.42
[00189952][01 00][00] v2.70.5440 -> v2.70.5440
[00190032][01 01][00] v2.70.5440 -> v2.70.5440
[00190156][03 05][00] v34.1.0.5 -> v34.1.0.5
[00190276][03 06][00] v2.4.20.50 -> v2.4.20.50
[00190395][05 00][00] v3.0.6.2 -> v3.0.6.2
[00190520][09 00][00] v5.0.0.0 -> v5.0.0.0
[00190635][11 00][00] v3.9.0.0 -> v3.9.0.0
[00190755][12 00][00] v1.11.0.0 -> v1.11.0.0
[00190895][12 01][00] v1.11.0.0 -> v1.11.0.0
[00191015][12 02][00] v1.11.0.0 -> v1.11.0.0
[00191175][12 03][00] v1.11.0.0 -> v1.11.0.0
[00191319][15 00][00] v1.1.2.0 -> v1.1.2.0
[00203899][17 00][06] device not detected.
[00216480][17 01][06] device not detected.
[00216568][19 00][00] v1.0.8.96 -> v1.0.8.96
[00216648]Packet upgrade failed at version checking.

My own interpretation of the above failed update log is the Vision Positioning System Module is broken or can't be contacted during upgrade. (found a pdf somewhere describing the
17 00 and 17 01 to be the VPS) All other modules seems to have been updated. Except getting a T6 torx screwdriver. Is it difficult to remove it to check if there is something loose? The cable from it that goes into the powerboard seems to be attached OK.

Hero22 Posted at 2017-7-14 18:10
After more than a year hiatus from my Inspire 1, I decided to break it out again and get back to flying.  First thing I did was try to update the firmware, but I keep getting a failure.  I may have made the mistake of formatting my SD card on the computer (not from the camera) and loading it with the latest all in one FW v01.11.01.50 from v1.04.00.10.  I am unable to reformat in the camera because my RC won't even connect with the Inspire 1.  What options do I have??

UPDATE:  Still have not managed to update the the firmware in the AC, but I did confiirm that my RC is linking with the AC even though the light on my RC is mainly red with very quick flashes of green.  I know this because I am able to contol the camera (up/down) and also take pictures/video even though I cannot enter camera mode in the DJI Go app to see what I am doing.  I also read somewhere that FW updates to the RC before v1.3 must be done via the USB and not the GO app.  However, that does not seem to be working either - I plug in my SD with FW v01.11.01.50 via the USB port, power up, and nothing happens. I then discovered people saying that the USB ports are failing?!?  WTF.  I appreciate ANY guidance whatsoever.

Is there any way to check the FW version of the RC without using the DJI Go app?  As mentioned above, I cannot enter the camera mode on the app and therefore am unable to check this.

Håkan K Posted at 2017-7-15 09:27
My own interpretation of the above failed update log is the Vision Positioning System Module is broken or can't be contacted during upgrade. (found a pdf somewhere describing the
17 00 and 17 01 to be the VPS) All other modules seems to have been updated. Except getting a T6 torx screwdriver. Is it difficult to remove it to check if there is something loose? The cable from it that goes into the powerboard seems to be attached OK.

Ok, I am not sure why the system wont let you downgrade, looks like you have the proper Firmware and all .

Regarding this : A question-  If I have the latest FW on SD card and start up the AC., what is supposed to happen then?  

What can happen is the video can be affected and Or also the video module .  this is NOT the case for you as  lines 0800 and 1500 would be effected with a "Device Not Detected '  on these lines of code .

Have you tried your other  x3 camera by any chance ?

donnie

donnie

Hero22 Posted at 2017-7-16 04:34
Is there any way to check the FW version of the RC without using the DJI Go app?  As mentioned above, I cannot enter the camera mode on the app and therefore am unable to check this.

Ok , sorry I missed your post and did not answer .  Are you still having issues ?  If so when you updated the AC did you also update the RC transmitter as well ?
You can check the version of the FW on the SD card that you loaded to the AC .  Here are some instructions on how to view Hidden file .  
How to View Hidden Files: Tool to  diagnose No signal and SD  Issues

donnie

Donnie * Posted at 2017-7-16 06:11
Ok, I am not sure why the system wont let you downgrade, looks like you have the proper Firmware and all .

Regarding this : A question-  If I have the latest FW on SD card and start up the AC., what is supposed to happen then?  

Well.

I updated the camera in my Osmo as I didn't want my Osmo camera to be bricked. (They are supposedly be interchangable between Osmo and Inspire to my understanding)  Tried the Inspire update again. Found out from the update log the camera got updated from an earlier version to latest version comparing with previous update log. So no issues with the camera. After some hours I found a PDF in the Inspire Pilot forum showing as attached the code <--> module mapping.
Having seen that I checked the app and the height was showing exactly "0". No matter if I lifted the Inpire up 3-5 feets. To further confirm I tried to enable travel mode (many times and with both RC and app) and it just says "click" in the landing gear. I assume it attempt to start lowering but find it already be zero feet above the ground.

So I think the VPS module is faulty. As it never was OK  and although purchased second hand I'm about to get in contact with the seller discussing how to proceed further. as the VPS module is $$ and if for some reason won't help replacing it I'm not sure how we will proceed.

It's probably perfectly OK to fly with as everything else got updated according to the log. And it spool up on the table and whatever else I can do withut having it in the air works OK. I suspect it was flown like this previosly.

Thanks for your help.

Donnie * Posted at 2017-7-16 06:19
Ok , sorry I missed your post and did not answer .  Are you still having issues ?  If so when you updated the AC did you also update the RC transmitter as well ?
You can check the version of the FW on the SD card that you loaded to the AC .  Here are some instructions on how to view Hidden file .  
How to View Hidden Files: Tool to  diagnose No signal and SD  Issues

Thanks for the reply Donnie.  I am still not able to update the FW on the AC and my RC won't enter camera mode to update/check the FW version.  I'm starting to think that my USB port is bad since I can't enter camera mode nor am I able to update the FW version via direct connect to the USB.

Thanks for the info on checking the version of FW on the SD card.  This is the most recent info from that file after I've tried multiple times to upgrade the FW on the AC.  Not exactly sure what to make of it...


[00047670]Firmware upgrading[1]...
[00047774][01 01] Firmware upgrade start...
[00058037][01 01] Firmware upgrade finished successfully.
[00058180][03 06] Firmware upgrade start...
[00304399][03 06] Firmware upgrade finished successfully.
[00304473][17 00] Firmware upgrade start...
[00345889][17 00] Firmware upgrade finished successfully.
[00345955][17 01] Firmware upgrade start...
[00379726][17 01] Firmware upgrade finished successfully.
[00379811][04 00] Firmware upgrade start...
[00433869][04 00] Firmware upgrade finished successfully.
[00433924]Done.

[00433986]Version checking[2]...
[00434078][04 00][05] v1.30.1.43 -> v1.30.1.43
[00446651][08 00][00] device not detected.
[00446711][01 00][00] v2.70.5440 -> v2.70.5440
[00446770][01 01][05] v2.70.5440 -> v2.70.5440
[00446862][03 05][00] v34.1.0.5 -> v34.1.0.5
[00446945][03 06][05] v2.4.20.50 -> v2.4.20.50
[00447145][05 00][00] v3.0.6.2 -> v3.0.6.2
[00447217][09 00][00] v5.0.0.0 -> v5.0.0.0
[00447323][11 00][00] v3.10.0.0 -> v3.9.0.0
[00447423][12 00][00] v1.11.0.0 -> v1.11.0.0
[00447563][12 01][00] v1.11.0.0 -> v1.11.0.0
[00447663][12 02][00] v1.11.0.0 -> v1.11.0.0
[00447763][12 03][00] v1.11.0.0 -> v1.11.0.0
[00460325][15 00][00] device not detected.
[00460401][17 00][05] v1.1.0.8 -> v1.1.0.8
[00460561][17 01][05] v2.0.1.6 -> v2.0.1.6
[00460630][19 00][00] v1.0.8.96 -> v1.0.8.96
[00460695]Packet upgrade failed at version checking.

Håkan K Posted at 2017-7-16 07:25
Well.

I updated the camera in my Osmo as I didn't want my Osmo camera to be bricked. (They are supposedly be interchangable between Osmo and Inspire to my understanding)  Tried the Inspire update again. Found out from the update log the camera got updated from an earlier version to latest version comparing with previous update log. So no issues with the camera. After some hours I found a PDF in the Inspire Pilot forum showing as attached the code  module mapping.

Ok one thing , is the VPS enabled on the go app ? it is under  Main controller settings/ Advanced .  You very well may have a bad VPS but that would not explain why you can't rollback FW and what not .

donnie

Hero22 Posted at 2017-7-16 09:52
Thanks for the reply Donnie.  I am still not able to update the FW on the AC and my RC won't enter camera mode to update/check the FW version.  I'm starting to think that my USB port is bad since I can't enter camera mode nor am I able to update the FW version via direct connect to the USB.

Thanks for the info on checking the version of FW on the SD card.  This is the most recent info from that file after I've tried multiple times to upgrade the FW on the AC.  Not exactly sure what to make of it...

OK, bad news, the Encoder on the camera has failed 0800 of code "device Not detected " and also the USB module on the AC has failed as well 1500 "device not detected". Now  in MOSY cases it is just the 0800 code on the camera that is casing issues and you will need to send the AC camera in for repair , now if they just need to re update the corrupted module it is usually less than 100 US dollars if it is Broken then you may want to just replace the camera with a new one as the repair is close to the cost off a new camera .  I would get an RMA number going and get it in for repair or replace ASAP.

I have NEVER seen a repair for this failure  that the consumer could do .

Sorry

donnie

Håkan K Posted at 2017-7-15 06:12
Ok. The full lok looks like the following:

[00006763]========== remo-con disconnect. boot(15) ============

So besides the VPS not working is the AC and RC communicating with one another ?  Can you start the motors and fly and have Live video ?

If yes and just cant downgrade and what not , have you tried another SD card ?  have you formatted the SD card on the Aircraft first before trying to rollback ?  Are you using a PC and not a MSAC for updating the FW to the SD card ?  

sorry , I just help many  members on this board and others plus email and I get confused .

donie

donnie

Donnie * Posted at 2017-7-17 04:18
Ok one thing , is the VPS enabled on the go app ? it is under  Main controller settings/ Advanced .  You very well may have a bad VPS but that would not explain why you can't rollback FW and what not .

donnie

Yes VPS enebled. regarding the roll back. It's actually roll backl all modules except VPS according to the log. I guess the only way to find out for sure is someone else is rolling back / upgrade without having the VPS connected. But that will probably not happen :-)  

Håkan K Posted at 2017-7-17 08:39
Yes VPS enebled. regarding the roll back. It's actually roll backl all modules except VPS according to the log. I guess the only way to find out for sure is someone else is rolling back / upgrade without having the VPS connected. But that will probably not happen :-)

Re your second update. (I do understand it get a bit much with a lot of issues going on at the same time) I have tried all possible ways in respect to the sd card. Tried several, formatted in the craft etc..) in the end i think the update logs are clear. It's updating (or rolling back) all modules except the VPS.
Edit:

Convinced by the theory the VPS module is broken I ordered one. I let you know the result.

After the update... I noticed the gimbal dance is different now. Not to sure why. I spoke to DJI and showed them the video. They said it's 'normal'. I'm getting no gimbal error at all. Flies fine... Horizon is level. Yet it does the usual gimbal dance around and then right before it finishes... It goes limp and instantly wakes up and spins. Here's the video of what I'm talking about: https://www.dropbox.com/s/kaopb2o4d7rmfk3/20170717_000304_1.mp4?dl=0

Cabralkev Posted at 2017-7-17 19:43
After the update... I noticed the gimbal dance is different now. Not to sure why. I spoke to DJI and showed them the video. They said it's 'normal'. I'm getting no gimbal error at all. Flies fine... Horizon is level. Yet it does the usual gimbal dance around and then right before it finishes... It goes limp and instantly wakes up and spins. Here's the video of what I'm talking about: https://www.dropbox.com/s/kaopb2o4d7rmfk3/20170717_000304_1.mp4?dl=0

Cabralkev, thank you for your feedback, does this issue occur once or every time after updating? Please leave us with the firmware version.

Cabralkev Posted at 2017-7-17 19:43
After the update... I noticed the gimbal dance is different now. Not to sure why. I spoke to DJI and showed them the video. They said it's 'normal'. I'm getting no gimbal error at all. Flies fine... Horizon is level. Yet it does the usual gimbal dance around and then right before it finishes... It goes limp and instantly wakes up and spins. Here's the video of what I'm talking about: https://www.dropbox.com/s/kaopb2o4d7rmfk3/20170717_000304_1.mp4?dl=0

I have confirmed with engineer. Here is the reason of this issue:
Usually during the calibration, the aircraft will send instruction to gimbal to find its position. If the calibration time of aircraft is longer than gimbal, the gimbal will get limp because it doesn't receive the instruction in time.
Then the aircraft finished its calibration and then send instruction to gimbal again, it will move to find his position. This is how it works.
Please calibrate IMU firstly and then gimbal to see if the issue persists.

Håkan K Posted at 2017-7-17 08:42
Re your second update. (I do understand it get a bit much with a lot of issues going on at the same time) I have tried all possible ways in respect to the sd card. Tried several, formatted in the craft etc..) in the end i think the update logs are clear. It's updating (or rolling back) all modules except the VPS.
Edit:

Ok ,let us know ,

donnie

DJI Mindy Posted at 2017-7-18 03:17
I have confirmed with engineer. Here is the reason of this issue:
Usually during the calibration, the aircraft will send instruction to gimbal to find its position. If the calibration time of aircraft is longer than gimbal, the gimbal will get limp because it doesn't receive the instruction in time.
Then the aircraft finished its calibration and then send instruction to gimbal again, it will move to find his position. This is how it works.

Thanks for the feedback. I did the IMU calibration and gimbal calibration 2 times each. I spoke to a DJI agent yesterday, and he said it's normal. He also passed it on to another staff member, and he said it's normal. I believe it's a software issue. The previous firmware didn't have this issue.

DJI Mindy Posted at 2017-7-18 01:53
Cabralkev, thank you for your feedback, does this issue occur once or every time after updating? Please leave us with the firmware version.

I updated to the latest firmware version. I'll post a picture to show you.

DJI Mindy Posted at 2017-7-18 01:53
Cabralkev, thank you for your feedback, does this issue occur once or every time after updating? Please leave us with the firmware version.

I just calibrated the IMU and gimbal again. When I do the gimbal calibration, it stops to the right not facing forward when it's finished the calibration. Doesn't face forward. Why is that? I gotta press C1 so it faces forward.

Here's my theory... There is something wrong with the DJI Go app. The tech department needs to correct this. Here's a video I did an hour ago to prove my theory: https://www.dropbox.com/s/w5y1zi ... 8_171636_1.mp4?dl=0

Cabralkev Posted at 2017-7-18 15:03
Here's my theory... There is something wrong with the DJI Go app. The tech department needs to correct this. Here's a video I did an hour ago to prove my theory: https://www.dropbox.com/s/w5y1zi3am66xn8l/20170718_171636_1.mp4?dl=0

Did you try boot up the craft with only the RC running and without the app started? Or RC running with Litchi started? To see if that make a difference?

Prado Posted at 2017-7-11 05:58
You just have to be logged in, no internet connection required all the time.

What if I get to a farm I normally shoot at, where there is not internet connection and cell service, so therefore can't log in. Am I then limited to the parameters of flying with the new update....

Hi Folks
I've done an update today on my RC for my I1 and it worked OK, using DJI GO App.  It says that both the aircraft and the camera need updating, watch the video.  So I've downloaded the latest FW for the I1, unzipped it, put it across to a cleab SD card, inserted into the camera, turned on and it does nothing.  The I1 comes up like normal, connects, did a small test flight outside, got a critically low power warning on the battery which was showing 60%.  Can anyone assist with what I could try next to upgrade the FW.  Thanks in advance, have tried different SD cards, remote off, remote on etc

Håkan K Posted at 2017-7-18 22:13
Did you try boot up the craft with only the RC running and without the app started? Or RC running with Litchi started? To see if that make a difference?

Like I showed in the video. I first turned on the Inspire. Gimbal did the rotation as it usually does, but this time it was normal. I then turned on the RC and turned on the Inspire, no DJI Go app. The gimbal again rotated fine no issues. Now, I turn on the RC and opened up the DJI Go app, then turn on the Inspire. That's when the gimbal behaves strange. As you can see in the video, it rotates around, then stops a little to the right, goes limp and corrects itself.

I've tested this with the Litchi app. Having the Litchi app opened before turning on the Inspire shows the same symptoms. The gimbal behaves strange. However, the symptoms are far less. The gimbal will rotate around as it's suppose to, then stops a little to the right, then corrects itself. It doesn't go limp, like the DJI Go app does.

There must be something in the DJI Go app that is triggering this. I know Litchi does use most of the coding in the DJI Go app. Might explain why I can see the same symptoms appearing, but far less than DJI Go. Hopefully DJI releases an update soon.

Cabralkev Posted at 2017-7-18 15:03
Here's my theory... There is something wrong with the DJI Go app. The tech department needs to correct this. Here's a video I did an hour ago to prove my theory: https://www.dropbox.com/s/w5y1zi3am66xn8l/20170718_171636_1.mp4?dl=0

Thanks for your updating. we are very sorry about what happened and the troubles caused to you, but the case is the very first one to us worldwide. We will do our best to locate what the problem is and keep you updated. Appreciate your patience.