Compass Redundancy Switched--But Not in Flight Logs

Joined
Apr 6, 2016
Messages
199
Reaction score
51
Age
67
Location
Fountain Hills, AZ
Hello All,

While returning on returning to home I received a Compass Redundancy Switched message in App. I returned to home safely following the message.

Later that evening I replayed the flight and went through my warning messages. The Compass Redundancy Switched message does not show up in a replay of the flight nor does it show up in list of warnings.

Where else might I look for this message?

Donald Barar
 
The .DAT log files stored on board the aircraft are much more detailed. They can be downloaded using the DJI Assistant 2 PC application and viewed on the DatCon site.

CsvView/DatCon
 
Hi S,

I will give that a try.

Don
Those messages will be in the .DAT but you'll have to look in the eventLog stream. To do this use DatCon and specify that you want to create the Event Log File.
upload_2017-2-20_7-7-37.png

When you look at the created log.txt file you should see something like
334.941 : 2131387479 : 23441 [L-FDI]NS(0) COMPASS(0): fault on , noise
334.941 : 2131388499 : 23441 [L-FMU/DM]Busy Device Changed. Type:compass1, <ID:3 idx:0-->ID:4 idx:1>, change times:
indicating that compass0 (the back compass) became noisy and a switch was made to the front compass (compass1)
 
  • Like
Reactions: smiller
Those messages will be in the .DAT but you'll have to look in the eventLog stream. To do this use DatCon and specify that you want to create the Event Log File.
View attachment 76696
When you look at the created log.txt file you should see something like
334.941 : 2131387479 : 23441 [L-FDI]NS(0) COMPASS(0): fault on , noise
334.941 : 2131388499 : 23441 [L-FMU/DM]Busy Device Changed. Type:compass1, <ID:3 idx:0-->ID:4 idx:1>, change times:
indicating that compass0 (the back compass) became noisy and a switch was made to the front compass (compass1)
Hi S,

I just got all of the .dat files off the aircraft and have have downloaded csvview and dat con. This additional information should help once I begin to examine the .dat files.

Don
 
Those messages will be in the .DAT but you'll have to look in the eventLog stream. To do this use DatCon and specify that you want to create the Event Log File.
View attachment 76696
When you look at the created log.txt file you should see something like
334.941 : 2131387479 : 23441 [L-FDI]NS(0) COMPASS(0): fault on , noise
334.941 : 2131388499 : 23441 [L-FMU/DM]Busy Device Changed. Type:compass1, <ID:3 idx:0-->ID:4 idx:1>, change times:
indicating that compass0 (the back compass) became noisy and a switch was made to the front compass (compass1)[/QUOTE

Hi Bud,

Not certain I am able to locate the correct .dat file. There are dates and times on the .dat files but they are not local time. What time do they represent?

Donald Barar
 
Hi Bud and S,

I have reviewed all .DAT files, line by line, the day before, the day of, and the day after. No where can I find Compass error message of any kind. Nor, am I able to locate an approximate latitude/longitude of a launch point near where the incident occurred.

I am baffled. What should I try next? I know I saw the message "Compass Redundancy Switch" come on the application and this was the first time I had seen this message or even heard of it.

Donald Barar
 
Hi Bud and S,

Performed a flight today. While I did not get the "Compass Redundancy Switch" I did see the following in the .dat logs but not certain how to interpret:

5.481 : 24665183 : 0 [L-SENSOR]imu group1 error, gyro_acc_freq=-1.
5.481 : 24665363 : 0 [L-SENSOR]imu group2 ok, gyro_acc_freq=2000.
6.900 : 31049760 : 69 [L-FDI][FDI][COMPASS(0)] is outlier(fault)
6.900 : 31050126 : 69 [L-FDI][FDI][COMPASS(1)] is outlier(fault)
6.960 : 31318814 : 72 [L-FDI][FDI][COMPASS(0)] is outlier(fault)
6.960 : 31319192 : 72 [L-FDI][FDI][COMPASS(1)] is outlier(fault)

The other thing that I have noticed are unusual date stamps on the .dat files. Follows are the last 3:

- FLY136 Created 10/19/15 3:45 PM Modified 10/2017 5:15 PM
- FLY135 Created 10/20/17 7:19 AM Modified 10/19/15 3:59 PM
- FLY134 Created 10/20/17 7:00 AM Modified 10/20/17 7:20 AM

The first two files appeared after my flights this afternoon. These are not typos. The dates are actually 2015 where I wrote 15. And so it is with the rest of the sequence of .dat files not lining up with the dates they were created or modified.

Can either of you comment?

Donald Barar
 

Members online

No members online now.

Forum statistics

Threads
143,066
Messages
1,467,358
Members
104,936
Latest member
hirehackers