tft lcd led backlit free sample

The wide range of conditions over which LCD monitors are used means that it is desirable to produce displays whose luminance (brightness) can be altered to match both bright and dim environments. This allows a user to set the screen to a comfortable level of brightness depending on their working conditions and ambient lighting. Manufacturers will normally quote a maximum brightness figure in their display specification, but it is also important to consider the lower range of adjustments possible from the screen as you would probably never want to use it at its highest setting. Indeed with specs often ranging up to 500 cd/m2, you will certainly need to use the screen at something a little less harsh on the eyes. As a reminder, we test the full range of backlight adjustments and the corresponding brightness values during each of our reviews. During our calibration process as well we try to adjust the screen to a setting of 120 cd/m2 which is considered the recommended luminance for an LCD monitor in normal lighting conditions. This process helps to give you an idea of what adjustments you need to make to the screen in order to return a luminance which you might actually want to use day to day.

Changing the display luminance is achieved by reducing the total light output for both CCFL- and LED-based backlights. By far the most prevalent technique for dimming the backlight is called Pulse Width Modulation (PWM), which has been in use for many years in desktop and laptop displays. However, this technique is not without some issues and the introduction of displays with high brightness levels and the popularisation of LED backlights has made the side-effects of PWM more visible than before, and in some cases may be a source of visible flicker, eyestrain, eye fatigue, headaches and other associated issues for people sensitive to it. This article is not intended to alarm, but is intended to show how PWM works and why it is used, as well as how to test a display to see its effects more clearly. We will also take a look at the methods some manufacturers are now adopting to address these concerns and provide flicker-free backlights instead. As awareness grows, more and more manufacturers are focusing on eye health with their monitor ranges.

1) Frequency –The backlight is cycled on and off very rapidly, and this cycling typically occurs at a fixed frequency (in Hz). How fast this cycling occurs can impact whether flicker is visible or perceivable to the user, with higher frequencies being potentially less problematic. PWM has been known to operate at low frequencies of 180 – 240Hz for example which are likely to be more problematic than higher frequencies ranging up in to the Kilohertz range (e.g. 18,000Hz).

2) Modulation –The modulation of the cycling has an impact on the perceived brightness, and this describes the difference between the luminance in an “on” and in an “off” state. In some examples the backlight is completely turned off during the cycle so it is literally being turned on/off rapidly across the full brightness adjustment range. In those examples the luminance output is controlled really by the duty cycle only (see point 3). In other examples the backlight is not always being completely turned off but rather the voltage applied to the backlight is being rapidly alternated, resulting in less extreme differences between the on and off states. Often this modulation will be narrow in the high brightness range of the display, but as you reduce further, the modulation becomes wider until it reaches a point where the backlight is being switched completely off. From there, the change in the duty cycle (point 3) controls the further changes in the luminance output.

3) Duty Cycle – The fraction of each cycle for which the backlight is in an “on” state is called the duty cycle. By altering this duty cycle the total light output of the backlight can be changed. As you reduce the brightness to reach a lower luminance, the duty cycle becomes progressively shorter, and the time for which the backlight is on becomes shorter, while the time for which it is off is longer. This technique works visually since cycling the backlight on and off sufficiently fast means the user cannot see this flickering, because it lies above their flicker-fusion threshold (more on this later).

The luminance of LED backlights can be adjusted greatly by altering the current passing through them, though this has the effect of altering the colour temperature slightly. This analogue approach to LED luminance is also undesirable since the accompanying circuits must take into account the heat generated by the LED’s. LED’s heat up when on, which reduces their resistance and further increases the current flowing through them. This can quickly lead to runaway current use in very high-brightness LED’s and cause them to burn out. Using PWM the current can be forced to hold a constant value during the duty cycle, meaning the colour temperature is always the same and current overloads are not a problem.

While PWM is attractive to hardware makers for the reasons outlined above, it can also introduce distracting visual effects if not used carefully. Flicker from LED backlights is typically much more visible than for older CCFL backlights at the same duty cycle because the LED’s are able to switch on and off much faster, and do not continue to “glow” after the power is cut off. This means that where the CCFL backlight showed rather smooth luminance variation, the LED version shows sharper transitions between on and off states. This is why more recently the subject of PWM has cropped up online and in reviews, since more and more displays are moving to W-LED backlighting units now.

So how fast is PWM cycling backlights on and off? This seems to depend on the backlight type used, with CCFL-based backlights nearly all cycling at 175Hz or 175 times per second. LED backlights have been reported typically running from 180 – 420Hz, with those at the lower end flickering much more visibly. Some have even faster frequencies of >2000Hz so it really can vary. While this might seem too fast to be visible, keep in mind that 175Hz is not much faster than the 100-120Hz flicker observed in lights connected directly to the mains power.

It is also important to distinguish the difference between flicker in CRT displays and CCFL and LED backlit TFT displays. While a CRT may flicker as low as 60Hz, only a small strip is illuminated at any time as the electron gun scans from top to bottom. With CCFL and LED backlit TFT displays the entire screen surface illuminates at once, meaning much more light is emitted over a short time. This can be more distracting than in CRTs in some cases, especially if short duty cycles are used.

The flicker itself in display backlights may be subtle and not easily perceptible for some people, but the natural variation in human vision seems to make it clearly visible to others. With the use of high-brightness LED’s on the rise it is becoming increasingly necessary to use short PWM duty cycles to control brightness, making flicker more of a problem. With users spending many hours every day looking at their monitors, shouldn’t we consider the long term effects of both perceptible and imperceptible flicker?

A much better method of course would be to purchase a display not relying on PWM for dimming, or at least one which uses a much higher cycling frequency. Few manufacturers seem to have implemented PWM at frequencies that would limit visible artefacts (well above 500Hz for CCFL and above 2000 Hz for LED). Additionally, some displays using PWM do not use a 100% duty cycle even at full brightness, meaning they will always produce flicker. Several LED-based displays may in fact be currently available which do not use PWM, but until backlight frequency and modulation become listed in specifications it will be necessary to see the display in person. Some manufacturers promote “flicker free” monitors in their range (BenQ, Acer for example) which are designed to not use PWM at all and instead use a Direct Current (DC) method of backlight dimming. Other manufacturers such as Eizo talk about flicker free backlights but also list a hybrid solution for their backlight dimming, where PWM is used for some of the brightness adjustment range at the lower end. In fact it seems an increasingly common practice for a screen to be PWM free down to a certain point, and then fro PWM to be used to really drive down the minimum luminance from there.

Depending on the monitor several additional effects may be visible. CCFL-based backlights often show different colours at the start and end of each cycle, which means the phosphors used respond at different rates. LED-based backlights often use a higher cycling frequency than CCFL-based, and more rapid camera movement may be needed to easily see them. Dark stripes between cycles mean that the PWM duty cycle has been reduced to such an extent that no light is emitted for part of the cycles.

Asus PA248Q – W-LED backlight. At 100% brightness we see a constant luminance output and a straight line, as there is no need for the backlight to be cycled. At 50% you can see PWM controls the backlight on and off. The modulation is always 100%, but the luminance reduction is controlled by the duty cycle which becomes progressively shorter. You can see much shorter “on” peaks in the 0% brightness graphs. We measure the frequency at 180Hz which is fairly typical.

BenQ GW2760HS – W-LED backlight. At all brightness settings the luminance output is a flat line, showing no PWM is being used. This is part of BenQ’s flicker free range.

The oscilloscope graphs can also allow us to examine the behaviour of the luminance output. Above is a typical W-LED backlight dimmed to 0% where PWM is used. You can see the changes between on and off are very steep and sudden, as the LED backlight is able to turn on and off very rapidly. As we’ve already discussed this can lead to potentially more noticeable flicker and associated issues as the changes are more pronounced.

The oscillographs for a typical CCFL display using PWM at 0% looks like the above. You can see the transitions from on to off are less sudden as the phosphors don’t go dark as quickly as with LED backlight units. As a result, the use of PWM may be less problematic to users.

As we said at the beginning, this article is not designed to scare people away from modern LCD displays, rather to help inform people of this potential issue. With the growing popularity in W-LED backlit monitors it does seem to be causing more user complaints than older displays, and this is related to the PWM technique used and ultimately the type of backlight selected. Of course the problems which can potentially be caused by the use of PWM are not seen by everyone, and in fact I expect there are far more people who would never notice any of the symptoms than there are people who do. For those who do suffer from side effects including headaches and eye strain there is an explanation at least.

With the long term and proven success of a technology like Pulse Width Modulation, and the many years of use in CCFL displays we can’t see it being widely changed at any time soon to be honest, even with the popular move to W-LED backlit units. It is still a reliable method for controlling the backlight intensity and therefore offering a range of brightness adjustments which every user would want and need. Those who are concerned about its side effects or who have had problems with previous displays should try and consider the frequency of the PWM in their new display, or perhaps even try and find a screen where it is not used at all in backlight dimming. Some manufacturers are proactively addressing this concern through the use of flicker free backlights, and so options are emerging which do not use PWM.

LCD (Liquid Crystal Displays) have two options or display modes.Positive mode (dark characters on a light colored background) and negative mode (lighter colored characters on a darker background).

Negative mode displays need backlit in order to be seen. They normally use transmissive polarizers. They have better contrast and wider viewing angles in the indoor dim environment. The readability is much better than positive displays.

Of course, we can always use LED backlight in the LCD module with fewer LED chips and turn off LED backlight when not use to save power. When can also add transflective polarizer to some negative LCDs to make it sunlight readable, but the contrast will be compromised.

Positive and negative mode concept is not only limited to monochrome LCD displays (LCD panels, character LCDs, graphic LCDs etc.), it also uses for color displays, or even other display technologies.  We will categorize the displays as below,

Character LCD modules (Alphanumeric LCD display modules) with character sets: 8×1 LCD display, 8×2 LCD display, 16×1 LCD display, 16×2 LCD display, 16×4 LCD display, 20×2 LCD display, 20×4 LCD display, 24×2 LCD display, 40×2 LCD display, 40×4 LCD display. COB (Chip on Board) bonded, 4 or 8 bits parallel, SPI, I2C interface

Graphic LCD modules with dot matrix sets 122×32, graphic LCD display, 128×64 graphic LCD display, 192×48 graphic LCD display,192×64 graphic LCD display,240×64 graphic LCD display,240×128 graphic LCD display,240×160 graphic LCD display with different color LED backlights, with COB and COG (Chip on Glass) assembling technologies

Monochrome and Color Graphic OLED modules with dot matrix sets 128×32 graphic OLED display,128×64 graphic OLED display, 128×96 graphic OLED display, 160×128 graphic OLED display, 128×128 graphic OLED display, 256×65 graphic OLED display

FocusLCDs.com sent me a free sample of a 4x3” TFT LCD (P/N: E43RG34827LW2M300-R) to try out. This is a color active matrix TFT (Thin Film Transistor) LCD (liquid crystal display) that uses amorphous silicon TFT as a switching device. This model is composed of a Transmissive type TFT-LCD Panel, driver circuit, backlight unit. The resolution of a 4.3” TFT-LCD contains 480x272 pixels, and can display up to 16.7M colors.

For this project, you would need the RA8875 driver board (available at AdaFruit for US$35) to interface the TFT display to the Arduino. It comes with a header which you can solder on as needed.

In this Arduino touch screen tutorial we will learn how to use TFT LCD Touch Screen with Arduino. You can watch the following video or read the written tutorial below.

The next example is controlling an RGB LED using these three RGB sliders. For example if we start to slide the blue slider, the LED will light up in blue and increase the light as we would go to the maximum value. So the sliders can move from 0 to 255 and with their combination we can set any color to the RGB LED,  but just keep in mind that the LED cannot represent the colors that much accurate.

As an example I am using a 3.2” TFT Touch Screen in a combination with a TFT LCD Arduino Mega Shield. We need a shield because the TFT Touch screen works at 3.3V and the Arduino Mega outputs are 5 V. For the first example I have the HC-SR04 ultrasonic sensor, then for the second example an RGB LED with three resistors and a push button for the game example. Also I had to make a custom made pin header like this, by soldering pin headers and bend on of them so I could insert them in between the Arduino Board and the TFT Shield.

Here’s the circuit schematic. We will use the GND pin, the digital pins from 8 to 13, as well as the pin number 14. As the 5V pins are already used by the TFT Screen I will use the pin number 13 as VCC, by setting it right away high in the setup section of code.

I will use the UTFT and URTouch libraries made by Henning Karlsen. Here I would like to say thanks to him for the incredible work he has done. The libraries enable really easy use of the TFT Screens, and they work with many different TFT screens sizes, shields and controllers. You can download these libraries from his website, RinkyDinkElectronics.com and also find a lot of demo examples and detailed documentation of how to use them.

After we include the libraries we need to create UTFT and URTouch objects. The parameters of these objects depends on the model of the TFT Screen and Shield and these details can be also found in the documentation of the libraries.

Next we need to define the fonts that are coming with the libraries and also define some variables needed for the program. In the setup section we need to initiate the screen and the touch, define the pin modes for the connected sensor, the led and the button, and initially call the drawHomeSreen() custom function, which will draw the home screen of the program.

So now I will explain how we can make the home screen of the program. With the setBackColor() function we need to set the background color of the text, black one in our case. Then we need to set the color to white, set the big font and using the print() function, we will print the string “Arduino TFT Tutorial” at the center of the screen and 10 pixels  down the Y – Axis of the screen. Next we will set the color to red and draw the red line below the text. After that we need to set the color back to white, and print the two other strings, “by HowToMechatronics.com” using the small font and “Select Example” using the big font.

drawDistanceSensor(); // It is called only once, because in the next iteration of the loop, this above if statement will be false so this funtion won"t be called. This function will draw the graphics of the first example.

getDistance(); // Gets distance from the sensor and this function is repeatedly called while we are at the first example in order to print the lasest results from the distance sensor

So the drawDistanceSensor() custom function needs to be called only once when the button is pressed in order to draw all the graphics of this example in similar way as we described for the home screen. However, the getDistance() custom function needs to be called repeatedly in order to print the latest results of the distance measured by the sensor.

Ok next is the RGB LED Control example. If we press the second button, the drawLedControl() custom function will be called only once for drawing the graphic of that example and the setLedColor() custom function will be repeatedly called. In this function we use the touch screen to set the values of the 3 sliders from 0 to 255. With the if statements we confine the area of each slider and get the X value of the slider. So the values of the X coordinate of each slider are from 38 to 310 pixels and we need to map these values into values from 0 to 255 which will be used as a PWM signal for lighting up the LED. If you need more details how the RGB LED works you can check my particular tutorialfor that. The rest of the code in this custom function is for drawing the sliders. Back in the loop section we only have the back button which also turns off the LED when pressed.

drawDistanceSensor(); // It is called only once, because in the next iteration of the loop, this above if statement will be false so this funtion won"t be called. This function will draw the graphics of the first example.

getDistance(); // Gets distance from the sensor and this function is repeatedly called while we are at the first example in order to print the lasest results from the distance sensor