DLP LightCommander hardware trigger

Hello Guylain,

Welcome to DLP & MEMS forum.

Unfortunately above three different behaviors requested are not possible with the 'external trigger'.

The external h/w trigger input to the LightCommander by design is "strictly" tighed to 'DLP_Display_DisplayPatternManualStep()" kind of behavior. So it can be used as pattern advancement (or single step) function only.

Now, there is software implementation possible to mimic your three behaviors -

For example - Let us say there are 20 patterns to be operated upon in your application then create a structured light project of 20 8bpp patterns stored in the following way |PAT_1 | PAT_2 |  .......|PAT_20|.

Behavior [#1] - a single trig to start the sequence display following the image LUT, with an internal fixed frequency (complete sequence, then stop)

a) Send ImageOrderLUT command with pattern numbers as {0,1,2,3,...,19}

b) We will soon be making a LightCommander f/w upgrade with DLP_Display_DisplayPatternAutoStepForSinglePass () support. So you can call this API.

Behavior [#2] - a trig for each image following the LUT, with continuous image display until the next trig

a) Send ImageOrderLUT command with pattern numbers as {0,1,2,3,...,19}

b) Call DLP_Display_DisplayPatternManualStep()

Behavior [#3] - a trig for each image following the LUT, with a single image display and then blank until the next trig

a) Send ImageOrderLUT command with pattern numbers as {0}

b) Call DLP_Display_DisplayPatternAutoStepForSinglePass

c) Repeat (a) with ImageOrderLUT command set to different pattern say {1} , {2} ....

PS:  The software implementation comes with added delays in the system; so if you are not particular about timing then I think the software approch would work for you.

Hello!

Thanks for your answer, that's more clear for me now.

Just one more question using the hardware input trigger:  if it behaves like the DLP_Display_DisplayPatternManualStep() function, will I get the display only once then it waits for the next trigger, or it will loop over the same image until the next hardware trigger?

Thanks,

Guylain Lemelin

Hi Guylain,

Yes, it will be like loop over the same image until next hardware trigger.

Regards,

Sanjeev

Thanks!

Guylain