Our 80% ver1 using a US Manufactured flight computer that incorperates cutting edge components including operating in GPS denied enviroments. 

Basic design planning:

First lets talk about the design and requirements. This is a completely design as you go process, By this I mean I established some basic parameters, designed then made changes until we got to a product that met our wants. 

1. Be able to carry large 6s batteries and have room for internal payloads. This is the reason for the fatbody. Learning as we go the current build uses 1 6s battery and the 80% scale uses 1 4s with lost of room to spare. As battery tek changes we will be able to configure our battery pod to accept different sizes and shapes

2 Has to be able to be 3d printed

3 needs to be flexable for controller and payload

4  Has to be available for as an open source project to allow for community builds and mods. This being a controlled enviroment so all mods and changes can be shared but files controlled by Daytona Drone Club 

Updates and improvments are required with any development. Our inhouse 3d printed drone is no exception But we believe we are at a point to release some files for others to evaluate. Our first build is full size but the 80% build is in process also.

pay attention to the bottom left corner cause that is where you identify the mode

i   just hitting i puts you in editing mode, you will see the i in the left bottom corner and will be able to change text, then esc to exit this mode

then shift colon to be able to WQ to save and quit.  This is why linux sucks it's real stupid

VOXL’s ARM applications processor and Hexagon SDSP

To prevent system partition flash corruption:
                   run poweroff before removing power:                $ poweroff -f

Use the /data partition for file storage

To see a list of MPA utilities available, adb | | or ssh into VOXL and type voxl{TAB}{TAB}

 https://hub.docker.com/r/kylemanna/openvpn/

I have included a post between tec support for a review so a general image can be formed on some things that are happening.  Then it goes into setting up VPN and docker so the objective is to get a feel of the termenolgy and verbage

research on tech posts 

 This is the top of the auto-generated .opvn file created by my OpenVPN server running on a Pi. I've generated 4 separate files, and used them on 2 different laptops tethered to phones (thus not on my local network at all) and the two phones themselves and those 4 devices connect flawlessly.

I have placed this voxl.ovpn file in /etc/openvpn/
When I execute openvpn with the file as the argument, I get this:

I have placed this voxl.ovpn file in /etc/openvpn/
When I execute openvpn with the file as the argument, I get this:
I briefly looked at your server link and it looks like it's set up not to require a password for the public key, which is required by my server when creating the user and generating the .ovpn. Is this the issue? When using the Windows and Android OpenVPN GUI clients, they prompt me for the password I created to go with the file. I don't get that far on the Voxl command line. Is there something about the OpenVPN installation on the Voxl that won't let it do the initial TLS handshake for the password? Like I said this stuff works like butter on two laptops and two phones...

• It looks as though your key is using a param that isn't available in the version installed on VOXL by default (tls-version-min 1.2). You could try removing this line from the key.

  You could also try building a newer version of OpenVPN via. the instructions at the bottom of this page: https://docs.modalai.com/voxl-vpn/#openvpn-client-on-voxl

   

  ---

  
  

   Well... I lied. I actually did spend most of the day on it again, but I learned a lot so it's ok. I have been 90% successfull in my efforts, with most of the success attibuted to .. Uh.. Following the instructions? LOL! I compiled the 2.5.1 version of OpenVPN on the Voxl. It connected to my server after properly prompting me for the password. I have full use of my subnet from the Voxl through the VPN. I can connect the Voxl to QGC on any machine (IP) on my network that I point the Voxl to. I need two things from you: Using this line does not keep it running as a daemon after I exit the shell: "openvpn --daemon --script-security 2 --config voxl.ovpn" As soon as I exit adb it drops the link. I need to make it persistent. Secondly, I need to know how to make the system clock setting utility persistent as well. Thanks!

Where: used mostly for communication between a Ground Control Station (GCS) and Unmanned vehicles, and in the inter-communication of the subsystem of the vehicle. It can be used to transmit the orientation of the vehicle, its GPS location and speed

This is where the instructions are  https://docs.emlid.com/navio2/

first you have to log into the controller  ssh pi@navio.local
password is raspberry pi

This setup allows both arduinopilot and PX4. If I were a normal person I would continue to use pX4 following the intense setup issues with the voxl but I chose the Arduinopilot route, why I don't know

As with the previous build (voxl) connection to the Qgroundcontrol is elusive, that is it's not working as a simple setup. 

notes 

man systemctl

Next 

verify the remote radio and tbs nano still communicates and figure out why qground control doesnt connect via wifi

That was where I ended, not able to configure qground control

(voxl instructions  Forum)
use the  voxl-vision-px4 service to facilitate the connection between PX4 and QGroundControl. If the service has been configured already, there will be a configuration file at /etc/modalai/voxl-vision-px4.conf  You’ll want to edit this file and set the field to the qgc_ip  IP address located in the previous step.

Connections between VOXL and qGroundControl can be configured either by informing voxl-vision-px4 of QGC’s IP address, or visa-versa. UDP connections can also be made locally on VOXL allowing services like MAVROS and MAVSDK to run on VOXL alongside voxl-vision-px4 and still communicate with the PX4 autopilot.

WTF  UDP connections?

What is the User Datagram Protocol (UDP/IP)?

The User Datagram Protocol, or UDP, is a communication protocol used across the Internet for especially time-sensitive transmissions . It speeds up communications by not formally establishing a connection before data is transferred. This allows data to be transferred very quickly, but it can also cause packets to become lost in transitHow does UDP work?

Like all networking protocols, UDP is a standardized method for transferring data between two computers in a network. Compared to other protocols, UDP accomplishes this process in a simple fashion: it sends packets (units of data transmission) directly to a target computer, without establishing a connection first, indicating the order of said packets, or checking whether they arrived as intended. (UDP packets are referred to as ‘datagrams’.)

UDP is faster but less reliable than TCP, another common transport protocol. In a TCP communication, the two computers begin by establishing a connection via an automated process called a ‘handshake.’ Only once this handshake has been completed will one computer actually transfer data packets to the other.

UDP communications do not go through this process. Instead, one computer can simply begin sending data to the other:

system-image: 4.0.0
kernel: #1 SMP PREEMPT Thu Oct 13 17:57:05 UTC 2022 3.18.71-perf
--------------------------------------------------------------------------------
hw version: VOXL
--------------------------------------------------------------------------------
voxl-suite: 0.9.4
--------------------------------------------------------------------------------

That being said we are trying to make the voxl the engine of our student drone build. Made In America is our objective and if we can provide some instruction to get working drones then we can proceed in development of custom software applications and develop some very useful tools for industry

There are several ways to connect to the flight core, the VOXL, and the wireless modem.  It gets confusing and frustrating because there is no roadmap and no forums that walk you throught it. 

First you have to have their flavor of Linux installed, then connect to the voxl through the usb and power it. This will allow a communication link. There is also connecting through wifi and tah setup is included in the disaster of instructions and help files. This powerful computer has a firehose of information forced down your throught when trying to get the basics. There is no simple single instruction and there several different configurations. You get started with one then the instructrions divert to a completely different path.  

So hopefully I will be able to document this process I am doing. This is my second attemp, my first was a disaster, learning linux then docker, then tryiong to VPN to qground control with the cell modem. 

So here goes

1. Dont think your stupid, the manuals and methods provided by Modalai are!

2. Even when you succeed getting the VOXL configured your not going to be impressed. The software and the results are really bad, bad to the point I believe they make excuses like develop your own we provide the hardware. I was successful getting the images to the program but never able to get the cell modem to ground control

3. My objective first is to get the modem and VPN gateway figured out, if thats possible maybe the voxl2 will have better user applications or at least not suck as bad, that is If I go that route, I am always looking for newer and better hardware and this setup is a total shit show unless you have months of time and a very high IQ. 

Update 1-29    To say this is confusing and lack of instructions would be a understatement. I'm digging into the VPN using openvpn. The voxl instructions say they are using cloud vpn and not a local server, I believe I had this setup working before with the ubuntu linux openvpn access server and had it showing 2 devices connected. 
         -The point here is this is a complex study, understanding the Openvpn setup and configuring the modem is a free for all. There are no step by step instructions and when there is an issue it gets really complicated. I contine this mission later in this post identifing the modem and links to locations for help and understanding. It's not coming from modalai thats for sure