Recent Posts

Pages: [1] 2 3 ... 10
TFTs / Polarization state of 5" TFT display?
« Last post by crschardt on July 19, 2018, 05:31:30 PM »
I just purchased a NHD-5.0-HDMI-N-RTXL module. I'm using it in a application where I need to know the polarization state of the emitted light, but I couldn't find it listed in the product documentation. Would someone please let me know the polarization orientation for this display?

Thank you for the help.
TFTs / Re: FT5x06 Sensitivity for 4mm glass cover
« Last post by Ted_M on July 19, 2018, 01:39:03 PM »
The sensitivity of the touchscreen would be controlled by adjusting the values in the registers in the Focaltech CTP controller.
The registers are 80h, 81h, and 82h found on page 9 of the NHD-7.0-800480EF-ASXN-CTP Datasheet:

Here is a link to the Focaltech datasheet:

And the link to Application Notes with more details to program the registers:

TFTs / FT5x06 Sensitivity for 4mm glass cover
« Last post by yraeisi on July 18, 2018, 01:18:06 AM »
Hi all
can any body tell me,how did you increase the sensitivity of 7" CTP?(IC:FT5x06 or FT5826)
which Registers must be modified?
I need CTP work with 4mm Glass cover Lens.
thanks so much
TFTs / Re: Capacitive touch problems under linux (FT5x06)
« Last post by yraeisi on July 18, 2018, 01:07:41 AM »
The I2C protocol between the two displays should be the same.  Do you have another 4.3" TFT with capacitive touch panel to try?

can you tell me,how did you increase the sensitivity of 7" CTP?
which Registers must be modified?
I need CTP work with 4mm Glass cover Lens.
thanks so much
OLEDs / current consumption of character OLEDs
« Last post by jinuos on July 13, 2018, 02:56:37 AM »
I am considering to use one of the character OLEDs, and have a couple of questions about current consumption.

1. Slim character OLEDs such as NHD-0420CW-AG3 support both 2.8V and 5V supply voltage. For the reference, my supply is 3.3V.
    Datasheet shows that current consumption is 70mA typ. and 135mA max.
    Are those figures the measured results @ 2.8V or 5V?
    For the normal character OLED, is current consumption @ 2.8V different from the current @ 5V?

2. The gap between 70mA typ. and 135mA max. seems to be large for me.
    So I want to know which condition is typical or max.
    If I light up all the characters of 4 lines x 20, I guess that's the max. current condition. right? If I reduce the usage of char as possible as I can, can I reduce current consumption? If so, how much?

3. Standard character OLED, NHD-0420DZW-AY5, which is smilar to the slim character OLED NHD-0420CW-AG3, also support 3V to 5.3V supply voltage. And its datasheet shows that the current consumption is 46mA min., 55mA typ., 73mA max at 5V supply condition. If I use NHD-0420DZW-AY5 @ 3.3V supply, the current consumption increases? If so, how much?

4. I use 3.3V voltage supply. which product has better performance of current consumption, slim character OLED? or standard character OLED?
Hello Brian.

This library GD23ZU supports the MCUs described in the repository; STM32F1x, STM32F4x and STM32F7x, Teensy 3.5 / 6 It hurts with your fabulous NHD screen then use an Arduino MEGA MCU.

If you want to playback video in Arduino MEGA, then you have to use the "sister" library called GD23Z from this repository;

After many frustrating moments, decide my friend (@TFTLCDCyg(MexSpa Team)) and I solve the main thing, use power MCU, Teensy is a very good option, its versions 3.5 and 3.6 have SDIO microSD reader on board and work very fine.

But other MCU's like the ST STM32F767ZI Nucleo is great for a project where up to 3 SPIs are needed and we have achieved it;

However, we have our forum where we can give support in 3 languages such as Spanish, English and French;

Bests regards! Tomas.
Graphic LCDs / Graphic LCD 128x64 LCD-00710 Doesn't Work
« Last post by robinsenny on July 12, 2018, 08:35:53 AM »

I then tried read-modify-write to set individual pixels. My program just set all the pixels one at a time from left to right, top to bottom. It mostly worked, but the reads of the first pixel strip in each bank weren't reliable.I then tried writing blocks of pixels, one pixel at a time, at random places, not at the beginning of a line for either controller. Any time I changed the line, the first read produced garbage, even if the new line was in the same pixel strip as the previous line (e.g., it was the same address in the controller). A curious thing is that if I did two consecutive reads for the first read on each controller after changing lines, without resetting the address between reads, the problem went away.As I tried to figure out what was wrong (playing with delays and such) it got worse and worse until now it won't set any pixels at all. Status reads from the controllers appear to be working (returning 0x20), but pixel writes and reads no longer work at all.I'm driving the display from an ATMEGA32 running on a combo Atmel Dragon / Dragon Rider, using code based on the driver from (I can't spell his name without special characters). I see that "radek"'s code does two reads for each read-modify-write operation. Does anybody understand why this is needed?

Please help.

I didn't find the right solution from the Internet.

Best explainer video companies


I am a new comer and is also using NHD-7.0-800480FT-CSXN-CTP to develop a system.  I downloaded both GD23ZU and SdFat library and put them under Arduino 1.8.5's library folder.   

I am using Arduino Mega2560 as the base board and had the following compiler error:

C:\Dev\Tools\arduino-1.8.5-windows\arduino-1.8.5\libraries\GD23ZU\GD23ZU.cpp: In member function 'byte GDClass::load(const char*, FUNC_POINTER)':

C:\Dev\Tools\arduino-1.8.5-windows\arduino-1.8.5\libraries\GD23ZU\GD23ZU.cpp:1685:13: error: 'SD' was not declared in this scope

   archivo =; 

Checked the code
#if defined(ARDUINO_ARCH_STM32)
   //SdFat SD(3);     // STM32F429
   SdFat SD(2);       // STM32F767

#if defined(TEENSYDUINO)
    SdFatSdioEX SD;   // Teensy 3.6-3.5

and found SD is only defined for ARDUINO_ARCH_STM32 and TEENSYDUINO platform. My problem is that I am not sure my atmega 2560 belongs to which platform.  Or should I use SD(2) or SD?

TFTs / Re: EVE2 Palette8 Pixels
« Last post by warriorofwire on July 07, 2018, 01:07:55 PM »
Oh goodness, hi Paul - thank you for your reply, I didn't have email notification set up for this thread!

I've reached out to FTDI for help.  I read that application note and the extensively.  It is very unclear what the "palette" schema is, and what a paletted bitmap should contain to reference that palette.

Here's the application, sorry for the poor video - I haven't implemented screen capture for video yet:

The tachometer needle is a subtle asset with a blue glow that fades off over the span of a few pixels.  I'd like to retain a very high quality color gradient and use transparency.  I tried using "rgb8888" 32 bit raw bitmap and was unable to get that to work.  Any alternative ideas?  32bpp is expensive, but totally tolerable for this small, high-value asset.

By the way, I thought it was kind of funny that the coprocessor uses "degrees" for rotation when it seems most natural to use "radians" with a transformation matrix  :D
TFTs / Re: Raspberry Pi driver for 1.8" and 2.4" TFT models
« Last post by deanflyer on July 06, 2018, 08:54:55 AM »
Just came across this post. Ive been messing around with theNH 2.4" sunlight readable TFT and the raspberry pi. Unfortunately I managed to short it out, so need to order another one :(

I'm more of a software guy. What im looking for is a small 2.4-3.5" TFT that I can drive at up to 60fps. It needs to be sunlight readable though i.e. ~1000CDM, hence looking at the Newhaven 2.4" displays.

Not 100% tied into Raspberry Pi, as long as I can develop c/c++ code on a SBC and interface it, I'd be happy.

Any thoughts before I order another TFT?
Pages: [1] 2 3 ... 10