Originally posted by 519zwave
View Post
Announcement
Collapse
No announcement yet.
Initial DSC setup and Envisalink
Collapse
X
-
Originally posted by spud View PostI encourage other users to comment on this, but from my experience the communication from the panel to HS3 through EnvisaLink is instant for me.
Comment
-
Originally posted by claude View PostFor me, PIR latency is the issue. It can take from 1 to 4 seconds before the sensor picks up; this may be a PIR setting issue or a bad PIR.
Delays in motion controlled lighting are a deal breaker for WAF around here.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by rprade View PostThat is exactly my concern. I have tried Bosch and DSC PIRs and they all seem to have about a 1 second lag reporting motion, which is still acceptable for motion controlled lighting. Using the Arduino as the input device and a Z-Wave switch or dimmer as the light control yields a response almost immediately after the PIR reports motion. The Arduino input triggers an event nearly instantly, so the only delays are in the PIR itself and the Z-Wave communication. As long as there is little or no added delay in going through the panel, Envisalink module and plug-in it would be fine.
Delays in motion controlled lighting are a deal breaker for WAF around here.
The point is, PIR's will perform in part based on how they're set up.
Comment
-
Guest
Thanks Spud -fixed issue - was my fault - My DSC auto registered zones 9-16, but I had to turn 17-48 on in programming 204-207. Sorry about that.
Your plug-in continues to work great for me.
Comment
-
Originally posted by spud View PostI encourage other users to comment on this, but from my experience the communication from the panel to HS3 through EnvisaLink is instant for me.
The events restart a pair of timers when the device goes to motion as well as to write a log entry with the other timer in it. I get a pair of log entries: the event that triggers first will show the other timer at 0:00:00 and the second event to trigger will show the elapsed time since the first. I ran the events for the last couple of days. Below is a sampling of the log entries, I edited out the first triggers, so all that is left is the second.
Dec-27 9:31:59 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.6406368
Dec-27 9:31:49 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5937520
Dec-27 9:30:48 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5469339
Dec-27 9:29:45 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.1562386
Dec-27 9:28:05 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6406274
Dec-27 9:27:04 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4687690
Dec-27 9:24:50 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7499332
Dec-27 9:23:46 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5468769
Dec-27 9:23:36 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4062506
Dec-27 9:22:36 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4999993
Dec-27 9:21:44 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5156243
Dec-27 9:20:41 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7031369
Dec-27 9:19:40 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4687501
Dec-27 9:18:45 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6406407
Dec-27 9:13:19 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6250141
Dec-27 9:11:24 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6093034
Dec-27 9:07:51 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7656290
Dec-27 9:07:43 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7187483
Dec-27 9:06:43 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4218746
Dec-27 9:05:39 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7187471
Dec-27 9:05:22 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7031356
Dec-27 8:58:57 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.8906136
Dec-27 8:57:55 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4843816
Dec-27 8:56:31 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5312006
Dec-27 8:55:46 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.3593692
Dec-27 8:55:12 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5312589
Dec-27 8:54:22 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5625018
Dec-27 8:53:20 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5000129
Dec-27 8:52:16 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5937985
Dec-27 8:32:41 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7656386
Dec-27 8:26:45 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4531344
Dec-27 8:25:21 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4843754
Dec-27 12:52:57 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7812454
Dec-26 11:55:08 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.3125090
Dec-26 11:53:05 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5937535
Dec-26 11:51:44 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.3124987
Dec-26 11:21:12 PM Trigger Arduino Motion DSB - DSC Timer: 00:00:00.3281191
Dec-26 11:20:39 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.3593627
Dec-26 11:18:42 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5000036
Dec-26 11:15:19 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.3593745
Dec-26 11:11:24 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5624898
Dec-26 9:59:47 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5468737
Dec-26 9:58:50 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4687488
Dec-26 9:57:48 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4062542
Dec-26 9:54:35 PM Trigger Arduino Motion DSB - DSC Timer: 00:00:00.8906197
Dec-26 9:52:44 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.6562500
Dec-26 9:52:34 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4062391
Dec-26 9:45:54 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.8281254
Dec-26 9:45:26 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.3750048
This is just a sample, but the results have been very consistent, the Envisalink is around 1/2-3/4 second behind the Arduino and earlier tests show the Arduino to be about 1/2 second behind the PIR.
The net result is that the Envisalink is *slightly* slower than the Arduino, but not much.
When it comes to triggering a light with motion, it is amazing how sensitive we are to delays. The 1/2 second additional, *feels* longer.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by rprade View PostI received my panel and put it in for a test over the holiday. It felt a little slower than my Arduino on the motion sensors, so I set up a handful of events to test it. I installed and configured the panel with a handful of PIRs and wired a couple of them to the panel as well as an Arduino input.
The events restart a pair of timers when the device goes to motion as well as to write a log entry with the other timer in it. I get a pair of log entries: the event that triggers first will show the other timer at 0:00:00 and the second event to trigger will show the elapsed time since the first. I ran the events for the last couple of days. Below is a sampling of the log entries, I edited out the first triggers, so all that is left is the second.
Dec-27 9:31:59 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.6406368
Dec-27 9:31:49 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5937520
Dec-27 9:30:48 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5469339
Dec-27 9:29:45 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.1562386
Dec-27 9:28:05 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6406274
Dec-27 9:27:04 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4687690
Dec-27 9:24:50 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7499332
Dec-27 9:23:46 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5468769
Dec-27 9:23:36 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4062506
Dec-27 9:22:36 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4999993
Dec-27 9:21:44 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5156243
Dec-27 9:20:41 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7031369
Dec-27 9:19:40 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4687501
Dec-27 9:18:45 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6406407
Dec-27 9:13:19 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6250141
Dec-27 9:11:24 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6093034
Dec-27 9:07:51 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7656290
Dec-27 9:07:43 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7187483
Dec-27 9:06:43 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4218746
Dec-27 9:05:39 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7187471
Dec-27 9:05:22 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7031356
Dec-27 8:58:57 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.8906136
Dec-27 8:57:55 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4843816
Dec-27 8:56:31 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5312006
Dec-27 8:55:46 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.3593692
Dec-27 8:55:12 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5312589
Dec-27 8:54:22 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5625018
Dec-27 8:53:20 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5000129
Dec-27 8:52:16 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5937985
Dec-27 8:32:41 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7656386
Dec-27 8:26:45 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4531344
Dec-27 8:25:21 AM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4843754
Dec-27 12:52:57 AM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7812454
Dec-26 11:55:08 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.3125090
Dec-26 11:53:05 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5937535
Dec-26 11:51:44 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.3124987
Dec-26 11:21:12 PM Trigger Arduino Motion DSB - DSC Timer: 00:00:00.3281191
Dec-26 11:20:39 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.3593627
Dec-26 11:18:42 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5000036
Dec-26 11:15:19 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.3593745
Dec-26 11:11:24 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5624898
Dec-26 9:59:47 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.5468737
Dec-26 9:58:50 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4687488
Dec-26 9:57:48 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.4062542
Dec-26 9:54:35 PM Trigger Arduino Motion DSB - DSC Timer: 00:00:00.8906197
Dec-26 9:52:44 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.6562500
Dec-26 9:52:34 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4062391
Dec-26 9:45:54 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.8281254
Dec-26 9:45:26 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.3750048
This is just a sample, but the results have been very consistent, the Envisalink is around 1/2-3/4 second behind the Arduino and earlier tests show the Arduino to be about 1/2 second behind the PIR.
The net result is that the Envisalink is *slightly* slower than the Arduino, but not much.
When it comes to triggering a light with motion, it is amazing how sensitive we are to delays. The 1/2 second additional, *feels* longer.
I wonder if there is a significant timing difference between the two?
Comment
-
Originally posted by spud View Postwhat type of trigger did you use: the native "device changes and become" type or the "EnvisaLink receives a message: Zone open" type?
I wonder if there is a significant timing difference between the two?
To everyone clear the delays are almost insignificant.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by spud View Postwhat type of trigger did you use: the native "device changes and become" type or the "EnvisaLink receives a message: Zone open" type?
I wonder if there is a significant timing difference between the two?
Dec-27 7:13:49 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.4687876
Dec-27 7:13:49 PM Trigger DSCM Motion EX - Arduino Timer: 00:00:00.4687876
Dec-27 7:12:47 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.2656136
Dec-27 7:12:47 PM Trigger DSCM Motion EX - Arduino Timer: 00:00:00.2656136
Dec-27 7:11:36 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6718741
Dec-27 7:11:36 PM Trigger DSCM Motion EX - Arduino Timer: 00:00:00.6718741
Dec-27 7:10:38 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5625041
Dec-27 7:10:38 PM Trigger DSCM Motion DSB - Arduino Timer: 00:00:00.5625041
Dec-27 4:59:31 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.1718857
Dec-27 4:59:31 PM Trigger DSCM Motion DSB - Arduino Timer: 00:00:00.1718857
Dec-27 4:58:45 PM Trigger DSCM Motion EX - Arduino Timer: 00:00:00.7656324
Dec-27 4:58:45 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.7500114
Dec-27 4:53:27 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.3749902
Dec-27 4:53:27 PM Trigger DSCM Motion EX - Arduino Timer: 00:00:00.3749902
Dec-27 3:50:02 PM Trigger DSCM Motion EX - Arduino Timer: 00:00:00.6562096
Dec-27 3:50:02 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6405728
Dec-27 3:49:30 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.5780605
Dec-27 3:49:30 PM Trigger DSCM Motion DSB - Arduino Timer: 00:00:00.5780605
Dec-27 3:48:20 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.6562546
Dec-27 3:48:20 PM Trigger DSCM Motion DSB - Arduino Timer: 00:00:00.6562546
Dec-27 3:47:19 PM Trigger DSC Motion DSB - Arduino Timer: 00:00:00.7499968
Dec-27 3:47:19 PM Trigger DSCM Motion DSB - Arduino Timer: 00:00:00.7499968
Dec-27 3:46:43 PM Trigger DSCM Motion EX - Arduino Timer: 00:00:00.8437484
Dec-27 3:46:43 PM Trigger DSC Motion EX - Arduino Timer: 00:00:00.6874986
Based on these tests, I would say it is safe to assume one trigger is as good as another. In the cases where there was a difference, the device was faster.Last edited by randy; December 28, 2015, 10:54 AM.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by mikedr View PostRandy, so is it fair to conclude that you're pretty happy with the way you're getting motion reports from the Enivsalink -- I.e., insignificant delays?
The one room that is most tested is a room in the basement. The fastest response we ever had was with the old HSM100 Z-Wave PIR. The Aeotec sensors were slower. Subjectively (I don't know how to measure) I would say that the Envisalink trigger is faster than the Aeotec sensor and slower than the HSM100s. My wife says the Envisalink response is quick enough for her. If it is responsive enough for her entering with a basket of laundry, it is fast enough.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
Comment