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 ... 22 23 [24] 25 26
OLEDs / Re: NHD-0420CW-AB3 init / cgram
« on: August 05, 2015, 08:15:44 AM »
One thing I've noticed and I'm not sure if you're doing it else where, the (0x00) you are sending for ROM selection should be sent as data and not a command. Same would be true when you are disabling the internal voltage regulator.

OLEDs / Re: NHD-0420CW-AB3 init / cgram
« on: August 04, 2015, 08:17:07 AM »
I was wondering if it would be possible to see your code specifically how you are writing either data or commands to the display. Also where you are selecting the ROM for custom characters..

OLEDs / Re: NHD-0420DZW-AY5 with scrambled display
« on: August 03, 2015, 10:31:13 AM »

I was wondering what that WaitReady function?

I still suspect timing might be the issue.

For the Write LCD function you mention that the execution time for previous command is around 300us. In the Table of command it does mention that most of the commands do have a 600us max execution time.

OLEDs / Re: NHD-0420CW-AB3 init / cgram
« on: August 03, 2015, 10:18:40 AM »
That 0x72 followed by data 0x00, selects ROM A.

I was wondering if you could post the code of how you are accessing the CGROM to put a character in the memory; also how you are printing the character out.

Example for what I have done to load a custom character in is:
Code: [Select]

OLEDs / Re: NHD-0420DZW-AY5 with scrambled display
« on: July 31, 2015, 07:44:02 AM »
Would it be possible to take a look at the code you are using to initialize the LCD and write to it?

OLEDs / Re: NHD-0420DZW-AY5 with scrambled display
« on: July 30, 2015, 02:49:50 PM »

From past experiences, it's usually a timing issue that causes strange characters to appear onto the display. This usually happens after the units have been running for a while. Usually when the timing commands are right on the threshold of the specifications.

I was wondering if you could tell me what interface you were using?

OLEDs / Re: SPI Communication Start Byte
« on: July 30, 2015, 11:05:12 AM »
You should be able to send continuous commands as well.

The minimum wait time should be about 40 ns. For the clock rise time, and the clock rise time plus hold time.

TFTs / Re: Controlling NHD-3.5-320240MF
« on: July 29, 2015, 08:04:28 AM »
The NV3035C is just the Driver, we do have controller boards specifically for this display. You can choose from either:

8-bit Parallel:
16-bit Parallel:

TFTs / Re: Controlling NHD-3.5-320240MF
« on: July 28, 2015, 07:49:29 AM »
Hi Cho,

Our 1.8" Displays have a controller built-in, so when you're programming directly from your MCU you're still talking to a TFT controller.

Unless your MCU has a built in TFT controller you might not be able to directly connect to the 3.5" display.

Character LCDs / MOVED: NHD-0420DZW-AY5-ND
« on: July 27, 2015, 01:26:17 PM »

OLEDs / Re: NHD-0420DZW-AY5-ND
« on: July 27, 2015, 10:56:19 AM »
Hi Mahesh,

If you could please submit a request to

We will be able to help you with the code there.

Character LCDs / Re: NHD-C0216CZ-NSW-BBW-3V3 does not show anything
« on: July 27, 2015, 10:33:35 AM »
First thing that jumps out is that the Follower Control value should be 0x6D if you are following the example on our website.

Also verify that the voltage on pin 7 is near 5.5 volts.

EDIT:  Display is now working.

You need to apply a 3.3V signal to the B/L Enable to turn on the backlight. You would also need to make sure the Vdd and Gnd are also connected as the backlight will be drawing current from pin 2.

Also if possible check the current draw for Pin 2 to see if there is enough current to power the backlight. Looking at the Characteristics, you would need a minimum or 45mA just for the backlight.

OLEDs / Re: NHD‐1.5‐128128UGC3 Scanning between functions
« on: July 27, 2015, 09:58:39 AM »
That would possibly help, check to see if you r graphic acceleration command isn't setting up a scrolling problem.

If you are moving it on purpose, you will need to rewrite the ram data after you stop the scrolling.

OLEDs / Re: NHD‐1.5‐128128UGC3 Scanning between functions
« on: July 24, 2015, 10:31:40 AM »
Could you give us a bit more information about what the button is doing? But the screen will display from the bottom to the top.

Pages: 1 ... 22 23 [24] 25 26