First of all, congrats on a wonderful program. Even though it seems it needs a bit of ironing out some glitches.
Ok, here's my problem: After some time (in this case about 2.5 hours, but it varies) of running cc2 the display turns itself off. The log for my LCD screen (lcd_631.log) shows this message:
(actually it gets repeated a lot, about two or three times per second of logs)
After getting this message, even when I stop the service, from the "tray" icon or even more forcefully by stopping cc2service and restarting, the display does not come on again, and the only way to resume it is unplugging the USB cable and replugging it. Also, when this has occurred, the 631_WinTest.exe seems to think that COM5 (the virtual COM port for CFA631-USB) is "in use".
I'm running WinXP pro SP2, on an Athlon XP 2000+ with 1.5 GB RAM. I'm also running BOINC which keeps my CPU quite busy, and I don't have a modem, so the only "COM" activity should be the 631 module.
Ok, here's my problem: After some time (in this case about 2.5 hours, but it varies) of running cc2 the display turns itself off. The log for my LCD screen (lcd_631.log) shows this message:
Code:
Sun 26 18:49:45 WARNING display_update: Sending packet failed.
After getting this message, even when I stop the service, from the "tray" icon or even more forcefully by stopping cc2service and restarting, the display does not come on again, and the only way to resume it is unplugging the USB cable and replugging it. Also, when this has occurred, the 631_WinTest.exe seems to think that COM5 (the virtual COM port for CFA631-USB) is "in use".
I'm running WinXP pro SP2, on an Athlon XP 2000+ with 1.5 GB RAM. I'm also running BOINC which keeps my CPU quite busy, and I don't have a modem, so the only "COM" activity should be the 631 module.
Looking for additional LCD resources? Check out our LCD blog for the latest developments in LCD technology.