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

OLEDs / Re: Mouser Oled
« on: July 17, 2015, 12:31:44 PM »
Those are pins that would be on a level shifter and not the OLED. 4050 is the part number for level shifter

By any chance do you have another MCU that is 3.3V instead?

OLEDs / Re: Mouser Oled
« on: July 17, 2015, 12:09:46 PM »
Code: [Select]
#define   SDI_PIN    1    // SDI (serial mode) signal connected to pin 1
#define   SCL_PIN    0    // SCL (serial mdoe) signal connected to pin 0
#define    RS_PIN    8    // RS signal connected to pin 8
#define    RW_PIN    9    // R/W (6800 mode) signal connected to pin 9
#define    WR_PIN    9    // /WR (8080 mode) signal connected to pin 9
#define     E_PIN   10    // E (6800 mode) signal connected to pin 10
#define    RD_PIN   10    // /RD (8080 mode) signal connected to pin 10
#define   RES_PIN   11    // /RES signal connected to pin 11
#define    CS_PIN   12    // /CS signal connected to pin 12
#define   BS1_PIN   A0    // BS1 signal connected to pin A0
#define   BS0_PIN   A1    // BS0 signal connected to pin A1
#define   LVL_DIR   A2    // DIR (direction control) signal of level shifter IC connected to pin A2
#define   LVL_OEN   A3    // /OE (output enable) signal of level shifter IC connected to pin A3

So the pins you need to have connected

OLED                                                                                     Arduino/personal circuit
1,5,6,10,11,12,13,14,15,18,19,20            |                         Ground
2    Vdd                                                        |                         +3.3V
4     D/C                                                       |                         Pin 8   [D/C is often referred to as RS (register select)]
7 SCLK                                                         |                         Pin 0
8 SDI                                                           |                        Pin 1
16 /RES                                                       |                         Pin 11
17 /CS                                                         |                         Pin 12

Again I would recommend using a proper level shifting IC.

TFTs / Re: Backlight brightness with TFT displays (5" and 7")
« on: July 17, 2015, 11:08:05 AM »

The rating for the backlight is 50k Hours, until it reaches half brightness.

You can also bring down the current supplied to the backlight to increase its life.

The led's for the 5" display do draw more current than the ones for the 7".

OLEDs / Re: Mouser Oled
« on: July 17, 2015, 11:01:23 AM »
But the rest of the pins you're using are at 5V. They need to be brought down to 3.3.

What pin do you have D/C connected to on the Arduino?

The example code is verified to work so long as everything is wired up correctly.

OLEDs / Re: Mouser Oled
« on: July 17, 2015, 09:31:57 AM »
I'm not too sure what you mean by cc. But looking at your board the bottom right pin should be pin 1, above that is pin 2, one one on the the bottom next to 1 is 3. The on on the top left should be pin 20. Follow that along with the TABLE on page 4. the sketches again aren't always accurate.

You are might be using the 3.3V output from the Arduino, but everything else going in is 5V. So you can do one of two things to stop it from heating up.

1. Swap out the voltage regulator on the Arduino for a 3.3V and use a dc jack to power it something like 3.3 V Regulator on Mouser


2. Get a level shifter to bring down the 5V coming from your Arduino digital pins to 3.3V. Something Like This

OLEDs / Re: Mouser Oled
« on: July 17, 2015, 08:47:40 AM »
As for the heat the Arduino still uses 5V logic; you want to either modify the voltage regulator on the Arduino or you would need to use a level shifter to bring down the voltage to 3.3V. Although you might be using the 3V output from the Arduino itself to power the chip, the rest of the pins are still applying 5V.

As for the D/C pin,  you do need to have that connected if you're running in 4 line mode. you're probably looking at the last picture which is the 3 line SPI interface. the D/C is a signal that will tell the display whether the incoming information is a command or data.

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