Show Posts
Pages: 1 [2] 3 4 ... 9
16  Using Arduino / Programming Questions / Re: format of the bitmap .c file on: August 28, 2013, 09:56:49 am
It looks to me to be raw image data.

The image, as the comments show, is 4x12 pixels.  4x12 = 48.

The data is 96 bytes.  96 / 48 = 2.  So two bytes per pixel.  Given the name of the program, that's what I'd expect.

565 is a 16-bit RGB colour space definition - 5 bits of red, 6 of green (the eye is more sensitive to green) and 5 of blue: RRRRRGGG GGGBBBBB

So each word is a single pixel in 565 RGB format, probably in a left-to-right, top-to-bottom arrangement.

You couldn't be more correct smiley

Each word is a RGB565 encoded value for a pixel starting from the upper left corner, going alone each line to end up in the lower right corner.

UTFT does not support transparency.

17  Using Arduino / Programming Questions / Re: Changing a sketch to work in the UTFT Libary "2.8" LCD display") on: August 08, 2013, 02:28:27 am
The "problem" is that the UTFT class you are using is pretty dumb. It does not know how to print a float. So, you must convert the float to a string first, using dtostrf().

Another solution would be to try reading the manual (included in the UTFT download) where one can find useful information, like how to print floats with printNumF()...

18  Using Arduino / Programming Questions / Re: utouch ssd1963 5 inch problem on: July 30, 2013, 10:21:08 am
Sainsmart, Elecfreaks, Itead... same products, different names.

If they are really the same product, please explain this:
I checked the emails I got over a six month period, and the percentage of emails ultimately caused by hardware problems turned out like this:
- ITead: 1.6%
- ElecFreaks: 1.8%
- SainSmart: 98.3%

Does not look like they are the same products to me...

19  Using Arduino / Programming Questions / Re: utouch ssd1963 5 inch problem on: July 30, 2013, 09:44:03 am
doesn't work as it should

This does not provide me with any information at all...

The calibration sketch have been tested on all the supported displays, but the SainSmart module will never be among them. SainSmart products are generally of so low quality that I say far away from them.

20  Using Arduino / Programming Questions / Re: utouch ssd1963 5 inch problem on: July 30, 2013, 09:22:05 am
CAL_X: 0x020D87E0
CAL_Y: 0x01F54701
CAL_S: 0x8031F1DF

The data you got here is normally in indication of a defective touch screen (or a completely incompatible display module)...

21  Using Arduino / Programming Questions / Re: utouch ssd1963 5 inch problem on: July 27, 2013, 06:29:29 am
CAL_S: 0x001DF31F

This line tells me that you have not followed the instructions in the manual.
If you had set the TOUCH_ORIENTATION correctly it should be 0x8031F1DFUL.

From the UTouch manual: 3.   Make sure the TOUCH_ORIENTATION define is correct. You can find a list of the correct parameter for all the tested displays in the UTouch_Supported_display_modules PDF.

From the UTouch_Supported_display_modules.pdf:
Notice the pattern? Every 5" module I have seen should have TOUCH_ORIENTATION set to LANDSCAPE...
This is also true for the module used in the video shown earlier in this thread.

22  Using Arduino / Programming Questions / Re: utouch ssd1963 5 inch problem on: July 26, 2013, 11:37:18 am
How about actually reading the UTouch manual, and especially the part about calibrating.

Proper calibration of the touch screen is REQUIRED when using anything other than a 3.2" display module and may be required even with those as there are minor difference in every single touch screen.

With proper calibration the getX() and getY() functions will be scaled correctly.

23  Using Arduino / Displays / Re: Womart TFT LCD Shield + Touch Panel Display on: July 10, 2013, 02:49:01 am
Also, if you get a sketch is too big error in the examples under UTFT, all you need to do is comment out the #include directive for UTFT.h and the go to sketch menu and use import library to put UTFT back in the program.  This puts an #include directive for savmemory.h in ahead of UTFT.  I still can't get them to run, but this lets me load them.

I really wish people would read the ******* manual...

In the box marked 'IMPORTANT' you will find the following paragraph:
Since most people have only one or possibly two different display modules a lot of memory has been wasted to keep support for many unneeded controller chips.
As of v1.1 you now have the option to easily remove this unneeded code from the library. By disabling the controllers you don't need you can reduce the memory footprint of the library by several Kb. For more information, please refer to memorysaver.h.

To make use of the feature you will actually have to make some modifications to the file, but including it in the sketch does absolutely nothing as it is already included by UTFT.cpp.

24  Using Arduino / Displays / Re: Rotate 5110 display on: April 12, 2013, 07:27:50 am
The PCD8544 display controller does not support rotating the display so it would mean that it would have to be done in software.

I do not plan on adding that to my libraries as it would only slow things down and it is also fairly easy to plan ahead and mount the display module upside down.

25  Using Arduino / Displays / Re: ANOTHER Sainsmart 3.2" TFT Screen topic.. on: January 31, 2013, 08:45:00 pm
The LED-A is supposed to get 5v. It is only used for the backlight.
The problem is all of the signal pins. They are rated for a maximum input of Vddio which in the case of the SSD1289 is maximum 3.6v (typically 3.3v).

You don't have to use a shield, but there is a possibility of killing your screen if you don't lower the signal voltage. This can normally be done by running a 10k ohm resistor in series with each signal (applies to the display, touch screen and the SD card).

It is possible to use 74HC595s to reduce the pin count, but you will have to rewrite the I/O part of the library, and the data transfer rate will be much slower.

26  Using Arduino / Displays / Re: ANOTHER Sainsmart 3.2" TFT Screen topic.. on: January 31, 2013, 11:49:36 am
The noise you are getting is quite common when you are feeding the 3.3v TFT controller with 5v signals....

There is actaully a reason why there are resistors or level translating ICs on the adapter shields.

27  Using Arduino / Displays / Re: My ITDB02 keeps being blank on: January 24, 2013, 01:27:54 pm
If you are not afraid of a little soldering you can use this:

You can probably find something similar already soldered on eBay or something as well. The main thing is that you should be looking for a pre-v2.0 shield.
These usually have jumpers to select between 8bit and 16bit modules.

Just be aware that a 16bit display module will use all the available I/O on the Uno just for the display. You will not be able to use the touch screen or the SD card slot.

28  Using Arduino / Displays / Re: My ITDB02 keeps being blank on: January 24, 2013, 06:28:22 am
You are not doing anything wrong. You have just bought hardware that is incompatible.

Your shield only supports 8bit display modules, and the display modules is a 16bit module.
You will never be able to get it working without extensive modifications to the shield.

29  Using Arduino / Project Guidance / Re: What's out there? on: January 01, 2013, 08:09:40 pm
As you are on a tight budget I would recommend getting one or two of each of these:


That would give you a lot of LEDs and resistors to start your learning experience.

30  Using Arduino / Displays / Re: TFT becomes pixelated and goes white on: January 01, 2013, 05:02:13 pm
Can I expect this chip is fried?

I wouldn't think so. I used the old ITead shields (resistor-based) for many hours on the 4.3" and 5.0" modules (without much luck), yet the display modules were not damaged at all.

Pages: 1 [2] 3 4 ... 9