Oh man. , thank you so much that was the issue
Latest posts made by Pey Astig
-
RE: MAVSDK offboard set_velocity_body strange behavior
-
MAVSDK offboard set_velocity_body strange behavior
(Firmware 1.10, indoor parameters used)
These set of MAVSDK code causes the drone to fly up approximately 5 feet and spin
await drone.action.arm() await drone.offboard.set_velocity_body(VelocityBodyYawspeed(0, 0, 0, 0)) try: await drone.offboard.start() except OffboardError as error: print(f"Starting offboard mode failed with error code: \ {error._result.result}") print("-- Disarming") await drone.action.disarm() return
My initial expectation is it would just stay in the ground. I'm just wondering what could be causing the issue, or how i can try to debug this. I'm getting odometry data in QGroundControl.
Thank you
-
take off in position flight mode causes the drone to fly a bit tilted forward instead of up
(Firmware 1.10)I have the indoor PX4 parameters uploaded to the drone in QGroundControl.
One possible source could be that the sensor calibration I did wasn't
perfect. But I believe that since I'm using indoor PX4 parameters, position flight mode depends only on the Tracking Camera (external vision) and not the sensors ? -
RE: Is HITL (hardware in the loop) supported in VOXL-m500?
Thank you, this helped a lot.
-
How does voxl-vision-configuration parameters relate to PX4 parameters?
For example, does having VIO to True, simply set PX4 parameters to use External Vision for EKF2? Do I have to change VIO and VOA to false if I'm doing an outdoor flight test?
-
Is HITL (hardware in the loop) supported in VOXL-m500?
The reason for the question is it would be helpful to test software command API's on the VOXL-m500 such as MAVSDK more intensively without risking accidents