manualshive.com logo in svg

Ness M1KAM, Quick Start Manual, Page: 6 / 6

Share
Download
Ness M1KAM Quick Start Manual Download Page 6

Page 6

Programming an Access Event from the NessRP Rules Engine

When an access credential (card, fob,) is read by a reader attached to a Keypad or M1KAM the Control immediately scans each of it's
programmed User Codes looking for a match to the code string.  If a match is found the control will produce an appropriate action
based on the authorization options for that particular User Code.  For example:

If the ARM option is enabled for that User Code the control will attempt to arm the area (partition).

If the DISARM option is enabled for that User Code the control will disarm the area (partition).

If the ACCESS option is enabled for that User Code the control will log an Access event and then scan for any Rules that may contain
an Access event.    IMPORTANT: No outputs or action will take place beyond the logging UNLESS a Whenever/And/Then rule has
been written to tell the control what it is supposed to do.  See the paragraph below concerning Whenever/And/Then Rules.

NOTE: 

It is possible for an access credential to Disarm the Control and unlock (Access) the door at the same time provided

the User Options for DISARM and ACCESS are both enabled.

Whenever/And/Then Rules

As mentioned above, an ACCESS event flag does not actually do anything (other than log) unless there has been a Whenever/And/
Then Rule written to tell the control what it is suppose to do.  Rules are written using the ElkRP Programming Software.  An Access
event can be used to create virtually any desired reaction.  i.e., turn on an output, a light, close/open a relay, etc.  The following is an
example of a rule designed to turn an output ON for 10 seconds whenever a valid credential (card, fob, iButton) is presented and
verified by the control.    The output might be wired to a door locking device which could unlock the door for 10 seconds.

WHENEVER ACCESS 'Keypad Name' (KP 2) IS TRIGGERED

THEN TURN Output 194 ON FOR 10 SECS

NOTE: NessRP will always use the reference of "KP" (for Keypad) followed by an address number (2 in this case) even if the
actual device at this address happens to be an M1KAM Access Module.  The actual Keypad Name can be custom programmed
to a more descriptive identity such as "Employee Entry" to help keeps things organized.

Ness Security Products

4/167 Prospect Hwy

Seven Hills, NSW, 2147

Australia

www.ness.com.au/m1

[email protected]

Sales offices :NSW - (02) 8825 9222, Vic (03) 9875 6400, Qld (07) 

3399

 

4910

, W.A. (08) 9

328

 

2511

, S.A. (08) 

8125

 

0000

[email protected]

Ness Doc No. 890-373

Summary of Contents for M1KAM

Page 1: ...nects to the 4 wire keypad data bus in place of a traditional M1 Keypad Since the maximum number of keypads on an M1 or M1EZ8 is 16 the maximum number of M1KAM modules and controlled doors is 16 minus any installed keypads Even though an M1 Keypad can accept a 26 bit access reader the M1KAM is a more powerful and less expensive access solution For example the M1KAM includes a relay door unlock out...

Page 2: ...Identification of the Relay Output on the M1KAM is based on the Data Bus Address of the M1KAM See Table 1 under Setting the Data Bus Address for more details 5 Install a proximity reader 26 BIT Wiegand compatible reader and connect it to the M1KAM as follows 26 Bit Wiegand Reader Requires a 4 wire connection 2 for power and 2 for data to the M1KAM Ideally the reader should be powered from the loca...

Page 3: ...Page 3 ...

Page 4: ...HO Time 20 Seconds 10 RTE Time 20 Seconds DHO Time 40 Seconds 01 RTE Time 30 Seconds DHO Time 60 Seconds 11 RTE Time 45 Seconds DHO Time 90 Seconds Enrolling the M1KAM with the control Once the address is set and the M1KAM powered up it will be necessary to manually ENROLL the new device so that the M1 Control knows it is present This is accomplished either from keypad programming Menu 1 Bus Modul...

Page 5: ...tial is rejected the Keypad will produce a low error tone and display Code Not Authorized Redo The most common causes for rejection are A The credential has already been enrolled duplicate codes are not allowed or B The facility code in the credential is not the same brand or is not compatible with the reader Some manufacturers credentials are not readable by other brands of readers 9 After the cr...

Page 6: ...CESS are both enabled Whenever And Then Rules As mentioned above an ACCESS event flag does not actually do anything other than log unless there has been a Whenever And Then Rule written to tell the control what it is suppose to do Rules are written using the ElkRP Programming Software An Access event can be used to create virtually any desired reaction i e turn on an output a light close open a re...

Reviews:

No comments