HedgeTrimmer
Captain
United States
Offline
|
fans8a004bf7 Posted at 2018-9-2 17:16
Well that's strange - the DAT log appears to stop 15 s before the txt log. The first IMU switch is visible:
87.415 : 25495 [L-FDI]ULTRASONIC(0): fault off, disconnect
87.415 : 25495 [L-NS][AHRS] connect us :1
87.432 : 25496 [L-FDI]NS(0) TOF(0): fault off, disconnect
87.705 : 25512 [L-FMU/MOTOR]No need to disable motor!
87.741 : 25514 [L-VISION][VIO]receive vio data befor current ts||
87.744 : 25514 [L-NS][AHRS] Bad sample tick measure or recapture signal: 9.880000
87.744 : 25514 [L-NS][AHRS] connect vo :1
87.756 : 25515 [L-FDI]NS(0) VO(0): fault off, disconnect
90.291 : 25663 [L-NS][comm] ext ns connect2
90.299 : 25664 [L-FDI]NS(0) FUSION(1): fault off, disconnect
90.931 : 25701 [L-FMU/LED]action changed. Normal Flash:not converged(2)
90.931 : 25701 [L-FMU/LED]type:0, normal flash action:
90.931 : 25701 [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
94.549 : 25913 [L-FDI]ns req:fdi,0to1,reason:normal,result:succeed
94.549 : 25913 [L-FDI][SWITCH] req:2,0->1,result:6,serr:7,derr:15
94.549 : 25913 [L-IMU][heading] state: drift
94.549 : 25913 [L-FMU/DM]Busy Device Changed. Type:imu1_ext_ns, ID:15 idx:1>, change ti
95.181 : 25950 [L-FDI]ns switch app warning!
95.419 : 25964 [L-IMU][heading] state: fixed
At this time the IMUs disagree, as is evident in the pitch data: 2018-09-01_18-46-57_FLY025_01.png
Obviously this happens again in the final 15 s of the flight, but the DAT file stops before that.
After that there are multiple entries of the forms:
128.819 : 27921 [L-COMPASS][mag auto cali(0)] init|
131.707 : 28090 [L-VISION][VIO]receive vio data befor current ts||
196.539 : 31889 [L-GEO][fmu_api_handler_update_app_db]wrong index! 55|
I find all three of those in the DAT log for my M2P, although fewer of them. However, it looks to me as if something is causing the FC to fail - whether that is overheating or a firmware bug of some kind is hard to say.
Both IMUs report the same temperature (65°C), which is appears to be a set point - the IMUs on mine run at exactly the same temperature. The CPU temperature is not recorded as far as I know. Do you know if the fan works(ed)?
This looks like a clear case to request a replacement. #37
You must have dug that information out of .DAT log file. Did not see it in output from FlightLog .txt file?
Never mind, I missed where you stated it. Had to seperate things out.
___________________________________________________________________________
Well that's strange - the DAT log appears to stop 15 s before the txt log. The first IMU switch is visible:
87.415 : 25495 [L-FDI]ULTRASONIC(0): fault off, disconnect
87.415 : 25495 [L-NS][AHRS] connect us :1
87.432 : 25496 [L-FDI]NS(0) TOF(0): fault off, disconnect
87.705 : 25512 [L-FMU/MOTOR]No need to disable motor!
87.741 : 25514 [L-VISION][VIO]receive vio data befor current ts||
87.744 : 25514 [L-NS][AHRS] Bad sample tick measure or recapture signal: 9.880000
87.744 : 25514 [L-NS][AHRS] connect vo :1
87.756 : 25515 [L-FDI]NS(0) VO(0): fault off, disconnect
90.291 : 25663 [L-NS][comm] ext ns connect2
90.299 : 25664 [L-FDI]NS(0) FUSION(1): fault off, disconnect
90.931 : 25701 [L-FMU/LED]action changed. Normal Flash:not converged(2)
90.931 : 25701 [L-FMU/LED]type:0, normal flash action:
90.931 : 25701 [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
94.549 : 25913 [L-FDI]ns req:fdi,0to1,reason:normal,result:succeed
94.549 : 25913 [L-FDI][SWITCH] req:2,0->1,result:6,serr:7,derr:15
94.549 : 25913 [L-IMU][heading] state: drift
94.549 : 25913 [L-FMU/DM]Busy Device Changed. Type:imu1_ext_ns, ID:15 idx:1>, change ti
95.181 : 25950 [L-FDI]ns switch app warning!
95.419 : 25964 [L-IMU][heading] state: fixed
At this time the IMUs disagree, as is evident in the pitch data: 2018-09-01_18-46-57_FLY025_01.png
Obviously this happens again in the final 15 s of the flight, but the DAT file stops before that.
After that there are multiple entries of the forms:
128.819 : 27921 [L-COMPASS][mag auto cali(0)] init|
131.707 : 28090 [L-VISION][VIO]receive vio data befor current ts||
196.539 : 31889 [L-GEO][fmu_api_handler_update_app_db]wrong index! 55|
I find all three of those in the DAT log for my M2P, although fewer of them. However, it looks to me as if something is causing the FC to fail - whether that is overheating or a firmware bug of some kind is hard to say.
Both IMUs report the same temperature (65°C), which is appears to be a set point - the IMUs on mine run at exactly the same temperature. The CPU temperature is not recorded as far as I know. Do you know if the fan works(ed)?
This looks like a clear case to request a replacement. #37
|
|