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 ... 23 24 [25] 26
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.

OLEDs / Re: NHD-0220CW-AY3 Upside down text
« on: July 24, 2015, 10:28:00 AM »
Ok, I was able to replicate this issue thanks to Paul.

There is a command to let you flip the direction and orientation of the characters.

Check to see if you are sending a command(0x05) in your initialization after sending a (0x2A), that sets the screen Upside down.

If you want a quick fix, try adding
Code: [Select]

at the end of the initialization, that should do it.

OLEDs / Re: NHD-0220CW-AY3 Upside down text
« on: July 24, 2015, 09:06:33 AM »
Hi psullivan,

That display does like flipped upside down, and it shouldn't be.

I was wondering if you could possibly also post a picture of the back of that display, and your code.

TFTs / Re: NHD-2.4-240320CF-CSXI#-F minimal wiring for power
« on: July 24, 2015, 08:34:33 AM »
The backlight should turn on so long as you have the cathodes grounded and the anode tied to Vdd. I would measure the voltage across the cathodes and anode.

With the tight area, I would recommend also checking to see if anything is getting shorted.

TFTs / Re: NHD-2.4-240320CF-CSXI#-F minimal wiring for power
« on: July 23, 2015, 03:18:14 PM »
Hey Jesse,

I'm not seeing a connection from the backlight cathodes to ground, they seem like they're tied together but just floating.

Other things I would change is having the Reset pin attached to the MPU because it does net to be toggled for the initialization. and it seems you're going to be using 8-bit mode, you want to use DB8 - DB15 (PINS 22-29) of the display.

OLEDs / Re: Large custom fonts in 8080 parallel mode
« on: July 22, 2015, 03:12:47 PM »
This issue has been solved thanks to Michael L.

You have to change the variable for the index from an unsigned char to an unsigned int. The size of the array is too large to address with an unsigned char.

OLEDs / Re: Mouser Oled
« on: July 20, 2015, 09:26:45 AM »
When sending a byte of data using hex, you should only be sending in (0x00) to (0xFF) to denote that the value is in hex, leave off the h at the end.

OLEDs / Re: Mouser Oled
« on: July 20, 2015, 08:27:49 AM »
As for the commands such as Display Off you would want to use the display mode command, if you look at the Controller Datasheet on page 43 it shows you how the different display modes will work depending on what command you send to the display.

With the text, there is no built in font tables or text saved on the controller. If you look at the example code given, it does have a font table that was previously created. You would have to use another set of commands to display that text. You would also need to send the X and Y positions you want the text to appear. And if you're using the same codes you need to specify the text color and background color as well to ensure it works. For the regular sized text the OLED_Text_128128RGB command will work on showing the text. (Each character will be 5 pixels wide, and 8 pixels tall). If you want the larger text, use the OLED_Text2x_128128RGB command.

OLEDs / Re: Mouser Oled
« on: July 17, 2015, 02:14:44 PM »
Those pins are not on the display correct, they're pins that should be on the Level Shifter.

If you take a look at page 3 of the DATASHEET , Michael linked you to, you will find those pins.

The DIR pin controls the direction of shift, whether the signals go from Port A to B or B to A.

The /OE is an Active Low output enable signal. Again both of these pins are on the level shifter.

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