rmazzaro Posted February 7, 2018 Share Posted February 7, 2018 I have $DailySumpCycles set up as an Integer variable.... The program is and the alert works...but the counter stays at "1" and never increments. I will also make this variable the "Yesterday" variable at the end of the day...and reset the Daily variable. Then I can see two days worth of counters.... Thanks in advance! ======================================= Sump ON - [iD 000D][Parent 0001][Run At Startup] If Status 'Sump' is 100% Then Send Notification to 'Russ' content 'Sump On' Wait 1 minute $DailySumpCycles += 1 Else - No Actions - (To add one, press 'Action') Link to comment
KeviNH Posted February 7, 2018 Share Posted February 7, 2018 Does the sump cycle normally last more than a minute? If not, the program will never make it past the Wait. (see this thread) Link to comment
Goose66 Posted February 7, 2018 Share Posted February 7, 2018 I assume the wait is to only update the counter if the sump stays at 100% (On?) for more than a minute. So I suspect that this is the issue. It is hard for me to imagine a sump pump running for more than 4 or 5 seconds, much less a minute. But I don't know what your installation looks like. Link to comment
stusviews Posted February 7, 2018 Share Posted February 7, 2018 As a test, run Then. Does the counter increment? If so, remove the Wait. What's the result? Link to comment
rmazzaro Posted February 7, 2018 Author Share Posted February 7, 2018 Does the sump cycle normally last more than a minute? If not, the program will never make it past the Wait. (see this thread) It doesn't. 30 seconds max. I assume the wait is to only update the counter if the sump stays at 100% (On?) for more than a minute. So I suspect that this is the issue. It is hard for me to imagine a sump pump running for more than 4 or 5 seconds, much less a minute. But I don't know what your installation looks like. The wait is to prevent multiple emails. For some reason, I'll get two or three sometimes. I still do so this was a failed attempt to prevent that. Link to comment
Goose66 Posted February 7, 2018 Share Posted February 7, 2018 Sounds like your sensor for the sump pump running is "bouncing," i.e., sending multiple Ons and Offs during a single run. Each time the status of the "Sump" device changes, the program is run anew and any running copies, e.g., sitting in Waits, are cancelled. So that's why the variable is never incremented. Can you tell us what type of device "Sump" is? One thing to try is something like this: If Status 'Sump' is 100% Then Disable Program 'Sump ON' Send Notification to 'Russ' content 'Sump On' $DailySumpCycles += 1 Wait 1 minute Enable Program 'Sump ON' Else - No Actions - (To add one, press 'Action')to move the Link to comment
rmazzaro Posted February 7, 2018 Author Share Posted February 7, 2018 Sounds like your sensor for the sump pump running is "bouncing," i.e., sending multiple Ons and Offs during a single run. Each time the status of the "Sump" device changes, the program is run anew and any running copies, e.g., sitting in Waits, are cancelled. So that's why the variable is never incremented. Can you tell us what type of device "Sump" is? One thing to try is something like this: If Status 'Sump' is 100% Then Disable Program 'Sump On' Send Notification to 'Russ' content 'Sump On' $DailySumpCycles += 1 Wait 1 minute Enable Program 'Sump On' Else - No Actions - (To add one, press 'Action')to move the It's a sump pump being monitored by a SynchroLinc V.30. Thanks for the idea. I'll give this a shot. Link to comment
Goose66 Posted February 7, 2018 Share Posted February 7, 2018 Depending on how your SynchroLinc was calibrated, it may very well be sending multiple Ons and Offs while the pump runs. I would suggest calibrating the SynchroLinc with the Off state first (hopefully 0W) and then the On state. That way the trigger point will be closer to the low energy state. Also, if you change your program to "If 'Sump' is switched On," you will have fewer program invocations. After performing both of these steps, you may be able to remove the Disable/Enable and Wait from the program. Link to comment
rmazzaro Posted February 8, 2018 Author Share Posted February 8, 2018 It's calibrated. I was very careful doing that. I'm now getting the counter changing each time...so maybe the WAIT was the issue. I'll make the "ON" change too. Thanks to all for their help and suggestion! Link to comment
larryllix Posted February 8, 2018 Share Posted February 8, 2018 It's calibrated. I was very careful doing that. I'm now getting the counter changing each time...so maybe the WAIT was the issue. I'll make the "ON" change too. Thanks to all for their help and suggestion!The synchrolinc already has a hysteresis delay timer built in. An additional wait should not be necessary in an ISY program. You cannot have a program disable itself and then re-enable itself. When a program is disabled, it stops processing lines. The suggested program does not display it's own name. Sent from my SGH-I257M using Tapatalk Link to comment
Goose66 Posted February 8, 2018 Share Posted February 8, 2018 The synchrolinc already has a hysteresis delay timer built in. An additional wait should not be necessary in an ISY program. You cannot have a program disable itself and then re-enable itself. When a program is disabled, it stops processing lines. The suggested program does not display it's own name. Sent from my SGH-I257M using Tapatalk The SynchroLinc threshold power usage depends on the order of calibration of the levels - high energy level first, then the threshold is 25% of the delta less than the high energy level, but low energy level first, then the threshold is 25% of the delta above the low energy level, which would be more effective for determining On vs. Off, IMO. I cannot verify that disabling a program halts its execution without testing - but that seems to go against my understanding of how programs work. Regardless, it seems that multiple Ons and Offs was/is the issue, so you can break your program into two programs: a Trigger Program: Sump On (enabled) If 'Sump' is switched On Then Run 'Sump Notify' (Then Path) Else - No Actions - (To add one, press 'Action') and a conditional program that is disabled: Sump Notify (disabled) If Status 'Sump' is On (Not evaluated or necessary) Then Disable Program 'Sump On' Send Notification to 'Russ' content 'Sump On' $DailySumpCycles += 1 Wait 1 minute Enable Program 'Sump On' Else - No Actions - (To add one, press 'Action') Link to comment
KeviNH Posted February 8, 2018 Share Posted February 8, 2018 This is getting really complicated. Just read the link in this first reply to this thread, and remove/minimize the Wait timer. Link to comment
Goose66 Posted February 8, 2018 Share Posted February 8, 2018 This is getting really complicated. Just read the link in this first reply to this thread, and remove/minimize the Wait timer. If the sensor is sending multiple Ons and he just removes the Wait timer, then he is going to get a bad counter value and multiple notifications with each sump pump cycle. Link to comment
larryllix Posted February 8, 2018 Share Posted February 8, 2018 The SynchroLinc threshold power usage depends on the order of calibration of the levels - high energy level first, then the threshold is 25% of the delta less than the high energy level, but low energy level first, then the threshold is 25% of the delta above the low energy level, which would be more effective for determining On vs. Off, IMO. I cannot verify that disabling a program halts its execution without testing - but that seems to go against my understanding of how programs work. Regardless, it seems that multiple Ons and Offs was/is the issue, so you can break your program into two programs: a Trigger Program: Sump On (enabled) If 'Sump' is switched On Then Run 'Sump Notify' (Then Path) Else - No Actions - (To add one, press 'Action') and a conditional program that is disabled: Sump Notify (disabled) If Status 'Sump' is On (Not evaluated or necessary) Then Disable Program 'Sump On' Send Notification to 'Russ' content 'Sump On' $DailySumpCycles += 1 Wait 1 minute Enable Program 'Sump On' Else - No Actions - (To add one, press 'Action') My synchroLinc has no order of calibration, or calibration settings. It has an On setting, a power hysteresis (I forget the exact nomenclature) setting and a delay timer. Both the power Off hysteresis, and the delay timer are different forms of hysteresis, one being by power in Watts and the other being by time. If you had a device that drew 100 Watts when On and 10 Watts off, you would set typically the On setting about 60 Watts (60%?) and the Off hysteresis setting about 30-40 Watts (20%) making it sense Off at anything below 60 - 40 = 20 Watts. After that appears to work satisfactorily, you would then add a small time delay so multiple triggers would never happen unless the synchrolinc was defective and not functioning correctly. This has been discussed many time in different threads previously. I know they are not available any more, and mine needs new power supply caps, apparently Have these units changed in the last two years? Link to comment
rmazzaro Posted February 9, 2018 Author Share Posted February 9, 2018 Just an update - I removed the WAIT that was there to prevent multiple alerts...and I started receiving multiple alerts for a single occurrence. So I broke this into two programs as was recommended. Sump ON Trigger If Status 'Sump' is On Then Run Program 'Sump ON Actions' (If) Else - No Actions - (To add one, press 'Action') Sump ON Actions If Status 'Sump' is 100% Then Disable Program 'Sump ON Trigger' Send Notification to 'Russ' content 'Sump On' $DailySumpCycles += 1 Wait 1 minute Enable Program 'Sump ON Trigger' Else - No Actions - (To add one, press 'Action') I'll post more once I know if the counter is working correctly (which it is so far) and I don't receive multiple alerts. Thanks everyone for your help and suggestions! Link to comment
larryllix Posted February 9, 2018 Share Posted February 9, 2018 Just an update - I removed the WAIT that was there to prevent multiple alerts...and I started receiving multiple alerts for a single occurrence. So I broke this into two programs as was recommended. Sump ON Trigger If Status 'Sump' is On Then Run Program 'Sump ON Actions' (If) Else - No Actions - (To add one, press 'Action') Sump ON Actions If Status 'Sump' is 100% Then Disable Program 'Sump ON Trigger' Send Notification to 'Russ' content 'Sump On' $DailySumpCycles += 1 Wait 1 minute Enable Program 'Sump ON Trigger' Else - No Actions - (To add one, press 'Action') I'll post more once I know if the counter is working correctly (which it is so far) and I don't receive multiple alerts. Thanks everyone for your help and suggestions! Looks like it should work What are the On, Off and timer settings you are using inside the synchrolinc? Link to comment
rmazzaro Posted February 9, 2018 Author Share Posted February 9, 2018 I think this is what you're looking for: Link to comment
larryllix Posted February 10, 2018 Share Posted February 10, 2018 Capture.JPG I think this is what you're looking for: Yes Thanks! 20 Watts seems very low for a sump pump and the time delay is quite short for a well working (and set) synchroLinc. Do you know how many Watt the pump draws when running? You can get that by turning off the time delay (0s) and increasing the Threshold to where it just barely turns on. Right now you have your On being sent at 20 watts and Off at 15 Watts wit only 1.34 seconds delay to send the On. This may just make it erratic as these things are made for loads up to 1800 Watts. That is working at the very bottom and maybe erratic end of the metering. Metering is not real good running at 0.3% of full scale hysteresis. That may be below it's resolution making the 5 Watts less than one count of change in the metering result. My sump pump is 1/4 HP and cycles on for shots of about 10-15 seconds each cycle. Just enough to clear the sump pit and then rests again for a few minutes or a few hours. My thoughts are you have a typical sump pump drawing a few hundred watts meaning your threshold may work better at 100-200 watts and then you could set your hysteresis somewhere around 100-150 Watts, No matter what the load of the pump I would set the time delay to 4-6 seconds if you think it is rattling the contact on/off. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.