Steigs Posted December 15, 2013 Share Posted December 15, 2013 I have a program that changes all my KPL backlights at various times of the day. (OFF) early morning (ON) evening (DIM) late night It's been running fine for the last couple years. Lately, I've noticed KPL lighting still on during the day and when I fire up the admin console I get the "Cannot communicate with" message for each KPL affected. The same KPLs also show with pending writes on them. If I select a KPL and click on "write changes", it goes through and the KPL moves to it's correct illumination state. The only changes I've made to the system were to replace a bad PLM and update to the latest (next) firmware. My best guess is some sort of traffic issue, though nothing in the physical setup (other than the PLM) has been changed and everything else works as expected. My question is what would be the best diagnostic tool to use to trace this problem? I'm not really familiar with how to use/interpret the log or trace functions in the ISY. Thanks in advance for any help. Link to comment
oberkc Posted December 15, 2013 Share Posted December 15, 2013 I would use scene tests to get a sense of how good is your communication. It will generally give you a sense of pass/fail. Pick a big scene. Run it several times. Make sure you disable any programs that can be triggered by devices in the scene. Do you find you system quick when you press buttons. Do the scenes react consistently, fast, and accurately? Link to comment
Steigs Posted December 15, 2013 Author Share Posted December 15, 2013 Scenes all work great. Everything is fine except for the sudden onset of this KPL program not running correctly. I'm wondering if perhaps this new PLM just doesn't like the burst of traffic. Link to comment
LeeG Posted December 15, 2013 Share Posted December 15, 2013 Suggest posting the Program with Copy to Clipboard. It sounds like a comm problem is developing which is slowing down the backlight processing or something is interfering with the Program trigger that is changing the backlight level. Look at Programs | Summary the next time this happens and see if the Program was actually triggered and what the Status column (True/False) indicates. To look at how well comm is working in general handling the backlight change run Tools | Diagnostics | Event Viewer at LEVEL 3. Right click the backlight Program and select Run Then (or Run Else). Look at the various Hops Left=x counts going to the various KPLs. Hops Left=2 is best, Hops Left=0 is poor. Link to comment
Steigs Posted December 15, 2013 Author Share Posted December 15, 2013 Status shows all programs were run at their expected time. When first opening Admin console, it thinks it has lost communication with those devices. "write changes" immediately updates device. Program: (On) - Called by another program If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Downstairs / Den / East Door 2-Gang / 2 - KPL6 / EAST DEN SCONCE' On 10 / Off 5 (Backlight Level) Set 'Downstairs / Kitchen / Hallway 4-Gang / 2 - KPL6 / KITCHEN TABLE' On 10 / Off 5 (Backlight Level) Set 'Downstairs / Kitchen / Hallway 4-Gang / 4 - KPL6 / KITCHEN COUNTERS' On 10 / Off 5 (Backlight Level) Set 'Upstairs / MBR / Door 4-Gang / 2 - KPL8 / BED OVERHEAD' On 10 / Off 5 (Backlight Level) Set 'Downstairs / Kitchen / East Slider / EAST KITCHEN SCONCE' On 10 / Off 5 (Backlight Level) Set 'Upstairs / MBR / Slider / Rear Flood East' On 10 / Off 5 (Backlight Level) Else - No Actions - (To add one, press 'Action') Diagnostic: Sun 12/15/2013 13:19:20 : [ Time] 13:19:23 10(0) Sun 12/15/2013 13:19:20 : [All ] Writing 6 bytes to devices Sun 12/15/2013 13:19:20 : [15 9C 2F 1 ] Memory : Write dbAddr=0x0264 [5A] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:19:20 : [iNST-TX-I2 ] 02 62 15 9C 2F 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 Sun 12/15/2013 13:19:20 : [iNST-ACK ] 02 62 15.9C.2F 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 06 (00) Sun 12/15/2013 13:19:21 : [iNST-SRX ] 02 50 15.9C.2F 25.28.11 27 2E 00 (00) Sun 12/15/2013 13:19:21 : [std-Direct Ack] 15.9C.2F-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 12/15/2013 13:19:21 : [15 9F 2E 1 ] Memory : Write dbAddr=0x0264 [5A] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:19:21 : [iNST-TX-I2 ] 02 62 15 9F 2E 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 Sun 12/15/2013 13:19:21 : [iNST-ACK ] 02 62 15.9F.2E 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 06 (00) Sun 12/15/2013 13:19:22 : [iNST-SRX ] 02 50 15.9F.2E 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:19:22 : [std-Direct Ack] 15.9F.2E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:19:22 : [15 9F 88 1 ] Memory : Write dbAddr=0x0264 [5A] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:19:22 : [iNST-TX-I2 ] 02 62 15 9F 88 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 Sun 12/15/2013 13:19:22 : [iNST-ACK ] 02 62 15.9F.88 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 06 (00) Sun 12/15/2013 13:19:23 : [iNST-SRX ] 02 50 15.9F.88 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:19:23 : [std-Direct Ack] 15.9F.88-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:19:23 : [15 9F E9 1 ] Memory : Write dbAddr=0x0264 [5A] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:19:23 : [iNST-TX-I2 ] 02 62 15 9F E9 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 Sun 12/15/2013 13:19:23 : [iNST-ACK ] 02 62 15.9F.E9 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 06 (00) Sun 12/15/2013 13:19:23 : [iNST-SRX ] 02 50 15.9F.E9 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:19:23 : [std-Direct Ack] 15.9F.E9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:19:23 : [15 C4 3C 1 ] Memory : Write dbAddr=0x0264 [5A] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:19:23 : [iNST-TX-I2 ] 02 62 15 C4 3C 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 Sun 12/15/2013 13:19:23 : [iNST-ACK ] 02 62 15.C4.3C 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 06 (00) Sun 12/15/2013 13:19:24 : [iNST-SRX ] 02 50 15.C4.3C 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:19:24 : [std-Direct Ack] 15.C4.3C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:19:24 : [16 7A 6A 1 ] Memory : Write dbAddr=0x0264 [5A] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:19:24 : [iNST-TX-I2 ] 02 62 16 7A 6A 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 Sun 12/15/2013 13:19:24 : [iNST-ACK ] 02 62 16.7A.6A 1F 2E 00 01 07 5A 00 00 00 00 00 00 00 00 00 00 70 06 (00) Sun 12/15/2013 13:19:25 : [iNST-SRX ] 02 50 16.7A.6A 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:19:25 : [std-Direct Ack] 16.7A.6A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:19:25 : [All ] Writing 0 bytes to devices Sun 12/15/2013 13:19:25 : [All ] Writing 0 bytes to devices Program: (Dim) If Time is 10:00:00PM Then Set 'Downstairs / Den / East Door 2-Gang / 2 - KPL6 / EAST DEN SCONCE' On 3 / Off 1 (Backlight Level) Set 'Downstairs / Kitchen / Hallway 4-Gang / 2 - KPL6 / KITCHEN TABLE' On 3 / Off 1 (Backlight Level) Set 'Downstairs / Kitchen / Hallway 4-Gang / 4 - KPL6 / KITCHEN COUNTERS' On 3 / Off 1 (Backlight Level) Set 'Upstairs / MBR / Door 4-Gang / 2 - KPL8 / BED OVERHEAD' On 3 / Off 1 (Backlight Level) Set 'Downstairs / Kitchen / East Slider / EAST KITCHEN SCONCE' On 3 / Off 1 (Backlight Level) Set 'Upstairs / MBR / Slider / Rear Flood East' On 3 / Off 1 (Backlight Level) Else - No Actions - (To add one, press 'Action') Diagnostic: Sun 12/15/2013 13:20:18 : [ Time] 13:20:20 10(0) Sun 12/15/2013 13:20:18 : [All ] Writing 6 bytes to devices Sun 12/15/2013 13:20:18 : [15 9C 2F 1 ] Memory : Write dbAddr=0x0264 [13] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:18 : [iNST-TX-I2 ] 02 62 15 9C 2F 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 Sun 12/15/2013 13:20:18 : [iNST-ACK ] 02 62 15.9C.2F 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 06 (00) Sun 12/15/2013 13:20:19 : [iNST-SRX ] 02 50 15.9C.2F 25.28.11 27 2E 00 (00) Sun 12/15/2013 13:20:19 : [std-Direct Ack] 15.9C.2F-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 12/15/2013 13:20:19 : [15 9F 2E 1 ] Memory : Write dbAddr=0x0264 [13] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:19 : [iNST-TX-I2 ] 02 62 15 9F 2E 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 Sun 12/15/2013 13:20:19 : [iNST-ACK ] 02 62 15.9F.2E 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 06 (00) Sun 12/15/2013 13:20:20 : [iNST-SRX ] 02 50 15.9F.2E 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:20 : [std-Direct Ack] 15.9F.2E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:20 : [15 9F 88 1 ] Memory : Write dbAddr=0x0264 [13] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:20 : [iNST-TX-I2 ] 02 62 15 9F 88 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 Sun 12/15/2013 13:20:20 : [iNST-ACK ] 02 62 15.9F.88 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 06 (00) Sun 12/15/2013 13:20:20 : [iNST-SRX ] 02 50 15.9F.88 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:20 : [std-Direct Ack] 15.9F.88-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:20 : [15 9F E9 1 ] Memory : Write dbAddr=0x0264 [13] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:20 : [iNST-TX-I2 ] 02 62 15 9F E9 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 Sun 12/15/2013 13:20:20 : [iNST-ACK ] 02 62 15.9F.E9 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 06 (00) Sun 12/15/2013 13:20:21 : [iNST-SRX ] 02 50 15.9F.E9 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:21 : [std-Direct Ack] 15.9F.E9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:21 : [15 C4 3C 1 ] Memory : Write dbAddr=0x0264 [13] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:21 : [iNST-TX-I2 ] 02 62 15 C4 3C 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 Sun 12/15/2013 13:20:21 : [iNST-ACK ] 02 62 15.C4.3C 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 06 (00) Sun 12/15/2013 13:20:21 : [iNST-SRX ] 02 50 15.9F.E9 25.28.11 23 2E 00 (00) Sun 12/15/2013 13:20:21 : [std-Direct Ack] 15.9F.E9-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 12/15/2013 13:20:22 : [iNST-SRX ] 02 50 15.C4.3C 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:22 : [std-Direct Ack] 15.C4.3C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:22 : [16 7A 6A 1 ] Memory : Write dbAddr=0x0264 [13] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:22 : [iNST-TX-I2 ] 02 62 16 7A 6A 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 Sun 12/15/2013 13:20:22 : [iNST-ACK ] 02 62 16.7A.6A 1F 2E 00 01 07 13 00 00 00 00 00 00 00 00 00 00 B7 06 (00) Sun 12/15/2013 13:20:22 : [iNST-SRX ] 02 50 16.7A.6A 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:22 : [std-Direct Ack] 16.7A.6A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:22 : [All ] Writing 0 bytes to devices Sun 12/15/2013 13:20:22 : [All ] Writing 0 bytes to devices Program: (Off) If Time is Sunrise Then Set 'Downstairs / Den / East Door 2-Gang / 2 - KPL6 / EAST DEN SCONCE' On 15 / Off 0 (Backlight Level) Set 'Downstairs / Kitchen / Hallway 4-Gang / 2 - KPL6 / KITCHEN TABLE' On 15 / Off 0 (Backlight Level) Set 'Downstairs / Kitchen / Hallway 4-Gang / 4 - KPL6 / KITCHEN COUNTERS' On 15 / Off 0 (Backlight Level) Set 'Upstairs / MBR / Door 4-Gang / 2 - KPL8 / BED OVERHEAD' On 15 / Off 0 (Backlight Level) Set 'Downstairs / Kitchen / East Slider / EAST KITCHEN SCONCE' On 15 / Off 0 (Backlight Level) Set 'Upstairs / MBR / Slider / Rear Flood East' On 15 / Off 0 (Backlight Level) Else - No Actions - (To add one, press 'Action') Diagnostic: Sun 12/15/2013 13:20:56 : [ Time] 13:20:59 10(0) Sun 12/15/2013 13:20:56 : [All ] Writing 6 bytes to devices Sun 12/15/2013 13:20:56 : [15 9C 2F 1 ] Memory : Write dbAddr=0x0264 [0F] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:56 : [iNST-TX-I2 ] 02 62 15 9C 2F 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB Sun 12/15/2013 13:20:56 : [iNST-ACK ] 02 62 15.9C.2F 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB 06 (00) Sun 12/15/2013 13:20:57 : [iNST-SRX ] 02 50 15.9C.2F 25.28.11 27 2E 00 (00) Sun 12/15/2013 13:20:57 : [std-Direct Ack] 15.9C.2F-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 12/15/2013 13:20:57 : [15 9F 2E 1 ] Memory : Write dbAddr=0x0264 [0F] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:57 : [iNST-TX-I2 ] 02 62 15 9F 2E 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB Sun 12/15/2013 13:20:57 : [iNST-ACK ] 02 62 15.9F.2E 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB 06 (00) Sun 12/15/2013 13:20:58 : [iNST-SRX ] 02 50 15.9F.2E 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:58 : [std-Direct Ack] 15.9F.2E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:58 : [15 9F 88 1 ] Memory : Write dbAddr=0x0264 [0F] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:58 : [iNST-TX-I2 ] 02 62 15 9F 88 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB Sun 12/15/2013 13:20:58 : [iNST-ACK ] 02 62 15.9F.88 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB 06 (00) Sun 12/15/2013 13:20:58 : [iNST-SRX ] 02 50 15.9F.88 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:58 : [std-Direct Ack] 15.9F.88-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:58 : [15 9F E9 1 ] Memory : Write dbAddr=0x0264 [0F] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:58 : [iNST-TX-I2 ] 02 62 15 9F E9 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB Sun 12/15/2013 13:20:58 : [iNST-ACK ] 02 62 15.9F.E9 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB 06 (00) Sun 12/15/2013 13:20:59 : [iNST-SRX ] 02 50 15.9F.E9 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:20:59 : [std-Direct Ack] 15.9F.E9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:20:59 : [15 C4 3C 1 ] Memory : Write dbAddr=0x0264 [0F] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:20:59 : [iNST-TX-I2 ] 02 62 15 C4 3C 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB Sun 12/15/2013 13:20:59 : [iNST-ACK ] 02 62 15.C4.3C 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB 06 (00) Sun 12/15/2013 13:21:00 : [iNST-SRX ] 02 50 15.C4.3C 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:21:00 : [std-Direct Ack] 15.C4.3C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:21:00 : [16 7A 6A 1 ] Memory : Write dbAddr=0x0264 [0F] cmd1=0x2E cmd2=0x00 Sun 12/15/2013 13:21:00 : [iNST-TX-I2 ] 02 62 16 7A 6A 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB Sun 12/15/2013 13:21:00 : [iNST-ACK ] 02 62 16.7A.6A 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB 06 (00) Sun 12/15/2013 13:21:01 : [iNST-SRX ] 02 50 16.7A.6A 25.28.11 2B 2E 00 (00) Sun 12/15/2013 13:21:01 : [std-Direct Ack] 16.7A.6A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/15/2013 13:21:01 : [All ] Writing 0 bytes to devices Sun 12/15/2013 13:21:01 : [All ] Writing 0 bytes to devices Link to comment
LeeG Posted December 15, 2013 Share Posted December 15, 2013 Thanks for the trace data. No obvious issues seen. It takes 1 extra hop to get to 15.9C.2F but that is consistent across the tests. Another user suggested putting a Wait 1 second between the calls to allow for any retry activity. I think that is a good idea. Also are other Insteon things being initiated at the same time these backlight changes are being run. Something else at Sunrise for example. Link to comment
Steigs Posted December 15, 2013 Author Share Posted December 15, 2013 No other simultaneous calls. I initially thought about putting in a wait, but I think (if it worked) that would just be a band-aid and not help me find the actual problem. This arrangement has been running fine for about 3 years now. The only variable is the new PLM and the firmware upgrade, though I really doubt the firmware would be the issue. I guess I'm just really trying to figure out how to verify if it is the new PLM or not. Seems anytime I have some stupid issue, it turns out to be that. Too bad UDI doesn't build their own... IMO, it really is the weak point in the system. Link to comment
LeeG Posted December 15, 2013 Share Posted December 15, 2013 Was the previous PLM a 2412? Link to comment
Steigs Posted December 15, 2013 Author Share Posted December 15, 2013 2413s, same as the new one. Link to comment
LeeG Posted December 15, 2013 Share Posted December 15, 2013 Are all the KPLs involved with the backlight change marked with a Red ! or Green Icon? If all the devices are marked there would something common. Could be general comm issue or PLM. If only selected KPLs are marked then comm would be more likely, maybe an Access Point not coupling as it should. Thanks for the PLM info. The 2413 PLMs have a faster processor than the older 2412. With both being a 2413 that would not be factor. Link to comment
Steigs Posted December 15, 2013 Author Share Posted December 15, 2013 Red !'s, yes. Basically it goes like this: 'Sunset' program fires, which results in all KPL lighting coming on. The following morning I notice they're all still on. Open Admin, Click "OK" through all the "cannot communicate with" messages for each KPL, all KPL's have red ! next to them. Right click on a single KPL, select 'write to device'. ISY turns 'busy', writes change, shows normal status. KPL light is now off. Repeat for all KPLs. What's a bit puzzling is that I can sit here and manually run the program over and over and it works fine, but I'll wake up tomorrow and darned if the KPLs aren't all still lit up. In the grand scheme of things it's not really any kind of big deal, but it is one of those thing that will eventually drive me into the looney bin. Link to comment
Michel Kohanim Posted December 15, 2013 Share Posted December 15, 2013 Hi Steigs, Do you have any programs that change scene settings for those devices for which you have ! every morning? With kind regards, Michel Link to comment
Steigs Posted December 15, 2013 Author Share Posted December 15, 2013 Hi Michel, No scene setting changes. Some outside lighting (none attached to a KPL) is turned off early morning, but that's it until the KPL program at sunrise. Link to comment
Michel Kohanim Posted December 15, 2013 Share Posted December 15, 2013 Hi Steigs, Then I am not at all certain why you would have pending writes as no configuration is being changed. Is there any reason you choose Write pending writes? Do you have green 1011 icons (I know you have !). With kind regards, Michel Link to comment
oberkc Posted December 15, 2013 Share Posted December 15, 2013 is not changing the LED backlights on a keypad considered a configuration change? Link to comment
Steigs Posted December 16, 2013 Author Share Posted December 16, 2013 Hi Steigs, Then I am not at all certain why you would have pending writes as no configuration is being changed. Is there any reason you choose Write pending writes? Do you have green 1011 icons (I know you have !). With kind regards, Michel Hi Michel, You know, at one time I did see 1011 icons, which prompted me to do the manual writes. I had forgotten about that. I think I had done a query or something on the non-communicative devices which brought them back into comm status, but then pending a write at that point. That's why I just automatically choose 'write pending' every time now when I see the !'s. I think I just assume the !'s meant it had tried to write but couldn't communicate. BTW, as of this posting, all KPL's have lit up for the evening. I'll try to watch them @ 10p for the dim phase. Link to comment
LeeG Posted December 16, 2013 Share Posted December 16, 2013 What would be helpful is to have Tools | Diagnostics | Event Viewer at LEVEL 3 running a few minutes before the backlight change at 10 PM. The event trace at that time will show what happens with the backlight changes if they fail. Link to comment
Steigs Posted December 16, 2013 Author Share Posted December 16, 2013 Copy that, I'll fire it up just short of. I didn't realise it logged autonomously. If I leave it up all night, it should catch any problem on the sunrise run, right? That could be just what I need to see anyhow. Link to comment
LeeG Posted December 16, 2013 Share Posted December 16, 2013 If it catches a failure that should provide good information. It is likely something before the Sunrise activity that is causing this with all the KPLs marked as comm failures. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.