biredale Posted June 15, 2012 Posted June 15, 2012 I am trying to figure out why my ISY seems to be inconsistent controlling devices. It 'seems' random and not related to specific times/days or other home activities. I am attaching the Level 3 Event Viewer, ISY and Error logs in the hope that someone can take a look. All I can figure is for some unknown reason, the command seems to get sent out but is not receiving an ack from the device. The logs represent a two minute period with a series of on and off's in sequence. Approximately half of the operations failed to activate or deactivate the light. I have a phase coupler, and about 25 devices in my system. ISY Log INSTEON Device Control Value Time User Log Type Ceiling Fan Light On Thu 2012/06/14 20:23:21 Web Log Ceiling Fan Light Status 100% Thu 2012/06/14 20:23:21 System Log Ceiling Fan Light Off Thu 2012/06/14 20:23:24 Web Log Ceiling Fan Light Status 0% Thu 2012/06/14 20:23:24 System Log Ceiling Fan Light On Thu 2012/06/14 20:23:27 Web Log Ceiling Fan Light Status 100% Thu 2012/06/14 20:23:27 System Log Ceiling Fan Light Off Thu 2012/06/14 20:23:30 Web Log Ceiling Fan Light On Thu 2012/06/14 20:23:33 Web Log Ceiling Fan Light Off Thu 2012/06/14 20:23:36 Web Log Ceiling Fan Light On Thu 2012/06/14 20:23:38 Web Log Ceiling Fan Light Off Thu 2012/06/14 20:23:41 Web Log Ceiling Fan Light On Thu 2012/06/14 20:23:43 Web Log Ceiling Fan Light OFF Thu 2012/06/14 20:23:46 Web Log Ceiling Fan Light On Thu 2012/06/14 20:23:49 Web Log Ceiling Fan Light Off Thu 2012/06/14 20:23:52 Web Log Ceiling Fan Light Status 0% Thu 2012/06/14 20:23:52 System Log Ceiling Fan Light On Thu 2012/06/14 20:23:55 Web Log Ceiling Fan Light Status 100% Thu 2012/06/14 20:23:56 System Log Ceiling Fan Light Off Thu 2012/06/14 20:23:57 Web Log Ceiling Fan Light Status 0% Thu 2012/06/14 20:23:58 System Log Ceiling Fan Light On Thu 2012/06/14 20:23:59 Web Log Ceiling Fan Light Status 100% Thu 2012/06/14 20:23:59 System Log Ceiling Fan Light Off Thu 2012/06/14 20:24:01 Web Log Ceiling Fan Light On Thu 2012/06/14 20:24:04 Web Log Ceiling Fan Light Off Thu 2012/06/14 20:24:06 Web Log Ceiling Fan Light On Thu 2012/06/14 20:24:08 Web Log Ceiling Fan Light Off Thu 2012/06/14 20:24:10 Web Log Error Log Time User Code Message Thu 2012/06/14 20:23:21 System -170001 [HTTP] 192.168.1.107:50711->80 Thu 2012/06/14 20:23:21 System -170001 [HTTP] 192.168.1.107:50714->80 Thu 2012/06/14 20:23:24 System -170001 [HTTP] 192.168.1.107:50717->80 Thu 2012/06/14 20:23:24 System -170001 [HTTP] 192.168.1.107:50720->80 Thu 2012/06/14 20:23:27 System -170001 [HTTP] 192.168.1.107:50721->80 Thu 2012/06/14 20:23:27 System -170001 [HTTP] 192.168.1.107:50724->80 Thu 2012/06/14 20:23:27 System -170001 [HTTP] 192.168.1.100:58120->80 Thu 2012/06/14 20:23:28 System -170001 0: GET-->/ Thu 2012/06/14 20:23:30 System -170001 [HTTP] 192.168.1.107:50725->80 Thu 2012/06/14 20:23:30 System -170001 [HTTP] 192.168.1.107:50728->80 Thu 2012/06/14 20:23:33 System -170001 [HTTP] 192.168.1.107:50729->80 Thu 2012/06/14 20:23:33 System -170001 [HTTP] 192.168.1.107:50732->80 Thu 2012/06/14 20:23:36 System -170001 [HTTP] 192.168.1.107:50733->80 Thu 2012/06/14 20:23:36 System -170001 [HTTP] 192.168.1.107:50736->80 Thu 2012/06/14 20:23:38 System -170001 [HTTP] 192.168.1.107:50737->80 Thu 2012/06/14 20:23:39 System -170001 [HTTP] 192.168.1.107:50740->80 Thu 2012/06/14 20:23:41 System -170001 [HTTP] 192.168.1.107:50741->80 Thu 2012/06/14 20:23:41 System -170001 [HTTP] 192.168.1.107:50744->80 Thu 2012/06/14 20:23:43 System -170001 [HTTP] 192.168.1.107:50746->80 Thu 2012/06/14 20:23:43 System -170001 [HTTP] 192.168.1.107:50749->80 Thu 2012/06/14 20:23:46 System -170001 [HTTP] 192.168.1.107:50750->80 Thu 2012/06/14 20:23:46 System -170001 [HTTP] 192.168.1.107:50753->80 Thu 2012/06/14 20:23:49 System -170001 [HTTP] 192.168.1.107:50754->80 Thu 2012/06/14 20:23:49 System -170001 [HTTP] 192.168.1.107:50757->80 Thu 2012/06/14 20:23:52 System -170001 [HTTP] 192.168.1.107:50758->80 Thu 2012/06/14 20:23:52 System -170001 [HTTP] 192.168.1.107:50761->80 Thu 2012/06/14 20:23:55 System -170001 [HTTP] 192.168.1.107:50762->80 Thu 2012/06/14 20:23:56 System -170001 [HTTP] 192.168.1.107:50765->80 Thu 2012/06/14 20:23:57 System -170001 [HTTP] 192.168.1.107:50766->80 Thu 2012/06/14 20:23:57 System -170001 [HTTP] 192.168.1.107:50769->80 Thu 2012/06/14 20:23:59 System -170001 [HTTP] 192.168.1.107:50770->80 Thu 2012/06/14 20:23:59 System -170001 [HTTP] 192.168.1.107:50773->80 Thu 2012/06/14 20:24:01 System -170001 [HTTP] 192.168.1.107:50774->80 Thu 2012/06/14 20:24:01 System -170001 [HTTP] 192.168.1.107:50777->80 Thu 2012/06/14 20:24:04 System -170001 [HTTP] 192.168.1.107:50778->80 Thu 2012/06/14 20:24:04 System -170001 [HTTP] 192.168.1.107:50781->80 Thu 2012/06/14 20:24:06 System -170001 [HTTP] 192.168.1.107:50782->80 Thu 2012/06/14 20:24:06 System -170001 [HTTP] 192.168.1.107:50785->80 Thu 2012/06/14 20:24:08 System -170001 [HTTP] 192.168.1.107:50786->80 Thu 2012/06/14 20:24:08 System -170001 [HTTP] 192.168.1.107:50789->80 Thu 2012/06/14 20:24:10 System -170001 [HTTP] 192.168.1.107:50790->80 Thu 2012/06/14 20:24:10 System -170001 [HTTP] 192.168.1.107:50793->80 Thu 2012/06/14 20:24:20 System -170001 [HTTP] 192.168.1.100:58139->80 Thanks!
Michel Kohanim Posted June 15, 2012 Posted June 15, 2012 Hello biredale, Can you tell me the scenario you are running? i.e. are you repeatedly sending a command ... At the moment it seems that the PLM is not responding: TX - Command sent from ISY ACK - Response from PLM for TX SRX - Response from the end device With kind regards, Michel
biredale Posted June 15, 2012 Author Posted June 15, 2012 I was doing a series of on and offs in sequence, approximately 10 commands total. send on wait about 3 seconds send off wait about 3 seconds repeat.. Thx Brian
LeeG Posted June 15, 2012 Posted June 15, 2012 The Event Viewer entries from 20:23:29 to 20:23:46 indicate the PLM was sent serial commands which the PLM failed to send back an Echo response (06 on end of message) which normally means the PLM did not process the request. The trace entry at 20:23:48 begins the next correct sequence. Serial PLM issued (-TX-I1), command echoed back (-ACK), and device responds (-SRX). Check the cable between Port A and the PLM. It might not be fulled snapped into either the ISY connector or the PLM connector. If another cable is available try another cable. How long is the cable run between the ISY and PLM?
biredale Posted June 15, 2012 Author Posted June 15, 2012 They are physically adjacent to each other, I do not recall the length of the cable but believe it was the one provided with the unit (maybe three feet?) Brian
LeeG Posted June 15, 2012 Posted June 15, 2012 Thanks. That is fine. Some folks have tried to use long cables since it looks like an Ethernet connection. Serial port has a 50' max length. The PLM either accepts the serial command and echoes back the message with an 06 on the end or rejects the command if too busy and echoes back the message with a 15 on the end. In this case the PLM did neither which could indicate it did not receive the command because of a bad cable or lose connection or the PLM is defective. Run Tools | Diagnostics | PLM Info. What does it show for the PLM firmware level?
LeeG Posted June 15, 2012 Posted June 15, 2012 There have been some problems with the v98 level firmware although I do not know if this specific symptom is part of those. There is a v.99 level available.
biredale Posted June 19, 2012 Author Posted June 19, 2012 I am still seeing inconsistent results with my operations. Any suggestions on further trouble shooting? I do have a bunch of CFLs but they have been in for some time now. Also, if they were a problem wouldn't I see a result from the PLM all the time? Thx Brian
LeeG Posted June 19, 2012 Posted June 19, 2012 Does the Event Viewer contilnue to show the PLM not responding to commands?
Michel Kohanim Posted June 19, 2012 Posted June 19, 2012 Brian, Also, when this happens, would you please unplug the PLM and then plug it back in (not the ISY)? With kind regards, Michel
Recommended Posts
Archived
This topic is now archived and is closed to further replies.