Warnings on P3S
- Thread starter @albapaterson
- Start date
If you are referring to me, please articulate so we can all benefit from your comment.
Yes I agree with your post. Looks like you edited your wording a bit in the post that I replied to and and I didn't catch that there was a clarification in wording. So now we're on the same page.
Last edited:
Ok, now that we got this sorted out, let's go back to the OP. It seems to me you had 2 unrelated problems.
The first is the "Strong Interference Detected" warnings, which are not uncommon. Some say that DJI GO for iOS is more prone to these, others say that things improved with the latest GO releases. In any case, many seem to suggest to simply ignore them. As for range, you got over 500m which is not bad considering you're in Scotland (CE mode). As always, best thing to do is to try in a different spot and see what results you get (warnings, range).
The second problem is RTH making the AC land "300m from the take off spot". You might want to upload the flight log to Airdata UAV (formerly Healthy Drones), there's plenty of smart people here that are very good at analyzing them. If the Home Point was really not set when you first took off, maybe the AC used the Home Point of a previous flight, which explains why it still landed in a good spot not far from you.There was a version of DJI GO on Android where the Home Point was incorrectly set, but since you're on iOS this does not apply. I would suggest to keep an eye on DJI GO on your next flights and make sure the Home Point gets properly set, then just rule this issue as a one-off.
The first is the "Strong Interference Detected" warnings, which are not uncommon. Some say that DJI GO for iOS is more prone to these, others say that things improved with the latest GO releases. In any case, many seem to suggest to simply ignore them. As for range, you got over 500m which is not bad considering you're in Scotland (CE mode). As always, best thing to do is to try in a different spot and see what results you get (warnings, range).
The second problem is RTH making the AC land "300m from the take off spot". You might want to upload the flight log to Airdata UAV (formerly Healthy Drones), there's plenty of smart people here that are very good at analyzing them. If the Home Point was really not set when you first took off, maybe the AC used the Home Point of a previous flight, which explains why it still landed in a good spot not far from you.There was a version of DJI GO on Android where the Home Point was incorrectly set, but since you're on iOS this does not apply. I would suggest to keep an eye on DJI GO on your next flights and make sure the Home Point gets properly set, then just rule this issue as a one-off.
- Joined
- Sep 3, 2016
- Messages
- 14
- Reaction score
- 1
- Age
- 55
I was using the DJI Go app, but normally use Litchi. I will try the Healthy drone data upload when I return home. I'm sure it's pilot error.
Was getting a battery temp warning tonight as well as the interference warning, but it was a bit cold on the coast. And I didn't risk a long flight as it was off the cliff.
Also black and white lines on parts of the video feed on the sky which was annoying
Was getting a battery temp warning tonight as well as the interference warning, but it was a bit cold on the coast. And I didn't risk a long flight as it was off the cliff.
Also black and white lines on parts of the video feed on the sky which was annoying
- Joined
- Sep 3, 2016
- Messages
- 14
- Reaction score
- 1
- Age
- 55
It is like the whole of the sky will be black & white stripes. I thought the exposure must be wrong at first.
zebra stripes ? it's the exposure warning , turn off in GO APP
- Joined
- Feb 24, 2017
- Messages
- 65
- Reaction score
- 8
- Age
- 61
You don't need the device to have gps in order to set home point with the bird OR the RC. I use an ipad air 2 without gps and never had an issue. What you need to make sure you do is cache the map in advance of where you're going to fly. It automatically knows your location and home point. It uses the birds gps. When you connect bird to the rc it knows its location and the bird. Never had issues
RodPad
Premium Pilot
@albapaterson
"Also black and white lines on parts of the video feed on the sky which was annoying"
Just in the sky and not on the video?
"zebra stripes ? it's the exposure warning , turn off in GO APP"
Yep, Yep
Rod
"Also black and white lines on parts of the video feed on the sky which was annoying"
Just in the sky and not on the video?
"zebra stripes ? it's the exposure warning , turn off in GO APP"
Yep, Yep
Rod
This pretty much answers all of your questions.
The warnings are software related and don't affect flight. Nobody knows why the standard gets them.
- Joined
- Sep 3, 2016
- Messages
- 14
- Reaction score
- 1
- Age
- 55
I'll try caching the map next time, I didn't have a good 3G or 4G signal on the coast so this would make sense. Thanks for explaining,
Ace, just turned the Over exposure warning off.
Thank you [emoji2][emoji2]
Ace, just turned the Over exposure warning off.
Thank you [emoji2][emoji2]
Very confused and confusing post, on something that we already clarified. In any case:
- You do need a device with GPS to re-set the Home Point to the RC position; if your device does not have GPS, you can only re-set the Home Point to the current AC position, as the RC has no knowledge of where it is.
- Caching the maps has nothing to do with the way Home Point works or is set or re-set.
- Home Point at startup is set to the AC position, stored in the AC and communicated to DJI GO; the RC never "knows its location and the bird".
We're definitely diverging from the original question, but you do raise a good point: Follow Me is only available with GPS-enabled devices.
Late to the thread, I'd add it's always a good idea to take a screen capture on your flying app device of a problem or unknown message when it happens, for later verification of exact wording or showing others the 'problem' you may seek help from. For example the "zebra lines" may be exposure warning, but could also be signal interference.
The standard gets them because the Standard uses WiFi for video, and there is a ton of WiFi interference everywhere. When the P3S senses WiFi interference, it warns you. You can decide to ignore it, if you want, but it's an indication that you can lose the video feed.
We discussed this recently in another thread, but nobody responded: why are you (we) assuming that these messages are related to the 2.4Ghz band? Could they be also about 5.8Ghz interference? And if they are indeed related to Wi-Fi, are they raised when multiple networks are generically detected in the area, or specifically when there are other networks operating on the same channel the P3S is on? And is interference detected by the AC or RC?
Similar threads
