GLK12232-25-WBL Problem with connection-please please help!!

chewie · Post by **chewie** » Thu Oct 23, 2003 6:32 pm

Hi people,

I bought one of the GLK12232-25-WBL displays not so long back and have now put it in my computer. Thing is, it powers up, displays "Graphics in any direction" etc etc, but I can't display anything else.

I've tried running both the software on the drivers disk and LCDC, neither with any result other than the screen occationally going blank. LCDC says it's connected properly and when I try sending "L.C.D.C!!!!!" it says it's been sent in the log - but nothing on the screen.

The com port works find and my psion connects through it.

I've tried everything, I'm being dull or something, please help....

got XP Pro, p4 3Gig, 120Gig Hard disk etc etc. Abit IC7-G Board.

Cheers people,

chewie

Post by **Mat-Moo** » Fri Oct 24, 2003 7:49 am

Have you uploaded any fonts to the screen yet?

chewie · Post by **chewie** » Sun Oct 26, 2003 10:33 am

No, didn't know I had too! I'll see if I can now.

Thanks for your help - told you I was more than likely just dumb..

Back in a sec...

chewie · Post by **chewie** » Sun Oct 26, 2003 10:43 am

Tried that, absolutely nothing happens, can't get the default screen off the display (I've tried every clear screen button I can find and writing to it).

The only button that does anything is the "draw image (calculated)" button in "mogd". Which seems to change the contrast so that "Graphics in Any Direction" fades out alittle. Then it goes back to how it started around 2 seconds after

Johnny1 · Post by **Johnny1** » Mon Oct 27, 2003 10:34 am

You might want to try installing LCD Tester and playing around with your display's settings, just to make sure that your display is working properly.

http://www.lcdforums.com/forums/viewtopic.php?t=1535

Otherwise, just make sure that you are connected to the right port with LCDC.

Open LCDC
Go to Configure/Test
Click on Auto-Detect
Select the display LCDC found connected to your computer
****
And then just to be 100% sure, click on Test Display and try sending text to it.
Make sure the contrast is set appropriately so that you can see the text sent.

Hope this helps.

chewie · Post by **chewie** » Mon Oct 27, 2003 6:36 pm

Thanks for the help, it's kinda got me a touch further.

The software said it was unable to autodetect the display (see screenshot below).

I've ordered the serial lead straight from you guys, as it was neater than cutting a hole in my case, so that shouldn't be the problem.

Also, I've not over powered it or anything, as it's definately working (see another picture).

Might it be a firmware or something problem?

Below I've included the log when the testing software started up, not sure if it gives any useful information, but it may say something I don't understand...

Thanks again for your help!

chewie

Oct 28, 2003 - 01:11:01

Read Module Type...
254 55
Module Type: -1
Initializing LCD...
Text Commands Support...
Auto Scroll.........[YES]
Auto Scroll On...
254 81
Line Wrap...........[ NO]
Underline...........[ NO]
Blinking Cursor.....[ NO]
Set Font............[YES]
Set Font (1)...
254 49 1
Font Metrics........[YES]
Font Metrics: (1, 1, 1, 32)...
254 50 1 1 1 1 32
Pixel Positioning...[YES]
Font Positioning....[YES]
Cursor Position (1, 1) ...
254 71 1 1
Cursor Back.........[ NO]
Cursor Home.........[YES]
Cursor Forward......[ NO]
Send Text...........[YES]
Clear Text..........[YES]
...Done Text Commands.
Graphics Support...
Drawing Color.......[YES]
Drawing Color Black...
254 99 1
Draw Pixel..........[YES]
Draw Line...........[YES]
Continuous Line.....[YES]
Outline Rectangle...[YES]
Solid Rectangle.....[YES]
Draw Bitmap.........[YES]
...Done Graphics Support.
Keypad/GPO Support...
Debounce Time.......[YES]
Debouce Time (sec)...
254 85 8
Auto Transmit.......[YES]
Auto Transmit On...
254 65
Auto Repeat.........[YES]
Auto Repeat On...
254 126 0
KU/KD Mode..........[YES]
25-Key Keypad.......[YES]
Poll Buffer.........[YES]
Clear Key Buffer....[YES]
Clear Key Buffer...
254 69
1 GPO ..............[YES]
Turn Off GPO...
254 87
...Done Keypad/GPOs.
Bar Graphs Support...
Graph Init..........[ NO]
Write Graph.........[ NO]
...Done Bar Graphs.
File System Support...
Upload Font.........[YES]
Upload Bitmap.......[YES]
Purge Memory........[YES]
...Done File System.
Checking Remember Support...
Remember Wrap.......[ NO]
Remember Scroll.....[YES]
Remember Underline..[ NO]
Remember Blinking...[ NO]
Remember Transmit...[YES]
Remember Repeat.....[YES]
Remember Debounce...[YES]
Remember Backlight..[ NO]
...Done Remember Support.
Checking Miscellaneous...
Baud Rate...........[YES]
Set RS232 Port Speed...
254 57 15
Read Serial #.......[ NO]
Read Version #......[YES]
Read Version Number...
254 54
Version Number: -1
Read Module #.......[YES]
Set I2C Address.....[YES]
Set I2C Address...
254 51 80
Set Contrast........[YES]
Set Brightness......[ NO]
Save Contrast.......[YES]
Save Brightness.....[ NO]
Clear Display.......[YES]
Startup Screen......[ NO]
Flow Control........[YES]
Exit Flow Control Mode...
254 59
Backlight...........[YES]
Set Backlight On Indefenitely...
254 66 0
...Done Miscellaneous.
...LCD Initialized.

Johnny1 · Post by **Johnny1** » Tue Oct 28, 2003 10:02 am

I just tested both LCDC and LCD Tester with a GLK12232-25-WBL and I actually sort of got the same results. It seems that when either one of the programs probe the display for its Module Type, that is when the programs send the command Read Module Type command 254 55, the GLK-WBL returns 0xFF. This causes the programs to think that there isn't a display connected to this port or that the display isn't a WBL because WBL's Module Type is 0x22.
Anyway, to be honest with you this seems to be a hardware problem and that is out of my league. However in the mean time you can still ignore both LCDC and LCD Tester's warnings about not finding a display connected to the port, or the display returning an invalid 0xFF module type, and still connect to them and send commands to them.

So in LCDC go to Configure/Test -> Select the port where your WBL is connected and the GLK12232 definition file -> Click the green check mark and finally click on Test display and try turning the backlight on and off to make sure that you are communicating with the display.

With LCD Tester, select the port AND LCD(WBL-Usually this is optional since the program auto-detects the display connected but obviously this won't work in this case) -> click connect. Click 'Yes' to 'Auto-Detect Failed...continue connecting?' or if you get 'LCD Type Mismatch...switch to LCD type 0xFF? click on 'NO'. Once connected you should be able to test out different commands.

Let me know how you make out.

chewie · Post by **chewie** » Thu Oct 30, 2003 7:58 am

No real difference, I get "Read version number failed" error right at the beginning, but I guess that's what you mean about the module.

I figure I must be communicating with it in some way as the screen fades out when I try and display a picture, but nothing happens when I change the contrast.

chewie · Post by **chewie** » Thu Oct 30, 2003 8:05 am

If it helps, when I try and upload fonts to the display in mogd, after a long wait it says the module didn't respond.

Johnny1 · Post by **Johnny1** » Thu Oct 30, 2003 10:37 am

Yeah, I think it is safe to say that there is definitely something wrong with your display.

Your best bet now is to contact support at

support@matrixorbital.ca

and they will file an RMA for you.

Sorry I couldn't be of any help.

chewie · Post by **chewie** » Sat Nov 01, 2003 9:05 am

Thanks!

At least I now know I'm not just being really slow or anything!

Cheers

chewie · Post by **chewie** » Fri Nov 07, 2003 1:48 pm

I got in contact with support and someone e-mailed me to say that I have to swap the communication cables around in the lead. This has sorted all problems!!! I guess I should have checked the cable for send recieve going into the display before I put it in.

THANKS FOR YOUR HELP!!!!!

Post by **Henry** » Wed Nov 12, 2003 12:04 pm

chewie wrote:I got in contact with support and someone e-mailed me to say that I have to swap the communication cables around in the lead. This has sorted all problems!!! I guess I should have checked the cable for send recieve going into the display before I put it in.

THANKS FOR YOUR HELP!!!!!

I though of the solution out of the blue... hehe...