Could you clarify use of the server software vs the apsync image? As I understand, either one is used for FC/companion communication and telemetry downloads? Is it because the former offers communication via the internet?
A flight operation could then involve use of the WiFi link, the SIK radio link for GCS communication and the TX transmitter for flight control? So three comm protocols are simultaneously occurring? Which of the three is used to monitor data downloading? For example, from sensors that I would like to connect to a companion board? I want to fly to WPs, measure a physical parameter, then time/GPS stamp it.
Sorry for all the questions - again the help is very much appreciated.
Mavproxy provided MAV>, but as before I got “link 1 down”.
Curiously, when I later rebooted, it would constantly crash after the end of the boot sequence. So I reflashed the image and it was ok. But still getting “link 1 down”.
If I tried to reboot the “Flight Board”, nothing happened. Looking at System Status, I’m not seeing data.
I supose I might conclude there is something wrong in the hardwiring between boards, but I have confirmed the continuity of the cable and the proper RPi GPIOs are used.
Not sure what the next step would be other than to try other boards.
This looks great. I sadly have a Pix Cube with Intel Edison carrier board and Intel Edison that does not seem worth pursuing – I got it used but APSync seems like abandonware. When I get a chance I will slap a Pixracer on a RPi3.
That would mean your Wifi connection is cutting out. I’m not sure why.
The Wifi range would be the limiting factor. From what I recall the Pi’s Wifi range isn’t brilliant. The exact range would depend on the Pi’s mounting in the vehicle and any potential interference from other devices. You’d need to measure it yourself for an accurate number.
All of it. Apsync will talk with any controller that runs Ardupilot.
I wrote Rpanion-server, so I’m probably a bit biased Rpanion-server is designed to be easier to use and install, but it’s quite new software so there may still be a few bugs in it.
I have my RPI zero w connected to my pixhawk 4 mini telem port and get the same error as the original post.
I only connected the tx & rx of my pi. The pi it’s powered on USB. Is GND necessary for a stable connection?
Is there anyone working on Pixhawk with Jetson Xavier NX. I have the issue that the command mavproxy.py --master=/dev/tthTHS0 --out=udp:192.168.0.119:14550 --cmd='set shownoise 0'
works sometimes, while sometimes not. Moreover, even when it does, it only works for a few min , then showing "link 1 down’ as the pic show below.
While I’m connecting the Jetson Xavier NX to Pixhawk Cube with arducopter v3.6.11 via TX RX GND to pixhawk cube telem2
Does anyone have any idea about this?
Dear ardupilot community, we are two German computer scientist guys working on a bachelor thesis for programming a drone to fly automatically through a room while measuring it. We found the following tutorial using a raspberry pi, the navio2 hat and the ardupilot software including mavlink. (Integration of ArduPilot and VIO tracking camera (Part 4): non-ROS bridge to MAVLink in Python) Unfortunately we are not able to make the raspberry pi communicate with the navio2 board via the serial0 / ttyS0 connection, although the system is correctly up and running. We always get the error “MAV link1 down” and no connection is established. As you can see from our shell, all components seem to be quite updated and running correctly. Do you have any idea what we can try next to make it working? Any help is very appreciated! Thanks in advance and regards from Germany! Stay healthy.