Recent content by prz3mk0

and goggles with 0015 or 0020 will allow you to take off without drone firmware update? I would call it a clear oversight on DJI part, they released 0020 for the drone to kill certificate hack and once downgrade was possible bumped ARB on 0015 to prevent downgrade yet on goggles that are...

so one can have hacked drone, presumably on recommended firmware, and goggles on 0015 or 0020 and still working certificate hack? or are we just discussing FCC hack?

what firmware do you have on goggles?

As far as I read somewhere (maybe here), it has to be DJI's OTG cable, or in other words, someone tried a different one and it wasn't working. So if you connect goggles to iPhone/iPad with Fly app and nothing happens this might be the reason.

make sure you're using the DJI OTG cable that came with the combo

Need to investigate further... the concerning part is that I immediately tried to switch to N mode and I couldn't - if my memory serves me right the N on screen became red and then black when it switched to Normal after few seconds.

Did you try to refresh just the RC firmware using DJI Assistant 2 (for FPV Series) or DJI Assistant for Consumer Drones?

Did you ever narrow it down to confirm it was caused by the card? I have the same card for over a year and even though I wasn't recording I just got the sensor system error. It did clear on it's own. Just like you I was in manual. It was a first flight in a while and first ever flight with...

There are a few tricks to make this option show up, first one to try is to take your computer offline and connect goggles to DJI Assistant 2 (DJI FPV Series). Let us know if it worked.

you also have "inconsistent battery firmware".... you have 4 AC with exactly the same issue???

You can downgrade the AC with DH app, which should be enough to bypass NFZ and altitude limit with DH license if this is what you're looking for.

also please be aware there are limitations to obstacle slowing, be careful with the wall, if it is a solid color slowing might not work, few weeks ago there was a video of the newest Mavic 3 flying into a solid white wall

the setting is in Settings / Safety - Obstacle Slowing, I think you can still fly into something - it is slowing not stopping, also there are exceptions when obstacle slowing wouldn't work, check manual

It might not be MC firmware, maybe said option was introduced in one of the newer Googles FW, didn't you stay on the older one? I will check mine in the evening and post what I see along MC and Googles FW.

Considering everything that so far has been said here, if the master does broadcast wouldn't that: - increase video latency? would that be visible in the recordings from master and slave googles? - shorten runtime of master googles? Also, why would you get any pixelization on slave granted...