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.

DLPC3478: BUSY signal for Write Pattern Order Table Entry

Part Number: DLPC3478
Other Parts Discussed in Thread: DLPA3000,

Hello Ti experts,

I have custom board with DLPC3478 and DLPA3000. I send commands to DLPC3478 to update internal pattern table via stm32. After i call project pattern (9Eh), it does not project patterns correctly (mostly projects only 1 pattern or no patttern). If i put 3ms delay between Write Pattern Order Table Entry and Write Internal Pattern Control, it projects patterns corretly. Is there a way to check Write Pattern Order Table Entry command processed and ready to project pattern signal? Is there a busy signal for command processing?

Best,
John

  • Hi John,

    Depending on your pattern setup there is some variable delay before the controller is ready to begin displaying the pattern set due to internal processing. In order to determine when all internal processing is complete we have a "pattern ready" signal which must be enabled through "Write Pattern Ready Configuration" (94h) command. This is a hardware signal which will go high when the controller is ready to display the pattern set, you can also read the status via the "Read Internal Pattern Status" (9Fh) command if the hardware signal is unavailable. 

    Best,

    Maximus

  • Hi Maximus,

    I enabled pattern read signal with 'Write Pattern Ready Configuration' command but i get pattern ready for tıme for example 43 ms for 10 exposure 15 pre and post exposure with run once command. After that'i always get not ready with command 'Read Internal Pattern Status. I am also using firmware v8.0.1.

    Can you explain when this pattern read should be ready? If i change operating mode this settings will be preserved?

    Best,

    John.

  • Hi John, 

    I'm not sure I understand the problem you are seeing. Are you saying you only get the pattern ready signal once and then never again? Can you explain further what you are trying to do?

    Best,

    Maximus

  • Hi Maximus,

    Yes i observe strange behaviour about pattern ready status, after proj on i set it to internal pattern mode and send write pattern ready configuration. After that i send start projection command(run once) and check pattern ready status, i see only couple of ms pattern ready is high, and never high again. 

    Best, 

    John

  • Hi John,

    Please give me some time to get back to you. 


    Best,

    Maximus

  • Hi Maximus,

    I am using in free run mode, is this signal valid for the free run mode or only Trigger In mode?

    Best,

    John.

  • Hi John,

    You should be able to still use this as an indication in free running mode without using a trigger in. Can you describe your process leading up to the the signal going low? The signal should follow the graph below.

    Best,

    Maximus

  • Hi Maximus,

    The process goes like this:

    -PROJ_ON

    -100 ms delay

    -PROJ_ON

    -WriteOperatingModeSelect: Internal Patterns

    -WriteTriggerOutConfig: trigger out 2

    -WriteRGBLedEnable: true

    -WritePatternReadyConfiguration: pattern ready enable

    -WritePatternOrderTable: only project one pattern

    -in while loop: ReadInternalPatternStatus: ready pattern ready status: always 0 

    If i call project pattern (WriteInternalPatternControl) before the ReadInternalPatternStatus it goes high for a couple of ms (close to pattern projection time) then goes low.

    Best, John

  • Hi John,

    I have checked back with our experts and we have realized the pattern ready signal cannot be used in this way, my apologies for this mistake. I will reach out and see if we can come up with another way for you to minimize the delay between the controller being ready and you sending your WritePatternControl command. You are correct there will be some variable delay after writing the pattern configuration, this should not be more than 10ms, please give me some time to get back to you on this. 

    Best,

    Maximus

  • Hi John,

    I will go ahead and close this thread as we have taken support offline.

    Best,

    Maximus