DLPC350: After update of DLPR350PROM from 3.1.0 to 4.0.3 we observe glitch on trigger out 1 for all settings of rising edge delay except 0x00

Hello Anders,

Sorry  about the issue.Could you upload a screenshot of the GUI showing how you are setting up the unit. Could you please also confirm if this is the Lightcrafter4500 EVM or your own hardware?

Thanks,
Kyle

Hi Kyle,

We are using I2C commands to control the dlpc350 which sits on our own hardware. Are there any differences between the two firmware versions that we need to be aware of? Why would the same i2c commands with same timing cause different behavior between the two dlpc350-firmwares? None of the listed changes in the changelog seems relevant to our use case. (no variable exposure, pattern timing = exposure timing, not using standby command)

Hi again Kyle,

We have now reproduced the issue with Lightcrafter 3.1.0 GUI, I've attached a couple of *.ini files with "solutions", so you can just use the "apply solution" button in lightcrafter on a standard Lightcrafter4500 EVM to reproduce the issue. 

Procedure to reproduce:

1. Hook up oscilloscope to trig1 output, trigger on pulse-width < 200us.
2. Load dlpc350 device with 4.0.3 firmware.
3. Apply "setup_with_extra_pulse.ini"
4. validate pattern sequence
5. play pattern sequence, watch for short ~20us pulse 230us after first frame trigger.

Then to check that 0 on trigger 1 rising edge delay removes the pulse, apply "rising_trigger_0_no_extra_pulse.ini" solution.

If you also try with rising edge delay register = 0x01, the pulse will be very short, 100ns long. it seems to increase in length with higher rising edge delay.

To verify that the older 3.1.0 firmware does not have this behaviour:

1. Load dlpc350 device with 3.1.0 firmware.
2. Apply the "setup_with_extra_pulse.ini" solutions and check that no extra pulse is present, regardless of rising edge delay.

/cfs-file/__key/communityserver-discussions-components-files/94/setup_5F00_with_5F00_extra_5F00_pulse.ini

/cfs-file/__key/communityserver-discussions-components-files/94/rising_5F00_trigger_5F00_0_5F00_no_5F00_extra_5F00_pulse.ini

Hi again!

Thanks for confirming this issue and committing to fixing it in the next release. Any idea about the time-frame for this maintenance release. (weeks or months?).  We have indications from our supplier that the new revision DMD can be present in shipped modules as early as 30th of September (in 7 days).

Hi again,

A test build would be appreciated, to confirm the issue is resolved earlier.  

Is there any way for us to detect/know which revision of DMD the DLPC350 is connected to? What will happen if we continue production but end up with old firmware and new DMD-revision? 

-Anders