I was able to use the v1.13.2-0.1.1 file with mission planner, it connected but said update was not required. I will keep an eye out for the v1.13.2-0.1.2 drop. Looking into my compass setup, its a new release from MRO, could be an issue there

I have been having trouble calibrating my compass so I figured I would update the flightcore v2. Of course following the instructions using the ./Tools/px_uploader.px had a few erros and didn't run so my question is will there ever be a fix to update this using QGC? I tried mission planner and that only had the option for modalai flightcore ver1. My drone is ready to fly, I was hoping to update the Fc before I attempt this but then again I have reached my stress limit with this VOXL-Cam and will probably shelve it for a while. Funny it says using a simple python script, so far the lack of clarity and instruction has made it anything but simple. as for the developer guide I'll just hope it can be figured out how to update with qgc, then again I'm at the point where I dont think this setup will ever work

@Adrian-Hidalgo said in rx-tx from v2 to voxl:

px4_uart_bus": 12, for J11 connection

worked transmitting data now

changing to j11 and px4_uart_bus": 12, for J11 connection brought the voxl alive Looks like I can move on to the openvpn brain storm.

so far I have tried about 6 different configurations to get the FC v2 to talk with the voxl.
Just as a simple question
If I have the voxl connected to the computer via cable and the fc connected by wifi, logging in to ssh root@192.168.8.1
1.if I run voxl-vision-px4 --debug_udp_recv I get , connected tovoxl-mavlink-server but no messages from px4
2 if I go to qgc analyze tools there is a heartbeat (190 heartbeat 2.0Hz)
I am not able to connect to qgc unless I use the usb cable to FC v2
I have tried the FC v2 telem1 and telem2 and switched the rx/tx with no good result

Any direction that I should be looking would be helpful

@Bulldog357
I have over 30 days invested in this and still no luck. You can study the silly image provided for hours but the openvpn stuff is not available on either end. when you put together your instructions I would be very interested. At one point I had 2 devices and communication but that was 6 months ago. I gave up but started trying 3 weeks back only this time there is an openvpn cloud option not just the local server. The modalai referances cloud but then says server so I don't think they mean the openvpn cloud. I useally put 8 or 10 hours of brain into it then give up. Right now I cant get the new ver2 controller to talk to voxl. want to see some confusion look at the cable instructions and updating the firmware

Just an update. No communications on either telemetry port
I'm trying not to have to remove and disassemble the voxl-cam. I guess i will read on settings , it says no messages from px4

Hello
I followed the wire details for core v2 to voxl
There was some confusion because I didn't want to remove and disassemble the voxl-cam to see the wire and connection so I just used the ver1 detals and transposed them to ver2. I guess I could have mixed up tx to rx wires but before I switch them is there a way to see if they are talking. i did qground control mavlink inspector and voxl-vision-px4 --debug_udp_recv on voxl and got no messages from px4.
question: I have voxl plugged into J5 Telem2 STM32 UART5 (ttyS4) on ver2.

ver1 was the same
Interface Connector (TELEM2, /dev/ttyS4, UART5)

There should be no changes in any cong files correct?

question2 is there a quick check command to see if any info is coming from the voxl to the ver2

it's almost funny. I kinda expect what would sound like a simple update like firmware would turn into a couple hours of trying to understand what is being said. To update the firmware, please use the px_uploader tool. No using qground control would be to easy but instead it takes searching how to find and install the px_uploader and then it actually has to run. Probably better that I just shelve it and wait a month or two when cables are available instead of breaking it tryng to figure it out. was there a question No, just trying to convince myself that there will be some value in this at the end

How does this make any sense? You provide a couple sentences and a link to vpn providers.
Openvpn is a nightmare on their own besides trying to figure out how to setup and edit a config file on voxl. I have spent weeks and this is my second attempt at getting qground control to communicate with either the wifi or the 4g modem. You would think there would be better technical instructions in stead of vague and confusing little seeds of instruction like this. Pure jibberish
even after figuring out connecting to voxl what does (openvpn --daemon --script-security 2 --config vpn-key.ovpn) even mean?

This is the most important setup on the voxl modem and it goes nowhere

OpenVPN client on VOXL
The base VOXL System Image comes with OpenVPN pre-installed

In order to use OpenVPN on VOXL, you will need to supply a configuration file and the certificates / keys for your VPN. These files can be placed in the directory /etc/openvpn.

The following is an example of running OpenVPN as a daemon:

cd /etc/openvpn

openvpn --daemon --script-security 2 --config vpn-key.ovpn

NOTE: The connection to the VPN will fail unless the date and time have been correctly set. This is required due to the dates embedded in the certificates. voxl-time-sync (included in voxl-utils) is a script that will run until the date and time have been set correctly and can be enabled to start on boot.

Qground control is just as bad. how about some steps that accomplish something.
I have invested several months with this voxl cam and would even consider moving into the voxl2 if there was someone who speaks english and can write a technical article that completes the process without diverting into several different configurations.
You can't just leave people hanging or is that the objective. Frustrate users with massive technical overload so they give up.