-
Notifications
You must be signed in to change notification settings - Fork 32
FAQs
- Getting the logs
- What programs do you recommend for stitching?
- Why does video feed disconnect in the GO app after I open DronePan?
- What firmware should I install to use DronePan?
- DronePan will not connect to my device?
- How can I share my DronePan panorama to the web?
- Can I shoot HDR / AEB bracketing with DronePan?
- Is DronePan the most amazing app ever built for drones?
- Is DronePan available on android?
- Which products are compatible with DronePan?
- What are the best camera settings while taking a panorama with DronePan?
- Why do I need to have my drone connected to change settings?
- What is error code 209 when DronePan tells me to move my switch to F position?
- I shot multiple panoramas during the same flight, and I’m having trouble delineating between the sets of photos?
- I’m testing DronePan on the bench and it is only moving the gimbal up and down?
- DronePan did something weird - how do I report / diagnose the issue?
- There are holes or gaps in my final stitch - what is causing this?
- There’s a funny blue haze/patch in my stitch?
- My Osmo keeps telling me it can’t set gimbal attitude?
- My Drone tells me it can’t set gimbal attitude?
Start the app and head to the settings page. Bottom left corner there’s a copy log to clipboard button
|
Tip
|
Logs are only kept for a few days - so don’t delay too long :) |
There is a known issue wherein users occasionally experience a video feed disconnection in DJI GO app when switching between third party apps and DJI GO. We are working with DJI to address the issue. Until we figure out a permanent solution, we recommend following these steps to avoid video feed disconnection:
-
Fly to the Panorama Point
-
Close DJI Go App with normal Home button
-
Open DronePan
-
Shoot your Panorama
-
Double Tap Home Button
-
Close DronePan Completely
-
Switch to DJI Go
For DronePan to function properly your drone and/or handheld gimbal needs to be on the latest firmware.
When running DronePan for the first time, you need to connect your device to wifi/mobile network so that your device can register with DJI’s servers. This should only be needed the very first time.
You have a few options:
-
add it to your site by uploading the stitched .jpg .swf .js and .htm output files
-
send us a DropBox folder containing files mentioned in above, and we’ll reply with a link
-
create an account at one of the following: 360cities.net, round.me, Holobuilder.com
DronePan currently supports AEB. In order to use AEB you need to enable 3 shot AEB in GO.
Phantom 3, Phantom 4, Inspire 1 with X3, Inspire 1 with X5®, Osmo with X3, Osmo with X5®.
We will try to add all new devices but we often need to wait for DJI to release an upgraded SDK first.
Although ideal settings will vary based on conditions, manual exposure is a MUST, and we also recommend locking the white balance.
DronePan has various settings (number of rows, shots per row etc) and it depends on which type of device you have as to which settings are relevant. To do this - it saves your settings per device type - so if you have both an Inspire and a Phantom they have separate settings. So - it needs to know what device is connected to know what settings to show and where to save them.
DronePan relies on the flight mode switch to operate. To be able to yaw the aircraft the switch must be in the F position to let DronePan control your aircraft. If you see error code 209 there’s a good chance you’ll need to enable multiple flight modes in the DJI GO app. Just toggle into GO and flip your switch a few times. You will be prompted to enable multiple flight modes. Click OK and then switch back to DronePan. You should now be able to capture your panorama. NOTE: this should be done while on the ground.
I shot multiple panoramas during the same flight, and I’m having trouble delineating between the sets of photos?
We’ve run into this issue ourselves in testing, and it is exacerbated by the vertical columns as it isn’t quite as easy to quickly identify the variance from one pano to the next. Unfortunately, at the moment the DJI SDK does not allow us to access the memory card so haven’t found a way to group by folder or rename from one pano to the next.
Our personal tricks include:
-
looking at the GPS data in the EXIF data, so if you shoot from slightly different locations GPS can be used to delineate
-
glance at the time stamps in hopes of identifying any sizable window between panos
-
point at something (e.g. yourself) and take a single shot.
Of course these are not reliable long term solutions and we will continue investigating a pano ID method.
DronePan currently only supports aircraft yaw method. Due to a newly discovered bug in the SDK we were required to temporarily remove gimbal yaw support for the Inspire. Work is in progress on bringing this back.
Let us know :) The easiest way is via our Facebook group. You can also submit an issue via our issues list.
We don’t want it doing weird things either but we do need some help:
-
What actually happened? "It didn’t work" doesn’t give us a lot to go on
-
What version of DronePan are you running - see Settings (button top right) and note the version (lower right corner)
-
What DJI device are you running and which firmware version is it on
-
What does the DronePan log say - see Settings (button top right) > Copy log to clipboard (lower left corner) and then share the log via some online paste service (pastebin, github gist, anything that allows you to paste in text content and send us a link).
Beware that stitching software often has issues establishing control points if you shoot over smooth water or clear blue skies. You can check this by looking to see if there are any images left out of the stitch or left in odd positions.
In the first 10 months of DronePan we had a missed shot bug where aircraft would occasionally ignore the commands for gimbal movement or yaw given by the app, but that bug is mostly dead now due to extensive retry logic.
In most cases now - a missed shot is either ignored (the stitcher couldn’t see that it was linked so didn’t include it) or badly positioned (the stitcher has placed it wildly incorrectly but behind other shots). In this case you’ll need to work with the stitching software controls to include it and place it correctly.
However it is definitely possible the missed shot SDK bug will still occur occasionally. We are constantly optimizing the app to prevent this.
If you’ve got a sky photo that is pretty clear - then the stitcher has difficulty. It seems that quite often the stitcher just leaves it in the middle of the shot not linked to anything else - but it still does a merge of the colour leaving a nice blue smear. Check to see if you have a non-linked sky shot and move it to where it should be.
The angles that the unit tells us about are relative to the angle of the handle of the Osmo itself. But - the SDK does not allow us to find out what that angle is. Make sure that you’ve got the Osmo handle as near vertical as you can and this should stop happening. Some more tips on getting good Osmo panoramas
This can be caused by DronePan trying to photograph above the horizon when this hasn’t been enabled in DJI Go.
You can fix this by telling DronePan not to go to a higher angle than the horizon or you can enable the setting in DJI Go.
To set the horizon limit in DronePan:
With your drone connected and DronePan running - click on the settings cog in the top right. If it’s showing sky row then switch to horizon.
To enable the setting in DJI Go:
Enable +30 gimbal tilt
This does not apply to the Inspire models.
DronePan has not managed to get your drone to change the gimbal attitude - the angle setting for all three axes (note that it’s attitude - not altitude).
So - this means that we’ve told the drone 5 times to change the angle the gimbal is pointing (its attitude) and it hasn’t done so.
In a little more detail - the process starts with us saying
-
move to this angle and do it in this length of time
The drone also sends us constantly a stream of what the current angle is (as well as lots of other information) - so we watch the incoming data and check to see if it has moved. We’ll wait as long as the time specified for the move plus half a second.
If it hasn’t moved to the right place - we’ll ask again. Up to 5 times. If it simply refuses to move the gimbal within 5 times then we assume that it’s not going to listen and stop the run.
Why doesn’t the drone do as it’s told sometimes? We don’t know. We know only two things - one is that it took the command without returning an error the other is that it hasn’t moved the gimbal. It has given us no other error or warning either :(
Soft landings, DP Team