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.

DLP4710EVM-LC: headless control with Python

Part Number: DLP4710EVM-LC


Tool/software:

Hi, is it possible to "headlessly" execute Python code controlling the DLP4710EVM-LC, i.e., without requiring the user to interact with software such as the DLP® EVM GUI Tool? There are at least two technical realization possibilities, but I couldn't find documentation whether any of them is supported:

  1. Importing the required Python modules (which are internally used by the GUI Tool) in a standalone Python script
  2. Launching the GUI Tool in some headless mode, have it execute a Python script, and exit when script execution is finished

Can this be done by one of the methods above (or a totally different method)?

Thanks & kind regards,

Markus

  • Markus,

    We have assigned this to our software team.  They should get back to you tomorrow on this.

    Fizix

  • Hello Markus,

    Can you share the reason for running the python script or running the GUI Tool in headless mode?

    1. Currently we have C based API (link) which can run standalone and have the capabilities of the GUI tool.

    Regards,
    Kirthi Vignan. 

  • We are working on a complex setup consisting of ~10 unrelated hardware and software components, all of which have well designed Python modules for fine-grained control of individual features, and we would like to operate the system directly from a Python IDE for rapid prototyping with minimum user interaction. The DLP was the last "missing link" in our Python workflow.

    However, in the meantime we found out how use to the Python code distributed with the DLP® EVM GUI Tool in a standalone Python script launched from our Python IDE. The only missing component was the 64 bit version of cyusbserial.dll, which we downloaded directly from the Infineon website (in a package which also contains the 32 bit version, which is identical to the one distributed with the GUI Tool). So the original question is no longer relevant for our particular use case (but might still be for others).

    Kind regards,
    Markus