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.

Problem with EVM6500

Hello all,


I have a problem with EVM6500. Initially I had similar problem like Paolo's (device freeze when updating LUT). After  rebooting the device several times, the device goes into such state: D5 is not shining at all and the device is not detected by the PC. After connecting J11, the device can be detected by the PC and I refreshed the firmware (v.1.1.0). But this doesn't solve the problem.

Has anybody seen something like this?

Regards,

Ding

  • To be more specific, D6 never blinks and D5 is now in one of the following three states quite randomly:
    - not on at all
    - four long pulses and three short pulses
    - four long pulses and two short pulses

    Most of the time the dmd is not active (flat mirror) and very rarely the dmd is active but not showing any pattern (idle on mode i suspect).

    And the device is recognizable by PC and GUI only when J11 is connected. Finally, refreshing firmware doesn't solve the problem.
  • Hello Ding,

    Thank you for the detailed description on your issue. I believe your issue is indeed related to the thread you mentioned above. We are currently working on finding a root cause and solution and will update you as soon as we can. Thank you for your patience.

    Best regards,
    Trevor
  • Hello Trevor,


    Thank you for the reply! Have you found a solution yet?


    I have some update on the problem that might help you guys. I made an update of the firmware so that the board starts in standby mode. In this case I don't need the jumper at J11 anymore. Since the board starts at standby, I can connect it to the GUI directly. Nevertheless, if I try to change the mode in the GUI or just wait a couple of minutes, the GUI simply freezes. Also, updating LUT in the GUI gives an error message. In a word, the device does not work.


    One thing I have noticed in particular in the GUI is the setting of active blocks. Most of the getting method of the GUI still function properly even in standby mode. However, when I try to get the active block of the device, the "End Block" property returns something like a nil. And setting the block doesn't work no matter what block number I chose for start/end and returns an error message. Meanwhile, when I try to update LUT, the error is also "DMD block selection invalid for the bit depth" and the GUI freezes afterwards.

    As most of the other set/get methods function properly, is it possible that this function regarding active blocks is causing all the trouble? I noticed in the release note of firmware 1.1 that block load is a new functionality. I could not find the previous version of the firmware anywhere from the internet. Could you provide this older version (1.0.0) so that I could test with my device?


    Thank you very much!

    Best,

    Ding

  • Hello Ding,

    I have sent you an E2E friend request. If you accept this, I will be able to send you a private message. I would like to talk more about the issues you are seeing and your application.

    Thanks,
    Trevor