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

    Detected 0 radio channels. To operate PX4 you need at least 5 channels

    Sentinel
    4
    17
    358
    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.
    • Paul CarffP
      Paul Carff @Paul Carff
      last edited by

      @Paul-Carff
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic autotune_attitude_control_status
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: mc_autotune_attitude_control start
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: land_detector start multicopter
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'land_detector'
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'start'
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg2 = 'multicopter'
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: land_detector start multicopter
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_land_detected
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_toINFO [qshell] Send cmd: 'manual_control start'
      Jul 30 20:13:13 m0054 voxl-px4[1907]: INFO [qshell] qshell return value timestamp: 16149538, local time: 16151789
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] Send cmd: 'control_allocator start'
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] qshell return value timestamp: 16436082, local time: 16437240
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] Send cmd: 'rc_update start'
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] qshell return value timestamp: 16756354, local time: 16757722
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] Send cmd: 'commander start'
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] qshell return value timestamp: 17013967, local time: 17016102
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] Send cmd: 'commander mode manual'
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] qshell return value timestamp: 17066595, local time: 17067798
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] Send cmd: 'param_set_selector start'
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] qshell return value timestamp: 17105139, local time: 17106319
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] Send cmd: 'flight_mode_manager start'
      Jul 30 20:13:14 m0054 voxl-px4[1907]: INFO [qshell] qshell return value timestamp: 17267022, local time: 17269946
      Jul 30 20:13:15 m0054 voxl-px4[1907]: pic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: manual_control start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'manual_control'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'start'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: manual_control start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic manual_control_setpoint
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: control_allocator start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'control_allocator'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'start'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic control_allocator_status
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Marking DeviceNode(control_allocator_status) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic actuator_motors
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic actuator_servos
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic actuator_servos_trim
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: control_allocator start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: rc_update start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'rc_update'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'start'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: RC_MAP_MODE_SW deprecated
      Jul 30 20:13:15 m0054 voxl-px4[1907]: ERROR [muorb] SLPI: Cannot reset parameters on client side
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: rc_update start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: commander start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'commander'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'start'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Creating pthread commander
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Successfully created px4 task PX4_commander with tid 2097641
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic led_control
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: LED: open /dev/led0 failed (22)
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic tune_control
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: commander start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic event
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic health_report
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic failsafe_flags
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic actuator_armed
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_control_mode
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_status
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic failure_detector_status
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_thrust_setpoint
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_torque_setpoint
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_rates_setpoint
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_local_position_setpoint
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_attitude_setpoint
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: commander mode manual
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'commander'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'mode'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg2 = 'manual'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_command
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: commander mode manual
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic vehicle_command_ack
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Marking DeviceNode(vehicle_attitude_setpoint) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: param_set_selector start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'param_set_selector'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'start'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: param_set_selector start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: qshell gotten: flight_mode_manager start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg0 = 'flight_mode_manager'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: arg1 = 'start'
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Marking DeviceNode(vehicle_command) as advertised in process_remote_topic
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Ok executing command: flight_mode_manager start
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic actuator_controls_status_0
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [dataman] data manager file '/data/px4/dataman' size is 7866640 bytes
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic transponder_report
      Jul 30 20:13:15 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic rtl_time_estimate
      Jul 30 20:13:17 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic position_sINFO [mavlink] MAVLink only on localhost (set param MAV_{i}_BROADCAST = 1 to e
      Jul 31 21:35:31 m0054 voxl-px4[1907]: etpoint_triplet
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [mavlink] mode: Onboard, data rate: 100000 B/s on udp port 14556 remote port 14557
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic telemetry_status
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [mavlink] partner IP: 127.0.0.1
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic vehicle_visual_odometry
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic obstacle_distance
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic offboard_control_mode
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic timesync_status
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic estimator_aid_src_ev_hgt
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic estimator_aid_src_ev_pos
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic estimator_aid_src_ev_vel
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic estimator_aid_src_ev_yaw
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [mavlink] mode: Normal, data rate: 100000 B/s on udp port 14558 remote port 14559
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Marking DeviceNode(telemetry_status) as advertised in process_remote_topic
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [px4] Startup script returned successfully
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: u-blox firmware version: SPG 3.01
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: u-blox protocol version: 18.00
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: u-blox module: NEO-M8N-0
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [uORB] Advertising remote topic sensor_gps
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [mavlink] partner IP: 127.0.0.1
      Jul 31 21:35:31 m0054 voxl-px4[1907]: WARN [uORB] orb_advertise_multi: failed to set queue size
      Jul 31 21:35:31 m0054 voxl-px4[1907]: INFO [muorb] SLPI: Advertising remote topic ping
      Jul 31 21:35:31 m0054 voxl-px4[1907]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read. Got 16 bytes. Protocol byte is 0x01

      --- Repeats that last line.

      Paul CarffP 1 Reply Last reply Reply Quote 0
      • Paul CarffP
        Paul Carff @Paul Carff
        last edited by

        @Paul-Carff

        I ran the SDK install again and am still getting this at the end of output of the journalctl -b -u voxl-px4

        voxl2:/$ px4-listener input_rc
        never published

        voxl2:/$ journalctl -b -u voxl-px4
        Jul 31 22:20:03 m0054 voxl-px4[1868]: WARN [uORB] orb_advertise_multi: failed to set queue size
        Jul 31 22:20:03 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:03 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:04 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:04 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:04 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:05 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:05 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:05 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:06 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:06 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:06 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read
        Jul 31 22:20:06 m0054 voxl-px4[1868]: ERROR [muorb] SLPI: Spektrum RC: Read something other than correct DSM frame on read

        Paul CarffP 1 Reply Last reply Reply Quote 0
        • Paul CarffP
          Paul Carff @Paul Carff
          last edited by

          @Paul-Carff I was wondering:

          • should try to reinstall 0.9.5?
          • it is the reciever?

          Will await your next suggestion.

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

            @Paul-Carff It looks like the correct driver is running but not receiving valid data on the serial port. This could indicate something wrong with the cabling or connectors. It's definitely not something we have seen before. You could try going back to 0.9.5 to see if it starts to work again. If it is still broken with 0.9.5 then that indicates a hardware problem. If it works with 0.9.5 then there is some sort of configuration issue with 1.0.0.

            Paul CarffP 1 Reply Last reply Reply Quote 0
            • Paul CarffP
              Paul Carff @Eric Katzfey
              last edited by

              @Eric-Katzfey
              Reflashed to 0.9.5 and have the same problem (expected this as that was my original issue.)

              The cable looks good from the receiver to the what looks like a board that is coated in silicon (I didn't want to start disassembling the drone yet.)

              I am wondering if it is the receiver that has failed?

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

                @Paul-Carff Unfortunately I don't have any other ideas. In theory it is a pretty simple interface. Is it possible to try a different receiver? Maybe that one has a hardware issue of some sort? Usually I will put an oscilloscope on the TX line coming out of the Spektrum receiver to see if I detect it trying to send data.

                Paul CarffP 1 Reply Last reply Reply Quote 0
                • Paul CarffP
                  Paul Carff @Eric Katzfey
                  last edited by

                  @Eric-Katzfey Thanks Eric - I will check the receiver and I have ordered a replacement to swap out as well. Will let you know what I find.

                  ? 1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User @Paul Carff
                    last edited by

                    @Paul-Carff

                    Again, sorry you're seeing this issue!

                    Check the connections on the side of sentinel, it appears you have power since you see the solid orange-bind LED, but maybe one of the data lines are not seated properly?
                    This is the binding board info: https://docs.modalai.com/sentinel-spektrum-bind-board/
                    This is the full part, you can see that it shares the same connector with GPS: https://www.modalai.com/products/voxl-2-gps-mag-rc-assembly?variant=40673762836531

                    If you can, I'd also open up the top and take a quick peak at the bind board connections as well.
                    Maybe part of that board died on you?

                    You're binding using the voxl2 utilities? We have been using the "-s" option from what I remember, DSMX 22.
                    On your DX8 and ix14, do you have 22 ms setting, etc?

                    It's worthwhile to try another Spektrum radio receiver.

                    Paul CarffP 1 Reply Last reply Reply Quote 0
                    • Paul CarffP
                      Paul Carff @Guest
                      last edited by

                      @RichieRich
                      Connected a new radio and have the same issue.

                      This is curious as I can put it into bind mode via adb shell or ssh and voxl-bind -t or voxl-bind-spektrum -t depending on the SDK version.
                      So it does communicate.

                      Confirm I am using the 22 ms setting and now that I just re-read your note and looking at the githhub:

                      Command Line Options

                      -d, --debug enable debug messages
                      -h, --help print this help messsage
                      -t, --DSM2_22 3 pulses (DSM2 1024/22ms)
                      -f, --DSM2_11 5 pulses (DSM2 2048/11ms)
                      -s, --DSMX_22 7 pulses (DSMX 22ms)

                      I will give the -s command a test tonight.

                      I am doing this on my own time in the evenings - sorry I am so slow to respond.

                      Paul CarffP 1 Reply Last reply Reply Quote 0
                      • Paul CarffP
                        Paul Carff @Paul Carff
                        last edited by

                        @Paul-Carff OMG - I just read my notes when I first configured and I wrote down that I used voxl-bind -s
                        Can't wait to test when I get home tonight.

                        Paul CarffP 1 Reply Last reply Reply Quote 0
                        • Paul CarffP
                          Paul Carff @Paul Carff
                          last edited by

                          @Paul-Carff
                          Well that is embarassing. -s not -t

                          Thanks all for the help - can close this one out as operator error.

                          tomT 1 Reply Last reply Reply Quote 0
                          • tomT
                            tom admin @Paul Carff
                            last edited by

                            @Paul-Carff Thanks for sharing your findings! It's super helpful for future users 🙂

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