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

Pages: 1 ... 4 5 [6] 7 8 ... 24
OLEDs / Re: nhd-0216cw-ar3 - locks up
« on: February 13, 2015, 04:47:46 PM »
Do you have any other devices present on the I2C bus?  If so can you please isolate the display on it and try testing this again?  Whether already isolated or not, can you try using the display again with larger pull-ups? (Try 10kΩ)

OLEDs / Re: NHD‐3.12‐25664UMB3 3 or 4 wire interface
« on: February 13, 2015, 04:43:21 PM »
The 4 pins (pins 19-22) are the serial lines for the multi-font IC on that display's PCB.  It is merely a chip with many different fonts/languages stored on it, and is separate from the display's controller.
That being said, the pins 7 and 8 are the serial lines for the actual display.  For the 4-wire mode, pins 4 and 16 are used with them, and for the 3-wire mode only pin 16 is.  For a clearer understanding of this, please refer to the table in the datasheet on page 5 titled "MPU Interface Pin Assignment Summary".

The logic levels the ST7066U controller can accept are not the only determining factors for being able to use a display with different voltages.  Based just off the controller specification regarding the voltage/logic level range, it seems like the 5.0V display would work fine with 3.3V.  However, the liquid crystal (the display glass) is different between the two.  Therefore, the voltage required for the glass is different.  You will notice a different VLCD rating in the datasheets, this refers to what I have just described.

If you are interested in a custom display to better suit your needs, feel free to email with your requirements and we can work with you to determine feasibility and cost.

TFTs / Re: NHD-5.7-320240WFB speed up Background
« on: February 02, 2015, 03:15:27 PM »
You will need to either increase your write speed, or blank the display while writing the new data and then turning it back on when done.  I'm sorry but there is no feature/command on the SSD1963 to change the background color quickly.

Character LCDs / Re: NHD-C0216CIZ Not Acknowledging
« on: January 29, 2015, 08:06:53 AM »
Have you checked your timing?  Sometimes if you are near the timing threshold on a display, you will get inconsistent results.  Please make sure you are allowing enough execution time for each command in the initialization.  You can see the execution times listed on page 7 of the display's datasheet.  You will notice the clear display and return home commands have longer execution times than the other commands (1.08ms).  Please verify this, and if you are unsure you can try adding delays after each command send.

OLEDs / Re: NHD-3.12-25664UCY2 flickering
« on: January 29, 2015, 07:54:29 AM »
I'm sorry but unfortunately we do not have such a guide explaining all the commands.  The controller's datasheet should have sufficient information for this.
Here is a link to it:

In terms of the initialization, please use our example initialization sequence in the display's datasheet, page 12.  There is no flickering present with this initialization.

Character LCDs / Re: NHD-C0216CIZ Not Acknowledging
« on: January 26, 2015, 03:48:46 PM »
Since you have one board that works with the display and software used, and another board that doesn't, it seems to be some issue with the second board.  Perhaps the solder flow isn't perfect on the non-working board.  If you are looking to debug this issue, that is where I would start.

OLEDs / Re: NHD‐0420CW‐AB3 I2C Interface
« on: January 23, 2015, 10:00:06 AM »
Perhaps the below code snippets will better assist you:

Code: [Select]
const char slave2w = 0x3C;

void send_packet(unsigned char x)
  unsigned char ix;

void command(unsigned char c)
      tx_packet[0] = 0x00;
      tx_packet[1] = c;

void data(unsigned char d)
      tx_packet[0] = 0x40;
      tx_packet[1] = d;

OLEDs / Re: NHD-2.23-12832UCB3 memory display
« on: January 23, 2015, 09:48:21 AM »
For this information, please refer to pages 40/41 of the controller's datasheet for that display, here:

TFTs / Re: Example Arduino Code for the NHD-4.3-480272EF-ATXL#-CTP
« on: January 23, 2015, 09:45:00 AM »
You can use the Arduino with the display but you will need a TFT controller.  It is not capable of driving it by itself.
For information on TFT interface signals, I would recommend you do some research via the Internet.  It is not something simply explained in a forum post.  Here's one link I found that has information on these signals, however there are many others:

Graphic LCDs / Re: NHD‐0216PZ‐FL‐YBW
« on: January 23, 2015, 09:37:27 AM »
I'm sorry but we do not have any information specifically for a Parallax MCU, but we do have example code for the display available on our example program code website.
Please refer to the link below:

Character LCDs / Re: NHD-C0216CIZ Not Acknowledging
« on: January 23, 2015, 09:33:30 AM »
You mention you are using 10kΩ pull-ups, but your schematic shows different.  Can you confirm if you have 10kΩ pull-ups?  Please also ensure all soldering is good and you have connectivity to all signals.

TFTs / Re: Example Arduino Code for the NHD-4.3-480272EF-ATXL#-CTP
« on: January 21, 2015, 07:53:47 AM »
You are referring to the incorrect example code link.  Please see below:

Please note that this is example code for the display when used with our NHD-4.3-480272MF-20 or NHD-4.3-480272MF-20 (uses the SSD1963 controller).  The TFT panel without a controller does not require any initialization code, as there is no controller to initialize.  TFT panels without controllers are like monitors that accept a digital RGB interface, basically like digital VGA.  You would either need an MCU that has the proper signals/drivers for a TFT display, or you would need to use an external TFT controller.

TFTs / Re: Controller for 800x480 TFT Display
« on: January 19, 2015, 02:34:41 PM »
TFTs typically have a digital RGB interface (essentially digital VGA) and are simply LCD panels that require pixel data (RGB data bus) and timing/synchronization signals (HSYNC, VSYNC, pixel clock).
Using a TFT with a TFT controller, such as the SSD1963, allows for a standard MCU type interface (8/16 bit parallel data bus, control signals such as command/data selection, active LOW write, etc.)
The TFT controller outputs the necessary 24bits of RGB, and the timing signals for you.  Some development boards / microcontrollers have TFT drivers/controllers built-in, and would therefore not need an external TFT controller such as the SSD1963.  Most others do not have a TFT driver/controller, which is where you would typically use an external one.  There are several TFT controllers on the market (the SSD193 being one of them) so you may use whatever you prefer.

Yes, the NHD-7.0-800480EF-ATXL#-T can be used with the NHD-7.0-800480EF-34 Controller Board (16-bit interface) or the NHD-7.0-800480EF-20 Controller Board (8-bit interface).

Many customers either prefer driving our TFTs directly, or with some other TFT controller they are using or have used.  This is why it is best to offer our TFT displays without controllers included.

OLEDs / Re: Safe to run NHD-0216CW-AB3 displays at 3.3V long-term?
« on: January 14, 2015, 10:04:52 AM »
Yes, it is absolutely safe to run these displays at 3.3V long-term.

Pages: 1 ... 4 5 [6] 7 8 ... 24