Hello guys, I have just recently encountered a strange incidence with Mission Planner 1.3.70 (build 1.3.7277.34800).
I managed to setup a Joystick (simulator controller) to override the RC Controller to control the drone via a TCP link. Managed to did it successfully over a span of few days for our bench testing.
However, it just decided to stop working one day. The Joystick setup window still recognizes the input from the “joystick”, all channels assigned properly, but it just does not pass on the signal to Mission Planner. The Radio Calibration window does not react to the “joystick” at all.
All settings remain stock, also SYSID_MYGCS = 255 (default).
I think that’s when I unplug everything to disconnect.
When everything was running, I can still move the sticks and the sliders in the Joystick window still moves, but not the one in the Initial Setup - Radio Calibration.
2020-04-02 15:08:42,209 INFO MissionPlanner.MAVLinkInterface - Request stream EXTRA2 at 4 hz for 1:1 (:0) [Main Serial reader]
2020-04-02 15:08:42,456 INFO MissionPlanner.MAVLinkInterface - Mavlink Bad Packet (Len Fail) len 32 pkno 125 (:0) [Main Serial reader]
2020-04-02 15:08:42,456 INFO MissionPlanner.MAVLinkInterface - unknown packet type 199 (:0) [Main Serial reader]
2020-04-02 15:08:42,457 INFO MissionPlanner.MAVLinkInterface - mav 1-1 seqno 209 exp 207 pkts lost 2 (:0) [Main Serial reader]
2020-04-02 15:08:42,561 INFO MissionPlanner.MAVLinkInterface - Mavlink Bad Packet (crc fail) len 30 crc 11820 vs 1513 pkno 35 RC_CHANNELS_RAW (:0) [Main Serial reader]
2020-04-02 15:08:42,565 INFO MissionPlanner.MAVLinkInterface - mav 1-1 seqno 217 exp 215 pkts lost 2 (:0) [Main Serial reader]
2020-04-02 15:08:42,606 INFO MissionPlanner.MAVLinkInterface - Mavlink Bad Packet (Len Fail) len 23 pkno 158 (:0) [Main Serial reader]
I uploaded all the log.X files to this folder so you can easily access those. Also, I’ll check on the comm link too, normally I setup a separated router dedicated for this, but was using a common router just now
Well, I see bad mavlink packets all over, and looks like the joystick is working.
I also noticed that you use an old version of Mission Planner with something that is definitely not Ardupilot… Most of the parameters are looks like unknown to me…
Yeap for sure the joystick is working, as it’s detectable in the joystick screen, just that it stops overriding the RC control whenever I click “enable” now.
Also, previously it was on 1.3.70, I recently downgraded back to 1.3.65 to see if it was the new version of MP that caused the bugs (but well, didnt solve).
And you are right, this is a very custom build hahaha, anyways thank you so much for your inputs. I guess I’ll just wait for the software builders of the drone to look if they messed up something
hi, can you solve your problem? I had this too. but i run mission planner on linux and it recognize joystick in joystick setup page but in radio calibration stick does not work.
New to the discourse, but have been learning Ardupilot the past month or so to use with our vehicles. I’m having the same issue, so wanted to revive this thread. Has anyone found a fix?
I ran a radio calibration last night - all joystick inputs were detected and I was able to calibrate. For some reason, now the roll, stick, and yaw joystick inputs are not working to calibrate. All other RC inputs are working and I’m able to set the limits. Running MP 1.3.80 build 1.3.8479.20… if that helps at all.
Actually, I read another thread and found that comparing params, writing params, then refreshing params fixed the issue of not seeing Roll, Pitch, & Yaw RC inputs in Mission Planner’s Radio Calibration.
If anyone is still stuggling - try that. Hope this helps!
Another observation with this - the same problem occurs when the Throttle signal is reversed i.e. the Reverse button is checked - that’s when the roll, pitch, and yaw inputs stop responding to input, at least via the sliders in radio calibration.
is necessary if You need joystick support under linux, when You build arducopter.
In other words, I think there is an issue , at least in ardupilot documentation, about this topic, because joystick support seems to be NOT enabled by default, at least under linux, so it is not possibile to download binary sitl with joystick support under linux, you musr build (compile) it.
MissionPlanner or GCSs are not necessary for handling joysticks in SITL , native SITL joystick support is sufficient, to play with SITL standalone on a PC, if it works.
I did not finish tests about, a few differences exist between MS-Windows and Linux behaviour of joystick, and I am investigating on them.
To be more technical,
I guess there is a problem in #define SFML GRAPHICS priorities allocation, while configuring sitl build.
Problem is “hidden” inside python scripts for cxx check.
–enable-osd should not be necessary.
I found, anyway, that under both MS-windows or Linux, OSD does not appear if You do not connect a GCS to arducopter,
may be the socket listening code precedes OSD rendering code…
I was also facing the same issue of being able to assign the joystick axis to respective channels but not being able to fetch the values in the Radio Calibration section. In my case, this error was caused by the RC override being timed out. Hence, changing the value of RC_OVERRIDE_TIME to -1 did the job for me.
Most of the parameters are looks like unknown to me…