Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Arming ELK
#11
Bah. The chances of someone coming in and finding a code INSIDE CQC are far outweighed by them adding a small invisible button to disarm the system whenever they want, WITHOUT a code. Both require being able to get into Interface Editor, both require a bit of knowledge to the system.

Bad Elk, bad.

Russ...
Reply
#12
They'd have to have a CQC user name and password before they could that though.

But still, it's a wierd side effect and seems like something they should address.
Dean Roddey
Software Geek Extraordinaire
Reply
#13
The would need a user name/password to look through the forms for a disarm code too.

Russ...
Reply
#14
Dean, can't arm Elk M1 using V2 driver and the action below upon a UI push button.   The error message states the driver... ValueRejected

Thanks, Ken


Devices::FieldWrite
    P1=ElkM1.InvokeCmd
    P2=ArmArea:1, Stay, 003456
    P3=True
Reply
#15
(10-01-2017, 06:42 PM)KenC Wrote: Dean, can't arm Elk M1 using V2 driver and the action below upon a UI push button.   The error message states the driver... ValueRejected

Thanks, Ken


Devices::FieldWrite
    P1=ElkM1.InvokeCmd
    P2=ArmArea:1, Stay, 003456
    P3=True
Reply
#16
Opps....Fixed it....For "Area" I used the area ID number instead of the area name! Ken
Reply
#17
I'm in documentation update mode now. I'll check the docs and tweak them if they are not sufficiently clear on that.
Dean Roddey
Software Geek Extraordinaire
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)