MP2 Unexpected "crash"

[Miki121]

yeah i guess... . just glad nothing bad happened! thanks guys anyway for your help!

 

[JDawg]

" There could have been some weird interactions there. "

I thnk Kilrah is onto the problem since you had a max flight distance set.

 

[sar104]

This looks a bit like a bug in the time-lapse function. There is no indication in the log of any reason for the descent, which began 7 seconds after it entered time-lapse mode:



Can you get the DAT file off your mobile device? The event log may shed some light on what happened.

Mobile device DAT file: How to retrieve a V3.DAT from the tablet

 

[Miki121]

Hey, it must be one of these two but i can't open either of them..but somehow when i import them with DatCon it tells me that these are not vaild DAT files ... is that normal ?
i had to put them on my DropBox because they were too big.

Thank you !

 

[DanMan32]

You got those from your mobile device and not the AC, correct?

 

[BudWalker]

Hey, it must be one of these two but i can't open either of them..but somehow when i import them with DatCon it tells me that these are not vaild DAT files ... is that normal ?
i had to put them on my DropBox because they were too big.

Thank you !

You'll need to tell DatCon that an invalid header is OK. It's probably a good idea to also allow excessive errors.

 

[Miki121]

You got those from your mobile device and not the AC, correct?

correct

 

[Miki121]

You'll need to tell DatCon that an invalid header is OK. It's probably a good idea to also allow excessive errors.
View attachment 58276

ok that works. but it's not the "19-01-02-04-16-15_FLY017" and the other one "19-01-02-05-03-34_FLY020" has nothing altough it is as large as the other one (file size)

i tried to connect the AC throuh the computer, i see the files and managed to download them:



i export the file but i always get the same message when i try to load them.
also,

the app does not look like the one they claim on their wepage with the integrated data viewer and so on (see screenshot from their pdf below)

 

[SpinItUp]

The (M2) AC DAT is not readable eh!
peeps?
[Edit] only DJI have the encrypted keys to read it

 

[sar104]

correct

ok that works. but it's not the "19-01-02-04-16-15_FLY017" and the other one "19-01-02-05-03-34_FLY020" has nothing altough it is as large as the other one (file size)

i tried to connect the AC throuh the computer, i see the files and managed to download them:
View attachment 58315


i export the file but i always get the same message when i try to load them.
also,
View attachment 58314
the app does not look like the one they claim on their wepage with the integrated data viewer and so on (see screenshot from their pdf below)
View attachment 58316

The aircraft logs are no use - as mentioned above, on the Mavic 2 they are encrypted and not readable.

 

[DanMan32]

That's why I asked if the DAT files were from the app or from the AC. Apparently they were from the AC.
The DAT files being asked for are on the mobile device that was connected to the RC. It has more info than the txt file.

I guess the retrieval of the AC DAT files via Assistant was interpreted as "from the app".

 

[BudWalker]

ok that works. but it's not the "19-01-02-04-16-15_FLY017" and the other one "19-01-02-05-03-34_FLY020" has nothing altough it is as large as the other one (file size)

i tried to connect the AC throuh the computer, i see the files and managed to download them:
View attachment 58315


i export the file but i always get the same message when i try to load them.
also,
View attachment 58314
the app does not look like the one they claim on their wepage with the integrated data viewer and so on (see screenshot from their pdf below)
View attachment 58316

Sorry, I'm not sure what the problem is. Your Dropbox contained the files 19-01-02-04-16-15_FLY017.DAT and 19-01-02-05-03-34_FLY020.DAT which are both valid .DAT files (once you've told DatCon to accept an invalid DatHeader)

 

[Miki121]

First of all - thanks guys for trying to help me, I appreciate

second, sorry i never had to go through that so i'm learning the hard way :S

exactly, these are the files i copied from here in my phone, .. but i only manage to see the map of one and the other has no "map" so to say to see if this is the one where the crash happened.

this below is a screenshot of my phone

 

[Miki121]

The aircraft logs are no use - as mentioned above, on the Mavic 2 they are encrypted and not readable.

Ok i think i managed,
it is this one (too large to put as attachement), i see the map and the point of crash
Dropbox - DatFile - Simplify your life

 

[Miki121]

The aircraft logs are no use - as mentioned above, on the Mavic 2 they are encrypted and not readable.

was this the right dat file ? in my last post?

 

[sar104]

was this the right dat file ? in my last post?

Yes - that was the correct DAT file. Unfortunately I didn't learn much from it, possibly because I'm not familiar enough with the mode functionality. It goes to timelapse and then descends (starting at 742 s on this time scale) with the following entries:

737.057 : 70946 [L-MIS][SDK] new open GS(cam)​

737.057 : 70946 [L-MIS]received on/off 1 from dev 2​

737.057 : 70946 [L-MIS]ack on/off 0 to can​

737.059 : 70947 [L-SDK]app API sub_mode 8 2​

737.059 : 70947 [L-MIS][NAVI MISSION] req sub_mode: TimeLapsePhoto on​

737.059 : 70947 [L-SDK][USER]send ack 0x00​

737.114 : 70950 [L-N_MIS]Exit mis 3. New mis 14​

737.114 : 70950 [L-N_MIS]Switch new mis 14 req 4 from mis 3 req 2​

743.999 : 71353 [L-VISION][VIO]receive vio data befor current ts||​

751.937 : 71818 [L-VISION][VIO]receive vio data befor current ts||​

752.845 : 71872 [L-FMU/MOTOR]safe_near_grd:true​

752.963 : 71878 [L-VISION][VIO]receive vio data befor current ts||​

753.507 : 71910 [L-SDK]app API sub_mode 8 0​

753.507 : 71910 [L-MIS][NAVI MISSION] req sub_mode: TimeLapsePhoto off​

753.507 : 71910 [L-SDK][USER]send ack 0x00​

753.511 : 71911 [L-MIS][SDK] new open GS(cam)​

753.511 : 71911 [L-MIS]received on/off 2 from dev 2​

753.511 : 71911 [L-N_MIS]req abort all for USER.mission.request.off​

753.511 : 71911 [L-MIS]ack on/off 0 to can​

753.511 : 71911 [L-N_MIS]Switch new mis 3 req 2 from mis 25 req 16​

753.511 : 71911 [L-FLYMODE]SWITCH2HOVER!​

754.066 : 71943 [L-VISION][VIO]receive vio data befor current ts||​

754.466 : 71967 [L-FMU/MOTOR]fault on , esc(1) is stall​

754.466 : 71967 [L-FMU/MOTOR] Stop. reason:motor stall near ground​

754.467 : 71967 [L-FMU/MOTOR]Total start times: 1, time: 884.14​

754.467 : 71967 [L-PWM]set actuator mode:IDLE​

754.467 : 71967 [L-N_MIS]req abort all for motor stopped​

754.467 : 71967 [L-RC]craft ctrl failed!!!​

754.469 : 71967 [L-FMU/FSM]state changed. cur: motor off​

754.471 : 71967 [L-NS][AHRS] reset baro just after land​

754.483 : 71968 [L-FMU/MOTOR]fault off, esc(1) is stall​

754.484 : 71968 [L-BATTERY]old:SAFE_FLY=>>>>new:ON_GROUND​

 

[Miki121]

Yes - that was the correct DAT file. Unfortunately I didn't learn much from it, possibly because I'm not familiar enough with the mode functionality. It goes to timelapse and then descends (starting at 742 s on this time scale) with the following entries:

737.057 : 70946 [L-MIS][SDK] new open GS(cam)​

737.057 : 70946 [L-MIS]received on/off 1 from dev 2​

737.057 : 70946 [L-MIS]ack on/off 0 to can​

737.059 : 70947 [L-SDK]app API sub_mode 8 2​

737.059 : 70947 [L-MIS][NAVI MISSION] req sub_mode: TimeLapsePhoto on​

737.059 : 70947 [L-SDK][USER]send ack 0x00​

737.114 : 70950 [L-N_MIS]Exit mis 3. New mis 14​

737.114 : 70950 [L-N_MIS]Switch new mis 14 req 4 from mis 3 req 2​

743.999 : 71353 [L-VISION][VIO]receive vio data befor current ts||​

751.937 : 71818 [L-VISION][VIO]receive vio data befor current ts||​

752.845 : 71872 [L-FMU/MOTOR]safe_near_grd:true​

752.963 : 71878 [L-VISION][VIO]receive vio data befor current ts||​

753.507 : 71910 [L-SDK]app API sub_mode 8 0​

753.507 : 71910 [L-MIS][NAVI MISSION] req sub_mode: TimeLapsePhoto off​

753.507 : 71910 [L-SDK][USER]send ack 0x00​

753.511 : 71911 [L-MIS][SDK] new open GS(cam)​

753.511 : 71911 [L-MIS]received on/off 2 from dev 2​

753.511 : 71911 [L-N_MIS]req abort all for USER.mission.request.off​

753.511 : 71911 [L-MIS]ack on/off 0 to can​

753.511 : 71911 [L-N_MIS]Switch new mis 3 req 2 from mis 25 req 16​

753.511 : 71911 [L-FLYMODE]SWITCH2HOVER!​

754.066 : 71943 [L-VISION][VIO]receive vio data befor current ts||​

754.466 : 71967 [L-FMU/MOTOR]fault on , esc(1) is stall​

754.466 : 71967 [L-FMU/MOTOR] Stop. reason:motor stall near ground​

754.467 : 71967 [L-FMU/MOTOR]Total start times: 1, time: 884.14​

754.467 : 71967 [L-PWM]set actuator mode:IDLE​

754.467 : 71967 [L-N_MIS]req abort all for motor stopped​

754.467 : 71967 [L-RC]craft ctrl failed!!!​

754.469 : 71967 [L-FMU/FSM]state changed. cur: motor off​

754.471 : 71967 [L-NS][AHRS] reset baro just after land​

754.483 : 71968 [L-FMU/MOTOR]fault off, esc(1) is stall​

754.484 : 71968 [L-BATTERY]old:SAFE_FLY=>>>>new:ON_GROUND​

Hmmm ok yeah i see...thank you either way for looking at it... what sucks is that i bought my drone in the USA and moved back to switzerland in the mean time ..so now from what dji tells me... my warranty is only valid in the usa... which sucks for a 2000$ professional product...

 

[Ahrimaan]

my warranty is only valid in the usa... which sucks for a 2000$ professional product...

But its normal, every company do it so

 

[ff22]

Hmmm ok yeah i see...thank you either way for looking at it... what sucks is that i bought my drone in the USA and moved back to switzerland in the mean time ..so now from what dji tells me... my warranty is only valid in the usa... which sucks for a 2000$ professional product...

I still find that an offensive posture to take. These days many folks travel for business or pleasure as well as move internationally. They buy products sold internationally and should be able to use a warranty elsewhere if they are now somewhere else. I was at the Amsterdam SuperStore - their darn airport!! I wanted to purchase Bose headphones for the nine hour flight back home. But passed on the purchase since I was not sure that I could use the warranty back in the US. That is a stupid limitation. They sell these headphones/drones/whatever everywhere and there should not be a limitation on where you can get them repaired.

Okay, my rant is over.

 

[Miki121]

I still find that an offensive posture to take. These days many folks travel for business or pleasure as well as move internationally. They buy products sold internationally and should be able to use a warranty elsewhere if they are now somewhere else. I was at the Amsterdam SuperStore - their darn airport!! I wanted to purchase Bose headphones for the nine hour flight back home. But passed on the purchase since I was not sure that I could use the warranty back in the US. That is a stupid limitation. They sell these headphones/drones/whatever everywhere and there should not be a limitation on where you can get them repaired.

Okay, my rant is over.

Exactly my thought...