Emlid

Community Forum

Arducopter spams GPIO related mavlink messages


(mkarklins) #1

Can reproduce with latest navio2 raspbian image as well as with latest arducopter binary installed which has version 3.6.8

Looking at the tcpdump sudo tcpdump -n udp port 14550 -X the arducopter spams messages (edited for clarity):

GPIO_Sysfs: Unable to get value file descriptor for pin 4.
GPIO_Sysfs: Unable to write pin 16 value.
APM: ArduCopter V3.6.8 (2f409678)
APM: Frame: QUAD
GPIO_Sysfs: Unable to get value file descriptor for pin 4.
GPIO_Sysfs: Unable to write pin 16 value.

I found that the issue has been reported before in the ardupilot github, but it seems that it has been resolved since ~3.6.0, so I’m a little confused why it’s happening now.

Has anyone else witnessed a similar behavior?


(Andrew Yushkevich) #3

Can you tell a little bit more about what you’re trying to accomplish?


(mkarklins) #4

I want interact with the drone using Dronekit via MAVLINK.

When I connected to the drone using e.g. mavproxy.py I noticed that there’s a huge amount of GPIO_Sysfs messages being sent from the arducopter daemon.

It’s not a show-stopper issue, because I can ignore them, but it seemed to have been fixed in the latest versions of Ardupilot, so I wanted to know why I’m still seeing this behavior. Or maybe there’s actually something wrong with my raspberry/navio2 shield’s GPIO pins.