Recent Posts

Pages: 1 ... 8 9 [10]
91
TFTs / EVE2 with Parallax Propeller MCU
« Last post by Rayman on June 01, 2018, 02:13:17 PM »
I just recently got a Newhaven EVE2 module working with Parallax's Propeller MCU in Spin language.
I'm really liking EVE2!

You can download my code from the Propeller forum here:
https://forums.parallax.com/discussion/168553/

I have to say the example code provided by Newhaven looks very nice, but was hard to follow...
Needed it to get the correct display timing info for the display.
I guess if you're an Arduino person, you'd be in good shape though.
I figured out most of this using the EVE2 programmer's guide.
92
The NHD-7.0-HDMI-N-RSXV-CTU LCD display module has a stated resolution of 800 X 480, but the module reports a resolution of 1024 X 768 to the operating system (i.e. Windows 10 reports 1024 X 768 as the "native" resolution of the panel).

When connected to a PC running Windows 10, this results in the lower and right sides of the desktop being cut off and the touch screen basically useless as all touches do not map to the physical screen. I was able to correct this by setting a custom screen resolution of 800 X 480.

I am also testing this display with Android and Windows 10 IoT Core.

In both cases, the operating system will NOT allow me to change the resolution to the correct 800 X 480.

I am able to compensate for the screen by setting the size of my application to 800 X 480 (with no scaling) which results in an application that fits exactly on the screen.

The touch screen in this case is still useless as the touches still appear to be mapped to a different display size and thus do not correspond to objects on the screen.

The two options to correct this issue are to (A) get the display to report the correct resolution via HDMI,  or (B) re-calibrate the touch controller to map to the usable area of the display.

While (B), recalibrate the touch controller seems the most practical, I am not sure how (B) can be done on this display. This model is a capacitive touch model which appears to use a PIC18LF2550 as a touch controller. There are calibration utilities for the resistive touch model using an AR1100 controller, but I cannot find a corresponding utility for the capacitive touch model.

Please advise on how to correct this issue.
93
Customer Projects / Re: New Support library for Screen EVE2 NHD Playback videos
« Last post by Paul_B on May 29, 2018, 08:24:42 AM »
Hi Lightcalamer!

Thank you so much for sharing, I look forward to seeing what the 'MexSpa' team puts out next.

Best Regards,
94
OLEDs / Re: NHD-2.7-12864UCY3 replace to previous version
« Last post by Paul_B on May 29, 2018, 08:13:40 AM »
Hi Zsolt,

The Newhaven Display 2.7” Monochrome Graphics OLED module, NHD-2.7-12864UCY3, has reached End-Of-Life and is being replaced by our new and improved 2.7” OLED module, the NHD-2.7-12864WDY3.

The new module has been designed to match the physical dimensions of its predecessor, and will fit into any existing housings/enclosures used currently. However, due to the current OLED panel’s built-in controller being discontinued, the new module will not be a drop-in replacement.

A product EOL (End‐Of‐Life Notification) was sent out on June 8, 2017.

If you are interested in received the Product EOL/Replacement Transition Guide, please see the link below:

http://www.newhavendisplay.com/docs/NHD-2.7_Transition_Guide.pdf

The purpose of this document is to highlight and explain the key differences that need to be accounted for when transitioning from the ‘EOL’ to ‘NEW’ 2.7” Monochrome Graphics OLED module from Newhaven Display.

Best Regards,
95
OLEDs / NHD-2.7-12864UCY3 replace to previous version
« Last post by telmo on May 28, 2018, 12:25:06 AM »
Hi,
The new NHD-2.7-12864UCY3  is not compatible with the previous version.

We have a product equipped with the previous version of NHD-2.7-12864UCY3. Does any easy way to insert the new product into the existing faulty place? What kind of HW and SW modifications is needed?
We need a few pieces for service purpose (less than 100). Are there anybody who has some on stock?

Thank you
Best regards,
Zsolt
96
News.

June 7, Team MexSpa publish library all series MCU' s STM32F4x, Nucleo-F7x  F103x, and Teensy 3.5/6 playback videos .avi (with sound) here a preview of the future ...

Video library launch; https://youtu.be/O8OUXB02g3w

Best regards.
97
These OLEDs are passively drawn, which means that each line is lit at once. If you have a line with almost all the pixels lit it wont be as bright as a line with only 50% or less lit up.
98
Hello Bill,

Unfortunately because these are Passive Matrix OLEDs the brightness of the pixels can vary based on how many pixels are on in a row.
The brightness will be higher if you only have a few pixels lit, as opposed to having the whole row on.
99
OLEDs / NHD-3.12-25664UCY2 display - inconsistent pixel brightness in same areas
« Last post by bill on May 23, 2018, 09:11:33 AM »
Hello,

    Using the NHD-3.12-25664UCY2  (256 x 64) using the 4-wire interface I have no problems sending full screen images and displaying them.  However all the images and patterns I send use the same grayscale value.  However, on the display some of pixels vary in their grayscale/intensity?  It's always the same pixels too.  I have tried two different displays with same results.  I would think if its noise that the pixels would be random but they are always the same. I checked the initialization sequence and it matches example in the data sheet.

    I have attached two images.  One with a picture and one with all the pixels set at the same greyscale level  (0x04).   On the image with all set to the same greyscale you can see a rectangle area at the left and right side of the LCD - but I am sending all the same greyscale values.  With the picture on some of the pixels are of different brightness/grayscale.

Please help.

Thanks,
Bill





100
TFTs / Re: EVE2 Startup for 7" Display
« Last post by warriorofwire on May 22, 2018, 01:18:23 AM »
Thanks for the reply!  I had a bug with my vertex2ii command bits.  I realized this when I was able to tweak the background color.  It's now working as expected.

I'm building a more trimmed, straightforward library for my simple consumption (no ifdefs).  The next hurdle is bitmap display!
Pages: 1 ... 8 9 [10]