Mavic mini starting order

[Dbez1]

We’ve had em and members dogged em and they left.
Well being active members anyway. Sure they read here though.
How you think they come up with all the new features .?

Too bad they left. Hopefully they’re monitoring though. Thanks for the information.

 

[old man mavic]

if all these methods work ,then surely unless you have issues with how you do it,does it really matter how you do it, it is a personal thing to individual pilots,and their choice

 

[slup]

Too bad they left. Hopefully they’re monitoring though. Thanks for the information.

Yeah ... but they can be a bit frustrating, some times I wonder if it's actually real people behind their posts ?

 

[DanMan32]

Another reason to have the app up first is so you are sure you have a USB connection between phone/app and RC. Your app is likely to auto start anyway once the RC is connected.

 

[Deleted member 114292]

That sequence suggests that those instructors never needed (or probably never knew about) the mobile device DAT file data. If you care about that then you want the app running and connected to the RC before the aircraft powers up, which is what I always do.

Are you saying the DAT file never gets created if the AC is on first or that items might be missed?

 

[Hodge]

i guess we are all different
my method is rc connected to device first (then turn on rc)
when screen says rc connected start drone
then wait for the screen to change to the camera view
and then i always turn off the drone first
i guess it stems from my early RC days when you always started the controller first then your plane car boat etc and then turned things off in reverse as it prevented someone from taking control of your plane car etc if they were on the same frequency and it has stuck

The Phantom 3 manual says to start the controller, then the app on the phone then the drone.
In theory it prevents the drone from doing something unexpected like having the blades startup while your holding the drone.
from the P3 manual
Takeoff/Landing Procedures
1. Place the aircraft in an open, flat area with the battery level indicators facing towards you.
2. Turn on the remote controller and your mobile device, then turn on the Intelligent Flight Battery.
3. Launch the DJI GO app and enter the Camera page.
4. Wait until the Aircraft Indicators blink green. This means the Home Point is recorded and it is now safe
to fly. If they flash yellow, the Home Point has not been recorded.
5. Push the throttle up slowly to take off or use Auto Takeoff.
6. Shoot photos and videos using the DJI GO app.
7. To land, hover over a level surface and gently pull down on the throttle to descend.
8. After landing, execute the CSC command or hold the throttle at its lowest position until the motors stop.
9. Turn off the Intelligent Flight Battery first, then the Remote Controller.

So by habit I just do the same thing with the mini.
But looking thru the user manual and quick start guide they have the order of start the drone then start the controller

 

[dirkclod]

Yeah ... but they can be a bit frustrating, some times I wonder if it's actually real people behind their posts ?

View attachment 96453
View attachment 96454

Yes when your in thier forum ya never know.
The member that was here was.I have had phone and e mail conversations and is in America. Lake Tahoe .Now I also know if you call the California number it is rerouted to Asia. They sound like they’re English but they’re not. The repair facility is here
though.

 

[slup]

Are you saying the DAT file never gets created if the AC is on first or that items might be missed?

No, you miss the data from the part before the RC/app comes on.

 

[Deleted member 114292]

The Phantom 3 manual says to start the controller, then the app on the phone then the drone.
In theory it prevents the drone from doing something unexpected like having the blades startup while your holding the drone.
from the P3 manual
Takeoff/Landing Procedures
1. Place the aircraft in an open, flat area with the battery level indicators facing towards you.
2. Turn on the remote controller and your mobile device, then turn on the Intelligent Flight Battery.
3. Launch the DJI GO app and enter the Camera page.
4. Wait until the Aircraft Indicators blink green. This means the Home Point is recorded and it is now safe
to fly. If they flash yellow, the Home Point has not been recorded.
5. Push the throttle up slowly to take off or use Auto Takeoff.
6. Shoot photos and videos using the DJI GO app.
7. To land, hover over a level surface and gently pull down on the throttle to descend.
8. After landing, execute the CSC command or hold the throttle at its lowest position until the motors stop.
9. Turn off the Intelligent Flight Battery first, then the Remote Controller.

So by habit I just do the same thing with the mini.
But looking thru the user manual and quick start guide they have the order of start the drone then start the controller

M2 with smart controller has a feature called "fly immediately" which if the AC is on and paired it gos right into the Go 4 app.
If your AC is on first the controller pairs right after power up.

 

[Deleted member 114292]

No, you miss the data from the part before the RC/app comes on.

I see well usually for me not too much happens before the RC/app are fired up.
I suppose you could cook up some odd scenario but I can think of one off the top of my head.

 

[bmwbob]

The recommended (and taught in all pilot schools) ..
1st Turn on accessories (tablet, mobile, etc.)
2nd Turn on RC
3rd Turn on aircraft.
4th Open Flight App.
To turn off ..
1º .- Check flight records.
carry out the rest of the processes in reverse order.

Basically that's what I do! Iphone's already on. Start the controller and mini and they sync before running shortcut

 

[slup]

I see well usually for me not too much happens before the RC/app are fired up.
I suppose you could cook up some odd scenario but I can think of one off the top of my head.

We actually had a crash case last week here were we initially couldn't understand why a Yaw-magYaw disagreement was true already when the DAT log started ... turned out that the AC was started indoors in a magnetic interfered environment, moved outside & then RC/app was connected... & then up & away sort of.

Don't think it's a so big hazzle if you know the scenario ... but to get a beginner to tell, well another story

But as said earlier ... not a must, but why not

 

[Deleted member 114292]

We actually had a crash case last week here were we initially couldn't understand why a Yaw-magYaw disagreement was true already when the DAT log started ... turned out that the AC was started indoors in a magnetic interfered environment, moved outside & then RC/app was connected... & then up & away sort of.

Don't think it's a so big hazzle if you know the scenario ... but to get a beginner to tell, well another story

But as said earlier ... not a must, but why not

Curious which model was it?

 

[slup]

Curious which model was it?

MA

 

[Deleted member 114292]

MA

Because I've done that with my M2 before and when it gets outside it corrects itself - it's a bad idea and I don't do that anymore, thanks to all I have learned here.

 

[sar104]

Because I've done that with my M2 before and when it gets outside it corrects itself - it's a bad idea and I don't do that anymore, thanks to all I have learned here.

Whether or not anything gets corrected is a completely different issue than whether or not the important data are in the log. To see those data requires the app to be running when the aircraft powers up. The M2 is currently unique in being able to recognize that magnetic yaw / IMU yaw separation on takeoff indicates an incorrectly initialized IMU, but it will only apply that immediate correction if it isn't moved after initialization.

 

[dirkclod]

Whether or not anything gets corrected is a completely different issue than whether or not the important data are in the log. To see those data requires the app to be running when the aircraft powers up. The M2 is currently unique in being able to recognize that magnetic yaw / IMU yaw separation on takeoff indicates an incorrectly initialized IMU, but it will only apply that immediate correction if it isn't moved after initialization.

I knew that.?

 

[Deleted member 114292]

Whether or not anything gets corrected is a completely different issue than whether or not the important data are in the log. To see those data requires the app to be running when the aircraft powers up. The M2 is currently unique in being able to recognize that magnetic yaw / IMU yaw separation on takeoff indicates an incorrectly initialized IMU, but it will only apply that immediate correction if it isn't moved after initialization.

Yeah I knew that (Or at least I just learned that ) was trying to morph it back to the original topic of starting order. But if starting order creates an issue It would be interesting to know how serious that issue is. So In some cases it can create a yaw discrepancy.
That I did not know.

 

[sar104]

Yeah I knew that (Or at least I just learned that ) was trying to morph it back to the original topic of starting order. But if starting order creates an issue It would be interesting to know how serious that issue is. So In some cases it can create a yaw discrepancy.
That I did not know.

No - starting order won't create an issue. Moving the aircraft after starting it may prevent the M2 from correcting a yaw error though. That said - if you follow the usual advice of checking the orientation arrow on the map to ensure that it is pointing in the right direction then the error won't occur in the first place.

 

[Deleted member 114292]

No - starting order won't create an issue. Moving the aircraft after starting it may prevent the M2 from correcting a yaw error though. That said - if you follow the usual advice of checking the orientation arrow on the map to ensure that it is pointing in the right direction then the error won't occur in the first place.

That’s interesting because I always wondered to what degree of accuracy this method is and how important is that. How accurate is your eye?

I know standing at my door which way is north or can pull out my iPhone which seems to be pretty accurate but to what degree of accuracy does it really need to be.