• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 870 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.

How to use the DLP Discovery 4100 API reference

Rem Fazio
Prodigy 20 points

Hello,

I am very new to this forum and currently working with a colleague of mine on developing a GUI application for the DLP Discovery 4100.

We received a DLL and an API reference guide from tech support but I am not entirely sure how to actually use it. The API reference just lists all the functions calls and a briefed description for each function.

The GUI application is written in WPF , C# and will need to invoke the appropriate functions from the DLL. I was able to reference the DLL in the GUI application and use P/Invoke to call a function. That seems to work just fine.

However, I am not entirely sure which functions I need to call to actually load the images into the DMD frame buffer so they can be loaded into the micromirros.

the examples I have use the ActiveX control which I did not receive from tech support.

Any help will be greatly appreciated. If someone has already done/written something similar and willing to share the code, it will be greatly appreciated as well.

Thank you,

  • 0
    TI__Intellectual 2175 points

    Hello Rem,

    Welcome to the DLP E2E forum.  We saw your message, but need a bit more time to provide some helpful information.  Thank you.

    Regards,

    Eric

  • 0 in reply to ELD
    Prodigy 20 points

    Hi Eric,

    I just wanted to follow up on my issue. It's been almost 1 week.

    Thanks,

  • 0 in reply to Rem Fazio
    TI__Guru 54635 points

    Hello Rem,

    Please contact the source that you got these files from and also ask for "2510447 DLP Discovery 4100 API Code Release".  This should have both the Discovery GUI (written in Visual Basic) and the OCX and USB-DLL codes. 

    The GUI code should show the order of function calls.  Although it calls into the OCX code I recommend bypassing it since it is basically a pass-through layer and really does nothing for you.

    If you have access to some older versions of Labiew 7.1 - 8.1 there is a Labview 7.1 example on how to load and display two alternating images, that you can ask for from them.  It is fairly well documented in the block diagrams and demonstrates the order of calls necessary to initialize and load images.

    Fizix