Flying ArduCopter with a Joystick


I tried following today on 2.0.49 firmware with APM Planner 1.0.86. As you can see from the video, there was obvious lag in the command around 1/2 seconds. The other thing the quad was doing it was not coming to stabilize position when I centered the joystick. This is because of the uneven cushion I placed above table. The settings are

Joystick: Saitek Cyborg

Telemetry: 900Mhz xbees @ 57600bps link speed

frame gaui 500X

 

Joystick is pretty slow to respond. When I checked in windows game controller I found out that in game controller calibration looking at the raw data the joystick response is slow. So its a windows + PC issue

E-mail me when people leave their comments –

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

Join diydrones

Comments

  • I don't know about Farooq, but the reason why I wanted to used wireless instead of the RC was because, I thought it would be good redundancy to have both and the range of the APC220 is supposed to be 2KM, so theoretically longer than my Turniqy 9x.

  • Moderator

    Why the interest in using a joystick? You have essentially reduced what is a fairly well designed solution using at least four channels, and two sticks to handle all three axis and power, down to a two or three channels, with a stick and a lever. What benefits are you seeking by reducing your controls and increasing (significantly) the potential points of failure (usb drivers, joystick drivers, operating system latency, APM Mission Planner event loops, event encoding and messaging, FTDI drivers, Xbee radio buffers, MAVlink encoding/decoding, adding significantly more MAVlink commands to an already saturated link, etc)

     

    I am not dismissing your goal, you may have many thoughts about the benefits, or it might be "just because", and I am curious about these ideas.

  • So, basically this feature is not yet possible with any existing wireless system, Mike?

  • Moderator

    You are unlikely to see any benefit by changing the Xbee data rates to 115k, because the radio link is just beyond 56k. In fact, you are likely to see poorer performance due to buffer problems and retransmits. 

  • You should just take the props off, it's a lot safer.  I did my testing without props, and saw the motor lag, and decided not to pursue it due to the latency issues.

  • No actually in flights later on I realized its not 1/2 second. Actually its night here and I was testing in my  room. Tomorrow I shall test it in open then I shall be able to confirm that if it flyable with joystick with an acceptable lag or not

  • It can't be the joystick causing lag.  With that kind of lag, it would be impossible to play games.

  • On the fact that it may be a Windows Lag. I wonder if there is a process or something in the background thats slowing it. That's a size-able slow down and it doesn't seem like it should be that slow just because of Windows.

  • I shall check it tomorrow on 115200 but after doing tests in open. However as I said when I tested the joystick in control panel in game controller I could visibly see the lag. So its a windows lag or at least one reason is its because of the windows

  • Yes, I tried it with my APC220 too, and I notice the lag too.

    If you connect to the USB, then the lag goes away.  I suspect that its due to my APC having a air rate of 19200bps.  But your Xbee is at 56K, and you're still getting lag.  I wonder if 115K Xbee is fast enough.

This reply was deleted.