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 2 [3] 4 5 ... 23
31
Character LCDs / Re: NHD-0216K1Z
« on: July 21, 2017, 08:25:07 AM »
Can you tell me what letter you are seeing on your display?
Also How long are the delays in your code?

32
OLEDs / Re: Too much current in sleep mode
« on: July 20, 2017, 04:58:04 PM »
Luis,

Unfortunately the datasheet needs to be updated to account for the DC/DC converter.
This does not shut down when the display enters sleep mode so the voltage is constantly being stepped up.

33
OLEDs / Re: Too much current in sleep mode
« on: July 17, 2017, 08:24:41 AM »
Luis,

The current is being drawing by the DC/DC convertor.
It often draws more current when its not being powered.

34
Character LCDs / Re: Problems with a NHD‐0420H1Z‐FL‐GBW‐3V3
« on: July 17, 2017, 08:17:45 AM »
Hi,

Can you tell me what the voltage you have going to VDD and V0 are for this display?


35
Would it be possible to get a picture of your display and the code you are using?

I would like to see if we can recreate the same problem.

36
Graphic LCDs / Re: 1.8V IO on NHD-2.4-240320CF-CTXI-F
« on: June 28, 2017, 11:30:55 AM »
While the controller for the display (ST7789S) Can work with a 1.8V system, the display will need 3.3V.
Because of this you CAN  use 1.8V on the IOVDD and 1.8V Logic with the data lines (DB0-15, /CS, D/C, /WR, /RD, /RES, IM0)
However you would need to apply 3.3V to the VDD for the LCD circuit. Is it possible for you to supply the +3.3V for the LCD alone?

The logic voltage should be related to the IOVDD, i will make this correction on future spec upgrades.

37
TFTs / Re: Graphic software for NHD-4.3CTP-SHIELD-V
« on: June 26, 2017, 08:39:38 AM »
Hello George,

I would recommend using the FTDI Screen Editor Software, this can be found here: http://www.ftdichip.com/Support/Utilities.htm#EVEScreenEditor

FTDI also includes a user guide to help you get started as well.

38
TFTs / Re: Using RGB666 on NHD-4.3-480272EF-ATXL#-T
« on: June 14, 2017, 08:00:03 AM »
Hello,

You would want to ground the unused RGB pins. These would be the LSB (R0,R1, G0, G1, B0, B1)

39
OLEDs / Re: NHD-3.12-25664UCB2 Problem Displaying Text
« on: June 09, 2017, 10:24:42 AM »
Unfortunately i am not aware of anyone that has example code for that.
However most libraries do come with a simple example, or someone might have created a fork for that as well.

40
OLEDs / Re: NHD-0216CW-AY3 VDD and REGVDD pin && SPI example
« on: June 05, 2017, 08:05:32 AM »
The OLED typically runs off 2.8-3.3V, When using 5V you would enable it so that the OLED will regulate the voltage down to the 2.8-3.3V levels.

41
OLEDs / Re: NHD-0216CW-AY3 VDD and REGVDD pin && SPI example
« on: June 02, 2017, 09:40:25 AM »
Hello,

I am not sure if i understand your first question.
However with the logic being set at 3.3V, you will want to make sure your SPI counts 3.3V as high, and GND as low.

If you are using this display in 3.3V you will want to ground RegVDD, and in the software you will want to disable the regulator.
the KGZ code will not work for this display.

You can find the example code for this display here: https://github.com/NewhavenDisplay/NHD_US2066

42
OLEDs / Re: NHD-3.12-25664UCB2 Problem Displaying Text
« on: June 02, 2017, 09:04:30 AM »
The display can do both, however this controller does not come with a built in font library.
Many of our customers use a library like the one i linked for fonts.

43
OLEDs / Re: NHD-3.12-25664UCB2 Problem Displaying Text
« on: June 01, 2017, 10:37:01 AM »
Unfortunatley we do not have a font library for this display currently.

However you can find many user created libraries that are Arduino Compatible through sites such as GitHub.

For instance : https://github.com/harlequin-tech/OledHQ
This library includes a font table, along with brightness control as well.

45
Hello David,

If you have VDD and VSS going to pins 2 & 3 of the display, they do not need to be applied to pins 5 & 6, they are all tied internally.

For this i would recommend using the following:
putc(0xFE)  // Prefix
putc(0x51) // Clear Screen

Pages: 1 2 [3] 4 5 ... 23