Recent Posts

Pages: 1 [2] 3 4 ... 10
11
OLEDs / Re: Connecting the NHD-0420-CW Display to the Evalboard
« Last post by Sergio_M on October 11, 2018, 08:11:06 AM »
Hello,

Unfortunately, the NHDev board does not support I2C interface, you can test in parallel mode to see how the display looks.
12
TFTs / Re: Windows 10 IoT Core
« Last post by GeerGuy on October 10, 2018, 11:19:41 PM »
This is with a full screen canvas.  The yellow is with a standard mouse and the blue lines is as far as the touchscreen will work with a stylus.  The dead space is the same with Win 10, Win 10 IoT Core and Linux.

https://www.dropbox.com/s/3tom4cpe4jmflho/20181010_201921.jpg?dl=0
13
TFTs / Re: Windows 10 IoT Core
« Last post by GeerGuy on October 10, 2018, 04:20:16 PM »
I can provide a picture in the next few days of the difference when using a standard mouse and the touch screen with a stylus.
14
TFTs / Re: Windows 10 IoT Core
« Last post by Saurabh_B on October 10, 2018, 03:37:47 PM »
The capacitive touch panel displays also provide a better resolution.
Could you also provide a video of where the displays cut off?
15
TFTs / Re: Windows 10 IoT Core
« Last post by Paul_B on October 10, 2018, 03:27:39 PM »
Unfortunately, its a limitation of this type of touch panel   :(

For the best edge to edge touch performance it is highly recommend to use the Capacitive Touch version (if possible):

http://www.newhavendisplay.com/nhd70hdminrsxvctu-p-9555.html









17
Character LCDs / Re: Inverse video on NHD‐C0220BiZ‐FSW‐FBW‐3V3M
« Last post by Saurabh_B on October 10, 2018, 03:26:22 PM »
No, Unfortunately this display does not allow you to flip individual characters.

18
TFTs / Re: Windows 10 IoT Core
« Last post by GeerGuy on October 10, 2018, 12:00:41 PM »
I have calibrated my display with a Raspberry Pi using rpi-AR1100 and it still has a ~1/4" area on all sides that can't see any touch.

Using a Win10 computer with the Microchip AR1100 Cal Config, how should the preferences be set?

Number of wires?  4 or 5?
USB Mode?  Mouse

Is the Calibration Inset % the "dead" area that I'm seeing?  Can this be 0 or 1%?

Will these setting be stored in the display?
19
TFTs / Re: Windows 10 IoT Core
« Last post by Paul_B on October 10, 2018, 08:53:54 AM »
Hi,

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:

https://github.com/tom-2015/rpi-AR1100

or

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

http://www.microchip.com/wwwproducts/en/AR1100#documentation


Hope this helps,
20
TFTs / NHD-4.3-480272FT-CTXL-T not clearing all to one color properly
« Last post by maolvera93 on October 09, 2018, 06:15:31 PM »
Hello,

I've been trying to get my Newhaven (NHD-4.3-480272FT-CTXL-T) display to work properly and I just can't. First I had an issue with the screen having random colors, and now when I run the following code, it works unless I OR the DL_CLEAR_RGB function with any color other than black or white. Am I missing a step in my initializing process? Why aren't my colors being displayed properly. I have my external clock set to 4MHz from my PSoC Cypress 5LP microcontroller connected to my Newhaven display. Is it a clock problem?

Code: [Select]
int main()
{
 

    SPIM_Start();
    Clock_SPI_Start();
   
   
    //ss_Write(1);
   
   
    Reset_Write(1);//Power on
    CyDelay(20);
    Reset_Write(0);//Power off
    CyDelay(20);
     Reset_Write(1);//Power on
    CyDelay(20);
   
    cmd_write(ACTIVE);
    CyDelay(20);
    cmd_write(CLKEXT);
    CyDelay(20);
    cmd_write(FT812_CLK36M);
    CyDelay(20);
 

    ft81xMemWrite8(REG_PCLK, ZERO); // Set PCLK to zero - don't clock the LCD until later
    ft81xMemWrite8(REG_PWM_DUTY, ZERO); // Turn off backlight
 
    //initialize display registers
    ft81xMemWrite16(HCYCLE,548);
ft81xMemWrite16(HOFFSET,43);
ft81xMemWrite16(HSYNC0,0);
ft81xMemWrite16(HSYNC1,41);
ft81xMemWrite16(VCYCLE,292);
ft81xMemWrite16(VOFFSET,12);
ft81xMemWrite16(VSYNC0,0);
ft81xMemWrite16(VSYNC1,10);
ft81xMemWrite8(SWIZZLE,0);
    ft81xMemWrite8(PCLK_POL,0);
ft81xMemWrite8(CSPREAD,1);
ft81xMemWrite16(HSIZE,480);
ft81xMemWrite16(VSIZE,272);
   
   
    ft81xMemWrite32(RAM_CMD    , (DL_CLEAR_RGB | WHITE));
    ft81xMemWrite32(RAM_CMD + 4, (DL_CLEAR | 0x1 | CLR_STN | CLR_TAG));
    ft81xMemWrite32(RAM_CMD + 8, (DL_DISPLAY));
    //ft81xMemWrite32(RAM_CMD +12, (DL_CLEAR_RGB | BLUE));
   
    ft81xMemWrite8(REG_DLSWAP,DLSWAP_FRAME);//display list swap
   
    ft81xMemWrite8(REG_GPIO_DIR,(0x80 | ft81xMemRead8(REG_GPIO_DIR)));
    ft81xMemWrite8(REG_GPIO,0x080 | ft81xMemRead8(REG_GPIO));//enable display bit
   
    ft81xMemWrite8(REG_PCLK,5);
   

   
    for(int duty = 0; duty <= 128; duty++)
    {
        ft81xMemWrite8(REG_PWM_DUTY, duty); // Turn on backlight - ramp up slowly to full brighness
        CyDelay(10);
    }


I am using the 4.23 CLEAR_COLOR_RGB command from the FT81x Programmers guide for the command.
Pages: 1 [2] 3 4 ... 10