AXIS A1601 Network Door Controller

The network door controller can easily be connected to and powered by your existing IP network with no need for special cabling.

Each network door controller is an intelligent device that is easily mounted close to a door. It can power and control up to four readers.

To find Axis devices on the network and assign them IP addresses in Windows®, use AXIS IP Utility or AXIS Device Manager. Both applications are free and can be downloaded from axis.com/support.

For more information about how to find and assign IP addresses, go to How to assign an IP address and access your device.

1. Open a browser and enter the IP address or host name of the Axis device.

   If you do not know the IP address, use AXIS IP Utility or AXIS Device Manager to find the device on the network.

2. Enter the username and password. If you access the device for the first time, you must set the root password. See .

3. The device’s webpage opens in your browser. The start page is called the Overview page.

A network router allows products on a private network (LAN) to share a single connection to the internet. This is done by forwarding network traffic from the private network to the internet.

Most routers are pre-configured to stop attempts to access the private network (LAN) from the public network (internet).

If the Axis product is located on an intranet (LAN) and you want to make it available from the other (WAN) side of a NAT (Network Address Translator) router, turn on NAT traversal. With NAT traversal properly configured, all HTTP traffic to an external HTTP port in the NAT router is forwarded to the product.

How to turn on the NAT-traversal feature

• Go to Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced.

• Click Enable.

• Manually configure your NAT router to allow access from the internet.

The device password is the primary protection for your data and services. Axis devices do not impose a password policy as they may be used in various types of installations.

To protect your data we strongly recommend that you:

• Use a password with at least 8 characters, preferably created by a password generator.

• Don’t expose the password.

• Change the password at a recurring interval, at least once a year.

To access the Axis product, you must set the password for the default administrator user root. This is done in the Configure Root Password dialog, which opens when the product is accessed for the first time.

To prevent network eavesdropping, the root password can be set via an encrypted HTTPS connection, which requires an HTTPS certificate. HTTPS (Hypertext Transfer Protocol over SSL) is a protocol used to encrypt traffic between web browsers and servers. The HTTPS certificate ensures encrypted exchange of information. See HTTPS.

The default administrator user name root is permanent and cannot be deleted. If the password for root is lost, the product must be reset to the factory default settings. See Reset to factory default settings.

To set the password, enter it directly in the dialog.

The Overview page in the product’s web page shows information about the door controller’s name, MAC address, IP address, and firmware version. It also enables you to identify the door controller on the network.

The first time you access the Axis product, the Overview page will prompt you to configure the hardware, to set date and time, and to configure the network settings. For more information about configuring the system, see Configuration – step by step.

To return to the Overview page from the product’s other webpages, click Overview in the menu bar.

To open the product’s setup pages, click Setup in the top right-hand corner of the Overview page.

The Axis product can be configured by administrators. For more information about users and administrators, see Users.

1. Before you start using the access control system, you should complete the following setup steps:

2. If English is not your first language, you may want the product’s web page to use a different language. See Select a language.

3. Set the date and time. See Set the Date and Time.

4. Configure the network settings. See Configure the Network Settings.

5. Configure the door controller and connected devices such as readers, locks and request to exit (REX) devices. See Configure the hardware.

6. Verify the Hardware Connections. See Verify the Hardware Connections.

7. Configure cards and formats. See Configure cards and formats.

For information about maintenance recommendations, see Maintenance Instructions.

The default language of the product’s web page is English, but you can switch to any of the languages that are included in the product’s firmware. For information about the latest available firmware, see www.axis.com

You can switch languages in any of the product’s web pages.

To switch languages, click the language drop-down list and select a language. All the product’s web pages and help pages are displayed in the selected language.

To set the date and time of the Axis product, go to Setup > Date & Time.

• You can set the date and time in the following ways:

• Get the date and time from a network time protocol (NTP) server. See Get the Date and Time from a Network Time Protocol (NTP) Server.

• Set the date and time manually. See Set the Date and Time Manually.

• Get the date and time from the computer. See Get the Date and Time from the Computer.

Current controller time displays the door controller’s current date and time (24h clock).

The same options for date and time are also available in the System Options pages. Go to Setup > Additional Controller Configuration > System Options > Date & Time.

1. Go to Setup > Date & Time.

2. Select your Timezone from the drop-down list.

3. If daylight saving time is used in your region, select Adjust for daylight saving .

4. Select Synchronize with NTP.

5. Select the default DHCP address or enter the address of a NTP server.

6. Click Save.

7. When synchronizing with an NTP server, date and time are updated continuously because the data is pushed from the NTP server. For information about NTP settings, see NTP Configuration.
8. If you use a host name for the NTP server, a DNS server must be configured. See DNS Configuration.

1. Go to Setup > Date & Time.

2. If daylight saving time is used in your region, select Adjust for daylight saving .

3. Select Set date & time manually.

4. Enter the desired date and time.

5. Click Save.

6. When setting the date & time manually, date and time are set once and will not be updated automatically. This means that if the date or time needs to be updated, the changes must be made manually because there is no connection to an external NTP server.

1. Go to Setup > Date & Time.

2. If daylight saving time is used in your region, select Adjust for daylight saving .

3. Select Set date & time manually.

4. Click Sync now and save.

5. When using the computer time, date and time are synchronized with the computer time once and will not be updated automatically. This means that if you change the date or time on the computer you use to manage the system, you should synchronize again.

To configure the basic network settings, go to Setup > Network Settings or to Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Basic.

For more information about network settings, see Network.

You can connect readers, locks and other devices to the Axis product before you complete the hardware configuration. However, it will be easier to connect devices if you complete the hardware configuration first. This is because a hardware pin chart will be available when the configuration is complete. The hardware pin chart is a guide on how to connect devices to the pins and can be used as a reference sheet for maintenance. For maintenance instructions, see Maintenance Instructions.

• If configuring the hardware for the first time, select one of the following methods:

• Import a hardware configuration file. See How to import a hardware configuration file.

• Create a new hardware configuration. See Create a new hardware configuration.

The hardware configuration of the Axis product can be completed faster by importing a hardware configuration file.

By exporting the file from one product and importing it to others, you can make multiple copies of the same hardware setup without having to repeat the same steps over and over again. You can also store exported files as backups and use them to restore previous hardware configurations. For more information, see How to export a hardware configuration file.

1. To import a hardware configuration file:

2. Go to Setup > Hardware Configuration.

3. Click Import hardware configuration or, if a hardware configuration already exists, Reset and import hardware configuration.

4. In the file browser dialog that appears, locate and select the hardware configuration file (*.json) on your computer.

5. Click OK.

The hardware configuration of the Axis product can be exported to make multiple copies of the same hardware setup. You can also store exported files as backups and use them to restore previous hardware configurations.

1. To export a hardware configuration file:

2. Go to Setup > Hardware Configuration.

3. Click Export hardware configuration.

4. Depending on the browser, you may need to go through a dialog to complete the export.

   Unless otherwise specified, the exported file (*.json) is saved in the default download folder. You can select a download folder in the web browser’s user settings.

Follow the instructions according to your requirements:

• How to create a new hardware configuration without peripherals

• How to create a new hardware configuration for wireless locks

• How to create a new hardware configuration with elevator control (AXIS A9188)

1. Go to Setup > Hardware Configuration and click Start new hardware configuration.

2. Enter a name for the Axis product.

3. Select the number of connected doors and click Next.

4. Configure the door monitors (door position sensors) and locks according to your requirements and click Next. For more information about the available options, see How to configure door monitors and locks.

5. Configure the readers and REX devices that will be used and click Finish. For more information about the available options, see How to configure readers and REX devices.

6. Click Close or click the link to view the hardware pin chart.

When you have selected a door option in the new hardware configuration, you can configure the door monitors and locks.

1. If a door monitor will be used, select Door monitor and then select the option that matches how the door monitor circuits will be connected.

2. If the door lock shall lock immediately after the door has been opened, select Cancel access time once door is opened.

   If you want to delay the relock, set the time of the delay in milliseconds in Relock time.

3. Specify the door monitor time options or, if no door monitor will be used, the lock time options.

4. Select the options that match how the lock circuits will be connected.

5. If a lock monitor will be used, select Lock monitor and then select the options that match how the lock monitor circuits will be connected.

6. If the input connections from readers, REX devices, and door monitors shall be supervised, select Enable supervised inputs.

   For more information, see How to use supervised inputs.

• The following door monitor options are available:

• Door monitor – Selected by default. Each door has its own door monitor that, for example, will signal when the door has been forced open or open too long. Deselect if no door monitor will be used.

• • Open circuit = Closed door – Select if the door monitor circuit is normally open. The door monitor gives the door open signal when the circuit is closed. The door monitor gives the door closed signal when the circuit is open.

  • Open circuit = Open door – Select if the door monitor circuit is normally closed. The door monitor gives the door open signal when the circuit is open. The door monitor gives the door closed signal when the circuit is closed.

• Cancel access time once door is opened – Select to prevent tailgating. The lock will be locked as soon as the door monitor indicates that the door has been opened.

• The following door time options are always available:

• Access time – Set the number of seconds the door shall remain unlocked after access has been granted. The door remains unlocked until the door has been opened or until the set time has been reached. The door will lock when it closes regardless of whether the access time has expired or not.

• Long access time – Set the number of seconds the door shall remain unlocked after access has been granted. Long access time overrides the already set access time and will be enabled for users with long access time selected.

• Select Door monitor to make the following door time options available:

• Open too long time – Set the number of seconds the door is allowed to stay open. If the door is still open when the set time has been reached, the door open too long alarm is triggered. Set up an action rule to configure which action the open too long event shall trigger.

• Pre-alarm time – A pre-alarm is a warning signal that is triggered before the open too long time has been reached. It informs the administrator and warns, depending on how the action rule has been set up, the person entering the door that the door needs to be closed to avoid the door open too long alarm to go off. Set the number of seconds before the door open too long alarm is triggered the system shall give the pre-alarm warning signal. To disable the pre-alarm, set the pre-alarm time to 0.

1. Access granted – lock unlocks
2. Access time
3. No action taken – lock locks
4. Action taken (door opened) – lock locks or stays unlocked until door closes
5. Open too long time
6. Pre-alarm goes off
7. Pre-alarm time
8. Open too long-alarm goes off

For information about how to set up an action rule, see How to set up action rules.

• The following lock circuit options are available:

• Relay – Can only be used on one lock per door controller. If two doors are connected to the door controller, a relay can only be used on the lock of the second door.

• None – Only available for Lock 2. Select if only one lock will be used.

• The following lock monitor options are available for single-door configurations:

• Lock monitor – Select to make the lock monitor controls available. Then select the lock that shall be monitored. A lock monitor can only be used on double-lock doors and cannot be used if two doors are connected to the door controller.

• • Open circuit = Locked – Select if the lock monitor circuit is normally closed. The lock monitor gives the door unlocked signal when the circuit is closed. The lock monitor gives the door locked signal when the circuit is open.

  • Open circuit = Unlocked – Select if the lock monitor circuit is normally open. The lock monitor gives the door unlocked signal when the circuit is open. The lock monitor gives the door locked signal when the circuit is closed.

When you have configured the door monitors and locks in the new hardware configuration, you can configure the readers and request to exit (REX) devices.

1. If a reader will be used, select the checkbox and then select the options that match the reader’s communication protocol.

2. If a REX device such as a button, sensor, or push bar will be used, select the checkbox and then select the option that matches how the REX device’s circuits will be connected.

   If the REX signal does not influence door opening (for example for doors with mechanical handles or push bars), select REX does not unlock door.

3. If connecting more than one reader or REX device to the door controller, do the previous two steps again until each reader or REX device has the correct settings.

• The following reader options are available:

• Wiegand – Select for readers that use Wiegand protocols. Then select the LED control that is supported by the reader. Readers with single LED control usually toggle between red and green. Readers with dual LED control use different wires for the red and green LEDs. This means that the LEDs are controlled independently of each other. When both LEDs are on, the light appears to be amber. See the manufacturer’s information about which LED control the reader supports.

• OSDP, RS485 half duplex – Select for RS485 readers with half duplex support. See the manufacturer’s information about which protocol the reader supports.

• The following REX device options are available:

• Active low – Select if activating the REX device closes the circuit.

• Active high – Select if activating the REX device opens the circuit.

• REX does not unlock door – Select if the REX signal does not influence door opening (for example for doors with mechanical handles or push bars). The door forced open alarm will not be triggered as long as the user opens the door within the access time. Deselect if the door shall unlock automatically when the user activates the REX device.

Supervised inputs report on the status of the connection between the door controller and the door monitors. If the connection is interrupted, an event is activated.

1. To use supervised inputs:

2. Install end of line resistors on all the used supervised inputs. See the connection diagram on Supervised inputs.

3. Go to Setup > Hardware Reconfiguration and select Enable supervised inputs. You can also enable supervised inputs during the hardware configuration.

• The following function supports supervised inputs:

• Door monitor. See Door connector.

1. Go to Setup > Hardware Configuration and click Start new hardware configuration.

2. Enter a name for the Axis product.

3. In the list of peripherals, select a manufacturer for a wireless gateway.

4. If you want to connect a wired door, select the 1 Door checkbox and click Next. If no door is included, click Finish.

5. Depending on what lock manufacturer you got, proceed according to one of the bullets:

6. • ASSA Aperio: Click the link to view the hardware pin chart or click Close and go to Setup > Hardware Reconfiguration to complete the configuration, see Add Assa Aperio^TM doors and devices

   • SmartIntego: Click the link to view the hardware pin chart or click Click here to select wireless gateway and configure doors to complete the configuration, see How To Configure SmartIntego.

Before adding a wireless door to the system it needs to be paired with the connected Assa Aperio communication hub, using Aperio PAP (Aperio programming application tool).

To add a wireless door:

1. Go to Setup > Hardware Reconfiguration.

2. Under Wireless Doors and Devices click Add door.

3. In the Door name field: Enter a descriptive name.

4. In the ID field under Lock: Enter the six-character-long address of the device that you want to add. The device address is printed on the product label.

5. Optionally, under Door position sensor: Choose Built in door position sensor or External door position sensor.

6. Note

   If using an external door position sensor (DPS), make sure that the Aperio lock device has support for door handle state detection before configuring it.

7. Optionally, in the ID field under Door position sensor: Enter the six-character-long address of the device that you want to add. The device address is printed on the product label.

8. Click Add.

1. In the door controller’s web page, go to Setup > Hardware Configuration and click Start new hardware configuration.

2. Enter a name for the Axis product.

3. In the list of peripherals, select Elevator control to include an AXIS A9188 Network I/O Relay Module and click Next.

4. Enter a name for the connected reader.

5. Select the reader protocol that will be used and click Finish.

6. Click Network Peripherals to complete the configuration see How to add and setup network peripherals or click the link to go to the hardware pin chart.

1. Go to Setup > Network Periphals to add a device

2. Find your device(s) under Discovered devices.

3. Click Add this device

4. Enter a name for the device

5. Enter the AXIS A9188 username and password

6. Click Add.

1. Go to Setup > Network Periphals and click on the Added devices row.

2. Choose which I/Os and relays to set as floor.

3. Click Set as floor and enter a name.

4. Click Add.

When the hardware installation and configuration is complete, and anytime during the door controller’s lifetime, you can verify the function of the connected door monitors, Network I/O Relay Modules, locks and readers.

To verify the configuration and access the verification controls, go to Setup > Hardware Connection Verification.

• Door state – Verify the current state of the door monitor, door alarms and locks. Click Get current state.

• Lock – Manually trigger the lock. Both primary locks and secondary locks if there are any will be affected. Click Lock or Unlock.

• Lock – Manually trigger the lock to grant access. Only primary locks will be affected. Click Access.

• Reader: Feedback – Verify the reader feedback, for example sounds and LED signals, for different commands. Select the command and click Test. Which types of feedback that are available depends on the reader. For more information, see Reader feedback. See also the manufacturer’s instructions.

• Reader: Tampering – Get information about the last tampering attempt. The first tampering attempt will be registered when the reader is installed. Click Get last tampering.

• Reader: Card swipe – Get information about the last swiped card or other type of user token accepted by the reader. Click Get last credential.

• REX – Get information about the last time the request to exit (REX) device was pressed. Click Get last REX.

• Floor state – Verify the current state of the floor access. Click Get current state.

• Floor lock & unlock – Manually trigger the floor access. Both primary locks and secondary locks if there are any will be affected. Click Lock or Unlock.

• Floor access – Manually grant temporary access to the floor. Only primary locks will be affected. Click Access.

• Elevator Reader: Feedback – Verify the reader feedback, for example sounds and LED signals, for different commands. Select the command and click Test. Which types of feedback that are available depends on the reader. For more information, see Reader feedback. See also the manufacturer’s instructions.

• Elevator Reader: Tampering – Get information about the last tampering attempt. The first tampering attempt will be registered when the reader is installed. Click Get last tampering.

• Elevator Reader: Card swipe – Get information about the last swiped card or other type of user token accepted by the reader. Click Get last credential.

• REX – Get information about the last time the request to exit (REX) device was pressed. Click Get last REX.

The door controller has a few predefined commonly used card formats that you can use as they are or modify as required. You can also create custom card formats. Each card format has a different set of rules, field maps, for how the information stored on the card is organized. By defining a card format you tell the system how to interpret the information that the controller gets from the reader. For information about which card formats the reader supports, see the manufacturer’s instructions.

1. To enable card formats:

2. Go to Setup > Configure cards and formats.

3. Select one or more card formats that match the card format used by the connected readers.

1. To create new card formats:

2. Go to Setup > Configure cards and formats.

3. Click Add card format.

4. In the Add card format dialog, enter a name, a description, and the bit length of the card format. See Card format descriptions.

5. Click Add field map and enter the required information in the fields. See Field maps.

6. To add multiple field maps, repeat the previous step.

To expand an item in the Card formats list and view the card format descriptions and field maps, click .

To edit a card format, click and change the card format descriptions and field maps as required. Then click Save.

To delete a field map in the Edit card format or Add card format dialog, click

To delete a card format, click .

• Name (required) – Enter a descriptive name.

• Description – Enter additional information as desired. This information is only visible in the Edit card format and Add card format dialogs.

• Bit length (required) – Enter the bit length of the card format. This has to be a number between 1 and 1000000000.

• Name (required) – Enter the field map name unspaced, for example OddParity.

  Examples of common field maps include:

• • Parity – Parity bits are used for error detection. Parity bits are usually added to the beginning or end of a binary code string and indicate if the number of bits is even or odd.

  • EvenParity – Even parity bits make sure that there is an even number of bits in the string. The bits that have the value 1 are counted. If the count is already even, the parity bit value is set to 0. If the count is odd, the even parity bit value is set to 1, making the total count an even number.

  • OddParity – Odd parity bits make sure that there is an odd number of bits in the string. The bits that have the value 1 are counted. If the count is already odd, the odd parity bit value is set to 0. If the count is even, the parity bit value is set to 1, making the total count an odd number.

  • FacilityCode – Facility codes are sometimes used for verifying that the token matches the ordered end user credential batch. In legacy access control systems, the facility code was used for a degraded validation, allowing entry to every employee in the credential batch that had been encoded with a matching site code. This field map name, which is case sensitive, is required for the product to validate on facility code.

  • CardNr – The card number or user ID is what is most commonly validated in access control systems. This field map name, which is case sensitive, is required for the product to validate on card number.

  • CardNrHex – The card number binary data is encoded as hex-lowercase numbers in the product. It is primarily used for troubleshooting why you are not getting the expected card number from the reader.

• Range (required) – Enter the bit range of the field map, for example 1, 2–17, 18–33, and 34.

• Encoding (required) – Select the encoding type of each field map.

• • BinLE2Int – Binary data is encoded as integer numbers in little endian bit order. Integer means that it needs to be a whole number (no decimals). Little endian bit order means that the first bit is the smallest (least significant).

  • BinBE2Int – Binary data is encoded as integer numbers in big endian bit order. Integer means that it needs to be a whole number (no decimals). Big endian bit order means that the first bit is the biggest (most significant).

  • BinLE2Hex – Binary data is encoded as hex-lowercase numbers in little endian bit order. The hexadecimal system, also known as the base-16 number system, consists of 16 unique symbols: the numbers 0–9 and the letters a–f. Little endian bit order means that the first bit is the smallest (least significant).

  • BinBE2Hex – Binary data is encoded as hex-lowercase numbers in big endian bit order. The hexadecimal system, also known as the base-16 number system, consists of 16 unique symbols: the numbers 0–9 and the letters a–f. Big endian bit order means that the first bit is the biggest (most significant).

  • BinLEIBO2Int – Binary data is encoded in the same way as for BinLE2Int, but the card raw data is read with inverted byte order in a multiple-byte sequence before field maps are taken out to be encoded.

  • BinBEIBO2Int – Binary data is encoded like for BinBE2Int, but the card raw data is read with inverted byte order in a multiple-byte sequence before the field maps are taken out to be encoded.

For information about which field maps your card format uses, see the manufacturer’s instructions.

The Configure Services in the Setup page is used to access the set up for the external services that can be used with the door controller.

SmartIntego is a wireless solution that increases the number of doors a door controller can handle.

The following prerequisites needs to be met before proceeding with the SmartIntego configuration:

• A csv-file needs to be created. The csv-file contains information about what GatewayNode and doors that are used in your SmartIntego solution. The file is created in a standalone software provided by a SimonsVoss partner.

• The Hardware Configuration of SmartIntego has been done, see How to create a new hardware configuration for wireless locks.

1. Click Browse..., select the csv-file and click Upload file.

2. Select a GatewayNode and click Next.

3. A preview of the new configuration is shown. Disable the door monitors if needed.

4. Click Configure.

5. An overview of the doors included in the configuration is shown. Click Settings to configure each door individually.

1. Click Setup in the top menu.

2. Click Configure Services > Settings.

3. Click Re-configure.

4. Click Browse..., select the csv-file and click Upload file.

5. Select a GatewayNode and click Next.

6. A preview of the new configuration is shown. Disable the door monitors if needed.

7. Note

   The door monitor settings come from the imported CSV file. You shouldn't need to change this setting in a normal installation.

8. Click Configure.

9. An overview of the doors included in the configuration is shown. Click Settings to configure each door individually.

To keep the access control system running smoothly, Axis recommends regular maintenance of the access control system, including door controllers and connected devices.

• Do maintenance at least once a year. The suggested maintenance procedure includes, but is not limited to, the following steps:

• Make sure all the connections between the door controller and the external devices are secure.

• Verify all the hardware connections. See Verification Controls Doors.

• Verify that the system, including the connected external devices, functions correctly.

• • Swipe a card and test the readers, doors, and locks.

  • If the system includes REX devices, sensors or other devices, test them as well.

  • If activated, test the tampering alarms.

• If the results from any of the steps above indicate faults or unexpected behavior:

• • Test the signals of the wires using appropriate equipment and check if the wires or cables are damaged in any way.

  • Replace all damaged or faulty cables and wires.

  • Once the cables and wires have been replaced, verify all the hardware connections again. See Verification Controls Doors.

• If the door controller is not behaving as expected, see Troubleshooting and Maintenance for more information.

Events that occur in the system, for example when a user swipes a card or a REX device is activated, are logged in the event log.

• View the event log. See View the event log.

• Export the event log. See .

• Configure the event log. See Configure the event log.

To view logged events, go to Event Log.

To expand an item in the event log and view the event details, click .

Applying filters to the event log makes it easier to find specific events. To filter the list, select one or several event log filters and click Apply filters. For more information, see Event Log Filters.

As an administrator, you might have more interest in some events than others. Therefore, you can choose which events that shall be logged. For more information, see Event log options.

• You can narrow the scope of the event log by selecting one or several of the following filters:

• User – Filter on events that relates to a selected user.

• Door & floor – Filter on events that relates to a specific door or floor.

• Topic – Filter on event type.

• Date and time – Filter the event log by a date and time span.

The Configure event log page allows you to define which events shall be logged.

To define which events shall be included in the event log, go to Setup > Configure Event Logs.

• The following options for logging events are available:

• No logging – Disable event logging. The event will not be registered or included in the event log.

• Log for all sources – Enable event logging. The event will be registered and included in the event log.

The Event pages allow you to configure the Axis product to perform actions when different events occur. The set of conditions that defines how and when the action is triggered is called an action rule. If multiple conditions are defined, all of them must be met to trigger the action.

For more information about available triggers and actions, see the product’s built-in help.

This example describes how to set up an action rule to activate an output port when the door is forced open.

1. Go to Setup > Additional Controller Configuration > System Options > Ports & Devices > I/O Ports.

2. Select Output from the desired I/O Port Type drop-down list and enter a Name.

3. Select the I/O port’s Normal state and click Save.

4. Go to Events > Action Rules and click Add.

5. Select Door from the Trigger drop-down list.

6. Select Door Alarm from the drop-down list.

7. Select the desired door from the drop-down list.

8. Select DoorForcedOpen from the drop-down list.

9. Optionally, select a Schedule and Additional conditions. See below.

10. Under Actions, select Output Port from the Type drop-down list.

11. Select the desired output port from the Port drop-down list.

12. Set state Active.

13. Select Duration and Go to opposite state after. Then enter the desired duration of the action.

14. Click OK.

To use more than one trigger for the action rule, select Additional conditions and click Add to add additional triggers. When using additional conditions, all conditions must be met to trigger the action.

To prevent an action from being triggered repeatedly, a Wait at least time can be set. Enter the time in hours, minutes and seconds, during which the trigger should be ignored before the action rule can be activated again.

For more information, see the product’s built-in help.

The product can send messages to notify recipients about events and alarms. But before the product can send notification messages, you must define one or more recipients. For information about available options, see .

To add a recipient:

1. Go to Setup > Additional Controller Configuration > Events > Recipients and click Add.

2. Enter a descriptive name.

3. Select a recipient Type.

4. Enter the information needed for the recipient type.

5. Click Test to test the connection to the recipient.

6. Click OK.

Email recipients can be configured by selecting one of the listed email providers, or by specifying the SMTP server, port and authentication used by, for example, a corporate email server.

1. To set up an email recipient using one of the listed providers:

2. Go to Events > Recipients and click Add.

3. Enter a Name and select Email from the Type list.

4. Enter the email addresses to send emails to in the To field. Use commas to separate multiple addresses.

5. Select the email provider from the Provider list.

6. Enter the user ID and password for the email account.

7. Click Test to send a test email.

To set up an email recipient using for example a corporate email server, follow the instructions above but select User defined as Provider. Enter the email address to appear as sender in the From field. Select Advanced settings and specify the SMTP server address, port and authentication method. Optionally, select Use encryption to send emails over an encrypted connection. The server certificate can be validated using the certificates available in the Axis product. For information on how to upload certificates, see Certificates.

Schedules can be used as action rule triggers or as additional conditions. Use one of the predefined schedules or create a new schedule as described below.

To create a new schedule:

1. Go to Setup > Additional Controller Configuration > Events > Schedules and click Add.

2. Enter a descriptive name and the information needed for a daily, weekly, monthly or yearly schedule.

3. Click OK.

To use the schedule in an action rule, select the schedule from the Schedule drop-down list in the Action Rule Setup page.

Recurrences are used to trigger action rules repeatedly, for example every 5 minutes or every hour.

To set up a recurrence:

1. Go to Setup > Additonal Controller Configuration > Events > Recurrences and click Add.

2. Enter a descriptive name and recurrence pattern.

3. Click OK.

To use the recurrence in an action rule, first select Time from the Trigger drop-down list in the Action Rule Setup page and then select the recurrence from the second drop-down list.

To modify or remove recurrences, select the recurrence in the Recurrences List and click Modify or Remove.

Readers use LEDs and beepers to send feedback messages to the user (the person accessing or trying to access the door). The door controller can trigger a number of feedback messages, some of which are preconfigured in the door controller and supported by most readers.

Readers have different LED behaviors, but typically they use different sequences of steady lights and flashing lights in red, green, and amber.

Readers can also use one-pitch beepers to send messages, using different sequences of short and long beeper signals.

The table below shows the events that are preconfigured in the door controller to trigger reader feedback and their typical reader feedback signals. Feedback signals for AXIS readers are presented in the Installation Guide supplied with the AXIS reader.

1. Idle state is entered when the door is closed and the lock is locked.

Feedback messages other than the above must be configured by a client such as an access management system, through the VAPIX® application programming interface, that supports this feature and use readers that can provide the required signals. For more information, see the user information supplied by the access management system developer and reader manufacturer.

User access control is enabled by default and can be configured under Setup > Additional Controller Configuration > System Options > Security > Users. An administrator can set up other users by giving them user names and passwords.

The user list displays authorized users and user groups (access levels):

• Administrators have unrestricted access to all settings. The administrator can add, modify and remove other users.

Under HTTP/RTSP Password Settings, select the type of password to allow. You may need to allow unencrypted passwords if there are viewing clients that do not support encryption, or if you upgraded the firmware and existing clients support encryption but need to log in again and be configured to use this functionality.

ONVIF is an open industry forum that provides and promotes standardized interfaces for effective interoperability of IP-based physical security products.

By creating a user you automatically enable ONVIF communication. Use the user name and password with all ONVIF communication with the product. For more information see www.onvif.org

IP address filtering is enabled on the Setup > Additional Controller Configuration > System Options > Security > IP Address Filter page. Once enabled, the listed IP address are allowed or denied access to the Axis product. Select Allow or Deny from the list and click Apply to enable IP address filtering.

The administrator can add up to 256 IP address entries to the list (a single entry can contain multiple IP addresses).

HTTPS (HyperText Transfer Protocol over Secure Socket Layer, or HTTP over SSL) is a web protocol providing encrypted browsing. HTTPS can also be used by users and clients to verify that the correct device is being accessed. The security level provided by HTTPS is considered adequate for most commercial exchanges.

The Axis product can be configured to require HTTPS when administrators log in.

To use HTTPS, an HTTPS certificate must first be installed. Go to Setup > Additional Controller Configuration > System Options > Security > Certificates to install and manage certificates. See Certificates.

To enable HTTPS on the Axis product:

1. Go to Setup > Additional Controller Configuration > System Options > Security > HTTPS

2. Select an HTTPS certificate from the list of installed certificates.

3. Optionally, click Ciphers and select the encryption algorithms to use for SSL.

4. Set the HTTPS Connection Policy for the different user groups.

5. Click Save to enable the settings.

To access the Axis product via the desired protocol, in the address field in a browser, enter https:// for the HTTPS protocol and http:// for the HTTP protocol.

The HTTPS port can be changed on the System Options > Network > TCP/IP > Advanced page.

IEEE 802.1X is a standard for port-based Network Admission Control providing secure authentication of wired and wireless network devices. IEEE 802.1X is based on EAP (Extensible Authentication Protocol).

To access a network protected by IEEE 802.1X, devices must be authenticated. The authentication is performed by an authentication server, typically a RADIUS server, examples of which are FreeRADIUS and Microsoft Internet Authentication Service.

In Axis implementation, the Axis product and the authentication server identify themselves with digital certificates using EAP-TLS (Extensible Authentication Protocol - Transport Layer Security). The certificates are provided by a Certification Authority (CA). You need:

• a CA certificate to authenticate the authentication server.

• a CA-signed client certificate to authenticate the Axis product.

To create and install certificates, go to Setup > Additional Controller Configuration > System Options > Security > Certificates. See Certificates.

To allow the product to access a network protected by IEEE 802.1X:

1. Go to Setup > Additional Controller Configuration > System Options > Security > IEEE 802.1X.

2. Select a CA Certificate and a Client Certificate from the lists of installed certificates.

3. Under Settings, select the EAPOL version and provide the EAP identity associated with the client certificate.

4. Check the box to enable IEEE 802.1X and click Save.

Certificates are used to authenticate devices on a network. Typical applications include encrypted web browsing (HTTPS), network protection via IEEE 802.1X and notification messages for example via email. Two types of certificates can be used with the Axis product:

Server/Client certificates

To authenticate the Axis product. A Server/Client certificate can be self-signed or issued by a Certificate Authority (CA). A self-signed certificate offers limited protection and can be used before a CA-issued certificate has been obtained.

CA certificates

To authenticate peer certificates, for example the certificate of an authentication server in case the Axis product is connected to an IEEE 802.1X protected network. The Axis product is shipped with several preinstalled CA certificates.

1. Go to Setup > Additional Controller Configuration > System Options > Security > Certificates.

2. Click Create self-signed certificate and provide the requested information.

1. Create a self-signed certificate, see How to create a self-signed certificate.

2. Go to Setup > Additional Controller Configuration > System Options > Security > Certificates.

3. Click Create certificate signing request and provide the requested information.

4. Copy the PEM-formatted request and send to the CA of your choice.

5. When the signed certificate is returned, click Install certificate and upload the certificate.

1. Go to Setup > Additional Controller Configuration > System Options > Security > Certificates.

2. Click Install certificate and upload the certificate.

The Axis product supports IP version 4 (IPv4) and IP version 6 (IPv6).

• The Axis product can get an IP address in the following ways:

• Dynamic IP address – Obtain IP address via DHCP is selected by default. This means that the Axis product is set to get the IP address automatically via Dynamic Host Configuration Protocol (DHCP).

  DHCP allows network administrators to centrally manage and automate the assignment of IP addresses.

• Static IP address – To use a static IP address, select Use the following IP address and specify the IP address, subnet mask and default router. Then click Save.

DHCP should only be enabled when using dynamic IP address notification, or if the DHCP can update a DNS server that makes it possible to access the Axis product by name (host name).

If DHCP is enabled and the product cannot be accessed, run AXIS IP Utility to search the network for connected Axis products, or reset the product to the factory default settings and then perform the installation again. For information about how to reset to factory default, see Reset to factory default settings.

AVHS used in conjunction with an AVHS service, provides easy and secure Internet access to controller management and logs accessible from any location. For more information and help to find a local AVHS Service Provider go to www.axis.com/hosting

The AVHS settings are configured under Setup > Additional Controller Configuration > System Options > Network > TCP IP > Basic. The possibility to connect to an AVHS service is enabled by default. To disable, clear the Enable AVHS box.

One-click enabled

Press and hold the product’s control button (see Product overview) for about 3 seconds to connect to an AVHS service over the Internet. Once registered, Always will be enabled and the Axis product stays connected to the AVHS service. If the product is not registered within 24 hours from when the button is pressed, the product will disconnect from the AVHS service.

Always

The Axis product will constantly attempt to connect to the AVHS service over the Internet. Once registered, the product will stay connected to the service. This option can be used when the product is already installed and it is not convenient or possible to use the one-click installation.

AXIS Internet Dynamic DNS Service assigns a host name for easy access to the product. For more information, see www.axiscam.net

To register the Axis product with AXIS Internet Dynamic DNS Service, go to Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Basic. Under Services, click the AXIS Internet Dynamic DNS Service Settings button (requires access to the Internet). The domain name currently registered at AXIS Internet Dynamic DNS service for the product can at any time be removed.

DNS (Domain Name Service) provides the translation of host names to IP addresses. The DNS settings are configured under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced.

Select Obtain DNS server address via DHCP to use the DNS settings provided by the DHCP server.

To make manual settings, select Use the following DNS server address and specify the following:

Domain name

Enter the domain(s) to search for the host name used by the Axis product. Multiple domains can be separated by semicolons. The host name is always the first part of a fully qualified domain name, for example, myserver is the host name in the fully qualified domain name myserver.mycompany.com where mycompany.com is the domain name.

Primary/Secondary DNS server

Enter the IP addresses of the primary and secondary DNS servers. The secondary DNS server is optional and will be used if the primary is unavailable.

NTP (Network Time Protocol) is used to synchronize the clock times of devices in a network. The NTP settings are configured under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced.

Select Obtain NTP server address via DHCP to use the NTP settings provided by the DHCP server.

To make manual settings, select Use the following NTP server address and enter the host name or IP address of the NTP server.

The Axis product can be accessed using a host name instead of an IP address. The host name is usually the same as the assigned DNS name. The host name is configured under Setup > Additional Controller Configuration> System Options > Network > TCP/IP > Advanced.

Select Obtain host name via IPv4 DHCP to use host name provided by the DHCP server running on IPv4.

Select Use the host name to set the host name manually.

Select Enable dynamic DNS updates to dynamically update local DNS servers whenever the Axis product’s IP address changes. For more information, see the online help.

Link-Local Address is enabled by default and assigns the Axis product an additional IP address which can be used to access the product from other hosts on the same segment on the local network. The product can have a Link-Local IP and a static or DHCP-supplied IP address at the same time.

This function can be disabled under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced.

The HTTP port used by the Axis product can be changed under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced. In addition to the default setting, which is 80, any port in the range 1024–65535 can be used.

The HTTPS port used by the Axis product can be changed under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced. In addition to the default setting, which is 443, any port in the range 1024–65535 can be used.

To enable HTTPS, go to Setup > Additional Controller Configuration > System Options > Security > HTTPS. For more information, see HTTPS.

A network router allows devices on a private network (LAN) to share a single connection to the internet. This is done by forwarding network traffic from the private network to the “outside”, that is, the internet. Security on the private network (LAN) is increased since most routers are pre-configured to stop attempts to access the private network (LAN) from the public network (internet).

Use NAT traversal when the Axis product is located on an intranet (LAN) and you wish to make it available from the other (WAN) side of a NAT router. With NAT traversal properly configured, all HTTP traffic to an external HTTP port in the NAT router is forwarded to the product.

NAT traversal is configured under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced.

Enable/Disable

When enabled, the Axis product attempts to configure port mapping in a NAT router on your network, using UPnP. Note that UPnP must be enabled in the product (see Setup > Additional Controller Configuration > System Options > Network > UPnP).

Use manually selected NAT router

Select this option to manually select a NAT router and enter the IP address for the router in the field. If no router is specified, the product automatically searches for NAT routers on your network. If more than one router is found, the default router is selected.

Alternative HTTP port

Select this option to manually define an external HTTP port. Enter a port in the range 1024–65535. If the port field is empty or contains the default setting, which is 0, a port number is automatically selected when enabling NAT traversal.

The FTP server running in the Axis product enables upload of new firmware, user applications, etc. The FTP server can be disabled under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced.

The RTSP server running in the Axis product allows a connecting client to start an event stream. The RTSP port number can be changed under Setup > Additional Controller Configuration > System Options > Network > TCP/IP > Advanced. The default port is 554.

SOCKS is a networking proxy protocol. The Axis product can be configured to use a SOCKS server to reach networks on the other side of a firewall or proxy server. This functionality is useful if the Axis product is located on a local network behind a firewall, and notifications, uploads, alarms, etc need to be sent to a destination outside the local network (for example the Internet).

SOCKS is configured under Setup > Additional Controller Configuration > System Options > Network > SOCKS. For more information, see the online help.

QoS (Quality of Service) guarantees a certain level of a specified resource to selected traffic on a network. A QoS-aware network prioritizes network traffic and provides a greater network reliability by controlling the amount of bandwidth an application may use.

The QoS settings are configured under Setup > Additional Controller Configuration > System Options > Network > QoS. Using DSCP (Differentiated Services Codepoint) values, the Axis product can mark event/alarm traffic and management traffic.

The Simple Network Management Protocol (SNMP) allows remote management of network devices. An SNMP community is the group of devices and management station running SNMP. Community names are used to identify groups.

To enable and configure SNMP in the Axis product, go to the Setup > Additional Controller Configuration > System Options > Network > SNMP page.

Depending on the level of security required, select the version on SNMP to use.

Traps are used by the Axis product to send messages to a management system on important events and status changes. Check Enable traps and enter the IP address where the trap message should be sent and the Trap community that should receive the message.

Traps for SNMP v1/v2 are used by the Axis product to send messages to a management system on important events and status changes. Check Enable traps and enter the IP address where the trap message should be sent and the Trap community that should receive the message.

The following traps are available:

• Cold start

• Warm start

• Link up

• Authentication failed

SNMP v3 provides encryption and secure passwords. To use traps with SNMP v3, an SNMP v3 management application is required.

To use SNMP v3, HTTPS must be enabled, see HTTPS. To enable SNMP v3, check the box and provide the initial user password.

The Axis product includes support for UPnP^®. UPnP is enabled by default and the product is automatically detected by operating systems and clients that support this protocol.

UPnP can be disabled under Setup > Additional Controller Configuration > System Options > Network > UPnP.

The Axis product includes support for Bonjour. Bonjour is enabled by default and the product is automatically detected by operating systems and clients that support this protocol.

Bonjour can be disabled under Setup > Additional Controller Configuration > System Options > Network > Bonjour.

The auxiliary connector provides four configurable input and output ports for connection of external devices.

The external connector provides two configurable input and output ports for connection of external devices.

You can configure the I/O ports under Setup > Additional Controller Configuration > System Options > Ports & Devices > I/O Ports. Select the port direction (Input or Output). You can give the ports descriptive names and their Normal states can be configured as Open circuit or Grounded circuit.

The list on the System Options > Ports & Devices > Port Status page shows the status of the product’s input and output ports.

The Axis product provides several maintenance functions. These are available under Setup > Additional Controller Configuration > System Options > Maintenance.

Click Restart to perform a correct restart if the Axis product is not behaving as expected. This will not affect any of the current settings.

Click Restore to reset most settings to the factory default values. The following settings are not affected:

• the boot protocol (DHCP or static)

• the static IP address

• the default router

• the subnet mask

• the system time

• the IEEE 802.1X settings

Click Default to reset all settings, including the IP address, to the factory default values. This button should be used with caution. The Axis product can also be reset to factory default using the control button, see Reset to factory default settings.

For information about firmware upgrade, see How to upgrade the firmware.

The Setup > Additional Controller Configuration > System Options > Support > Support Overview page provides information on troubleshooting and contact information, should you require technical assistance.

See also Troubleshooting.

To get an overview of the Axis product’s status and settings, go to Setup > Additional Controller Configuration > System Options > Support > System Overview. Information that can be found here includes firmware version, IP address, network and security settings, event settings, and recent log items.

The Setup > Additional Controller Configuration > System Options > Support > Logs & Reports page generates logs and reports useful for system analysis and troubleshooting. If contacting Axis Support, please provide a server report with your query.

System Log

Provides information about system events.

Access Log

Lists all failed attempts to access the product. The access log can also be configured to list all connections to the product (see below).

View Server Report

Provides information about the product status in a pop-up window. The access log is automatically included in the server report.

Download Server Report

Creates a .zip file that contains a complete server report text file in UTF–8 format. Select the Include snapshot from Live View option to include a snapshot of the product’s Live View. The .zip file should always be included when contacting support.

Parameter List

Shows the product's parameters and their current settings. This may prove useful when troubleshooting or when contacting Axis Support.

Connection List

Lists all clients that are currently accessing media streams.

Crash Report

Generates an archive with debugging information. The report takes several minutes to generate.

The log levels for the system and access logs are set under Setup > Additional Controller Configuration > System Options > Support > Logs & Reports > Configuration. The access log can be configured to list all connections to the product (select Critical, Warnings & Info).

Scripting allows experienced users to customize and use their own scripts.

Axis strongly recommends that you do not use this function unless you understand the consequences. Axis Support does not provide assistance for problems with customized scripts.

To open the Script Editor, go to Setup > Additional Controller Configuration > System Options > Advanced > Scripting. If a script causes problems, reset the product to its factory default settings, see Reset to factory default settings.

For more information, see www.axis.com/developer

Files, for example webpages and images, can be uploaded to the Axis product and used as custom settings. To upload a file, go to Setup > Additional Controller Configuration > System Options > Advanced > File Upload.

Uploaded files are accessed through http://<ip address>/local/<user>/<file name> where <user> is the selected user group (administrator) for the uploaded file.

To reset the product to the factory default settings:

1. Disconnect power from the product.

2. Press and hold the control button while reconnecting power. See Product overview.

3. Keep the control button pressed for 25 seconds until the status LED indicator turns amber for the second time.

4. Release the control button. The process is complete when the status LED indicator turns green. The product has been reset to the factory default settings. If no DHCP server is available on the network, the default IP address is 192.168.0.90.

5. Use the installation and management software tools, assign an IP address, set the password, and access the product.

It is also possible to reset parameters to factory default through the web interface. Go to Setup > Additional Controller Configuration > Setup > System Options > Maintenance and click Default.

Firmware is software that determines the functionality of network devices. One of your first actions when troubleshooting a problem should be to check the current firmware version. The latest version may contain a correction that fixes your particular problem.

The current firmware version in the Axis product is displayed in the Overview page.

1. Download the latest firmware file to your computer, available free of charge at www.axis.com/support

2. Go to Setup > Additional Controller Configuration > System Options > Maintenance in the product’s webpages.

3. Under Upgrade Server, click Choose file and locate the file on your computer.

4. If you want the product to automatically restore to factory default settings after the upgrade, check the Default checkbox.

5. Click Upgrade.

6. Wait approximately 5 minutes while the product is being upgraded and restarted. Then clear the web browser's cache.

7. Access the product.

Text marked with UL is only valid for UL 293 or UL 294 installations.

1. Relay is active when COM is connected to NO.

• The control button is used for:

• Resetting the product to factory default settings. See Reset to factory default settings.

RJ45 Ethernet connector with Power over Ethernet Plus (PoE+).

UL: Power over Ethernet (PoE) shall be supplied by a UL 294 listed Power over Ethernet IEEE 802.3af/802.3at Type 1 Class 3 or Power over Ethernet Plus (PoE+) IEEE 802.3at Type 2 Class 4 power limited injector that provides 44–57 V DC, 15.4 W / 30 W.  Power over Ethernet (PoE) has been evaluated by UL with AXIS T8133 Midspan 30 W 1-port.

Two 8–pin terminal blocks supporting both RS485 and Wiegand protocols for communication with the reader.

The specified power output values are shared between the two reader ports. It means that 486 mA at 12 V DC is reserved for all readers connected to the door controller.

Select which protocol to use in the product’s web page.

Configured for RS485

Configured for Wiegand

To use supervised inputs, install end of line resistors according to the diagram below.

i	Input
ii	0 V DC (-)

UL: Supervised inputs were not evaluated by UL for burglary use. Only door monitor and REX support supervision with end of line resistors.

Two 4-pin terminal blocks for door monitoring devices (digital input).

Door monitor supports supervision with end of line resistors. If the connection is interrupted, an alarm is triggered. To use supervised inputs, install end of line resistors. Use the connection diagram for supervised inputs. See .

Two 4-pin terminal blocks for form C relays that can be used, for example, to control a lock or an interface to a gate.

Relay power jumper

When the relay power jumper is fitted, it connects 12 V DC or 24 V DC to the relay COM pin.

It can be used to connect a lock between the GND and NO, or GND and NC pins.

1. The power is shared between the two relays and AUX I/O12 V DC.

Use the auxiliary connector with external devices in combination with, for example, motion detection, event triggering, and alarm notifications. In addition to the 0 V DC reference point and power (DC output), the auxiliary connector provides the interface to:

Digital input

For connecting devices that can toggle between an open and closed circuit, for example PIR sensors, door/window contacts, and glass break detectors.

Digital output

For connecting external devices such as relays and LEDs. Connected devices can be activated by the VAPIX® Application Programming Interface or from the product’s webpage.

6–pin terminal block

4-pin terminal block for external devices, for example glass break or fire detectors.

UL: The connector has not been evaluated by UL for burglar/fire alarm use.

2-pin terminal block for DC power input. Use a Safety Extra Low Voltage (SELV) compliant limited power source (LPS) with either a rated output power limited to ≤100 W or a rated output current limited to ≤5 A.

UL: DC power to be supplied by a UL 294, UL 293 or UL 603 listed power supply, depending on application, with appropriate ratings.

For a backup solution using a battery with built-in charger. 12 V DC input.

UL: The connector has not been evaluated by UL.

To reach the device’s web interface, type the device’s IP address in a web browser.

Time sync status

Shows NTP synchronization information, including if the device is in sync with an NTP server and the time remaining until the next sync.

Device info

Shows the device information, including AXIS OS version and serial number.

Date and time

The time format depends on the web browser’s language settings.

IPv4

IPv6

Hostname

DNS servers

HTTP and HTTPS

HTTPS is a protocol that provides encryption for page requests from users and for the pages returned by the web server. The encrypted exchange of information is governed by the use of an HTTPS certificate, which guarantees the authenticity of the server.

To use HTTPS on the device, you must install an HTTPS certificate. Go to System > Security to create and install certificates.

Network discovery protocols

One-click cloud connection

One-click cloud connection (O3C) together with an O3C service provides easy and secure internet access to live and recorded video from any location. For more information, see axis.com/end-to-end-solutions/hosted-services.

SNMP

The Simple Network Management Protocol (SNMP) allows remote management of network devices.

Connected clients

Shows the number of connections and connected clients.

Certificates

Network access control and encryption

Prevent brute-force attacks

Firewall

Custom signed AXIS OS certificate

Accounts

ALPN

MQTT client

MQTT publication

MQTT subscriptions

I/O ports

Use digital input to connect external devices that can toggle between an open and closed circuit, for example, PIR sensors, door or window contacts, and glass break detectors.

Use digital output to connect external devices such as relays and LEDs. You can activate connected devices through the VAPIX® Application Programming Interface or the web interface.

Reports and logs

Network trace

Remote system log

Syslog is a standard for message logging. It allows separation of the software that generates messages, the system that stores them, and the software that reports and analyzes them. Each message is labeled with a facility code, which indicates the software type generating the message, and assigned a severity level.