Welcome DJI Spark Pilot!
Jump in and join our free Spark community today!
Sign up

Help! Almost lost it in ATTI mode!

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
There is a bug in DatCon that is causing the initial part of this flight to be omitted. At the moment I'm unable to create a new version. But, attached is a .zip that contains the full FLY056.csv. You should be able to submit this directly to CsvView

@sebip
 

Attachments

  • FLY056.csv.zip
    8.1 MB · Views: 6
  • Like
Reactions: sebip and Dronason
There is a bug in DatCon that is causing the initial part of this flight to be omitted. At the moment I'm unable to create a new version. But, attached is a .zip that contains the full FLY056.csv. You should be able to submit this directly to CsvView

@sebip
Great, many thanks for it.
 
  • Like
Reactions: 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
.......

This comes from the Spark's eventLog stream which is contained in the .DAT. DatCon doesn't create this, it just copies what's in the .DAT to this file. The eventLog stream seems to change format and contents with every firmware. Most of the time I don't find it very useful. In this case I can't even speculate what these messages mean.
 
  • Like
Reactions: sebip
Where did you see it?
 
Sorry about that, was reading another post about possibly losing the spark due to solar flares. And P mode was mention. Dont know how my question ended up here.
No problem, happy fly.
 
There is a bug in DatCon that is causing the initial part of this flight to be omitted. At the moment I'm unable to create a new version. But, attached is a .zip that contains the full FLY056.csv. You should be able to submit this directly to CsvView

@sebip
Thank you ,you are more helpful than dji support !!!
 
  • Like
Reactions: notime
A high Kp index may have caused the loss of satellites, esp. as there have been only 13 to begin with.

However, the flight behaviour of the Spark in Atti mode seems to be the real culprit here. It should be no problem for a DJI drone to auto-calibrate in P mode and remain more or less hovering in Atti mode. Drifting with the wind but no more. A phantom can be flewn in Atti mode with no problem.

Spark /Atti needs to be watched.
What is P mode? Insee it mentioned in the spark manual but it doesn't say what P mode actually is.
 
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.


That’s how I lost my spark, same way
 
That’s how I lost my spark, same way
I've talked to Tech support a number of times now and basically, they say recalibrate the compass, refresh the firmware or send it in. I really don't think there's anything "wrong" with my Spark. I think it's something with the way the Spark handles these "weak GPS" warnings. I've recalibrate the compass and refreshed the firmware and calibrated them IMU, so I'll see how it goes. Two weeks until my road trip and I was planning some over water, looking back at the coast shots. I'm pretty stressed about doing that now.
 
This comes from the Spark's eventLog stream which is contained in the .DAT. DatCon doesn't create this, it just copies what's in the .DAT to this file. The eventLog stream seems to change format and contents with every firmware. Most of the time I don't find it very useful. In this case I can't even speculate what these messages mean.
is asked cause i have think i have one defect battery , when i connect the spark at pc trough usb and power on the drone internal fan and led lights are not starting always . if power on the spark and after that connect usb is starting normally .
Dropbox - DJI_ASSISTANT_EXPORT_FILE_2017-09-13_13-25-47.DAT dat file for fan not starting
And out of the drone light on battery stay on .
 
My problem was in 11 september
Back to the original question, now, thanks to @BudWalker, we have more data.
As previously said, your compass seems to change a lot. As you where high in altitude, the compass output should not change that much when you rotate. it change from 1600 to 1900.

In blue first, there was already some error between the compas and the yaw position calculated by the Spark flight controller. In a second rotation maneuver there was again some error, but not enough to trigger an error. Finally in red, again an error and this one triggered the ATTI mode. During the ATTI mode you where able to stop its drift and the error becomes low enough to stop the ATTI and be back to GPS control.
Capture90.PNG

So the compass need to be recalibrate in an open area, better in a remote area.
You would also do an IMU calibration as it is quick to do.
If it happen again, there is also the possibility that the compass sensor has a problem.
 
is asked cause i have think i have one defect battery , when i connect the spark at pc trough usb and power on the drone internal fan and led lights are not starting always . if power on the spark and after that connect usb is starting normally .
Dropbox - DJI_ASSISTANT_EXPORT_FILE_2017-09-13_13-25-47.DAT dat file for fan not starting
And out of the drone light on battery stay on .
Sorry, I have no idea about your battery problem. Maybe you should contact DJI with the first video.

First video is strange for sure.
In the second video, I don't see what it wrong.
  1. Short press it blink
  2. Long press it blink
  3. Double click it blink one time
 
All led light on for minutes without blink ? Update :both batteries have in flight message , fan problem when connected with both . Online supp told me send for repair but i have to pay for shipping to Germany from Romania , i think is cca. 50-70 usd .And only when arrive they can tell me if repair is under warranty . I will send email to open a case , with all dats , logs and videos
 
Last edited:

Members online

No members online now.

Forum statistics

Threads
14,601
Messages
118,823
Members
18,012
Latest member
Dayanadiast