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 - Saurabh_B

Pages: 1 ... 7 8 [9] 10 11 ... 25
121
TFTs / Re: Using NHD-1.8 Displays with a FFC connector
« on: November 14, 2016, 09:32:25 AM »
Hello Mark,

Unfortunately there are no standard ZIF / FFC connectors for the 0.8mm pitch connector, these would have to be soldered directly to the pcb.
We do offer the 1.8" TFTs with a FFC style connector, such as the NHD-1.8-128160EF-CSXN#-F

122
Graphic LCDs / Re: NHD‐240128WG‐BTFH‐VZ - custom characters
« on: November 11, 2016, 12:09:42 PM »
Unlike standard character LCDs it doesn't look like the RA6963 allows you to store custom fonts.
However it is a graphic display and you should be able to create your own font table to use and just display the text how you would like.

123
Graphic LCDs / Re: NHD-C160100DiZ
« on: November 08, 2016, 11:57:26 AM »
Hello,

This display is only set to work with monochrome.
You would not be able to send different values for the pixels.

124
Graphic LCDs / Re: NHD-12864WX-T1TFH# IN C LANGUAGE !!!
« on: November 08, 2016, 11:56:32 AM »
Working on this through Email.

125
OLEDs / Re: NHD-0420CW I2C interface
« on: November 03, 2016, 11:08:35 AM »
Hi,

You should be able to use this with multiple sources on the same bus, however sometimes the other devices tend to sink some of the current and create invalid high signals.

The continuation byte needs to be sent between each datawrite.
While it is possible to send larger amounts of data continuously, for I2C you would need the command byte.

The first bit is going to be the continuation bit, which should just be a 0 meaning there is "Data" to follow, by this it could mean that the following information could be data or a command.
the DC bit will determine how the "Data" is interpreted.

126
Character LCDs / Re: Muli-language support for NHD‐0440WH‐ATMI‐JT#
« on: October 31, 2016, 08:24:30 AM »
All of our character LCDs can use one of the font tables that are found here: http://www.newhavendisplay.com/char_fonts.html
The controllers used for these LCD's are limited to only allow one font table used at a time.

However the controllers on our OLED displays have multiple font tables built in. Our standard character OLED has the following fonts built in: http://www.newhavendisplay.com/appnotes/fonttables/CharOLED/
You can select the font table by choosing it when using the function set command.

Our slim OLED displays also offer multiple font tables as well. You can see the offered font tables on pages 54-56 the controller datasheet: http://www.newhavendisplay.com/app_notes/US2066.pdf

127
TFTs / Re: Blank display after several hours of working normally
« on: October 27, 2016, 01:54:07 PM »
An external reset would clear the contents of the display.

However if the display is retaining the image in the RAM, it sounds like the power to the display might be dropping momentarily before the RAM losses the stored data.

128
TFTs / Re: Blank display after several hours of working normally
« on: October 25, 2016, 03:34:24 PM »
This does sound like something is causing the display to reset externally.

You should be able to fill the frame buffer at any time. After the display re-initializes and you send the display ON command, it will show whatever is filled in the buffer.

129
TFTs / Re: Blank display after several hours of working normally
« on: October 25, 2016, 11:49:48 AM »
Do you know if the voltage applied to the display pins 7&8 is constant the whole time.
Another cause could be a reset caused by either a loose connection or just power dropping.

Finally do you know if yoru code might be sending the Display OFF command or the Sleep Command?

130
TFTs / Re: Blank display after several hours of working normally
« on: October 25, 2016, 08:50:16 AM »
Hello,

It sounds like the display is getting reset.
Do you know if the Reset Pin on your display is tied high constantly?

131
Character LCDs / Re: Data Address
« on: October 24, 2016, 07:55:52 AM »
Hello,

Are you sending a command to go to line 2? [command(0xC0);]

Because of the way the controller is set-up, the RAM Address can be found on page 5 of the display datasheet.
You would need to use the Set DDRAM Address to move to line 2.

132
Character LCDs / Re: NHD-C0216CiZ-FSW-FBW-3V3 not working
« on: October 21, 2016, 03:09:51 PM »
Hello,

I have another example code for this display here:
I was able to get this to work with an Arduino Mega with a 3.3V regulator.

The Voltage should not be dropping to 2.1V when you plug in the display.
Has this only occurred with one unit or multiple units?
Can you also confirm that you are going right to left for the pin numbers?

Code: [Select]
/*****************************************************/
/*
C0216CiZ.c

  This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
  the Free Software Foundation; either version 2 of the License, or
  (at your option) any later version.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.
*/
/*****************************************************/

/*****************************************************/
unsigned char text1[]={"NEWHAVEN Display"};
unsigned char text2[]={"2x16 LCD Module "};
unsigned char text3[]={0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0a,0x0b,0x0c,0x0d,0x0e,0x0f};
unsigned char text4[]={0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17,0x18,0x19,0x1a,0x1b,0x1c,0x1d,0x1e,0x1f};
/*****************************************************/
#define SDO 22            //Serial data
#define SCLK 23            //Serial clock
#define RESET 24             //RESETET
/*****************************************************/
const char Slave = 0x7C;
const char Comsend = 0x00;
const char Datasend = 0x40;
const char Line2 = 0xC0;
/*****************************************************/

/*****************************************************/
void I2C_out(unsigned char j)       //I2C Output
{
  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);
    digitalWrite(SCLK, HIGH);
    digitalWrite(SCLK, LOW);
    }
  digitalWrite(SCLK, HIGH);
  while(SDO==HIGH){
    digitalWrite(SCLK, LOW);
    digitalWrite(SCLK, HIGH);
    }
  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(SCLK, HIGH);
}
/*****************************************************/
void Show(unsigned char *text)
{
  int n, d;
  d=0x00;
  I2C_Start();
  I2C_out(Slave);
  I2C_out(Datasend);
  for(n=0;n<16;n++){
    I2C_out(*text);
    ++text;
    }
  I2C_Stop();
}
/*****************************************************/
void nextline(void)
{
  I2C_Start();
  I2C_out(Slave);
  I2C_out(Comsend);
  I2C_out(Line2);
  I2C_Stop();
}
void CGRAM (void)
{
  I2C_Start();
  I2C_out(Slave);
  I2C_out(Comsend);
  I2C_out(0x38);    //go to instructino table 0
  I2C_out(0x40);    //Set CGRAM addRESETs to 0x00
  I2C_Stop();
  delay(10);
 
  I2C_Start();
  I2C_out(Slave);
  I2C_out(Datasend);
  I2C_out(0x00);    //write to first CGRAM addRESETs
  I2C_out(0x1E);
  I2C_out(0x18);
  I2C_out(0x14);
  I2C_out(0x12);
  I2C_out(0x01);
  I2C_out(0x00);
  I2C_out(0x00);    //8 bytes per character
  I2C_out(0x00);
  //continue writing to remaining CGRAM if desired
  I2C_Stop();
}
/****************************************************
*           Initialization For ST7032i              *
*****************************************************/
void init_LCD()
{
  I2C_Start();
  I2C_out(Slave);
  I2C_out(Comsend);
  I2C_out(0x38);
  delay(10);
  I2C_out(0x39);
  delay(10);
  I2C_out(0x14);
  I2C_out(0x78);
  I2C_out(0x5D);
  I2C_out(0x6D);
  I2C_out(0x0C);
  I2C_out(0x01);
  I2C_out(0x06);
  delay(10);
  I2C_Stop();
 
  //CGRAM();      //define CGRAM
 
  I2C_Start();
  I2C_out(Slave);
  I2C_out(Comsend);
  I2C_out(0x39);   
  I2C_out(0x01);    //go back Home
  I2C_Stop();
  delay(10);
}
/*****************************************************/
/*****************************************************/


void setup() {
  pinMode(RESET, OUTPUT);
  pinMode(SDO, OUTPUT);
  pinMode(SCLK, OUTPUT);
  digitalWrite(RESET, LOW);
  delay(10);
  digitalWrite(RESET, HIGH);
  delay(100);

}

void loop() {
  init_LCD();
  delay(2);
  Show(text1);
  nextline();
  Show(text2);
  delay(2500);
  while(1){
    digitalWrite(SDO, HIGH);
    delay(1000);
  }
       

}

133
TFTs / Re: NHD-7.0-800480EF-ASXV-T TFT screen image deformed
« on: October 19, 2016, 08:15:13 AM »
Responded to the email.
It looks like you are going under the assumption that all of the pixels are going to be squares.

This might not have to do with the settings you have listed. It seems you might be displaying a square image that is being stretched to fit the full display.
You might need to send another image that has 800x480 pixels to avoid the distortion.

134
OLEDs / Re: NHD 1.69 1601128ASC3 with Arduino Leonardo
« on: October 19, 2016, 07:58:36 AM »
One Code example that would allow you to show images saved onto the SD card can be found here: https://github.com/Pbartek/NHD_SEPS525

135
Hi David,

There should be no differences between the touch panel used between the two displays.

The only difference between the displays will be the backlight and polarizer used to provide the wide viewing angles for the NHD-4.3-480272EF-ASXV#-T.

Pages: 1 ... 7 8 [9] 10 11 ... 25