Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Ted_M

Pages: [1] 2 3 4
TFTs / Re: NHD-3.5-320240MF-ASXV#-CTP Increase touch sensitivity
« on: December 03, 2018, 10:46:33 AM »
Hi pekka.k,

The default values for the FT-5x16 controller are different than the FT5x06 so the value range will be different.
Please refer to the FT5x16 controller register data for more details:
Let us know what values were working to get the proper sensitivity on the FT5x06 and the new value range you have tried.

Best Regards,

Hi billtrib,

The I2C address can be changed to any 8-bit value by command function, with the exception that the LSB (least significant bit) must always be 0. Once the I2C address has
been changed, it will be saved in the system memory, and it will revert back to the default address if either RS232 or the SPI protocol is selected.
Also, if that is not the issue, then try lowering the I2C clock rate to 50Khz and try again.

Best Regards,

Evaluation Tools / Re: Does NHD-FT81x-SHIELD support Arduino due?
« on: November 26, 2018, 03:42:23 PM »
Hi Nachalan,

Unfortunately the Due is not compatible. The NHD-FT81x-SHIELD requires an operating voltage of 5V to be supplied by the Arduino.  The Arduino Due board runs using a 3.3V operating voltage.

For a list of compatible Arduino's, please refer to our NHD-FT81x-Shield User Guide on page 11.

Best Regards,

Evaluation Tools / Re: FTDI Eve screen editor
« on: November 26, 2018, 03:26:46 PM »
Hi Nachalan,

FTDI has just released a new Asset Builder Tool that allows you to generate Fonts, convert JPEG images, Video files and Audio into EVE compatible formats.
The new "EVE Asset Manager" tool can be found on FTDI's Website here:

Also, the new "EVE Screen Designer 4.5" tool is available from the same link.

Best Regards,

TFTs / Re: Difficulty with SPI with NHD-4.3-480272FT-CSXV-CTP
« on: November 08, 2018, 10:07:16 AM »
Hi Makoto.inoue,

It's good to hear you have solved this issue.

Thanks for posting the solution!

Best Regards,

OLEDs / Re: Double Width Font NHD-0216CW
« on: November 02, 2018, 10:40:14 AM »
Hi Matthew,

Unfortunately the US2066 controller does not support double width characters, however there is an option to set a 6-dot width character vs. a 5-dot character in the Extended function set command list. (pg. 7 of the datasheet)

Best Regards,

OLEDs / Re: Double Height Font NHD-0216CW
« on: November 02, 2018, 10:06:54 AM »
Hi Matthew,

Please review the example code from this post for working with double height characters using the US2066 controller:,929.msg2160.html#msg2160

Best Regards,

TFTs / Re: Difficulty with SPI with NHD-4.3-480272FT-CSXV-CTP
« on: November 01, 2018, 03:56:10 PM »
Hi Makoto.inoue,

The issue from the topic,8363.0.html was resolved by adding a hardware buffer to the SPI clock source.

It appears that MOSI goes low once SS is goes low, therefore MOSI is idle High with the Arduino example.  Try this configuration to see if helps.

Best Regards,

TFTs / Re: SPI problem with NHD-3.5-320240FT-CSXN-CTP
« on: November 01, 2018, 03:04:48 PM »
As an update to this topic - This issue was resolved by adding a hardware buffer to the SPI clock signal at the MPSSE cable.

Best Regards,

OLEDs / Re: NHD-1.5-128128ASC3 and Teensy 3.6
« on: November 01, 2018, 02:41:37 PM »
Hi Killkrt,

Both Chip Select signals for the OLED (OLEDCD) and the SD card reader (SDCS) are active low and would need to be active independently of each other. 
Using a pull-up resistor on each of these Chip Select lines will ensure they are both inactive on power up.

Best Regards,

OLEDs / Re: NHD-5.0-HDMI-N-RTXL-CTU brightness control
« on: October 24, 2018, 02:25:47 PM »
Please refer to the 5.0" HDMI TFT Module user guide on page 5. See item # 3 for the connector CN4 which controls the backlight PWM. In order to dim the LED backlight, A PWM frequency range of 5khz - 100khz would be used.

For further information please refer to the user Guide:


TFTs / Re: How To Mount - NHD-7.0-HDMI-N-RTXL-CTU -
« on: October 17, 2018, 10:05:28 AM »
It is recommended that the gasket be placed at least 0.5mm from the outside front surface edge of the CTP. Then up tp 1.0mm from the inside edge of the metal bezel frame of the TFT beneath the CTP glass to provide a stable compressible surface.  The gasket compression should not press the gasket over the outside edge and also should not compress the CTP glass over the air gap on the inside area of the TFT display. This will help prevent interference with the touchscreen due to distortion of the glass.

The NHD-7.0-HDMI-N-RTXL-CTU display module contains the TFT display NHD-7.0-800480EF-ATXL#-CTP.
The datasheet for this TFT display will include the dimensions of the metal bezel frame edge widths.

Datasheet for your reference:

Best Regards,


TFTs / Re: EVE2 TFT Modules VHDL Coding
« on: October 03, 2018, 10:17:07 AM »
Hi Bivin,

Thanks for your inquiry.
This information may be best answered by the FTDI technical support resources provided in the link below:

Best Regards,


Graphic LCDs / Re: Newhaven Display Problems
« on: September 27, 2018, 09:20:57 AM »
The Vo contrast pin 3 will need approximately +0.5V to get you in the ballpark to set the contrast level.
It would be best to connect the resistor to the VDD power supply in order to provide voltage to this pin. 

A variable resistor is recommended as this makes it possible to adjust the contrast level with the desired visual setting. Then you may replace the variable resistor with a fixed resistance equal to the value set by the variable resistor.  A variable resistor with a minimum of 10K and maximum of 20k will work to get the voltage supplied to the contrast pin 3 set to approximately +0.5V for optimal contrast.

The circuit board labeling the pin-outs should also match the datasheet as published on our website.  If this is not the case, please send us a picture of the display.

Please let us know if you have any questions.


Graphic LCDs / Re: NHD-C12864A1Z-FSW-FBW-HTT pixel problem
« on: September 19, 2018, 09:32:00 AM »
This topic was supported through email and was resolved by clearing buffer memory.

Pages: [1] 2 3 4