Krugz
lvl.1
Flight distance : 97726 ft
United States
Offline
|
Squashpile Posted at 2018-9-9 07:13
It is not the auto switching between 5.8 and 2.4 I have tested this. It happens on manual too. It MAY be messing up while switching frequencies while on one band. I was manually switching frequencies and I did get a controller lockup. I spent the next 20 minutes manually changing freq trying to replicate it. I could not and got sick of trying.
I had this problem on my first M2P flight. I posted about that a week or so ago. SCared the crap out of me. Now it has happened at least 5 times. Pretty much been scared to fly. I'm going out to another location today to test. I think it could just be massive interference, but you would think it would show on the meters, sign str or warnings.
many of the same issues and more. (see below for a run-down of the last 3 days sinc I got my new M2P) not a single clean flight yet. P3S never had a problem at all, even at the end of its range and RTH because of signal loss. Whats up here?
Got my mavic 2 pro 3 days ago and unbelievable errors. Not a single safe flight yet. Started with firmware updates that weren't possible with the app. Had to get them through the assistant. Then constant emmc full errors. Couldn't format card because it wouldn't connect. App kept asking to link, but it would fail. Finally got it to connect long enough to format, then it must have erased the firmware because it needed an update again. Got it to work through the app that time. Got a 6 minute flight because so much battery was used trying to connect. Try to fly today, several mag interfer errors from several rural locations. Wouldn't connect. Asked to link. Link failed....deleted app and reinstalled. Got it to connect. Flew 1000 ft and rc disconnected. Controller was connected so no RTH, video or app connection. Used the RTH button, then pause and landed it manually. Tried again later. Saw controller connect then disconnect several times. Finally got a solid "go fly" and no firmware banner. Went into camera mode, stayed stable for a decent time so I took off. Kept it low and close. Within 3 minutes and 30' away, disconnected again. This time didn't respond to the controller at all. Didn't want to hit the RTH button because branches were above it. Rc kept connecting and DC. Got a "landing" message but couldn't react before DC. Finally, not sure how, got it to land. Not even safe to fly and no idea why.....everything is up to date but nothing stays connected. App, rc, nothing.
Is this a compatibility issue? The only other option available to me is an ipad, but it seems to be the RC and the app failing at times. |
|