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

Pages: 1 ... 13 14 [15] 16 17 ... 20
211
Morning,

Correct, this VFD display has a 14 pin connection (see picture attached). The 5-wire cable is soldered to Pin NO. 1,2,3,4,6

Pin-Out:

1. GND
2. Vcc
3. SI/SO
4. STB
5. SCK

Please let me know if you need any additional help  ;)


[attachment deleted by admin]

212
OLEDs / Re: NHD-0216CW module using SPI - Question
« on: June 22, 2015, 07:50:33 AM »
Morning Fred,

Below is some example code written for the Arduino  ;)

https://github.com/NewhavenDisplay/NHD_US2066

Next, (IS, RE and SD) will need to be configured correctly in order for the controller to correctly identify which command the user wishes to execute. Take a look at the initialization sequence (File: NHD_US2066.cpp). The code is heavily commented and should clear up any questions.

Please keep us posted on your progress!


213
Hello,

To answer your question, yes you can use the linker cable as long as the pin-out matches your motherboards serial header.

Please see page 16 in the displays datasheet regarding the pin-out and how to configure the jumper settings.

http://www.newhavendisplay.com/specs/M0220SD-202SDAR1-S.pdf

Hope this helps!



[attachment deleted by admin]

214
Character LCDs / Re: NHD-0212WH-ATMI-JT# on 3.3V
« on: June 10, 2015, 02:00:01 PM »
Hi Dave,

Glad to hear, thank you for posting an update  :)

215
OLEDs / Re: NHD-0420CW-AG3 Pixel Test
« on: June 05, 2015, 07:39:57 AM »
Not a problem, have a good one!

216
OLEDs / Re: NHD-0420CW-AG3 Pixel Test
« on: June 04, 2015, 08:39:08 AM »
Hello,

Burn-in (as in ghostly image) is a more susceptible to OLED displays, however it can still occur with standard LCD's.

The length of time required for noticeable screen burn to develop varies due to many factors. It can take as little as only a few weeks for noticeable ghosting to set in, especially if the screen displays a certain image (example: a menu bar at the top or bottom of the screen) constantly, and displays it continually over time.

Please note that screen burn-in can easily be avoided, you may want to think of a plan to reduce long-term display in the same place on the screen.

Below are a few simple steps you can take to prevent burn-in:

E.g. In your case maybe install a PIR sensor to turn off the display when no one is in proximity of the unit.

E.g. Enable the OLED's built-in scroll feature.


Finally, Karma points are given by members to other members for any reason, usually for answering or posting a helpful question  8)

217
OLEDs / Re: NHD-0420CW-AG3 Pixel Test
« on: June 03, 2015, 08:33:47 AM »
Hello,

I have seen similar behavior before usually caused by ESD (Electrostatic Discharge) damage to the module / controller. Unfortunately in this case the damage is irreversible, generally devices with finer geometries are more susceptible to damage from ESD.

I always recommend working on a static-safe work bench and following the appropriate procedures to ensure your device is protected from ESD. This includes grounding enclosures, bezels, etc ...

Finally, can you please tell me what steps you took to ground your devices as a whole?

Thanks!







 

218
Hello,

To answer your question yes, it is definitely possible. If you have some shorter jumper wires on hand it wouldn't hurt to swap them out.

However, I do not believe this is the culprit  ;)

219
Hello,

Regarding your first post, can you please tell me if your MCU has built-in pull up resistors?

If so it is possible that it could be causing a weak pull-up.

Finally, I recommend you use 10k Ohm resistors. If you get no response we will continue to debug  8)

Thanks!



220
OLEDs / Re: OLED dark horizontal bands
« on: May 14, 2015, 08:15:23 AM »
Hello Edwin,

Since these OLEDs are passive matrix displays unfortunately there will always be slight banding. You can reduce the effect by adjusting the registers like you previously stated.

221
TFTs / Re: NHD-5.0-800480TF-ATXL#-CTP backlight Driver
« on: May 13, 2015, 05:05:39 PM »
Hello,

There are no discrepancies within the NHD-5.0-800480TF-ATXL datasheet.

The backlight supply current values are: Min - 45, Typ. - 60 and Max. 75 mA

There must be an issue with your wiring or backlight circuit. Please note you have to limit your current. The reason your display is getting hot is because the supply current is 250mA.  :o





222
Character LCDs / Re: NHD-C0220Biz and Arduino/Teensy3.1
« on: May 13, 2015, 07:52:28 AM »
Hello,

I'm sorry to hear about the issue you encountered. We have a set quality control process that is followed for every part so I'm not sure how this one got through, but we will make a note to double-check this type of issue during our QC inspections. I apologize for the inconvenience.

Please contact:

quality@newhavendisplay.com

Thanks!

223
TFTs / Re: NHD-2.4-240320SF-CTXI#-FT1
« on: May 12, 2015, 02:15:46 PM »
Hello,

Pin 14 (DB0) is the LSB (least significant bit) of the data byte.

Pin 29 (DB15) is the MSB (most significant bit) of the data byte.

Hope this helps!

224
Vacuum Fluorescent Displays / Re: "C-20-503F" vfd NEWHAVEN
« on: May 12, 2015, 12:24:53 PM »
Hello,

Thank you for the datasheet! This was a custom design which is why I did not recognize the part number.

Please note this is a non-stocked part, there will also be a MOQ (Minimum Order Quantity) when placing an order.

If you would like more information please contact me below:

pbartek@newhavendisplay.com

Thanks!

225
OLEDs / Re: NHD-0420CW With PIC32MX Controller
« on: May 12, 2015, 09:37:32 AM »
Excellent, thank you for the clean wiring diagram  ;)

The good news is that your wiring is correct, the issue must be within your code.

Your initialization appears to be correct, I suspect the problem is how your SPI is configured.

SPI Example:

Code: [Select]
case 2:   
              temp = 0xF8;
              for(i=0;i<8;i++)
              {
                digitalWrite(SCLK, LOW);
                if((temp&0x80)>>7==1)
                {
                  digitalWrite(SDIN, HIGH);
                }
                else
                {
                  digitalWrite(SDIN, LOW);
                }
                temp = temp << 1;
                digitalWrite(SCLK, HIGH);
              }
 
              for(i=0;i<4;i++)
              {
                digitalWrite(SCLK, LOW);
                if((c&0x01)==1)
                {
                  digitalWrite(SDIN, HIGH);
                }
                else
                {
                  digitalWrite(SDIN, LOW);
                }
                c = c >> 1;
                digitalWrite(SCLK, HIGH);
              }
              for(i=0;i<4;i++)
              {
                digitalWrite(SCLK, LOW);
                digitalWrite(SDIN, LOW);
                digitalWrite(SCLK, HIGH);
              }
              for(i=0;i<4;i++)
              {
                digitalWrite(SCLK, LOW);
                if((c&0x01)==1)
                {
                  digitalWrite(SDIN, HIGH);
                }
                else
                {
                  digitalWrite(SDIN, LOW);
                }
                c = c >> 1;
                digitalWrite(SCLK, HIGH);
              }
              for(i=0;i<4;i++)
              {
                digitalWrite(SCLK, LOW);
                digitalWrite(SDIN, LOW);
                digitalWrite(SCLK, HIGH);
              }
              break;
  }

If you have an oscilloscope on hand I highly recommend checking your data lines and posting some screen shots.

Pages: 1 ... 13 14 [15] 16 17 ... 20