Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

kp ngK

kp ng

@kp ng
Contributor
Unfollow Follow
About
Posts
15
Topics
2
Shares
0
Groups
1
Followers
0
Following
0

Posts

Recent Best Controversial

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    @Eric-Katzfey
    Hi Eric.
    Yes the same error messages occur each time.
    Have tried pressing on the connector as well. Doesn't help.
    Have spaced the power supply, wifi, gps antenna apart also.

    Below are the logs

    voxl2:/$ voxl-px4
    Found DSP signature file
    INFO [px4] mlockall() enabled. PX4's virtual address space is locked into RAM.
    INFO [px4] assuming working directory is rootfs, no symlinks needed.


    | ___ \ \ \ / / / |
    | |/ / \ V / / /| |
    | __/ / \ / /
    | |
    | | / /^\ \ ___ |
    _| / / |_/

    px4 starting.

    INFO [px4] Calling startup script: /bin/sh /etc/modalai/voxl-px4.config 0
    Running on M0054
    INFO [muorb] SLPI: Creating qurt thread hpwork

    INFO [muorb] SLPI: Successfully created px4 task PX4_hpwork with tid 82
    INFO [muorb] SLPI: Creating qurt thread lpwork

    INFO [muorb] SLPI: Successfully created px4 task PX4_lpwork with tid 81
    INFO [muorb] SLPI: Creating qurt thread wkr_hrt

    INFO [muorb] SLPI: Successfully created px4 task PX4_wkr_hrt with tid 80
    INFO [muorb] SLPI: Creating qurt thread client_sync_thread

    INFO [muorb] SLPI: Successfully created px4 task PX4_client_sync_thread with tid 79
    INFO [muorb] SLPI: Creating qurt thread wq_manager

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_manager with tid 78
    INFO [muorb] SLPI: Creating qurt thread qshell

    INFO [muorb] SLPI: Successfully created px4 task PX4_qshell with tid 77
    INFO [qshell] Send cmd: 'icm42688p start -s'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: icm42688p start -s
    INFO [muorb] SLPI: Creating qurt thread wq_SPI1

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_SPI1 with tid 76
    INFO [muorb] SLPI: *** SPI Device ID 0x26000a 2490378
    INFO [uorb] Advertising remote topic sensor_accel
    INFO [uorb] Marking DeviceNode(parameter_server_set_used_request) as advertised in process_remote_topic
    INFO [muorb] SLPI: Marking DeviceNode(parameter_server_set_used_response) as advertised in process_remote_to
    INFO [uorb] Advertising remote topic sensor_gyro
    INFO [uorb] Advertising remote topic imu_server
    INFO [muorb] SLPI: on SPI bus 1
    INFO [muorb] SLPI: icm42688p #0 on SPI bus 1 (devid=0x0)
    INFO [muorb] SLPI:

    INFO [muorb] SLPI: Ok executing command: icm42688p start -s
    INFO [muorb] SLPI: Sending qshell retval with timestamp 41957598, current timestamp 41957599
    INFO [uorb] Advertising remote topic qshell_retval
    INFO [qshell] qshell return value timestamp: 41957598, local time: 41959528
    INFO [muorb] SLPI: Marking DeviceNode(parameter_client_reset_request) as advertised in process_remote_topic
    ERROR [muorb] SLPI: Cannot reset all parameters on client side
    INFO [uorb] Marking DeviceNode(parameter_client_reset_response) as advertised in process_remote_topic
    INFO [muorb] SLPI: Advertising remote topic parameter_update
    INFO [muorb] SLPI: Marking DeviceNode(parameter_client_set_value_request) as advertised in process_remote_to
    INFO [uorb] Marking DeviceNode(parameter_client_set_value_response) as advertised in process_remote_topic
    INFO [logger] logger started (mode=all)
    Starting Holybro magnetometer
    INFO [qshell] Send cmd: 'ist8310 start -R 10 -X -b 1'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: ist8310 start -R 10 -X -b 1
    INFO [muorb] SLPI: Creating qurt thread wq_I2C1

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_I2C1 with tid 75
    INFO [muorb] SLPI: *** I2C Device ID 0x60e09 396809
    INFO [muorb] SLPI: ist8310 #0 on I2C bus 1 (external)

    INFO [muorb] SLPI: Ok executing command: ist8310 start -R 10 -X -b 1
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44022129, current timestamp 44022130
    INFO [qshell] qshell return value timestamp: 44022129, local time: 44028451
    Starting Holybro LED driver
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [qshell] Send cmd: 'rgbled_ncp5623c start -X -b 1 -f 400 -a 56'
    INFO [muorb] SLPI: qshell gotten: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
    INFO [muorb] SLPI: *** I2C Device ID 0x7b3809 8075273
    INFO [muorb] SLPI: rgbled_ncp5623c #0 on I2C bus 1 (external)

    INFO [muorb] SLPI: Ok executing command: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44071605, current timestamp 44071606
    INFO [qshell] qshell return value timestamp: 44071605, local time: 44073373
    INFO [qshell] Send cmd: 'icp10100 start -I -b 5'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: icp10100 start -I -b 5
    INFO [muorb] SLPI: Creating qurt thread wq_I2C5

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_I2C5 with tid 74
    INFO [muorb] SLPI: *** I2C Device ID 0x9c6329 10249001
    INFO [muorb] SLPI: probe probe succeeded. data = 0x1 0x48
    INFO [muorb] SLPI: icp10100 #0 on I2C bus 5

    INFO [muorb] SLPI: Ok executing command: icp10100 start -I -b 5
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44119538, current timestamp 44119540
    INFO [qshell] qshell return value timestamp: 44119538, local time: 44120763
    INFO [uorb] Advertising remote topic sensor_mag
    INFO [qshell] Send cmd: 'modalai_esc start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: modalai_esc start
    INFO [muorb] SLPI: Creating qurt thread wq_hp_default

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_hp_default with tid 73
    INFO [uorb] Advertising remote topic test_motor
    INFO [uorb] Advertising remote topic sensor_baro
    INFO [muorb] SLPI: Ok executing command: modalai_esc start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44170549, current timestamp 44170550
    INFO [muorb] SLPI: Opened UART ESC device
    INFO [qshell] qshell return value timestamp: 44170549, local time: 44172188
    INFO [qshell] Send cmd: 'mixer load /dev/uart_esc quad_x.main.mix'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: mixer load /dev/uart_esc quad_x.main.mix
    INFO [muorb] SLPI: Creating qurt thread wq_rate_ctrl

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_rate_ctrl with tid 71
    INFO [muorb] SLPI: Ok executing command: mixer load /dev/uart_esc quad_x.main.mix
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44239985, current timestamp 44239986
    INFO [qshell] qshell return value timestamp: 44239985, local time: 44241616
    INFO [uorb] Advertising remote topic actuator_outputs
    INFO [uorb] Advertising remote topic multirotor_motor_limits
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [qshell] Send cmd: 'voxlpm start -X -b 2'
    INFO [muorb] SLPI: qshell gotten: voxlpm start -X -b 2
    INFO [muorb] SLPI: Creating qurt thread wq_I2C2

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_I2C2 with tid 4169
    INFO [muorb] SLPI: *** I2C Device ID 0x784411 7881745
    INFO [uorb] Advertising remote topic battery_status
    INFO [muorb] SLPI: voxlpm #0 on I2C bus 2 (external)

    INFO [muorb] SLPI: Ok executing command: voxlpm start -X -b 2
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44301919, current timestamp 44301920
    INFO [qshell] qshell return value timestamp: 44301919, local time: 44302736
    INFO [uorb] Advertising remote topic power_monitor
    Starting Holybro GPS
    INFO [qshell] Send cmd: 'gps start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: gps start
    INFO [muorb] SLPI: Creating qurt thread gps

    INFO [muorb] SLPI: Successfully created px4 task PX4_gps with tid 70
    INFO [muorb] SLPI: Ok executing command: gps start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44356373, current timestamp 44356374
    INFO [qshell] qshell return value timestamp: 44356373, local time: 44357420
    INFO [uorb] Advertising remote topic gps_dump
    INFO [qshell] Send cmd: 'px4io detect'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: px4io detect
    INFO [muorb] SLPI: serial port fd 2
    ERROR [muorb] SLPI: px4io read failed
    ERROR [muorb] SLPI: px4io io_reg_get(0,0,1): data error -5
    ERROR [muorb] SLPI: IO not installed
    ERROR [muorb] SLPI: Detection attempt 2 failed
    ERROR [muorb] SLPI: Detection attempt 1 failed
    ERROR [muorb] SLPI: Detection attempt 0 failed
    ERROR [muorb] SLPI: Failed to execute command: px4io detect
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44408878, current timestamp 44408879
    INFO [qshell] cmd returned with: -17
    INFO [qshell] qshell return value timestamp: 44408878, local time: 44416905
    ERROR [qshell] Command failed
    M0065 not detected, starting Spektrum RC driver
    INFO [qshell] Send cmd: 'spektrum_rc start -d 8'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: spektrum_rc start -d 8
    INFO [muorb] SLPI: Creating qurt thread spektrum_rc_main

    INFO [muorb] SLPI: Successfully created px4 task PX4_spektrum_rc_main with tid 67
    INFO [muorb] SLPI: Ok executing command: spektrum_rc start -d 8
    INFO [muorb] SLPI: Sending qshell retval with timestamp 44459706, current timestamp 44459708
    INFO [qshell] qshell return value timestamp: 44459706, local time: 44463848
    INFO [qshell] Send cmd: 'sensors start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: sensors start
    INFO [muorb] SLPI: Creating qurt thread wq_nav_and_controllers

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_nav_and_controllers with tid 66
    INFO [muorb] SLPI: Ok executing command: sensors start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 45536132, current timestamp 45536133
    INFO [uorb] Advertising remote topic vehicle_angular_acceleration
    INFO [qshell] qshell return value timestamp: 45536132, local time: 45537985
    INFO [uorb] Advertising remote topic vehicle_angular_velocity
    INFO [muorb] SLPI: Creating qurt thread wq_INS0

    INFO [muorb] SLPI: Successfully created px4 task PX4_wq_INS0 with tid 65
    INFO [uorb] Advertising remote topic vehicle_imu
    INFO [uorb] Advertising remote topic vehicle_imu_status
    INFO [uorb] Advertising remote topic sensors_status_imu
    INFO [uorb] Advertising remote topic vehicle_acceleration
    INFO [uorb] Advertising remote topic vehicle_air_data
    INFO [qshell] Send cmd: 'ekf2 start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: ekf2 start
    INFO [uorb] Advertising remote topic vehicle_magnetometer
    INFO [uorb] Advertising remote topic sensor_preflight_mag
    INFO [uorb] Advertising remote topic sensor_selection
    INFO [uorb] Advertising remote topic sensor_combined
    ERROR [muorb] SLPI: Timeout waiting for parameter_server_set_used_response for EKF2_ASP_DELAY
    INFO [muorb] SLPI: Ok executing command: ekf2 start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 45782283, current timestamp 45782283
    INFO [qshell] qshell return value timestamp: 45782283, local time: 45784731
    ERROR [muorb] SLPI: 0 - vehicle_magnetometer lost, generation 0 -> 8
    INFO [uorb] Advertising remote topic ekf2_timestamps
    INFO [qshell] Send cmd: 'mc_pos_control start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: mc_pos_control start
    INFO [muorb] SLPI: Ok executing command: mc_pos_control start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 45833887, current timestamp 45833888
    INFO [qshell] qshell return value timestamp: 45833887, local time: 45834370
    INFO [qshell] Send cmd: 'mc_att_control start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: mc_att_control start
    INFO [muorb] SLPI: Ok executing command: mc_att_control start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 45897359, current timestamp 45897360
    INFO [qshell] qshell return value timestamp: 45897359, local time: 45898791
    INFO [qshell] Send cmd: 'mc_rate_control start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: mc_rate_control start
    INFO [muorb] SLPI: Ok executing command: mc_rate_control start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 45969574, current timestamp 45969574
    INFO [qshell] qshell return value timestamp: 45969574, local time: 45971046
    INFO [qshell] Send cmd: 'mc_hover_thrust_estimator start'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: mc_hover_thrust_estimator start
    INFO [muorb] SLPI: Ok executing command: mc_hover_thrust_estimator start
    INFO [muorb] SLPI: Sending qshell retval with timestamp 46028199, current timestamp 46028200
    INFO [qshell] qshell return value timestamp: 46028199, local time: 46028634
    INFO [qshell] Send cmd: 'land_detector start multicopter'
    INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
    INFO [muorb] SLPI: qshell gotten: land_detector start multicopter
    INFO [muorb] SLPI: Ok executing command: land_detector start multicopter
    INFO [muorb] SLPI: Sending qshell retval with timestamp 46072642, current timestamp 46072643
    INFO [qshell] qshell return value timestamp: 46072642, local time: 46073625
    INFO [uorb] Advertising remote topic vehicle_land_detected
    INFO [muorb] SLPI: 46371633: reset position to last known position
    INFO [muorb] SLPI: 46371633: reset velocity to zero
    INFO [uorb] Advertising remote topic vehicle_local_position
    INFO [uorb] Advertising remote topic vehicle_odometry
    INFO [uorb] Advertising remote topic estimator_states
    INFO [uorb] Advertising remote topic estimator_status
    INFO [uorb] Advertising remote topic estimator_status_flags
    INFO [uorb] Advertising remote topic estimator_innovations
    INFO [uorb] Advertising remote topic estimator_innovation_test_ratios
    INFO [uorb] Advertising remote topic estimator_innovation_variances
    INFO [dataman] Unknown restart, data manager file '/data/px4/dataman' size is 11798680 bytes
    INFO [uorb] Advertising remote topic estimator_sensor_bias
    INFO [muorb] SLPI: Advertising remote topic position_setpoint_triplet
    INFO [muorb] SLPI: Advertising remote topic mission
    INFO [commander] LED: open /dev/led0 failed (22)
    INFO [muorb] SLPI: Advertising remote topic led_control
    INFO [muorb] SLPI: Advertising remote topic tune_control
    INFO [PreFlightCheck] Failed EKF health preflight check while waiting for filter to settle
    INFO [muorb] SLPI: Advertising remote topic vehicle_control_mode
    INFO [muorb] SLPI: Advertising remote topic vehicle_status
    INFO [muorb] SLPI: Advertising remote topic actuator_armed
    INFO [muorb] SLPI: Advertising remote topic commander_state
    INFO [uorb] Advertising remote topic rate_ctrl_status
    INFO [uorb] Advertising remote topic actuator_controls_0
    INFO [muorb] SLPI: Advertising remote topic vehicle_status_flags
    INFO [muorb] SLPI: Advertising remote topic vehicle_command
    INFO [commander] Handling Commander command 176
    INFO [muorb] SLPI: Advertising remote topic vehicle_command_ack
    INFO [mavlink] mode: Onboard, data rate: 100000 B/s on udp port 14556 remote port 14557
    INFO [muorb] SLPI: Marking DeviceNode(vehicle_command) as advertised in process_remote_topic
    ERROR [muorb] SLPI: UBX CFG-GNSS message ACK failed
    INFO [muorb] SLPI: Advertising remote topic telemetry_status

    VOXL 2

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    @Eric-Katzfey Thanks Eric, Vinn.

    Here are the detailed debug info.

    Send cmd: 'gps start'
    cannot reset all parameters on client side
    px4io read failed
    px4io io_reg_get(0,0,1): data error -5
    IO not installed
    Detection attempt failed
    ...
    Failed to execute command px4io detect
    command failed

    VOXL 2

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    I get an error message
    "[muorb] SLPI: UBX CFG-GNSS message ACK failed".

    VOXL 2

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    @Eric-Katzfey Yes. The magnetometer is working correctly. QGC display indicator suggests so.
    The LED also blinking GPS lock

    VOXL 2

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    Thanks. I doubt it is the hardware that is not working. The GPS fix indicator on the module is blinking blue.

    How do I check that the VOXL2 is talking to the GPS module correctly?
    Is there a command to see the GPS location readings on VOXL2?

    VOXL 2

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    unnamed.jpg |

    VOXL 2

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    The GPS module says M8N.
    I bought it a couple of months ago under the VOXL2 flight deck.

    I have tried "qshell gps start". No it doesnt resolve the issue.

    VOXL 2

  • GPS Not OK with VOXL2 PX4
    kp ngK kp ng

    Hi.

    I am unable to get set up the GPS unit which came with the VOXL2 flight deck I purchased.

    muorb SLPI: UBX CFG-GNSS message ACK failed
    ...
    muorb SLPI: status: NOT OK, port:6, baudrate: 0

    Would appreciate some help.

    VOXL 2

  • VOXL2 PX4 cannot connect to QGC
    kp ngK kp ng

    I have managed to get the VOXL2 px4 to connect to QGC

    VOXL 2

  • VOXL2 PX4 cannot connect to QGC
    kp ngK kp ng

    Sorry. Here is the voxl-version output.
    I have also check with another PX4 flight control board and it works. so it is unlikely an issue with QGC side.

    libmodal-cv              0.2.3
    libmodal-exposure        0.0.7
    libmodal-journal         0.2.1
    libmodal-json            0.4.3
    libmodal-pipe            2.8.2
    libqrb5165-io            0.1.0
    libvoxl-cci-direct       0.1.5
    libvoxl-cutils           0.1.1
    mv-voxl                  0.1-r0
    qrb5165-bind             0.1-r0
    qrb5165-dfs-server       0.1.0
    qrb5165-imu-server       0.5.0
    qrb5165-slpi-test-sig    01-r0
    qrb5165-system-tweaks    0.1.5
    qrb5165-tflite           2.8.0-2
    voxl-bind                0.0.1
    voxl-camera-calibration  0.2.3
    voxl-camera-server       1.3.5
    voxl-cpu-monitor         0.3.0
    voxl-docker-support      1.2.4
    voxl-gphoto2-server      0.0.10
    voxl-jpeg-turbo          2.1.3-4
    voxl-libgphoto2          0.0.4
    voxl-libuvc              1.0.7
    voxl-logger              0.3.4
    voxl-mavlink             0.1.0
    voxl-mavlink-server      0.3.0
    voxl-modem               0.16.1
    voxl-mongoose            7.7.0-1
    voxl-mpa-to-ros          0.3.6
    voxl-mpa-tools           0.7.6
    voxl-opencv              4.5.5-1
    voxl-portal              0.5.0
    voxl-px4                 1.12.31
    voxl-px4-imu-server      0.1.2
    voxl-qvio-server         0.8.2
    voxl-remote-id           0.0.5
    voxl-streamer            0.4.1
    voxl-suite               0.9.5
    voxl-tag-detector        0.0.4
    voxl-tflite-server       0.3.1
    voxl-utils               1.2.2
    voxl-uvc-server          0.1.3
    voxl-vision-px4          1.4.0
    voxl2-system-image       1.5.5-r0
    voxl2-wlan               1.0-r0
    
    VOXL 2

  • VOXL2 PX4 cannot connect to QGC
    kp ngK kp ng

    I also don't see any UDP traffic originating from VXOL2 using wireshark on the laptop hosting QGroundControl. Please help

    VOXL 2

  • VOXL2 PX4 cannot connect to QGC
    kp ngK kp ng

    I checked on QGroundControl Logs. It says
    "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/4"

    VOXL 2

  • VOXL2 PX4 cannot connect to QGC
    kp ngK kp ng

    I have a voxl2 flight deck.

    I want to set it up and simulate fly by waypoints, guided by GPS, using QGC-Gazebo and PX4 before I go and size up the motor-props-frame and develop the drone.

    So far,
    I have been able to set up the mavlink and PX4 server running.
    I have been able to ping the QGC computer from voxl2 and voxl2 from computer
    I have set up the IP address to be the computer hosting QGC.

    But I am unable to get QGC automatically connect to the PX4. It says disconnected
    I am not sure if it is QGC issue or the VOXL2 setup though

    VOXL 2

  • VOXL2 PX4 cannot connect to QGC
    kp ngK kp ng

    @Zachary-Lowell-0 Hi. Yes. I am able to set up voxl-wifi station properly and can ping between my QgroundCtrl computer and VOXL2. I am to run mavlink server and vision px4 as well.

    VOXL 2

  • VOXL2 PX4 cannot connect to QGC
    kp ngK kp ng

    Hi.

    I purchased the VOXL2 flight deck (without the ESC and motors) and tried to run the example to connect PX4 MAVLINK to QGC. I play to run the flight simulation with gazebo
    I am unable to get connection up. I also realised there is no config files e.g.
    /etc/modalai/voxl-px4.config

    Would appreciate if you could help

    VOXL 2
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups