I hope you find a solution. My Phantoms (p4a and p4p) give me that error every time when initializing. I tried manual and auto focus. I leave it on AFC and tell it to ignore the error.
The errors are on p4pros and also on inspire. Last time out the inspire just froze on ‘initialing drone’ 4 times. Had to change the battery restart the app, restart controller, reload missions
I’m using:
DroneDeploy version 4.25.0-4.25.0
DJI Go 4 version 4.3.38
I was using an iPhone 7 and an iPad mini 4
Now I’m using an iPhone XS and an iPad mini 5.
It was doing it on both versions of the phone and mini iPads . The DD app also has trouble starting up and I have restart the app to get it to work.
Somewhat related to this thread re DD focussing error at the start of a mission (it would return to home).
Mavic Pro
Latest iPad and DD software
Flying in desert climate (45C in shade)
SD card: San Disk Extreme Pro (formatted in Go4 in device) 128GB
Flying offline (remote)
Cause:
It took a bit to troubleshoot. At the beginning thought related to offline flight. Reason being I had newly bought 2 SanDisk extreme Pro SD cards for the trip. And I’d tested them prior to the trip in the park and no error. The error of focusing would pop up after some autonomous flights. The drone would fly to the start, then after taking the first pic, error msg and then RTH. Others had suggested replacing / reformatting the SD card. So what we did was replace one card with another which gave the same problem which threw us of the trail of being SD card related. Fortunately I had brought with me additional SD cards and after I must admit ‘giving up’ and flying ,manually, I swapped the SD card for a RUGGED Pro master 64GB and presto, problem solved during autonomous flights. Maybe it was the hot environment but mental note to self to check if the focus is simply related to the read/write nature, size, or brand of SD card. Hopefully someone out there might be able to shine a more technical reason for the difference in read/write SD behavior I experienced to avoid it happening next time.
I fly wit the SanDisk Extreme Pro MicroSDs all the time, they are formatted before each use, however with DD, there is a catch. Turns out DD wants to see a directory structure in place before using the MicroSD. So before doing a DD flight/mission, simply go into Go4, Litchi, any other app, snap a photo while on the ground, shutdown the app, launch DD and DD should be able to use the MicroSD.
Thanks for the reply. It happened again today with a sd card used before. Samsung 128gb EVO. It was ahead of continuing the mission after a battery changeout. Tried taking a photo in DJI4 and reopening
Restarting apps.
Couldn’t get the camera to focus in DJI4, switch from AF to MF
What I had to do was switch out the SD card for a new one and away it went. There was a problem in DD where it didn’t recognise where it had paused the mission.
Same here, use SanDisk Extreme Pro’s win fmt before each use, however in the past ran into an issue where solution was to snap a photo using Go4, then DD was happy. Its possible that issue has been fixed over the past several months making room for something else to break, or, at least on droid ;).
Haha, there’s a little clue. The Droid version and have an issue with the camera test shot a while back but same here I don’t know if anything ever became of it or if it just went away.
Lol, yup, if its a DD bug, issue or problem its probably tied to a droid issue or limitation, even if it is an ios issue . Will test to see if the microsd card needing to have a file/folder/dir structure on it issue is/was fixed when get a chance.
I have the same problem mission abort due “Focus Calibration Failure” at the mission start point using an Inspire 2 tested with all 3 firmwares available (including latest V01.02.0600) on an iPad (iOS 15.7) Dronedeploy 4.107.0 and an Micasense Altum-PT camera. Tried 3 different SD cards and also flying with no SD card.
With Pix4D Capture I don´t have this issue, same as DJI GO 4, so its a Dronedeploy BUG
. Will test to see if the microsd card needing to have a file/folder/dir structure on it issue is/was fixed when get a chance.