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.

Stored pattern Sequence problem on LCR

Other Parts Discussed in Thread: DLPC300

Hi there,

In the stored pattern sequence mode, i often found that the pattern is not always displayed as it should be, or sometimes missing actions.

E.g, in command mode, after loading all the patterns, clicking start, when next button is clicked, sometimes there is no pattern being displayed.

And again, in command mode, after loading all the patterns, clicking start, when next button is clicked, the pattern sequence did not start from first one. And then stop clicked, and re-click start, next button, the pattern sequence is normal again. 

Such behavior is quite annoying, i wonder whether it is my setting problem or there is some forbidden setting, or just firmware problem, or hardware problem? 

Much thanks.

  • Hello Natty,

    Looks like configuration problem to me. Before we zero on it, could let us know the exact step and configuration detail.

    Like pattern mode, pattern bit-depth, total number of patterns, exposure, period etc...

    This will help us look more into the issue you are facing.

    Regards,

    Sanjeev

  • Hi Sanjeev, 

    Thanks for replying.

    1, problem i called 'flashing', such as setting bit depth 1, pattern cnt 40, command trigger, ExpTime 1Sec, after loading the patterns, click start,  click next will give me first pattern, then click stop, the patterns are flahsing quickly. This problem is easy to reproduce. Almost with all the pattern number larger than 24 and every time you click stop following next button, the patterns will flash. 

    2, problem also with stop action, this one comes with the pattern number larger than 96, e.g. 98 pattern number, keeps other settings the same, after loading, start, next and click stop will give me any random pattern for quite a short time.

    3, problem i called as no show at first next action. This one is difficult to reproduce, and during test it happens once and awhile.  with settings like pattern 28, 30, 60 i often used, 1 bit depth, 1second exp time, start, next , next ....stop, and repeat, sometimes the first next action will give me nothing.

    4, problem called as random show at first next action. This one seems relative with changing settings. Such first set ptn count to 96, 1bitdepth, 1 second,command trigger, and upload the pattern sequences, start ,next..., stop, behaves normal. Then changing the ptn count to 95, keeps other settings the same, uploading pattern sequences, click start, click next will give me a random pattern but not the first pattern,e.g, the 6th pattern, second next will give me 7th pattern, and aftern several actions, the pattern goes back to its normal ordering, e.g, 20th click next will give me 20th pattern, and others are normal again. Or if you click stop at any step, and restart, the sequence will be normal again.

    regards

    Natty

  • Hello Natty,

    #1. Unfortunately I cannot reproduce it here. Before we go further, please ensure you are updating to the latest 3.0 Package software baseline which is DM365 v5.0 FPGA 2.6.43 and MSP3.0. The flashing happens typically when the DLPC300 still sending the LED_EN signals going to the LEDs is still active even after sending the stop command. But would like if you keep the software upto date.Is it also having a 2.0 Sticker on the hardware?

    #2. Okay.

    #3. We haven't seen nothing shown issue. But we keep looking on it.

    #4. Okay, we can see this issue. we will investigate more on it. Looks to me it #2 and #4 behavior are same problem.

    I am assuming, right now you are able to workaround these issue and proceed further, please let us know if are blocked completely. 

    Regards,

    Sanjeev

  • Hi Sanjeev,

    The firmware/software/hardware version i am using here are

    DLP lightcrafter control Software 5.0

    DM365: 5.0

    FPGA: 2.6.43

    MSP430: 3.0

    Hardware V2.0 , (a red sticker near the light engine part says 2.0)

    1# settings: bitdepth, 1

                           pattern count 28, 

                          input trigger command

                          exposuretime 2second

     after uploading all patterns, click start, then click stop button immediately after clicking next  button, you may see the patterns flashing. 

    3#, No show after first next action can be observed much easily with combined odd and even pattern numbers.

    ( i know odd number is not selectable but still manually editable).

    First set settings bit depth 1, 29 pattern count, command trigger, 1 second exposure time, uploading 29 patterns, start, next ...., stop behaves normal

    then set setting bit depth 1, 28 pattern count, command trigger, 1 second exposure time, uploading 28 patterns,

    start, first next is always no show.

    Or some odd combination of actions can also lead to a reproducible first next no show problem

    Set mode to stored pattern sequence mode,

    set settings bit depth 1, pattern count 28, command trigger, 1sec exposuretime,

    upload 28 patterns

    Set display mode to Static image,

    Set display mode back to stored pattern sequence mode

    Start , first next is usually gives us no action.

    I have try other pattern count also, it seems 28 and 56 are easy to lead to such no show action.

    These thing are just annoying, currently we still can bypass such things. But we hope that LCr can behave much normally.

    regards

    Natty

  • Hello Natty,

    Thank you for providing details.

    #1. Yes we can see the problem.

    #3. Okay.

    We will work on these and get back to you. Basically, the LED enable and trigger signals are running for sometime after issuing a stop command. Ideally we could block them first then proceed for disabling the signals, this will avoid showing wrong data.

    Note, please understand that "STOP" is like aborting the current pattern display sequence, this will stop in the middle of display, so whatever gets displayed after issuing the command should be discarded or treated as don't care. 

    Regards,

    Sanjeev