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.

Control the Lightcrafter by using Microcontroller

Hallo Sanjeev,

Sorry to bother you again. I have now two Questions:

1. I have about 300 1 bit Patterns to display by using external Trigger. For every pattern it needs to be lighting for  minimum 5seconds, but it seems that the exposure time can not be over 2seconds. How can i solve this problem?

2. Is it possible to control the LCr by using a microcontroller or mocroprocessor, but without using the PCs?

 

Could you please provide me some suggestions?

Thank you very much in advance.

best regards,

Di

 

  • Hi Di,

    1. The 2.0 Seconds exposure time limitation for 1-bit pattern sequence is applicable to AUTO trigger mode. Since you are using 'External Trigger' what you are asking is definitely possible.

    Please make following settings:

    • As usual configure 1-bit pattern sequence mode and upload the patterns. One important thing is that - Set Exposure Time = 0. When you set exposure to ZERO the pattern is put on as long as possible till the next trigger comes.
    • One caution - Continuously driving LEDs for long time can damage the LED and/or LED Driver circuit. So you need to be careful in choosing the proper timing.
    • Due to above 'caution' we have put a protective logic in the MSP430 code this will basically turn OFF LED if it is OK more than for 2.0-3.0 seconds. We can work it to further. I suggest you to experiment initially with short duration.

    2. Definitely, you know the DM365 does bulk of job of configuring the system to operate the hardware in the mode you are requestion. Right now DM365 communicates via ethernet over USB port. To simplify based on the user request it is possible make is communicate over I2C port. Then it is possible to control the device easily by a microcontroller.

    Another option, since DM365 itself is embedded application processor, you can add your control logic in it. But for this you will have to wait long because the DM365 software is not publicly available.

    Regards,

    Sanjeev

  • Thanks Sanjeev,

    But for the first question i want to at first display a pattern for 5seconds, then take a pause for 3seconds (no display), then the second pattern will be put on for  5seconds, then pause, ......

    It means, for example my external trigger period is 8seconds,  i wana take 5seconds to display a pattern, and the rest 3 seconds for pause. So i think i cannot just set Exposure Time = 0, because if so it would be no pause time. Am i right?

     

    regards,

    Di

  • Hi Di,

    Yes you are correct.

    Setting 0 exposure display the pattern indefinitely. It goes back to same thing, the existing software DM365 v3.31 the maximum exposure you can keep it on it 2.0 Seconds for 1-bit. You can only do 2.0 pattern display and any length of pause in case of external trigger.

    Since you are using around 300 1-bit patterns, I have one more suggestion. Convert 1-bit patterns to 2-bit patterns then upload them. With 2-bit pattern you can easily set exposure time of 5.0Seconds. Then you can run external hardware triggers at 8.0 Seconds.

    Regards,

    Sanjeev

     

  • Hi Sanjeev,

    Thank you very very much.

    But as you said, the LED will be turned OFF if it is  more than for 2.0-3.0 seconds,  even if i do that (Convert 1-bit patterns to 2-bit patterns) , and the exposure time of 5.0Seconds can be set,  am i correct?

    regards,

    Di

  • Hi Sanjeev,

    For 1-bit, 0 exposure the LEDs are driven continuously until the next trigger. So LEDs will be turned OFF.

    For more than 1-bit pattern LEDs will not be running continuously LEDs will turned of for short duration in uSec between loading each bit planes. So you can use 2-bit patterns 5.0 seconds safely.

    Regards,

    Sanjeev

     

  • Thanks a lot!! I have tried it, it worked. But it seems each pattern can displayed maximum 5.1seconds, the more will never be reached. right?