{"id":5101,"date":"2017-03-17T06:10:27","date_gmt":"2017-03-17T11:10:27","guid":{"rendered":"http:\/\/www.plastibots.com\/?p=5101"},"modified":"2018-07-31T09:53:25","modified_gmt":"2018-07-31T13:53:25","slug":"nextion-tft-lcd-why-you-need-one","status":"publish","type":"post","link":"https:\/\/www.plastibots.com\/index.php\/2017\/03\/17\/nextion-tft-lcd-why-you-need-one\/","title":{"rendered":"Nextion TFT LCD – Why you need one!"},"content":{"rendered":"

\"capture\"I’ll start this by stating that I don’t work for iTead, and nor am I getting any sort of kickbacks… \u00a0 I just really like this TFT LCD. \u00a0I stumbled upon the Nextion<\/a>\u00a0(which is a slick easy-to-use TFT LCD with a HMI editor) when they had their first crowdfunding campaign a year or so ago. \u00a0 I ignored it as there was not a lot of documentation, and frankly, I really didn’t understand the concept of graphics work done on the TFT, and the rest on the MCU. \u00a0 Wish I had taken a gamble at the time. \u00a0Instead, I went down a path building projects using SPI-based TFTs which require a lot of work to draw and manipulate graphics and text. They are also generally slow at drawing as they require the MCU (an ESP8266 in my case) to do the graphics processing work and send them pixel-by-pixel to the TFT.
\n<\/p>\n

The Nextion Approach:<\/strong><\/p>\n

The Nextion approach\u00a0consists of a TFT LCD that has brains and memory built in, and a Windows editor (HMI) to develop your graphical interface by placing images and text on a screen and designing how they will interact. \u00a0 You can even do some programming <\/a>on the base device and more so on the enhanced version (which has GPIO pins). \u00a0You could, for example do an entire project solely on the Nextion screen (enhanced model) by connecting a temperature and other sensors directly and reading the results. \u00a0What I (and most others do) is connect it to an Arduino or \u00a0EPS8266. \u00a0 These MCUs become the brains to process input from sensors etc and simply need to send commands over serial to display results graphically. \u00a0You can see this in action with my\u00a0WIoT-2<\/a>.<\/p>\n

The general idea is you develop your interface (HMI) on the Nextion. \u00a0Lay out all the graphics, text, buttons etc and assign them variable names. \u00a0You can then develop your sketch which procesess sensor and other data and sends the commands over serial to update the values in the interface. \u00a0You can also \u00a0control the interface (i.e. change a page, force a button click etc etc). \u00a0In the HMI, you lay out your graphics, buttons and text, compile it, transfer the .tft file to a Micro SD card, then load the card into the back of the Nextion, and power it up. \u00a0This will load the tft file into the firmware of the Nextion. \u00a0Once complete, disconnect power, remove the card, then power it back up. \u00a0You will see your screen with graphics and default values you created. \u00a0You compile the sketch and upload that to the MCU and you have a project! \u00a0 Then, connect +5V, GND and the TX\/RX lines to your MCU and you’re done.\u00a0 Easy peasy! \u00a0My WIoT-2<\/a> project provides lots of info and as well as a sketch and HMI file.<\/p>\n\n\n\n
\n

\"The<\/a>
The Nextion HMI Editor<\/figcaption><\/figure><\/td>\n
\n

\"The<\/a>
The Nextion Screen<\/figcaption><\/figure><\/td>\n
\"\"<\/a><\/td>\n\n

\"Nextion<\/a>
Nextion to MCU Connection<\/figcaption><\/figure><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

About the Cost:<\/strong><\/p>\n

There’s no question that the Nextion TFT’s are more expensive than other TFT’s out there. \u00a0 However, you have to consider the total cost of ownership. \u00a0What is your time worth? How complex is it to draw graphics to other TFT’s? \u00a0Prior to the Nextion, I was using other TFTs that used SPI to communicate. They require graphics and font processing code to be written in your MCU and pushed from the MCU to the screen when displaying content. \u00a0You have to do this for each element. For example, to place some text you have to send separate commands to define which font to use, which size, it’s colour, and x\/y placement. \u00a0It also requires many debug runs to ensure you have the placement correct. \u00a0This is very time consuming. \u00a0Over 80% of my time coding the original WIoT was dedicated to writing code to manipulate graphic \/ button elements to send to the RA8875 TFT controller and LCD I had. \u00a0Considering this, is that extra ~30% cost of a Nextion worth the many more hours you have to put in coding your project? I can safely say definitely not. \u00a0I estimate that I put in more than 50 hours writing code to interface with the RA8875 driver and coming up with the screens\/graphics\/fonts for my original WIoT. \u00a0It was a lot of work. \u00a0The Nextion and HMI Editor made this easy and slick \u00a0(used in WIoT-2<\/a>). \u00a0I haven’t even mentioned the time it took me to learn how to create custom fonts and then integrate them into the libraries. \u00a0The Nextion has a tool built-in and does all the heavy lifting automatically. \u00a0Again, don’t forget – after doing all this, the other methods require the MCU to draw graphics by sending pixel-by-pixel over the SPI line. \u00a0The Nextion has all graphics and fonts in memory, so all your MCU has to do is issue serial (text) commands to set pictures and change text – which makes things very zippy. \u00a0As an example, it takes 3-5 seconds to update 1 weather icon with the RA8875 in my original WIoT. \u00a0My MCU is sending a 100x100px image over SPI each time the weather refreshes. \u00a0In WIoT-2, the Nextion does an entire page with all graphics\/text (including background graphic) in 1-2 seconds. \u00a0The reason is all graphics are already in memory. \u00a0So changing a weather icon can be done by simply stating pic=2, <\/em>and BAM it’s updated in a flash.<\/em>\u00a0 \u00a0That’s a huge improvement. \u00a0Switching one graphic for another is a split second action and a single command.<\/p>\n

Notable Features:<\/strong><\/p>\n

Easy Debugging: \u00a0You can do most of the screen feature debugging within the Nextion Editor and it’s debug window. \u00a0You can simulate commands from the MCU and look at results. All without even having an MCU \/ sketch running.<\/p>\n

MCU debugging: \u00a0You can even connect your MCU with running sketch to your PC, open the HMI editor and allow it to push data over serial to the Editors’ debug window to see actual results. \u00a0You don’t even need a physical Nextion screen. \u00a0So you can develop your project while you wait for your Nextion to arrive in the mail… \u00a0Oh, and the Editor is a free download (link below).<\/p>\n

Font Generation: \u00a0The Nextion Editor comes with a font tool that allows you to select any system font that you have and convert it for use on the Nextion. \u00a0There is no ugly creation or modifications to font libraries etc, it automatically makes the font available (by ID) and embeds it in the TFT file package.<\/p>\n

Links:<\/strong><\/p>\n