Coming back to the voxl i worked through the connect posts, most of it was helpful and I made a change or two so it made more sense or at least had better flow. I got hung up because I didn't change the wirreless access point on my computer to be connected to the voxl wifi, once I made that change I was connected to qgc again wireless. It is my objective to complete the final page for connect this week to get a openvpn setup with voxl talking through cellular to my workstation qgc. OR NOT!  Either way I have a complete configuration including radio and gps setup so I will complete a build and try to get a flight.  The new rooster 80 airframe is alot stiffer with duel slot mounts for the struts and blade guards.  

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.

Next issue was voxl was not connecting to the FC ver2. There are cable instructions (good luck), nothing worked

Had to connect to a different VOXL connector, connected to telemetry 1, made adjustment to .conf file and The Rooster Crows!

Connecting to the rooster by wifi  (make sure you have wifi connected with the computer) 

All systems look good except mavlink  so still reading   the inspect-mavlink didn't give good result

Hello

Traditionally MCBL-00007 plugs into J12 on VOXL. Only, if after the switch around, still no data shows up, then if it works in your situation, use J11. If you decide to go down this route, you will also need to change which uart gets used:On Voxl

vi /etc/modalai/voxl-mavlink-server.conf

Change "px4_uart_bus": 5, for J12 connection
To "px4_uart_bus": 12, for J11 connection

For question 2:

voxl-mavlink-server-r

^will give you a feed of mavlink to see the data running

Continued on connect4     This story gets better, I mean transmission happens

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