CC unable to reliably interact with 631 module (631_WinTest works though)
[Edit: The problem is actually better described in the next two responses... after having a little more time to experiment with the issue. The issue seems to be more to do with a general communication reliability problem, rather than addressing a specific line. I am unsure if this is a problem specific to my module (fault), or the CC code/timing for the 631 modules in general...]
I'm finding that, using CC, the 2nd line of my 631 seems to be unreliably updated. Is this a known problem, and is there a fix I can apply.
The LCD display content seems to lag the CC "virtual" display content also. In other words, the CC application's virtual screen (in the settings window) cycles through the screens, but the LCD content does not mirror it's changes... the LCD lines are not changing in-sync with the virtual display.
I notice that often the contents of the 2nd line from a previous screen remain in the next screen (or screens), rather than being overwritten by the next tag content.
For instance, I have a screen that displays the CPU temp on line 1, Case temp on line 2. I also have a screen that displays the email new message count on Line 1, and latest email subject on Line 2. From time to time the temperature related screen shows the Line 1 CPU temp, and the latest email message subject on Line 2... Line 2 did not get updated to the Case temperature text.
Eg:
New Mail: 4
Sub: Hello
[ New screen active...]
CPU: 40
Sub: Hello <--- Should be "Case: 35", and is on the CC applcations virtual screen display.
Any suggestions?
Edit:
631_WinTest seems to immediately update the line content... as soon as the line's send button is pressed, the LCD line updates. I've noticed that if I exit CC, I have to reboot the system before I can run 631_Wintest and gain control of the module (after making sure CC isn't configured to load with windows). I'm running a recent version of MBM (5.3.5.1). Not sure why CC isn't always updating the content of Line 2 with the currently active screen. I'll try a few other things this evening once I get home. The 631 module is a virtual serial port/USB connected unit. When CC starts it reports that it's talking with the unit at the 115xxx rate.
Any chance these symptoms could be because of running the module on another USB header at an earlier time?... Is there any hardware manager cleanup that I need to do clean up from previous USB port connections, or COM port configuration assignments?
[Edit: The problem is actually better described in the next two responses... after having a little more time to experiment with the issue. The issue seems to be more to do with a general communication reliability problem, rather than addressing a specific line. I am unsure if this is a problem specific to my module (fault), or the CC code/timing for the 631 modules in general...]
I'm finding that, using CC, the 2nd line of my 631 seems to be unreliably updated. Is this a known problem, and is there a fix I can apply.
The LCD display content seems to lag the CC "virtual" display content also. In other words, the CC application's virtual screen (in the settings window) cycles through the screens, but the LCD content does not mirror it's changes... the LCD lines are not changing in-sync with the virtual display.
I notice that often the contents of the 2nd line from a previous screen remain in the next screen (or screens), rather than being overwritten by the next tag content.
For instance, I have a screen that displays the CPU temp on line 1, Case temp on line 2. I also have a screen that displays the email new message count on Line 1, and latest email subject on Line 2. From time to time the temperature related screen shows the Line 1 CPU temp, and the latest email message subject on Line 2... Line 2 did not get updated to the Case temperature text.
Eg:
New Mail: 4
Sub: Hello
[ New screen active...]
CPU: 40
Sub: Hello <--- Should be "Case: 35", and is on the CC applcations virtual screen display.
Any suggestions?
Edit:
631_WinTest seems to immediately update the line content... as soon as the line's send button is pressed, the LCD line updates. I've noticed that if I exit CC, I have to reboot the system before I can run 631_Wintest and gain control of the module (after making sure CC isn't configured to load with windows). I'm running a recent version of MBM (5.3.5.1). Not sure why CC isn't always updating the content of Line 2 with the currently active screen. I'll try a few other things this evening once I get home. The 631 module is a virtual serial port/USB connected unit. When CC starts it reports that it's talking with the unit at the 115xxx rate.
Any chance these symptoms could be because of running the module on another USB header at an earlier time?... Is there any hardware manager cleanup that I need to do clean up from previous USB port connections, or COM port configuration assignments?
Looking for additional LCD resources? Check out our LCD blog for the latest developments in LCD technology.
Last edited: