need a CV library for my Graphic LCD

Go To Last Post
13 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

its a TS12864-a2 version 1.3 and it has three onboard driver chips behind it. 20 pins out.

i need a header file including both letter and graphic
functions. the CV seems to be supporting some Graphic LCDs but this one was not on the list.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have you asked Pavel? He seems to be adding support for new displays all the times.

Do you know the type of driver chip used in the display? It may be compatible with other supported displays.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

no i dont know him yet.

before putting the topic here i searched the web. some forums suggest that its driver chip is k0108 which exists on the code wizard but i noticed that those are either 128x64 two chips or larger displays with three chips.
this one is a 128x64 with three drivers and i am not sure if its chips are k0108 or not.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well you could give it a shot with some k0108 code, see what happens. Can you read out the number off the driver chips?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

i also have another question. a while ago i made a SMS writting system utilizing a SIM900 module. i used a colored graphic LCD with mounted touch screen and an ATmega64L. the micro reads a image of a nice graphic keyboard's BMP file from the SD card and puts it on the color LCD then checks the touch screen. it has all the letters, numbers, some functions and symboles. the software recieves the destination cell phone number and the text SMS and stores them on SRAM string char variables then send them through the USART into the SIM900 module. the projects was working firmly and i was quite impressed with myself but then it happened!

the first SMS is typed and dispatched with no problems at all but once the operation is finished and the operator is asked to push the function button to restart the operation a very strange issue occures. with in the software i cleared all the CHAR strings and then returned the program to the beginning line but its very weird to see that some of the texts created at the previous message randomly appear on the display and screw up the whole job! actually it only works fine at the first attempt and then i must use the restart pin on the micro to commit another cycle. the problem only happens on the LCD and the new message can be sent with no defections.

any ideas that how the hell does this happen?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

this LCD supports a 16 bit color code for each pixel including the RGB values but it has no driver chips on it and should be performed directly with the micro controller.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

the chips behind the TS12864 are the kind of block dots and nothing is written on those.

some times ago i tried this display and achieved no successes. some net forums suggest that its issue is with the pins configuration but to test those first i must be sure about the used library.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

could you please provide the link to Pavel's profile?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Pavel is they guy who writes codevision.

I'd be suggesting you identify your display and be 100% sure of exactly what it is. That will answer the question of what pinout and driver it has. Once you are sure of that, then the software side is clear. If you cant accurately identify the display, get one that you can, otherwise you can burn a lot of time fiddling.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I would guess that it is a regular "KS0108 128x64 CS1,CS2" and fully supported by CV.

You just need to identify the pins.
Google is your friend.

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

any ideas about the other matter?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Regarding the "other matter" - we can only guess. You have only provided superficial information. The process i usually follow when dealing with a defect:

1. Can the defect be demostrated?
2. Review the code to identify possible defects.
3. Debug to narrow in on the problem.
4. Fix defect.

Its all a matter of getting evidence and narrowing in on the problem - no magic involved.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Buy an lcd with a ks0108 controller. Write a cv program to draw lines on it, observe lines. Now connect your lcd. Run program. Lines? Its a ks0108. No lines? Its not a ks0108, or its wired wrong.

Imagecraft compiler user