Does your Elk M1 have 1367 control restarts in the event log?

The power on the 16awg is DC, so that shouldn't be causing any noise on the data lines.
 
Discount everything except what is in the panel log and RP.
 
I wouldn't suspect the keypad/house, but if you had bad splices in one location, generally there's more. Possibly a cable stapled too tight causing an intermittent short that is taking out the bus. I'd look through the log some more.
 
DELInstallations said:
Discount everything except what is in the panel log and RP.
 
I wouldn't suspect the keypad/house, but if you had bad splices in one location, generally there's more. Possibly a cable stapled too tight causing an intermittent short that is taking out the bus. I'd look through the log some more.
Click to expand...
There is nothing else to see in the log, it is otherwise error free.

Mike
 
I was getting numerous 1367 errors after adding an Input Expander to a remote building. I would get scores per day. The data bus run is about 400 feet. After research and a post here, I determined that there was excessive voltage drop on the data bus power feed. I had about 11.65 volts at the remote end. After changing the power feed to the remote input expander to a remote power supply, the 1367 errors went away completely.
 
LakeHouse said:
I was getting numerous 1367 errors after adding an Input Expander to a remote building. I would get scores per day. The data bus run is about 400 feet. After research and a post here, I determined that there was excessive voltage drop on the data bus power feed. I had about 11.65 volts at the remote end. After changing the power feed to the remote input expander to a remote power supply, the 1367 errors went away completely.
Click to expand...
 
I had similar problem with the detached garage and upgraded with a 4 amp auxiliary power supply and have sufficient voltage at both buildings. This restart has only happened once after several weeks of running well. It also showed zones in both buildings as bypassed immediately following the restart.
 
Mike
 
Can someone explain why the event log shows each zone as bypassed immediately following an auto system start up? Some of these zones are set as bypassable and some are not. What is the meaning of these entries? The system was armed at the time of the start up. So are these zones really bypassed or are the still alarmed after the start up? The system still appears to be alarmed at the keypad and in ekeypad.
 
Mike.
 
Here is a copy of my event log. Does anyone know why each zone is shown as bypassed following the restart when most of them are not even set as bypassable?
 

21,Thu 1/1/2015,06:17,1,1363 = REMOTE PROGRAMMING,
22,Wed 12/31/2014,22:55,1,1174 = AREA DISARMED,USER 1 (User 1)
23,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Door 3 (Zn 168)
24,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Door 2 (Zn 167)
25,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Door 1 (Zn 166)
26,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Motion1 (Zn 165)
27,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Walkin Dr (Zn 164)
28,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Window3 (Zn 163)
29,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Window2 (Zn 162)
30,Wed 12/31/2014,18:53,2,1239 = ZONE BYPASSED,Garage Window1 (Zn 161)
31,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,Kitchen Motion (Zn 20)
32,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,Front Door (Zn 19)
33,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,FamRm Rear Door (Zn 18)
34,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,FamRm Front Door (Zn 17)
35,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,Garage Door 0 (Zn 4)
36,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,Dining Rm Window (Zn 3)
37,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,Living Rm Window (Zn 2)
38,Wed 12/31/2014,18:53,1,1239 = ZONE BYPASSED,Kitchen Window (Zn 1)
39,Wed 12/31/2014,18:53,,1367 = SYSTEM START UP,Control
40,Wed 12/31/2014,17:04,1,1173 = AREA ARMED,USER 1 (User 1)
41,Wed 12/31/2014,16:42,1,1174 = AREA DISARMED,USER 1 (User 1)
42,Wed 12/31/2014,12:17,1,1173 = AREA ARMED,USER 1 (User 1)
43,Wed 12/31/2014,08:42,1,1174 = AREA DISARMED,USER 1 (User 1)
44,Tue 12/30/2014,22:07,1,1173 = AREA ARMED,USER 1 (User 1)
45,Mon 12/29/2014,16:10,2,1293 = AUTOMATIC CLOSING,
46,Mon 12/29/2014,16:10,2,1173 = AREA ARMED,"No Code" (User 203)
47,Mon 12/29/2014,10:54,2,1174 = AREA DISARMED,"No Code" (User 203)
48,Sun 12/28/2014,18:46,1,1174 = AREA DISARMED,USER 1 (User 1)
49,Sun 12/28/2014,13:02,1,1173 = AREA ARMED,User 2 (unnamed)
50,Sat 12/27/2014,22:17,1,1174 = AREA DISARMED,USER 1 (User 1)
51,Sat 12/27/2014,17:57,1,1173 = AREA ARMED,USER 1 (User 1)
52,Sat 12/27/2014,16:00,2,1293 = AUTOMATIC CLOSING,
53,Sat 12/27/2014,16:00,2,1173 = AREA ARMED,"No Code" (User 203)
54,Sat 12/27/2014,14:36,2,1174 = AREA DISARMED,USER 1 (User 1)
55,Sat 12/27/2014,14:11,2,1173 = AREA ARMED,USER 1 (User 1)
56,Sat 12/27/2014,13:06,2,1174 = AREA DISARMED,"No Code" (User 203)
57,Sat 12/27/2014,12:22,1,1174 = AREA DISARMED,USER 1 (User 1)
58,Sat 12/27/2014,10:21,1,1173 = AREA ARMED,User 2 (unnamed)
59,Fri 12/26/2014,16:40,2,1293 = AUTOMATIC CLOSING,
60,Fri 12/26/2014,16:40,2,1173 = AREA ARMED,"No Code" (User 203)
61,Fri 12/26/2014,10:51,2,1174 = AREA DISARMED,"No Code" (User 203)
62,Thu 12/25/2014,20:06,1,1174 = AREA DISARMED,USER 1 (User 1)
63,Thu 12/25/2014,11:20,2,1173 = AREA ARMED,USER 1 (User 1)
64,Thu 12/25/2014,11:19,2,1174 = AREA DISARMED,USER 1 (User 1)
65,Thu 12/25/2014,11:19,2,1293 = AUTOMATIC CLOSING,
66,Thu 12/25/2014,11:19,2,1173 = AREA ARMED,"No Code" (User 203)
67,Thu 12/25/2014,11:18,1,1173 = AREA ARMED,USER 1 (User 1)
68,Thu 12/25/2014,10:59,2,1174 = AREA DISARMED,USER 1 (User 1)
69,Wed 12/24/2014,17:10,2,1293 = AUTOMATIC CLOSING,
70,Wed 12/24/2014,17:10,2,1173 = AREA ARMED,"No Code" (User 203)
71,Wed 12/24/2014,16:53,1,1364 = REMOTE PROGRAMMING ENDS,
72,Wed 12/24/2014,16:49,1,1363 = REMOTE PROGRAMMING,
73,Wed 12/24/2014,16:30,2,1174 = AREA DISARMED,USER 1 (User 1)
74,Wed 12/24/2014,16:30,2,1293 = AUTOMATIC CLOSING,
75,Wed 12/24/2014,16:30,2,1173 = AREA ARMED,"No Code" (User 203)
76,Wed 12/24/2014,16:30,2,1239 = ZONE BYPASSED,Garage Walkin Dr (Zn 164)
77,Wed 12/24/2014,16:29,2,1174 = AREA DISARMED,"No Code" (User 203)
78,Wed 12/24/2014,15:21,1,1364 = REMOTE PROGRAMMING ENDS,
79,Wed 12/24/2014,15:20,1,1363 = REMOTE PROGRAMMING,
80,Wed 12/24/2014,15:19,1,1364 = REMOTE PROGRAMMING ENDS,
81,Wed 12/24/2014,15:17,1,1363 = REMOTE PROGRAMMING,
82,Wed 12/24/2014,14:15,1,1146 = RESTORE BURGLAR ZONE,Garage Door 0 (Zn 4)
83,Wed 12/24/2014,14:03,1,1174 = AREA DISARMED,USER 1 (User 1)
84,Wed 12/24/2014,14:03,1,1300 = EXCEPTION OPENING,USER 1 (User 1)
85,Wed 12/24/2014,14:02,1,1003 = BURGLAR ALARM, ANY AREA,Garage Door 0 (Zn 4)
86,Wed 12/24/2014,13:45,1,1173 = AREA ARMED,USER 1 (User 1)
87,Wed 12/24/2014,13:36,2,1293 = AUTOMATIC CLOSING,
88,Wed 12/24/2014,13:36,2,1173 = AREA ARMED,"No Code" (User 203)
89,Wed 12/24/2014,11:05,2,1174 = AREA DISARMED,USER 1 (User 1)
90,Wed 12/24/2014,10:35,1,1364 = REMOTE PROGRAMMING ENDS,
91,Wed 12/24/2014,10:35,1,1363 = REMOTE PROGRAMMING,
92,Tue 12/23/2014,22:17,1,1364 = REMOTE PROGRAMMING ENDS,
93,Tue 12/23/2014,21:58,1,1363 = REMOTE PROGRAMMING,
94,Tue 12/23/2014,14:56,1,1174 = AREA DISARMED,USER 1 (User 1)
95,Tue 12/23/2014,13:20,1,1173 = AREA ARMED,USER 1 (User 1)
96,Tue 12/23/2014,13:14,2,1293 = AUTOMATIC CLOSING,
97,Tue 12/23/2014,13:14,2,1173 = AREA ARMED,"No Code" (User 203)
98,Tue 12/23/2014,12:49,2,1174 = AREA DISARMED,USER 1 (User 1)
99,Mon 12/22/2014,16:50,2,1293 = AUTOMATIC CLOSING,
100,Mon 12/22/2014,16:50,2,1173 = AREA ARMED,"No Code" (User 203)
101,Mon 12/22/2014,16:45,2,1174 = AREA DISARMED,USER 1 (User 1)
102,Mon 12/22/2014,16:20,2,1293 = AUTOMATIC CLOSING,
103,Mon 12/22/2014,16:20,2,1173 = AREA ARMED,"No Code" (User 203)
104,Mon 12/22/2014,16:15,2,1174 = AREA DISARMED,USER 1 (User 1)
105,Mon 12/22/2014,16:00,2,1293 = AUTOMATIC CLOSING,
106,Mon 12/22/2014,16:00,2,1173 = AREA ARMED,"No Code" (User 203)
 
Looks like the panel rebooted for some reason. Wonder if the aux power PTC took down the panel. Wonder if the bypass was actual or if it was during a system stabilization period. Don't have much else I could offer.
 
DELInstallations said:
Looks like the panel rebooted for some reason. Wonder if the aux power PTC took down the panel. Wonder if the bypass was actual or if it was during a system stabilization period. Don't have much else I could offer.
Click to expand...
Under what circumstance might the aux power take down the panel? And what is a stabilization period? I think that I mentioned that it is every zone in the system listed in the log as bypassed.
 
The next time it happens I will open the door causing an alarm to see if the zones are bypassed or alarmed.
 
DELInstallations said:
Looks like the panel rebooted for some reason. Wonder if the aux power PTC took down the panel. Wonder if the bypass was actual or if it was during a system stabilization period. Don't have much else I could offer.
Click to expand...
Also, my Altronix is fused and has no PTC.
 
Mike.
 
mikefamig said:
Good to know. Doesn't all current in a conductor cause some EMF?
 
Mike.
Click to expand...
 
Only a changing electromagnetic field (as you get with AC) will cause interference in nearby wires.  DC current will create a constant field, but that won't cause interference. 
 
mikefamig said:
Also, my Altronix is fused and has no PTC.
 
Mike.
Click to expand...
Referring to the main panel itself, not a separate power supply.
 
If the panel's aux power output tripped out on PTC, I wonder if it would take down the entire panel or just the aux power outputs on the board. Never had a situation where I needed to try or test it.
 
Many panels and/or devices (motions, GBD's) observe a power up delay or grace period after a reboot, usually 60-90 seconds.
 
Arm the system, momentarily short vaux to ground, see what happens.   I know (from experience) that the control will restart.
 
DELInstallations said:
Referring to the main panel itself, not a separate power supply.
 
If the panel's aux power output tripped out on PTC, I wonder if it would take down the entire panel or just the aux power outputs on the board. Never had a situation where I needed to try or test it.
 
Many panels and/or devices (motions, GBD's) observe a power up delay or grace period after a reboot, usually 60-90 seconds.
Click to expand...
Interesting thought, I am running the exp from the vaux.
 
You must log in or register to reply here.

Similar threads

StarTrekDoors
PC Access 3.17.0.843 Update Release Notes
Replies
0
Views
3K
StarTrekDoors
StarTrekDoors
B
1367=SYSTEM START UP Control - after adding expander board
2 3
Replies
36
Views
5K
blueman2
B
A
My M1 experience (long).
Replies
5
Views
2K
AnotherOne
A
Back
Top