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 ... 10
1
Character LCDs / Re: Character Display top row
« on: December 31, 2019, 02:49:58 PM »
Hi Houston,

If the very top row of pixels are not being displayed, there may be a connection problem with the LCD glass to the PCB.
This could be caused by some form of contamination to the LCD glass contacts, or a possible mechanical connection issue. 
Please describe if this failure was seen after some period of time working it the end product, or if this failure was seen at the time of product assembly?
Any more details you can share will help us to determine a possible cause for failure.

Best Regards,

2
Character LCDs / Re: Data interface not the same..!!
« on: December 20, 2019, 10:58:36 AM »
Hi Zonker,

Unfortunately we do not have a standard 2x20 display with the pinout you require. 
If you are interested in a customized display, please contact us at nhtech@newhavendisplay.com
We are able to manufacture a custom version of the NHD-0220DZ-NSW-BBW with a pinout compatible with the Kyocera.

Best Regards,

3
OLEDs / Re: NHD-1.1-9696G
« on: December 18, 2019, 04:43:02 PM »
Hi Kishan,

Here is some working Arduino example code on our Github site that may help you to test the display.

https://github.com/NewhavenDisplay/NHD-1.1-9696G

Best Regards,

4
Graphic LCDs / Re: NHD-7.0CTP-CAPE-L
« on: December 11, 2019, 11:52:20 AM »
Hi Adithya,

A good platform to use for developing a custom graphical user interface would be to use the QT Creator tools.
http://exploringbeaglebone.com/chapter13/

There are also links to the Android OS and the Ubuntu OS in our datasheet of working images for the BeagleBone Cape that can be used to get you started.
http://www.newhavendisplay.com/userguides/NHD-7.0CTP-CAPE_User_Guide.pdf

Best Regards,

5
Character LCDs / Re: NHD-0216K3Z-FL-GBW-V3 losing/dropping characters
« on: December 11, 2019, 10:26:33 AM »
Hi Eashwar,

Please review the example I2C code below that is written for the Arduino Mega.  It uses much longer delays so it may be worth trying to increase your delay time a bit more to see if that resolves the issue.

Code: [Select]
/******************************************************
 * Using i2c on NHD 0216KZ3
 * ARDUINO MEGA
 */

#define SCLK 21
#define SDO 20



const char Slave    = 0x50;

const char t1[]=("Newhaven Display");
const char t2[]=("    LINE  2     ");

void I2C_out(unsigned char j){
  int n;
  unsigned char d;
  d=j;
  for(n = 0; n<8; n++){
    if((d&0x80) == 0x80)
      digitalWrite(SDO, HIGH);
    else
      digitalWrite(SDO, LOW);
    d = (d<<1);
    digitalWrite(SCLK, LOW);
    delay(10);
    digitalWrite(SCLK, HIGH);
    delay(5);
    digitalWrite(SCLK, LOW);
    delay(10);
  }
  digitalWrite(SCLK, HIGH);
  delay(1);
  while(SDO ==1){
   
    digitalWrite(SCLK, LOW);
    //delay(1);
    digitalWrite(SCLK, HIGH);
    //delay(1);
   
  }
  digitalWrite(SCLK, LOW);
}
void I2C_Start(){
  digitalWrite(SCLK, HIGH);
  digitalWrite(SDO, HIGH);
  digitalWrite(SDO, LOW);
  digitalWrite(SCLK, LOW);
}

void I2C_Stop(){
  digitalWrite(SDO, LOW);
  digitalWrite(SCLK, LOW);
  digitalWrite(SCLK, HIGH);
  digitalWrite(SDO, HIGH);
}
void disp(const char *text)
{
  int n;
  for(n=0;n<16;n++)
  {
    I2C_Start();
    delay(5);
    I2C_out(Slave);
    delay(5);
    I2C_out(*text);
    text++;
    I2C_Stop();
    delay(10);
  }
}

void setup() {
  // put your setup code here, to run once:
  pinMode(SDO, OUTPUT);
  pinMode(SCLK, OUTPUT);
  digitalWrite(SCLK, LOW);
  digitalWrite(SDO, LOW);
 
  I2C_Start();
  delay(1);
  I2C_out(0x50);
  delay(1);
 
  delay(10);
  I2C_out(0xFE);
  I2C_out(0x51);
  I2C_Stop();
  delay(100);
  I2C_Start();
  delay(5);
  I2C_out(Slave);
  delay(5);
  I2C_out(0xFE);
  I2C_out(0x46);
  delay(10);
  I2C_Stop();
  delay(100);
  I2C_Start();
  delay(5);
  I2C_out(Slave);
  delay(5);
  I2C_out(0xFE);
  I2C_out(0x47);
 

  delay(100);
  I2C_Stop();
  delay(10);
  I2C_Start();
    delay(5);
    I2C_out(Slave);
    delay(5);
    I2C_out(0xFE);
    I2C_out(0x52);
    delay(5);
    I2C_out(40);
    delay(5);
    I2C_Stop();
    delay(250);
 
 
}

void loop() {
  unsigned char x = 0x21;
  int i;
  I2C_Start();
  delay(5);
  I2C_out(Slave);
  delay(5);
  I2C_out(0xFE);
  I2C_out(0x51);
  I2C_Stop();
  double a;
  char buff[10];
  a = 2.523;

  sprintf(buff, "%g" , a);
  int n = 0;
  /*
    for (n = 0; n < 8 ; n ++){
      I2C_Start();
  delay(1);
  I2C_out(Slave);
  delay(1);
    I2C_out(buff[n]);
    delay(1);
    I2C_Stop();
    delay(1);
  }
 
  delay (2500);*/
  disp(t1);
  delay(100);

  delay(100);
  I2C_Start();
  delay(5);
  I2C_out(Slave);
  delay(5);
  I2C_out(0xFE);
  I2C_out(0x45);
  //delay(10);
  I2C_out(0x40);
  delay(10);
  I2C_Stop();
  delay(10);
  disp(t2);
  I2C_Stop();
  delay(1000);
  do{
   delay(10);
  for( i = 0 ; i < 50 ; i++){
    I2C_Start();
    delay(5);
    I2C_out(Slave);
    delay(5);
    I2C_out(0xFE);
    I2C_out(0x52);
    delay(5);
    I2C_out(i);
    delay(5);
    I2C_Stop();
    delay(5);
  }
  int b;
  for( i = 0 ; i < 51 ; i++){
    I2C_Start();
    delay(5);
    I2C_out(Slave);
    delay(5);
    I2C_out(0xFE);
    I2C_out(0x52);
    delay(5);
    b = 50 - i;
    I2C_out(b);
    delay(5);
    I2C_Stop();
    delay(25);
  }
  }while(1);
  /*for(i = 0; i < 57; i++){
    I2C_Start();
    delay(5);
    I2C_out(Slave);
    delay(5);
    I2C_out(x);
    x++;
    I2C_Stop();
    delay(10);
  }
// delay(5000);
 
  I2C_Start();
  delay(5);
  I2C_out(Slave);
  delay(5);
  I2C_out(0xFE);
 
  I2C_out(0x51);
  delay(10);

    I2C_out(0xFE);
  I2C_out(0x4B);
  delay(10);
  I2C_out(0xFE);
  I2C_out(0x46);
  delay(10);
  I2C_Stop();
  disp(t1);
  delay(1000);
  for( i = 0 ; i < 50 ; i++){
    I2C_Start();
    delay(5);
    I2C_out(Slave);
    delay(5);
    I2C_out(0xFE);
    I2C_out(0x52);
    delay(5);
    I2C_out(i);
    delay(5);
    I2C_Stop();
    delay(250);
  }
   I2C_Start();
    delay(5);
    I2C_out(Slave);
    delay(5);
    I2C_out(0xFE);
    I2C_out(0x52);
    delay(5);
    I2C_out(40);
    delay(5);
    I2C_Stop();
    delay(250);
 
  while(1);*/
 
}

6
TFTs / Re: Help needed to configure NHD-4.3RTP-SHIELD-N with Ardunio Due
« on: November 01, 2019, 08:33:45 AM »
Hi,

The Hello World example code was written to be used with the Arduino UNO and therefore will not compile on the DUE without software changes.

We recommend running the NHD-4.3RTP-SHIELD-N with a 5v version Arduino such as the UNO, Mega 2560 or other 5V compatible versions as the SHIELD requires to be driven with a 5V source as listed in our user guide.  http://www.newhavendisplay.com/userguides/NHD-4.3CTP-SHIELD_User_Guide.pdf

Unfortunately the Arduino Due is not compatible with the SHIELD as it would supply it with only 3.3v volts.


Best Regards,

8
OLEDs / Re: NHD-0420CW-AW3 powering ( I2C driven )
« on: September 23, 2019, 02:37:55 PM »
Hi Sam,

The NHD-0420CW-AW3 display can be run using a 3.3V source for Vdd with no issues.  To select running at 3.3V, pin 3 for RegVdd would be grounded.

Best Regards,

9
TFTs / Re: LCD compatibility issue with USB (NHD-4.3-480272EF-ASXN-CTP)
« on: September 23, 2019, 02:06:22 PM »
Hi Robb,

It appears there may some contention of the frame buffer memory, or with the 2 memory layers when using both the display and the USB.  Have you tried double buffering the frames?
Please see this link for more details http://www.lucadavidian.com/2017/10/02/stm32-using-the-ltdc-display-controller/

Best Regards,


10
Evaluation Tools / Re: NHD-3.5-320240MF-PIC Eval Board
« on: September 17, 2019, 12:00:21 PM »
The NHD-3.5-320240MF TFT displays come with a 24-bit RGB interface so it would be best to connect the display to our NHD-3.5-320240MF-20 Controller Board. 
https://www.newhavendisplay.com/nhd35320240mf20-controller-board-p-2656.html

It will support the 24-bit RGB display interface and allow you to program the controller's SSD1963 controller using an 8-bit parallel interface from the PIC.
Libraries are available to support the SSD1963 controller that will help get you started.  Here are a few examples:

http://www.microchip.com/forums/download.axd?file=0;757320
https://github.com/fbrausse/ssd1963

Here is a link at Digikey with more details on using our 3.5" TFT with a PIC32:
https://www.digikey.com/eewiki/display/Motley/PIC32+Low-Cost+Controllerless+Graphics+Interface+to+Newhaven+Color+LCD

Best Regards,

11
TFTs / Re: NHD-10.1-1024600AF-ASXV#-CTP
« on: September 17, 2019, 10:24:43 AM »
Hi ElremGu,

Unfortunately, the Focaltech FT5x26 controller is not sensitive enough to detect touches reliably with an extra 4mm of cover class on top of the standard touchscreen's cover glass.
It is possible to add up to 2.0mm of cover glass on top of the standard touchscreen's glass and adjust the register values to increase the sensitivity. 
If a 4mm cover glass is required, then we can quote you a custom capacitive touchscreen with one piece of cover glass and a different touch controller to meet your requirements.

Please contact us at nhtech@newhavendisplay.com for more details and a quote.

Best Regards,

12
Hi jrandall11,

Try formatting the SDcard as FAT32.

Best Regards,

13
Please double check the logic high and logic low are within the specified target ranges when using a level shifter from 3.3V to 5V.  For a High, the logic level would need to be at least (0.8*VDD).  For a Low, the value would need to be less than (0.2*VDD).  If necessary, use a pull-up or pull-down resistor to help achieve these logic levels.
Best Regards,


14
TFTs / Re: Unable to use multi-touch protocol in NHD-5.0-800480TF-ATXL-CTP
« on: September 06, 2019, 04:20:39 PM »
Hi Nitin,

Please reference our Github for the Focaltech FT5x26 Linux drivers:
https://github.com/NewhavenDisplay/FT5X26-Focaltech-Drivers

Best Regards,

15
OLEDs / Re: Valid VCC Range for NHD-0216MW-AB3
« on: August 28, 2019, 02:18:57 PM »
Changing the resistance to lower the Iref will affect the overall contrast level range that can be adjusted in software, however it may not produce a counteracting effect to the displays lifetime. This would still be dependent on the contrast level the display is set to while using the higher VCC voltage.

Best Regards,


Pages: [1] 2 3 ... 10