Recent Posts

Pages: 1 2 [3] 4 5 ... 10
The contrast of the LCD module referenced in the subject can be adjusted by adding a variable resistor between the VEE (negative supply), GND and Vo (input for contrast adjustment).  When tracing where the interface header pins are connected, there appears to be resistor pads that will allow either a variable or fixed contrast setting directly on the module.  As this display is replacing a different type of display, I don't want to require external components for this purpose.

LCD Module Datasheet

The component locations in question are R6, R7, VR1, R81, R82 and Q2.  The stock configuration has 0Ω jumpers at R6 and R7 and I believe Q2 is a PNP 2SB1198K based on the device markings.  VR1, R81 and R82 are not populated.  I have included pictures of the actual PCB and a hand-drawn schematic as I see it.  Note that there is one node in the schematic that I couldn't determine it's connection, but it would appear to be a supply connection with voltage greater than VEE.



I am sure there must be a configuration that would only require a change in population (no cuts or jumps) otherwise why would they bother to include all these component locations ... ESPECIALLY when you see the pads for the variable resistor (VR1)!

The transistor is what is throwing me.  I would like to know what it's purpose is in the default configuration.  If R6, R7 and Q2 were removed, a fixed voltage divider can be created using R6 and R81 and a 0Ω jumper at R82, just as recommended for the external voltage divider.  Obviously, this could be adjustable by populating a pot for VR1 and not populating R6.

If any of you have been down this road before, I would appreciate you sharing your experience!
I am new to the model listed above and was wondering if there are any good resources to help me in the programming of this LCD display.
Customer Projects / Re: New Support library for FTDI Screen Newhaven Display
« Last post by lightcalamar on April 01, 2018, 05:30:59 PM »
Hello again.

Many thanks to you @Paul_B

The reason for rewriting, I made a new purchase in NHD, specifically this screen; NHD-7.0-800480FT-CSXN-CTP link

But on this occasion, there is something special ... you commented that you will have an ESP32, it will be ideal for your projects.

I belong to the FT81xmania team as I said in my previous messages, well, come to this, we have worked very hard and we have managed to unify the libraries to all the MCUs that I wrote in my initial message.

I am, we are very fortunate to be able to buy these magnificent screens in NHD, and without profit, we publish our advances.

No more I leave the library of the repository;

And suggestions, help in our forum;

A big greeting from the Team
Character LCDs / NHD-0420D3Z-NSW-BBW-V3 with raspberry pi
« Last post by ljtc1793 on March 30, 2018, 12:20:18 AM »
I just brought a new NHD-0420D3Z-NSW-BBW-V3, but I don't know how to connect it with raspberry pi 3 B :'(. Anyone can give me some help? If possible, please also give me an sample code (python) to run it. Thanks!!! :)
TFTs / SPI problem with NHD-3.5-320240FT-CSXN-CTP
« Last post by Wiggum on March 29, 2018, 11:25:04 AM »
Hi all,

I have a problem with above mentioned display.
My setups are
1. TFT connected via MPSSE to PC, MSVC software
2. TFT connected to custom board with TI Tiva 1294 uC
 2.1 using a modified "simple app" with customized hardware layer
 2.2 using exported EVE Screen Designer projects with own hardware layer for the Tiva

For comparison, I also have a VM810C50A-D evaluation board from FTDI

A. The VM810 board runs flawlessly in all configurations.

B. I had to fumble around a lot with the NHD TFT to get it to work. Firstly, with the MPSSE cable and the sample app, I had to reduce SPI speed from 12MHz to 1.2 MHz but also then, it was not stable in all cases.
By accident, I found out that when I reduce the supply voltage from 3.3V to 2.9V, the NHD display worked even at 12MHz SPI speed.
At voltages above 3.3V, it does not even read the 0x7C code correctly.

For the custom board, it's almost the same scenario, however it is rather unstable and does not carry out commands, so the display app get's stuck at waiting for the cmd write and read pointers to match.

Am I doing anything wrong? Do others see this behaviour as well?

Any help is greatly appreciated.

Best regards,

TFTs / Re: Touch shifting on NHD-7.0-HDMI-N-RSXV-RTU
« Last post by Sergio_M on March 29, 2018, 09:21:09 AM »

It may seem the touch panel might have not been calibrated correctly, which could explain the touch shift. The AR1100 (Resistive Touch Screen Controller IC) shows up like a USB mouse, it works on all operating systems as the computer doesn't know it's a touch screen, it just thinks its a mouse. You can adjust the AR100 to consider itself a Touch Digitizer, supported by many but not all computers.

If you have a Raspberry Pi available you may  re-calibrate the touch IC via USB using the following program:


If you have a Windows computer you may re-calibrate the touch IC via USB using the following program:

Hope this helps,

If you have any questions please email me:

Customer Projects / Re: New Support library for FTDI Screen Newhaven Display
« Last post by Paul_B on March 29, 2018, 08:18:10 AM »
Awesome, thank you for sharing! I actually just picked up a ESP-WROOM-32 module, I'll have to give your library a try in the near future  8)
Customer Projects / Re: New Support library for FTDI Screen Newhaven Display
« Last post by lightcalamar on March 28, 2018, 12:36:32 PM »
Thanks you @Paul_B and Michael_L

I went up a few moments ago, a new special library for ESP32, with example for asset management of images. It works on all family of FTDI chip displays.

Valid for all MCU shields with ESP32 WROOM-2 espressif chip, in my tests I have used DOIT, DevKit v1.1 and NODEMCU-32s and work very fine, I guess other MCUs of different brands have to work too.

This library also works in other tests performed such as STM32 Nucleo, example STM32F767ZI with Arduino IDE

I still have to debug the library and make a configuration wiki.

Link to repository;

Enjoy.  :)
OLEDs / Re: NHD-0216MW-IB3 Command Decoder
« Last post by Paul_B on March 26, 2018, 08:02:39 AM »
Hi Tim,

The” IS”, “RE” and “SD” bits are flags that are internal to the controller. You would set these using the commands that have the flag in as one of their parameters.

To set the “RE” & “IS” flags, you would use the Function Set Command:

(See Image1.png)

You could only set the ”IS” flag if the “RE” Bit is low.

(See Image2.png)

To set the “SD” flag, you would first need to enter the Extended Command Set by setting the “RE” bit high, then using the OLED Characterization Command to set the “SD” Bit high:
OLEDs / NHD-0216MW-IB3 Command Decoder
« Last post by BumpSplat on March 24, 2018, 02:00:27 PM »
I'm using the NHD-0216MW in a serial module (I2C) and am having trouble understanding the commands for the controller.  The US2066 controller uses a couple bits that are hardware set to enable software commands (IS/RE/SD).  It's not clear how these bits are set or cleared using a serial data format.  I've gone through the suggested initialization process found at the end of the datasheet (Page 17).  I'd like to understand how these (and above) commands binary map to the hex values shown.  This will enable me to build my own custom commands.  Basically I'm asking:

"Is there a bit level secret decoder ring for the serial commands listed in the initialization code found listed above?"

Thanks in advance - Tim
Pages: 1 2 [3] 4 5 ... 10