@ryan-langlois1 We found it the voxl-static-ip service and have it working. This can be closed. Was also for VOXL2

We're using the static IP service to set our static IP (voxl-startic-ip). As well, we "stop" and "disable" the dhcpcd service. However, we're seeing the VOXL2 randomly switch back to it's 169.xxx.xxx.xxx (I don't remember specifically) default IP address when we're running our autonomy. It doesn't happen every time, but it happens at random on random vehicles (we have 10 vehicles all on a running at once). We have been unable to replicate the issue.

@Eric-Katzfey 232. I'm not terribly worried about it. I've worked with their VN-100 series before, which we might go with. A logic shifter should work fine. So maybe we open another UART? Our custom daughter board connects to J3 and J5 so we can get more than 1 UART even though we're currently only using UART7? from the J3.

@modaltb thanks for the info, but we already have our UART configuration working. See my response to Eric Katzfey for explanation. We're about to start doing some gps-denied research in-which we expect to have gps, and then have gps get jammed. We'll need a better IMU than the mems on pixhawk and VOXL2.

For what it's worth, we're starting small here. GPS-denied SLAM is not our wheelhouse. We develop fully autonomous "plays" and swarming algorithms on fixed-wing UAS.

@Eric-Katzfey We're using a daughter board; yours (the 3.0 with UART & USB) and we have a custom one that essentially does the same as yours, but we're converting USB to ethernet on-board. This eliminates our need for a fat external USB to eth converter. As for external IMU, we're considering a vectornav VN200. We currently fly that same unit on a different airframe. We are also considering using the ones onboard the VOXL2, but I'm assuming it's a low cost "hobby-grade" mems? I believe it's the icm-42688 so I'm looking at it online and comparing to the vectornav units.

We're looking to pull in GPS and IMU data into the VOXL2. We are not using the DSP. We are using an external flight controller with the VOXL2 as a standalone SBC for our autonomy. We want to use an external IMU and Compass to improve our state estimation. What would be your recommendations on doing this?

@Vinny It's all good. They work fine with soldering. It's more of a pain getting the headers off than anything else. We do stuff like that all the time. I've done 6 or 7 of them already.

Turn the fan header 90 degree. It's in the way of the mount hole. I've had to de-solder the header and solder our fans directly to the board.

Is there currently any research being done on this or are you guys sticking with px4 on the VOXL2 DSP?

Hello, we'd like to clone our system image and copy to our other VOXL2 units. We imagine this is possible. Can you point us in the right direction?

We built our own "daughter board" that stacks on J3 breaking out UART and USB. We are using a smsc Lan9514 converter which VOXL is seeing, but not functioning due to the absence of the driver. We can pull the source code for the driver, but can't get it to build. It seems the build file is pointing at the kernel where the headers are missing. Can you help fix this? I think in 1.2.2 you guys had support for the lan chip but that kernel or the drivers don't appear to be available to us.