dba62 Posted October 9, 2014 Share Posted October 9, 2014 I am using the program from another forum thread to monitor my water sensors. After running flawlessly, I have ended up with a situation where both of my water sensors are missing their heartbeats (I get notification at 9am and 6pm). As I understand it, the device sends one ping per day. Both devices (which are about 4 months old) stop heartbeating at roughly the same time. I tried rebooting the ISY-994i and that did not correct the problem. What's the proper way to resolve this issue. Thanks in advance. Link to comment
stusviews Posted October 9, 2014 Share Posted October 9, 2014 One of my leak detectors stopped sending a heartbeat no matter what I tried (e.g., factory reset, new battery, deleting & adding, etc.). Notification of wet and dry, when tested, function.I consider the device defective and will get a replacement. Unless someone has a better solution Link to comment
LeeG Posted October 9, 2014 Share Posted October 9, 2014 dba62 Run Tools | Diagnostics | Event Viewer at LEVEL 3. Tap the Set button on a Leak Sensor. Either a Wet=On or Dry=On message should be traced followed approx 15 seconds later by a Heartbeat message. Post the event trace after waiting at least 30 seconds for Heartbeat. Link to comment
dba62 Posted October 10, 2014 Author Share Posted October 10, 2014 Not a thing. The green led flashes once when I tap the set button, but nothing is displayed on the event viewer. Just to make sure I wasn't screwing the pooch, I pressed the up/down buttons on my thermostat and I got some data. Link to comment
LeeG Posted October 10, 2014 Share Posted October 10, 2014 I would move the Leak Sensor near the PLM (if a 2413) and repeat the Set button tap test. At this point the Leak Sensor is either not sending any Wet/Dry message or is not in range of a Dual Band device. Link to comment
dba62 Posted October 10, 2014 Author Share Posted October 10, 2014 I tried the test with the leak sensor in the same room as the PLM. Should I try deleting and adding the sensor? I was reticent to do this as I was thinking it would cause a problem with the program. Link to comment
LeeG Posted October 10, 2014 Share Posted October 10, 2014 Factory Reset the Leak Sensor, right click on -Dry node and select Restore Device to rebuild device. If that does not work then Delete the device and add it back to the ISY. Without any traffic from the Leak Sensor unless the Factory Reset restores function, the device may not respond to the Restore Device. Link to comment
dba62 Posted October 10, 2014 Author Share Posted October 10, 2014 Thanks - I will give that a try this weekend. Link to comment
dba62 Posted October 16, 2014 Author Share Posted October 16, 2014 Well - I finally tried this and I got a "Cannot Communicate" with the water sensor error. How does communication with the ISY actually work? I assume the water sensor communicates directly with the ISY and not through the PowerLinc Modem. Is that correct? If not, perhaps I should reset the modem. Link to comment
stusviews Posted October 16, 2014 Share Posted October 16, 2014 The leak sensor communicates with all dual-band device within range. Any dual-band device that hears the signal copies it to the powerline. Link to comment
dba62 Posted November 29, 2014 Author Share Posted November 29, 2014 Well - I'm not having any luck with the water sensors. I purchased a 3rd sensor and added it into the mix and I replaced one of the existing sensors with the newly purchased sensor. Then I did the factory reset on the deleted sensor and used it to replace the other "dead" sensor. This worked for about a month and once again the old sensor died. I decide to give this one last try and purchased yet another sensor (I now have 4, yet need only 2). This time I couldn't get the new sensor added. Then when I tried restore device on the new sensor I lost contact with the other sensor. So now I have no working sensors (3 of which are in the same room as the PLM). Meanwhile, the entire procedure when adding a water sensor to my ISY is flaky. More than once, the device I am attempting to add doesn't show up until AFTER I reboot the ISY. This happened to me even when I did the successful installation of the original 2 devices. I guess I am going to abandon the entire water sensor endeavor. All of the devices which are hardwired (dimmers, switches, garage door status/control, themostat) are working great. Link to comment
Teken Posted November 29, 2014 Share Posted November 29, 2014 Well - I'm not having any luck with the water sensors. I purchased a 3rd sensor and added it into the mix and I replaced one of the existing sensors with the newly purchased sensor. Then I did the factory reset on the deleted sensor and used it to replace the other "dead" sensor. This worked for about a month and once again the old sensor died. I decide to give this one last try and purchased yet another sensor (I now have 4, yet need only 2). This time I couldn't get the new sensor added. Then when I tried restore device on the new sensor I lost contact with the other sensor. So now I have no working sensors (3 of which are in the same room as the PLM). Meanwhile, the entire procedure when adding a water sensor to my ISY is flaky. More than once, the device I am attempting to add doesn't show up until AFTER I reboot the ISY. This happened to me even when I did the successful installation of the original 2 devices. I guess I am going to abandon the entire water sensor endeavor. All of the devices which are hardwired (dimmers, switches, garage door status/control, themostat) are working great. Based on your reply there looks like a few possible areas for you to confirm and validate. 1. How old is the PLM in the home? Please state all the hardware info on the back of the PLM. Using the ISY go to Tools -> Diagnostics -> PLM Info / Status. Please provide a screen capture of the information. 2. Coupling / Bridging: Please confirm proper coupling following the full users guide for the PLM to another dual band device. Report back success / failure. 3. Confirm that the PLM is not plugged into any surge, filtering, UPS system. Confirm other noise makers / signal suckers are not the root cause of this issue. The best and proven method is to unplug all the electrical devices in the home. Once proper coupling / bridging has been verified via the 4 tap beacon test. You will confirm COM's are good, if they are add one electrical device and see how the Insteon network behaves. Keep adding a device until you find a fault, at that time you will filter out that device to avoid future issues. 4. Please post up a Level 3 Error Log for those such as LeeG for review. As this will help narrow down the root cause or at the very least identify what COM's or the level of COM's are present. 5. Take just one sensor and delete it from the ISY. Hard reset this sensor, add it back to the ISY. Do not add it to any scenes or programs. Change the state of the sensor by pressing the button and ensure the Level 3 Error log is running. Upload the results here for review. You're doing this because it will identify how this one device operates with a known state. 6. If you're not on 4.2.18 firmware and your *About* in the system does not confirm the firmware and UI are not the same. Please ensure you clear the Java Cache, ensure you're using the supplied links from 4.2.18 to access the Admin UI as using a older version will cause random issues. Link to comment
dba62 Posted November 29, 2014 Author Share Posted November 29, 2014 PLM is v9B. I just purchased this back in May. The ISY is running 4.0.5. Should I upgrade to 4.2.18? Honestly, I'm probably not going to unplug every electrical device in my house. The PLM and ISY are not plugged into a surge detector and I have good communication with all of my hardwired Insteon devices with the exception of the leak sensors. Link to comment
LeeG Posted November 29, 2014 Share Posted November 29, 2014 Are there other battery powered RF only devices in use (Motion Sensor, TriggerLinc, Mini Remote, etc)? Link to comment
Teken Posted November 29, 2014 Share Posted November 29, 2014 PLM is v9B. I just purchased this back in May. The ISY is running 4.0.5. Should I upgrade to 4.2.18? Honestly, I'm probably not going to unplug every electrical device in my house. The PLM and ISY are not plugged into a surge detector and I have good communication with all of my hardwired Insteon devices with the exception of the leak sensors. It would be best to upgrade the ISY so everyone is using the same point of reference. Please ensure you follow all the steps for the upgrade process and confirm that the firmware and UI match 4.2.18 when done. You will need to confirm the 4 tap beacon test outlined in the full users manual. This will at least confirm proper coupling and bridging. Keep in mind it doesn't matter what others tell you about dual band devices installed into (metal) JBOX's the RF is extremely limited. The only proven and sure method is using a plug in dual band device or a AP / Range Extender. Note, all the proper coupling in the world does not help you if your problem is a noise issue or signal sucker. As painful as it is to do its something you really do once and that's it. Why? Because this ensures a rock solid Insteon network and identifies those signal suckers / noise makers. Ultimately, this translates to a happy customer who can enjoy his HA system to the fullest. All other steps outlined above still need to be done and provided. This will allow the forum members to assist you with factual data and the same point of reference. Link to comment
dba62 Posted November 29, 2014 Author Share Posted November 29, 2014 Are there other battery powered RF only devices in use (Motion Sensor, TriggerLinc, Mini Remote, etc)? No. I have switches, dimmer, thermostat and garage door status. Link to comment
LeeG Posted November 29, 2014 Share Posted November 29, 2014 Thanks. That means the only RF battery devices are the Leak Sensors. Could mean there is not reliable RF coverage for some reason. I would move to 4.2.18. It has always been stable and is now the latest Official release. Use Help | About to confirm both Firmware and UI indicate 4.2.18. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device. Enter a Leak Sensor address, use Name of choice, and Auto Discover. Before clicking Ok put Leak Sensor into manual linking mode and have it near the 2413 PLM, then click Ok. Post the event trace when New INSTEON Device completes. Link to comment
LeeG Posted November 29, 2014 Share Posted November 29, 2014 There are some additional items to look into. It is not possible to have multiple Leak Sensor failures. Are there other wireless devices (not Insteon) in use such as a wireless baby sitter or some other source for RF activity? Unless the PLM RF has failed which is unlikely the Leak Sensor should have no trouble talking to the PLM a few feet away. I'm hoping there is something else that is using RF which is interfering with Leak Sensor to PLM comm. Link to comment
stusviews Posted November 29, 2014 Share Posted November 29, 2014 No. I have switches, dimmer, thermostat and garage door status. The INSTEON thermostat is RF. I had one Leak Sensor that stopped sending heartbeats which resulted in my getting the same messages you're getting (same program), Nothing I did corrected the problem--except replacing the Leak Sensor. BTW, the "defective" Leak Sensor function correctly in every other way. Only the heartbeat stopped. Alive, but no heartbeat--It's an INSTEON zombie Link to comment
dba62 Posted November 30, 2014 Author Share Posted November 30, 2014 Thanks. That means the only RF battery devices are the Leak Sensors. Could mean there is not reliable RF coverage for some reason. I would move to 4.2.18. It has always been stable and is now the latest Official release. Use Help | About to confirm both Firmware and UI indicate 4.2.18. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device. Enter a Leak Sensor address, use Name of choice, and Auto Discover. Before clicking Ok put Leak Sensor into manual linking mode and have it near the 2413 PLM, then click Ok. Post the event trace when New INSTEON Device completes. OK - I did that. It seemed to work. During that add of the one leak sensor it detected a second, but that failed to add (presumably because I had not engaged the set button) Here is the event trace. Anything interesting? Sat 11/29/2014 07:50:39 PM : [2E 14 DF ] Added to list of devices to link to ISY Sat 11/29/2014 07:50:39 PM : [iNST-TX-I1 ] 02 62 2E 14 DF 0F 0D 00 Sat 11/29/2014 07:50:39 PM : [iNST-ACK ] 02 62 2E.14.DF 0F 0D 00 06 (00) Sat 11/29/2014 07:50:40 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 0D 02 (02) Sat 11/29/2014 07:50:40 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:40 PM : [iNST-TX-I1 ] 02 62 2E 14 DF 0F 10 00 Sat 11/29/2014 07:50:40 PM : [iNST-ACK ] 02 62 2E.14.DF 0F 10 00 06 ID-REQ (00) Sat 11/29/2014 07:50:40 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 10 00 ID-REQ (00) Sat 11/29/2014 07:50:40 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:40 PM : [iNST-SRX ] 02 50 2E.14.DF 10.08.41 8B 02 41 (41) Sat 11/29/2014 07:50:40 PM : [std-Broadcast] 2E.14.DF-->10.08.41, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:40 PM : [2E 14 DF 0 ] Calibrating engine version Sat 11/29/2014 07:50:40 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 11/29/2014 07:50:40 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 11/29/2014 07:50:41 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:50:41 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:41 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F FF 01 E2 01 2B 94 EA FF 00 01 35 Sat 11/29/2014 07:50:41 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:50:41 PM : [2E 14 DF 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Sat 11/29/2014 07:50:41 PM : [2E 14 DF 0 ] Reading all links Sat 11/29/2014 07:50:41 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Sat 11/29/2014 07:50:41 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Sat 11/29/2014 07:50:42 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:50:42 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:42 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F FF 01 E2 01 2B 94 EA FF 00 01 35 Sat 11/29/2014 07:50:42 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:50:42 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA Sat 11/29/2014 07:50:42 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00) Sat 11/29/2014 07:50:43 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:50:43 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:43 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F F7 01 62 02 2B 94 EA FF 00 02 BB Sat 11/29/2014 07:50:43 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:50:43 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Sat 11/29/2014 07:50:43 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Sat 11/29/2014 07:50:44 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:50:44 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:44 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F EF 01 62 04 2B 94 EA FF 00 04 BF Sat 11/29/2014 07:50:44 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:50:44 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Sat 11/29/2014 07:50:44 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Sat 11/29/2014 07:50:45 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:50:45 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:45 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F E7 01 E2 FF 28 51 E7 03 00 04 91 Sat 11/29/2014 07:50:45 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:50:45 PM : [28 51 E7 1 ] Added to list of devices to link to ISY Sat 11/29/2014 07:50:45 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 Sat 11/29/2014 07:50:45 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00) Sat 11/29/2014 07:50:46 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:50:46 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:50:46 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1 Sat 11/29/2014 07:50:46 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:50:46 PM : [2E 14 DF 1 ] Start : Adding device to ISY Sat 11/29/2014 07:50:46 PM : [2E 14 DF 1 ] Finish : Adding device to ISY was Successful Sat 11/29/2014 07:50:46 PM : [2E 14 DF 1 ] Link 0 : 0FF8 [E2012B94EA010001] Saving [E2012B94EA010001] Sat 11/29/2014 07:50:46 PM : [2E 14 DF 2 ] Start : Adding device to ISY Sat 11/29/2014 07:50:46 PM : [2E 14 DF 2 ] Finish : Adding device to ISY was Successful Sat 11/29/2014 07:50:46 PM : [2E 14 DF 2 ] Link 1 : 0FF0 [E2022B94EA010002] Saving [E2022B94EA010002] Sat 11/29/2014 07:50:46 PM : [2E 14 DF 4 ] Start : Adding device to ISY Sat 11/29/2014 07:50:46 PM : [2E 14 DF 4 ] Finish : Adding device to ISY was Successful Sat 11/29/2014 07:50:46 PM : [2E 14 DF 4 ] Link 2 : 0FE8 [E2042B94EA010004] Saving [E2042B94EA010004] Sat 11/29/2014 07:50:46 PM : [2E 14 DF 0 ] Successfully added device Sat 11/29/2014 07:50:46 PM : [iNST-TX-I1 ] 02 62 28 51 E7 0F 0D 00 Sat 11/29/2014 07:50:46 PM : [iNST-ACK ] 02 62 28.51.E7 0F 0D 00 06 (00) Sat 11/29/2014 07:50:55 PM : [iNST-TX-I1 ] 02 62 28 51 E7 0F 0D 00 Sat 11/29/2014 07:50:55 PM : [iNST-ACK ] 02 62 28.51.E7 0F 0D 00 06 (00) Sat 11/29/2014 07:51:04 PM : [iNST-TX-I1 ] 02 62 28 51 E7 0F 0D 00 Sat 11/29/2014 07:51:04 PM : [iNST-ACK ] 02 62 28.51.E7 0F 0D 00 06 (00) Sat 11/29/2014 07:51:08 PM : [28 51 E7 1 ] Failed to add device, reason 3 Sat 11/29/2014 07:51:08 PM : ---- Start: Generate Scenes from links ---- Sat 11/29/2014 07:51:09 PM : ---- End: Generate Scenes from links ---- Sat 11/29/2014 07:51:09 PM : [All ] Writing 24 bytes to devices Sat 11/29/2014 07:51:09 PM : [2E 14 DF 1 ] Link 0 : 0FF8 [E2012B94EA010001] Writing [E2012B94EA010001] Sat 11/29/2014 07:51:09 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 02 0F FF 08 E2 01 2B 94 EA 01 00 01 2B Sat 11/29/2014 07:51:09 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 02 0F FF 08 E2 01 2B 94 EA 01 00 01 2B 06 (00) Sat 11/29/2014 07:51:10 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:51:10 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:51:10 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 2E 14 DF 10 08 41 15 Sat 11/29/2014 07:51:10 PM : [PLM ] Group 1 : Writing Responder Link matching [2E 14 DF 1 ] Link 0 : 0FF8 [E2012B94EA010001] Sat 11/29/2014 07:51:10 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 23 2F 00 (00) Sat 11/29/2014 07:51:10 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sat 11/29/2014 07:51:10 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 23 2F 00 (00) Sat 11/29/2014 07:51:10 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sat 11/29/2014 07:51:10 PM : [iNST-DUP ] Previous message ignored. Sat 11/29/2014 07:51:10 PM : [2E 14 DF 1 ] Link 1 : 0FF0 [E2022B94EA010002] Writing [E2022B94EA010002] Sat 11/29/2014 07:51:10 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 02 0F F7 08 E2 02 2B 94 EA 01 00 02 31 Sat 11/29/2014 07:51:10 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 02 0F F7 08 E2 02 2B 94 EA 01 00 02 31 06 (00) Sat 11/29/2014 07:51:11 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:51:11 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:51:11 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 2E 14 DF 10 08 41 06 Sat 11/29/2014 07:51:11 PM : [PLM ] Group 2 : Writing Responder Link matching [2E 14 DF 1 ] Link 1 : 0FF0 [E2022B94EA010002] Sat 11/29/2014 07:51:11 PM : [2E 14 DF 1 ] Link 2 : 0FE8 [E2042B94EA010004] Writing [E2042B94EA010004] Sat 11/29/2014 07:51:11 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 02 0F EF 08 E2 04 2B 94 EA 01 00 04 35 Sat 11/29/2014 07:51:11 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 02 0F EF 08 E2 04 2B 94 EA 01 00 04 35 06 (00) Sat 11/29/2014 07:51:12 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:51:12 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:51:12 PM : [MNG-LNK-RSP ] 02 6F 41 A2 04 2E 14 DF 10 08 41 06 Sat 11/29/2014 07:51:12 PM : [PLM ] Group 4 : Writing Responder Link matching [2E 14 DF 1 ] Link 2 : 0FE8 [E2042B94EA010004] Sat 11/29/2014 07:51:12 PM : [2E 14 DF 1 ] Link 4 : 0FD8 [0000000000000000] Writing [00..............] Sat 11/29/2014 07:51:12 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 Sat 11/29/2014 07:51:12 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 06 (00) Sat 11/29/2014 07:51:13 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:51:13 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:51:13 PM : [2E 14 DF 1 ] Link 5 : 0FD0 : Writing High Water Byte Sat 11/29/2014 07:51:13 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 0F D7 01 00 00 00 00 00 00 00 00 EA Sat 11/29/2014 07:51:13 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 0F D7 01 00 00 00 00 00 00 00 00 EA 06 (00) Sat 11/29/2014 07:51:14 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:51:14 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:51:14 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F D7 01 00 00 00 00 00 00 00 00 E9 Sat 11/29/2014 07:51:14 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:51:14 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 00 0F D7 01 00 00 00 00 00 00 00 00 EA Sat 11/29/2014 07:51:14 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 00 0F D7 01 00 00 00 00 00 00 00 00 EA 06 (00) Sat 11/29/2014 07:51:15 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:51:15 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 11/29/2014 07:51:15 PM : [iNST-ERX ] 02 51 2E 14 DF 2B 94 EA 11 2F 00 00 01 0F D7 01 00 00 00 00 00 00 00 00 E9 Sat 11/29/2014 07:51:15 PM : [Ext-Direct ] 2E.14.DF-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 11/29/2014 07:51:15 PM : [iNST-TX-I2CS] 02 62 2E 14 DF 1F 2F 00 00 02 0F D7 08 00 00 00 00 00 00 00 00 E1 Sat 11/29/2014 07:51:15 PM : [iNST-ACK ] 02 62 2E.14.DF 1F 2F 00 00 02 0F D7 08 00 00 00 00 00 00 00 00 E1 06 (00) Sat 11/29/2014 07:51:16 PM : [iNST-SRX ] 02 50 2E.14.DF 2B.94.EA 2B 2F 00 (00) Sat 11/29/2014 07:51:16 PM : [std-Direct Ack] 2E.14.DF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Link to comment
LeeG Posted November 30, 2014 Share Posted November 30, 2014 Device 2E.14.DF Leak Sensor with firmware v.41 added successfully with the best comm possible. Could not be any better comm. Link to comment
LeeG Posted November 30, 2014 Share Posted November 30, 2014 The next test is have the Event Viewer at LEVEL 3 as before. Tap the Leak Sensor Set button to generate a Dry On or Wet On followed by a Heartbeat message 15-20 seconds later. Post the event trace. Link to comment
dba62 Posted November 30, 2014 Author Share Posted November 30, 2014 I have successfully added all 4 leak sensors. This is a new record. May call Guinness. I'm thinking I will move two of the sensors to their remote locations and leave the other two near the PLM in order to see if I have an RF connectivity issue. Here is the event log from the set button test: Sun 11/30/2014 08:53:37 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.02 CB 11 02 LTONRR (02) Sun 11/30/2014 08:53:37 AM : [std-Group ] 28.54.F7-->Group=2, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:37 AM : [D2D EVENT ] Event [28 54 F7 2] [DON] [2] uom=0 prec=-1 Sun 11/30/2014 08:53:37 AM : [ 28 54 F7 2] DON 2 Sun 11/30/2014 08:53:37 AM : [D2D EVENT ] Event [28 54 F7 2] [sT] [255] uom=0 prec=-1 Sun 11/30/2014 08:53:37 AM : [ 28 54 F7 2] ST 255 Sun 11/30/2014 08:53:37 AM : [D2D EVENT ] Event [28 54 F7 1] [sT] [0] uom=0 prec=-1 Sun 11/30/2014 08:53:37 AM : [ 28 54 F7 1] ST 0 Sun 11/30/2014 08:53:38 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.02 CB 11 02 LTONRR (02) Sun 11/30/2014 08:53:38 AM : [std-Group ] 28.54.F7-->Group=2, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:38 AM : [iNST-DUP ] Previous message ignored. Sun 11/30/2014 08:53:39 AM : [iNST-SRX ] 02 50 28.54.F7 2B.94.EA 41 11 02 LTONRR (02) Sun 11/30/2014 08:53:39 AM : [std-Cleanup ] 28.54.F7-->ISY/PLM Group=2, Max Hops=1, Hops Left=0 Sun 11/30/2014 08:53:39 AM : [iNST-DUP ] Previous message ignored. Sun 11/30/2014 08:53:39 AM : [iNST-SRX ] 02 50 28.54.F7 11.01.02 CB 06 00 (00) Sun 11/30/2014 08:53:39 AM : [std-Group ] 28.54.F7-->11.01.02, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:39 AM : [iNST-INFO ] Previous message ignored. Sun 11/30/2014 08:53:40 AM : [iNST-SRX ] 02 50 28.54.F7 11.01.02 CB 06 00 (00) Sun 11/30/2014 08:53:40 AM : [std-Group ] 28.54.F7-->11.01.02, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:40 AM : [iNST-INFO ] Previous message ignored. Sun 11/30/2014 08:53:53 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.04 CB 11 04 LTONRR (04) Sun 11/30/2014 08:53:53 AM : [std-Group ] 28.54.F7-->Group=4, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 4] [DON] [4] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 4] DON 4 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 1] [sT] [255] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 1] ST 255 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 2] [sT] [0] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 2] ST 0 Sun 11/30/2014 08:53:54 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.04 CB 11 04 LTONRR (04) Sun 11/30/2014 08:53:54 AM : [std-Group ] 28.54.F7-->Group=4, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:54 AM : [iNST-DUP ] Previous message ignored. Sun 11/30/2014 08:53:55 AM : [iNST-SRX ] 02 50 28.54.F7 2B.94.EA 41 11 04 LTONRR (04) Sun 11/30/2014 08:53:55 AM : [std-Cleanup ] 28.54.F7-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Sun 11/30/2014 08:53:55 AM : [iNST-DUP ] Previous message ignored. Sun 11/30/2014 08:53:55 AM : [iNST-SRX ] 02 50 28.54.F7 11.01.04 CB 06 00 (00) Sun 11/30/2014 08:53:55 AM : [std-Group ] 28.54.F7-->11.01.04, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:55 AM : [iNST-INFO ] Previous message ignored. Sun 11/30/2014 08:53:56 AM : [iNST-SRX ] 02 50 28.54.F7 11.01.04 CB 06 00 (00) Sun 11/30/2014 08:53:56 AM : [std-Group ] 28.54.F7-->11.01.04, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:56 AM : [iNST-INFO ] Previous message ignored. Link to comment
LeeG Posted November 30, 2014 Share Posted November 30, 2014 Thanks for the additional data. It looks as it should, the Heartbeat message is there with good comm. When you move two to their remote location try the Set button tap again to see how comm is at the final location. Sun 11/30/2014 08:53:53 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.04 CB 11 04 LTONRR (04) Sun 11/30/2014 08:53:53 AM : [std-Group ] 28.54.F7-->Group=4, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 4] [DON] [4] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 4] DON 4 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 1] [sT] [255] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 1] ST 255 Link to comment
dba62 Posted November 30, 2014 Author Share Posted November 30, 2014 Thanks for the additional data. It looks as it should, the Heartbeat message is there with good comm. When you move two to their remote location try the Set button tap again to see how comm is at the final location. Sun 11/30/2014 08:53:53 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.04 CB 11 04 LTONRR (04) Sun 11/30/2014 08:53:53 AM : [std-Group ] 28.54.F7-->Group=4, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 4] [DON] [4] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 4] DON 4 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 1] [sT] [255] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 1] ST 255 Thanks for your help Lee. Does the (04) indicate the comm status? If not, how can you tell? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.