-
Traceback (most recent call last):
File "/usr/local/bin/mavproxy.py", line 491, in process_stdin
fn(args[1:])
File "/usr/local/bin/mavproxy.py", line 319, in cmd_module
load_module(arg…
-
Almost all MAV_CMDs are processed in guided mode when sent inside a COMMAND_LONG (see MAVLINK_MSG_ID_COMMAND_LONG in [GCS_Mavlink.cpp](https://github.com/diydrones/ardupilot/blob/master/ArduCopter/GCS…
-
Right now we have the following hard-coded camera names (which are set in `instument/camera.py`) and are also written to `ctapipe_resources`:
- ASTRI (ASTRICam?)
- FlashCam
- NectarCam
- LSTCam
…
-
@dogmaphobic @LorenzMeier
For users to test PX4 camera triggering, we need to send a `DO_DIGICAM_CONTROL` command, with Param 5 > 0. It would go on to the existing "Camera" page in QGC as a **butt…
-
@DonLakeFlyer This command is sent with system ID 1 (correct) and component ID 255 (why?)
```
sendMavCommand(FactSystem::defaultComponentId, MAV_CMD_DO_DIGICAM_CONTROL, true, // show errors 0.0, 0…
-
It seems PX4 is occasionally missing camera triggers in distance base triggering. We've seen this happen both in real flight testing and also in HIL simulation. FMUv4 based hardware, MAVlink compat…
-
If we think of a multirotor survey, since survey poses as only one mission item, how can user land, then resume from correct place in mission ?
Usually we would (for example) fly WP 1...50 , poshol…
AndKe updated
7 years ago
-
We should revisit and understand the user model for surveying - how users want to configure the survey and what API we should expose.
I'm less interested in what is there on the tech side, but rather…
-
#### Issue details
compiling with
#define CAMERA DISABLED
cause error
commands_logic.cpp:1104:73: error: no 'void Copter::do_digicam_configure(const AP_Mission::Mission_Comman…
-
Discussion starts in #4868. Rest of discussion should be here.