IS2000: HID: Global Lockdown

The following commands can be created and executed from a text file.  Create a text file in Notepad with the commands listed below and then copy the text file to the IS2000\Data\Drivers\x\Commands folder where x is the Driver ID.  The file name can be anything with a file extension of cm0 where 0 represents the prioritization of the order in which the command should get processed.

307 Door Strike Command (VertX / Edge)

This is how the 307 command should be used to change the state of a door strike:


CA = Controller address that the reader is connected to.  This can be a number from 0 to 255.

SCA = Sub-Controller address that the reader is connected to.  This can be a number from 0 to 31.

DN = Door Number identifies which of the 2 door strikes on the sub-controller will get affected by the command.  0 or 16 are the only 2 choices for this field where 0 is the first Door Strike, and 16 is the second Door Strike.

DSM = Door Strike Mode:  0-Locked, 1-Unlock, 2-Momentary Unlock

Here an example of the command line: 

307 4 0 16 2

In this example we are telling controller 4 to momentarily unlock the second door strike on sub-controller 0.

Below is a list of commands to unlock the first 6 doors (sub-controllers 0, 1, and 2) on Controller 4:

307 4 0 0 1
307 4 0 16 1
307 4 1 0 1
307 4 1 16 1
307 4 2 0 1
307 4 2 16 1

Executing a Command File from an Input (VertX / Edge)

To execute a command file from an Input event that has gone active, create a command file with the proper format as outlined above and save the file to the IS2000\Data\Drivers\x\Data folder where x is the Driver ID.

Next, create a file in the RemotePath called ‘CommandFileX.ini’, where X is the Driver ID that references the driver that is responsible for polling the events of the Input that will trigger the command file execution.  The ‘CommandFileX’ will contain the Input address as a section header followed by a File parameter that will reference the file to execute.  Below is a sample of what a CommandFileX.ini would look like:



In the example above, the command file ‘Test.cm1’ will get executed when Input 1.0.0.I16 goes active.  ‘Test.cm1’ must be properly formatted with the 307 commands and must be located in the IS2000\Data\Drivers\x\Data folder.  ‘CommandFileX.ini’ (where X is the Driver ID for the driver that is responsible for polling the input that will cause the trigger) must be located in the RemotePath.  Please note that multiple inputs can be added to the same ‘CommandFileX.ini’ file, and can be used to trigger the same or different command file(s).