• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 1258 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.

DLP4500: DLP4500 -- GUI driver vs python drivers

Matthew Jaffe
Prodigy 100 points
Part Number: DLP4500
Other Parts Discussed in Thread: DLPC350,

Hello,

I'm setting up a DLP4500 (DLPC350 controller). Ultimately, I would like to upload custom bitmap images to turn the mirrors in the array on or off (the light engine is removed; we will be shining an external laser beam on the DMD).

I installed the GUI (is there only a Windows version? Is there a Mac or Linux version?), which initially worked. I could turn mirrors to different internal test patterns, and upgraded the firmware to the latest version. I then used Zadig to install libusb-win32 driver to use the pyCrafter4500 package (https://github.com/SivyerLab/pyCrafter4500) to communicate via python. Unfortunately, this breaks the GUI (no longer HID driver).

Is there a HID driver file so that I can switch between the two (GUI, python scripting)?

  • 0
    TI__Genius 12785 points

    Hello Matthew,

    Welcome to the E2E forum and thank you for your interest in DLP technology.

    The GUI is only available for Windows.

    Texas Instruments does not offer an HID driver to switch between the GUI and Python script. Since the repository is unofficial, we cannot guarantee any support of the software.

    Kind regards,

    Austin

  • 0 in reply to Austin Snyder
    Prodigy 100 points

    Hi Austin,

    Thanks for your reply!! I'm sorry, I wasn't clear on my problem: The unofficial python package is working just fine, but requires a different set of drivers be installed. These drivers are incompatible with the official GUI (on Windows). I would like to install the proper drivers to use the GUI again. What drivers are required to use the GUI? How can I find/install them?

    Thanks,

    - Matt

  • 0 in reply to Matthew Jaffe
    TI__Expert 3360 points

    Hi Matt,

    The GUI for DLP4500 can be found here: https://www.ti.com/tool/DLPLCR4500EVM. The download link should provide installation of the application and drivers necessary to communicate with the DLP 4500 EVM.

    Thank you,

    Chris

  • 0 in reply to Cody Smith
    Prodigy 100 points

    Hi Chris,

    When I initially installed this GUI, it worked as intended. However, after changing the device drivers for python scripting, then changing them back, the GUI no longer connects to the DLP4500. I have tried uninstalling and re-installing the GUI, which didn't help.

    Any suggestions for how to get the GUI to connect to the DLP4500 again?

    Thanks,

    - Matt

  • 0 in reply to Matthew Jaffe
    Prodigy 100 points

    Maybe I should restate my problem:

    The GUI doesn't recognize my DLP4500. I'm on Windows 10. I've tried many combinations of reinstalling the GUI, deleting drivers from Device Manager, and restarting the computer. I haven't gotten it to work.

    How can I get the GUI to recognize my device?

    When powered, the device does show the startup screen on the DMD (the light engine is removed; we are just using the DMD)

    Thanks,

    - Matt

  • 0 in reply to Matthew Jaffe
    Prodigy 100 points

    Figured it out! For anyone who comes by this in the future, this is what worked:

    Use Windows Device Manager to uninstall the current drivers. You may have to uninstall/unplug/replug multiple times, until no devices show up under the "libusb-win32 devices" Device Manager category. The DLP4500 then shows up only in "Universal Serial Bus Controllers" category (the DLP4500 may initially show up under both categories). At this point, (and when the GUI is working), Zadig indicates the device driver is "HidUsb (v10.0.19041.1)".

    Next, I also required a computer restart (without it, GUI still didn't recognize the DLP4500). But after the restart, the GUI recognizes the DLP4500 again!