@Vinny Thanks Vinny! Just trying to maximize the versitility of my investments! Same way you guys do when you use the same board for both products! I'll leave it alone...

@tom Tom, Thanks for the Saturday reply! I' know I won't be able to ping the device's IP from the internet, just like I can't ping my phone or any other cellular device. They're inside the carrier's NAT'd subnet. I get that. But I cannot ping any public ip FROM the device. At the end of that old thread, he shows the Voxl pinging 8.8.8.8 and getting a response. I still don't, after following all of the suggestions in that thread. Like I said, I can get a DNS response if I ping a hostname, just no response to the ICMP from the host. Things that might help me: Another SIM from a different carrier or (or carrier's reseller, as most of the IoT SIM providers tout using ATT, T-Mobile and Verizon's networks, but have their own APN's..) to try. I'm working on that. In the meantime, coming from my early beginnings jockeying Hayes modems from DOS 3.3 running a BBS (Bulletin Board System, the pre-internet way we communicated..) I'm familiar with the Hayes AT command set (or used to be..) so I'd like a document (that I can't find on the Sierra site) listing my modem's AT command set so I can dig deeper into this problem myself. The Tailscale VPN looks nice and may be the simplest route (at a cost, and once I can actually talk to the outside world with this thing..) but I'm linking to a good video for you guys to look at. This guy is pretty savvy, and what he's doing here works. Without a VPN I might add.. The reverse SSH tunnel is quite interesting. Worth a look.
https://www.youtube.com/watch?v=IokyotAGbJI

@jconk If you're struggling with an issue you are more than welcome to create a post here with a description of the problem, things you've tried, things that aren't working, etc. and we will gladly help you resolve your issue.

It seems as though this is your first post on this forum meaning you haven't reached out previously.

We want people to succeed using our platforms and our team monitors this forum every day providing solutions.

The modules support different LTE bands for different cellular network regions

EMEA is Europe, Middle East, Asia
NA is North America

@tom Curriously, it does not seem to accept -p 0000, which was our pin. We changed it to 1234, which is accepted, but that didn't help with the issue, and it acted identically to providing the wrong pin.

quectel-CM -p 0000 [03-02_13:02:16:064] Quectel_QConnectManager_Linux_V1.6.0.24 [03-02_13:02:16:064] unknow -p '0000' quectel-CM -p 1234 [03-02_13:02:39:300] Quectel_QConnectManager_Linux_V1.6.0.24 [03-02_13:02:39:305] Find /sys/bus/usb/devices/2-1.1 idVendor=0x2c7c idProduct=0x800, bus=0x002, dev=0x003 [03-02_13:02:39:307] Auto find qmichannel = /dev/cdc-wdm0 [03-02_13:02:39:307] Auto find usbnet_adapter = wwan0 [03-02_13:02:39:307] netcard driver = qmi_wwan, driver version = 22-Aug-2005 [03-02_13:02:39:308] Modem works in QMI mode [03-02_13:02:39:325] cdc_wdm_fd = 7 [03-02_13:02:39:399] Get clientWDS = 15 [03-02_13:02:39:430] Get clientDMS = 1 [03-02_13:02:39:462] Get clientNAS = 4 [03-02_13:02:39:494] Get clientUIM = 1 [03-02_13:02:39:526] Get clientWDA = 1 [03-02_13:02:39:557] requestBaseBandVersion RM502QAEAAR11A04M4G [03-02_13:02:39:686] requestGetSIMStatus SIMStatus: SIM_PIN [03-02_13:02:39:718] requestGetProfile[1] 3gnet/carl/1234/1 [03-02_13:02:39:749] requestRegistrationState2 MCC: 238, MNC: 20, PS: Detached, DataCap: UNKNOW [03-02_13:02:39:781] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED [03-02_13:02:39:781] ifconfig wwan0 0.0.0.0 [03-02_13:02:39:803] ifconfig wwan0 down

@Ainars-Bralitis The quectel-CM program is part of the voxl-modem package, you can find the latest release here: http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.0/binary-arm64/voxl-modem_1.0.5_arm64.deb

@Denver-Bennett Great, glad to hear that helped!

@Chase-Riley yes, we can work with Doodle Labs to get this resolved

@groupo em9191 should work for you

@tahawaru We have never tried that. But according to the Quectel product documentation it seems like it should be possible. Of course you would need to attach a suitable GNSS antenna to it. And if you want to use that with PX4 then you would need to create a new driver for it.

hey not sure if this is an @tom or @modaltb inquiry, but when following the steps for the kernel build guide, stuff is off with the drone. It boots up and I can adb fine, but there are issues with the wifi, similar to another post Tom helped me with two weeks ago, but for definitely not the same hardware-related reason. The wifi adaptable does not turn on and when you run voxl-wifi the mac address is undefined. I remember stepping through those scripts while troubleshooting the hardware issues and recall that script queries to find its mac address, which must be returning something invalid.

I have tested this with both of my drones. I can very easily flash them back with https://docs.modalai.com/sentinel-factory-reset/ and they operate as expected. While my desire is to edit part of the usb driver scripts, the kernel I am attempting to put on the drone is the unchanged version following the steps here https://docs.modalai.com/voxl2-kernel-build-guide/. The only deviation from the guide is that the guide is written for SDK 1.1.3. I have put 1.3.0 on both of my drones, and from my understanding the docker scripts pull the default branch of each repo which has the same commit tags as 1.7.8. I have included the output of dmesg for both the 1.3.0 image available from the downloads page, and the results when following the custom kernel build steps.

https://drive.google.com/drive/folders/14L5gLbAOfF2OcSW2rHFTI4VIoREkTCFJ?usp=sharing

@tahawaru I like using Google Fi, super easy to setup

@tom That's really excellent news that you are working on the AT Command issue. I'm really looking forward to the update.

The thermal pad seems to be self-adhesive. When you loosen the screw it is held in place by the thermal pad.
I suspect that the thermal pad will need to be replaced if you force it off. Do you have a type designation for the thermal pad? Then I can buy a replacement somewhere.

Quectel modems are updated by plugging them into a USB adapter, connecting it to a Windows PC and installing the firmware update using proprietary Quectel software. With Sierra it probably works in a similar way.

@pthomason Anyone have thoughts on correcting IP bindings, or the list of services that need to be restarted to notice a new 5G connection?

@David-Smyth Would you be willing to share the .service files you created?