ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    How to link microhard pDDL?

    Ask your questions right here!
    3
    4
    111
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      shlee853
      last edited by

      Hi Dev,

      I'm testing microhard pDDL module.

      I read all manual and did it.

      Here is IP for VOXL.

      eth0 Link encap:Ethernet HWaddr DA:2C:5D:18:7B:6F
      inet addr:192.168.168.100 Bcast:0.0.0.0 Mask:255.255.255.0
      inet6 addr: fe80::d82c:5dff:fe18:7b6f/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:0 (0.0 B) TX bytes:8196 (8.0 KiB)

      Here is IP for HOST

      enp0s20u4u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 192.168.168.152 netmask 255.255.255.0 broadcast 192.168.168.255
      inet6 fe80::b25c:13b3:5c33:9e6 prefixlen 64 scopeid 0x20<link>
      ether 9e:2c:f3:a6:2b:76 txqueuelen 1000 (Ethernet)
      RX packets 42 bytes 6607 (6.6 KB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 78 bytes 10752 (10.7 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      enp0s20u4u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 192.168.168.237 netmask 255.255.255.0 broadcast 192.168.168.255
      inet6 fe80::dc90:2e27:ecc3:21b8 prefixlen 64 scopeid 0x20<link>
      ether 66:af:0d:e7:31:7d txqueuelen 1000 (Ethernet)
      RX packets 413 bytes 29899 (29.8 KB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 472 bytes 66478 (66.4 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      But, I cannot access each other. I checked ping each other IP.

      I think I have to link mater and slave.

      I refer to manual for link and powered same time with reset button as like this.

      https://docs.modalai.com/microhard-add-on-manual/

      But, IP is not initialized 192.168.168.1 or 2 also, pDDL module was blinking tx only. RX LED is alway on.

      Could you please send me video for pDDL LINK procedure if you have?

      Thanks,

      S 1 Reply Last reply Reply Quote 0
      • S
        shlee853 @shlee853
        last edited by shlee853

        @shlee853 Hi,

        Here is my HOST

        swift@swift-HP-Pavilion-dv6-Notebook-PC:~$ ifconfig
        eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        ether a0:b3:cc:52:14:b8 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        enp0s20u4u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.168.152 netmask 255.255.255.0 broadcast 192.168.168.255
        inet6 fe80::471c:500f:28c7:3d86 prefixlen 64 scopeid 0x20<link>
        ether 9e:2c:f3:a6:2b:76 txqueuelen 1000 (Ethernet)
        RX packets 41 bytes 6279 (6.2 KB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 81 bytes 10981 (10.9 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        enp0s20u4u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.168.237 netmask 255.255.255.0 broadcast 192.168.168.255
        inet6 fe80::2fc7:c2e8:d5e0:a059 prefixlen 64 scopeid 0x20<link>
        ether 66:af:0d:e7:31:7d txqueuelen 1000 (Ethernet)
        RX packets 202 bytes 16855 (16.8 KB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 219 bytes 32282 (32.2 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000 (Local Loopback)
        RX packets 4858 bytes 457898 (457.8 KB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 4858 bytes 457898 (457.8 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.219.182 netmask 255.255.255.0 broadcast 192.168.219.255
        inet6 fe80::6fd6:734f:3553:baf4 prefixlen 64 scopeid 0x20<link>
        ether 60:6c:66:81:e7:19 txqueuelen 1000 (Ethernet)
        RX packets 208551 bytes 118036955 (118.0 MB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 49693 bytes 5838784 (5.8 MB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

        swift@swift-HP-Pavilion-dv6-Notebook-PC:~$

        Here is my VOXL
        yocto:/# ifconfig
        eth0 Link encap:Ethernet HWaddr B6:B4:A2:53:47:47
        inet addr:192.168.168.100 Bcast:0.0.0.0 Mask:255.255.255.0
        inet6 addr: fe80::b4b4:a2ff:fe53:4747/64 Scope:Link
        UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
        RX packets:2 errors:0 dropped:0 overruns:0 frame:0
        TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:1000
        RX bytes:92 (92.0 B) TX bytes:1342 (1.3 KiB)

        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:47188 errors:0 dropped:0 overruns:0 frame:0
        TX packets:47188 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:0
        RX bytes:5046771 (4.8 MiB) TX bytes:5046771 (4.8 MiB)

        wlan0 Link encap:Ethernet HWaddr EC:5C:68:CD:25:A1
        inet addr:192.168.8.1 Bcast:192.168.8.255 Mask:255.255.255.0
        inet6 addr: fe80::ee5c:68ff:fecd:25a1/64 Scope:Link
        UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
        RX packets:0 errors:0 dropped:0 overruns:0 frame:0
        TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:3000
        RX bytes:0 (0.0 B) TX bytes:3644 (3.5 KiB)

        yocto:/# ping 192.168.168.152
        PING 192.168.168.152 (192.168.168.152) 56(84) bytes of data.
        From 192.168.168.100 icmp_seq=1 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=2 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=3 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=4 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=5 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=6 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=7 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=8 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=9 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=10 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=11 Destination Host Unreachable
        From 192.168.168.100 icmp_seq=12 Destination Host Unreachable
        ^C
        --- 192.168.168.152 ping statistics ---
        13 packets transmitted, 0 received, +12 errors, 100% packet loss, time 12014ms
        pipe 3

        I cannot reach to my HOST from VOXL.

        Could you please give me advice?

        Thanks

        1 Reply Last reply Reply Quote 0
        • tomT
          tom admin
          last edited by

          @shlee853 In order for the two Microhard modules to communicate with eachother, one needs to be configure as a "Master" and one needs to be configured as a "Slave". Our recommended configuration is to have the "Master" module on the VOXL and the "Slave" module on the host computer side. The easiest way to check whether they are configured correctly as Master / Slave is to ADB onto VOXL and attempt to ping 192.168.168.1. If that is succesful, then you know that the Microhard module on VOXL was configured correctly as Master. You can do the same on the host PC side to check the Slave module ping 192.168.168.2. It is likely that one of these two modules has not been configured correctly.

          1 Reply Last reply Reply Quote 0
          • M
            manzur
            last edited by manzur

            We have the same issue here with the Microhard pairing as posted in this https://forum.modalai.com/topic/251/issue-in-microhard-paring-with-slave-unit. We also tried to follow the instruction but its not paring.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Powered by NodeBB | Contributors