Recent Posts

Pages: 1 ... 8 9 [10]
91
TFTs / Re: NHD-7.0-HDMI-N-RSXM -RTV touchscreen calibration
« Last post by Paul_B on May 16, 2018, 10:35:56 AM »
No problem  ;)
92
TFTs / Re: NHD-7.0-HDMI-N-RSXM -RTV touchscreen calibration
« Last post by roman on May 16, 2018, 09:40:21 AM »
Hi Paul.

Screen is recalibrated and working fine!

Thanks a lot!

Regards.
Roman
93
TFTs / Re: NHD-7.0-HDMI-N-RSXM -RTV touchscreen calibration
« Last post by Paul_B on May 16, 2018, 07:59:22 AM »
Hi Roman,

The AR1100 (Resistive Touch Screen Controller IC) shows up like a USB mouse, it works on all operating systems as the computer doesn't even know its a touch screen, it just thinks its a mouse. You can adjust the AR1100 to consider itself a Touch Digitizer, supported by many but possibly not all computers.

You can also re-calibrate the touch screen. We do calibrate it with the 800x480 7" screens but we recommend re-calibrating it if you feel like its not precise enough for your tastes.

If you have a Raspberry Pi available you can 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 can re-calibrate the touch IC via USB using the following program:

http://www.microchip.com/wwwproducts/en/AR1100#documentation
94
TFTs / NHD-7.0-HDMI-N-RSXM -RTV touchscreen calibration
« Last post by roman on May 16, 2018, 04:23:40 AM »
Hi !

I've just bought a NHD-7.0-HDMI-N-RSXM -RTV display. Looks good, brighness is really high !

But I have a problem with touchscreen. It says it does not need calibration as it is pre-calibrated. Looks like precalibration is lost or wrong. I cannot reach top of screen on left top corner, cannot reach right side on top right border and so on... similar on other corners. Cursor is

Is there a way to recalibrate ???

Thanks!!
95
Hello,

To help you getting started please take a look at our example initialization code.
8-bit parallel: https://newhavendisplay.com/appnotes/excode/txt/CharLCD/8bit_character.txt

If you have any question please contact us @: techsupport@newhavendisplay.com
96
TFTs / EVE2 Startup for 7" Display
« Last post by warriorofwire on May 13, 2018, 02:30:14 AM »
Hi Newhaven folks,

I'm following the FT81x Series Programmer Guide and the DS_FT81x datasheet to set my Newhaven display up and running.  I've been stuck for several days trying to get a hello world working.

My first test is to make a red circle on the screen.  It works very rarely and sometimes makes the circle the wrong size or at the bottom of the screen, sometimes it's only 1/2 or 1/4 circle.  Re-running startup randomly makes the screen kind of work, but the red dot location, size and presence is completely random.

  • 10mhz single SPI.
  • FTDI internal 12mhz crystal, not using external crystal.  (should I?)
  • Particle Photon microcontroller.

Here's what I'm writing to the display, with comments.  I write to the display, then read back what I wrote in a follow-up transaction to see if it "took" properly.  First column is "milliseconds since bootup."

Code: [Select]
0000004092 [app.ft81x.display] INFO: wrote to register: 0x34, wrote: 0x00000320, read: 0x00000320.  good // Sets HSIZE=800
0000004092 [app.ft81x.display] INFO: wrote to register: 0x2c, wrote: 0x000003a0, read: 0x000003a0.  good // Sets HCYCLE=928
0000004093 [app.ft81x.display] INFO: wrote to register: 0x30, wrote: 0x00000058, read: 0x00000058.  good // Sets HOFFSET=88
0000004093 [app.ft81x.display] INFO: wrote to register: 0x38, wrote: 0x00000000, read: 0x00000000.  good // Sets HSYNC0=0
0000004094 [app.ft81x.display] INFO: wrote to register: 0x3c, wrote: 0x00000030, read: 0x00000030.  good // Sets HSYNC1=48
0000004095 [app.ft81x.display] INFO: wrote to register: 0x48, wrote: 0x000001e0, read: 0x000001e0.  good // Sets VSIZE=480
0000004095 [app.ft81x.display] INFO: wrote to register: 0x40, wrote: 0x0000020d, read: 0x0000020d.  good // Sets VCYCLE=525
0000004096 [app.ft81x.display] INFO: wrote to register: 0x44, wrote: 0x00000020, read: 0x00000020.  good // Sets VOFFSET=32
0000004096 [app.ft81x.display] INFO: wrote to register: 0x4c, wrote: 0x00000000, read: 0x00000000.  good // Sets VSYNC0=0
0000004097 [app.ft81x.display] INFO: wrote to register: 0x50, wrote: 0x00000003, read: 0x00000003.  good // Sets VSYNC1=3
0000004097 [app.ft81x.display] INFO: wrote to register: 0x6c, wrote: 0x00000001, read: 0x00000001.  good // Sets PCLK_POL=1 (falling edge, this is a curious setting in Newhaven's documentation)
0000004098 [app.ft81x.display] INFO: wrote to register: 0x68, wrote: 0x00000001, read: 0x00000001.  good // Sets CSPREAD=1
0000004098 [app.ft81x.display] INFO: wrote to register: 0x60, wrote: 0x00000001, read: 0x00000001.  good // Sets DITHER=1
0000004099 [app.ft81x.display] INFO: wrote to register: 0x64, wrote: 0x00000000, read: 0x00000000.  good // Sets SWIZZLE=0
0000004099 [app.ft81x.display] INFO: wrote to register: 0xd4, wrote: 0x00000080, read: 0x00000080.  good // Sets backlight PWM=128 (fully on)
0000004100 [app.ft81x.display] INFO: Settings are set.
0000004100 [app.ft81x.display] INFO: Waited 0ms for display list after register init.                           // This loops to wait for REG_DLSWAP's value to be 0
0000004101 [app.ft81x.display] INFO: Wrote display list: 0, command: 0x04000000, written: 0x04000000.  good // color_rgb(0,0,0) (display list number is (dl_offset)/4 for more convenient log reading)
0000004101 [app.ft81x.display] INFO: Wrote display list: 1, command: 0x26000007, written: 0x26000007.  good // clear(all)
0000004101 [app.ft81x.display] INFO: wrote to register: 0x54, wrote: 0x00000002, read: 0x00000002.  good // Writes 2 to REG_DLSWAP
0000004102 [app.ft81x.display] INFO: wrote to register: 0x70, wrote: 0x00000002, read: 0x00000002.  good // Sets PCLK=2 (Also a curious setting, FTDI programmer guide says this goes after the first display list)
0000004103 [app.ft81x.display] INFO: Waited 0ms for display list ready after initial clear display list. // This loops to wait for REG_DLSWAP's value to be 0
0000004103 [app.ft81x.display] INFO: Wrote display list: 0, command: 0x02000000, written: 0x02000000.  good // dl_ram+00 = color_rgb(0,0,0)
0000004104 [app.ft81x.display] INFO: Wrote display list: 1, command: 0x26000007, written: 0x26000007.  good // dl_ram+04 = clear(all)
0000004104 [app.ft81x.display] INFO: Wrote display list: 2, command: 0x04a01616, written: 0x04a01616.  good // dl_ram+08 = color_rgb(160,22,22)
0000004105 [app.ft81x.display] INFO: Wrote display list: 3, command: 0x0d000140, written: 0x0d000140.  good // dl_ram+12 = point_size(20+16)  (for a 40 pixel diameter circle)
0000004105 [app.ft81x.display] INFO: Wrote display list: 4, command: 0x1f000002, written: 0x1f000002.  good // dl_ram+16 = begin(point)
0000004106 [app.ft81x.display] INFO: Wrote display list: 5, command: 0x38085001, written: 0x38085001.  good // dl_ram+20 = vertex2ii(192,133,0,0)  (to try to drop the circle somewhere on the screen)
0000004106 [app.ft81x.display] INFO: Wrote display list: 6, command: 0x21000000, written: 0x21000000.  good // dl_ram+24 = end()
0000003908 [app.ft81x.display] INFO: wrote to register: 0x54, wrote: 0x00000002, read: 0x00000002.  good // Writes 2 to REG_DLSWAP

Am I interacting with the screen wrong?  Setting wrong settings?
97
OLEDs / Problem with NHD-0420CW-AR3 - Double spaced characters now.
« Last post by JKleiber on May 05, 2018, 07:32:51 PM »
So...I fixed the original problem I posted about.  Now I have most of my problems solved.  The remaining serious problem is that I get double spaced characters:  "John"  displays as "J o h n".  Anyone have a suggestion?  I have a "work around" in which I reset the DRAM pointer each character.  Not what I want but it works.  Still interested in any ideas anyone may have for a real fix.

int LCD_GoToXY (char L, char C)  // L(ine) = 1..4, C(ollumn)=1..20
{
    if( L > 4 || C > 20) return(0);
    C--;
    switch(L)
    {
        case 1: LCD_SendCMD(LCD_Line1 + C); break;
        case 2: LCD_SendCMD(LCD_Line2 + C); break;
        case 3: LCD_SendCMD(LCD_Line3 + C); break;
        case 4: LCD_SendCMD(LCD_Line4 + C); break;
    }
    return(1);
}

void LCD_WriteStr(char L, char C, char* s)  //send start location (L,C) and pointer to string to be displayed.
{
    int i = 0;   
    while(s)
    {
        LCD_GoToXY(L, C++);
        LCD_SendChar(s[i++]);   
    }
}



I have a new project in which I am using the above NH OLED display.   I followed exactly the initialization sequence suggested on pages 20 & 21 in the NH data sheet but my display is reversed, a mirror image.   I saw a post here from 2016 in which the author had the same issue but no answers followed an initial reply. 
I am driving the display with a PIC16 8 bit MC using the 8080 8bit parallel interface scheme.  Everything seems to work with the exception of the problem described above.

Any suggestions?
John
98
OLEDs / Re: How to reset NHD-0216SZW-BY5?
« Last post by jamespandit on May 05, 2018, 06:18:17 AM »
Been encountering a similar issue with NHD-0216SZW-BY5; have you been able to fix it yet?
99
Character LCDs / Re: NHD-0108BZ-RN-GBW-ND Contrast Problem
« Last post by hwalker92 on May 02, 2018, 10:42:46 AM »
Inputting 0.3V to the contrast pin gets doubled by the display to 0.6V which now makes the text readable.

But why is the display changing the voltage? I know my board and ribbon cable are fine..checked them both extensively.
100
OLEDs / NHD-0420DZW-AY5 Problem initializing
« Last post by gbgb on May 02, 2018, 05:04:33 AM »
Although this topic appears in previous posts, which I looked into, I still cannot initialize my display.
I am working in 8 bits mode with a PIC.

I followed the initialization sequence as it appears in page 18 of the manual (rev 11).

One piece of information that is missing is in what mode does the display wake up, 4 or 8 bits?
Is it possible that it wakes up in 4 bits mode and that the first command in the initialization (function set) has to be sent in 4 bits mode and only after it is sent switch to 8 bits mode and send the rest of the initialization commands in 8 bits mode?

Is there a sample code for 8 bits for this display? The only code I saw is one that has a "wakeup" command 3 time at the beginning, which is not what the specs for this display say.

Just for reference:
I am waiting 50mS after power up to begin the sequence
I am strobing the E signal as a 1mS pulse
I wait at least 5mS between commands
Pages: 1 ... 8 9 [10]