LCDInfo.com
http://forum.lcdinfo.com/

Edit: Strange behaviour of lcd
http://forum.lcdinfo.com/viewtopic.php?f=6&t=901		 Page 1 of 4
Author:  Myscha [ Thu Nov 04, 2004 15:00 ]
Post subject:  Edit: Strange behaviour of lcd
Hello,

i got a LCD from a friend today. It seems to be very nice, but i can't find any datasheets for it. It's a HLM8491 from Hosiden. There are eight LC79400 and two LC79431 controllers on the back.

Can anybody help me find a datasheet or tell me how to wire it, please? And will it work with LCDInfo?

Greetz!
Myscha
Author:  Myscha [ Wed Dec 08, 2004 10:46 ]
Post subject: 
2 times 4 of the LC79400 are parallel and their datapins go to the connector. That means i have 8 datapins on the connector. 2 times a 4 bit-bus.

And one of the LC79431 makes the lines from 1 to 80 and from 161 to 240 and the other one the lines from 81 to 160 and from 241 to 320.

The display seems to be divided to an upper and a lower display.

The LC79400 and LC79431 is connected like on page 7 of the LC79400 datasheet.

http://www.alldatasheet.com/datasheet-p ... 9400D.html
http://www.alldatasheet.com/datasheet-p ... 9431D.html

What kind of controller could work with this display?
Author:  Myscha [ Thu Dec 30, 2004 23:27 ]
Post subject:  Strange behaviour of LCD
I have now connected the lower half of the display and tried to run it with LCDinfo. I tested it with a screenconfig from my T6963C display with a resolution of 160x128 pixels.
I guessed that this screen was showed correctly with 160x128 and the rest of the half display would stay empty. But i was wrong. The lines 1 to 64 were correctly but then it started again at the top and showed again the lines 1 to 64 and the 3rd time it showed the lines 1 to 32.
The lcd has a resolution of 320x320 and at the moment i only control the lower half of it, that means 160 lines (64+64+32).

Has anyone an idea why this could be and what's the problem?

I took the controller-board of the following display and connected it to my lcd, because there are all wirings for the S1D13305 already done.
http://www.mscbp.hu/download/LCD/Ampire ... e%20driver).pdf
http://www.mscbp.hu/download/LCD/Ampire/AT-320240Q1.pdf
But i think this shouldn't matter...

I made pictures of it, but have no webspace to upload them. If you don't know what i mean, email me then i will send it to you.


Edit:
I upped the pictures in another forum now. They're not very good (but big ;)) - but better than nothing. You can find them here:
http://lcdhype.mod-extreme.info/lcdhype ... etlastpost
http://lcdhype.mod-extreme.info/lcdhype ... topic=1492
Author:  Henri [ Tue Jan 11, 2005 14:41 ]
Post subject: 
Have you tried different screen size settings from the driver config dialog like I suggested ? I would be interested hearing what kind effects that has.
Author:  Myscha [ Tue Jan 11, 2005 23:41 ]
Post subject: 
It only shows something if the width is set to 320 (319 works also ;)) If i set it to 240, 160 or anythig else nothing is happening...

Now i wired the whole display but the result is the same. It's now wired like the schematic on page 22 of the S1D13305 (Figure 3, but with 2 line-drivers instead of one). Theoreticaly i have a resolution of 640x160 dots now. Pictures you can see if you follow the links in the post below...

I took the controller-device of another display (Ampire 320240Q2 with a resolution of 320x240) ( http://www.mscbp.hu/download/LCD/Ampire/ or http://www.mscbp.hu/download/LCD/Ampire ... e%20driver).pdf ), because this was completely with oscillator and RAM,... I think it shouldn't matter what display is connected to the controller-device, but maybe it does...

I have no more ideas what could be the problem...

Is there any command in the driver that tells the controller to do something special after 64 lines?

Edit: Where can i find the initialization in the source code? There is a W/S flag that is set to 0 if single panel display and to 1 if dual panel display. My lcd is a dual panel... You can see this in the S1D13305 datasheet on page 21 and 22 (and 23). Perhaps this could solve my problem...
Author:  Myscha [ Tue Jan 18, 2005 22:32 ]
Post subject: 
@ Henri:

Could you please make me a S1D13305 driver where the W/S flag is set to 1 instead of 0?
Author:  Henri [ Thu Jan 20, 2005 2:04 ]
Post subject: 
Myscha wrote:
@ Henri:

Could you please make me a S1D13305 driver where the W/S flag is set to 1 instead of 0?

I'll have a look into the W/S flag.
Author:  Myscha [ Mon Jan 24, 2005 8:59 ]
Post subject: 
Henri, please don't forget me! ;)
Author:  Henri [ Wed Jan 26, 2005 21:11 ]
Post subject: 
I didn't forget you this time. This morning I added an option for the W/S flag to the driver config but before I had time to post it here I already had to run. Also it's not yet tested by me.
http://www.skippari.net/lcd/alpha/plugi ... driver.dll
Author:  Myscha [ Thu Jan 27, 2005 11:40 ]
Post subject: 
What is the maximum resolution that LCDInfo can handle? LCDHype for example runs only up to 320x240 and crashes above...
Author:  Myscha [ Thu Jan 27, 2005 12:05 ]
Post subject: 
I tried the driver on 2 computers now (Win2k and Win98) and on both LCDInfo crashed when i copy the DLL into the directory. When i change the ending to DL_ or DL it works, but not when it is a DLL...
Author:  coorz [ Thu Jan 27, 2005 12:12 ]
Post subject: 
Myscha wrote:
What is the maximum resolution that LCDInfo can handle? LCDHype for example runs only up to 320x240 and crashes above...


I've successfully used the LCDinfo SED driver to drive a 640x200 LCD. Albeit a horrible sight, it should work.
Author:  Henri [ Thu Jan 27, 2005 14:59 ]
Post subject: 
There shouldn't really be a limitation in the resolution LCDInfo can handle as it just dynamically adjusts to the values given from the driver. Ok, the size is saved in 32-bit integer variable so of course if you overflow that...
But if I remember correctly I put in checks for values above 1000 x 1000 as that big values don't really sound realistic.

Sorry I made a mistake that caused you the crashing. I hope the file works now.
I had already done some work in LCDInfo with functionality that wouldn't allow plugins made with wrong SDK version crash LCDInfo and during that I increased the interface version number. And as the current released LCDInfo doesn't yet properly handle this it gets confused with the wrong interface version number and crashes even if the plugin otherwise would be compatible. But it should now be compiled with the older interface version number.

Also you should either overwrite the old sed133x driver from the LCDInfo directory or delete the old one when using this.
Author:  Myscha [ Thu Jan 27, 2005 16:37 ]
Post subject: 
Now LCDInfo doesn't crash, but when i select the driver and click on "Configure" i get the error-message "Failed loading configuration dialog!"
Author:  Henri [ Fri Jan 28, 2005 16:52 ]
Post subject: 
Ok, I know why this happens if you didn't rename the file as sed133x_driver.dll

I have to revise the previous instructions that you need to rename the file to sed133x_driver.dll as the original for it to work.
Page 1 of 4 All times are UTC + 2 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/