• We recently switched our forum platform. If you experience any issues please email support@crystalfontz.com

Keyboard Commands

jc634

Administrator
If you want to use your keyboard to perform commands, what follows is an example.

I use the F11 to turn on my LCD's, the F12 key to turn them off.

Create a file named cc2_keyboard.ini and copy the following into this file.

[options]

[input00]
id=2110068363
repeat=250
key0=0x0058
key1=0

[input01]
id=92724513
repeat=250
key0=0x0057
key1=0

Save it in your cc2_service directory.

Edit your cc2_service.ini file (red text) as follows:

[m02]
id=3088604686
module_name="Crystalfontz 635"
options=0
screen_sel=0
alt_enabled=1
brightness=70
contrast=40

[m02-event00]
if_type=1
if=2110068363
cond=0
to=1.000000
do_type=6
do=0.000000

[m02-event01]
if_type=1
if=92724513
cond=0
to=1.000000
do_type=6
do=70.000000


Please note the following:

1. I have my brightness set at 70. make the do=70.000000 the same as what you have your brightness set to.

2. There is a possibility that the id #'s in the cc2_keyboard.ini might already be in use. I would recommend you use rand_gen.exe program to generate new id #'s.

3. There is also a possibility that your specific keyboard outputs different scan codes than mine. If the code does not work, use the key_test.exe program to test your keyboard.

For 2 & 3, the possibility of a problem is probably remote. I just noted them, in case you run into a problem.

Using this code as an example, you can program other commands thru the keyboard, if you wish.

Questions?

Stay tuned for LED and keypad examples...

Jim

ps: I forgot to mention: "key_export.dll" needs to be copied to your windows\system32 directory for the keyboard hotkeys to operate correctly.
Looking for additional LCD resources? Check out our LCD blog for the latest developments in LCD technology.
 
Last edited:

reider

New member
Not awfully sure, but since I formatted before our last installation test the key_export.dll found its own way into Windows/system32. It might be part of the installation feature in CC2 now. Just another very good advantage if true.

Steve
 

CF Mark

Administrator
reider said:
Not awfully sure, but since I formatted before our last installation test the key_export.dll found its own way into Windows/system32. It might be part of the installation feature in CC2 now. Just another very good advantage if true.
It has been for quite a while :)
 

jdgordon

New member
well i finally setup the keyboard events :) makes everything a bit simpler

the cc2_keyboard.ini just has 3 keys setup so i wont show them.. the cc2_service.ini is where the fun is :D

[m01-event00]
if_type=1
if=2570936349
cond=0
to=1.000000
do_type=6
do=0.000000

[m01-event01]
if_type=1
if=2570936349
cond=0
to=1.000000
do_type=7
do=0.000000

[m01-event02]
if_type=1
if=2350032676
cond=0
to=1.000000
do_type=6
do=100.000000

[m01-event03]
if_type=1
if=2350032676
cond=0
to=1.000000
do_type=7
do=59.000000

[m01-event04]
if_type=1
if=2350032678
cond=0
to=1.000000
do_type=1
do=2.000000

all that is under my 634.. the first 2 turn the screen off completyl (0 brighntess, 0 contrast) both using the same key..
the next 2 turn it back on (100 brighntess, 59 contrast)
and the last jumps to the screen with the clock (its the only one on my desk :D )

now the big question is... can these be added in a screen file? or do they have to be manually added?
________
Asian tits
 
Last edited:

jc634

Administrator
jdgordon said:
all that is under my 634.. the first 2 turn the screen off completyl (0 brighntess, 0 contrast) both using the same key..
the next 2 turn it back on (100 brighntess, 59 contrast)
and the last jumps to the screen with the clock (its the only one on my desk :D )

now the big question is... can these be added in a screen file? or do they have to be manually added?
FWIW, you don't have to change the contrast. Setting brightness to 0 completely blanks the LCD, unless there is a reason I am unaware of as to why one would need to set contrast to 0.

As far as adding to a screen file, sure. The only thing I *think* would happen is that the keyboard commands would be screen specific, not module specific, just like keypad commands.

This might be bad, if your screens are set to scroll and you have the LCD's blanked. Of course, you could add a module keyboard command to go to that screen...;)

Jim
 
Top