• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 337 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DLPDLCR230NPEVM: 240Hz, image not stable and jittering

David Stephanson
Prodigy 20 points
Part Number: DLPDLCR230NPEVM
Other Parts Discussed in Thread: DLPC3436

Hello everyone,

I'm trying to reach high frame rates with the DLPDLCR230NPEVM but I'm barely able to reach 60Hz and the frames jitter while displaying anything other than a still image. The other problems I've encountered until now were solved by finding the answers in the forum. 

What I've done until now :

  • Updated the firmware on the DLPDLCR230NPEVM to the latest one (7.4.0)
  • Installed the WiringPi library manually to be able to drive the Raspberry Pi's GPIO like the i2c.py is supposed to and put the gpio drive power to 7 or more
  • Changed the config.txt to the one in the manual and change the HDMI Timing to : hdmi_timings=960 0 8 32 40 540 0 56 6 6 0 0 0 240 0 151756000 3 
  • In the init_parallel_mode.py, after the black curtain to disable the XPR actuator added the line : Summary = WriteActuatorGlobalDacOutputEnable(Set.Disabled)
  • To solve the issue of the screen being shifted, added the WriteXprFpgaRegister(Address, Data) function described in https://e2e.ti.com/support/dlp-products-group/dlp/f/dlp-products-forum/1054799/dlpdlcr230npevm-in-960x540-240hz and the line Summary = WriteXprFpgaRegister(0x508, 0x1B58) before disabling the black curtain image

The XPR actuator should be disabled but just to be sure I used the sample06_status.py to see the state of the XPR and whether I set it to Set.Enabled or Set.Disabled, the result would be the same:

'ActuatorDriveEnable': 0,
'ActuatorPwmGenSource1080POnly': 1
'ActuatorConfigurationError': 1,
'ActuatorWatchdogTimerTimout': 0,
'ActuatorSubframeFilteredStatus': 0,

I've included two videos, one where the image is static and one where a 60fps video is playing.

Click here to play this videoClick here to play this video

Thank you for your help,
David

  • 0
    TI__Expert 5750 points

    Hello David,

    • Updated the firmware on the DLPDLCR230NPEVM to the latest one (7.4.0)
      • The current version of the EVM FW is 7.3.14. Please confirm that you are using the FW for the EVM product page and not a generic DLPC3436 FW.
    • Installed the WiringPi library manually to be able to drive the Raspberry Pi's GPIO like the i2c.py is supposed to and put the gpio drive power to 7 or more
      • This library has been deprecated and the EVM typically doesn't need it when running 1080p @ 60 Hz. You may need to look through other forums to see how to get this library to work.
    • Changed the config.txt to the one in the manual and change the HDMI Timing to : hdmi_timings=960 0 8 32 40 540 0 56 6 6 0 0 0 240 0 151756000 3
      • There may need to be some fine tuning with the video data settings. This timing parameter would have only been tested @ 1080p. I have no recommendations.
  • 0 in reply to John McKnight
    Prodigy 20 points

    Hello John,

    I want to be able to reach the 240Hz at 960x540 which the DLPDLCR230NPEVM is advertised to be able to do with some tuning. 

    I updated the firmware version to 7.4.0 because I wasn't able to reach it with firmware version 7.3.14 and using TI's DLP Pico Firmware Selector, I found there was a new one. I have now rolled back to 7.3.14 as per your advice.

    The "official" WiringPi has been deprecated and is not installed be default on Raspberry Pi's but has been copied. It is now available and is working. It drives the gpio strength higher reduces the jitter.

    As stated by your colleague, Cody Smith, in this forum post: https://e2e.ti.com/support/dlp-products-group/dlp/f/dlp-products-forum/1054640/dlpdlcr230npevm-can-i-use-960x640-240hz-with-the-provided-firmware/3901877?tisearch=e2e-sitesearch&keymatch=DLPDLCR230NPEVM%2520240#3901877 :

    # 960 x 540 @ 240 Hz Timings
# Recommend use at GPIO DRIVE 7
#hdmi_timings=960 0 8 32 40 540 0 56 6 6 0 0 0 240 0 151756000 3

    There are some timings which were used to reach 240Hz 960x540 and it requires to drive the GPIOs higher than default. 

    I have now been able to stop the jitter of the image by changing the pixel clock to 125000000 but I can still see with a high speed camera that the XPR is still active and not disabled as it should be with the WriteActuatorGlobalDacOutputEnable(Set.Disabled) function. Could there be an other function which is still activating it ? Maybe the "ActuatorPwmGenSource1080POnly" which is not at 0 could be deactivated by a function which is not in the available ones ?

    I'm stating to believe this DLPDLCR230NPEVM might be defective but can't be sure. 

  • 0 in reply to David Stephanson
    TI__Expert 3905 points

    Hello David,

    Do you have another EVM with you to test whether your current system is defective?

    Best,

    Maxine

  • 0 in reply to Maxine Cabrasawan
    Prodigy 20 points

    Hello Maxine,

    I do not have another DLPDLCR230NPEVM with me. The reason I think it might be defective is that there is no difference in the image when disabling the XPR with the line of code. Also when we received the EVM 1-2 weeks ago, the front lens seemed to have scratches on it like in the picture of one of the latest forum posts so it might not be brand new even though we bought if from a reputable supplier. 

    Best,
    David 

  • 0 in reply to David Stephanson
    TI__Mastermind 23070 points

    Hello David,

    The difference in image with and without may not easily visible with naked eye for all content. We will discuss internally and get back to you.

    regards,

    Vivek

  • +1 in reply to David Stephanson
    TI__Expert 5750 points

    Hello David,

    Video timings are going to have to be figured out with trail and error, and changes in the GPIO drive strength. This is a timing we have used for test HW on our end. I will note that VBP must be > 0.103 ms. This timing is used from a traditional video generator. When it comes to the Raspberry Pi there is more trial and error that has to be done to find a suitable timing setting. That is something the user will have to figure out. The limitation of video timings comes from the RPi HW and forcing it to send data this fast, clearly, and with stability.