The behavior is clearly visible in log file 00036, especially in the second part (start #2). But there is no indication that points to the source of the problem.
Sensor_00041.txt belongs to that flight. Here are the messages for the second part of #00036:
84110 00:24:46 INFO: 'Armed by arm/disarm component command.'
84111 00:24:46 INFO: '(3,14)home: 33.1507581, -97.2688140, 212.38'
84112 00:24:46 INFO: '(3,14)home: 33.1507581, -97.2688140, 212.38'
84113 00:24:46 INFO: '[logger] file: /fs/microsd/log/2021-04-10/23_59_1'
84116 00:24:46 MIS_TAKEOFF_ALT : Type: 9, Index: 353, Count: 813, Value: 3
84127 00:24:46 INFO: '(3,11)TAKEOFF MODE'
84130 00:24:46 CRITICAL: 'Using minimum takeoff altitude: 3.00 m'
84133 00:24:46 INFO: '(2,87) not angle mode obs not available'
84134 00:24:46 INFO: 'Takeoff detected.'
84222 00:24:47 INFO: '(3,26)ANGLE MODE'
84278 00:24:48 MPC_REALSENSE : Type: 6, Index: 393, Count: 813, Value: $01=0000 0001
113739 00:33:17 INFO: '(2,86) altitude Less than 1.5m, obs not available'
114156 00:33:24 INFO: '(3,82) obs close'
114822 00:33:35 INFO: 'Landing detected.'
114829 00:33:35 INFO: 'Disarmed by auto disarm on land.'
There is only one message regarding RealSense. I don't know what this message really means. But in other flights there were error messages from RealSense module:
Sensor00037 - 28925 00:09:14 INFO: 'realsense moudle fault'.
Possible root causes:
- defect RealSense Module or disturbed RealSense sensors (most probable, my guess).
- defect OBS.
- disturbed camera connections (I don't think, but who knows...).
What can we do?
Test the following:
- fly with switched off OBS and check if the problem persists
- fly without camera (I'm not sure if this is possible for H Plus) and check again
- clean RealSense sensors and test the behavior again.
br HE