I am getting a consistent error with the DLPC350 chip. For our use case we use a computer with Windows 10 with a projector. we need the projector to be in Pattern mode but we have found when we send a command for the projector to go back to Video mode there is a chance that the DLPC350 chip will freeze and no longer respond to commands. We have had this issue with both Keynote Photonics projectors and ones from Anhua.
I have written a testing program (see attachment) to really nail down this issue and I am able to reproduce the error by calling the LC45 Display Mode command (USB:0x1b,0x1a) with a value of 0 (Video mode). Running this command repeatedly with a HDMI valid connection will cause the chip to freeze in usually under 30 tries. Interestingly, A HDMI cable needs to be plugged into the device for the freeze to occur. When i say 'freeze' i mean, the chip will no longer respond to commands resulting in having to be power cycled to work again.
To help debug the issue
* I have a testing program (testusb.exe) I have written in C.
* My program sends commands via USB.
* I have run this test on multiple WIN 10 computers.
* I have run this test on firmware versions: 4.0.3 and the latest 4.4.0.
* I have run this test on projectors by Anhua and Keynote Photonics.
* Freezing only happens if there is a HDMI plugged into the device - NO HDMI plugged in no error.
My testing program basically works like this :
0 - start loop
1 - Get Projector's Firmware Tag
2 - Set Buffer Freeze to 1
3 - Set Display Mode to 0 (Video mode)
4 - Set Display Mode to 1 (Pattern mode)
5 - Set Buffer Freeze to 0
6 - Wait for 300 milliseconds
7 - end of loop repeat
In usually under 30 loops the chip will freeze and no longer respond to commands. When it is in this frozen state. My testing program will no longer be able to get the Firmware Tag, and if I run the GUI the GUI doesn't find the projector (it says 'connected' but the firmware version and tag are written as 'xxxxxxxxx') To get the projector working again I have to turn it off and on again.
Note : The test will still freeze the chip if I just loop getting the projector's firmware tag and setting the display mode to 0 repeatedly. No real need for the other commands but they are there for consistency and so i can get a visual that the projector is switching modes.
Again - strangely - If I run the same test without a HDMI connection it doesn't freeze. I have tried various different monitors and displays for the HDMI (even having the HDMI connected to another computer from the USB cable's source - so having a seperate computer for each cable!)
To help debug the issue
* I have a testing program (testusb.exe) I have written in C.
* My program sends commands via USB.
* I have run this test on multiple WIN 10 computers.
* I have run this test on firmware versions: 4.0.3 and the latest 4.4.0.
* I have run this test on projectors by Anhua and Keynote Photonics.
* Freezing only happens if there is a HDMI plugged into the device - NO HDMI plugged in no error.
My testing program basically works like this :
0 - start loop
1 - Get Projector's Firmware Tag
2 - Set Buffer Freeze to 1
3 - Set Display Mode to 0 (Video mode)
4 - Set Display Mode to 1 (Pattern mode)
5 - Set Buffer Freeze to 0
6 - Wait for 300 milliseconds
7 - end of loop repeat
In usually under 30 loops the chip will freeze and no longer respond to commands. When it is in this frozen state. My testing program will no longer be able to get the Firmware Tag, and if I run the GUI the GUI doesn't find the projector (it says 'connected' but the firmware version and tag are written as 'xxxxxxxxx') To get the projector working again I have to turn it off and on again.
Note : The test will still freeze the chip if I just loop getting the projector's firmware tag and setting the display mode to 0 repeatedly. No real need for the other commands but they are there for consistency and so i can get a visual that the projector is switching modes.
Again - strangely - If I run the same test without a HDMI connection it doesn't freeze. I have tried various different monitors and displays for the HDMI (even having the HDMI connected to another computer from the USB cable's source - so having a seperate computer for each cable!)
The program to reproduce the error is here
