In case anyone else has this issue, in my server under Tunnel settings, the Redirect Ipv4 Gateway selected. Dont do that. I am getting the routes pushed to the device, and the the device is communicating with QGroundControl with 6% packet loss.

I have been trying different profiles, etc to trying to get more detail on this issue. I have used the drone profile on windows machines, and I am able to connect and ping; so I dont think its a firewall issue. I am using oepnvpn client 2.4.6; the openvpn server is 2.4.9

Is anyone else using the 2.4.6 client with success? Before the system bricked, I was successfully connecting and using the drone... I am unsure which penclient version I was using ... I am scratching my head as to why the udp packets are not gettting to the QGroundControl PC box. I did a tcpdump and the drone is sending packets to the QGroundcontrol, but I see no blocks on the firewall, nor do i see any passed packets. I am reaching...

I switched to a NUC, and I have everything up and running now. Appreciate the patience, I was a bit confused on the voxl platform version; bc I have v2 LTE modem. I found that ATT sim cards are not the best choice for the platform - customer service at ATT couldnt explain why the Sierra Wireless modem was getting rejected from there HLR during registration. I switched to a GoogleFi sim card (data only) and no problem registering. I am planning on taking the drone out of the country, and switching the modem to EMEA with the same sim card, fingers crossed.

I have openvpn setup on the drone, the corp server, and my laptop establishing 2 vpn clients. Drone has 10.0.0.10 ip; windows laptop has 10.0.0.5 with QGroundcontrol, the Openvpn server has interclient communication ticked, though I am not able to see each device through the vpn and I obviously fly the device. in voxl-vision-px4 configure the qgcip is set to null, the secondary is also set null. In QGcountrol I have the communication links setup to accept 10.0.0.10.

Any suggestions on getting the devices connected?

Thanks. I have setup a pi, installed all the android-* packages, and have successfully got the system to the point where fastboot device shows the device id. The install.sh -f downloads and looks to install the system image. The system states it will be reboot in 2 seconds, it reboots and it cant get find the adb server to connect and finish the reboot. I have a tail on the syslog; it looks like it needs to wait several seconds a bit more, when it reboots the voxl device does not register as a usb device until some time later. I traced and went into the shell scripts flash_ build*sh and increased the time to sleep. It still seems to fail after the isntall.sh -f reboot. Is there any other procedure I can use to get this back to a state where I can use the system in the way intended?

Thanks!

Hi, I received the debug board today, I removed the LTE board and added the debug board on per the video. I am reading the Flash system Image document, It seems like I need to perform this flash off a linux box. The Flash ssystem doc says to download the latest image from the asset directory. I am in the asset directory; though I am unclear as to which image to download. The directions say to run voxl-version to find my version, though unfortunately my system is bricked; and I dont know which version I have. Note: I purchased this drone from a vendor who built the software, and the drone as a turn key system. Is there a way I can determine this by looking at the board?

@Chad-Sweet Thanks. It looks like I need a usb and serial dev board to complete this process? It looks from the video, they connect to a linux box, and operate from the linux command line w/o docker?

Hi, First off I apologize for yet, again a question on the ADB connection issue. I have read through the various posts referencing the ADB offline issue. I see that the issue could be because of power supply, or corruption of the system. I am a relative noob to VOXL and docker. I generally work on systems that are closer to the silicon. I have successfully added openvpn to connect to GC via LTE; and I modified voxl-vision-px4 configuration parm qgc_ip to null, allowing the aircraft to connect to any QGC in my vpn. After I made that change I lost the connection over ADB and have never got it back. It looks like nothing is "booting". Its just stuck. I was using windows. I am more proficient in linux. Though, my noob"ness" makes me a bit nervous reflashing the system in windows. Is there a step by step process for windows? Or will I have to set it up in a linux (pi-ubuntu 20) environment?

Any advice,help is greatly appreciated! Thank You in advance!

@tom Tom, Thanks for the help. The connection issue was definitively the VPN key. I used the same keys with different login credentials. I created a new user cert, and new profile, associated those 2 together downloaded the ovpn and create a separate instance of the vpn session. No problem connecting with the vehicle, though it says thats its at 60% loss. I have a goo connection with ATT at -90 RSRP, low SNR.

The flickering lights appear to be from a bad battery. I change batteries when I went into the office, and all was better.

Also, the ability to push the signals from the modem to a server via wget works well. I believe that was symptom of the vpn key issue.

Now, I just need to figure out how to compile a c program to use the voxl-inspect-gps program to pull real time off the gps pipe. Is there a concise document you can point me to? Will I need to compile on a ubuntu system then push it over to the vehicle? Thats fine, I am use to that..

@tom It may have done the trick. I had QGC running in the background with the vehicle on, connected to the vpn. When I changed the keys; the vehicle's led 1 changed from solid green to flashing green, then to flashing red. I googled around for the led flash pattern, bc it never seems good when a system flashes red - I haven't found what flash red mean yet, though i ran across a mention where flashing green means firmware upgrade? I suspect the red means the flash of the firmware failed. I can't get back into the system via adb or any method so far. If, in fact the flashing red light mean error with the firmware can you point me to the correct docs to reload the firmware and get my system back to the previous state? I feel that the key issue was the culprit.

thank you!

@tom Thanks for the tips. I'll verify the key issue with openvpn. That didnt occur to me. They are both using the same key. I do have several machines with Ubuntu on them. I'll try that next. Thanks!

w/r/t voxl-vision-px4 running and attempting to run a shell script after openvpn connects much less pinging a server on the vpn; -- should the voxl system experience such a large load making those operations fail?