GPIO missing in /sys/class/gpio
-
I'm trying to connect a serial device to J19 (Pin10, 11)
voxl-gpio read 179 ERROR: Failed to open path /sys/class/gpio/gpio1279/valueI don't see GPIO 178 and 179 on my system:
-
@psafi I was able to use the info in the link below to enable the GPIO pin
-
@psafi , before calling
voxl-gpio read, you need to enable the pin by setting it to input or output. Please checkvoxl-gpio -h. (hint: usevoxl-gpio -m/voxl-gpio mode)Alex
-
@Alex-Kushleyev Thank you!
I understand these ports are intended for RC input and QUP7 is connected directly to the DSP. I am considering these ports to connect a SiK radio (data format can be raw or mavlink). I want to make information coming through the radio available to ROS and PX4 at the same time. Can I use this port at all for application running on linux or is this only available to voxl-px4? -
@psafi said in GPIO missing in /sys/class/gpio:
@Alex-Kushleyev Thank you!
I understand these ports are intended for RC input and QUP7 is connected directly to the DSP. I am considering these ports to connect a SiK radio (data format can be raw or mavlink). I want to make information coming through the radio available to ROS and PX4 at the same time. Can I use this port at all for application running on linux or is this only available to voxl-px4?I am already using the External UART (J10) for another MAVLink device (optical flow sensor board) which is currently configured and working with PX4 (I don't need to intercept that one on the linux side). Would it be possible to connect my serial radio to J10 and switch my optical flow to J19 (and configure PX4 to read MAVLink from J19-10,11)?
-
@psafi Unfortunately, the Mavlink module is not available on the DSP side. We tried it in the past and there were a lot of issues so we only have it on the apps side. You are welcome to try to add it into the DSP side and see how it goes.
