• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 32 subscribers
  • Views 2001 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Connecting multiple lightcrafters to one computer

DAC
Prodigy 50 points


I am having difficulty communicating with the lightcrafters when more than 2 are connected.

I am trying to connect 5 lightcrafters to a computer running Windows 7 through a D-link USB port. I have successfully changed the IP's of each of the lightcrafters to end with 110, 120, 130, 140, 150. I can connect to them successfully either individually or if only two are connected. If I add more than 2 I can not connect to the new one and can sometimes not connect to one of the first two connected. Can anyone help me fix this? 

  • 0
    TI__Mastermind 30875 points

    Hello DAC,

    While some one experiencing similar problem and have found solution i would like to give some more inputs. 

    Please check from the command line if you are able to get the ping response from each Lightcrafter ip address when more than two connected to the USB hub.

    Regards,

    Sanjeev

  • 0 in reply to Sanjeev
    Prodigy 50 points

    Hi Sanjeev,

    I have posted the results of pinging all 5 devices below. It appears I can ping the device but there is some trouble with assigning my computer the correct IP. Hope this helps.

    ping 192.168.1.110

    Pinging 192.168.1.110 with 32 bytes of data:
    Reply from 192.168.1.110: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.110: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.110: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.110: bytes=32 time<1ms TTL=64

    Ping statistics for 192.168.1.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

    ping 192.168.1.120

    Pinging 192.168.1.120 with 32 bytes of data:
    Reply from 192.168.1.109: Destination host unreachable.
    Reply from 192.168.1.120: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.120: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.120: bytes=32 time<1ms TTL=64

    Ping statistics for 192.168.1.120:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

    ping 192.168.1.130

    Pinging 192.168.1.130 with 32 bytes of data:
    Reply from 192.168.1.109: Destination host unreachable.
    Reply from 192.168.1.119: Destination host unreachable.
    Reply from 192.168.1.130: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.130: bytes=32 time<1ms TTL=64

    Ping statistics for 192.168.1.130:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

    ping 192.168.1.140

    Pinging 192.168.1.140 with 32 bytes of data:
    Reply from 192.168.1.109: Destination host unreachable.
    Reply from 192.168.1.119: Destination host unreachable.
    Reply from 192.168.1.129: Destination host unreachable.
    Reply from 192.168.1.140: bytes=32 time=1ms TTL=64

    Ping statistics for 192.168.1.140:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

    ping 192.168.1.150

    Pinging 192.168.1.150 with 32 bytes of data:
    Reply from 192.168.1.109: Destination host unreachable.
    Reply from 192.168.1.119: Destination host unreachable.
    Reply from 192.168.1.129: Destination host unreachable.
    Reply from 192.168.1.139: Destination host unreachable.

    Ping statistics for 192.168.1.150:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

  • 0 in reply to DAC
    TI__Mastermind 30875 points

    Hello DAC,

    I see problem with pinging reply from 2nd Lightcrafter onward. For any ping address after 192.168.1.110 say 192.168.1.120, 192.168.1.130 etc...I see below errors?

    Reply from 192.168.1.109: Destination host unreachable.

    Reply from 192.168.1.119: Destination host unreachable.

    Reply from 192.168.1.129: Destination host unreachable.

    Reply from 192.168.1.139: Destination host unreachable.

    What are these IP addresses? Are you not having just one IP to the host that is PC side?

    Like PC can have 192.168.1.99 and LightCrafter hardware can have 192.168.1.100, 192.168.1.101, 192.168.1.102 etc..

    Regards,

    Sanjeev

  • 0 in reply to Sanjeev
    Intellectual 590 points

    Hi,

    please open a console window and enter this command:

    ipconfig /all

    Whats the output?

  • 0 in reply to Curtis Newton
    Prodigy 50 points

    Thank you both for the replies.

    Sanjeev, I was not aware the lightcrafters could be configured this way. I was under the impression that the assigned IPs must be at least 2 apart so that the lightcrafter could assign the computer its own IP minus 1. If you have two lightcrafters with IP's 192.168.1.110 and 192.168.1.111 won't the second lightcrafter (IP 192.168.1.111) assign the computer an IP of 192.168.1.110 and create an issue? If I do this, then I cannot connect to one of the lightcrafters, is there a different way to configure the system?

    Curtis. irrelevant information cropped out

    Ethernet adapter Local Area Connection 9:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : USB Ethernet/RNDIS Gadget #8
    Physical Address. . . . . . . . . : 02-A1-2F-F3-1E-D1
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::2540:a69b:dcda:9a4c%23(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.129(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Monday, June 17, 2013 10:21:13 AM
    Lease Expires . . . . . . . . . . : Saturday, June 29, 2013 12:07:51 AM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.1.130
    DHCPv6 IAID . . . . . . . . . . . : 513736063
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-D3-CC-9B-90-2B-34-5C-51-D9

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection 8:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : USB Ethernet/RNDIS Gadget #7
    Physical Address. . . . . . . . . : BE-D8-BD-28-6E-20
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::7000:186d:cd8f:11b0%22(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.119(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Monday, June 17, 2013 10:21:19 AM
    Lease Expires . . . . . . . . . . : Saturday, June 29, 2013 12:08:03 AM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.1.120
    DHCPv6 IAID . . . . . . . . . . . : 488041772
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-D3-CC-9B-90-2B-34-5C-51-D9

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection 7:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : USB Ethernet/RNDIS Gadget #6
    Physical Address. . . . . . . . . : 66-99-70-DD-02-43
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::15b5:5d2a:713:2486%20(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.149(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Monday, June 17, 2013 10:22:04 AM
    Lease Expires . . . . . . . . . . : Saturday, June 29, 2013 12:08:42 AM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.1.150
    DHCPv6 IAID . . . . . . . . . . . : 525789134
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-D3-CC-9B-90-2B-34-5C-51-D9

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection 6:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : USB Ethernet/RNDIS Gadget #5
    Physical Address. . . . . . . . . : C6-CF-87-D6-C2-5E
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::41be:bc4b:ec69:fbad%18(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.139(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Monday, June 17, 2013 10:21:42 AM
    Lease Expires . . . . . . . . . . : Saturday, June 29, 2013 12:08:20 AM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.1.140
    DHCPv6 IAID . . . . . . . . . . . : 467804172
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-D3-CC-9B-90-2B-34-5C-51-D9

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection 4:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : USB Ethernet/RNDIS Gadget #3
    Physical Address. . . . . . . . . : 16-25-9A-51-5C-00
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::6812:17cb:73fd:356f%16(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.109(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Monday, June 17, 2013 10:20:15 AM
    Lease Expires . . . . . . . . . . : Saturday, June 29, 2013 12:07:23 AM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.1.110
    DHCPv6 IAID . . . . . . . . . . . : 386539947
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-D3-CC-9B-90-2B-34-5C-51-D9

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

  • 0 in reply to DAC
    Intellectual 590 points

    Ethernet adapter Local Area Connection 9:
    IPv4 Address. . . . . . . . . . . : 192.168.1.129(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    Ethernet adapter Local Area Connection 8:
    IPv4 Address. . . . . . . . . . . : 192.168.1.119(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    Ethernet adapter Local Area Connection 7:
    IPv4 Address. . . . . . . . . . . : 192.168.1.149(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    Ethernet adapter Local Area Connection 6:
    IPv4 Address. . . . . . . . . . . : 192.168.1.139(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    Ethernet adapter Local Area Connection 4:
    IPv4 Address. . . . . . . . . . . : 192.168.1.109(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    http://support.microsoft.com/kb/175767/en-us

  • 0 in reply to Sanjeev
    Prodigy 50 points

    Thanks Curtis

    I think you've nailed the problem. Unfortunately that page is way above my understanding of networks, do you happen to have a solution for how to fix this? Is there a way TI could fix this problem, perhaps by giving the user the option to tell the Lighcrafter what IP to use when communicating with the computer?

    Thanks

  • 0 in reply to DAC
    Prodigy 225 points

    DAC,

    Could you try using different sub network for different LCrs? E.g, first using 192.168.1.100, and second using 192.168.2.100,etc...

    regards

    Natty

  • 0 in reply to DAC
    Intellectual 590 points

    Hi,

    its a linux on the lightcrafter so it should be easy to config the network und the dhcp server so that every LC is in a different subnet. I do not know if the LC or the GUI supports this.

    Curtis

  • 0 in reply to Natty Dale
    Prodigy 50 points

    Thanks a ton everyone,

    Natty's answer is the easiest way to set up separate sub networks and worked like a charm, nullifying the issue the Curtis identified. Although this is a separate problem, other people trying to set up multiple lightcrafters should note http://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/f/850/t/212321.aspx which makes them connect faster.

    thanks again