How do you use Graupner SUMD with Pixhawk ?

Hi,

I know how to use Graupner SUMO, but I would like to try SUMD with 3.2.1.

I found PX4 SUMD which I thought would be similar and therefore I connected the Spektrum/DSM port of the Pixhawk with GND and signal only to the Graupner RX port 8. I didn't connect Vcc because its 3V3 at the Pixhawk and I use 5V. Didn't work, any ideas ?

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Hi,

    Pull request is now accessible here

    Benoit

    Ap sumd grxx compatibility by Benoit3 · Pull Request #72 · ArduPilot/PX4Firmware
    This Pull Request superseded Pull Request #71. It corrects issue PX4#5197 and PX4#5285. It has been tested in flight on ArduPlane 3.7.1 and on bench…


  • Benoît said:


    @Ultrafuge : what do you mean by "MP act as if it would be on hold" ?

    No big deal, don't worry, in my case MP doesn't reflect shutting down the TX (channels are showing last value), I have to restart MP to see the correct state (failsafe and channels 0 and grey). 

  • Hi,

    @Andre : yes an internal pullup (or down) may have the same effect than connecting input to the ground, but i'm not px4io hardware specialist

    @Ultrafuge : what do you mean by "MP act as if it would be on hold" ?

    Yes at power up (with tx off) the GR 16 send some channel values (visible on MP), decoded by the Pixhawk, but the flag failsafe is set => the pixhawk is really in failsafe  (and then circle/rtl mode)

    After that if you set the transmitter on and then off, the gr16 will have a different behaviour and won't send any data ( with SUMDOF setting), and MP won't display any values.

    Graupner provide an alternate software for GR16, which send always data, even in FS with SUMDOF setting. In this case data are tagged with "failsafe" flag.

    The merge on master is not an huge job, just need the time to do it.

    Benoit

     

  • Hi Benoit,

    I just did one quick test. MX-20 + GR-16 SUMD OF 12 all 12 channels were working fine, but failsafe didn't really work in MP 1.3.41. MP acts as if it would be on Hold, but when you reconnect it shows correct OFF behaviour, therefore I think it should work.

    SRXL: http://wiki.beastx.com/index.php/SRXL_-_Serial_Receiver_Link_protoc...

    They should be very similar, but ofcourse never ever the same. The tragedy is, that even Futaba changes SBUS whenever they like, but the name is always the same :-(((.

    Thanks a lot for your work !

    SRXL - Serial Receiver Link protocol - BEASTX Wiki
  • Sounds like RCIN should get it's internal pullup enabled.

  • Yes, I was not clear and you are right :

    - I had connected RCIN signal wire to RCIN GND and SBUS signal wire to SBUS GND to avoid spurious input on these signals.

    I will propose these changes for the master but these files have been modified to support srxl protocol, I need to do the merge.

    Benoit



  • Benoît said

    RCIN signal input and SBUS signal input was connected to avoid spurious input on these pins.

    Sorry I am not sure what you say. Does this mean you connected RCIN signal wire with SBUS signal wire or does it mean you connected RCIN signal wire to RCIN GND and SBUS signal wire to SBUS GND as written above ?

    Could you please ask Randy and Tridge to put this in master.

  • And here are source files

    sumd-a-b-files.tar.gz

  • Hello,

    modification have been tested in flight this afternoon without problem.

    Here are the file modified on ArduPlane 3.7.1 and the result of the build.

    My GR16 receiver was powered from the servo rail (servo 8 plug)  as I have some doubt with power on RCIN (which seems to come from one px4io processor output pin). RCIN signal input and SBUS signal input was connected to avoid spurious input on these pins.

    Do not hesitate to give your feedback.

    Benoît

    ArduPlane-v2-3.7.1-SUMD-B.px4

  • Hi Benoit,

    Thank you very much, please report once you think it will work and I will try as well.

This reply was deleted.

Activity