tft lcd editor brands

Whether you’re using a point and shoot model or a top-of-the-line DSLR, you can count on a TFT LCD display screen to give you the photo preview and the photo itself. The technology is so effective that rarely do you need the optical viewfinder to preview your shot. It especially comes handy for self-portraits, wherein the users can invert the lens to look at their selfies.

Everybody expects the subject of their photos to appear as they are in real life. So apart from the viewfinder, the preview screen needs to reflect that. TFT LCD screens can show up to 16.7 million colors, so imagine how accurate they can be!

The technology of TFT can allow the photographer to make last-minute composition changes to their photos. There’s still time for a change of tux or an extra flower in the shot, thanks to LCD previews. Can you imagine how good it is to get the ideal shot, with little need for photo-editing later on? Such is the convenience TFT gives.

TFT LCD offers a quality resolution at any screen size. When you’re taking a picture using a TFT LCD module camera, you lock in every detail — contrast, light, and expression — in your resulting photo. This is because of TFT’s in-plane switching (IPS) technology, which improves on basic LCD’s color and angle display. Photographers value accuracy above all, and TFT’s IPS does the trick for them.

Besides being cheaper than OLED technology, TFT LCD still allows for less energy consumption, as well as quicker responsiveness. Photographers value long battery life and camera response time, especially when covering personal events and news beats. The efficiency of TFT ensures that they’ll capture more memories and tell the full story.

For the discerning camera manufacturer, having a quality TFT display is a must. No matter how large your screen, you can be sure of the most precise images around. Get it only from a supplier who can offer it at affordable rates.

Let our team at Microtips Technology USA help you with your camera TFT screens. For nearly 30 years, we have been supplying the best TFT module displays in the market. Whether it’s the industrial sector or any industry, we have displays perfectly matched to your field. In addition, our displays are readily available and offered at a reasonable price. Contact us immediately, so we can make TFT LCD work for you!

This document goes through various features of the current Nextion Editor. The Nextion Editor is used to rapidly create Human Machine Interface GUIs for Nextion HMI devices. As such the GUI can be created within Hours instead of Weeks, and Days instead of Months. So while we won’t be covering basics such as opening a file, we will point out somethings that might prove helpful to know, or reminders need be made.

Note: Nextion Editor has indeed evolved since its early beginnings, so I would like to take a moment for a quick review. As time has passed, many additional features and bug fixes were incorporated. The Nextion Editor is not expected to retain every previous behaviours between versions exactly. With the new, then there are indeed new behaviours and new possibilities.

The pandemic had created global supply shortages and to meet these challenges while keeping with Nextion quality then second source components/ICs were indeed needed. This said, while elder devices only require firmware level code to communicate with primary sources ICs, the newer devices with secondary source ICs (visually identified with QR codes on the microSD slot) indeed require more recent versions of the Nextion Editor (v1.63.3 and later recommended) for the firmware to communicate with the secondary source ICs. As such, newer devices with secondary source ICs can not make use of elder versions of the Nextion Editor (such as v0.38, or LTS) before such firmware level code was incorporated into the Nextion Editor version firmware.

Since 2020, the newer Nextion devices may give a Data Error when trying to attempt loading a *.TFT file that was created with an Editor version prior to version 1.63.3 that does not have the ability to communicate with second source ICs. One would need to compile their project with a version 1.63.3 or later and use that *.TFT file to upload their project to the newer Nextion device.

Now mostly Historical, those original Nextion devices from 2015/2016 with the Itead logo on the PCB may require an intermediary upgrade only if all the Legacy conditions are met (see the Legacy FAQ, v0.42 intermediary TFTs are supplied in FAQ), otherwise when every condition is not met then such an intermediary is not required. Devices that were upgraded to a version of the Nextion Editor v0.29 and later can not return to an earlier version (v0.28 and before). Devices that were upgraded to a version of the Nextion Editor v0.38 and later can not return to an earlier version (v0.37 and before). Enhanced Series models require v0.33 or later, when Enhanced models were introduced. Intelligent Series models require v0.58 or later, when Intelligent models were introduced. Discovery Series models require v1.62.2 and later, when Discovery models were introduced. The Nextion Editor LTS Edition (Long Term Support) can only be used with elder Basic and Enhanced devices without second sources ICs. And of course, any newer devices with the QR code on the microSD card slot requires v1.63.3 or later.

This Editor Guide will refer exclusively to the new and current Nextion Editor. Where an item within the guide may be specific to a particular Nextion series, the following icons will be used to represent the series: For the Basic T Series

Requirements* Windows Operating System (XP or higher). Users must know and be able to use their Windows OS. Windows OS support is beyond the scope of Nextion, so while Microsoft discontinues there support of earlier OSes, the current Nextion Editor does run on XP with the x86 .NET 3.5 and x86 2015 VC++ Redistributable. Users are expected to know their own development environment. Note: Installations on VMware and other Operating Systems may have been accomplished successfully, but is not officially supported and beyond the scope of any manual.

* As stated in the Note above, use of Nextion Editor v1.63.3 or later is required for newer Nextion devices with second source ICs, or a Data Error may occur when the *.tft file firmware can not communicate with the second source ICs

* A reasonable sized monitor for the model’s resolution you are designing for is only good sense. When designing for a 320×240 or 240×320 model then a standard monitor size is probably sufficient. However, if one is designing for 1024×600 or 600×1024 resolutions, then it would stand to good reason not to expect best ease from using an 800×600 monitor resolution. For comfort, then it is senseful to use a large enough monitor resolution so that your design canvas, tool panes, menus, and event panes fit for your designing comfort. And in the reverse, a large enough screen for for your development comfort when designing for the smallest of Nextion devices. It is not appropriate to blame the Editor software for your too small monitor when you really know you need more screen real estate.

The latest version of the Nextion Editor can be downloaded from [here]. Earlier versions of the Nextion Editor can be downloaded from the Nextion Editors and Change Logs thread in the Announcement Forum (Register for the forum, confirm and then Login to use).

There are typically two versions of the nextion-setup available for download.1) The EXE version is installed through the Windows MSI for a more automated installation. Only one version of the Nextion Editor may be registered at a time via the EXE version. When updating within the Nextion Editor, Auto Update will install the EXE version

2) The ZIP version can be unzipped into a user chosen folder and run directly from that folder. For maintaining multiple versions of the Nextion Editor, the ZIP version is recommended. When updating within the Nextion Editor, Manual Update will launch your web browser to the download page so you may download the ZIP version

Other settings in the Nextion Editor can be configured in Configuration under the Settings menu. The default font of the Nextion Editor can now be changed to suit your taste. The default timeout of 100ms for the Debug Simulator can be adjusted from 20ms to 5000ms. Code hints, highlighting, description, tooltips and auto-complete can be set individually for the Editor and the Debug Simulator. Default path for eeprom and sd files can be customized to suit your taste. When needed, you can reset these settings by selecting the Reset layout under the Settings menu.

In the Display Tab of the Nextion Editor on starting the Editor, there is a section for listing the most Recent Projects. The number of recent projects tracked is by default 10, and can be increased. Right-clicking a project allows you to select from the following:* Open the file: if the project file exists, then opens in the Editor

Here, Users can create a New project, Open an existing project, Save the current project, Save as to rename and save the currently loaded project, Close Project to close their current project, and Exit the Nextion Editor. Import Project will append an existing project into the current project – usually with resulting naming and renumbering issues. As such, it is recommended to either: a) load your project, adjust your device settings, and Save as under your new project name, or limit importing to individual pages if importing is required.

With the new TFT File Output, users can select where the TFT file should be placed (which folder, sd card drive, other). A valid HMI without compile errors is required to generate a valid TFT output file. The option to open the output folder location in Windows Explorer can be made by clicking only open the output folder link. The old folder location C:\Users\Username\AppData\Roaming\Nextion Editor\bianyi will still contain previously compiled TFTs from elder Editor versions, and only if this is used as the TFT File Output location, will the new TFT for the current project be added to that folder.

The Backup Directory has been renamed to Version backup folder only keeps a copy of an older HMI project opened with a new version of the Nextion Editor launches Windows Explorer to the C:\Users\Username\AppData\Roaming\Nextion Editor\backup folder.

The Virtual EEPROM Folder located C:\Users\Username\AppData\Roaming\Nextion Editor\eeprom contains the eeprom.bin for the Enhanced/Intelligent series models. The default folder can be customized in Settings > Configuration.

The Virtual SD Card Folder located C:\Users\Username\AppData\Roaming\Nextion Editor\sdcard0 allows users of the Intelligent series models to copy project files here that will eventually be on their Nextion microSD card, allowing users to test their project in the Debug Simulator. The default folder can be customized in Settings > Configuration.

In the Configuration menuitem, the user can choose for the Nextion Editor and the Debug Simulator if code should be highlighted or not, if Auto-Complete should be on, if the descriptions for instruction parameters should be on or not, if the tooltips should be shown when the mouse is over the toolbar buttons.

Finally, the default Font used for the Nextion Editor can be changed to suit the users taste. Currently, this default font effects both Editor wide as well as the Event code font. Resetting the font to the default Microsoft Sans Serif will return the Editor to its normal traditionally used font.

Reset layout will reset the Nextion Editor default panes back to their original positions. This is a useful starting point if you have somehow misplaced your pane or positioned it in some obscure unreachable position.

Selecting About Nextion Editor menuitem in the About menu will show the about box with the version of the Nextion Editor. Clicking the link will take you to the Nextion website where you can access the forums and other documentation.

Selecting Check for new version menuitem in the About Menu will show the Update dialog when a new version is available (see Downloading the Nextion Editor at the beginning of this Guide), or a dialog informing that you have the most recent version.

A TFT file is no longer built and placed in the bianyi folder on Compile. To generate a TFT file, one has to use the TFT file output menuitem located under the File menu

The Nextion Editor contains a built-in Simulator that can be accessed via the toolbar Debug. To be clear this is not a precision emulator and is intended to be sufficient to assist in debugging a users project. It in no way is meant to replicate the Nextion device exactly. (Any Windows OS is already sufficient to make such precision unattainable). The Debug Simulator will be covered in more detail in Section 3 of this Guide.

If a project is not currently loaded in the Nextion Editor, Debug will open a dialog to open a compiled *.TFT file directly. This is handy for loading demos or sharing ideas without surrendering your original source code. Although the Debug Simulator can run a *.TFT file from any Nextion Series or model supported by the version of the Nextion Editor, it is important that the same version of Nextion Editor and *.TFT file is used to successfully simulate. (ie: an older v0.36 project TFT file can not be used with the current version of the Nextion Editor.)

Selecting Upload will launch an Open dialog to select a *.TFT file before the Upload to Nextion Device dialog. Ensure the Nextion is connected via serial (typically via USB to TTL adapter) before upload or the Port may not be available to select. Auto search feature will look for your Nextion’s reply to the connect instruction, but realize that data is being sent on all serial ports that are searched (and may interfere with the other connected serial devices). A better choice is to select the correct Port and Baud Rate. Proper configuration of Serial adapters, Windows drivers, device conflicts, etc is beyond the scope of Nextion support and remains the domain of user responsibility to know their used Operating System and devices.

Once Nextion has responded to the connect instruction, the upload process will begin. Do not interrupt this process until completed. If the process has been interrupted, resetting the serial port may be required. When a partial *.TFT file has been uploaded and uploading over serial is no longer an option, then the user will need to upload via the microSD method. Refer to Section 4 of this guide.

Note: While the Nextion Editor HMI project can only have one base character encoding. This does not prevent the inclusion of different encoded fonts within your HMI project. Building on the above explanation, when your MCU sends a byte 0xFF to the Nextion device, the component .font attribute is responsible for which Font resource the byte 0xFF is rendered in (provided the chosen font resource has a glyph to render and is not undefined).

One-time update option will rename the *.tft file on your microSD card to a different extension after successful upload.  You can now also now choose to ignore your pictures (image resources) and fonts (library resources) at compile time.  While this is a small time saving step, it is recommended to turn these off when you are ready to create your final project compiled TFT.

New to the Nextion Editor is the ability to Zoom the design canvas both in and out. Users can zoom from 20% to 600% using the slider, or increment steps using the + and – buttons on the ends of the slider. The value of the zoom is shown in percentage to the right of the Canvas Zoom. Clicking on the percentage zoomed allows you to reset the zoom back to an unzoomed 100% state. Note: Component dragging-by-edge (indicated by double ended arrow pointer) to move or resize components whether intended or accidental can cause an undesired snap-to effect in size and/or position where zoom is not at 100%. Calculation for the placement of component or edge must be to whole numbers and as such drag ending on partial-pixels can indeed effect component size, position or both.  In the event of undesired results, use the Undo (ctrl+z) to revert back to your previous unaltered state. Version v1.65.0 maintains edge-dragging to resize, a drag movement will not resize the component.

Pages can be renamed to a maximum of 14 characters and the page names are case sensitive (avoid using space and other characters that can be code ambiguous as this could cause code parsing issues: Since the Intelligent Series, the Editor compile becomes more strict). To rename your page highlight the page, right click. and select Rename. Then enter your new name (it is recommended to press Enter to ensure the change takes place). Double clicking a Highlighted page name will also trigger the page renaming function.

The page Lock and Unlock functions are only accessed by right clicking the highlighted page name and selecting Lock or Unlock. If the page has been locked with a password, the password must be entered to access the components and event code. There is no password recovery should the password becomes lost, so don’t use or don’t use. As an example, the keyboard pages are imported as locked, but do not use passwords (the keyboard pages are also a good coding example to review). When keyboard pages are imported by the Nextion Editor component .key attribute, reset system page option is included in the context menu, which is used to reload the keyboard page and proper orientation in the cases where the keyboard page may have been edited or display orientation options may have changed.

Nextion Editor now has four different built-in-keyboards that can be added to a project.  This allows for Text, Scrolling Text, Xfloat and Number component .txt and .val to be changed using a built in keyboard by the device user at runtime.  In order to add a built-in-keyboard to your project, the component must first be set to .vscope global, second the .key attribute needs to select your desired keyboard.  Selecting one of the keyboards will add the keyboard page to your project.  Choices are full qwerty style (keybdA), numeric keyboard (keybdB), speed dial style (keybdC), and Chinese Input (Pinyin) style (keybdAP).  The associated keyboard will load an appropriate font if not already included in the project and the keyboard page for the model size and orientation.   Should you choose to change model size or orientation, use the context-menu (right click) for the keyboard page and select Reset System Page to reload.

The Attribute Pane contains the list of components included within the current design page in the Component drop down. Clicking on a component, or selecting it from the drop down will display the component’s available attributes. The left side contains the attribute name, the right side contains the attributes current value. Clicking on an attribute will display the attributes meaning and valid range/options at the bottom of the Attribute Pane. Double clicking a field with bring up resource editor for the attribute if attribute has such (ie: .pco opens color picker, .pic opens picture chooser).

Audio resources are imported into your HMI project through the Audio Resource Pane. An audio resource is added with Add, deleted with Delete, and swapped with Replace. Insert will add the imported audio resource before the currently highlighted audio resource. Use the Arrow Up and Arrow Down to renumber the audio resource number within the Audio Resource Pane. Double clicking on a selected Audio resource will preview/play the audio file in the Nextion Editor. Using Trash will delete all audio resources within the pane. Note that Delete will not delete a picture resource if it is being used with a component.

The Output Pane contains details on the build process when Compile/Debug/Upload is selected. Compile needing to occur first, the user HMI is assembled into a usable TFT file for the selected Nextion Model. The first four lines of the output will list the total amount of Available Memory, Global SRAM Memory consumed by the HMI project, and then statistics for the total amount of Flash space the picture resources consumes, followed by the total amount of Flash space the ZI Font resources consumes. For the Intelligent series: a line will be displayed for each Gmov, Video and Audio with the total amount of Flash space each resource group consumes.

Warnings listed in blue (such as when using the not recommended layering techniques, it will compile, but warn of potential unexpected behaviours), Errors listed in red (this will not compile, and the build process halts). Note: Do not upload a zero byte *.tft file.

Once you have completed designing your HMI project in the Nextion Editor and tested it with the Debug Simulator, it is now time to test it on your actual Nextion device. Note: With previous versions of the Nextion Editor, the Compile and Debug toolbar buttons created the project TFT file in the bianyi folder, note this has changed in favour of outputing your *.tft file directly to microSD card (or folder of your choice).

To upload via microSD card, first use the TFT file output under the File menu to generate your TFT file to your microSD card. You need to ensure that your microSD card is Windows formatted as FAT32, that there is only 1 *.tft file on the microSD card in the root folder, that the microSD card is less than 32GB in size (32GB microSD cards generally are), that the power to Nextion device is off when inserting and removing the microSD card, and that you allow time for any firmware updates to occur after powering your Nextion device back on. Note: not all microSD cards are designed for embedded use. example: Ultra High Speed microSD cards for use with high speed digital cameras. Not all manufacturers adhere to the same standards. It is a matter of finding microSD cards that work for you in a reliable manner. As an example, We have had good successes with Kingston 32GB class 10 HC microSD cards … there are many many others that work well.

The Nextion Upload Protocol v1.1 has been published in the Nextion blog section. This allows users to upload their *.tft files over Serial without the Nextion Editor. As this is an advanced topic, it will not be covered in depth here. Please refer to the published Nextion Upload Protocol v1.1

The Nextion Editor ZI Font Creator has undergone an overhaul to introduce proportional fonts with anti-aliasing. Height must be between 16 and 254 and Custom can be chosen to set a height not listed in the dropdown (between 16 and 254). Choosing Anti-aliasing of fonts option will generate an anti-aliased font. Leaving anti-aliased not selected will generate a mono-bit font. Previous embedded 1:2 ratio with width=1/2height has been replaced in favour of proportional fonts. Fixed width fonts can still be generated from a fixed width font source (such as Consolas). Fonts created in the new Font Creator are not compatible with v0.53/LTS. Any installed font on your system can be used as a source for generating your ZI font.  ZI Fonts can now be limited to a specified range of characters, useful for subsetting your fonts to what is project required and reduce font resource space usage.  (56 pixel height UTF-8 could be a very large ZI file at 23,168,377 bytes)

The TFT-LCD (Flat Panel) Antitrust Litigationclass-action lawsuit regarding the worldwide conspiracy to coordinate the prices of Thin-Film Transistor-Liquid Crystal Display (TFT-LCD) panels, which are used to make laptop computers, computer monitors and televisions, between 1999 and 2006. In March 2010, Judge Susan Illston certified two nationwide classes of persons and entities that directly and indirectly purchased TFT-LCDs – for panel purchasers and purchasers of TFT-LCD integrated products; the litigation was followed by multiple suits.

TFT-LCDs are used in flat-panel televisions, laptop and computer monitors, mobile phones, personal digital assistants, semiconductors and other devices;

In mid-2006, the U.S. Department of Justice (DOJ) Antitrust Division requested FBI assistance in investigating LCD price-fixing. In December 2006, authorities in Japan, Korea, the European Union and the United States revealed a probe into alleged anti-competitive activity among LCD panel manufacturers.

The companies involved, which later became the Defendants, were Taiwanese companies AU Optronics (AUO), Chi Mei, Chunghwa Picture Tubes (Chunghwa), and HannStar; Korean companies LG Display and Samsung; and Japanese companies Hitachi, Sharp and Toshiba.cartel which took place between January 1, 1999, through December 31, 2006, and which was designed to illegally reduce competition and thus inflate prices for LCD panels. The companies exchanged information on future production planning, capacity use, pricing and other commercial conditions.European Commission concluded that the companies were aware they were violating competition rules, and took steps to conceal the venue and results of the meetings; a document by the conspirators requested everybody involved "to take care of security/confidentiality matters and to limit written communication".

Companies directly affected by the LCD price-fixing conspiracy, as direct victims of the cartel, were some of the largest computer, television and cellular telephone manufacturers in the world. These direct action plaintiffs included AT&T Mobility, Best Buy,Costco Wholesale Corporation, Good Guys, Kmart Corp, Motorola Mobility, Newegg, Sears, and Target Corp.Clayton Act (15 U.S.C. § 26) to prevent Defendants from violating Section 1 of the Sherman Act (15 U.S.C. § 1), as well as (b) 23 separate state-wide classes based on each state"s antitrust/consumer protection class action law.

In November 2008, LG, Chunghwa, Hitachi, Epson, and Chi Mei pleaded guilty to criminal charges of fixing prices of TFT-LCD panels sold in the U.S. and agreed to pay criminal fines (see chart).

The South Korea Fair Trade Commission launched legal proceedings as well. It concluded that the companies involved met more than once a month and more than 200 times from September 2001 to December 2006, and imposed fines on the LCD manufacturers.

Sharp Corp. pleaded guilty to three separate conspiracies to fix the prices of TFT-LCD panels sold to Dell Inc., Apple Computer Inc. and Motorola Inc., and was sentenced to pay a $120 million criminal fine,

Seven executives from Japanese and South Korean LCD companies were indicted in the U.S. Four were charged with participating as co-conspirators in the conspiracy and sentenced to prison terms – including LG"s Vice President of Monitor Sales, Chunghwa"s chairman, its chief executive officer, and its Vice President of LCD Sales – for "participating in meetings, conversations and communications in Taiwan, South Korea and the United States to discuss the prices of TFT-LCD panels; agreeing during these meetings, conversations and communications to charge prices of TFT-LCD panels at certain predetermined levels; issuing price quotations in accordance with the agreements reached; exchanging information on sales of TFT-LCD panels for the purpose of monitoring and enforcing adherence to the agreed-upon prices; and authorizing, ordering and consenting to the participation of subordinate employees in the conspiracy."

On December 8, 2010, the European Commission announced it had fined six of the LCD companies involved in a total of €648 million (Samsung Electronics received full immunity under the commission"s 2002 Leniency Notice) – LG Display, AU Optronics, Chimei, Chunghwa Picture and HannStar Display Corporation.

On July 3, 2012, a U.S. federal jury ruled that the remaining defendant, Toshiba Corporation, which denied any wrongdoing, participated in the conspiracy to fix prices of TFT-LCDs and returned a verdict in favor of the plaintiff class. Following the trial, Toshiba agreed to resolve the case by paying the class $30 million.

The TFT-LCD (Flat Panel) Antitrust Litigationclass-action lawsuit regarding the worldwide conspiracy to coordinate the prices of Thin-Film Transistor-Liquid Crystal Display (TFT-LCD) panels, which are used to make laptop computers, computer monitors and televisions, between 1999 and 2006. In March 2010, Judge Susan Illston certified two nationwide classes of persons and entities that directly and indirectly purchased TFT-LCDs – for panel purchasers and purchasers of TFT-LCD integrated products; the litigation was followed by multiple suits.

TFT-LCDs are used in flat-panel televisions, laptop and computer monitors, mobile phones, personal digital assistants, semiconductors and other devices;

In mid-2006, the U.S. Department of Justice (DOJ) Antitrust Division requested FBI assistance in investigating LCD price-fixing. In December 2006, authorities in Japan, Korea, the European Union and the United States revealed a probe into alleged anti-competitive activity among LCD panel manufacturers.

The companies involved, which later became the Defendants, were Taiwanese companies AU Optronics (AUO), Chi Mei, Chunghwa Picture Tubes (Chunghwa), and HannStar; Korean companies LG Display and Samsung; and Japanese companies Hitachi, Sharp and Toshiba.cartel which took place between January 1, 1999, through December 31, 2006, and which was designed to illegally reduce competition and thus inflate prices for LCD panels. The companies exchanged information on future production planning, capacity use, pricing and other commercial conditions.European Commission concluded that the companies were aware they were violating competition rules, and took steps to conceal the venue and results of the meetings; a document by the conspirators requested everybody involved "to take care of security/confidentiality matters and to limit written communication".

Companies directly affected by the LCD price-fixing conspiracy, as direct victims of the cartel, were some of the largest computer, television and cellular telephone manufacturers in the world. These direct action plaintiffs included AT&T Mobility, Best Buy,Costco Wholesale Corporation, Good Guys, Kmart Corp, Motorola Mobility, Newegg, Sears, and Target Corp.Clayton Act (15 U.S.C. § 26) to prevent Defendants from violating Section 1 of the Sherman Act (15 U.S.C. § 1), as well as (b) 23 separate state-wide classes based on each state"s antitrust/consumer protection class action law.

In November 2008, LG, Chunghwa, Hitachi, Epson, and Chi Mei pleaded guilty to criminal charges of fixing prices of TFT-LCD panels sold in the U.S. and agreed to pay criminal fines (see chart).

The South Korea Fair Trade Commission launched legal proceedings as well. It concluded that the companies involved met more than once a month and more than 200 times from September 2001 to December 2006, and imposed fines on the LCD manufacturers.

Sharp Corp. pleaded guilty to three separate conspiracies to fix the prices of TFT-LCD panels sold to Dell Inc., Apple Computer Inc. and Motorola Inc., and was sentenced to pay a $120 million criminal fine,

Seven executives from Japanese and South Korean LCD companies were indicted in the U.S. Four were charged with participating as co-conspirators in the conspiracy and sentenced to prison terms – including LG"s Vice President of Monitor Sales, Chunghwa"s chairman, its chief executive officer, and its Vice President of LCD Sales – for "participating in meetings, conversations and communications in Taiwan, South Korea and the United States to discuss the prices of TFT-LCD panels; agreeing during these meetings, conversations and communications to charge prices of TFT-LCD panels at certain predetermined levels; issuing price quotations in accordance with the agreements reached; exchanging information on sales of TFT-LCD panels for the purpose of monitoring and enforcing adherence to the agreed-upon prices; and authorizing, ordering and consenting to the participation of subordinate employees in the conspiracy."

On December 8, 2010, the European Commission announced it had fined six of the LCD companies involved in a total of €648 million (Samsung Electronics received full immunity under the commission"s 2002 Leniency Notice) – LG Display, AU Optronics, Chimei, Chunghwa Picture and HannStar Display Corporation.

On July 3, 2012, a U.S. federal jury ruled that the remaining defendant, Toshiba Corporation, which denied any wrongdoing, participated in the conspiracy to fix prices of TFT-LCDs and returned a verdict in favor of the plaintiff class. Following the trial, Toshiba agreed to resolve the case by paying the class $30 million.

This application note is part 1 of our 2 part TFT LCD screen series. Part 1 discusses configuring the screen resolution of a TFT with a Raspberry Pi. Part 2 discusses calibrating the touch screen of a TFT. Click here to read part 2.

This application note discusses how to setup a TFT touch screen display with Raspberry Pi. The display chosen for this project is a 7-inch LCD with a capacitive touch feature. The display has 1024x600 pixels of resolution and when calibrated for the Raspberry Pi can display 16.7M colors. With a few changes to the Raspberry Pi configuration files the dimensions of this display can be matched for perfect resolution.

Connecting the TFT to the Raspberry Pi is simple and only requires a few steps. The display has a HDMI connection backpack interfaced with the device so there is no need for soldering or individual pin connections. If you have used Raspberry Pi before, you will notice that the connection to the TFT is standard and straightforward. Before powering the Raspberry Pi you should make all the necessary connections to the screen. Plug in the HDMI. Connect the CTP port with a micro-USB cable. Power the screen with micro-USB cable connected to a USB port on the Raspberry Pi or a power adapter that provides 5V. You only need three connections to the HDMI backpack module on the TFT.

The file will open in a text editor called nano. We need to add the specifics of our display to the file by adding the following commands to the file:

With only a few changes to the Raspberry Pi’s default configuration file the TFT can become compatible with the Raspberry Pi. This display is a great choice for interfacing with the Raspberry Pi because it has an HDMI connection type which makes for any easy setup. After the resolution and is set to a desired value we can now optimize the touch feature of the display. See here for more information on how to further calibrate this display.

Buyers and others who are developing systems that incorporate FocusLCDs products (collectively, “Designers”) understand and agree that Designers remain responsible for using their independent analysis, evaluation and judgment in designing their applications and that Designers have full and exclusive responsibility to assure the safety of Designers" applications and compliance of their applications (and of all FocusLCDs products used in or for Designers’ applications) with all applicable regulations, laws and other applicable requirements.

Designer agrees that prior to using or distributing any applications that include FocusLCDs products, Designer will thoroughly test such applications and the functionality of such FocusLCDs products as used in such applications.

TOPWAY Smart LCDs embed a display engine and a versatile range of TFT display sizes and Touch-Panels to support a wide range of industrial and instrumentation application.

UI designs are implemented under usage of TOPWAY’s Graphic Editor allowing designs with zero coding. It dramatically simplifies and speeds up the whole product design process.