Electronic – extremely high frame rate oled

oled

What's the maximum dotclk frequency for a typical OLED display with serial input?
I've looked through some driver specs, example: SEPS525 but its not clear to me.
I'm looking to update a small resolution RGB oled (64×64) display at several hundred Hz for a perception/display experiment.

I think my best bet is to drive the dotclk and sync signals, while delivering the data 18 bits wide in serial format.

Best Answer

Almost none of the prefab display modules I've seen on the market give a "user" any significant control over when information is actually displayed; many don't even let the user know when information will be displayed. The normal design pattern is for the module to accept data from the user into a buffer at times of the user's choosing, and then display the contents of that buffer at a time of the module's choosing. In cases where both the module and the eyes of anyone looking at it are stationary, having the time between when data is fed to the module and when it appears on screen arbitrarily vary between 0-15ms won't be a problem. If the module or the user's eyes are moving, however, the scanning behavior may become quite relevant.

For a 64x64 module, I would expect that it should probably be possible to supply the module with a new frame's worth of data on every scan cycle; if you're interested in controlling or at least knowing exactly when things are displayed, however, you'll have to check the data sheets of any specific modules you're considering to see what sort of control you can get. I wouldn't say that modules "typically" give any control, but some might let you program a frame rate or scanning pattern that would fit your needs even if you have to do some trickery to achieve such behavior (e.g. if the module scans one line every 100us, allows a programmable number of scan lines, and counts scan lines with a down-counter that's reloaded when it hits zero, and if one wanted a frame rate of exactly 125Hz, one could have the scan-line count register programmed with a value of 81 for 7.809ms and a value of 80 for 101us. The timing on the module would then drift until the start of frame coincided with the time when the screen was programmed for 80 lines.