Can one PC operate multiple lightcrafter at the same time?

Hi Adam,

The assigned IP address last subnet should be two numbers higher or lower than the other LightCrafter's IP address.

For example, when 192.168.1.100 is assigned to LightCrafter1, 192.168.1.99 will be assigned to the PC. Yo should assign 192.168.1.102 to the next one(LightCrafrer2), so the virtual address 192.168.1.101 will be assigned to the PC and so on..

The LightCrafter port value remains the same. Check the IP configuration by typing ipconfig in the cmd terminal.

Regards,

Divya

Hi Divya,

So this time I tried to connect to two of them instead of three. I manually assigned the IP address to them to be "192.168.1.100" and "192.168.1.102". But still the same thing, that is, the demo program works fine with "192.168.1.100" but gave me "Unable to connect to server" when change the IP in the program to "192.168.1.102".

Hello Adam,

See this link regarding assigning IP addresses http://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/f/850/t/271118.aspx from a single USB hub.

Regards,
Sanjeev

Hi Sanjeev,

Thank you for the link. I followed the suggestion in that link, and manually assigned the IP to be "192.168.1.100", "192.168.2.100" and so on. However, the same thing happened. I can run the demo program on the device with IP "192.168.1.100" but not on "192.168.2.100". I also tried to ping those IP, and following is the screenshots. Currently I only try to connect two of them to make sure it would work.

I think there is something wrong when pinging 192.168.2.100, but I don't know what is the problem.

Hello Adam,

The log you have attached showing it is able to ping to both HW without any problem. Perhaps you should look at your demo code. In the demo code comment everything and just add code for pining two different IPs. And verify if it works.

Regards,
Sanjeev

Hi Sanjeev,

When you mentioned to add code for pining two different IPs, do you mean something like 

system("ping 192.168.2.100")?

Or is it something else? The above one works fine BTW.

Thank you.

Hello Adam,

No. I wanted to you have the basic test. I think what you are doing with system(ping 192.168.2.100) looks fine to me. Now add the code to ping all the LightCrafters. Test if the result is pass for all the cases.

Regards,

Sanjeev

Hi Sanjeev,

I don't quite understand what do you mean by "all the cases", could you provide a little more details?

Also, I tried something else today. I connect only one lightcrafter to the PC, and set the IP to be "192.168.2.100", I can ping the IP address okay, but the sample code cannot connect to it. I am not sure what could be the problem?

Adam,

Since you have mentioned system(ping "192.168.2.100") works, so i wanted you try pining both IPs like system("ping 192.168.1.100) and system(ping "192.168.2.100").

Regards,

Sanjeev

Hi Sanjeev,

So I tried the following three cases.

1. 

system("ping 192.168.1.100");

system("ping 192.168.2.100");

2. 

//system("ping 192.168.1.100");

system("ping 192.168.2.100");

3.

system("ping 192.168.1.100");

//system("ping 192.168.2.100");

They all work fine. That is, pinging the lightcrafter has no problem at all. Also, like I mentioned before, one strange thing is that if I connect only one lightcrafter and set the IP to be "192.168.2.100", then it doesn't work. However, if I change the IP to be "192.168.1.100" then it works fine. This is very strange and I have no idea why that would happen.

Hi Adam,

What is the PC side IP when communicating with LightCrafter having IP 192.168.2.10? If your PC is showing the IP address as 192.168.1.99 or so... then just change it to 192.168.2.99 and then try communicating with it. I think it is something to do with TCP/IP network level configuration. Nothing to do with the LightCrafter hardware.

Regards,

Sanjeev

Hi Sanjeev,

The IP of the PC is always set to be 192.168.1.1.

Following your suggestion, I connected only one of the lightcrafter and change the IP address of the lightcrafter to be 192.168.2.1. When I run the program, the pining is fine but still cannot connect to it. I also tried 192.168.3.1 and the same thing happened.

I also believe the problem is in the TCP/IP communication, but don't know what is the problem...