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

      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