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.

Communicating with packets via tcp/ip

Dear Forum,

I have just received my lightcrafter (DM365) and got it working with the GUI on windows. I would like to communicate via TCP/IP and found a useful discussion for people who wish to control the device using Matlab.

I use a piece of software called Igor Pro that has the ability to communicate via Sockits (an external operation) and I can connect to the lightcrafter using the correct IP address and port number. I can connect fine and apparently send information although I have yet to send anything that seems to have a proper effect.


I used sharkwire to examine the information and when I try to send a command like this (which is 8 bytes in length):

02 01 03 00 01 00 00 07


Then the data length according to sharkwire is 9 bytes and includes 0A at the end. The same command sent via the GUI (display checkerboard pattern)  is 8 bytes and does not have 0A and of course works. So I think that 0A represents a line feed. I don't think that I am deliberately sending a line feed and wonder if before sending commands such as the one above, I need to configure the tcp/ip connection or send some start up commands to configure how the communication is handled. I know that I should precede the command above by putting the lightcrafter into static mode etc. but since I can't send information of the correct size, then these commands don't work either.


I hope someone can offer some help and advise.

Thanks,

Nick

  • Hi Nick,

    I am going to move your conversation to our LightCrafter Forum, they should be able to give you advice on your current situation.

    Best regards,

    Trevor
  • Thank you Trevor.

    If I can update my own post, I have discovered the cause of the problem of adding a new line (0A) to the end of the packet. I was using a bit of code that added it automatically for another purpose and didn't spot it.

    Anyway, that problem is solved but I still can't get the lightcrafter to respond to my packets of information. Using wireshark, the data appear to be correct in terms of the bytes sent but the lightcrafter does not respond properly.

    Any thoughts as to how i can go about troubleshooting this?

    thanks,

    Nick

  • Hi Nick,

    Have you taken a look at the DM365 Command Interface guide? It is a useful resource for understanding the DM365 on the LightCrafter. The source code for the GUI is also useful. This is included in the LightCrafter SW download.

    What command(s) are you sending to the LightCrafter? Did you determine these from packet sniffing what the GUI was sending? Are you sending these packets after the LightCrafter has booted? You have also successfully connected to the LightCrafter with your TCP/IP communication, correct?

    Thanks,

    Clinton

  • Thank you for your response Clinton.

    After many days of struggling, I have finally managed to get the system working. At first, the problem was probably due to sending the wrong information but I still had problems when I was sending the correct data in the correct way. In the end the problem was probably caused by trying to sniff with sharkwire whilst sending information and/or expecting to be able to control the system from my own software whilst the GUI was open. Now I just use my software, then all seems to work fine.

    Whilst i am here, I like my lightcrafter very much but eventually would like to remove the LEDs to just have access to the DMD. I think this is possible with the version I have (3000) and I have seen a video on your web site how to do this. However, there are a number of newer versions of the DLP evaluation technology that are of interest (4500, 6500, 9000). First, can these also be operated via Sockits using similar approaches of sending bytes etc. and second, can the 4500 work without the LEDs. I read somewhere that some of these technologies now shut down if the LEDs are removed or disconnected. My overall goal is to just use the DMD with a USB control via tcp/ip.

    B

    Nick

  • Hi Nick,

    I'm glad you were able to resolve your problem.

    In regards to your other questions. There is no problem removing the LEDs or optics to access the DMD. This can also be done for the LightCrafter4500 (see this post e2e.ti.com/.../278008). The LightCrafter6500 and LightCrafter9000 do not come with a light engine, so you have direct access to the DMD out of the box.

    The LightCrafter3000 is the only platform out of those mentioned that has the RNDIS interface. All the others use USB HID to connect to the PC.

    Thanks,
    Clinton
  • Hi Clinton,
    I found this discussion while roaming through the forum, trying to find some clues on how to communicate with my DLP over TCP/IP.
    I am currently not sure on how to determine the address and port I should be using to open the connection. Any tips? I am using the DLP 9000 (I also found some related topics on the forum, but nothing that tells me how to determine the port).

    Thanks,
    Mirco
  • Hi Mirco,

    Only LightCrafter EVM has TCP/IP communication interface option, on this EVM there is a DM365 embedded processor to which the PC is communicating via TCP over USB (RNDIS driver on windows).

    For LightCrafter 9000 EVM, the controller has direct USB HID interface option, you can download the GUI code from here http://www.ti.com/dlpc900refsw20-dl

    Regards,
    Sanjeev

  • Hi Sanjeev,

    thanks for your reply. I do already have that software to run the EVM, but I am in need of figuring what is the IP address of the device and what port it's using to communicate. How can I do that? The software doesn't give me any indication on that and nor does the device manager.

    Thanks,

    Mirco

  • Hi Mirco,

    I believe that the information needed is available in the Lightcrafter EVM User's guide, from section 2.2.2 thru section 2.2.5

    Regards,

    A214529