Hello, i am having trouble using my no-ip name instead of ip address when launching arducopter software.
I can connect telemetry trough LTE no problem if i launch the software with the correct ip address, but launching it with the no-ip name like mynavio.no-ip.net doesn’t work.
No-ip is correctly configured and other applications can use the name mynavio.no-ip.net and correctly resolve the name.
Thanks for your answer, but since Gstreamer starts with no prob and can resolve my GCS ip, i was hoping in something a bit easier than running a proxies.
Everything works as it should now over LTE network, i just have to fix that little thing so that i don’t have to edit the local.rc everytime my ADSL IP changes.
As said, Gstreamer works so i hope there was a little trick to add to the string that launches Arducopter application in local.rc
mavproxy is a program that runs on your rpi and passes mavlink protocol to your DDNS target! You can also run it on Startup ( etc/rc.local ) together with ArduXXX (-Copter);
after installation:
ok it seems like it doesn’t start in rc.local (not even with --daemon); not sure right now I’look into it the next days;
But you can do it another way i just tested:
make a file:
sudo nano mavproxy.sh
write in the file:
#!/bin/bash
sudo mavproxy.py --master=udp:127.0.0.1:14550 --out=udp:XXX.noip.com:14550 --nodtr
CTRL-X and Y to save
make executable:
sudo chmod -x mavproxy.sh
make a cronjob on boot:
sudo crontab -e
write in the last row: @reboot sudo sh /home/pi/mavproxy.sh (!!! edited this line at 19:18)
CTRL-X and Y to save
keep the Arducopter line in rc.local with localhost IP as described before (udp:127.0.0.1:14550)
but remove the mavproxy line in rc.local! (or just put a # at the beginning of the line to comment it out!)
reboot and it should work!
make sure you are logged in as user pi;
check if the file exists in /home/pi/:
cd /home/pi
dir
check if “mavproxy.sh” is listed below the command “dir”
open mavproxy.sh:
sudo nano mavproxy.sh
add --daemon to the command:
sudo mavproxy.py --master=udp:127.0.0.1:14550 --out=udp:YOURDDNSIP:14550 --nodtr --daemon
*reboot and check if works
IF that doesn’t work:
open crontab:
sudo crontab -e
remove the line @reboot sudo sh /home/pi/mavproxy.sh
add the command instead: @reboot sudo mavproxy.py --master=udp:127.0.0.1:14550 --out=udp:yourDDNSIP:14550 --nodtr --daemon
i remember i had these “slowness” issues when multiple mavproxy instances were running or i had a lot of “–out” parameters;
→ recheck if you removed the mavproxy line from /etc/rc.local
→ if you use the mavproxy.sh file - make sure crontab didin’t start mavproxy parallel;
recheck if you have any typos in rc.local (with ArduCopter) and crontab (with mavproxy)
just tried (though over wifi) mavproxy it wasn’t noticeable slower than from ArduCopter