Ошибка компаса dji spark


 

#1

OFFLINE
 

Antoniostr

    Начинающий летчик

  • Пользователи
  • Pip

  • 28 сообщений
  • Город:Зеленодольск
  • Коптер:Dji Mavic PRO

Отправлено 14 июня 2017 — 09:40

Во время полета периодически выскакивает «Compass error. Exit P-GPS Mode» плюс ко всему, когда даже нет ошибки — коптер плохо держится на месте, как говорят в сети его «унитазит» (вращается по своей оси) Плывет горизонт.

А если ошибку выдает то может вообще начать двигаться самопроизвольно в какую-нибудь сторону.

Почитал в интернете про эту проблему и многие пишут про намагниченный компас и про устройство cfixer, которое это все лечит.

Эта проблема — основная, которая приводит к падению и потерю ваше коптера. Давайт разберем подробно эту тему. Какие есть устройства, где их купить, как сделать и помогают ли они.

Вот описание проблемы и работы устройства на одном из сайтов:

«Сколько раз вы видели на экране вашего планшета в программе DJI GO надпись Compass Error ? И эта зловещая надпись Exit GPS Mode ((

Особенно страшно, когда коптер далеко и нет визуального контакта с ним.

Любой коптер компании DJI не может работать в режиме GPS (удержания позиции) без правильно работающего компаса. 

Вот несколько случаев вывода компаса из строя:

Полет рядом с опорами ЛЭП (вблизи 30ти метров)

Установка коптера на капот автомобиля (особенно это касается DJI phantom 3)

Случайная «дружба» компаса вашего Коптера с магнитом (даже кратковременная)

Полет внутри помещений с большим количеством металла (производственные цеха, заводы, склады)

В последствии вы увидите такие симптомы:

Частое появление Compass Error

Невозможность пролететь коптером по прямой

При полете по маршруту — камера смотрит немного в сторону

«Туалет» при висении на месте

 Завал горизонта камеры при поворотах

Поднесите CFixer к компасу и нажмите кнопку. Через 15 секунд ваш компас будет приведен к заводскому состоянию.

Выйдите в «чистое поле» и выполните калибровку Компаса по инструкции DJI.

В некоторых случаях требуется калибровка ИМУ. Выполните ее на ровной поверхности согласно инструкции DJI. Затем выполните калибровку Подвеса.

В дальнейшем вам не понадобится калибровать Компас. Если Полетная программа просит вас это сделать, просто поднимите коптер с земли или поменяйте место взлета.

Применяйте CFixer каждый раз, после полета рядом с металлическими конструкциями, ЛЭП, внутри цехов или складов. И при появлении симптомов намагниченного компаса.

После применения CFixer не забывайте калибровать компас в чистом поле.

Теперь полеты на Коптерах DJI стали намного безопасней!»

Прикрепленные изображения

  • 0


 

#2

OFFLINE
 

sirus

sirus

    Начинающий летчик

  • Пользователи
  • Pip

  • 5 сообщений
  • Город:Нижний Новгород

Отправлено 14 июня 2017 — 12:33

Я вот стал жертвой этой ошибки. Подробно написал о своей ошибке в другой теме — http://dji-club.ru/i…mavic/?p=115793

Летать стало невозможно и пока решения не нашел. Кто-нибудь пробовал cfixer с этой ошибкой? Успешно?

  • 0


 

#3

OFFLINE
 

Fixxxer

Fixxxer

  • Город:Екатеринбург
  • Коптер:Mavic Pro

Отправлено 14 июня 2017 — 02:36

У меня у друга все эти симптомы были — ошибки компаса, не летел по прямой, унитазинг итп

Всевозможные калибровки и прошивки не помогли, CFixer не помог.

4bf759578e679d0bb00ce4f48fc4a04d.jpg

Помогла только замена переднего компаса (который в 1 блоке с GPS приемником)

5b12956535b85812ace364884d33e26e.jpg5d4cfef80b173381f5a0838d411755ac.jpg

Сообщение отредактировал Fixxxer: 14 июня 2017 — 02:36

  • 0


 

#4

OFFLINE
 

Avrmich

Avrmich

  • Город:Tomsk
  • Коптер:MavicProCombo

Отправлено 14 июня 2017 — 05:05

Всегда смотрим показания датчиков и компаса в DJI GO4!!!!! Если зеленые ито ничего делать не надо!!! Только сменить место полета!! Если компас хоть чуток желтого цвета ( а тем более красного) — несколько движений обыкновенным магнитом на расстоянии 3-5 см от компасов… перезагруз и калибровка) …. до зеленых значений!!

Имею «Фиксер», но его нет под рукой, когда нужен!

  • 0


 

#5

OFFLINE
 

Kelmak

Kelmak

    Начинающий летчик

  • Пользователи
  • Pip

  • 31 сообщений
  • Город:санкт-петербург
  • Коптер:mavic

Отправлено 14 июня 2017 — 07:09

Смотрел видео там простым магнитом все решалось:)

  • 0


 

#6

OFFLINE
 

Antoniostr

Antoniostr

    Начинающий летчик

  • Пользователи
  • Pip

  • 28 сообщений
  • Город:Зеленодольск
  • Коптер:Dji Mavic PRO

Отправлено 14 июня 2017 — 08:44

У меня все шкалы показывают нормальные цифры, но при полете иногда ошибка возникает.

когда разбирал коптер оторвал пару проводов от платы компаса 1, припаяли, стало лучше, но ошибка не исчезла.

Добавлено позже (14 Июнь 2017 — 20:44)

Fixxxer,

Этот компас находится в задней части коптера. 

  • 0


 

#7

OFFLINE
 

maxkoud

Отправлено 15 июня 2017 — 03:54

  • 0


 

#8

OFFLINE
 

Parcifall

Parcifall

  • Город:Moscow
  • Коптер:Mavic air/pro

Отправлено 15 июня 2017 — 11:47

maxkoud,Да.. интересное исследование..

Но ошибка-то живёт!

Мой сегодня как взбесился.. на ровном месте стоять не мог.. мотало во все стороны.. а компасы зелёные..

постоянно просил перезагрузить коптер..  хотя при наличии ошибки летает вобщем-то одинаково, что без нее..

это глюк получается, если намагничивание компаса — бред ?!

может солнечные бури )

  • 0


 

#9

OFFLINE
 

Fixxxer

Fixxxer

  • Город:Екатеринбург
  • Коптер:Mavic Pro

Отправлено 17 июня 2017 — 10:06

Этот компас находится в задней части коптера.

в мавике 2 компаса, в передней части и в задней.

тот что в передней части основной, фото выше, находится он в 1 блоке с GPS,

а 2й компас выглядит вот так

b8007a1c2e14c190546905b6f6f8ccbd.jpg

Были постоянные переключения между компасами, не висит на месте, не летит по прямой итд

9296076c39a8ddb29cb91216a715924c.jpg

После размагничивания cFixer’ом последующей калибровки показания в приложении становятся зеленые но через полчаса опять проблема возвращалась.

Помогла только замена блока, сейчас все прекрасно.

Так что cFixer может и помогает в каких-то случаях, но не во всех.

  • 0


 

#10

OFFLINE
 

Parcifall

Parcifall

  • Город:Moscow
  • Коптер:Mavic air/pro

Отправлено 17 июня 2017 — 10:13

Fixxxer,Замена только заднего компаса?

  • 0


 

#11

OFFLINE
 

Fixxxer

Fixxxer

  • Город:Екатеринбург
  • Коптер:Mavic Pro

Отправлено 17 июня 2017 — 10:35

Parcifall,

повторю, помогла только замена переднего компаса.

задний тоже меняли, но это ничего не дало

  • 0


 

#12

OFFLINE
 

Parcifall

Parcifall

  • Город:Moscow
  • Коптер:Mavic air/pro

Отправлено 17 июня 2017 — 12:26

Fixxxer,У меня прикол в том, что они всегда зеленые.. подобная ошибка выскакивает чаще после взлёта..

Причем летал среди гаражей — держится ровно летит прямо.. а в небо поднимаешь выдаёт ошибку.. короче работает нестабильно. 

  • 0


 

#13

OFFLINE
 

sirus

sirus

    Начинающий летчик

  • Пользователи
  • Pip

  • 5 сообщений
  • Город:Нижний Новгород

Отправлено 17 июня 2017 — 02:05

Короче говоря, я обновился на .800, откалибровал imu, компас, и все стало ок, на сколько это возможно. Его немного унитазит и не всегда летит ровно, но хоть теперь держится ровно. 

  • 0


 

#14

OFFLINE
 

Fixxxer

Fixxxer

  • Город:Екатеринбург
  • Коптер:Mavic Pro

Отправлено 18 июня 2017 — 02:52

подобная ошибка выскакивает чаще после взлёта

потрясите его на месте, тоже должна выскочить)

Добавлено позже (18 Июнь 2017 — 17:52)

Видяшка о работе компаса

  • 0


 

#15

OFFLINE
 

Parcifall

Parcifall

  • Город:Moscow
  • Коптер:Mavic air/pro

Отправлено 18 июня 2017 — 11:31

Сегодня в парке полетал.. ни разу не ругнулся  :sad:

поднимался до 500.. потом в гаражах летал.. мистика 

  • 0


 

#16

OFFLINE
 

Gonzo070

Gonzo070

  • Город:Нижний Новгород
  • Коптер:Mav

Отправлено 21 июня 2017 — 05:04

  • 1


 

#17

OFFLINE
 

N00B

N00B

  • Город:Moscow
  • Коптер:Небесный Нубас

Отправлено 21 июня 2017 — 05:32

видяшка с продолжением)))

Про винтик понятно, интересен другой момент

В общем как я и говорил что калибровку компаса надо выполнять с уверенностью что в месте калибровки нет магнитных полей и других наводок т.к. компас калибруется и выдает «зачёт» в любом случае лишь полагаясь на правильность действий пользователя. Затем в воздухе начинаются проблемы с отвалом спутников и с переходом в ATTI b и как следствие полетом в сторону

  • 0


 

#18

OFFLINE
 

Gonzo070

Gonzo070

  • Город:Нижний Новгород
  • Коптер:Mav

Отправлено 21 июня 2017 — 05:58

creep,

у меня же мысль такая — компас после калибровки находясь с намагниченным болтом (пусть так) в ноле…. ок.

Далее в полете влияние этого болта на работу одинаково, намагниченность его же не скачет, он просто рядом, и компас спокойно работает измеряя отклонения (или чего он там измеряет) с учетом этого влияния, давая стабильные показания. ИМХО.   

  • 0


 

#19

OFFLINE
 

N00B

N00B

  • Город:Moscow
  • Коптер:Небесный Нубас

Отправлено 21 июня 2017 — 06:54

у меня же мысль такая — компас после калибровки находясь с намагниченным болтом (пусть так) в ноле…. ок.

Я же начал со слов что «Про винтик понятно», я имел ввиду совсем другое — калибровка подтверждается в любом случае если правильно покрутить дрон, а вот внешние факторы в месте калибровки не могут быть учтены. Т.е. если откалибровать с намагниченным винтиком, а летать без винтика, примерно как то так. И соответственно если калибровка выполняется перед полетом, то показания компаса в норме не смотря на предполагаемые аномалии в данном месте, а стоит улететь как компас начинает давать неверные показания

Сообщение отредактировал creep: 21 июня 2017 — 06:57

  • 0


 

#20

OFFLINE
 

Gonzo070

Gonzo070

  • Город:Нижний Новгород
  • Коптер:Mav

Отправлено 21 июня 2017 — 08:03

creep

Все верно. в реалиях так и происходит.

  • 0

dji spark

Let us calibrate. Let us avoid. Let Us Drone. Calibrating the compass on your DJI Spark is very important to do as your drone needs to know which direction it is facing. First, let’s look at how to calibrate the compass.

To calibrate the compass on a Spark, follow these five steps:

  1. Tap on settings>MC settings>advanced settings>sensors>compass.
  2. At the bottom, you will see “calibrate”. Tap on that. 
  3. When prompted by the app, hold the aircraft horizontally and rotate 360 degrees. The status indicator lights should turn green. 
  4. Now hold the aircraft vertically with the nose pointing down and rotate 360 degrees. 
  5. If the status indicator lights turn red at any point, the calibration has failed. Move to a different location and try again. 

This subject gets brought up so frequently because of how important it is to take-off and fly without compass errors, but how often do you really need to calibrate it? Let’s dive into what the compass does, common errors, and when you should calibrate.

When should you calibrate the compass on Spark?

If you have been around the drone scene for a few years then you have certainly heard many different answers to this question. Some say that you should calibrate the compass before every flight, while others say that that’s unnecessary, or downright ludicrous. Most of us agree that it is smart to calibrate your compass when initially setting up your drone for the first time.

DJI recommends that you calibrate the Spark’s compass when the DJI GO 4 app or status indicator lights prompt you to do so.

People recommend that you calibrate the compass on the Spark when you travel a distance away from the last spot you flew. How far of a distance, exactly? Some say more than thirty miles, while others say fifty, and still, others say one hundred miles from the last spot you flew. DJI does not discuss this in the Spark manual, which I find interesting as they do in manuals of other drone models. 

Now, is it going to hurt your Spark if you calibrate it more often than necessary? No, it shouldn’t, but it’s also not necessary. Some say that you run the risk of throwing something out of whack when you calibrate a drone more frequently than DJI’s suggests to.

I have to say that my wife (Hailey) and I just did a road trip across the country and I did quite a bit of drone flying. Knowing full well that it’s recommended to calibrate the compass if you’re traveling, I decided to conduct a little test. I was only going to calibrate my drone if I got an error in the DJI GO 4 app.

After traveling for almost 3900 miles without not one compass calibration, I had not one compass error while flying. Granted, I didn’t take off near any large metal objects, but still, I was impressed. Was this a responsible test that I conducted? Eh, probably not, but I was curious as to what would happen while constantly flying in a new location for about two weeks straight.

Related questions

Should you also calibrate the IMU while calibrating the compass? You have likely seen a few comments about the importance of calibrating the IMU on your drone. To find out how to do this, check out my post-DJI Drone IMU Calibration: When and How You Should Do It.

Should you get DJI’s Care Refresh with your new drone? Learning how to fly a drone can be an intimidating endeavor, and buying an extended warranty may be wise for some. I cover in detail DJI’s Care Refresh in this post-DJI Care Refresh: The Ultimate 2019 Guide.

What is the role of the compass?

The compass gives the drone it’s bearing, or in simpler terms, it lets the drone know which way the nose is facing. 

Why is this important while flying your Spark? Imagine that you are flying along and the drone suddenly loses connection from your RC. When the drone commences its RTH sequence, you’re going to have some issues if the drone thinks that north is actually south.

Your Spark uses GPS and the compass when performing an RTH operation, but the bird will get conflicting information from these two systems if it doesn’t know which way it’s going.

What objects cause compass interference for your Spark?

When calibrating the compass, it is extremely important to do so in an open area, free of obstruction. So, what kind of objects may cause compass calibration errors? 

Ferromagnetic materials, such as nickel, iron, and cobalt should be avoided. DJI mentions that cell phones often have ferromagnetic materials in them, and they suggest that you don’t carry them in your pocket when calibrating the drone. I find this interesting that DJI specifically mentions cell phones, because, well, we have to use our cell phones (or tablets) to perform the calibration process. I guess they are saying “don’t have three extra phones hanging out near the drone during the compass calibration, bud”. 

If you want to be overly cautious about the cell phone thing, you can have someone hold the RC with the phone/tablet while you have the drone about 10 feet away, or you can set the drone on the ground and walk over to it when you tap “calibrate” in the app. 

Here’s a list of other objects that should be avoided while performing the calibration. Understand that this isn’t a complete list, but it contains some of the most common objects we encounter in our environment. 

  • Large metal structures
  • Rebar (this may be an easy one to not realize you’re close to)
  • Parking structures 
  • Steel reinforced basements 
  • Cars
  • Bridges (I attempted to calibrate in the middle of a very large bridge once. It didn’t go well. I never did perform a successful calibration.)
  • Scaffolding 
  • Any electromagnetic fields

An area of discussion that doesn’t seem to have a conclusive answer is smart-watches. Does that Apple or Samsung watch that you’re wearing cause interference? Some people claim that their smart-watch makes a difference, while other’s say that this is nonsense. 

I wear a Garmin watch, which is technically a smart-watch, but in a class where the Apple watch gets straight A’s, the Garmin is more of a C kind of student. I don’t seem to have any compass issues with my C average watch. 

I’d say that if you want to be on the safe side, take off the smart watch. It would also be smart to perform a test to see if the watch causes problems. 

You can actually see if the compass has any interference before you calibrate your Spark. To do this, open the DJI GO 4 app and go to settings>main controller settings>advanced settings>sensors>compass.

dji compass interference

This screenshot was taken from a Phantom 4 Pro. This page will look slightly different for the Spark.

There have been so many discussions on where the best location is to calibrate the compass on a drone, and the truth of the matter is that it will be difficult to truly escape all forms of interference when you’re in an urban environment. 

People have joked that the best spot to calibrate the compass on your drone is in the middle of a cornfield while you’re in your birthday suit. But don’t get too close to those to those gigantic metal rolling structures that water the field;).

Calibrate, or just move?

Something that I should note is that calibrating the compass near an object that is causing interference will not simply make the errors disappear. 

It may be tempting to see a compass error on the GO 4 app and immediately think that the remedy is to calibrate it. Don’t do this. You are likely just too close to some metal object and the proper course of action would be to move a few feet away and see if the errors go away. 

Calibrating a compass that is already calibrated and in good working order only gives the drones compass an opportunity to get worse, not better. 

In-flight signs that you should calibrate the Spark’s compass

If you are cruising around with your Spark and the drone suddenly enters ATTI mode, there is a good chance that this is because of a compass or GPS problem.

You may also experience the “toilet bowl” effect, which is when the drone starts spinning on its axis instead of keeping its nose facing forward as it should.

You may get a notification in the DJI GO 4 app while flying that lets you know there is compass interference, but this doesn’t always happen. I was having problems with my drone a while back that we’re a bit confusing at the time. 

I would be flying along with 18+ satellites and I would suddenly get an error that the drone lost GPS and was now entering ATTI mode. This was extremely frustrating as it would happen at the most random times, usually when I least expected it. In fact, I remember thinking that I would for sure lose GPS on one occasion when I only had 8 satellites. To my surprise, the drone remained in P-mode for the entire flight. 

This was frustrating conundrum because I didn’t have much faith in the consistency of my drone, and I was alway on guard thinking that the AC would go into ATTI mode at any moment. 

When I started calibrating my drone on a more regular basis I noticed that this occurence would happen less often. Even if I didn’t get a compass error, I would calibrate it and wouldn’t lose GPS while flying as often. Does it still happen occasionally? Sure, but probably because I live in San Diego and it’s difficult to escape all forms of interference when in or near a large city. 

If your Spark does enter ATTI mode while you’re out flying, immediately panic! No, I’m totally kidding…panicking is the last thing you should do. When a drone is in ATTI (attitude) mode, you will need to fly it manually as GPS is not available. The drone will maintain its altitude but will drift with any wind.

This is a good reason to not fly too far from your location if you have a weak GPS signal or are getting compass errors. If the drone is just a tiny speck off in the distance, you will have to fly it back solely using the image transmission on your phone or tablet, and we all know how laggy that image can be.

If you lose GPS and happen to have the aircraft disconnect due to signal loss, you’re going to be in a lot of trouble as the drone will have no clue how to return to home. If you’re newer to flying or would like a refresher, I would strongly recommend reading Drone Flyaways: 14 ways to Prevent Them, and Best 17 Drone Flying Tips for Every DJI Beginner.

One last note about ATTI mode. I can guarantee with almost complete certainty that there will come a time when you have to fly in ATTI mode unexpectantly. To prepare yourself for this, you have a couple of options. If you own a Phantom or Inspire, you can toggle ATTI mode on the controller.  I would recommend practicing in ATTI mode while you’re in an open area with a lot of room for error. It’s not easy at first, but every seasoned drone pilot has a working knowledge of ol‘ ATTI and knows how to control her when necessary.

If you don’t have a drone that allows you to manually enter ATTI mode, you may want to buy a cheap drone that will behave like a drone in ATTI mode, as this experience will go a long way in preparing you for the occasion when your Spark loses GPS. 

How to check if there are compass errors on your Spark

Before you fly, the GO 4 app may display a compass error. If this is the case, follow the instructions listed at the beginning of this post and calibrate the compass in an area with no interference. Remember, there is a difference between the app telling you to calibrate the compass and that there is magnetic interference nearby. If the app is just letting you know that there is interference, move locations and see if the warning disappears

Here is an example of the DJI GO 4 app telling me to calibrate the compass.

calibrate the compass dji

And here is an example of the DJI GO 4 app telling me that I need to try taking off from a different location and that there may be metal or magnetic objects nearby. 

magnetic interference dji compass

You may also get a compass error while you are flying. If this is the case, I’d strongly recommend landing as soon as you can and proceed with calibrating the compass.

Alternating red and yellow blinking lights on the aircraft also indicate that a compass calibration is needed. 

If you continue to get compass errors despite trying to calibrate in multiple areas, I’d recommend trying this course of action:

1- Check for any firmware updates. Just remember that firmware updates are often large so complete the update when you are near Wi-Fi. 

2- If all firmware is updated and you are still getting compass errors, I’d try deleting and re-installing the DJI GO 4 app. In theory, this wouldn’t rectify the problem because the compass is on the drone itself and not the GO 4 app, but there’s a chance that the compass is completely fine and the app is just displaying unfounded errors.

Detailed Spark compass calibration steps

So if after changing locations the app is still prompting you to calibrate the compass, it’s time to go through the calibration process. The five steps listed in the beginning are the main points, but here is where we get into the step-by-step instructions. 

Step #1- Bring your drone, remote controller and phone or tablet to an open area free of metal or magnetic objects. 

Step #2- Power on the RC, then the drone. 

Step #3- Tap on settings in the upper righthand corner. 

settings dji go 4

Step #4- Tap on main controller settings in the top left.

main controller settings dji go 4

Step #5- Scroll down and tap advanced settings at the bottom.

advanced settings dji go 4

Step #6- Tap on sensors. 

sensors dji go 4

Step #7- Toggle over to Compass at the top.

compass interference dji go 4

Step #8- Tap on calibrate compass at the bottom. 

calibrate compass dji go 4

Step #9- Press start when prompted. 

start compass calibration dji go 4

Step #10- Begin the calibration by rotating the drone horizontally in a counterclockwise direction, parallel with the ground. You can stop when the status indicator lights flash green. 

rotate horizontally dji compass calibration

Step #11- Next, rotate the drone on its side and rotate the aircraft 360 degrees vertically in a counterclockwise direction. Again, you can stop when the status indicator lights turn green. 

rotate vertically dji compass calibration

Step #12- Congrats, you’ve successfully calibrated the drone’s compass! If the compass errors don’t disappear, move locations and try to re-calibrate. 

Trevor’s Take

You know, sometimes I just wish that nothing had to be calibrated on my drones and I could just whip them out wherever and whenever I wanted, but that’s not technology. The amount of engineering that has gone into making these drones operate as well as they do is astounding. Really, this is what has set DJI apart from the rest. They’ve managed to put the best technology and engineering into their drones at an affordable price point. When you cram that much technology into a flying device that fits in the palm of your hand, it’s asinine to think that the aircraft will fly perfect one hundred percent of the time without any maintenance (calibration). 

Have you had any compass errors on your Spark? What was your experience and were you able to resolve the issues? I’d love to hear about it in the comment section below!

DJI Compass error is another common DJI drone error. Users have been asking for solutions for this error for a long period of time in every DJI drone forum. Also, this error is a serious one and affects drone take-off.

Hence, this error can’t be ignored, this needs to be fixed as soon as possible. Therefore I started researching the error through forums, articles, and videos. Luckily I was able to collect information about why the DJI Compass error is thrown and how to fix the compass error. Hopefully, this article will help with fixing your DJI Compass error.

Causes For DJI Compass Error.

1. Placing the DJI Aircraft near an electromagnetic field.

Placing the aircraft near an electromagnetic field is the common reason why users confront the error. Once the DJI aircraft is placed near a magnetic field, it assumes the artificial magnetic field as the earth’s natural magnetic field. Then it pops “Compass Error” when the drone checks its orientation against its GPS position and finds a discrepancy. That’s why you need to calibrate the IMU and compass if you carried the aircraft to a different location cause it might have been placed near an electromagnetic field.

2. Miscalibrated DJI Compass.

miscalibrated compass is another reason for DJI compass error. Calibrated DJI Compass is essential for safe aircraft flight. Therefore once the aircraft detects miscalibrated compass it throws the compass error.

3. Firmware glitches.

Firmware is the software of the drone which manages data and actions of the drone (including calibrating the compass and informing errors to the user). So if the firmware is glitched it might cause an improper compass calibration or faulty data which ultimately causes DJI Compass error.

4. Temporary or permanent faulty settings.

If the aircraft has stored faulty compass data, it also could cause compass error. So those settings need to be cleared or back to the factory settings to fix the error.

5. Damaged or faulty compass.

If you have crashed the drone recently or you just bought the drone and face this error even after calibrating the compass, the compass component might have been damaged or faulty.

6. DJI mobile application error.

The DJI mobile app is the medium that informs aircraft errors to the users. So it’s better to suspect that DJI mobile app (DJI GO/ DJI Fly) glitch could cause throwing faulty error, even though the compass is all right.

Next, we would go through step by step procedure to fix the compass error by clearing the reasons for the DJI compass error. So follow these steps to clear the causes of the DJI compass error and ultimately fix the DJI compass error.

1. Restart the DJI Aircraft.

As I said before temporary faulty compass data might cause the compass error. Therefore you need to clear the temporary faulty setting by restarting the aircraft. Restart the aircraft and check whether the error is gone.

2. Update DJI mobile app ( DJI GO/ DJI Fly)

Having an outdated or glitched DJI mobile app causes faulty compass calibration or faulty error communication which ultimately might cause the error. Therefore we need to update the DJI mobile app (DJI GO/ DJI Fly) before going next steps.

How to update DJI GO/ DJI Fly app.

Android users.

If you are android user, you have to install DJI GO/ DJI Fly app manually. Never install DJI apps on the Playstore. Because most of the time they are glitched and DJI doesn’t publish their apps on Playstore.

  • Uninstall the current DJI GO/ DJI Fly app from your device.
  • Visit the DJI Downloads center and click on the app for your DJI drone. Then you will be directed to the download page.
  • Then click on the Android icon and the “.apk” file would be downloaded to the Downloads directory of the device.
  • Once it is completely downloaded, visit the Downloads directory of the device and click on the downloaded “apk” file. Then you will be directed to the apk installation process according to your OS. follow those steps and wait until it is completely installed.

IOS users.

IOS users can install/ update the DJI GO/ DJI Fly app on Appstore because DJI officially releases their apps on Appstore.

  • Visit Appstore and search the app name on the search bar. Once the right app is appeared Then click the “GET” button and install/update the current app. If you are struggling with searching the app on the Appstore, Visit the DJI Downloads center and click on the app for your DJI drone. Then you will be directed to the download page. After that click on the IOS icon and the DJI app’s Appstore screen would be opened.

3. Calibrate DJI Compass.

As I said before if your DJI drone’s compass is miscalibrated, the compass error is thrown. So let’s see how to calibrate the DJI Compass properly. Check whether the error is gone after the compass is calibrated.

How to Calibrate DJI Compass.

  1. Move to a different location if you are getting the Compass error.
  2. Power on the DJI aircraft and remote controller.
  3. Open the DJI App (DJI GO / DJI Fly) and enter the camera view.
  4. DJI GO users click on the three dots at the top left corner and click on the drone icon go to Main Controller Settings > Advanced Settings > Sensors > Compass and hit the “Calibrate Compass” button.
  5. If you are using the DJI Fly app click on the three dots at the top right corner and open the menu bar. Then click on “Safety” and scroll down until you found the ”Compass normal” under the “Sensors” section. Then click on the “Calibrate” button. And hit start.
  6. Then put the remote controller away where you can see the app screen.
  7. Take the aircraft into your hands and hold it horizontally and about 4 feet away from you. DJI aircraft’s indicators should be light yellow right now. Then spin around 360 degrees until those indicators turn to solid green.
  8. After that, hold the drone vertically and spin again around 360 degrees until indicators turn to solid green.
  9. Then place the DJI drone down and you are ready to go.
  10. If the DJI drone indicator lights blink red and yellow alternatively after calibration, this means that it has failed. There could be a high level of magnetic interference. Change location and try the calibration again.

4. Update/ Downgrade firmware using DJI Assistant 2.

If you are still getting the compass error after calibrating the compass, next you must try calibrating the compass after updating the firmware using the DJI Assistant 2. I personally like to update the DJI firmware using the DJI Assistant 2 PC application because there is a low risk of glitched firmware updates.

  1. Download and install DJI Assistant from the DJI Download center.
  2. Power off the aircraft and connect to the computer through the charging port using a micro USB cable.
  3. Power on the aircraft.
  4. Open DJI Assistant 2 application on the PC and log in to your DJI account.
  5. Then select your DJI Drone and click on the “Firmware Updates” on the left panel and click on the “Upgrade” option.
  6. Click on “Start Update”.
  7. Wait until the firmware is completely downloaded and the firmware update process would start automatically.
  8. Follow the same steps to update the controller’s firmware.

Once the firmware is successfully updated or refreshed, calibrate the compass again as explained in step 4.

5. Factory reset the aircraft.

As I explained before, If your aircraft have stored permanently faulty compass settings or data, it also could cause this error. So you need to reset the aircraft to the default settings for clearing those faulty settings or data.

How to Factory Reset DJI aircraft.

  • Download and install DJI Assistant 2 and connect the aircraft to the PC and turn it on. Open DJI Assistant 2 application and log in to your DJI account. Once you logged choose DJI drone and hit “Factory Restore Defaults”.

After factory resetting the aircraft, calibrate the compass as explained in step 4. Then check whether the error is gone.

6. Contact DJI Support.

Read the detailed article: How to get DJI Support to repair/fix your DJI drone issue.

If you are still struggling with the compass error, your aircraft’s compass is damaged or faulty. So you might need to repair or replace the compass. There are tons of videos about replacing different DJI drone’s compass on the youtube but I think it’s advisable to contact DJI Support for replacing or repairing the compass.

dji spark

Let us calibrate. Let us avoid. Let Us Drone. Calibrating the compass on your DJI Spark is very important to do as your drone needs to know which direction it is facing. First, let’s look at how to calibrate the compass.

To calibrate the compass on a Spark, follow these five steps:

  1. Tap on settings>MC settings>advanced settings>sensors>compass.
  2. At the bottom, you will see “calibrate”. Tap on that. 
  3. When prompted by the app, hold the aircraft horizontally and rotate 360 degrees. The status indicator lights should turn green. 
  4. Now hold the aircraft vertically with the nose pointing down and rotate 360 degrees. 
  5. If the status indicator lights turn red at any point, the calibration has failed. Move to a different location and try again. 

This subject gets brought up so frequently because of how important it is to take-off and fly without compass errors, but how often do you really need to calibrate it? Let’s dive into what the compass does, common errors, and when you should calibrate.

When should you calibrate the compass on Spark?

If you have been around the drone scene for a few years then you have certainly heard many different answers to this question. Some say that you should calibrate the compass before every flight, while others say that that’s unnecessary, or downright ludicrous. Most of us agree that it is smart to calibrate your compass when initially setting up your drone for the first time.

DJI recommends that you calibrate the Spark’s compass when the DJI GO 4 app or status indicator lights prompt you to do so.

People recommend that you calibrate the compass on the Spark when you travel a distance away from the last spot you flew. How far of a distance, exactly? Some say more than thirty miles, while others say fifty, and still, others say one hundred miles from the last spot you flew. DJI does not discuss this in the Spark manual, which I find interesting as they do in manuals of other drone models. 

Now, is it going to hurt your Spark if you calibrate it more often than necessary? No, it shouldn’t, but it’s also not necessary. Some say that you run the risk of throwing something out of whack when you calibrate a drone more frequently than DJI’s suggests to.

I have to say that my wife (Hailey) and I just did a road trip across the country and I did quite a bit of drone flying. Knowing full well that it’s recommended to calibrate the compass if you’re traveling, I decided to conduct a little test. I was only going to calibrate my drone if I got an error in the DJI GO 4 app.

After traveling for almost 3900 miles without not one compass calibration, I had not one compass error while flying. Granted, I didn’t take off near any large metal objects, but still, I was impressed. Was this a responsible test that I conducted? Eh, probably not, but I was curious as to what would happen while constantly flying in a new location for about two weeks straight.

Related questions

Should you also calibrate the IMU while calibrating the compass? You have likely seen a few comments about the importance of calibrating the IMU on your drone. To find out how to do this, check out my post-DJI Drone IMU Calibration: When and How You Should Do It.

Should you get DJI’s Care Refresh with your new drone? Learning how to fly a drone can be an intimidating endeavor, and buying an extended warranty may be wise for some. I cover in detail DJI’s Care Refresh in this post-DJI Care Refresh: The Ultimate 2019 Guide.

What is the role of the compass?

The compass gives the drone it’s bearing, or in simpler terms, it lets the drone know which way the nose is facing. 

Why is this important while flying your Spark? Imagine that you are flying along and the drone suddenly loses connection from your RC. When the drone commences its RTH sequence, you’re going to have some issues if the drone thinks that north is actually south.

Your Spark uses GPS and the compass when performing an RTH operation, but the bird will get conflicting information from these two systems if it doesn’t know which way it’s going.

What objects cause compass interference for your Spark?

When calibrating the compass, it is extremely important to do so in an open area, free of obstruction. So, what kind of objects may cause compass calibration errors? 

Ferromagnetic materials, such as nickel, iron, and cobalt should be avoided. DJI mentions that cell phones often have ferromagnetic materials in them, and they suggest that you don’t carry them in your pocket when calibrating the drone. I find this interesting that DJI specifically mentions cell phones, because, well, we have to use our cell phones (or tablets) to perform the calibration process. I guess they are saying “don’t have three extra phones hanging out near the drone during the compass calibration, bud”. 

If you want to be overly cautious about the cell phone thing, you can have someone hold the RC with the phone/tablet while you have the drone about 10 feet away, or you can set the drone on the ground and walk over to it when you tap “calibrate” in the app. 

Here’s a list of other objects that should be avoided while performing the calibration. Understand that this isn’t a complete list, but it contains some of the most common objects we encounter in our environment. 

  • Large metal structures
  • Rebar (this may be an easy one to not realize you’re close to)
  • Parking structures 
  • Steel reinforced basements 
  • Cars
  • Bridges (I attempted to calibrate in the middle of a very large bridge once. It didn’t go well. I never did perform a successful calibration.)
  • Scaffolding 
  • Any electromagnetic fields

An area of discussion that doesn’t seem to have a conclusive answer is smart-watches. Does that Apple or Samsung watch that you’re wearing cause interference? Some people claim that their smart-watch makes a difference, while other’s say that this is nonsense. 

I wear a Garmin watch, which is technically a smart-watch, but in a class where the Apple watch gets straight A’s, the Garmin is more of a C kind of student. I don’t seem to have any compass issues with my C average watch. 

I’d say that if you want to be on the safe side, take off the smart watch. It would also be smart to perform a test to see if the watch causes problems. 

You can actually see if the compass has any interference before you calibrate your Spark. To do this, open the DJI GO 4 app and go to settings>main controller settings>advanced settings>sensors>compass.

dji compass interference

This screenshot was taken from a Phantom 4 Pro. This page will look slightly different for the Spark.

There have been so many discussions on where the best location is to calibrate the compass on a drone, and the truth of the matter is that it will be difficult to truly escape all forms of interference when you’re in an urban environment. 

People have joked that the best spot to calibrate the compass on your drone is in the middle of a cornfield while you’re in your birthday suit. But don’t get too close to those to those gigantic metal rolling structures that water the field;).

Calibrate, or just move?

Something that I should note is that calibrating the compass near an object that is causing interference will not simply make the errors disappear. 

It may be tempting to see a compass error on the GO 4 app and immediately think that the remedy is to calibrate it. Don’t do this. You are likely just too close to some metal object and the proper course of action would be to move a few feet away and see if the errors go away. 

Calibrating a compass that is already calibrated and in good working order only gives the drones compass an opportunity to get worse, not better. 

In-flight signs that you should calibrate the Spark’s compass

If you are cruising around with your Spark and the drone suddenly enters ATTI mode, there is a good chance that this is because of a compass or GPS problem.

You may also experience the “toilet bowl” effect, which is when the drone starts spinning on its axis instead of keeping its nose facing forward as it should.

You may get a notification in the DJI GO 4 app while flying that lets you know there is compass interference, but this doesn’t always happen. I was having problems with my drone a while back that we’re a bit confusing at the time. 

I would be flying along with 18+ satellites and I would suddenly get an error that the drone lost GPS and was now entering ATTI mode. This was extremely frustrating as it would happen at the most random times, usually when I least expected it. In fact, I remember thinking that I would for sure lose GPS on one occasion when I only had 8 satellites. To my surprise, the drone remained in P-mode for the entire flight. 

This was frustrating conundrum because I didn’t have much faith in the consistency of my drone, and I was alway on guard thinking that the AC would go into ATTI mode at any moment. 

When I started calibrating my drone on a more regular basis I noticed that this occurence would happen less often. Even if I didn’t get a compass error, I would calibrate it and wouldn’t lose GPS while flying as often. Does it still happen occasionally? Sure, but probably because I live in San Diego and it’s difficult to escape all forms of interference when in or near a large city. 

If your Spark does enter ATTI mode while you’re out flying, immediately panic! No, I’m totally kidding…panicking is the last thing you should do. When a drone is in ATTI (attitude) mode, you will need to fly it manually as GPS is not available. The drone will maintain its altitude but will drift with any wind.

This is a good reason to not fly too far from your location if you have a weak GPS signal or are getting compass errors. If the drone is just a tiny speck off in the distance, you will have to fly it back solely using the image transmission on your phone or tablet, and we all know how laggy that image can be.

If you lose GPS and happen to have the aircraft disconnect due to signal loss, you’re going to be in a lot of trouble as the drone will have no clue how to return to home. If you’re newer to flying or would like a refresher, I would strongly recommend reading Drone Flyaways: 14 ways to Prevent Them, and Best 17 Drone Flying Tips for Every DJI Beginner.

One last note about ATTI mode. I can guarantee with almost complete certainty that there will come a time when you have to fly in ATTI mode unexpectantly. To prepare yourself for this, you have a couple of options. If you own a Phantom or Inspire, you can toggle ATTI mode on the controller.  I would recommend practicing in ATTI mode while you’re in an open area with a lot of room for error. It’s not easy at first, but every seasoned drone pilot has a working knowledge of ol‘ ATTI and knows how to control her when necessary.

If you don’t have a drone that allows you to manually enter ATTI mode, you may want to buy a cheap drone that will behave like a drone in ATTI mode, as this experience will go a long way in preparing you for the occasion when your Spark loses GPS. 

How to check if there are compass errors on your Spark

Before you fly, the GO 4 app may display a compass error. If this is the case, follow the instructions listed at the beginning of this post and calibrate the compass in an area with no interference. Remember, there is a difference between the app telling you to calibrate the compass and that there is magnetic interference nearby. If the app is just letting you know that there is interference, move locations and see if the warning disappears

Here is an example of the DJI GO 4 app telling me to calibrate the compass.

calibrate the compass dji

And here is an example of the DJI GO 4 app telling me that I need to try taking off from a different location and that there may be metal or magnetic objects nearby. 

magnetic interference dji compass

You may also get a compass error while you are flying. If this is the case, I’d strongly recommend landing as soon as you can and proceed with calibrating the compass.

Alternating red and yellow blinking lights on the aircraft also indicate that a compass calibration is needed. 

If you continue to get compass errors despite trying to calibrate in multiple areas, I’d recommend trying this course of action:

1- Check for any firmware updates. Just remember that firmware updates are often large so complete the update when you are near Wi-Fi. 

2- If all firmware is updated and you are still getting compass errors, I’d try deleting and re-installing the DJI GO 4 app. In theory, this wouldn’t rectify the problem because the compass is on the drone itself and not the GO 4 app, but there’s a chance that the compass is completely fine and the app is just displaying unfounded errors.

Detailed Spark compass calibration steps

So if after changing locations the app is still prompting you to calibrate the compass, it’s time to go through the calibration process. The five steps listed in the beginning are the main points, but here is where we get into the step-by-step instructions. 

Step #1- Bring your drone, remote controller and phone or tablet to an open area free of metal or magnetic objects. 

Step #2- Power on the RC, then the drone. 

Step #3- Tap on settings in the upper righthand corner. 

settings dji go 4

Step #4- Tap on main controller settings in the top left.

main controller settings dji go 4

Step #5- Scroll down and tap advanced settings at the bottom.

advanced settings dji go 4

Step #6- Tap on sensors. 

sensors dji go 4

Step #7- Toggle over to Compass at the top.

compass interference dji go 4

Step #8- Tap on calibrate compass at the bottom. 

calibrate compass dji go 4

Step #9- Press start when prompted. 

start compass calibration dji go 4

Step #10- Begin the calibration by rotating the drone horizontally in a counterclockwise direction, parallel with the ground. You can stop when the status indicator lights flash green. 

rotate horizontally dji compass calibration

Step #11- Next, rotate the drone on its side and rotate the aircraft 360 degrees vertically in a counterclockwise direction. Again, you can stop when the status indicator lights turn green. 

rotate vertically dji compass calibration

Step #12- Congrats, you’ve successfully calibrated the drone’s compass! If the compass errors don’t disappear, move locations and try to re-calibrate. 

Trevor’s Take

You know, sometimes I just wish that nothing had to be calibrated on my drones and I could just whip them out wherever and whenever I wanted, but that’s not technology. The amount of engineering that has gone into making these drones operate as well as they do is astounding. Really, this is what has set DJI apart from the rest. They’ve managed to put the best technology and engineering into their drones at an affordable price point. When you cram that much technology into a flying device that fits in the palm of your hand, it’s asinine to think that the aircraft will fly perfect one hundred percent of the time without any maintenance (calibration). 

Have you had any compass errors on your Spark? What was your experience and were you able to resolve the issues? I’d love to hear about it in the comment section below!

djiuser_xLE6O03

Second Officer

Flight distance : 1198346 ft

Romania

Offline

i did another firmware refresh , and i fly today just hovering around
-46.060 : 218014562 :    2140 [L-ACTIVATION]send index:0 send id:2 get info, state:1, date:1970-1-18, time:11-55-23,
-44.318 : 225853241 :    2228 [L-HOME]First. lati:47.6556802 longti:23.5635836 alti:192.42
-43.457 : 229727488 :    2271 [L-FMU/LED]action changed. set home0)
-42.773 : 232806364 :    2305 [L-BATTERY]no space to save the ipc packet 15
-41.357 : 239176955 :    2376 [L-FMU/LED]action changed. Normal Flash(0)
-41.357 : 239177136 :    2376 [L-FMU/LED]type:0, normal flash action:
-41.357 : 239177367 :    2376 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
-39.758 : 246375848 :    2456 [L-FMU/VERSION]Mc  ID  :0BMLE6J101063D
-39.758 : 246376022 :    2456 [L-FMU/VERSION]Mc  Ver :v3.2.37.75
-39.757 : 246376169 :    2456 [L-FMU/VERSION]Bat Ver :v1.0.0.75
-39.757 : 246376321 :    2456 [L-FMU/VERSION]svn Ver :013be256c2b14fcbda2257d4e01ddccffaf33504
-39.757 : 246376452 :    2456 [L-FMU/VERSION]Time    :commit:2017-08-16 20:31:55 /build:2017-08-17 15:21:57
-39.380 : 248074749 :    2474 [L-CFG][write_cfg_item_value_by_hash] save(var_addr)
-39.380 : 248075021 :    2474 [L-CFG]write g_config.flying_limit.radius_limit_enabled(1.000000) by hash sender:0x02
-27.220 : 302795137 :    3082 [L-CFG]successfully request send, size:19, fre:1
-27.220 : 302795807 :    3082 [L-CFG]successfully request send, size:0, fre:0
-27.220 : 302796411 :    3082 [L-CFG]successfully request send, size:0, fre:0
-27.220 : 302796855 :    3082 [L-CFG]successfully request send, size:0, fre:0
-21.760 : 327364557 :    3355 [L-CFG]successfully request send, size:0, fre:0
-21.740 : 327454684 :    3356 [L-CFG]successfully request send, size:0, fre:0
-21.740 : 327455108 :    3356 [L-CFG]successfully request send, size:0, fre:0
-21.740 : 327455724 :    3356 [L-CFG]successfully request send, size:0, fre:0
-17.318 : 347352552 :    3578 [L-TAKEOFF]alti: 172.541489 tors: -81.979515
-17.175 : 347997605 :    3585 [L-BATTERY]no space to save the ipc packet 15
-16.155 : 352587622 :    3636 [L-BATTERY]no space to save the ipc packet 15
-15.133 : 357185449 :    3687 [L-BATTERY]no space to save the ipc packet 15
-12.878 : 367332763 :    3800 [L-TAKEOFF]alti: 173.002319 tors: 144.941772
-10.818 : 376603210 :    3903 [L-TAKEOFF]alti: 173.895630 tors: 157.265076
-3.915 : 407666495 :    4248 [L-BATTERY]double press informed
-3.900 : 407734564 :    4248 [L-FMU/LED]set_open_led_action(3344,71,1)
-3.897 : 407747827 :    4249 [L-FMU/LED]action changed. y_slow(0)
-2.380 : 414574459 :    4324 [L-FMU/LED]set_open_led_action(3344,71,0)
-2.380 : 414574639 :    4324 [L-FMU/LED]set_open_led_action(3344,73,1)
-1.897 : 416747148 :    4349 [L-FMU/LED]action changed. g_l(0)
-.180 : 424474388 :    4434 [L-API]get_id_index_by_basic_cmd: cmd 33 index 20
-.180 : 424474547 :    4434 [L-CMD]exec_fc_basic_function index 20
-.180 : 424474676 :    4434 [L-API]on_hand_takeoff_check
-.180 : 424475092 :    4434 [L-API]basic_cmd_on_hand_takeoff
-.178 : 424484616 :    4435 [L-FMU/MOTOR]Start. reason:REQ_API
-.178 : 424484852 :    4435 [L-PWM]set actuator mode:CTRL
-.177 : 424487446 :    4435 [L-FLYMODE][Ctrl<2>] REQ_RC_COMMAND ENGINE_START ctrl_engine_start
-.177 : 424489444 :    4435 [L-FDI]tilt when motor on = 0.035890, static flag = 0
-.174 : 424502177 :    4435 [L-FMU/FSM]state changed. cur: on ground
-.160 : 424566668 :    4436 [L-IMU]set imu switch level = 8
-.158 : 424572633 :    4436 [L-IOC]Set CL. 127.6 Degree
-.158 : 424572885 :    4436 [L-TAKEOFF]alti: 174.349533 tors: 127.712929
.184 : 426113166 :    4453 [L-NS][AHRS] connect us . :1
.441 : 427269600 :    4466 [L-FMU/FSM]near ground
.842 : 429073994 :    4486 [L-FMU/MOTOR]safe_near_grd:true
1.362 : 431415162 :    4512 [L-FLYMODE][Ctrl<2>] REQ_RC_COMMAND ASST_TAKEOFF ctrl_asst_takeoff
2.640 : 437165437 :    4575 [L-FMU/LED]set_open_led_action(3344,73,0)
2.640 : 437165713 :    4575 [L-FMU/LED]set_open_led_action(3344,71,1)
2.660 : 437254767 :    4576 [L-FMU/LED]set_open_led_action(3344,71,0)
2.663 : 437267488 :    4577 [L-FMU/LED]action changed. Normal Flash(0)
3.256 : 439937637 :    4606 [L-FMU/FSM]state changed. cur: in air
3.262 : 439963322 :    4607 [L-HOME]Update. lati:47.6556501 longti:23.5635926 alti:194.35
3.263 : 439966310 :    4607 [L-FLYMODE]CTRL reset all by auto assisted takeoff timeout
3.263 : 439968190 :    4607 [L-FDI][FDI CTRL] event: impact turn on
3.263 : 439968566 :    4607 [L-FDI][FDI CTRL] event: height turn on
3.263 : 439968721 :    4607 [L-FDI][FDI CTRL] event: tilt turn on
3.263 : 439968953 :    4607 [L-FDI][FDI CTRL] event: head turn on
3.263 : 439969196 :    4607 [L-FDI][FDI CTRL] event: random fly turn on
3.263 : 439969340 :    4607 [L-FDI][FDI CTRL] event: fly away turn on
3.263 : 439969508 :    4607 [L-FDI][FDI CTRL] event: horiz turn on
3.283 : 440056826 :    4608 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
3.643 : 441677311 :    4626 [L-FMU/LED]action changed. set home0)
4.306 : 444662162 :    4659 [L-FMU/FSM]not near ground
4.462 : 445365914 :    4667 [L-RC]Emergency break. rc vib!
4.541 : 445719664 :    4671 [L-FMU/FSM]near ground
4.720 : 446525241 :    4679 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
4.720 : 446525545 :    4679 [L-CMD]exec_fc_basic_function index 19
4.720 : 446525719 :    4679 [L-API]on_hand_landing_check
4.720 : 446525834 :    4679 [L-API]basic_cmd_on_hand_landing
5.743 : 451128060 :    4731 [L-FMU/LED]action changed. Normal Flash(0)
5.743 : 451128240 :    4731 [L-FMU/LED]type:0, normal flash action:
5.743 : 451128666 :    4731 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
8.300 : 462634701 :    4858 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
8.300 : 462634869 :    4858 [L-CMD]exec_fc_basic_function index 19
8.300 : 462635008 :    4858 [L-API]on_hand_landing_check
8.300 : 462635110 :    4858 [L-API]basic_cmd_on_hand_landing
11.243 : 475877636 :    5006 [L-FMU/LED]type:0, normal flash action:
11.243 : 475877917 :    5006 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
11.900 : 478834834 :    5038 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
11.900 : 478834988 :    5038 [L-CMD]exec_fc_basic_function index 19
11.900 : 478835111 :    5038 [L-API]on_hand_landing_check
11.900 : 478835222 :    5038 [L-API]basic_cmd_on_hand_landing
13.043 : 483978098 :    5096 [L-FMU/LED]type:0, normal flash action:
13.043 : 483978556 :    5096 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
13.143 : 484427099 :    5101 [L-RC]Emergency break. rc vib!
13.280 : 485045187 :    5107 [L-FMU/LED]set_open_led_action(3344,71,1)
13.303 : 485148056 :    5109 [L-FMU/LED]action changed. y_slow(0)
14.520 : 490624751 :    5169 [L-FMU/LED]set_open_led_action(3344,71,0)
14.520 : 490624930 :    5169 [L-FMU/LED]set_open_led_action(3344,73,1)
14.643 : 491176980 :    5176 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
14.700 : 491435409 :    5178 [L-SDK]app API sub_mode 4 2
14.700 : 491435653 :    5178 [L-MIS][NAVI MISSION] req sub_mode: Gesture on
14.700 : 491435826 :    5178 [L-SDK][USER]send ack 0x00
15.023 : 492887541 :    5195 [L-FMU/LED]type:0, normal flash action:
15.023 : 492887812 :    5195 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
15.303 : 494148040 :    5209 [L-FMU/LED]action changed. g_l(0)
20.080 : 515645827 :    5447 [L-FMU/LED]set_open_led_action(3344,73,0)
20.080 : 515646018 :    5447 [L-FMU/LED]set_open_led_action(3344,71,1)
20.103 : 515747974 :    5449 [L-FMU/LED]action changed. y_slow(0)
20.200 : 516184937 :    5453 [L-FMU/LED]set_open_led_action(3344,71,0)
20.200 : 516185115 :    5453 [L-FMU/LED]set_open_led_action(3344,73,1)
20.420 : 517174660 :    5464 [L-FMU/LED]set_open_led_action(3344,73,0)
20.420 : 517174833 :    5464 [L-FMU/LED]set_open_led_action(3344,71,1)
22.001 : 524287241 :    5543 [L-FMU/LED]set_open_led_action(3344,71,0)
22.103 : 524748212 :    5549 [L-FMU/LED]action changed. Normal Flash(0)
22.441 : 526269607 :    5566 [L-FMU/FSM]not near ground
24.300 : 534635425 :    5658 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
24.303 : 534647636 :    5659 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
24.303 : 534647807 :    5659 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
24.303 : 534648568 :    5659 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
24.903 : 537346902 :    5689 [L-RC]Emergency break. rc vib!
25.960 : 542104977 :    5741 [L-FMU/LED]set_open_led_action(3344,74,1)
25.985 : 542218588 :    5743 [L-FMU/LED]action changed. y_l(0)
26.003 : 542297361 :    5744 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
26.100 : 542735531 :    5748 [L-SDK]app API sub_mode 1 2
26.100 : 542735744 :    5748 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
26.100 : 542735891 :    5748 [L-SDK][USER]send ack 0x00
26.120 : 542825524 :    5749 [L-SDK]app API sub_mode 1 2
26.120 : 542825748 :    5749 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
26.120 : 542825894 :    5749 [L-SDK][USER]send ack 0x00
26.140 : 542916410 :    5750 [L-SDK]app API sub_mode 1 2
26.140 : 542916565 :    5750 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
26.140 : 542916707 :    5750 [L-SDK][USER]send ack 0x00
26.160 : 543005598 :    5751 [L-SDK]app API sub_mode 1 2
26.160 : 543005794 :    5751 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
26.160 : 543005952 :    5751 [L-SDK][USER]send ack 0x00
26.180 : 543096280 :    5752 [L-SDK]app API sub_mode 1 2
26.180 : 543096429 :    5752 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
26.180 : 543096562 :    5752 [L-SDK][USER]send ack 0x00
28.380 : 552995907 :    5862 [L-FMU/LED]set_open_led_action(3344,74,0)
28.380 : 552996089 :    5862 [L-FMU/LED]set_open_led_action(3344,73,1)
28.385 : 553017521 :    5863 [L-FMU/LED]action changed. g_l(0)
36.060 : 587554829 :    6246 [L-FMU/LED]set_open_led_action(3344,73,0)
36.060 : 587556262 :    6246 [L-SDK]app API sub_mode 1 0
36.060 : 587556409 :    6246 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
36.060 : 587556558 :    6246 [L-SDK][USER]send ack 0x00
36.065 : 587577198 :    6247 [L-FMU/LED]action changed. Normal Flash(0)
36.080 : 587646313 :    6247 [L-SDK]app API sub_mode 1 0
36.080 : 587646463 :    6247 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
36.080 : 587646590 :    6247 [L-SDK][USER]send ack 0x00
36.100 : 587735731 :    6248 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
36.103 : 587747809 :    6249 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
36.103 : 587747986 :    6249 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
36.103 : 587748732 :    6249 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
40.280 : 606545769 :    6457 [L-FMU/LED]set_open_led_action(3344,74,1)
40.303 : 606648498 :    6459 [L-FMU/LED]action changed. y_l(0)
40.323 : 606738026 :    6460 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
40.401 : 607087357 :    6463 [L-SDK]app API sub_mode 1 2
40.401 : 607087512 :    6463 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
40.401 : 607087802 :    6463 [L-SDK][USER]send ack 0x00
40.420 : 607175741 :    6464 [L-SDK]app API sub_mode 1 2
40.420 : 607175905 :    6464 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
40.420 : 607176051 :    6464 [L-SDK][USER]send ack 0x00
40.440 : 607266083 :    6465 [L-SDK]app API sub_mode 1 2
40.440 : 607266248 :    6465 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
40.440 : 607266383 :    6465 [L-SDK][USER]send ack 0x00
40.460 : 607355588 :    6466 [L-SDK]app API sub_mode 1 2
40.460 : 607355798 :    6466 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
40.460 : 607355934 :    6466 [L-SDK][USER]send ack 0x00
40.480 : 607446178 :    6467 [L-SDK]app API sub_mode 1 2
40.480 : 607446327 :    6467 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
40.480 : 607446456 :    6467 [L-SDK][USER]send ack 0x00
46.540 : 634715248 :    6770 [L-FMU/LED]set_open_led_action(3344,74,0)
46.540 : 634715593 :    6770 [L-FMU/LED]set_open_led_action(3344,73,1)
46.545 : 634738380 :    6771 [L-FMU/LED]action changed. g_l(0)
112.372 : 930958853 :   10062 [L-BATTERY]no space to save the ipc packet 15
113.392 : 935548623 :   10113 [L-BATTERY]no space to save the ipc packet 15
114.413 : 940142828 :   10164 [L-BATTERY]no space to save the ipc packet 15
115.430 : 944720696 :   10215 [L-BATTERY]no space to save the ipc packet 15
128.180 : 1002095541 :   10852 [L-IMU]api data from 1860.
128.180 : 1002095752 :   10852 [L-DBG1]receive data from 1860_cmd_id = (2)|
128.180 : 1002095882 :   10852 [L-DBG1]fan gaurd work|
128.180 : 1002095990 :   10852 [L-DBG1]fan ctrl out1 =  100 ||
128.180 : 1002096148 :   10852 [L-IMU][INFO] cmd_from_1860 = (2,0,0,0)|
128.640 : 1004164869 :   10875 [L-DBG1]fan_speed:  247, ctrl_out: 100  ||
129.140 : 1006414895 :   10900 [L-DBG1]fan_speed:  247, ctrl_out: 100  ||
129.200 : 1006686734 :   10903 [L-IMU]api data from 1860.
129.200 : 1006686898 :   10903 [L-DBG1]receive data from 1860_cmd_id = (255)|
129.200 : 1006687036 :   10903 [L-DBG1]receive 1860 0xff |
129.201 : 1006687135 :   10903 [L-DBG1]fan gaurd work|
129.201 : 1006687243 :   10903 [L-DBG1]fan ctrl out1 =  100 ||
129.201 : 1006687391 :   10903 [L-IMU][INFO] cmd_from_1860 = (255,0,0,0)|
129.640 : 1008665145 :   10925 [L-DBG1]fan_speed:  247, ctrl_out: 100  ||
129.840 : 1009566266 :   10935 [L-CFG]successfully request send, size:19, fre:1
129.840 : 1009566713 :   10935 [L-CFG]successfully request send, size:0, fre:0
129.860 : 1009654747 :   10936 [L-CFG]successfully request send, size:0, fre:0
129.860 : 1009655403 :   10936 [L-CFG]successfully request send, size:0, fre:0
130.140 : 1010914922 :   10950 [L-DBG1]fan_speed:  247, ctrl_out: 100  ||
130.640 : 1013164990 :   10975 [L-DBG1]fan_speed:  247, ctrl_out: 100  ||
131.140 : 1015414982 :   11000 [L-DBG1]fan_speed:  247, ctrl_out: 100  ||
131.640 : 1017664760 :   11025 [L-DBG1]fan_speed:  247, ctrl_out: 100  ||
142.260 : 1065454798 :   11556 [L-CFG]successfully request send, size:0, fre:0
142.260 : 1065455226 :   11556 [L-CFG]successfully request send, size:0, fre:0
142.260 : 1065456010 :   11556 [L-CFG]successfully request send, size:0, fre:0
142.260 : 1065456437 :   11556 [L-CFG]successfully request send, size:0, fre:0
143.720 : 1072025352 :   11629 [L-CFG]successfully request send, size:19, fre:1
143.720 : 1072025893 :   11629 [L-CFG]successfully request send, size:0, fre:0
143.720 : 1072026273 :   11629 [L-CFG]successfully request send, size:0, fre:0
143.720 : 1072026638 :   11629 [L-CFG]successfully request send, size:0, fre:0
145.760 : 1081205383 :   11731 [L-CFG]successfully request send, size:0, fre:0
145.760 : 1081205925 :   11731 [L-CFG]successfully request send, size:0, fre:0
145.760 : 1081206672 :   11731 [L-CFG]successfully request send, size:0, fre:0
145.760 : 1081207052 :   11731 [L-CFG]successfully request send, size:0, fre:0
166.440 : 1174265409 :   12765 [L-BATTERY]no space to save the ipc packet 17
166.440 : 1174265722 :   12765 [L-BATTERY]no space to save the ipc packet 17
167.740 : 1180115411 :   12830 [L-BATTERY]no space to save the ipc packet 17
167.740 : 1180115725 :   12830 [L-BATTERY]no space to save the ipc packet 17
167.740 : 1180116261 :   12830 [L-BATTERY]no space to save the ipc packet 17
167.740 : 1180116449 :   12830 [L-BATTERY]no space to save the ipc packet 17
167.740 : 1180116603 :   12830 [L-BATTERY]no space to save the ipc packet 17
168.200 : 1182186803 :   12853 [L-BATTERY]no space to save the ipc packet 17
168.220 : 1182274822 :   12854 [L-BATTERY]no space to save the ipc packet 17
168.220 : 1182275033 :   12854 [L-BATTERY]no space to save the ipc packet 17
194.660 : 1301256107 :   14176 [L-BATTERY]no space to save the ipc packet 17
194.660 : 1301256335 :   14176 [L-BATTERY]no space to save the ipc packet 17
197.900 : 1315835570 :   14338 [L-CFG]successfully request send, size:19, fre:1
197.900 : 1315836171 :   14338 [L-CFG]successfully request send, size:0, fre:0
197.900 : 1315836714 :   14338 [L-CFG]successfully request send, size:0, fre:0
197.900 : 1315837090 :   14338 [L-CFG]successfully request send, size:0, fre:0
198.920 : 1320424973 :   14389 [L-CFG]successfully request send, size:0, fre:0
198.920 : 1320425565 :   14389 [L-CFG]successfully request send, size:0, fre:0
198.920 : 1320426001 :   14389 [L-CFG]successfully request send, size:0, fre:0
198.920 : 1320426395 :   14389 [L-CFG]successfully request send, size:0, fre:0
202.133 : 1334882736 :   14550 [L-BATTERY]no space to save the ipc packet 15
202.133 : 1334883168 :   14550 [L-BATTERY]no space to save the ipc packet 15
215.392 : 1394548695 :   15213 [L-BATTERY]no space to save the ipc packet 15
232.220 : 1470275212 :   16054 [L-CFG]successfully request send, size:19, fre:1
232.220 : 1470276094 :   16054 [L-CFG]successfully request send, size:0, fre:0
232.220 : 1470276514 :   16054 [L-CFG]successfully request send, size:0, fre:0
232.260 : 1470454924 :   16056 [L-CFG]successfully request send, size:0, fre:0
234.180 : 1479095631 :   16152 [L-CFG]successfully request send, size:0, fre:0
234.180 : 1479096096 :   16152 [L-CFG]successfully request send, size:0, fre:0
234.200 : 1479186596 :   16153 [L-CFG]successfully request send, size:0, fre:0
234.200 : 1479187031 :   16153 [L-CFG]successfully request send, size:0, fre:0
235.792 : 1486348991 :   16233 [L-BATTERY]no space to save the ipc packet 15
241.020 : 1509874732 :   16494 [L-CFG]successfully request send, size:19, fre:1
241.020 : 1509875148 :   16494 [L-CFG]successfully request send, size:0, fre:0
241.020 : 1509875763 :   16494 [L-CFG]successfully request send, size:0, fre:0
241.020 : 1509876152 :   16494 [L-CFG]successfully request send, size:0, fre:0
242.420 : 1516174853 :   16564 [L-CFG]successfully request send, size:0, fre:0
242.420 : 1516175388 :   16564 [L-CFG]successfully request send, size:0, fre:0
242.420 : 1516175934 :   16564 [L-CFG]successfully request send, size:0, fre:0
242.420 : 1516176343 :   16564 [L-CFG]successfully request send, size:0, fre:0
257.143 : 1582427152 :   17301 [L-FMU/MOTOR]safe_near_grd:false
258.303 : 1587647505 :   17359 [L-FMU/MOTOR]safe_near_grd:true
259.803 : 1594398529 :   17434 [L-FMU/MOTOR]safe_near_grd:false
261.290 : 1601090983 :   17508 [L-BATTERY]no space to save the ipc packet 15
261.422 : 1601685452 :   17515 [L-FMU/MOTOR]safe_near_grd:true
263.176 : 1609577612 :   17602 [L-FMU/FSM]near ground
269.220 : 1636775990 :   17904 [L-SDK]app API sub_mode 1 0
269.220 : 1636776140 :   17904 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
269.220 : 1636776283 :   17904 [L-SDK][USER]send ack 0x00
269.220 : 1636776742 :   17904 [L-SDK]app API sub_mode 1 0
269.220 : 1636776867 :   17904 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
269.220 : 1636776978 :   17904 [L-SDK][USER]send ack 0x00
269.221 : 1636777365 :   17904 [L-SDK]app API sub_mode 1 0
269.221 : 1636777597 :   17904 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
269.221 : 1636777785 :   17904 [L-SDK][USER]send ack 0x00
269.240 : 1636865243 :   17905 [L-FMU/LED]set_open_led_action(3344,73,0)
269.240 : 1636866679 :   17905 [L-SDK]app API sub_mode 1 0
269.240 : 1636866824 :   17905 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
269.240 : 1636866955 :   17905 [L-SDK][USER]send ack 0x00
269.260 : 1636955563 :   17906 [L-SDK]app API sub_mode 1 0
269.260 : 1636955776 :   17906 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
269.260 : 1636955913 :   17906 [L-SDK][USER]send ack 0x00
269.263 : 1636968679 :   17907 [L-FMU/LED]action changed. Normal Flash(0)
269.280 : 1637046444 :   17907 [L-SDK]app API sub_mode 1 0
269.280 : 1637046607 :   17907 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
269.280 : 1637046735 :   17907 [L-SDK][USER]send ack 0x00
269.300 : 1637135812 :   17908 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
269.303 : 1637148072 :   17909 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
269.303 : 1637148240 :   17909 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
269.303 : 1637149104 :   17909 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
269.440 : 1637765831 :   17915 [L-FMU/LED]set_open_led_action(3344,71,1)
269.463 : 1637869395 :   17917 [L-FMU/LED]action changed. y_slow(0)
270.143 : 1640927327 :   17951 [L-RC]Emergency break. rc vib!
270.623 : 1643087435 :   17975 [L-FMU/LED]type:0, normal flash action:
270.623 : 1643087707 :   17975 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
270.780 : 1643795148 :   17982 [L-FMU/LED]set_open_led_action(3344,71,0)
270.780 : 1643795522 :   17982 [L-FMU/LED]set_open_led_action(3344,73,1)
270.843 : 1644077120 :   17986 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
270.900 : 1644335720 :   17988 [L-SDK]app API sub_mode 4 2
270.900 : 1644335879 :   17988 [L-MIS][NAVI MISSION] req sub_mode: Gesture on
270.900 : 1644336028 :   17988 [L-SDK][USER]send ack 0x00
271.063 : 1645068491 :   17997 [L-FMU/LED]type:0, normal flash action:
271.063 : 1645068880 :   17997 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
271.463 : 1646867898 :   18017 [L-FMU/LED]action changed. g_l(0)
271.488 : 1646980264 :   18018 [L-BATTERY]no space to save the ipc packet 15
275.120 : 1663325214 :   18199 [L-FMU/LED]set_open_led_action(3344,73,0)
275.120 : 1663325553 :   18199 [L-FMU/LED]set_open_led_action(3344,71,1)
275.201 : 1663687118 :   18203 [L-FMU/LED]set_open_led_action(3344,71,0)
275.201 : 1663687300 :   18203 [L-FMU/LED]set_open_led_action(3344,73,1)
275.320 : 1664224697 :   18209 [L-FMU/LED]set_open_led_action(3344,73,0)
275.320 : 1664224870 :   18209 [L-FMU/LED]set_open_led_action(3344,71,1)
275.440 : 1664765570 :   18215 [L-FMU/LED]set_open_led_action(3344,71,0)
275.440 : 1664765791 :   18215 [L-FMU/LED]set_open_led_action(3344,73,1)
275.520 : 1665124852 :   18219 [L-FMU/LED]set_open_led_action(3344,73,0)
275.543 : 1665228849 :   18221 [L-FMU/LED]action changed. Normal Flash(0)
275.740 : 1666115424 :   18230 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
275.740 : 1666115658 :   18230 [L-CMD]exec_fc_basic_function index 19
275.740 : 1666115827 :   18230 [L-API]on_hand_landing_check
275.740 : 1666115926 :   18230 [L-API]basic_cmd_on_hand_landing
276.401 : 1669087219 :   18263 [L-FMU/LED]set_open_led_action(3344,72,1)
276.423 : 1669187591 :   18265 [L-FMU/LED]action changed. y_fast(0)
276.520 : 1669624955 :   18269 [L-FMU/LED]set_open_led_action(3344,72,0)
276.583 : 1669909371 :   18273 [L-FMU/LED]action changed. Normal Flash(0)
276.920 : 1671425254 :   18289 [L-FMU/LED]set_open_led_action(3344,72,1)
276.943 : 1671528205 :   18291 [L-FMU/LED]action changed. y_fast(0)
276.980 : 1671696022 :   18292 [L-FMU/LED]set_open_led_action(3344,72,0)
277.103 : 1672248265 :   18299 [L-FMU/LED]action changed. Normal Flash(0)
277.220 : 1672774862 :   18304 [L-FMU/LED]set_open_led_action(3344,72,1)
277.223 : 1672788502 :   18305 [L-FMU/LED]action changed. y_fast(0)
279.800 : 1684386900 :   18433 [L-FMU/LED]set_open_led_action(3344,72,0)
279.943 : 1685028518 :   18441 [L-FMU/LED]action changed. Normal Flash(0)
280.300 : 1686634649 :   18458 [L-FMU/LED]set_open_led_action(3344,72,1)
280.303 : 1686648640 :   18459 [L-FMU/LED]action changed. y_fast(0)
280.420 : 1687175000 :   18464 [L-FMU/LED]set_open_led_action(3344,72,0)
280.463 : 1687367412 :   18467 [L-FMU/LED]action changed. Normal Flash(0)
283.730 : 1702071050 :   18630 [L-BATTERY]no space to save the ipc packet 15
285.201 : 1708687474 :   18703 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
285.205 : 1708706541 :   18704 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
285.205 : 1708706770 :   18704 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
285.205 : 1708707357 :   18704 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
288.500 : 1723535109 :   18868 [L-FMU/LED]set_open_led_action(3344,72,1)
288.505 : 1723556747 :   18869 [L-FMU/LED]action changed. y_fast(0)
289.943 : 1730027222 :   18941 [L-RC]Emergency break. rc vib!
290.863 : 1734167342 :   18987 [L-FMU/LED]type:0, normal flash action:
290.863 : 1734167620 :   18987 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
292.560 : 1741804842 :   19071 [L-BATTERY]no space to save the ipc packet 17
292.640 : 1742165154 :   19075 [L-BATTERY]no space to save the ipc packet 17
293.040 : 1743965400 :   19095 [L-BATTERY]no space to save the ipc packet 17
293.040 : 1743965944 :   19095 [L-BATTERY]no space to save the ipc packet 17
293.040 : 1743966154 :   19095 [L-BATTERY]no space to save the ipc packet 17
293.440 : 1745765388 :   19115 [L-BATTERY]no space to save the ipc packet 17
293.440 : 1745766013 :   19115 [L-BATTERY]no space to save the ipc packet 17
293.440 : 1745766209 :   19115 [L-BATTERY]no space to save the ipc packet 17
293.440 : 1745766376 :   19115 [L-BATTERY]no space to save the ipc packet 17
293.440 : 1745766524 :   19115 [L-BATTERY]no space to save the ipc packet 17
293.440 : 1745766746 :   19115 [L-BATTERY]no space to save the ipc packet 17
293.441 : 1745767317 :   19115 [L-BATTERY]no space to save the ipc packet 17
293.441 : 1745767586 :   19115 [L-BATTERY]no space to save the ipc packet 17
294.520 : 1750624763 :   19169 [L-BATTERY]no space to save the ipc packet 17
294.520 : 1750625022 :   19169 [L-BATTERY]no space to save the ipc packet 17
294.520 : 1750625197 :   19169 [L-BATTERY]no space to save the ipc packet 17
294.520 : 1750625508 :   19169 [L-BATTERY]no space to save the ipc packet 17
294.540 : 1750714847 :   19170 [L-BATTERY]no space to save the ipc packet 17
294.540 : 1750715040 :   19170 [L-BATTERY]no space to save the ipc packet 17
294.880 : 1752246104 :   19187 [L-BATTERY]no space to save the ipc packet 17
294.880 : 1752246298 :   19187 [L-BATTERY]no space to save the ipc packet 17
294.880 : 1752246467 :   19187 [L-BATTERY]no space to save the ipc packet 17
294.880 : 1752246799 :   19187 [L-BATTERY]no space to save the ipc packet 17
294.900 : 1752334672 :   19188 [L-BATTERY]no space to save the ipc packet 17
294.953 : 1752572841 :   19191 [L-BATTERY]no space to save the ipc packet 15
294.960 : 1752604953 :   19191 [L-BATTERY]no space to save the ipc packet 17
294.960 : 1752605259 :   19191 [L-BATTERY]no space to save the ipc packet 17
295.201 : 1753687203 :   19203 [L-BATTERY]no space to save the ipc packet 17
295.201 : 1753687404 :   19203 [L-BATTERY]no space to save the ipc packet 17
295.201 : 1753687932 :   19203 [L-BATTERY]no space to save the ipc packet 17
295.201 : 1753688155 :   19203 [L-BATTERY]no space to save the ipc packet 17
295.500 : 1755035608 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.500 : 1755035863 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.500 : 1755036032 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.500 : 1755036253 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.500 : 1755036423 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.500 : 1755036605 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.500 : 1755036936 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.501 : 1755037306 :   19218 [L-BATTERY]no space to save the ipc packet 17
295.801 : 1756387248 :   19233 [L-BATTERY]no space to save the ipc packet 17
295.801 : 1756387448 :   19233 [L-BATTERY]no space to save the ipc packet 17
295.801 : 1756387761 :   19233 [L-BATTERY]no space to save the ipc packet 17
296.805 : 1760907147 :   19284 [L-FMU/LED]type:0, normal flash action:
296.805 : 1760907420 :   19284 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
297.420 : 1763674764 :   19314 [L-FMU/LED]set_open_led_action(3344,72,0)
297.463 : 1763867549 :   19317 [L-FMU/LED]action changed. Normal Flash(0)
301.560 : 1782305166 :   19521 [L-BATTERY]no space to save the ipc packet 22
302.092 : 1784698876 :   19548 [L-BATTERY]no space to save the ipc packet 15
302.280 : 1785545617 :   19557 [L-BATTERY]no space to save the ipc packet 17
304.130 : 1793870850 :   19650 [L-BATTERY]no space to save the ipc packet 15
304.130 : 1793871336 :   19650 [L-BATTERY]no space to save the ipc packet 15
305.540 : 1800215548 :   19720 [L-FMU/LED]set_open_led_action(3344,72,1)
305.545 : 1800236818 :   19721 [L-FMU/LED]action changed. y_fast(0)
305.600 : 1800486819 :   19723 [L-FMU/LED]set_open_led_action(3344,72,0)
305.703 : 1800948225 :   19729 [L-FMU/LED]action changed. Normal Flash(0)
305.720 : 1801024815 :   19729 [L-FMU/LED]set_open_led_action(3344,72,1)
305.743 : 1801128235 :   19731 [L-FMU/LED]action changed. y_fast(0)
306.520 : 1804625007 :   19769 [L-FMU/LED]set_open_led_action(3344,72,0)
306.520 : 1804625192 :   19769 [L-FMU/LED]set_open_led_action(3344,71,1)
306.543 : 1804728019 :   19771 [L-FMU/LED]action changed. y_slow(0)
306.643 : 1805176635 :   19776 [L-RC]Emergency break. rc vib!
306.920 : 1806424874 :   19789 [L-FMU/LED]set_open_led_action(3344,71,0)
306.920 : 1806425054 :   19789 [L-FMU/LED]set_open_led_action(3344,73,1)
307.043 : 1806977333 :   19796 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
307.100 : 1807235790 :   19798 [L-SDK]app API sub_mode 4 2
307.100 : 1807235949 :   19798 [L-MIS][NAVI MISSION] req sub_mode: Gesture on
307.100 : 1807236098 :   19798 [L-SDK][USER]send ack 0x00
307.543 : 1809228631 :   19821 [L-FMU/LED]action changed. g_l(0)
310.060 : 1820554796 :   19946 [L-FMU/LED]set_open_led_action(3344,73,0)
310.183 : 1821108860 :   19953 [L-FMU/LED]action changed. Normal Flash(0)
310.240 : 1821365761 :   19955 [L-FMU/LED]set_open_led_action(3344,71,1)
310.263 : 1821467472 :   19957 [L-FMU/LED]action changed. y_slow(0)
310.360 : 1821904809 :   19961 [L-FMU/LED]set_open_led_action(3344,71,0)
310.360 : 1821904994 :   19961 [L-FMU/LED]set_open_led_action(3344,73,1)
310.700 : 1823434872 :   19978 [L-FMU/LED]set_open_led_action(3344,73,0)
310.700 : 1823435049 :   19978 [L-FMU/LED]set_open_led_action(3344,71,1)
310.920 : 1824424934 :   19989 [L-FMU/LED]set_open_led_action(3344,71,0)
310.920 : 1824425108 :   19989 [L-FMU/LED]set_open_led_action(3344,73,1)
311.263 : 1825968440 :   20007 [L-FMU/LED]action changed. g_l(0)
313.400 : 1835586847 :   20113 [L-FMU/LED]set_open_led_action(3344,73,0)
313.400 : 1835587045 :   20113 [L-FMU/LED]set_open_led_action(3344,71,1)
313.423 : 1835687295 :   20115 [L-FMU/LED]action changed. y_slow(0)
313.520 : 1836124786 :   20119 [L-FMU/LED]set_open_led_action(3344,71,0)
313.520 : 1836124961 :   20119 [L-FMU/LED]set_open_led_action(3344,73,1)
313.900 : 1837834751 :   20138 [L-FMU/LED]set_open_led_action(3344,73,0)
314.120 : 1838824881 :   20149 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
314.120 : 1838825040 :   20149 [L-CMD]exec_fc_basic_function index 19
314.120 : 1838825160 :   20149 [L-API]on_hand_landing_check
314.120 : 1838825262 :   20149 [L-API]basic_cmd_on_hand_landing
314.423 : 1840187102 :   20165 [L-FMU/LED]action changed. Normal Flash(0)
317.700 : 1854934804 :   20328 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
317.700 : 1854934961 :   20328 [L-CMD]exec_fc_basic_function index 19
317.700 : 1854935083 :   20328 [L-API]on_hand_landing_check
317.700 : 1854935189 :   20328 [L-API]basic_cmd_on_hand_landing
321.200 : 1870686971 :   20503 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
321.201 : 1870687139 :   20503 [L-CMD]exec_fc_basic_function index 19
321.201 : 1870687263 :   20503 [L-API]on_hand_landing_check
321.201 : 1870687364 :   20503 [L-API]basic_cmd_on_hand_landing
324.002 : 1883292294 :   20643 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
324.005 : 1883307208 :   20644 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
324.005 : 1883307382 :   20644 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
324.005 : 1883308112 :   20644 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
324.800 : 1886887063 :   20683 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
324.801 : 1886887230 :   20683 [L-CMD]exec_fc_basic_function index 19
324.801 : 1886887357 :   20683 [L-API]on_hand_landing_check
324.801 : 1886887480 :   20683 [L-API]basic_cmd_on_hand_landing
324.805 : 1886906536 :   20684 [L-RC]Emergency break. rc vib!
325.166 : 1888532158 :   20702 [L-FMU/FSM]not near ground
325.381 : 1889499600 :   20713 [L-FMU/FSM]near ground
325.605 : 1890507228 :   20724 [L-FMU/LED]type:0, normal flash action:
325.605 : 1890507495 :   20724 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
326.483 : 1894458159 :   20768 [L-FMU/LED]type:0, normal flash action:
326.483 : 1894458618 :   20768 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
327.588 : 1899430460 :   20823 [L-BATTERY]no space to save the ipc packet 15
339.740 : 1954115829 :   21430 [L-CFG]successfully request send, size:19, fre:1
339.740 : 1954116237 :   21430 [L-CFG]successfully request send, size:0, fre:0
339.740 : 1954116772 :   21430 [L-CFG]successfully request send, size:0, fre:0
339.741 : 1954117146 :   21430 [L-CFG]successfully request send, size:0, fre:0
343.900 : 1972834843 :   21638 [L-CFG]successfully request send, size:0, fre:0
343.900 : 1972835704 :   21638 [L-CFG]successfully request send, size:0, fre:0
343.900 : 1972836170 :   21638 [L-CFG]successfully request send, size:0, fre:0
343.900 : 1972836702 :   21638 [L-CFG]successfully request send, size:0, fre:0
356.160 : 2028004711 :   22251 [L-BATTERY]no space to save the ipc packet 17
363.820 : 2062474808 :   22634 [L-FMU/LED]set_open_led_action(3344,72,1)
363.823 : 2062488104 :   22635 [L-FMU/LED]action changed. y_fast(0)
374.000 : 2108286799 :   23143 [L-FMU/LED]set_open_led_action(3344,72,0)
374.063 : 2108568202 :   23147 [L-FMU/LED]action changed. Normal Flash(0)
375.220 : 2113774922 :   23204 [L-FMU/LED]set_open_led_action(3344,72,1)
375.223 : 2113788448 :   23205 [L-FMU/LED]action changed. y_fast(0)
381.743 : 2143127047 :   23531 [L-RC]Emergency break. rc vib!
382.283 : 2145558555 :   23558 [L-FMU/LED]type:0, normal flash action:
382.283 : 2145558933 :   23558 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
387.123 : 2167339377 :   23800 [L-FMU/LED]type:0, normal flash action:
387.125 : 2167346632 :   23800 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
388.020 : 2171374799 :   23844 [L-FMU/LED]set_open_led_action(3344,72,0)
388.020 : 2171374982 :   23844 [L-FMU/LED]set_open_led_action(3344,71,1)
388.023 : 2171387967 :   23845 [L-FMU/LED]action changed. y_slow(0)
388.043 : 2171476907 :   23846 [L-RC]Emergency break. rc vib!
388.140 : 2171915770 :   23850 [L-FMU/LED]set_open_led_action(3344,71,0)
388.140 : 2171915957 :   23850 [L-FMU/LED]set_open_led_action(3344,73,1)
388.243 : 2172376841 :   23856 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
388.300 : 2172635450 :   23858 [L-SDK]app API sub_mode 4 2
388.300 : 2172635707 :   23858 [L-MIS][NAVI MISSION] req sub_mode: Gesture on
388.300 : 2172635851 :   23858 [L-SDK][USER]send ack 0x00
389.023 : 2175887494 :   23895 [L-FMU/LED]action changed. g_l(0)
392.520 : 2191625112 :   24069 [L-FMU/LED]set_open_led_action(3344,73,0)
392.520 : 2191625382 :   24069 [L-FMU/LED]set_open_led_action(3344,71,1)
392.623 : 2192087670 :   24075 [L-FMU/LED]action changed. y_slow(0)
392.840 : 2193065620 :   24085 [L-FMU/LED]set_open_led_action(3344,71,0)
392.840 : 2193065844 :   24085 [L-FMU/LED]set_open_led_action(3344,73,1)
393.623 : 2196587459 :   24125 [L-FMU/LED]action changed. g_l(0)
393.900 : 2197835246 :   24138 [L-FMU/LED]set_open_led_action(3344,73,0)
393.900 : 2197835576 :   24138 [L-FMU/LED]set_open_led_action(3344,71,1)
394.040 : 2198465711 :   24145 [L-FMU/LED]set_open_led_action(3344,71,0)
394.040 : 2198465893 :   24145 [L-FMU/LED]set_open_led_action(3344,73,1)
394.800 : 2201887026 :   24183 [L-FMU/LED]set_open_led_action(3344,73,0)
394.801 : 2201887212 :   24183 [L-FMU/LED]set_open_led_action(3344,71,1)
394.823 : 2201987169 :   24185 [L-FMU/LED]action changed. y_slow(0)
394.920 : 2202424775 :   24189 [L-FMU/LED]set_open_led_action(3344,71,0)
394.920 : 2202424956 :   24189 [L-FMU/LED]set_open_led_action(3344,73,1)
395.720 : 2206025047 :   24229 [L-FMU/LED]set_open_led_action(3344,73,0)
395.720 : 2206025229 :   24229 [L-FMU/LED]set_open_led_action(3344,71,1)
395.820 : 2206474638 :   24234 [L-FMU/LED]set_open_led_action(3344,71,0)
395.820 : 2206474827 :   24234 [L-FMU/LED]set_open_led_action(3344,73,1)
395.823 : 2206488135 :   24235 [L-FMU/LED]action changed. g_l(0)
401.032 : 2229929109 :   24495 [L-BATTERY]no space to save the ipc packet 15
412.500 : 2281534672 :   25068 [L-FMU/LED]set_open_led_action(3344,73,0)
412.500 : 2281534861 :   25068 [L-FMU/LED]set_open_led_action(3344,71,1)
412.620 : 2282074973 :   25074 [L-FMU/LED]set_open_led_action(3344,71,0)
412.620 : 2282075146 :   25074 [L-FMU/LED]set_open_led_action(3344,73,1)
412.680 : 2282346040 :   25077 [L-FMU/LED]set_open_led_action(3344,73,0)
412.680 : 2282346203 :   25077 [L-FMU/LED]set_open_led_action(3344,71,1)
412.863 : 2283167477 :   25087 [L-FMU/LED]action changed. y_slow(0)
412.920 : 2283425195 :   25089 [L-FMU/LED]set_open_led_action(3344,71,0)
412.920 : 2283425513 :   25089 [L-FMU/LED]set_open_led_action(3344,73,1)
412.980 : 2283695929 :   25092 [L-FMU/LED]set_open_led_action(3344,73,0)
412.980 : 2283696113 :   25092 [L-FMU/LED]set_open_led_action(3344,71,1)
414.520 : 2290624666 :   25169 [L-FMU/LED]set_open_led_action(3344,71,0)
414.720 : 2291525014 :   25179 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
414.720 : 2291525160 :   25179 [L-CMD]exec_fc_basic_function index 19
414.720 : 2291525375 :   25179 [L-API]on_hand_landing_check
414.720 : 2291525562 :   25179 [L-API]basic_cmd_on_hand_landing
414.863 : 2292167472 :   25187 [L-FMU/LED]action changed. Normal Flash(0)
416.300 : 2298635039 :   25258 [L-FMU/LED]set_open_led_action(3344,72,1)
416.303 : 2298649120 :   25259 [L-FMU/LED]action changed. y_fast(0)
416.520 : 2299624955 :   25269 [L-FMU/LED]set_open_led_action(3344,72,0)
416.520 : 2299625130 :   25269 [L-FMU/LED]set_open_led_action(3344,71,1)
416.623 : 2300087724 :   25275 [L-FMU/LED]action changed. y_slow(0)
417.601 : 2304487255 :   25323 [L-FMU/LED]set_open_led_action(3344,71,0)
417.601 : 2304487433 :   25323 [L-FMU/LED]set_open_led_action(3344,73,1)
417.623 : 2304587267 :   25325 [L-FMU/LED]action changed. g_l(0)
419.800 : 2314386953 :   25433 [L-FMU/LED]set_open_led_action(3344,73,0)
419.801 : 2314387147 :   25433 [L-FMU/LED]set_open_led_action(3344,71,1)
419.920 : 2314924768 :   25439 [L-FMU/LED]set_open_led_action(3344,71,0)
419.920 : 2314924942 :   25439 [L-FMU/LED]set_open_led_action(3344,73,1)
420.000 : 2315287083 :   25443 [L-FMU/LED]set_open_led_action(3344,73,0)
420.001 : 2315287265 :   25443 [L-FMU/LED]set_open_led_action(3344,71,1)
420.023 : 2315387297 :   25445 [L-FMU/LED]action changed. y_slow(0)
420.260 : 2316454886 :   25456 [L-FMU/LED]set_open_led_action(3344,71,0)
420.260 : 2316455067 :   25456 [L-FMU/LED]set_open_led_action(3344,73,1)
420.320 : 2316724854 :   25459 [L-FMU/LED]set_open_led_action(3344,73,0)
420.320 : 2316725033 :   25459 [L-FMU/LED]set_open_led_action(3344,71,1)
420.412 : 2317138499 :   25464 [L-BATTERY]no space to save the ipc packet 15
422.520 : 2326624843 :   25569 [L-FMU/LED]set_open_led_action(3344,71,0)
422.571 : 2326854656 :   25572 [L-FMU/FSM]not near ground
423.023 : 2328887360 :   25595 [L-FMU/LED]action changed. Normal Flash(0)
424.602 : 2335992572 :   25673 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
424.605 : 2336007598 :   25674 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
424.605 : 2336007860 :   25674 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
424.605 : 2336008551 :   25674 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
425.203 : 2338698705 :   25704 [L-RC]Emergency break. rc vib!
426.360 : 2343904907 :   25761 [L-FMU/LED]set_open_led_action(3344,74,1)
426.385 : 2344017924 :   25763 [L-FMU/LED]action changed. y_l(0)
426.405 : 2344106569 :   25764 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
426.500 : 2344535882 :   25768 [L-SDK]app API sub_mode 1 2
426.500 : 2344536038 :   25768 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
426.500 : 2344536172 :   25768 [L-SDK][USER]send ack 0x00
426.520 : 2344626019 :   25769 [L-SDK]app API sub_mode 1 2
426.520 : 2344626170 :   25769 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
426.520 : 2344626301 :   25769 [L-SDK][USER]send ack 0x00
426.560 : 2344805735 :   25771 [L-SDK]app API sub_mode 1 2
426.560 : 2344805893 :   25771 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
426.560 : 2344806036 :   25771 [L-SDK][USER]send ack 0x00
426.560 : 2344806601 :   25771 [L-SDK]app API sub_mode 1 2
426.560 : 2344806731 :   25771 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
426.560 : 2344806892 :   25771 [L-SDK][USER]send ack 0x00
426.580 : 2344896399 :   25772 [L-SDK]app API sub_mode 1 2
426.580 : 2344896552 :   25772 [L-MIS][NAVI MISSION] req sub_mode: Tracking on
426.580 : 2344896687 :   25772 [L-SDK][USER]send ack 0x00
429.160 : 2356505086 :   25901 [L-FMU/LED]set_open_led_action(3344,74,0)
429.160 : 2356505362 :   25901 [L-FMU/LED]set_open_led_action(3344,73,1)
429.263 : 2356968276 :   25907 [L-FMU/LED]action changed. g_l(0)
474.468 : 2560390361 :   28167 [L-BATTERY]no space to save the ipc packet 15
486.176 : 2613077632 :   28752 [L-FMU/FSM]near ground
491.380 : 2636496354 :   29012 [L-SDK]app API sub_mode 1 0
491.380 : 2636496503 :   29012 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
491.380 : 2636496634 :   29012 [L-SDK][USER]send ack 0x00
491.401 : 2636587196 :   29013 [L-SDK]app API sub_mode 1 0
491.401 : 2636587344 :   29013 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
491.401 : 2636587480 :   29013 [L-SDK][USER]send ack 0x00
491.420 : 2636675619 :   29014 [L-SDK]app API sub_mode 1 0
491.420 : 2636675821 :   29014 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
491.420 : 2636675949 :   29014 [L-SDK][USER]send ack 0x00
491.440 : 2636765675 :   29015 [L-FMU/LED]set_open_led_action(3344,73,0)
491.440 : 2636767044 :   29015 [L-SDK]app API sub_mode 1 0
491.441 : 2636767190 :   29015 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
491.441 : 2636767327 :   29015 [L-SDK][USER]send ack 0x00
491.460 : 2636855627 :   29016 [L-SDK]app API sub_mode 1 0
491.460 : 2636855818 :   29016 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
491.460 : 2636855985 :   29016 [L-SDK][USER]send ack 0x00
491.480 : 2636946525 :   29017 [L-SDK]app API sub_mode 1 0
491.480 : 2636946666 :   29017 [L-MIS][NAVI MISSION] req sub_mode: Tracking off
491.480 : 2636946813 :   29017 [L-SDK][USER]send ack 0x00
491.500 : 2637034653 :   29018 [L-FMU/LED]set_open_led_action(3344,72,1)
491.500 : 2637036396 :   29018 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
491.503 : 2637048502 :   29019 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
491.503 : 2637048701 :   29019 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
491.503 : 2637049462 :   29019 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
491.523 : 2637137058 :   29020 [L-FMU/LED]type:0, normal flash action:
491.523 : 2637137346 :   29020 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
491.663 : 2637769256 :   29027 [L-FMU/LED]action changed. y_fast(0)
491.900 : 2638834895 :   29038 [L-FMU/LED]set_open_led_action(3344,72,0)
491.900 : 2638835081 :   29038 [L-FMU/LED]set_open_led_action(3344,71,1)
491.985 : 2639216880 :   29043 [L-FMU/LED]action changed. y_slow(0)
492.243 : 2640376839 :   29056 [L-RC]Emergency break. rc vib!
493.320 : 2645224963 :   29109 [L-FMU/LED]set_open_led_action(3344,71,0)
493.320 : 2645225140 :   29109 [L-FMU/LED]set_open_led_action(3344,73,1)
493.443 : 2645777419 :   29116 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION API_MODE ctrl_API
493.500 : 2646035978 :   29118 [L-SDK]app API sub_mode 4 2
493.500 : 2646036141 :   29118 [L-MIS][NAVI MISSION] req sub_mode: Gesture on
493.500 : 2646036274 :   29118 [L-SDK][USER]send ack 0x00
493.723 : 2647037437 :   29130 [L-FMU/LED]type:0, normal flash action:
493.723 : 2647037723 :   29130 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
493.985 : 2648216872 :   29143 [L-FMU/LED]action changed. g_l(0)
501.620 : 2682574907 :   29524 [L-FMU/LED]set_open_led_action(3344,73,0)
501.620 : 2682575082 :   29524 [L-FMU/LED]set_open_led_action(3344,71,1)
501.663 : 2682767525 :   29527 [L-FMU/LED]action changed. y_slow(0)
501.740 : 2683115520 :   29530 [L-FMU/LED]set_open_led_action(3344,71,0)
501.740 : 2683115752 :   29530 [L-FMU/LED]set_open_led_action(3344,73,1)
501.781 : 2683299631 :   29533 [L-FMU/FSM]not near ground
502.663 : 2687267594 :   29577 [L-FMU/LED]action changed. g_l(0)
502.821 : 2687979601 :   29585 [L-FMU/FSM]near ground
504.500 : 2695535024 :   29668 [L-FMU/LED]set_open_led_action(3344,73,0)
504.500 : 2695535203 :   29668 [L-FMU/LED]set_open_led_action(3344,71,1)
504.583 : 2695909035 :   29673 [L-FMU/LED]action changed. y_slow(0)
504.620 : 2696074829 :   29674 [L-FMU/LED]set_open_led_action(3344,71,0)
504.620 : 2696075008 :   29674 [L-FMU/LED]set_open_led_action(3344,73,1)
504.700 : 2696435043 :   29678 [L-FMU/LED]set_open_led_action(3344,73,0)
504.700 : 2696435221 :   29678 [L-FMU/LED]set_open_led_action(3344,71,1)
506.000 : 2702285089 :   29743 [L-FMU/LED]set_open_led_action(3344,71,0)
506.220 : 2703274437 :   29754 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
506.220 : 2703274589 :   29754 [L-CMD]exec_fc_basic_function index 19
506.220 : 2703274718 :   29754 [L-API]on_hand_landing_check
506.220 : 2703274828 :   29754 [L-API]basic_cmd_on_hand_landing
506.583 : 2704908881 :   29773 [L-FMU/LED]action changed. Normal Flash(0)
506.640 : 2705165375 :   29775 [L-FMU/LED]set_open_led_action(3344,71,1)
506.663 : 2705267566 :   29777 [L-FMU/LED]action changed. y_slow(0)
506.700 : 2705434823 :   29778 [L-FMU/LED]set_open_led_action(3344,71,0)
506.800 : 2705886944 :   29783 [L-FMU/LED]set_open_led_action(3344,71,1)
508.120 : 2711824868 :   29849 [L-FMU/LED]set_open_led_action(3344,71,0)
508.120 : 2711825049 :   29849 [L-FMU/LED]set_open_led_action(3344,73,1)
508.663 : 2714267835 :   29877 [L-FMU/LED]action changed. g_l(0)
510.120 : 2720824737 :   29949 [L-FMU/LED]set_open_led_action(3344,73,0)
510.120 : 2720824918 :   29949 [L-FMU/LED]set_open_led_action(3344,71,1)
510.340 : 2721815158 :   29960 [L-FMU/LED]set_open_led_action(3344,71,0)
510.340 : 2721815427 :   29960 [L-FMU/LED]set_open_led_action(3344,73,1)
510.400 : 2722084668 :   29963 [L-FMU/LED]set_open_led_action(3344,73,0)
510.400 : 2722084857 :   29963 [L-FMU/LED]set_open_led_action(3344,71,1)
510.583 : 2722909112 :   29973 [L-FMU/LED]action changed. y_slow(0)
511.188 : 2725630413 :   30003 [L-BATTERY]no space to save the ipc packet 15
511.520 : 2727124818 :   30019 [L-FMU/LED]set_open_led_action(3344,71,0)
511.583 : 2727409090 :   30023 [L-FMU/LED]action changed. Normal Flash(0)
511.640 : 2727665576 :   30025 [L-FMU/LED]set_open_led_action(3344,71,1)
511.663 : 2727767338 :   30027 [L-FMU/LED]action changed. y_slow(0)
512.300 : 2730634901 :   30058 [L-FMU/LED]set_open_led_action(3344,71,0)
512.520 : 2731624529 :   30069 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
512.520 : 2731624694 :   30069 [L-CMD]exec_fc_basic_function index 19
512.520 : 2731624829 :   30069 [L-API]on_hand_landing_check
512.520 : 2731624943 :   30069 [L-API]basic_cmd_on_hand_landing
512.663 : 2732267672 :   30077 [L-FMU/LED]action changed. Normal Flash(0)
513.740 : 2737115892 :   30130 [L-FMU/LED]set_open_led_action(3344,71,1)
513.745 : 2737137392 :   30131 [L-FMU/LED]action changed. y_slow(0)
514.920 : 2742424979 :   30189 [L-FMU/LED]set_open_led_action(3344,71,0)
514.920 : 2742425159 :   30189 [L-FMU/LED]set_open_led_action(3344,73,1)
515.743 : 2746129029 :   30231 [L-FMU/LED]action changed. g_l(0)
516.900 : 2751334679 :   30288 [L-FMU/LED]set_open_led_action(3344,73,0)
516.900 : 2751334867 :   30288 [L-FMU/LED]set_open_led_action(3344,71,1)
516.943 : 2751528276 :   30291 [L-FMU/LED]action changed. y_slow(0)
517.040 : 2751965462 :   30295 [L-FMU/LED]set_open_led_action(3344,71,0)
517.040 : 2751965753 :   30295 [L-FMU/LED]set_open_led_action(3344,73,1)
517.100 : 2752235007 :   30298 [L-FMU/LED]set_open_led_action(3344,73,0)
517.100 : 2752235190 :   30298 [L-FMU/LED]set_open_led_action(3344,71,1)
518.420 : 2758174891 :   30364 [L-FMU/LED]set_open_led_action(3344,71,0)
518.580 : 2758896041 :   30372 [L-FMU/LED]set_open_led_action(3344,71,1)
519.160 : 2761504766 :   30401 [L-FMU/LED]set_open_led_action(3344,71,0)
519.320 : 2762224796 :   30409 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
519.320 : 2762224969 :   30409 [L-CMD]exec_fc_basic_function index 19
519.320 : 2762225089 :   30409 [L-API]on_hand_landing_check
519.320 : 2762225192 :   30409 [L-API]basic_cmd_on_hand_landing
519.500 : 2763034651 :   30418 [L-FMU/LED]set_open_led_action(3344,71,1)
520.000 : 2765286639 :   30443 [L-FMU/LED]set_open_led_action(3344,71,0)
520.370 : 2766950734 :   30462 [L-BATTERY]no space to save the ipc packet 15
520.943 : 2769528909 :   30491 [L-FMU/LED]action changed. Normal Flash(0)
522.900 : 2778334862 :   30588 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
522.900 : 2778335030 :   30588 [L-CMD]exec_fc_basic_function index 19
522.900 : 2778335154 :   30588 [L-API]on_hand_landing_check
522.900 : 2778335261 :   30588 [L-API]basic_cmd_on_hand_landing
526.300 : 2793635827 :   30758 [L-FLYMODE]CTRL reset target mode by USER.mission.request.off 12
526.303 : 2793647731 :   30759 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
526.303 : 2793647902 :   30759 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
526.303 : 2793648623 :   30759 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
526.520 : 2794624827 :   30769 [L-API]get_id_index_by_basic_cmd: cmd 32 index 19
526.520 : 2794624976 :   30769 [L-CMD]exec_fc_basic_function index 19
526.520 : 2794625098 :   30769 [L-API]on_hand_landing_check
526.520 : 2794625206 :   30769 [L-API]basic_cmd_on_hand_landing
526.606 : 2795011705 :   30774 [L-IMU][IMU_PROPELLER_PRO] never revise bit enable. |
527.600 : 2799484878 :   30823 [L-FMU/LED]set_open_led_action(3344,72,1)
527.623 : 2799587177 :   30825 [L-FMU/LED]action changed. y_fast(0)
527.720 : 2800025237 :   30829 [L-FMU/LED]set_open_led_action(3344,72,0)
527.783 : 2800309285 :   30833 [L-FMU/LED]action changed. Normal Flash(0)
530.994 : 2814759479 :   30993 [L-NS][AHRS] yaw aligned 1
540.141 : 2855919660 :   31451 [L-FMU/FSM]not near ground
540.886 : 2859272141 :   31488 [L-FMU/FSM]near ground
554.120 : 2918824629 :   32149 [L-MIS][SDK] old open GS(app)
554.120 : 2918824779 :   32149 [L-MIS]received on/off 1 from can
554.120 : 2918824941 :   32149 [L-MIS]ack on/off 0 to can
554.620 : 2921074860 :   32174 [L-MIS][IOC]enter tripod by GS
554.623 : 2921087546 :   32175 [L-CTRL]enter tripod mode
554.623 : 2921087869 :   32175 [L-FLYMODE][Ctrl<3>] REQ_NAVI_MISSION ATTI_HOLD_TRIPOD ctrl_tripod
556.676 : 2930327585 :   32277 [L-FMU/FSM]not near ground
597.243 : 3112876830 :   34306 [L-RC]rc cmd:STD_PAUSE_CUR_MIS
597.243 : 3112877477 :   34306 [L-FLYMODE]CTRL rc pause gps_atti
598.043 : 3116476668 :   34346 [L-RC]Emergency break. rc vib!
598.125 : 3116846632 :   34350 [L-FMU/LED]type:0, normal flash action:
598.125 : 3116846939 :   34350 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
600.323 : 3126737156 :   34460 [L-FMU/LED]type:0, normal flash action:
600.323 : 3126737432 :   34460 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
604.483 : 3145456790 :   34668 [L-RC]rc cmd:STD_PAUSE_CUR_MIS
604.483 : 3145457443 :   34668 [L-FLYMODE]CTRL rc pause gps_atti
605.283 : 3149056490 :   34708 [L-RC]Emergency break. rc vib!
605.723 : 3151037608 :   34730 [L-FMU/LED]type:0, normal flash action:
605.723 : 3151037878 :   34730 [L-FMU/LED]c0:0,1;c1:0,1;c2:0,1;c3:2,3;c4:0,1;c5:0,1;c6:0,1;c7:0,1
607.703 : 3159947908 :   34829 [L-FMU/LED]type:0, normal flash action:
607.703 : 3159948189 :   34829 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
608.540 : 3163715210 :   34870 [L-MIS][IOC]stop tripod
608.543 : 3163727658 :   34871 [L-FLYMODE]CTRL reset all by APP.mission.tripod.no.mission
608.562 : 3163816172 :   34872 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
609.020 : 3165874855 :   34894 [L-MIS][SDK] old open GS(app)
609.020 : 3165875010 :   34894 [L-MIS]received on/off 2 from can
609.020 : 3165875162 :   34894 [L-FLYMODE]CTRL reset target mode by APP.mission.request.off 12
609.020 : 3165875377 :   34894 [L-MIS]ack on/off 0 to can
609.023 : 3165886972 :   34895 [L-FLYMODE]CTRL reset target mode by ctrl_dev_changed 12
609.023 : 3165887144 :   34895 [L-MIS][SDK]reset user_emergency_brake by ctrl dev changing
617.267 : 3202985737 :   35307 [L-BATTERY]no space to save the ipc packet 15
619.406 : 3212612114 :   35414 [L-FMU/FSM]near ground
622.370 : 3225950866 :   35562 [L-BATTERY]no space to save the ipc packet 15
630.525 : 3262648061 :   35970 [L-BATTERY]no space to save the ipc packet 15
630.703 : 3263446633 :   35979 [L-RC]mode switch changed!
630.703 : 3263447417 :   35979 [L-FLYMODE][RC] mode switch changed
630.703 : 3263447580 :   35979 [L-FLYMODE]CTRL reset all by rc mode switch
631.103 : 3265248108 :   35999 [L-FMU/LED]type:0, normal flash action:
631.103 : 3265248563 :   35999 [L-FMU/LED]c0:0,1;c1:0,3;c2:0,1;c3:2,3;c4:0,3;c5:0,3;c6:0,1;c7:0,3
631.186 : 3265622140 :   36003 [L-FMU/FSM]not near ground
631.586 : 3267422141 :   36023 [L-FMU/FSM]near ground
649.651 : 3348714628 :   36926 [L-FMU/FSM]not near ground
650.603 : 3352997303 :   36974 [L-FMU/MOTOR]safe_near_grd:false
665.442 : 3419775762 :   37716 [L-FMU/MOTOR]safe_near_grd:true
665.671 : 3420804640 :   37727 [L-FMU/FSM]near ground
666.230 : 3423320802 :   37755 [L-BATTERY]no space to save the ipc packet 15
671.083 : 3445156813 :   37998 [L-RC]mode switch changed!
671.083 : 3445157569 :   37998 [L-FLYMODE][RC] mode switch changed
671.083 : 3445157715 :   37998 [L-FLYMODE]CTRL reset all by rc mode switch
671.423 : 3446687341 :   38015 [L-FMU/LED]type:0, normal flash action:
671.423 : 3446687619 :   38015 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
673.931 : 3457974637 :   38140 [L-FMU/FSM]not near ground
675.771 : 3466254666 :   38232 [L-FMU/FSM]near ground
675.791 : 3466344629 :   38233 [L-FMU/FSM]not near ground
677.086 : 3472172185 :   38298 [L-FMU/FSM]near ground
681.527 : 3492156155 :   38520 [L-BATTERY]no space to save the ipc packet 15
689.688 : 3528880537 :   38928 [L-BATTERY]no space to save the ipc packet 15
706.911 : 3606384597 :   39789 [L-FMU/FSM]not near ground
707.822 : 3610485150 :   39835 [L-FMU/MOTOR]safe_near_grd:false
713.002 : 3633795417 :   40094 [L-FMU/MOTOR]safe_near_grd:true
715.961 : 3647109629 :   40242 [L-FMU/FSM]near ground
718.223 : 3657287248 :   40355 [L-FMU/LED]action changed. battery warning!:battery_status_data.capacity_level1_status
719.100 : 3661235142 :   40398 [L-API]get_id_index_by_basic_cmd: cmd 2 index 1
719.100 : 3661235391 :   40398 [L-CMD]exec_fc_basic_function index 1
719.100 : 3661235579 :   40398 [L-API]auto_landing_check
719.100 : 3661235750 :   40398 [L-API]basic_cmd_auto_landing
719.203 : 3661696827 :   40404 [L-FLYMODE][Ctrl<5>] REQ_APP AUTO_LANDING ctrl_auto_landing
720.003 : 3665296214 :   40444 [L-RC]Start landing. rc vib!
720.466 : 3667382086 :   40467 [L-FMU/FSM]not near ground
720.681 : 3668349615 :   40478 [L-FMU/FSM]near ground
723.606 : 3681512150 :   40624 [L-FMU/FSM]state changed. cur: on ground
723.642 : 3681673946 :   40626 [L-FMU/MOTOR] Stop. reason:ACT.landing
723.642 : 3681674180 :   40626 [L-FMU/MOTOR]Total start times: 1, time: 723.82
723.642 : 3681674419 :   40626 [L-PWM]set actuator mode:IDLE
723.642 : 3681674782 :   40626 [L-FLYMODE]CTRL reset all by motor stopped
723.643 : 3681677433 :   40626 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
723.646 : 3681692139 :   40626 [L-FMU/FSM]state changed. cur: motor off
723.660 : 3681756478 :   40627 [L-IMU]set imu switch level = 1
723.662 : 3681765298 :   40627 [L-FLYMODE][LANDING] reset landing status
723.814 : 3682448100 :   40634 [L-NS][AHRS] connect us . :0
724.706 : 3686462066 :   40679 [L-FMU/FSM]not near ground
726.222 : 3693284176 :   40755 [L-FMU/MOTOR]safe_near_grd:false
736.607 : 3740015051 :   41274 [L-BATTERY]no space to save the ipc packet 15

Hi, I just received the email instruction from DJI support:

Dear Luis,

Thank you for contacting DJI Technical Support. We understand that you suddenly received magnetic field interference and weak GPS signal error with your Spark. Don’t worry as we will do our best to help you with this concern.

In this case, may we ask if you are using the latest firmware version for both your aircraft and remote controller? Before this issue happened, did you had an update on your drone or DJI Go App? We suggest that you do IMU and Compass Calibration again to make sure that everything is working fine before flying your drone.

Compass Calibration:
1. Choose an open area to conduct the compass calibration.        
2. Tap the Aircraft Status bar in the app and select «Calibrate», then follow the on-screen instructions.        
3. Hold the aircraft horizontally and rotate 360 degrees. The aircraft status indicators will go solid green.        
4. Hold the aircraft vertically with the nose pointing downward, and rotate it 360 degrees around the center axis.        
5. Recalibrate the aircraft if the status indicators blink red.        
If the status indicators blink red and yellow after the calibration procedure, move your aircraft to a different location and try again.        

IMU Calibration:
1. Make sure that the Aircraft and Remote Controller battery is more than 50%.  
2. Turn on Remote Controller and connect to the Mobile Device.  
3. Place the Aircraft on a level surface.  
4. Turn on the Aircraft.      
5. Launch DJI Go app and go to Main Controller settings > Advanced Settings> Sensors> IMU Calibration> Start Calibration.  
6. The calibration process will take about 5 minutes. Please wait for the confirmation on DJI Go app.  
7. IMU Calibration will fail if the aircraft is not positioned according to the instruction on DJI GO app.  
8. If calibration fails, restart the aircraft and calibrate the IMU again.  

Also, please do try to re-link your remote controller and your aircraft to make sure that they both have a fresh connection again. Please do follow the guide below.

Linking the Remote Controller:        
1. Power on the aircraft and the remote controller. Wait until the aircraft status indicators blink yellow. Ensure that the remote controller is within 20 cm of the aircraft during linking.        
2. Press and hold the power button of the Intelligent Flight Battery for three seconds. Release the button after hearing a single beep. The Front LEDs will blink red.        
3. Press and hold the Flight Pause button, the Function button, and the Customizable button simultaneously.        
Linking begins when the alarm becomes a quick single beep after an alternating single/double beep.        
4. Then the front LEDs turn solid red after blinking green. When the status LED on the remote controller turns solid green, linking is complete.        

We will be waiting for your response.
Thank you and may you have a nice day.
Thank you for supporting DJI.

Понравилась статья? Поделить с друзьями:

Интересное по теме:

  • Ошибка кода 5100 основной шлюз указан неверно
  • Ошибка компас ошибка при направлении команды приложению
  • Ошибка компилятора cs0029
  • Ошибка компилятора c3861
  • Ошибка кода 5022 tp link

  • Добавить комментарий

    ;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: