ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    VOXL2 SDK 1.0.0-beta6 voxl-px4 couldn't arm UAV (GPS LED always RED blinking)

    VOXL 2
    2
    33
    764
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Eric KatzfeyE
      Eric Katzfey Dev Team @Aaky
      last edited by

      @Aaky Your parameters must not be set correctly. You can find our parameter sets here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params. One of the parameters controls the CPU monitoring and our parameter set disables that check here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/params/v1.14/platforms/Sentinel_V1.params#L17

      1 Reply Last reply Reply Quote 0
      • Eric KatzfeyE
        Eric Katzfey Dev Team @Aaky
        last edited by

        @Aaky said in VOXL2 SDK 1.0.0-beta6 voxl-px4 couldn't arm UAV (GPS LED always RED blinking):

        GPS Horizontal Pos Error too high

        This is the error that is preventing arming.

        A 1 Reply Last reply Reply Quote 0
        • A
          Aaky @Eric Katzfey
          last edited by Aaky

          @Eric-Katzfey Thank you for the quick response. I am aware of those default parameters. Will again give it a try.

          What is the reason behind GPS LED continuously blinking RED? That wasn't happening even if I was in indoor with GPS on older version PX4 1.12.31.

          Also in manual mode GPS Horizontal pos error preflight check shouldn't matter right? I am trying to arm in manual mode only and not in position mode.

          A Eric KatzfeyE 3 Replies Last reply Reply Quote 0
          • A
            Aaky @Aaky
            last edited by Aaky

            @Eric-Katzfey I tried to set parameters from above-mentioned link with ekf2_helpers for GPS outdoor with baro but with no luck, still GPS led continues to blink red.

            I also tried deleting default parameter file at /data/px4/parm/parameter and again restarting PX4 service still with no luck.

            I also tried flashing sentinel V1/V2 parameters but again with no luck.

            I can see 12 satellites with good enough HDOP and VDOP but still GPS led blinks red and never let's me arm the drone.

            I can sense some initialisation is not correct which is causing this. I have freshly installed system image with no changes on PX4 firmware side.

            Please help me further on this issue.

            Eric KatzfeyE 3 Replies Last reply Reply Quote 0
            • Eric KatzfeyE
              Eric Katzfey Dev Team @Aaky
              last edited by

              @Aaky Do you still see it fail with GPS Horizontal Pos Error too high?

              1 Reply Last reply Reply Quote 0
              • Eric KatzfeyE
                Eric Katzfey Dev Team @Aaky
                last edited by

                @Aaky Yes, you should be able to arm in manual mode without good GPS.

                1 Reply Last reply Reply Quote 0
                • Eric KatzfeyE
                  Eric Katzfey Dev Team @Aaky
                  last edited by

                  @Aaky Can you show us the current output messages of px4 like in your first post?

                  1 Reply Last reply Reply Quote 0
                  • Eric KatzfeyE
                    Eric Katzfey Dev Team @Aaky
                    last edited by

                    @Aaky What happens if you set the parameter SYS_HAS_GPS to 0?

                    1 Reply Last reply Reply Quote 0
                    • Eric KatzfeyE
                      Eric Katzfey Dev Team @Aaky
                      last edited by

                      @Aaky What if you set COM_ARM_WO_GPS to 1?

                      A 1 Reply Last reply Reply Quote 0
                      • A
                        Aaky @Eric Katzfey
                        last edited by

                        @Eric-Katzfey Yes I still see it fail.

                        SYS_HAS_GPS setting to 0 has no effect.

                        COM_ARM_WO_GPS has no effect.

                        I will share the logs in this situation soon.

                        My main concern is why GPS LED is not going into blue blink even if it dosent have GPS lock in indoor just like it used to go in 1.12.31 PX4 version?

                        Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                        • Eric KatzfeyE
                          Eric Katzfey Dev Team @Aaky
                          last edited by

                          @Aaky It flashes red when a preflight check is failing. It doesn't necessarily have anything to do with GPS.

                          A 1 Reply Last reply Reply Quote 0
                          • A
                            Aaky @Eric Katzfey
                            last edited by

                            @Eric-Katzfey Okay but On QGC No such preflight check failure notification is coming up which can help solve this problem. I am using QGC v4.2.4 but I have also tried with v3.5.6.

                            Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                            • Eric KatzfeyE
                              Eric Katzfey Dev Team @Aaky
                              last edited by

                              @Aaky That is why you need to share the output from voxl-px4. It should print out an indication of which preflight check failed.

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                Aaky @Eric Katzfey
                                last edited by

                                @Eric-Katzfey Please find attached logs of voxl-px4 service.

                                Below log is without daemon mode and with Holybro GPS

                                voxl2:/etc/systemd/system$ voxl-px4 -b
[INFO] /etc/modalai/voxl-px4.conf not found, using defaults
Found DSP signature file
[INFO] Holybro GPS selected

*************************
GPS=HOLYBRO
RC=SPEKTRUM
OSD=DISABLE
DAEMON_MODE=DISABLE
SENSOR_CAL=ACTUAL
EXTRA STEPS:
*************************

INFO  [px4] mlockall() enabled. PX4's virtual address space is locked into RAM.
INFO  [px4] assuming working directory is rootfs, no symlinks needed.
INFO  [muorb] Got muorb init command
Sending initialization request
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
INFO  [muorb] SLPI: muorb aggregator thread running
INFO  [muorb] muorb protobuf initalize method succeeded
INFO  [muorb] succesfully did ADVERTISE_TEST_TYPE
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097656
INFO  [muorb] succesfully did SUBSCRIBE_TEST_TYPE
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097655
INFO  [muorb] succesfully did TOPIC_TEST_TYPE
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097654
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097653
INFO  [muorb] succesfully did UNSUBSCRIBE_TEST_TYPE
INFO  [muorb] muorb test passed

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

px4 starting.

INFO  [px4] startup script: /bin/sh /usr/bin/voxl-px4-start 0
INFO  [muorb] SLPI: Advertising remote topic log_message
INFO  [parameters] Starting param sync THREAD

*************************
GPS: HOLYBRO
RC: SPEKTRUM
OSD: DISABLE
EXTRA STEPS:
	
*************************

INFO  [muorb] SLPI: Starting param sync THREAD
Running on M0054
INFO  [muorb] SLPI: before starting the qshell_entry task
INFO  [muorb] SLPI: Creating pthread qshell

INFO  [muorb] SLPI: Successfully created px4 task PX4_qshell with tid 2097652
INFO  [muorb] SLPI: qshell entry.....
INFO  [muorb] SLPI: after starting the qshell_entry task
INFO  [muorb] SLPI: Init app map initialized
INFO  [param] selected parameter default file /data/px4/param/parameters
INFO  [muorb] SLPI: Marking DeviceNode(parameter_client_reset_request) as advertised in process_remote_topic
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_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] Marking DeviceNode(parameter_client_set_value_response) as advertised in process_remote_topic
INFO  [parameters] BSON document size 2081 bytes, decoded 2081 bytes (INT32:30, FLOAT:64)
INFO  [logger] logger started (mode=all)
Starting IMU driver with no rotation
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [qshell] Send cmd: 'icm42688p start -s'
INFO  [muorb] SLPI: qshell gotten: icm42688p start -s
INFO  [muorb] SLPI:   arg0 = 'icm42688p'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-s'

INFO  [muorb] SLPI: *** SPI Device ID 0x26000a 2490378
INFO  [uORB] Advertising remote topic sensor_accel
INFO  [uORB] Advertising remote topic sensor_gyro
INFO  [muorb] SLPI: ICM42688P::probe successful!
INFO  [muorb] SLPI: on SPI bus 1
INFO  [muorb] SLPI: icm42688p #0 on SPI bus 1
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: >>> ICM42688P this: 3176c0c0
INFO  [muorb] SLPI: Ok executing command: icm42688p start -s
INFO  [uORB] Advertising remote topic qshell_retval
INFO  [muorb] SLPI: >>> ICM42688P this: 3176c0c0
INFO  [qshell] qshell return value timestamp: 1444994972, local time: 1444999175
INFO  [muorb] SLPI: >>> ICM42688P this: 3176c0c0
INFO  [muorb] SLPI: Register interrupt b21d3164 e620e69c 3176c0c0
INFO  [uORB] Advertising remote topic sensor_gyro_fifo
INFO  [uORB] Advertising remote topic sensor_accel_fifo
INFO  [uORB] Advertising remote topic imu_server
INFO  [muorb] SLPI: >>> ICM42688P this: 3176c0c0
INFO  [qshell] Send cmd: 'icp101xx start -I -b 5'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: icp101xx start -I -b 5
INFO  [muorb] SLPI:   arg0 = 'icp101xx'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-I'

INFO  [muorb] SLPI:   arg3 = '-b'

INFO  [muorb] SLPI:   arg4 = '5'

INFO  [muorb] SLPI: *** I2C Device ID 0xb76329 12018473
INFO  [muorb] SLPI: icp101xx #0 on I2C bus 5
INFO  [muorb] SLPI:  address 0x63
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: icp101xx start -I -b 5
INFO  [qshell] qshell return value timestamp: 1446063254, local time: 1446065261
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:   arg0 = 'ist8310'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-R'

INFO  [muorb] SLPI:   arg3 = '10'

INFO  [muorb] SLPI:   arg4 = '-X'

INFO  [muorb] SLPI:   arg5 = '-b'

INFO  [muorb] SLPI:   arg6 = '1'

INFO  [muorb] SLPI: *** I2C Device ID 0x60e09 396809
INFO  [muorb] SLPI: ist8310 #0 on I2C bus 1
INFO  [muorb] SLPI:  (external)
INFO  [muorb] SLPI:  address 0xE
INFO  [muorb] SLPI:  rotation 10
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: ist8310 start -R 10 -X -b 1
INFO  [qshell] qshell return value timestamp: 1446122603, local time: 1446124645
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:   arg0 = 'gps'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Creating pthread gps

INFO  [muorb] SLPI: Successfully created px4 task PX4_gps with tid 2097648
INFO  [muorb] SLPI: Ok executing command: gps start
INFO  [qshell] qshell return value timestamp: 1446176501, local time: 1446178234
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:   arg0 = 'rgbled_ncp5623c'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-X'

INFO  [muorb] SLPI:   arg3 = '-b'

INFO  [muorb] SLPI:   arg4 = '1'

INFO  [muorb] SLPI:   arg5 = '-f'

INFO  [muorb] SLPI:   arg6 = '400'

INFO  [muorb] SLPI:   arg7 = '-a'

INFO  [muorb] SLPI:   arg8 = '56'

INFO  [muorb] SLPI: *** I2C Device ID 0x7b3809 8075273
INFO  [muorb] SLPI: rgbled_ncp5623c #0 on I2C bus 1
INFO  [muorb] SLPI:  (external)
INFO  [muorb] SLPI:  address 0x38
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
INFO  [qshell] qshell return value timestamp: 1446211242, local time: 1446214237
INFO  [uORB] Advertising remote topic sensor_mag
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [qshell] Send cmd: 'modal_io start'
INFO  [uORB] Advertising remote topic sensor_baro
INFO  [muorb] SLPI: qshell gotten: modal_io start
INFO  [muorb] SLPI:   arg0 = 'modal_io'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Advertising remote topic actuator_outputs
INFO  [muorb] SLPI: Ok executing command: modal_io start
INFO  [muorb] SLPI: Opened UART ESC device
INFO  [qshell] qshell return value timestamp: 1446338696, local time: 1446341515
INFO  [uORB] Advertising remote topic esc_status
Starting Spektrum RC
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: spektrum_rc start
INFO  [qshell] Send cmd: 'spektrum_rc start'
INFO  [muorb] SLPI:   arg0 = 'spektrum_rc'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Creating pthread spektrum_rc_main

INFO  [muorb] SLPI: Successfully created px4 task PX4_spektrum_rc_main with tid 2097645
INFO  [muorb] SLPI: Ok executing command: spektrum_rc start
INFO  [qshell] qshell return value timestamp: 1447405538, local time: 1447407699
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:   arg0 = 'voxlpm'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-X'

INFO  [muorb] SLPI:   arg3 = '-b'

INFO  [muorb] SLPI:   arg4 = '2'

INFO  [muorb] SLPI: *** I2C Device ID 0xd24411 13779985
INFO  [muorb] SLPI: Set i2c address 0x6a, fd 3
INFO  [muorb] SLPI: Set i2c address 0x44, fd 3
INFO  [uORB] Advertising remote topic battery_status
INFO  [muorb] SLPI: voxlpm #0 on I2C bus 2
INFO  [muorb] SLPI:  (external)
INFO  [muorb] SLPI:  address 0x44
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: voxlpm start -X -b 2
INFO  [uORB] Advertising remote topic power_monitor
INFO  [qshell] qshell return value timestamp: 1448475700, local time: 1448478307
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: sensors start
INFO  [muorb] SLPI:   arg0 = 'sensors'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [qshell] Send cmd: 'sensors start'
INFO  [uORB] Advertising remote topic sensor_selection
INFO  [uORB] Advertising remote topic sensors_status_imu
INFO  [uORB] Advertising remote topic vehicle_acceleration
INFO  [uORB] Advertising remote topic vehicle_angular_velocity
INFO  [uORB] Advertising remote topic sensor_combined
INFO  [uORB] Advertising remote topic vehicle_air_data
INFO  [uORB] Advertising remote topic vehicle_gps_position
ERROR [muorb] SLPI: Timeout waiting for parameter_server_set_used_response for SENS_MAG_MODE
INFO  [uORB] Advertising remote topic sensors_status_baro
INFO  [uORB] Advertising remote topic vehicle_magnetometer
INFO  [uORB] Advertising remote topic sensor_preflight_mag
INFO  [uORB] Advertising remote topic vehicle_imu
INFO  [uORB] Advertising remote topic vehicle_imu_status
INFO  [muorb] SLPI: Ok executing command: sensors start
INFO  [qshell] qshell return value timestamp: 1448704886, local time: 1448712168
INFO  [uORB] Advertising remote topic sensors_status_mag
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: ekf2 start
INFO  [muorb] SLPI:   arg0 = 'ekf2'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [qshell] Send cmd: 'ekf2 start'
INFO  [uORB] Advertising remote topic vehicle_attitude
INFO  [uORB] Advertising remote topic vehicle_local_position
INFO  [uORB] Advertising remote topic estimator_event_flags
INFO  [uORB] Advertising remote topic estimator_innovation_test_ratios
INFO  [uORB] Advertising remote topic estimator_innovation_variances
INFO  [uORB] Advertising remote topic estimator_innovations
INFO  [uORB] Advertising remote topic estimator_sensor_bias
INFO  [uORB] Advertising remote topic estimator_states
INFO  [uORB] Advertising remote topic estimator_status_flags
INFO  [uORB] Advertising remote topic estimator_status
INFO  [muorb] SLPI: Ok executing command: ekf2 start
INFO  [qshell] qshell return value timestamp: 1449031475, local time: 1449039018
INFO  [uORB] Advertising remote topic ekf2_timestamps
INFO  [uORB] Advertising remote topic vehicle_odometry
INFO  [uORB] Advertising remote topic estimator_aid_src_fake_pos
INFO  [uORB] Advertising remote topic estimator_aid_src_fake_hgt
INFO  [uORB] Advertising remote topic estimator_aid_src_mag_heading
INFO  [uORB] Advertising remote topic estimator_aid_src_mag
INFO  [uORB] Advertising remote topic estimator_aid_src_gravity
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:   arg0 = 'mc_pos_control'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Advertising remote topic estimator_aid_src_baro_hgt
INFO  [uORB] Advertising remote topic takeoff_status
INFO  [muorb] SLPI: Ok executing command: mc_pos_control start
INFO  [qshell] qshell return value timestamp: 1449174525, local time: 1449176355
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [qshell] Send cmd: 'mc_att_control start'
INFO  [muorb] SLPI: qshell gotten: mc_att_control start
INFO  [muorb] SLPI:   arg0 = 'mc_att_control'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Ok executing command: mc_att_control start
INFO  [qshell] qshell return value timestamp: 1449244387, local time: 1449246464
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:   arg0 = 'mc_rate_control'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Advertising remote topic rate_ctrl_status
INFO  [muorb] SLPI: Ok executing command: mc_rate_control start
INFO  [qshell] qshell return value timestamp: 1449391261, local time: 1449394034
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [qshell] Send cmd: 'mc_hover_thrust_estimator start'
INFO  [muorb] SLPI: qshell gotten: mc_hover_thrust_estimator start
INFO  [muorb] SLPI:   arg0 = 'mc_hover_thrust_estimator'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Ok executing command: mc_hover_thrust_estimator start
INFO  [qshell] qshell return value timestamp: 1449469671, local time: 1449473908
INFO  [qshell] Send cmd: 'mc_autotune_attitude_control start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: mc_autotune_attitude_control start
INFO  [muorb] SLPI:   arg0 = 'mc_autotune_attitude_control'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Advertising remote topic autotune_attitude_control_status
INFO  [muorb] SLPI: Ok executing command: mc_autotune_attitude_control start
INFO  [qshell] qshell return value timestamp: 1449531494, local time: 1449532797
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:   arg0 = 'land_detector'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = 'multicopter'

INFO  [muorb] SLPI: Ok executing command: land_detector start multicopter
INFO  [uORB] Advertising remote topic vehicle_land_detected
INFO  [qshell] qshell return value timestamp: 1449602580, local time: 1449606580
INFO  [qshell] Send cmd: 'manual_control start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: manual_control start
INFO  [muorb] SLPI:   arg0 = 'manual_control'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Ok executing command: manual_control start
INFO  [qshell] qshell return value timestamp: 1449685436, local time: 1449688087
INFO  [uORB] Advertising remote topic manual_control_setpoint
INFO  [qshell] Send cmd: 'control_allocator start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: control_allocator start
INFO  [muorb] SLPI:   arg0 = 'control_allocator'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Advertising remote topic control_allocator_status
INFO  [uORB] Marking DeviceNode(control_allocator_status) as advertised in process_remote_topic
INFO  [uORB] Advertising remote topic actuator_motors
INFO  [uORB] Advertising remote topic actuator_servos
INFO  [uORB] Advertising remote topic actuator_servos_trim
INFO  [muorb] SLPI: Ok executing command: control_allocator start
INFO  [qshell] qshell return value timestamp: 1450104510, local time: 1450108431
INFO  [qshell] Send cmd: 'rc_update start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: rc_update start
INFO  [muorb] SLPI:   arg0 = 'rc_update'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Ok executing command: rc_update start
INFO  [qshell] qshell return value timestamp: 1450511359, local time: 1450513507
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: commander start
INFO  [qshell] Send cmd: 'commander start'
INFO  [muorb] SLPI:   arg0 = 'commander'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Creating pthread commander

INFO  [muorb] SLPI: Successfully created px4 task PX4_commander with tid 2097641
INFO  [uORB] Advertising remote topic led_control
INFO  [muorb] SLPI: LED: open /dev/led0 failed (22)
INFO  [uORB] Advertising remote topic tune_control
INFO  [muorb] SLPI: Ok executing command: commander start
INFO  [qshell] qshell return value timestamp: 1450817059, local time: 1450818888
INFO  [uORB] Advertising remote topic event
INFO  [uORB] Advertising remote topic health_report
INFO  [uORB] Advertising remote topic failsafe_flags
INFO  [uORB] Advertising remote topic actuator_armed
INFO  [uORB] Advertising remote topic vehicle_control_mode
INFO  [uORB] Advertising remote topic vehicle_status
INFO  [uORB] Advertising remote topic failure_detector_status
INFO  [uORB] Advertising remote topic vehicle_thrust_setpoint
INFO  [uORB] Advertising remote topic vehicle_torque_setpoint
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: commander mode manual
INFO  [muorb] SLPI:   arg0 = 'commander'

INFO  [muorb] SLPI:   arg1 = 'mode'

INFO  [qshell] Send cmd: 'commander mode manual'
INFO  [muorb] SLPI:   arg2 = 'manual'

INFO  [uORB] Advertising remote topic vehicle_command
INFO  [muorb] SLPI: Ok executing command: commander mode manual
INFO  [uORB] Advertising remote topic vehicle_command_ack
INFO  [qshell] qshell return value timestamp: 1450866530, local time: 1450874528
INFO  [uORB] Advertising remote topic vehicle_rates_setpoint
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [qshell] Send cmd: 'param_set_selector start'
INFO  [muorb] SLPI: qshell gotten: param_set_selector start
INFO  [muorb] SLPI:   arg0 = 'param_set_selector'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Ok executing command: param_set_selector start
INFO  [qshell] qshell return value timestamp: 1450932625, local time: 1450933962
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [qshell] Send cmd: 'flight_mode_manager start'
INFO  [muorb] SLPI: qshell gotten: flight_mode_manager start
INFO  [muorb] SLPI:   arg0 = 'flight_mode_manager'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Marking DeviceNode(vehicle_command) as advertised in process_remote_topic
INFO  [muorb] SLPI: Ok executing command: flight_mode_manager start
INFO  [qshell] qshell return value timestamp: 1451123263, local time: 1451126349
INFO  [dataman] data manager file '/data/px4/dataman' size is 7866640 bytes
INFO  [muorb] SLPI: Advertising remote topic transponder_report
INFO  [muorb] SLPI: Advertising remote topic rtl_time_estimate
INFO  [muorb] SLPI: Advertising remote topic position_setpoint_triplet
INFO  [mavlink] mode: Onboard, data rate: 100000 B/s on udp port 14556 remote port 14557
INFO  [muorb] SLPI: Advertising remote topic telemetry_status
INFO  [mavlink] partner IP: 127.0.0.1
INFO  [muorb] SLPI: Advertising remote topic offboard_control_mode
INFO  [muorb] SLPI: Advertising remote topic obstacle_distance
INFO  [muorb] SLPI: Advertising remote topic timesync_status
INFO  [mavlink] mode: Normal, data rate: 100000 B/s on udp port 14558 remote port 14559
INFO  [muorb] SLPI: Marking DeviceNode(telemetry_status) as advertised in process_remote_topic
INFO  [mavlink] partner IP: 127.0.0.1
INFO  [mavlink] MAVLink only on localhost (set param MAV_{i}_BROADCAST = 1 to enable network)
INFO  [px4] Startup script returned successfully
pxh> INFO  [muorb] SLPI: Advertising remote topic ping
WARN  [uORB] orb_advertise_multi: failed to set queue size
INFO  [uORB] Advertising remote topic actuator_test
INFO  [uORB] Advertising remote topic trajectory_setpoint
INFO  [uORB] Advertising remote topic vehicle_constraints
INFO  [uORB] Advertising remote topic landing_gear
INFO  [uORB] Advertising remote topic actuator_controls_status_0
INFO  [uORB] Advertising remote topic mavlink_log
INFO  [muorb] SLPI: Connection to ground station lost	
INFO  [muorb] SLPI: GCS connection regained

                                One quick question, Is daemon mode enabling necessary on 1.14? What does daemon mode mean? Even with daemon enabled I face same problem.

                                I can see warning "WARN [uORB] orb_advertise_multi: failed to set queue size" coming up when first time I try to arm the UAV. Can this be problem?

                                Please help further what preflight check is failing as per above log. I am still unable to arm the UAV in manual mode and GPS LED is also always blinking red.

                                Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                                • Eric KatzfeyE
                                  Eric Katzfey Dev Team @Aaky
                                  last edited by

                                  @Aaky Daemon mode means it is running as a background system process. And that orb_advertise_multi warning can be safely ignored. Did you try to arm and get a failure in that log?

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    Aaky @Eric Katzfey
                                    last edited by

                                    @Eric-Katzfey Yes I tried to arm and got failure. What can be the reason as per the logs?

                                    Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                                    • Eric KatzfeyE
                                      Eric Katzfey Dev Team @Aaky
                                      last edited by

                                      @Aaky There isn't really anything in the log declaring a preflight failure. If you keep trying to arm do you get anything in the log? What does QGC tell you if you try to arm?

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        Aaky @Eric Katzfey
                                        last edited by Aaky

                                        @Eric-Katzfey QGC says, " MAV_CMD_COMPONENT_ARM_DISARM temperorily rejected".
                                        This happens in manual mode and GPS LED blinks red, even after I have completed calibration of Mag, Accel and gyro.
                                        Also whenever I ARM, I do not get anything on voxl-px4 logs.
                                        Should I send over my parameter file? Can that help?

                                        Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                                        • Eric KatzfeyE
                                          Eric Katzfey Dev Team @Aaky
                                          last edited by

                                          @Aaky What is the contents of /data/modalai/sku.txt?

                                          Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                                          • Eric KatzfeyE
                                            Eric Katzfey Dev Team @Eric Katzfey
                                            last edited by

                                            @Eric-Katzfey Perhaps run voxl-configure-mpa -f sentinel to reconfigure the system and then reboot and try again

                                            A 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Powered by NodeBB | Contributors