We haven't checked to see if the voxl2 is overheating. I'll run that script during our test when I get back into our lab later this week.

At what temperature does the board go into thermal shutdown?

One of my sentences was unfinished. The second paragraph should be this:

The issue that we are having is the following. We can start our software to log data and it will run fine for about a minute or two. After a minute or two the Voxl2 seems to become disconnected from the network. It no longer is receiving images from the camera, and cannot ping the camera or another ground control station (GCS) that is connected on the same network. Likewise the GCS cannot ping the Voxl2 but CAN ping the camera and is able to stream images from the camera to the GCS. The Voxl2 never seem to rejoin the network until we perform a power cycle. I'll note that we can access the Voxl2 using the USB-C port and adb and that the Voxl2 ip addresses (we assign it 2. One to be able to talk to the camera and one to talk to our GCS) remain unchanged so it seems like either the network services crashed or there is some sort of issue with the serial port.

We have the following problem. We are trying to run a MSCKF using the Voxl2 to perform our image processing and state estimation.

We have a Prosilica GT2460 as our camera which receives triggers from an IMU to generate the images at 10hz. The information from the camera is passed out over Ethernet, through an ethernet switch board, and is converted to USB by an Ethernet/USB3.0 adapter before connection to the USB/UART daughter board (MDK-M00125-1-00).

The issue that we are having is the following. We can start our software to log data and it will run fine for about a minute or two. After a minute or two the Voxl2 seems to become disconnected from the network. It no longer is receiving images from the camera, and cannot ping the camera or another ground control station (GCS) that is connected on the same network. Likewise the GCS cannot ping the Voxl2 but CAN ping the camera and is able to stream images from the camera to the GCS. The Voxl2 never seem to rejoin the network until we perform a power cycle. I'll note that we can access the Voxl2 using the USB-C port and adb and that the Voxl2 ip addresses (we assign it 2. One to be able to talk to the camera and one to talk to our GCS).

We have recreated the issue a few different ways but all of them involve using our camera and the associated software (Pleora SDK) to read the images being sent.

We are at a loss as to why running software would cause the Voxl2 to disconnect from the network or cause issues with its serial ports since data is entering the Voxl2 through USB.

Has anybody experience any similar issues or have any suggestions?

I apologize for the delay in responding. It seems like your suggestion seems to do what we want.

Unfortunately it seems that I am unable to shut down the network interface on eth0. I get an error when I try to set the MAC address that the resource is busy. Are there any subroutines or other services that would keep the interface from being shut down?

We put a license for the camera we are using on the Voxl2 board. The license is bound to the MAC address of the board (found using ifconfig on eth0). We ran into some other issues (not related to the camera) and opted to reinstall Linux. However, upon doing so we noticed that the MAC address has changed and as such the camera is not usable. Is there a way to set the MAC address back it's prior value so we don't need to purchase a new license?