I manually ran the commands in the aphw script and checked after I manually run arducopter
debian@beaglebone:~$ ls /sys/class/gpio/
export gpio80 gpiochip0 gpiochip32 gpiochip64 gpiochip96 unexport
debian@beaglebone:~$ ls /sys/class/gpio/gpio80
active_low device direction edge label power subsystem uevent value
debian@beaglebone:~$ cat /sys/class/gpio/gpio80/direction
out
debian@beaglebone:~$ cat /sys/class/gpio/gpio80/value
1
debian@beaglebone:~$ cat /sys/devices/platform/ocp/ocp:P8_15_pinmux/state
pruecapin_pu
Did you use chmod on every file that needs to be executed? See here: https://help.ubuntu.com/community/FilePermissions.
Oh. And...sometimes powering the receiver off of a separate power supply works too. These are all just some items to take into consideration.
yes I did. I have just finished a new CD card, exact image, per instructions.
debian@beaglebone:~/ardupilot$ git branch
* Copter-3.6
masterArducopter loads, (red light flashes) DSMX reveiver is bound to transmitter, signals visible on scope.
Qgroundcontrol does not complain that there's no receiver found, calibrating the radio fails though.
My service (I removed the $RANGER variable):
● arducopter.service - ArduCopter Service
Loaded: loaded (/lib/systemd/system/arducopter.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-09-12 12:14:22 UTC; 27min ago
Process: 797 ExecStartPre=/usr/bin/ardupilot/aphw (code=exited, status=0/SUCCESS)
Main PID: 805 (arducopter)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/arducopter.service
└─805 /usr/bin/ardupilot/arducopter -C /dev/ttyO1 -A udp:192.168.178.53:14550 -B /dev/ttyO2
Sep 12 12:14:22 beaglebone systemd[1]: Starting ArduCopter Service...
Sep 12 12:14:22 beaglebone systemd[1]: Started ArduCopter Service.my aphw file
debian@beaglebone:~$ cat /usr/bin/ardupilot/aphw
#!/bin/bash
# aphw
# ArduPilot hardware configuration.
/bin/echo 80 >/sys/class/gpio/export
/bin/echo out >/sys/class/gpio/gpio80/direction
/bin/echo 1 >/sys/class/gpio/gpio80/value
/bin/echo pruecapin_pu >/sys/devices/platform/ocp/ocp:P8_15_pinmux/statethe permissions
debian@beaglebone:~$ ls -l /usr/bin/ardupilot/
total 7412
-rwxr-xr-x 1 root root 890024 Sep 12 11:51 antennatracker
-rwxr-xr-x 1 root root 257 Sep 12 09:36 aphw
-rwxr-xr-x 1 root root 1461016 Sep 12 11:51 arducopter
-rwxr-xr-x 1 root root 1434284 Sep 12 11:51 arducopter-heli
-rwxr-xr-x 1 root root 1416180 Sep 12 11:51 arduplane
-rwxr-xr-x 1 root root 1181896 Sep 12 11:51 ardurover
-rwxr-xr-x 1 root root 1189688 Sep 12 11:51 ardusub
thanks @silver2row @awright424 @patrickpoirier51 for taking the time. I appreciate that.
debian@beaglebone:~$ uname -a
Linux beaglebone 4.19.71-bone-rt-r38 #1stretch PREEMPT RT Sat Sep 7 10:05:07 UTC 2019 armv7l GNU/Linux
can it be a protocol thing? like my dsmx receiver can't talk with Ardupilot?
i have also used orangerx receivers
sudo systemctl stop arducopter.service
done, and all stopped ok
sudo ./arducopter -C udp:192.168.7.1:14550
Does it starts ?
debian@beaglebone:~$ sudo /usr/bin/ardupilot/arducopter -C udp:192.168.178.80:14550
DataFlash_File: buffer size=16384
� Q}�� Q��� Q� Init GyroMPU: temp reset IMU[0] 8343 0
*� QC^**
Ready to FLY � Q���3�EKF2 IMU0 initial yaw alignment complete��� Q_�3�EKF2 IMU0 tilt alignment completeB�� Q�� Q���
Q�C�
o�r4T#��
QH3� Qv��Q�Q��� Q��� QE�� Q{z� Q�� Qt�3�PreArm: Throttle below Failsafe�Z�3�PreArm: 3D Accel calibration needed7�3�PreArm: Compass not calibratedR\�3�PreArm: Compass not calibrated�3�PreArm: RC Roll not configured���3�PreArm: RC Pitch not configured/;�3�PreArm: RC Throttle not configured�&�3 �PreArm: RC Yaw not configured�/� Q��� oY�f��H� QK� Q��� !Q-�� "Q � #Q�w� $Q~� %Q�y� &Q��� 'Q@�� (Q��)o������� *Qp�� +Q��� ,Q �� -Q��� .Q��/Q#k� 0Q"� 1Q�\� 2Q��� 3
the gibberish looks to be the mavlink data
Actually you could read it with FTDI and RealTerm
I'll be back in 15 mins