I loaded m500 parameters that I got from github onto the board using QGC. I'm hoping enabling DSHOT will address the above issues.

The larger issue is that I fried my drone's original VOXL-flight by accidentally powering it with a 19v supply. I've installed a replacement VOXL-flight, along with a new Pixhawk4 gps module. What I want is just a list of steps for getting the new VOXL-Flight and gps module configured for use in the m500, probably something similar to what you guys would do before shipping m500 orders. Obviously, that's a different question so I'll create a new topic for that.

Should all motor issues not be solved by properly integrating the fresh VOXL-Flight into the m500:
-Everything onboard the drone, is HW that comes included with an order for a VOXL-m500
SKU: MRB-D0001-2-V1.1-F1-B1-C3-M0-T1-K0

-the battery I'm using is a Thunder Power RC ProliteX TP3400-4SPX25 (4 Cell, 14.8V, 50.3Wh)

-The ESCs are covered with insulation. They don't appear to be scraped or crushed, but electrically, I don't know if they've been damaged.

I'm setting up a new VOXL-Flight for use in an m500 after frying the original.

I just ran through the ESC calibration process using the px4-cal-tool and only heard one jingle during the process, I gave the prompt that was waiting for the second jingle probably 3-5 minutes and the drone didn't seem to do anything in that time so I just hit enter to finish.

The motors vibrate pretty violently and even sound like they grind at times when I'm increasing the throttle. One of them won't start spinning until the throttle is at about 50% of max; that motor also vibrates and heats up more than the other 3. I'm hoping, since this drone has barely flown, and these motors aren't available right now, that all of this can be solved by ESC calibration. Help appreciated, thanks.

My motors have also been vibrating violently, one of them has a higher throttle threshold than the other 3, tends to vibrate more and gets considerably hotter than the other ones, so I'd like to hear the dev team's thoughts on this issue as well.

I inadvertently connected a 19V supply to the Barrel Jack on my Voxl m500 drone. What are the odds I only damaged the power module and not my flight core? Are there any easy ways to check?

@tom Thanks for the response. The issue has been resolved. I successfully pinged google after trying this on my home network (WPA2-Personal security type), I'm guessing the issue was with the security type of my firm's network that I had been trying to connect to originally.

As for the modem issues, after familiarizing myself more with the hardware I realized I hadn't attached the VOXL LTE modem that came with my kit which probably explains why a disabling command worked and an enabling command gave me a failure message. I had incorrectly assumed the modem of concern was already onboard the flight core. Thanks to the dev team and @Chad-Sweet for your responses.

@Chad-Sweet

docker0 Link encap:Ethernet HWaddr 02:42:2B:2F:08:D2
inet addr:172.17.0.30 Bcast:0.0.0.0 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:50873 errors:0 dropped:0 overruns:0 frame:0
TX packets:50873 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3919208 (3.7 MiB) TX bytes:3919208 (3.7 MiB)

wlan0 Link encap:Ethernet HWaddr EC:5C:68:CD:24:BD
inet addr:192.168.8.1 Bcast:192.168.8.255 Mask:255.255.255.0
inet6 addr: fe80::ee5c:68ff:fecd:24bd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8863 errors:0 dropped:0 overruns:0 frame:0
TX packets:28646 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3000
RX bytes:659524 (644.0 KiB) TX bytes:2228956 (2.1 MiB)

Hey @modaltb

Thank you for the response! I believe I'm using the Microhard modem, but just to be sure, could you tell me how I can verify that, presumably within the adb shell?

All in the adb shell, I was trying to pull the docker image for the C++ SDK when I kept getting the following error:
Error response from daemon: unable to ping registry endpoint https://gcr.io/v0/
v2 ping attempt failed with error: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [::1]:53: server misbehaving
v1 ping attempt failed with error: Get https://gcr.io/v1/_ping: dial tcp: lookup gcr.io on [::1]:53: server misbehaving

I assumed the board had failed to connect to the internet so I again tried entering station mode with a different SSID of another working network, rebooting as needed. Neither of the networks I tried are password protected if that's important.

I've tried several trouble-shooting tactics mentioned here on the forums including various combinations of [ifconfig docker0 down] and [ifconfig wlan0 down] and then the corresponding [...up] commands when those failed to yield better results. I also used [systemctl disable voxl-modem] and rebooting then trying to ping google.com and modalai.com and failed at both, getting "unknown host" messages. I then tried using [systemctl enable voxl-modem] and was returned "Failed to execute operation: No Such File or directory."
Between all my trouble shooting steps I've tried pinging google.com and modalai.com.
with no avail.
The drone was handed to me as a project at work. I thought I was working with an m500 but my ifconfig response in the adb shell doesn't show a "eth0" like the m500's seem to based one what I've noticed in the forums. The board I'm working with has "MODAL AI M0019-REV B" printed on one of the edges forming the triangular point at one end.

Help me re-enable my modem and get VOXL connected to internet, please. Thanks!