Help! Almost lost it in ATTI mode!

[Dronason]

Same problem yesterday. After 5 minutes of flight (not in sport mode) compass error , magnetic interference , gps signal lost and drifting for 20 secundes. Airdata UAV - Flight Data Analysis for Drones . I have extracted csv from dat also FLY057.csv . Kp index was ok , checked with uav forecast.

Can you share the CSV ? Would be interesting to see if it comes from compass or GPS error.

 

[sebip]

The links are in my post

 

[sebip]

 

[Dronason]

The links are in my post

Thanks, will have a look on it.

 

[Dronason]

The flight you show in Airdata UAV is not the same as in the CSV ?
Was the one in the CSV having the same problem ?

PS: In CsvView, the best is to open several graph windows with few plots in each. The cursor and zoom will be sync across these windows. This is valid also for the GeoPlayer window.
The MagDataPlayer will not be sync but it will plot the current zoomed area. Best is to zoom on fly time and then open MagDataPlayer. Refer to the doc for more info.

 

[AndrewA]

Same problem yesterday. After 5 minutes of flight (not in sport mode) compass error , magnetic interference , gps signal lost and drifting for 20 secundes. Airdata UAV - Flight Data Analysis for Drones . I have extracted csv from dat also FLY057.csv . Kp index was ok , checked with uav forecast.

What kind of construction in the stadium? It looks like lighting or loudspeakers. I got an issue like this when make a turn for flight back to home point and rear part of the Spark (where compass is located) was pointed directly to power line. I post video with my thoughts above.

 

[Dronason]

Can

What kind of construction in the stadium? It looks like lighting or loudspeakers. I got an issue like this when make a turn for flight back to home point and rear part of the Spark (where compass is located) was pointed directly to power line. I post video with my thoughts above.

Regarding power line, I have a big one where I usually fly and never had an issue. With my PH3 I had even flown above or behind with no problem.
If it would be some cell phone/radio pylon, yes there would be a risk.
Can you share the DAT file ? If would like to have a look on it and see if the power line could have an effect so I see if I am at risk too.

 

[AndrewA]

Regarding power line, I have a big one where I usually fly and never had an issue. With my PH3 I had even flown above or behind with no problem.
I

Power lines can be the source of high-frequency interference mainly due to the so-called "corona discharge". It make short duration (6-7ms) repetitive impulses in the high-frequency spectrum and not always exists. So you can one day fly near power lines without any problem and on the next day get a crash because Spark electronics malfunction. There is also exists "Spark discharge" effect. I'll try to upload DAT file.

 

[Dronason]

Power lines can be the source of high-frequency interference mainly due to the so-called "corona discharge". It make short duration (6-7ms) repetitive impulses in the high-frequency spectrum and not always exists. So you can one day fly near power lines without any problem and on the next day get a crash because Spark electronics malfunction. There is also exists "Spark discharge" effect. I'll try to upload DAT file.

I see what you mean. That's true that I avoid to fly when it is too much wet.
Hope you can link the DAT, that's interesting to see potential problem before they come to you.

 

[sebip]

I have flied many times in area. And after incident i fly the second battery without problems in same place . I m playing with RC from 10 years , mostly rc fpv fixed wings ,so i m aware about possible factors of disturbances . It is my first p&p model , dji.
Digging on dat files i see one message about google can not give me any result " [L-BATTERY]no space to save the ipc packet "

 

[sebip]

What kind of construction in the stadium? It looks like lighting or loudspeakers. I got an issue like this when make a turn for flight back to home point and rear part of the Spark (where compass is located) was pointed directly to power line. I post video with my thoughts above.

I have same yaw difference like in your video.

 

[sebip]

The flight you show in Airdata UAV is not the same as in the CSV ?
Was the one in the CSV having the same problem ?

PS: In CsvView, the best is to open several graph windows with few plots in each. The cursor and zoom will be sync across these windows. This is valid also for the GeoPlayer window.
The MagDataPlayer will not be sync but it will plot the current zoomed area. Best is to zoom on fly time and then open MagDataPlayer. Refer to the doc for more info.

In airdata is the txt file from smartphone. the csv is from dat . Here is the .dat file

 

[Dronason]

DAT file is same as CSV.

Strange how different it looks from CsvView and from Airdata.

2017-09-11 20:04:36 2017-09-11 19:50

Date seems also to be not the same.

 

[sebip]

It seems I have make a big mistake . I posted logs from the second flight.
here is my complet .dat file .

 

[sebip]

here is my whole .dat file

 

[Dronason]

Seems that the related flight is FLY056 but it contains only the end of the flight.

Blue bar is the orientation from the compass, Green bar is the orientation from the flight controller. They are not the same but for only some moment.
The missing part is where there was your issue, but also in this part it was close to declare a compass error (Yaw error). This is most probably what happened in the first part of the flight. There was large difference between the orientation reported by compass and flight controller. Then the Spark warn the pilot and give him full manual control (ATTI mode).

In the available flight section, there was very large change of the magnetic module (normally magnetic field of earth is constant) when the Spark was rotating.
It changed from 1900 down to 1700 and then up again.
The second graph is a flight with mine where the Mag:Mod remain constant is the Spark is rotating.


The Mag:Mod value should not change that much when the Spark is at some altitude, either there was close metallic structure (< 10 meters) or your compass is wrongly calibrated.
From the altitude and the area where it was, there is much more chance of a compass calibration issue. Of coarse internal failure of the Spark is another possibility.

If you had already calibrated it, maybe you should redo and check if your procedure was correct. Follow the instructions which are given by the Go4 app.

You can also refer to DJI Spark Accessories & Tips - Spark Help

 

[sebip]

dat for 56
extracted logs from 56
Before flight in app all sensors was withot warnings.
in 56 log.txt i have battery messages , appearing in all flight with this battery
29.755 : 2643297455 : 29088 [L-BATTERY]no space to save the ipc packet 15
38.938 : 2684620882 : 29547 [L-BATTERY]no space to save the ipc packet 15
40.978 : 2693799985 : 29649 [L-BATTERY]no space to save the ipc packet 15
41.998 : 2698390211 : 29700 [L-BATTERY]no space to save the ipc packet 15
43.018 : 2702979803 : 29751 [L-BATTERY]no space to save the ipc packet 15
44.037 : 2707565903 : 29802 [L-BATTERY]no space to save the ipc packet 15
91.985 : 2923333547 : 32199 [L-BATTERY]no space to save the ipc packet 17
92.998 : 2927890257 : 32250 [L-BATTERY]no space to save the ipc packet 15
94.017 : 2932476078 : 32301 [L-BATTERY]no space to save the ipc packet 15
101.153 : 2964587522 : 32658 [L-BATTERY]no space to save the ipc packet 15
168.473 : 3267527394 : 36024 [L-BATTERY]no space to save the ipc packet 15
169.495 : 3272128078 : 36075 [L-BATTERY]no space to save the ipc packet 15
170.518 : 3276730166 : 36126 [L-BATTERY]no space to save the ipc packet 15
172.553 : 3285887879 : 36228 [L-BATTERY]no space to save the ipc packet 15
173.577 : 3290495825 : 36279 [L-BATTERY]no space to save the ipc packet 15
174.597 : 3295086290 : 36330 [L-BATTERY]no space to save the ipc packet 15
176.617 : 3304176019 : 36431 [L-BATTERY]no space to save the ipc packet 15
177.635 : 3308758511 : 36482 [L-BATTERY]no space to save the ipc packet 15
178.655 : 3313347772 : 36533 [L-BATTERY]no space to save the ipc packet 15
179.677 : 3317946054 : 36584 [L-BATTERY]no space to save the ipc packet 15
180.695 : 3322528224 : 36635 [L-BATTERY]no space to save the ipc packet 15
181.718 : 3327129981 : 36686 [L-BATTERY]no space to save the ipc packet 15
182.737 : 3331716242 : 36737 [L-BATTERY]no space to save the ipc packet 15
183.758 : 3336310427 : 36788 [L-BATTERY]no space to save the ipc packet 15
185.795 : 3345478022 : 36890 [L-BATTERY]no space to save the ipc packet 15
186.817 : 3350075991 : 36941 [L-BATTERY]no space to save the ipc packet 15
187.835 : 3354658378 : 36992 [L-BATTERY]no space to save the ipc packet 15
189.875 : 3363837869 : 37094 [L-BATTERY]no space to save the ipc packet 15
190.897 : 3368436226 : 37145 [L-BATTERY]no space to save the ipc packet 15
191.918 : 3373030045 : 37196 [L-BATTERY]no space to save the ipc packet 15
192.937 : 3377616333 : 37247 [L-BATTERY]no space to save the ipc packet 15
194.985 : 3386833616 : 37349 [L-BATTERY]no space to save the ipc packet 17
196.005 : 3391422998 : 37400 [L-BATTERY]no space to save the ipc packet 17
197.005 : 3395923577 : 37450 [L-BATTERY]no space to save the ipc packet 17
197.017 : 3395975757 : 37451 [L-BATTERY]no space to save the ipc packet 15
197.017 : 3395976233 : 37451 [L-BATTERY]no space to save the ipc packet 15
198.045 : 3400602883 : 37502 [L-BATTERY]no space to save the ipc packet 17
199.065 : 3405192504 : 37553 [L-BATTERY]no space to save the ipc packet 17
200.073 : 3409727089 : 37604 [L-BATTERY]no space to save the ipc packet 15
200.073 : 3409727567 : 37604 [L-BATTERY]no space to save the ipc packet 15
219.308 : 3496286190 : 38566 [L-FMU/LED]action changed. battery warning!:battery_status_data.capacity_level1_status
245.805 : 3615523406 : 39890 [L-API]set battery go home status:2
249.968 : 3634253910 : 40099 [L-FMU/MOTOR]safe_near_grd:true
251.901 : 3642954620 : 40195 [L-FMU/FSM]near ground
252.506 : 3645676921 : 40226 [L-FMU/FSM]not near ground
252.901 : 3647454606 : 40245 [L-FMU/FSM]near ground
253.865 : 3651792396 : 40293 [L-API]get_id_index_by_basic_cmd: cmd 2 index 1
253.865 : 3651792660 : 40293 [L-CMD]exec_fc_basic_function index 1
253.865 : 3651792850 : 40293 [L-API]auto_landing_check
253.865 : 3651793044 : 40293 [L-API]basic_cmd_auto_landing
253.968 : 3652255320 : 40299 [L-FLYMODE][Ctrl<5>] REQ_APP AUTO_LANDING ctrl_auto_landing
254.106 : 3652876910 : 40306 [L-FMU/FSM]not near ground
254.588 : 3655044850 : 40330 [L-RC]Start landing. rc vib!
255.101 : 3657354651 : 40355 [L-FMU/FSM]near ground
255.631 : 3659739349 : 40382 [L-FMU/FSM]not near ground
255.846 : 3660707002 : 40393 [L-FMU/FSM]near ground
258.471 : 3672519415 : 40524 [L-FMU/FSM]state changed. cur: on ground
258.507 : 3672682474 : 40526 [L-FMU/MOTOR] Stop. reason:ACT.landing

 

[Dronason]

That's often the problem, the warnings come from Go4 app only when it is almost too late.
Probably the message related to battery is just that the battery voltage need to be stored in the flight record but it fails to.

 

[sebip]

also today i have connected the spark to pc and fan h

Seems that the related flight is FLY056 but it contains only the end of the flight.
View attachment 1265
Blue bar is the orientation from the compass, Green bar is the orientation from the flight controller. They are not the same but for only some moment.
The missing part is where there was your issue, but also in this part it was close to declare a compass error (Yaw error). This is most probably what happened in the first part of the flight. There was large difference between the orientation reported by compass and flight controller. Then the Spark warn the pilot and give him full manual control (ATTI mode).

In the available flight section, there was very large change of the magnetic module (normally magnetic field of earth is constant) when the Spark was rotating.
It changed from 1900 down to 1700 and then up again.
The second graph is a flight with mine where the Mag:Mod remain constant is the Spark is rotating.
View attachment 1266

The Mag:Mod value should not change that much when the Spark is at some altitude, either there was close metallic structure (< 10 meters) or your compass is wrongly calibrated.
From the altitude and the area where it was, there is much more chance of a compass calibration issue. Of coarse internal failure of the Spark is another possibility.

If you had already calibrated it, maybe you should redo and check if your procedure was correct. Follow the instructions which are given by the Go4 app.

You can also refer to DJI Spark Accessories & Tips - Spark Help

I that spot i not have any problem in flight and the drone was rotated by me

 

[SeaD]

I was flying this morning in the hills. Nothing around. No problems. Using the remote connected with OTG cable. Had 13 GPS signals. The Spark was about 100 ft up and 100 ft out when all of a sudden I get some kind of GPS disconnect notice and then the voice saying something about ATTI mode and the ATTI sign on the screen. The Spark took off like a bat out of hell in what seemed to be the Sport mode. I lost sight almost immediately and figured it was not going to end well. I looked at the map and turned it to head to the home point, I was hoping, but not sure. I could hear the Spark... finally saw it up quite high. Then GPS came back and I flew it home. WTF? I have no idea what happened. What should I have done? Anything different? I assumed the compass still worked so pointing the arrow home seemed the right thing to do. Any thoughts? This was very scary. I was sure it was gone in the hills forever.

On September 10 there was a geomagnetic storm from an X class solar flare. The radiation made it all the way to the ground. It did disrupt GPS operations.
No idea if this was the cause but?
It was very unusual and disturbances were brief.
SpaceWeather.com -- News and information about meteor showers, solar flares, auroras, and near-Earth asteroids