This section contains information about peripherals for connecting Pixhawk (PX4) to a companion computer, and peripherals that might be connected to such a companion computer (and potentially triggered/accessed by PX4).
Typical companion computer work with Pixhawk requires a companion link to transmit/receive the data between the companion computer and Pixhawk hardware (e.g. Intel NUC and Pixhawk 4).
There are a few devices that allow this communication bridge such as FTDI USB breakouts and level shifters (see below).
PX4 configuration for communicating with a companion computer over MAVLink configuration is covered in MAVLink (OSD / Telemetry). Relevant topics/sections in the developer guide include: Companion Computer for Pixhawk Series, Robotics and RTPS/ROS2 Interface: PX4-FastRTPS Bridge.
The FTDI USB adapters are the most common way of communicating between companion computer and Pixhawk. They are usually plug and play as long as the IO of the adapter is set to 3.3v. In order to utilize the full capability/reliability of the serial link offered on the Pixhawk hardware, flow control is recommended.
|Device||3.3v IO (Default)||Flow Control||Tx/Rx LEDs||JST-GH|
|PixDev FTDI JST-GH Breakout||Yes||Yes||Yes||Yes|
|mRo USB FTDI Serial to JST-GH (Basic)||Capable||Capable||No||Yes|
|SparkFun FTDI Basic Breakout||Yes||No||Yes||No|
On occasion a companion computer may expose hardware level IO that is often run at 1.8v or 5v, while the Pixhawk hardware operates at 3.3v IO. In order to resolve this, a level shifter can be implemented to safely convert the transmitting/receiving signal voltage.
- SparkFun Logic Level Converter - Bi-Directional
- 4-channel I2C-safe Bi-directional Logic Level Converter - BSS138
Cameras are among the most common form of data collection on a drone whether it be hobbyist, educational, or industrial use.
Stereo cameras are typically used for depth perception, path planning and SLAM. They are in no way guaranteed to be plug and play with your companion computer.
An LTE USB module can be attached to a companion computer and used to route MAVLink traffic between the flight controller and the Internet.
There is no "standard method" for a ground station and companion to connect over the Internet. Generally you can't connect them directly because neither of them will have a public/static IP on the Internet.
Typically your router (or the mobile network) has a public IP address, and your GCS computer/vehicle are on a local network. The router uses network address translation (NAT) to map outgoing requests from your local network to the Internet, and can use the map to route the responses back to requesting system. However NAT has no way to know where to direct the traffic from an arbitrary external system, so there is no way to initiate a connection to a GCS or vehicle running in the local network.
A common approach is to set up a virtual private network between the companion and GCS computer (i.e. install a VPN system like zerotier on both computers). The companion then uses mavlink-router to route traffic between the serial interface (flight controller) and GCS computer on the VPN network.
This method has the benefit that the GCS computer address can be static within the VPN, so the configuration of the mavlink router does not need to change over time. In addition, the communication link is secure because all VPN traffic is encrypted (MAVLink 2 itself does not support encryption).
You can also choose to route to the VPN broadcast address (i.e.
x.x.x.255:14550, where 'x' depends on the VPN system). This approach means that you do not need to know the IP address of the GCS computer, but may result in more traffic than desired (since packets are broadcast to every computer on the VPN network).
Some USB modules that are known to work include: