Sentinel VOXL2 Microhard not running
-
@rohitpillai Woot! Thank you for all of your help! I will go ahead and merge this into master so that it will make it into the next release.
@tom Hey Tom,
I am noticing this issue of microhard not having a static ip on my system as well.

It appears I am on a later version than the one in the post. Is the voxl-static-ip service now the preferred way to have a static ip?
-
@tom Hey Tom,
I am noticing this issue of microhard not having a static ip on my system as well.

It appears I am on a later version than the one in the post. Is the voxl-static-ip service now the preferred way to have a static ip?
@wilkinsaf Code is still there

-
@wilkinsaf Code is still there

-
@wilkinsaf Interesting, give
voxl-static-ipa try and see if it helps. I have yet to integrate that directly into voxl-modem. We have a systemd service setup for it, so I would go ahead and modify/usr/bin/voxl-static-ipand then enable it's servicesystemctl enable voxl-static-ip -
@wilkinsaf Interesting, give
voxl-static-ipa try and see if it helps. I have yet to integrate that directly into voxl-modem. We have a systemd service setup for it, so I would go ahead and modify/usr/bin/voxl-static-ipand then enable it's servicesystemctl enable voxl-static-ip -
@wilkinsaf voxl-static-ip is pretty "dumb" as it doesn't check to see if the interface is actually up before trying to modify the IP so that's probably the reason why you need the big sleep, but I'm sure you figured that out already.
@tom Yeah. I think I figured it out
My uname has "m0054". It uses eth0 as interface instead of usb0. i dont see code for setting the ip for eth0. What is weird is that I also see usb0 come up as an interface. But I am going to add some code here to hopefully fix that. Will make a branch or something if it is useful for someone else

-
@wilkinsaf Also a
voxl-versionwould be helpful to see. To give you some background on why this part is a little confusing, on newer builds of Microhard add-ons we had to change out a chip due to supply shortages and so the newer Microhard add-ons will be handled as "usb0" instead of "eth0". -
@wilkinsaf Also a
voxl-versionwould be helpful to see. To give you some background on why this part is a little confusing, on newer builds of Microhard add-ons we had to change out a chip due to supply shortages and so the newer Microhard add-ons will be handled as "usb0" instead of "eth0".No other wifi or ethernet. I am connected with adb.
VOXL2 with microhard
cameras: stereo, tracking, hires (although my config only has the tracking and hires turned on rn)voxl-version:

dmesg | grep eth0
[ 3.291467] smsc75xx 1-1.1:1.0 eth0: register 'smsc75xx' at usb-xhci-hcd.0.auto-1.1, smsc75xx USB 2.0 Gigabit Ethernet, 42:cd:53:3c:37:18 [ 5.516283] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 9.465432] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 9.475251] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 14.332677] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 14.345964] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 21.188500] smsc75xx 1-1.1:1.0 eth0: link down [ 22.663119] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 22.682574] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 23.155729] smsc75xx 1-1.1:1.0 eth0: link down [ 23.168624] smsc75xx 1-1.1:1.0 eth0: link down [ 25.801191] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 34.154417] smsc75xx 1-1.1:1.0 eth0: link down [ 35.708201] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 35.723892] smsc75xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1dmesg | grep usb0
2.202994] register_client_adhoc:Client handle 64 usb0 [ 5.322266] f_cdev_alloc: port_name:at_usb0 (ffffffdd12c44c00) portno:(0) [ 37.386234] rndis_host 1-1.2:1.0 usb0: register 'rndis_host' at usb-xhci-hcd.0.auto-1.2, RNDIS device, 46:b5:b5:15:45:b0 -
@wilkinsaf Hmm okay very interesting, I'll replicate your setup and see what I can find
-
@wilkinsaf Hmm okay very interesting, I'll replicate your setup and see what I can find
-
@wilkinsaf What does your
/etc/network/interfacesfile looks like@tom said in Sentinel VOXL2 Microhard not running:
/etc/network/interfaces

I am wondering if they could be clashing
-
@tom said in Sentinel VOXL2 Microhard not running:
/etc/network/interfaces

I am wondering if they could be clashing
@wilkinsaf No, took out usb0 entry and it still didnt set the correct ip
Reading along? Create a free ModalAI Forum account to join in.
With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.
Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.
Register Login


