@modalab For anyone working with these in the future.
I needed to be on 3.8.0 for the correct driver to be picked up for the microhard to register as an ethernet device.
I needed to call dhcpcd manually to get it to pickup the static IP configuration.
I used the AT command interface to the microhard over telnet to get it to be configured correctly. Holding the button for 10 seconds did not put it into a master transmitting state (confirmed via telnet).
You need to enter AT&W after the commands to write them to the device otherwise they are discarded.

Maybe this was a fluke of the 2.3GHz model, but it was definitely not plug and play.

@modaltb thanks for the follow up. I'll see if I can secure a starling 2 soon.

I have an original Starling and am developing a platform around it. I noticed that the sensor package on my Starling is different than the Starling 2. Are the sensors offered on Starling 1 still recommended or should I base my design around Starling 2. I want to ensure I am not wasting development time or tuning if I'll need to reimplement the sensors. Thanks.

What is the estimated flight time of the Sentinel as delivered with the 5Ah battery? Totally understand there are a lot of variables in that equation, but just need an estimate.

I searched the docs/forum and was unable to find a method to clone a running and configured VOXL for backup. I was looking for a method to mount the voxl as a block device so I could dd the memory off as backup. Is there a method to clone the voxl in this manner? I saw the backup utility for the camera settings but I didn't see a complete system backup/image creation method.

Would like to get some ideas on what could lead to 2 PWM channels dying on what was a working quad when it landed. When arming for a second flight I noticed two motors weren't turning. After troubleshooting up the signal chain, I could confirm the output of PWM2 and PWM3 had no output no matter what setting/command was attempted. I flashed to PX4 in case it was an Ardupilot issue, but still have no output on PX4.

I can move to channels 5/6 with no issue, but I'm a little concerned that without identifying root cause I may be placing other channels at risk. Any ideas on troubleshooting steps, or things that could have caused it? There were no shorts that I could measure and the PWM and ESC are on the same ground reference.

Its working on a different android device, so I think its a kernel module issue on the S21. We can close this out.

@tom I've tried it on an S21 and Pixel 4 phones and haven't had any luck. If its a non-starter, that would be good to know so I can focus my efforts on a different solution versus trying to force the phones to cooperate. FWIW, I can flash/modify/sideload whatever is required to make it happen.

The objective is to bring up QGC on the device with the GCS link via uHard.

I don't know if its related to your problem, but I had a lack of communication issue between voxl-vision and my PX4 and it was due to an additional process, voxl-mavlink-server not running. You may want to check if there are any other supporting processes you need running first in order to bring up ROS. I'm not a ROS user, so I can't help too much in that regard.

I am having some trouble getting my Android devices to recognize the modem carrier. Can you provide guidance on connecting the standalone carrier to an Android host? The device works fine with Windows/Linux PC over USB.

Based on the documentation stating that the carrier added the LAN7500 controller for Android compatibility, I thought my device would recognize it. I contacted Microhard, and they were surprised it worked with Android at all... I know it must be possible since the Voxl is android at its core. Any pointers would be great so I can decide if it is even worth trying, or if I need to completely change approach. USB to RJ45 adapter is working with the phone, worst case I could try to connect directly to the ethernet port on the modem.

From the documentation, https://docs.modalai.com/microhard-usb-carrier/, USB DN1 and DN2 are both connected to the modem. I assume DN2 is responsible for the network connection, right? Just trying to collect information for USB enumeration/troubleshooting. I've noticed that sometimes the device shows up as NULL on Android, and sometimes as pmDDLxxx. I haven't been able to consistently determine what causes the state change.

@tom thanks. I was able to resolve the communications issue for 3.8 (mavlink-server is separate unlike the prior version).