M500 VOXL connectivity issues
-
We received 10 new M500s. One of the ten is having an issue connecting to the VOXL. It has a microhard modem which was configured with a custom IP. The microhards are connected to each other, but I cannot connect to the vehicle over UDP from QGC. I am able to adb into the VOXL. This vehicle was set up exactly as the other 9 were. I was looking for some additional troubleshooting steps or ideas as to what could be wrong. Thank you.
-
@spitkowsky Are you able to ping the VOXL over the Microhard network?
-
@tom I cannot
-
@spitkowsky When you ADB onto the problmeatic M500 and run
ifconfigdo you see the microhard network interface showing up? Is it getting the IP address you're assigning to it? -
@tom the microhard network is not showing up when I ifconfig on the problematic m500
-
@spitkowsky Can you try running
voxl-configure-modemand running through the microhard setup -
@tom Yes this is what I did. I also did this on 9 other M500s without issues. The steps are:
adb shell into the voxl
voxl-configure-modemSelect 4 for microhard
Select 2 for custom IP
Input IP Address -
@spitkowsky What do you see with
journalctl -u voxl-modem? -
-- Logs begin at Thu 1970-01-01 00:00:04 UTC, end at Thu 1970-01-01 00:00:26 UTC. --
Jan 01 00:00:06 apq8096 systemd[1]: Starting Modem Initialization...
Jan 01 00:00:08 apq8096 systemd[1]: Started Modem Initialization.
Jan 01 00:00:09 apq8096 voxl-modem-start[2881]: apq8096 detected...
Jan 01 00:00:09 apq8096 voxl-modem-start[2881]: Initializing Microhard modem...~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
standard input -
@tom You likely know what this should look like but here are the logs for a "good" one
-- Logs begin at Thu 1970-01-01 00:00:04 UTC, end at Thu 1970-01-01 00:00:42 UTC. --
Jan 01 00:00:07 apq8096 systemd[1]: Starting Modem Initialization...
Jan 01 00:00:09 apq8096 systemd[1]: Started Modem Initialization.
Jan 01 00:00:09 apq8096 voxl-modem-start[2985]: apq8096 detected...
Jan 01 00:00:09 apq8096 voxl-modem-start[2985]: Initializing Microhard modem...
Jan 01 00:00:14 apq8096 voxl-modem-start[2985]: ifdown: interface eth0 not configured
Jan 01 00:00:15 apq8096 voxl-modem-start[2985]: run-parts: /etc/network/if-pre-up.d: No such file or directory
Jan 01 00:00:15 apq8096 voxl-modem-start[2985]: RTNETLINK answers: Network is unreachable
Jan 01 00:00:15 apq8096 voxl-modem-start[2985]: Setting up GPIO pins for the Microhard Modem
Jan 01 00:00:15 apq8096 voxl-modem-start[2985]: Using eth0 workflow
Jan 01 00:00:15 apq8096 voxl-modem-start[2985]: [INFO] Using eth0 for Microhard -
@spitkowsky Is there any chance you can take the microhard modem add-on board off one of the "good" M500s and put it on this "bad" one? This way we can determine whether or not the modem board is the issue.
-
@tom
Swapped the modem from a good and the bad M500 and the vehicle issue stayed persistent. In other words, the modems both function correctly. -
@tom @spitkowsky
I'm wondering if this may be a HW issue on the VOXL board. Possible the USB or the USB VBUS control is now no longer working correctly, thus not allowing the MH modem USB hub to enumerate (eth0 never seems to be detected, implying a USB hub path issue, but on the VOXL side since the MH HW is known good on another system).
https://docs.modalai.com/expansion-design-guide/#modalai-usb-hub-example
This may be cause for an RMA.
