I am currently trying to connect my navio/raspberry to the Mission Planner. I have followed every tutorial step up to the command:
sudo systemctl start arducopter
Still, I keep receiving the message from Mission Planner saying that it is connecting to Mavlink, and yet it never does.
I’m trying udp communication, using the IP address from my laptop:
Could you please post the output of emlidtool before sudo systemctl start arducopter, the content of /etc/default/arducopter and sudo journalctl -u arducopter after launching arducopter?
I know one is not supposed to repost the same topic, but I haven’t gotten a reply in about two weeks and got a little desperate haha
the original problem is stated here: Connecting to Mission Planner
i moved your post to the existing topic, because it is easier to follow;
could you start ardupilot with
sudo systemctl start arducopter
and then post an output of
sudo journalctl -xn?
and copy the red messages from
sudo journalctl
to a post (or whole output)?
I did as you asked. The red message from ‘sudo journalctl -xn’ states:
“navio systemd[1]: Failed to start Arducopter for Linux”
The whole output is:
~
~
~
~
~
~
~
~
~
~
lines 1-28/28 (END)
– Logs begin at Thu 2017-04-20 06:16:31 UTC, end at Thu 2017-04-20 06:32:57 UTC. –
Apr 20 06:32:18 navio systemd[1]: arducopter.service: main process exited, code=exited, status=1/FAILURE
Apr 20 06:32:18 navio systemd[1]: Unit arducopter.service entered failed state.
Apr 20 06:32:19 navio systemd[1]: arducopter.service holdoff time over, scheduling restart.
Apr 20 06:32:19 navio systemd[1]: Stopping ArduPilot for Linux…
– Subject: Unit arducopter.service has begun shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page
– Unit arducopter.service has begun shutting down.
Apr 20 06:32:19 navio systemd[1]: Starting ArduPilot for Linux…
– Subject: Unit arducopter.service has begun with start-up
– Defined-By: systemd
– Support: systemd-devel Info Page
– Unit arducopter.service has begun starting up.
Apr 20 06:32:19 navio systemd[1]: arducopter.service start request repeated too quickly, refusing to start.
Apr 20 06:32:19 navio systemd[1]: Failed to start ArduPilot for Linux.
– Subject: Unit arducopter.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page
– Unit arducopter.service has failed.
– The result is failed.
Apr 20 06:32:19 navio systemd[1]: Unit arducopter.service entered failed state.
Apr 20 06:32:57 navio sudo[17259]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xn
Apr 20 06:32:57 navio sudo[17259]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
~
~
~
~
open the config file for arducopter: sudo nano /etc/default/arducopter
remove -A from the line ARDUPILOT_OPTS=… so it looks like:
ARDUPILOT_OPTS="$TELEM1 $TELEM2"
This worked just fine, I’m now connected to Mission Planner =)
Thank you for the attention! I realize it was a stupid mistake haha
I do have a new question, though, when running “sudo emildtool”, all sensors return “passed”, with the exception of the barometer, which gives me:
ERROR ms5611: Failed
– Reason: Is barometer covered with a foam?
I do have a foam covering the barometer. It is a generic piece of yellow foam, but it does block illumination from reaching the sensor.
my beste guesses:
disconnect anything from i2c
use open cell foam to let the air pass through and block the “superbad” uv radiation which severely affects barometer values;
dont glue/stick adhesive completely over the barometer - basically only the foam without glue should cover the baro - put the glue/adhesive beside the baro