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.
Part Number: DLPC350
I ask about the following problems. Please resolve this problem.
1.1 Problems where projected images are overlapped or solution file is not recognized when using two solution files(*.ini) alternately for long time(about 3 hours or more).
2 Operating Condition
2.1 Using the DLP350 controller on a custom board. It is communicating to the host PC via USB.
2.2 The images to be projected is stored in the flash memory.
2.3 First solution file(*.ini)
a Pattern sequence mode. Use of images stored in flash. Pattern exposure and period 40ms. Internal trigger(See projected image Fig.1)
2.4 The second solution file(*.ini)
a Pattern sequence mode. Use of images stored in flash. Pattern exposure and period 40ms. External trigger(See projected image Fig.2)
2.5 Applying the 1st solution file → Projection about 5 seconds → Applying the 2nd solution file → Projection about 5 seconds. If I repeat this process for more than 3 hours, the issue is caused.
2.6 ‘Image Load Timing’ was confirmed to be around 100ms. R, G, B channels are extracted and used in one image. So I think the ‘Image Load Timing’ is not a problem.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Azad:
Thanks for reply, Azad
Yes. It works well after booting.
Two solution files are well recognized and run for more than 3 hours, the same problems mentioned above will occur.
Reset the projector power will restore normal operation.
In reply to Neo Kim:
Hi Neo, Can you kindly provide us the INI file you are using? This will help us reproduce the problem. Thanks & Regards,
In reply to Hirak Biswas:
Thanks for reply, Hirak
I upload two ini files.
Do not need a firmware file(*.bin) to reproduce the problem?
The firmware that I use is confidential. So If you necessary, I will share the firmware file by replacing the another images.
Please reply. Regards, Neo
I’m using FW v3.1.
Here's an additional explanation of the experiment:
Window10: Both problems occur randomly. (Projected images are overlapped or the solution file is not recognized)
Window7: As a result of my experiment so far, only solution files are not recognized.
I will test again with FW v4.0. Could you tell me the difference between v3.1 and v4.0.
Below are the changes in v4.0 ; you can download; it from http://www.ti.com/tool/DLPR350
F/W Version 4.0.3:* Bug-Fixes: - Solved variable exposure pattern sequence frame freeze issue when running in Variable Exposure mode and setting the pattern exposure period as 10ms,20ms consequtively. - Fixed issue of mirrors getting unparked even after sending DMD park command. - Fixed I2C flash programming issue.
* Modifications: - Video sequences updated to support DLP4500AFQE, DLP4500AFQD and DLP4500NIRAFQD devices - Standby command (I2C: 0x07; USB: CMD2:0x02, CMD3:0x00) modified to support DLP4500AFQE, DLP4500AFQD and DLP4500NIRAFQD devices
* Known issue: - Displaying more than 1 pattern in external trigger mode will not work properly under the following condition i.e., display more than one pattern with a single external trigger with condition Pattern Period > Pattern Exposure by > 230us. Workaround - Keep Pattern Period = Pattern Exposure; for inserting dark time select Clear DMD after exposure option this will automatically insert 230us dark time. - Pausing and resuming the pattern sequence in Variable Pattern Exposure/Pattern Exposure mode causes the colors to shift by one pattern.
In the f/w file you can store one INI file at a time; I am not sure how you are using two INI files together.
If a post answers your question, please click on "Verify Answer" button
In reply to Sanjeev:
I share progress on the issue. And I will ask you additional questions.
First, I will explain the sequence that I used to help understanding. Note that both of the ini files have been changed to use external trigger.
Load the 1st ini file → Projector Send → Projector Validate → Projector Play → Generate the external trigger → Stop the external trigger → Projector Stop → Load the 2nd ini file → Projector Send → Projector Validate → Projector Play → Generate the external trigger → Stop the external trigger → Projector Stop
Projected images are overlapped or solution file is not recognized issues seem to be resolved.
I fixed the sequence that stop the external trigger before ini file load. Previously, only the projector was stopped(external trigger still generated) and the ini file was ‘Load→Send→Validate’.
The current 12-hour repeat test seems to be working normally.
Is it problematic to ‘Load & Validate’ the ini file while the trigger is being generated?
Could you provide C++ example code for 'ini file load → Send → Validate → Play → Stop'?
I have coded with reference to 'LightCrafter4500_GUI_Source_Code_v3.1.0'. And I want to check if it is correct.
Hi, Kindly check the DLPC350 Programmers Guide Chapter 4 for example sequences of commands to be sent for different configurations. Hope this helps to verify your code. Thanks & Regards,
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.