Seth here. Hello…I see what you typed out MagicRuB. My Mission Planner software does not connect. Obviously, esp. since I am new, I am missing something that should have been read beforehand.
Assuming you have successfully logged into the Beaglebone Blue and installed Arducopter, make sure you know the IP address of your computer from the Beaglebone, as well as the address the other way around. Use ping to check it.
Then you need to run Arducopter on the Beaglebone with a parameter of -C udp:x.x.x.x:14550 where x is the IP address of your ground station from the beaglebone. Then run mission planner and set it to UDP mode and it should find ArduCopter.
On mine it is a simple case of sudo ./arducopter -C udp:192.168.7.1:14550
It is easy to accidentally get the ports wrong and send the MAVlink messages to the wrong IP. If you see a wall of random text in the beaglebone console then ardupilot hasn’t accepted the parameter and is dumping MAVlink messages here instead.
Seth here, again. Hello once more. I will test out the BBBlue w/out purchasing the extra hardware for now. @SuzL, thank you for replying so quickly. I am still new and trying to find a foothold currently w/ this Linux board.
I will listen to your commands.
Seth
P.S. I will find out how to search for ports. My com Port was 9 and now it does not accept the com port 9. See here:
This is Seth. Um, should I install Arducopter on my BBBlue or on my Linux Desktop or both?
Seth
P.S. If you would, when you have time, please send over a hyperlink of a viable tutorial. I have tried the qmake version for Ubuntu but I have not gotten very far w/ progress.
I am compiling now. The ArduPilot software is on the BBBlue and I am making headway. Thank you for your support. @ppoirier, the mirkix/BBBMINI site from GitHub.com has worked out. I am pretty sure of it.
Hello again sir…I tried that command. I was unsuccessful w/ that command. I was going to use a “config-pin” utility to promote my spidev2.0 and spidev2.1 usage.
Seth
P.S. I had compiled and made the BBBMini work for the board but not w/ the BBBlue yet.
Here are more photos of my concerns: @SuzL and @MagicRuB.
I cannot connect yet. I have compiled the --board=blue for ardupilot. I have tried ping via the cmd line in a terminal and I even tried to connect by going to /usr/bin/ardupilot and using the cmd, chmod a+x blue-arducopter, I thought things would connect from your ideas SuzL.
I then went away from that directory and used the cmd, sudo ./blue-ardupilot, to run the system on my BBBlue.
I received some odd text as feedback. Please see the photos below.
As you all know, I became very excited to see things, esp. from your end of things, in a space where the BBBlue could support the MavLink and Mission Planner software. In haste, I asked away w/out thinking of your time and how long you have been exercising your right to perform with ArduPilot.
The sudo should not be necessary, and is a hint that something earlier
in your command sequence might have gone awry. However, it’s working for
you, so carry on
I see you were right. I actually had to perform the cmd in the directory to suit my needs but I will keep find tuning things until I can use it w/out sudo as a cmd.
Oh stating the obvious perhaps, but you need to run ardupilot with a parameter -A or -C and the output port to connect to a groundstation, otherwise it will just merrily work on the bbb and print the mavlink messages to the console (perhaps what you are seeing)
Hello…I got the ground station to connect. I am waiting on some parts now but I soon plan to apply the hardware and test things out. I will reply back here.
Seth
P.S. I was seeing MavLink dumps on the terminal on the BBBlue but it seems I was still connected, i.e. at least it showed on ArduPilot that I was connected w/out issues.
