Quantcast
Channel: ArduPilot Discourse - Latest topics
Viewing all articles
Browse latest Browse all 45727

RaspberryPi3 and APM2.6 via MAVProxy

$
0
0

@kungfrank wrote:

Hi everyone,

I'm newbie here.
I am following this guide: http://ardupilot.org/dev/docs/raspberry-pi-via-mavlink.html

i know Rpi3 has changed the uart access,following reply form @fnoop http://discuss.ardupilot.org/t/connecting-raspberry-pi-to-pixhawk/9784

Add this to /boot/config.txt:

enable_uart=1
dtoverlay=pi3-disable-bt

then I got result below:

root@pi-desktop:~# mavproxy.py --master=/dev/ttyAMA0 --baudrate 57600 --aircraft MyCopter
WARNING: You should uninstall ModemManager as it conflicts with APM and Pixhawk
Connect /dev/ttyAMA0 source_system=255
Failed to connect to /dev/ttyAMA0 : [Errno 2] could not open port /dev/ttyAMA0: [Errno 2] No such file or directory: '/dev/ttyAMA0'

and

root@pi-desktop:~# mavproxy.py --master=/dev/ttyS0 --baudrate 57600 --aircraft MyCopter
WARNING: You should uninstall ModemManager as it conflicts with APM and Pixhawk
Connect /dev/ttyS0 source_system=255
Failed to connect to /dev/ttyS0 : Could not configure port: (5, 'Input/output error')

On the other hand, I also try this guide

In /boot/config.txt, add the line

core_freq=250.

Save and reboot.

I got result:

root@pi-desktop:~# mavproxy.py --master=/dev/ttyAMA0 --baudrate 57600 --aircraft MyCopter
WARNING: You should uninstall ModemManager as it conflicts with APM and Pixhawk
Connect /dev/ttyAMA0 source_system=255
no script MyCopter/mavinit.scr
Log Directory: MyCopter/logs/2017-05-10/flight6
Telemetry log: MyCopter/logs/2017-05-10/flight6/flight.tlog
MAV> param show ARMING_CHECK
MAV>

I am not getting any communication between the two.

and

root@pi-desktop:~# mavproxy.py --master=/dev/ttyS0 --baudrate 57600 --aircraft MyCopter
WARNING: You should uninstall ModemManager as it conflicts with APM and Pixhawk
Connect /dev/ttyS0 source_system=255
Failed to connect to /dev/ttyS0 : [Errno 2] could not open port /dev/ttyS0: [Errno 2] No such file or directory: '/dev/ttyS0'

They are both totally contrary to the result normally should be !!

The problem confuse me all day. Is there any configuration I might missed?

I use Ubuntu Mate: 16.04 on rpi3

Posts: 3

Participants: 2

Read full topic


Viewing all articles
Browse latest Browse all 45727

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>