Elk Arming Status ('as' command)

iostream212

iostream212

Active Member
Hello World! (programming joke)
I am working on an Elk programming project and have noticed an undesirable occurrence when running the 'arming status' request command ('as') to my panel. It seems like when I query with the 'as' command, the results I get is the status from the previous arming state. Meaning if the arming status is 'disarmed' and I change it to 'armed stay instant' the next 'as' query results in 'disarmed.' Then I change it to something completely different, and the 'as' command is then 'armed stay instant,' as if I am always a step behind. Will someone who knows what they are doing please set me straight? :lol:
 
If I remember correctly, the status does not change in the M1 until the timer(s) runs out. By default that is 60 seconds.

I would run a test to verify, but the baby has already gone to bed.
 
I did some testing this morning and waiting a minute between polls seemed to make no difference. Even when I send an arming command to the panel, then log on to the virtual console, the same results. Always a step behind and showing the last arming state.
 
I did a test today with debugging turned on in eKeypad Here is what I get from my M1 panel.

Is it possible you are trying to read the status from the wrong index? The AS message contains details for all 8 possible areas.

Code: 
[I typed my security code into a keypad here. The system was 'ready to arm'.]

2009-08-28 13:19:16.685 eKeypad Pro Beta[27103:20b] (My Elk M1) Received Elk Msg: 1EAS00000000111111110000000000 - Arming Status Report Data
2009-08-28 13:19:16.686 eKeypad Pro Beta[27103:20b] - Raw Data:000000001111111100000000
2009-08-28 13:19:16.688 eKeypad Pro Beta[27103:20b] - Parsed Data:
Area:1 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:2 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:3 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:4 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:5 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:6 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:7 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:8 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active

2009-08-28 13:19:16.764 eKeypad Pro Beta[27103:20b] (My Elk M1) Received Elk Msg: 1EAS10000000411111110000000000 - Arming Status Report Data
2009-08-28 13:19:16.765 eKeypad Pro Beta[27103:20b] - Raw Data:100000004111111100000000
2009-08-28 13:19:16.766 eKeypad Pro Beta[27103:20b] - Parsed Data:
Area:1 Armed Status:Armed Away 	 Armed State:Armed Fully 	 Alarm State:No Alarm Active
Area:2 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:3 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:4 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:5 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:6 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:7 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:8 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active

[ The exit timer on my M1 starts]

2009-08-28 13:19:16.803 eKeypad Pro Beta[27103:20b] (My Elk M1) Received Elk Msg: 0FEE1006006000 - Entry/Exit Timer Data
2009-08-28 13:19:16.804 eKeypad Pro Beta[27103:20b] - Raw Data:100600600
2009-08-28 13:19:16.804 eKeypad Pro Beta[27103:20b] - Parsed Data:
Timer #1: 60 seconds
Timer #2: 60 seconds

2009-08-28 13:19:17.152 eKeypad Pro Beta[27103:20b] (My Elk M1) Received Elk Msg: 1EAS1000000031111111000000003B - Arming Status Report Data
2009-08-28 13:19:17.154 eKeypad Pro Beta[27103:20b] - Raw Data:100000003111111100000000
2009-08-28 13:19:17.154 eKeypad Pro Beta[27103:20b] - Parsed Data:
Area:1 Armed Status:Armed Away 	 Armed State:Exit Timer Running 	 Alarm State:No Alarm Active
Area:2 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:3 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:4 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:5 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:6 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:7 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:8 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active

[ The exit timer on my M1 expires]

2009-08-28 13:20:16.448 eKeypad Pro Beta[27103:20b] (My Elk M1) Received Elk Msg: 0FEE1000000000 - Entry/Exit Timer Data
2009-08-28 13:20:16.449 eKeypad Pro Beta[27103:20b] - Raw Data:100000000
2009-08-28 13:20:16.449 eKeypad Pro Beta[27103:20b] - Parsed Data:
Timer #1: 0 seconds
Timer #2: 0 seconds

2009-08-28 13:20:16.452 eKeypad Pro Beta[27103:20b] (My Elk M1) Received Elk Msg: 1EAS20000000311111110000000000 - Arming Status Report Data
2009-08-28 13:20:16.453 eKeypad Pro Beta[27103:20b] - Raw Data:200000003111111100000000
2009-08-28 13:20:16.453 eKeypad Pro Beta[27103:20b] - Parsed Data:
Area:1 Armed Status:Armed Stay 	 Armed State:Exit Timer Running 	 Alarm State:No Alarm Active
Area:2 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:3 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:4 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:5 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:6 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:7 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:8 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active

2009-08-28 13:20:17.679 eKeypad Pro Beta[27103:20b] (My Elk M1) Received Elk Msg: 1EAS20000000411111110000000000 - Arming Status Report Data
2009-08-28 13:20:17.680 eKeypad Pro Beta[27103:20b] - Raw Data:200000004111111100000000
2009-08-28 13:20:17.680 eKeypad Pro Beta[27103:20b] - Parsed Data:
Area:1 Armed Status:Armed Stay 	 Armed State:Armed Fully 	 Alarm State:No Alarm Active
Area:2 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:3 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:4 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:5 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:6 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:7 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
Area:8 Armed Status:Disarmed 	 Armed State:Ready To Arm 	 Alarm State:No Alarm Active
 
Ok so I send a disarm command and get: 1EAS000000001111111100000000000E

Looks good. I send an stay instant command and the speaker confirms 'area 1 is armed stay instant mode',
and yet when I query I get: 1EAS000000001111111100000000000E. Doesn't matter if it is a second later or 5 minutes later.

Now I disarm, the speaker confirms 'area 1 is disarmed.' I query and get : 1EAS3000000041111111000000000008

;)

* Note : I am testing this by adding a button that triggers the 'as' command, so I can 'see' the status at anytime. When I query the M1 again the results don't match the actual state.
 
Ok,

That is odd. I would call Elk. They should be able to help shed some more light on this.

--
Jayson

iostream212 said:
Ok so I send a disarm command and get: 1EAS000000001111111100000000000E

Looks good. I send an stay instant command and the speaker confirms 'area 1 is armed stay instant mode',
and yet when I query I get: 1EAS000000001111111100000000000E. Doesn't matter if it is a second later or 5 minutes later.

Now I disarm, the speaker confirms 'area 1 is disarmed.' I query and get : 1EAS3000000041111111000000000008

;)

* Note : I am testing this by adding a button that triggers the 'as' command, so I can 'see' the status at anytime. When I query the M1 again the results don't match the actual state.
Click to expand...
 
Ok good. So maybe I'm not crazy. Thanks for looking into this jaysonc! Seeing that beautiful code post only make me wish I had an iPhone / iTouch. ;) I'll just send a email to Elk and see what they say. Maybe its a bug. If so I will post when they respond.
 
Ok so now everything is working properly. Elk support told me to make sure that I had the globals 35-40 enabled. The only ones in that group that I previously didn't have enabled were 'transmit event log' and 'transmit keypad keys'. Turns out these made all the difference in the world. Problem resolved! Thanks to CT and Elk!
 
You must log in or register to reply here.

Similar threads

J
Help with ideas to cross-communicate between OmniPro II and Elk M1G
Replies
4
Views
213
jcd
J
J
Elk M1XRF319 wireless zones acting opposite - READY=NOT READY and NOT READY=READY
Replies
11
Views
795
Sandpiper
Sandpiper
A
DSC 24-hour zone not calling central station when alarming
Replies
7
Views
977
apostolakisl
A
StarTrekDoors
PC Access 3.17.0.843 Update Release Notes
Replies
0
Views
4K
StarTrekDoors
StarTrekDoors
P
Controlling Keypad Backlighting/LED indicators via Rules?
Replies
1
Views
1K
Del91574
D
Back
Top