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

CC2 won't initialize my 633 LCD at first

JakeNL

New member
Since a week, CC2 won't initialize my 633 LCD when Windows starts up. The cc2_service.log says the following:
Code:
ERROR    20080224-202239-0.462235s init_modules#1004: error initilising module (ID = 542810416)
ERROR    20080224-202449-130.559984s init_modules#1004: error initilising module (ID = 542810416)
ERROR    20080225-073525-0.458715s init_modules#1004: error initilising module (ID = 542810416)
ERROR    20080226-134030-0.391862s init_modules#1004: error initilising module (ID = 542810416)
ERROR    20080226-210130-0.365781s init_modules#1004: error initilising module (ID = 542810416)
ERROR    20080226-210504-213.856257s init_modules#1004: error initilising module (ID = 542810416)
When I configure the LCD module, I choose the one time for connection port "automatic", the next time I select the correct port. It doesn't matter, as long as I select a different one then the one that is displayed. After selecting the connection port, the display is picked up after a 'restart'

I also tried to reinstall the software, this didn't help.
Looking for additional LCD resources? Check out our LCD blog for the latest developments in LCD technology.
 

CF Mark

Administrator
Is it a USB or a Serial module?
Can you attach your "lcd_633.ini" file in here so i can take a quick look.
 

JakeNL

New member
Is it a USB or a Serial module?
Can you attach your "lcd_633.ini" file in here so i can take a quick look.
It is an USB-model. Unfortunately within Linux the upload tool doesn't want to work. Therefore I will just quote the first part of the .ini file:
Code:
[module00]
id=542810416
id_keypad=2126142511
key_repeat_rate=250
port="\\\\?\\ftdibus#vid_0403+pid_fc0b+cf000000a#0000#\12386e0d1e0-8089-11d0-9ce4-08003e301f73\125"
speed=115200
log_stats="stats-633-542810416.txt"
log_history="history-633-542810416.csv"
history_period=60
history_length=1500
fan_control=1
fan01_name="01 : CPU"
fan01_divider=2
My Windows crashed just after I had changed the port and restarted the driver. I don't know if this has influeced the strange port id

UPDATE:

possibly I found the solution myself. After correcting the port once again, I all of a sudden realized that the port speed was at 15200 instead of 19200. I changed that as well and after the next reboot, Crystal control worked 100%
 
Last edited:

JakeNL

New member
Unfortunately the problem comes back every day again.
As you can see in the .ini file the port is not correct. When I set it to automatic or to the specific com port, restart Crystal control, then everything is fine.
 

Attachments

CF Mark

Administrator
Try setting the com port name manually...
Go into the windows device manager and find out the com port number for the 633 (ie, COM3).

Then close all of CC2 (stop the service, and close the config app).
Edit the lcd_633.ini file, and change the port line to be port="com3" (or whatever number it was in the device manager).

Than re-run the CC2 config app, and start the CC2 service.

See if that fixes the problem.
 
Top