Recent Posts

Pages: [1] 2 3 ... 10
1
TFTs / Windows CE 7.0 Touch Driver for NHD-7.0-HDMI-N-RSXV-CTU
« Last post by eudoxos on Today at 01:28:46 AM »
Hello,

has anybody experience with touch drivers (NHD-7.0-HDMI-N-RSXV-CTU) for Windows Compact Embedded 7.0? The operating system cannot identify the touch controller IC (PIC18LF2550).
Are there any drivers/libraries for download?
The touch controller works well with Win 10 / Win 7, that means the hardware is ok.

Thanks a lot in advance.
Regards
2
TFTs / Re: NHDev board and NHD-1.8-128160EF-CTXI#-FT
« Last post by Ted_M on June 18, 2018, 10:29:04 AM »
Hi Steve,

It's good to hear you have found the answer.
The latest version of our product catalog referenced in your post can also be found on our website here: http://www.newhavendisplay.com/nhd_catalog.html

The NHDev board supported display listing is on the same page 3-1.

Thanks and Best Regards,
Ted
3
TFTs / Re: NHDev board and NHD-1.8-128160EF-CTXI#-FT
« Last post by SteveK on June 17, 2018, 06:41:00 PM »
I have answered my own question. 

On page 3-1 of this doc https://www.e-sonic.com/Upload//LeaderBoard//c32e6567-1330-4e81-a72d-a50b0ca7d645.pdf  it indicates that the NHD-1.8-128160EF-CTXI#-F is indeed suported by the NHDev board.

4
TFTs / Re: NHDev board and NHD-1.8-128160EF-CTXI#-FT
« Last post by SteveK on June 14, 2018, 04:22:49 PM »
I have not yet purchased the development board.

My query stems from looking at the online datasheet for the NHDev:  http://www.newhavendisplay.com/nhdev/specs/NHDev_v2.pdf

On page 2 it lists the supported displays. The only 1.8" one listed there is the NHD-1.8-128160TF-CTXL#


5
TFTs / Re: NHDev board and NHD-1.8-128160EF-CTXI#-FT
« Last post by Saurabh_B on June 14, 2018, 09:13:53 AM »
Can you tell me when you purchased the NHDev Development board?

It seems that you have an older version of the software. the NHD-1.2-128160TF was an older model we used to sell and has been replaced by the NHD-1.8-128160EF series.
6
TFTs / Re: Raspberry Pi driver for 1.8" and 2.4" TFT models
« Last post by Ted_M on June 14, 2018, 08:28:33 AM »
Thanks for posting the drivers for the Rasberry Pi!  They will be very useful for many users. 
We look forward to seeing more of your postings in the future.

Best Regards,
7
TFTs / Raspberry Pi driver for 1.8" and 2.4" TFT models
« Last post by joaBaur on June 14, 2018, 01:55:15 AM »
So after the FPGA drivers I went for something easier, and connected the TFTs to the Raspberry Pi's GPIOs.

Repo for the NHD-1.8-128160EF TFTs:
https://github.com/joaBaur/RaspberryPi-NHD-1.8-TFT

Repo for the NHD-2.4-240320CF TFTs:
https://github.com/joaBaur/RaspberryPi-NHD-2.4-TFT

Both drivers are native C, they map the main display's internal framebuffer (/dev/fb0) to memory, read the pixels' RGB values and bit bang them to TFT via the GPIOs.

The frame rates are ok, about 20 fps on the 2.4" and 34 fps on the 1.8" display.
8
TFTs / NHDev board and NHD-1.8-128160EF-CTXI#-FT
« Last post by SteveK on June 13, 2018, 05:40:05 PM »
Hi,
I would like to use the NHDev module to evaluate a NHD-1.8-128160EF-CTXI#-FT display.

However, in the list of displays that the NHDev supports, it lists only NHD-1.8-128160TF-CTXL#, which appears to be a bogus number, ie it shows no results if we search for it on the Newhaven site.

Can anyone confirm if the NHD-1.8-128160EF-CTXI#-FT will work with the NHDev module?

Thanks,
Steve
9
TFTs / Re: FPGA driver for NHD-1.8-128160EF TFTs
« Last post by joaBaur on June 13, 2018, 11:58:31 AM »
Alright, the MADCTL issue is resolved - I connected the other 1.8" TFT I have here (a NHD-1.8-128160EF-CSXN#) and MADCTL is working as it should, so I removed the workarounds from my code.
10
I'm trying to send commands and characters to the LCD Screen, and instead of recognizing any of the data coming through via SPI, the screen just prints out the same character that doesn't match any form in the datasheet. This printout happens for every byte that is sent from the Pi to the LCD.

On the oscilloscope and other signal analysis tools, the data looks fine. Our clock speed is under 10kHz, there is definitely data being sent from MOSI, and the chip enable matches up.

I suspect this is some kind of timing issue but we can't seem to figure it out. We're currently using the bcm2835 library for SPI. This problem persists for both a Raspberry Pi Zero W and a Raspberry Pi 3B.

Here is a picture of the LCD Screen characters: https://drive.google.com/open?id=1NL5L29cRPE3PIjEKbWjCc4p9CLdEgsyQ
Pages: [1] 2 3 ... 10