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.

DLPLIGHTCRAFTER: Python TCP/IP socket reported WinError 10061, when two DLPs were connected

Part Number: DLPLIGHTCRAFTER


Dear all, 

I was trying to control 6 DLPs by using python TCP/IP socket.

I can successfully control one DLP with the customized python script. No problem at all.

But whenever the second DLP was connected, I lost the connection to any DLP.

The python was mentioning WinError 10061. 

(BTW, my colleague is using a very similar python code, but he is able to control 2 DLP.)

And sometimes I noticed the red LED on the middle PCB was ON (meanwhile the screen was OFF).

I have to reboot the DLP to start everything again because the PCB onboard power button was not functioning.

N.B.: I was using 6-port phone charger to power the 2 DLPs, the rating was 5V-6A.

Is there anything I missed before establishing the connection for 2 DLPs?

Thanks.

Best,

JH

  • JH,

    Welcome to the E2E forums, and thanks for your interest in our DLP technology.

    I do not believe that our standard DLP LightCrafter driver supports multiple systems at once. As for your python software, where did you get it from?

    Regards,
    Philippe Dollo
  • Dear Philippe,
    Thanks for your email.
    I wrote that python code myself. (My colleague was using that code too.)
    The code was just using a simple Socket module and communicate to the DLP with unique IP address (IP addresses was assigned in GUI).
    It worked fine with one DLP only (i.e. only one USB cable was connected in the network).

    It was mentioned on the DLP user guide (DLPU006E, section 2.2.6, page 28), that multiple DLP can be controlled via different IP address.
    "After all DLP LightCrafter's have unique IP addresses, start an instance of the DLP LightCrafter GUI for each EVM"
    And I tried, it works. (2 GUIs controlling 2 DLPs simultaneously, no problem.)
    I was thinking to use python threading to controlling multiple DLP, but didn't work either.

    A red LED on the middle PCB was lit on from time to time.
    I started to wondering, is it something to do with, e.g. the power supply?
    (I borrowed my friend's phone charger, the issue was still there. Looks like it's not because of the power supply.)
    Is it an LED for something else then, e.g. the network status? (can't read the label next to the LED)
    Why the DLP power button not functioning, when the red LED was on?

    Alternatively, does TI have an upgraded driver which support multiple DLP control?
    Cheers.

    Best,
    Jiaqi Huang (Joseph)
  • Dear Philippe, 

    There were some additional tests, might be helpful for your diagnoses.

    I've run the same python code on a Linux (Ubuntu 16.04 LTS) system.

    The result was the same: one DLP was fine, two DLPs were not.

    The Linux was showing the error message:

    ConnectionRefusedError: [Error 111] Connection refused

    I would assume this issue is not related to the PC, it's something to do with the DLP.

    Please correct me if I am wrong.

    BTW, is there any document talking about how DLP ran as an internet server?

    Cheers.

    Best,

    Jiaqi Huang

  • Hi Jiaqi Huang,

    Please connect one LightCrafter at a time, after boot-up completion, verify that you are able to connect with the LightCrafter GUI and you are able to read the version numbers. 

    If any of the EVM is not connecting/working, then it is specific to the hardware itself, also read the ip configuration version and ping working with the hardware that is not working. The solid RED LED indicates failure during the boot-sequence. For a proper boot-up you need to see red & green blinking pattern.Just solid RED means processor struck in booting. Also when you connect this hardware you can see the device is not getting listed in ip config list.

    You are correct that we should be able to drive multiple EVMs buy assigning different IP address. 

    Also please check if MAC address conflict causing the issue.

    Regards,
    Sanjeev

  • Dear Sanjeev,

    Thanks for the reply.
    I've replaced the 5V phone chargers to a bench-top power supply.
    Now the DLPs can boot up without problem.
    No red LEDs lit on from the middle PCB (power PCB, I guess) any more.

    But still, I can only control one DLP at a time.
    I tried to "ping" the other DLPs, but only (for example) the first DLP respond, and showing "[Errno 113] no route to host".
    Once I switch off the power of the first DLP, I am able to control the second DLP.
    Even if the first DLP is back online again, the computer can still talk to the second DLP.

    For example, I pinged the DLP with IP 192.168.1.150 (the active one). I got response from the same IP.
    But then I pinged 192.168.1.130.
    The response came back from 192.168.1.149 (it should be the DLP with IP 192.168.1.150, don't know why the IP is one digit smaller).

    It made me wonder, Is it something to do with the Linux system on the DLP?
    How does it decide the end of a TCP/IP conversation?
    And release the line for other DLPs.

    Cheers,
    Jiaqi Huang
  • Hi Jiaqi Huang,
    Are you using windows OS system? Try flushing the DNS by sending commands in command window in admin mode

    ipconfig /flushdns
    ipconfig /registerdns

    Also try suggestions on the stackoverflow website
    stackoverflow.com/.../winerror-10061-no-connection-could-be-made

    Let me know if it helps.

    Regards,
    Sanjeev
  • Dear Sanjeev,

    Finally, the DLPs are working together.
    I changed the IP address of the DLPs, and switch back to windows OS.

    The story was:
    1. I set IP address of DLPs to 100, 101, 102, 103, 104, 105. They do not work together, and some DLP won't boot up. (Win 10)
    2. I tested the same setting on the other computer, didn't work either. (Ubuntu)
    3. I replaced the 5V phone charger with bench-top power supply, all DLPs could boot up completely. (Ubuntu)
    4. I changed the IP address to 110, 120, 130, 140 ,150, 160, but still only one DLP can be controlled at a time. (Ubuntu)
    5. After change back to windows, the system just work together magically. (Win 10)

    A detail here, when I type ipconfig(Win)/ifconfig(Linux), the responding IP addresses are always one digit smaller than the set one.
    e.g. 109, 119, 129, 139, 149, 159 instead of 110, 120, 130, 140 ,150, 160.
    I would guess maybe that's why the IP address should be more separated, to avoid collision.

    Well the system is still not working on Linux, but I am happy now, at least it's fine on Windows 10.
    Thanks very much for all the email and support.
    Sorted!

    Have a nice day.

    Best,
    JH
  • You are welcome.
    Regards,
    Sanjeev