Microhard Carrier Setup

  • Where can I find information on the setup and configuration of the microhard module itself? I couldn't find a manual on uhard website or via modal. Thanks.

  • Dev Team

    Hi @tangotoo ,

    I believe we just use a standard config that boots up on the module, but I know there's a web interface from Microhard that you can access.

    Google for something like pDDL2450 - Operating Manual and you'll find a PDF available that shows some of the setup.

    We have docs here that describe how to use the modules as add-ons.

  • Thanks, I'm using the 2.3GHz modules. Following the config button 10 seconds on master/5 seconds on the slave isn't providing a link between the two units for some reason.

    I followed the procedure here, https://docs.modalai.com/microhard-add-on-manual/ . I can see on the VOXL that the file /etc/network/interfaces was updated with the static IP to the uhard. Dmesg shows that the uhard is picked up on the VOXL USB, however a new network interface is not created on the voxl as for as I can see with ifconfig.

    I am able to get to the uhard WebUI on my standalone board via USB. Do you have a recommended way to get to the Microhard WebUI on the VOXL add on unit? I don't have a way to get to the USB Host port directly on the add-on carrier as far as I can tell.

  • OK I can confirm I have at least two issues to resolve. For now, we'll attack the first issue of VOXLFlight not recognizing the carrier as eth0. After not seeing the eth0 listed in ifconfig, I checked the status of the modem service, it was in an error state because device eth0 not found. I also noticed that lsusb on the VOXL does not list the USB-to-Ethernet device as seen on my standalone USB module. Any ideas on where I should try to start troulbleshooting?


  • Progress. After flashing to latest, 3.8.0, a USB0 interface is detected and added to the interfaces. This is different than the eth0 I was seeing in the shell scripts from v3.6. The interface is not taking the static configuration from the /etc/network/interfaces file created during the execution of modem-configure.

  • @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.

  • Dev Team

    Thanks for this update @tangotoo . This isn't something we've seen (needing to use the AT commands for this) so we'll need to check this out on our side and I'll relay this to the team to check out. Thanks!!

  • No problem. What I found was that the Microhards were in a Radio Off state by default. The slave unit on the USB standalone module was easy to access the web interface to configure, but since I couldn't get to the web interface on the master I used the telnet interface to configure the radio to on.

    The new problem is wlan0 dropped out once I got the microhard at usb0 working. The interface is no longer present with an ifconfig on my system. Calling the wlan start function directly yielded a insmod error. So it looks like the system doesn't see the wifi module anymore? Any thoughts on this?

Log in to reply