Testing ColdTears Electronics TFT Displays

The desplay demos with the UTFT_CTE library allow selection of
a Sketch for the CTE70 (7" 800x450), the CTE50 (5" 800x450),
and the CTE32HR (3.2" 480x320), and they work fine on
my 5" and 3.2" displays (I did not yet try it on the 7" display).

However, there is no Sketch for the 4" 480x320 or the
slightly smaller 3.5" 480x320. Perhaps the sketch for
the 480x320 CTE32HR will work for these same-resolution
displays?

Does anybody have demo Sketches for these two displays?

Also, I would like to test the Touch input for these displays
(7, 5, 4, 3.5, and 3.2 inch), but I have not found any
Sketches to do that. Does CTE have any test Sketches?

Well, the DueGUI will run on 1.5.2 on the 7" display, and
that at least does some limited touch input.

Thanks, Gary

What Touch library is used for the CTE Due shield?
And, various CTE TFT displays?

Ok, I found the UTouch library at:
http://www.henningkarlsen.com/electronics/library.php?id=55

Although it is not programmed for several displays,
it includes a Calibration script, which I used to get
the CTE32HR (480X320) display working.

When I get more time, I will try to make my version of
the UTouch library initialize for other CTE displays as well,
when using the CTE display shield for the Due.

I will add the CTE50 and CTE70 for starters.

Has anybody else already done this?
Cheers, Gary

garygid:
When I get more time, I will try to make my version of
the UTouch library initialize for other CTE displays as well,
when using the CTE display shield for the Due.

I will add the CTE50 and CTE70 for starters.

I am not sure what you mean by this... UTouch already supports the 3.2" (320x240), 3.2" (480x320), 5" and 7" display modules from Coldtears Electronics.

The calibration data is specific to every single module, and not the display type. This is the reason you have to calibrate your display for proper use.

/Henning

Good additions, thanks, I will try a new version later.

I use the default pins for the touch connections to the shield,
since I did not know what connections that the CTE Due shield
used.

Although it worked, the calibrations were far off (by almost
a factor of two), and the y-axis was reversed,...
and there was no way to specify what display or shield
was supported,...
so it appeared as if the CTE Due shield with the CTE32HR
was not really "supported".

Being able to specify a display type, and shield type, with
default calibrations that are "close" for each type, as is
specified in the UTFT library, would seem to be helpful.

In any event, thanks for your great contributions.

garygid:
Although it worked, the calibrations were far off (by almost
a factor of two), and the y-axis was reversed,...

As the calibration data supplied with UTouch is for a 320x240 display is would only be logical that they were off by a factor of nearly two on a 480x320 display!!

garygid:
so it appeared as if the CTE Due shield with the CTE32HR was not really "supported".

What type of development board and shield you use does not have anything to do with the calibration data. The data are specific to the display module and would be the same on an Arduino Uno, an Arduino Mega, an Arduino Due or a chipKit board. A shield is just an adapter to facilitate easier connection of the display module and does not alter any signals other than possibly lowering the voltage where needed.
I have calibration data for ALL the displays listed as supported in the UTouch documentation and they have all been tested on all three platforms (AVR, ARM and PIC32).

I did supply calibration data for all supported modules in earlier releases but then people complained that the data caused the touch screen to be inaccurate so I removed the data.
Now that I have removed the data I find that people complain that they actually have to do something to get it working properly.

If you are not satisfied with what you are getting for free you can just create your own library.

I am getting really fed up with all the complaints and I am considering removing all my libraries. It is not fun when you try your best to do something that hopefully will help people and all (or at least most) you get in return are complaints. In addition to trying to find time to actually improve the libraries I spend most of my time answering emails from people who think they have a right to free support for a free product.

It seems there is no pleasing some people...

/Henning

The UTFT Class is unique... Normally If one wishes to learn how to use a class like UTFT, One reads the header file and then the examples... Hopefully to get a glimmer of the use of the code...
Mr Karlsen had the kindness to write a manual(s) delineating Supported Modules, Module Requirements and use of the Class (Library).

Doc

Sorry, I did not know what you had before in UTouch.

I appreciate very much your efforts, "Takk Skal Du Ha"
(or something close to that, as I recall from 1958
long ago in Kristiansand).

I was going to try help and improve what I found,
which seems to have no way to specify the display,
and only one set of calibration, and not even
an indication of what display it was for.

Sorry, maybe I did not get the latest version.

Also, I apparently missed the Manual for UTouch.
I will look for it.

Thanks, Gary

There is no need to specify which display you are using. All the library needs are the calibration data for the display in use.

As most people only use one display at the time there is really no need to add functionality for multiple sets of data as the would only serve to increase the memory footprint of the library mostly needlessly.

I am not really sure how you managed to miss the manual. It is available on the library webpage under the heading "Manual". It is also stated right below the link that the manual is included in the library download as well... BTW: All my libraries include manuals.

/Henning

Thank you for the new version of UTouch (22 Sep 2013).

Now, the supported CTE displays (CTE32HR, CTE50, and CTE70)
calibrate well, and your Paint example also works well.

Now, I am trying to find driver chip data for the CTE35 and CTE40
(both are the same resolution, 480x320, as the CTE32HR),
and add support for them to UTFT, which is needed before
I can try to calibrate their touch inputs.

I appreciate your attention to the calibration bugs.
Hilse, Gary

Progress!
I was able to add the CTE35 and CTE40 display types to the
UTFT library and modify UTFT_CTE to run the demo sketches.

I hope to try touch calibration on these two displays this weekend.

Can you please publish your Version with the CTE40 Display.
I'm trying since a few days without success.

Markus

I am quite willing to share my modifications, but understand these are
not originally my libraries or scripts, and they still should have a bit more cleaning.

The display of icons in the CTE demo normally goes from left to right, but
they show up right to left for the CTE35 and CTE40, so there is at LEAST
one bug left, perhaps in the UTFT_CTE library.

See the PM I sent to you.