U-PROX IP400 Access Control Controller

Trademarks

ITV® and U-PROX® are registered trademarks of Limited Liability Company Integrated Technical Vision.

About This Document

This manual describes the installation, connection, and operation of the U-PROX IP400 access control system controller. Before installation, carefully study this manual. Controller specifications and parameters are described in the Specifications section. The Terms section explains terms used in this document.

The controller's appearance, contact descriptions, and operating modes are provided in the Description and Operation section. Installation, connection of external devices, and controller setup are described in the Local Network Operation Algorithm section.

Attention! Before installing and connecting the controller, carefully read this manual. Installation and connection of the controller are permitted only for persons or organizations authorized by the manufacturer.

Training and Technical Support

Training courses covering the installation and use of the U-PROX IP400 controller are conducted by "Limited Liability Company Integrated Technical Vision". For more information, contact "Limited Liability Company Integrated Technical Vision" personnel at the numbers listed below.

Technical support for all U-PROX products is available during business hours:

+38 (091) 481 01 69

support@u-prox.systems

https://t.me/u_prox_support_bot

This support is intended for trained specialists. End-users of "Limited Liability Company Integrated Technical Vision" products should contact their dealers or installers before contacting "Limited Liability Company Integrated Technical Vision".

Technical information is available on the website: www.u-prox.systems

Certification

"Limited Liability Company Integrated Technical Vision" declares that the U-PROX IP400 complies with the Electromagnetic Compatibility Directive 2014/30/EU and the Directive 2011/65/EU (RoHS). The original Declaration of Conformity is available on the website www.u-prox.systems in the Certificates section.

Controller Description

The U-PROX IP400 controller is a device designed for access control in residential and industrial premises, time tracking, and event logging. The controller is supplied in a housing with a power supply unit. The controller works with two readers connected via the Wiegand interface.

The U-PROX IP400 processes information from the reader(s) and controls actuators (e.g., locks, sirens) using four relays. The presence of eight additional inputs with various programming options allows for round-the-clock monitoring of eight security zones (with current control).

The controller can operate autonomously or as part of a network. The Ethernet interface (wired computer network) is used to connect controllers into an ACS network. The controller features network settings programming and firmware updates via a standard USB port (micro USB B). The controller is powered by a 12V source.

The U-PROX IP400 controller has advanced hardware capabilities and intelligent functions for controlling two doors with one reader and an exit request button (two single-door doors) or one door with two readers (double-door doors). A large non-volatile memory capacity allows the controller to be used for access control with up to 31,768 permanent employees and up to 1,000 visitors (temporary cards).

Thoughtful technical and design solutions, communication via Ethernet network, non-volatile memory and real-time clock, protection of communication ports and reader ports against short circuits, overvoltage, and reverse polarity – all this allows the controller to be used for building various access control and management systems.

Device Purpose

The U-PROX IP400 controller is designed to work as part of access control systems (ACS) of various scales, from small office ACS to checkpoints of large enterprises. In ACS, controllers are combined via a computer network.

The controller allows organizing access to two different rooms or one room, but with control of both entry and exit, as well as a signaling system for premises associated with these access points. In case of simultaneous control of entry and exit from a room, the "Anti-passback" function is provided.

Specifications

• Power supply - external 12V source: Current consumption from a 12V source (with loads disconnected) not exceeding 160 mA. DC power supply ripple amplitude not exceeding 500 mV.
• Ability to connect external readers of contactless identifiers operating in the Wiegand 26, 32, 34, 37, 40, 42, 56, 58, 64, 80-bit protocol.
• Eight inputs for connecting loops with current control (termination resistor – 2.2 kOhm).
• Two relays (NO, NC, COM contacts) 5 A @ 24 V.
• Two relays (NO, COM contacts) 1 A @ 24 V.
• One USB port for configuring network settings (for communication with the ACS server) and updating firmware via a standard USB port (micro USB B).
• Monitors the device enclosure opening.
• Ethernet port 10BASE-T/100BASE-TX.
• Full configuration is done using the ACS via the computer network.
• Real-time clock.
• Anti-passback function.
• Non-volatile memory: Identifiers: 31768, Events: 47000, Time zones: 250, Weekly schedules: 250, Holidays: 250, Temporary identifiers: 1000.

Terms

Identifiers

In access control systems, each user has an identifier with a unique code. Identifiers can be in the form of a plastic card, key fob, etc.

Reader

Readers are used to read identifier codes, which are connected to the ACS controller. There are several common types of identifiers and readers for them. When connecting to the controller, it is important that the interface type between the reader and the controller matches. The Wiegand interface is used to connect to the U-PROX IP400 controller.

PIN code

If readers have a built-in keypad, the identifier can be a code entered from the keypad. This code is usually called a PIN code; it can be a standalone identifier or an addition to a card or key fob, in which case, after presenting the card, the reader "waits" for the PIN code entry.

Door

A place, an access point, where access control is directly carried out (e.g., a door, turnstile, passage booth equipped with the necessary control means).

Access Point

See Door.

Passage Point

A passage point is a logical unit of the ACS that controls passage through a door in one direction and includes a reader, a controller (or part of a controller), and an actuator. Thus, a turnstile controlling passage in both directions constitutes two passage points, and a door with a reader on only one side is one passage point. Doors that consist of two passage points are called double-door, and doors that consist of one passage point are single-door.

Exit Request Button

For single-door access, an exit request button connected to the controller is used to exit the premises. Opening the door by any other means, such as pressing a button on an electric lock, using a key, etc., results in a "DOOR BREACH" event. The exit request button can also be used for remote door opening.

Passage Sensor (Door Contact)

A properly designed ACS must monitor the status of the passage point: the position of the door leaf, the turnstile barrier, the turnstile rotor, etc. This allows the ACS to prevent situations where several people pass through with the same identifier, or the door remains open after a user passes through, etc.

For this purpose, a magnetic door contact sensor, a turnstile rotor position sensor, or a barrier position sensor is connected to the controller input. The input to which these sensors are connected is called the passage sensor input (or door contact).

Anti-passback (AntiPassBack)

The controller has a built-in anti-passback function, which is necessary to prevent a situation where one user, having passed through a door controlled by the ACS in one direction, gives their identifier to another user. If this function is enabled, the controller tracks the identifier's position inside/outside. When attempting to pass again in the same direction, the ACS controller denies access and generates the message "ACCESS DENIED, ANTI-PASSBACK".

The anti-passback function can only be enabled if the controller manages double-door doors.

Global Anti-passback (AntiPassBack)

Tracking the movement of an identifier through all controlled doors. With global anti-passback, the facility is divided into access zones, passage through which is possible via several doors. In case of repeated passage attempts, unauthorized use of an identifier in these zones, ACS controllers deny access and generate the message "GLOBAL ANTI-PASSBACK: ACCESS DENIED".

Passage Time Interval

When the door contact is violated, the passage point enters the "Alarm" mode (see "Alarm" Mode below). An alarm does not activate if the contact is violated during the "Passage Time" interval. The interval begins when the controller allows the user to pass. The passage time is set during programming. The passage time also ends when the door contact is violated and then restored.

Identifier Guessing Attempt

The controller has a function that activates alarm mode if an identifier not registered in the system is presented several times in a row. Presenting a registered identifier resets the identifier guessing attempt counter. During controller programming, this function can be enabled and the number of presentations specified.

Schedules

When setting user access rights, time intervals and dates are specified for which passage is allowed. The controller can store up to 250 time intervals, and up to 250 weekly schedules can be created from these time intervals. Additionally, there are holidays that occur once a year; up to 250 such dates can be set in the controller.

Time Zones (Time Intervals)

A time zone is a component of a schedule and is used to organize time intervals and link them to access rights. They are used to check access rights and perform other functions based on schedules.

Loading

After programming inputs, outputs, access rights for identifier holders, and other controller parameters, the controller must be loaded. During loading, the configuration data is transferred from the computer to the controller.

Controller Structure

Figure 1 shows the external view of the device.

Figure 1. External view of U-PROX IP400

1. Device housing

2. Housing door

3. Tamper (opening sensor)

4. Controller

5. Power supply unit

Component Layout on the Controller Board

Figure 2 shows the location of jumpers, buttons, and removable connectors with terminals on the controller board and their purpose.

Figure 2. External view of the controller board

Reader connection

Controller Board Terminals

Current Mode

• Standby mode: TMP contacts closed (device enclosure closed).
• Configuration mode: Do not disconnect power, open the device enclosure (violate TMP).

Firmware Update Mode:

• Violate TMP: Open the device enclosure.
• Turn off the device.
• Apply power.
• Connect via USB (access is allowed for 10 seconds).

Reset to Factory Settings:

• Violate TMP: Open the device enclosure.
• Turn off the device.
• Set the FACT jumper.
• Apply power.
• Wait 40-50 seconds, or if readers are connected, wait for 6 short beeps indicating successful reset.

Controller Input/Output Assignment

Controller Operation Modes

Standby Mode

Standby mode is the primary operating mode of the controller. In this mode, the controller grants or denies access to identifier holders.

Passage Upon Identifier Presentation

For passage through the door, the user presents a contactless identifier to the reader. If the identifier is registered and passage is currently allowed, the door opens (the controller activates the actuator).

Passage Upon Presentation of Identifier and PIN Code

After presenting a registered identifier, the controller checks if a PIN code entry is required and, if so, prompts for PIN code entry. After entering the correct PIN code, the passage point opens (the actuator is activated).

Passage via Exit Request Button (Remote Door Opening)

For exiting a room with a single-door passage point or for admitting visitors, an exit request button is used. Pressing and releasing the exit request button opens the passage point (the actuator is activated).

Access Denial Upon Identifier Presentation

An identifier holder may be denied access for the following reasons:

• The controller is in an uninitialized state.
• The card is not registered in the controller.
• The card's validity period has expired.
• Access is currently or for the specified day of the week prohibited.
• Attempted re-entry with the "Anti-passback" function enabled.
• The presented identifier is registered as lost or blocked.
• The controller is in "Alarm" mode.
• The controller is in "Lock" mode.
• The validity period of the temporary card has not yet begun.
• The passage limit for a temporary card (visitor card) has been reached.

Alarm Mode

The passage point enters "Alarm" mode upon unauthorized passage (door breach), controller enclosure opening, identifier presentation, an identifier registered as lost, if the door is opened for too long (exceeding the door open time), or if the identifier guessing function is enabled.

In "Alarm" mode, the controller activates outputs designated as ALARM and SIREN. The alarm output remains active until the "Alarm" mode is disabled, and the SIREN output is programmed for a siren duration.

If a passage point is in "Alarm" mode, passage is blocked. The door can be opened by pressing the exit request button. "Alarm" mode can be deactivated by presenting an identifier with the "Disarm alarm" attribute or by a command from the computer.

Free Passage Mode

In ACS operation, there may be situations where it is necessary to open the door for free passage of people, for example, in case of fire, earthquake, or other emergency situations. For this purpose, the controller provides the "Free Passage" mode.

The passage point switches to "Free Passage" mode by operator command from the computer or by violating a loop designated as FREE PASSAGE. The passage point remains in "Free Passage" mode until the FREE PASSAGE loop is violated (if the loop is violated, the FREE PASSAGE state cannot be canceled by operator command).

The controller allows configuring a loop for the FREE PASSAGE function for passage point A, passage point B, or both passage points together (A+B).

Throughout the time the passage point is in "Free Passage" mode, the lock remains in the unlocked state. The controller registers identifier presentations, code entries, and logs them as "Access Granted", regardless of the anti-passback, schedule, etc. This is used to monitor the presence of personnel in the premises in case of an emergency.

For free passage when using locking devices with mechanical reset, it is essential to monitor the door status. Devices with mechanical reset unlock with a current pulse and remain unlocked until the door is closed. When the door is closed, the locking device returns to the locked state. The controller in "Free Passage" mode checks the door contact status and after each door closure, it sends an unlocking pulse to the lock.

When operating the controller without a door contact (magnetic contact), the "pulse" output type for unlocking the lock is not recommended. The "Free Passage" mode will not work correctly in this case; it is impossible to open the door without presenting an identifier.

Lock Mode

In case of a situation requiring blocking the door for all system users, the "Lock" mode is activated in the controller. If a passage point is in "Lock" mode, passage is allowed only to identifiers with the "Security Service" attribute. The door cannot be opened by pressing the exit request button.

The passage point switches to "Lock" mode by operator command from the computer or by violating a loop designated as LOCK. The passage point remains in "Lock" mode until the LOCK loop is violated (if the loop is violated, the LOCK state cannot be canceled by operator command).

The controller allows configuring a loop for the LOCK function for passage point A, passage point B, or both passage points together (A+B).

Identifier (Card) Properties

Code (Electronic Card Code)

Each card has its unique code, assigned during manufacturing. It consists of 10 hexadecimal digits.

PIN Code

An additional code assigned to the card. It must consist of only six decimal digits. It can be used with readers that have a built-in keypad. After presenting the card to the reader, the PIN code must be entered on the reader's keypad, followed by the '#' button. If the correct PIN code is entered, the controller unlocks the door and grants access. Otherwise, the controller will issue a warning signal, the event "Incorrect PIN code" will be logged, and the door will remain locked.

Expiration Date

The expiration date of the card.

Disarm Alarm

When presenting such a card to the door reader, if the door is in an alarm state, the controller registers the event "Alarm state ended" and returns the door to standby mode. If a card that does not have the "Disarm alarm" attribute is presented, the door remains in the same state, and the event "Passage denied. Alarm state." is logged.

Security Service

Right to pass through locked doors. If the door is in the "Lock" state, presenting a regular card results in logging the event "Passage denied. LOCK state." Presenting a card with the "Security Service" attribute grants access and logs the event "Passage granted. LOCK state."

VIP

Right to pass always and everywhere, except when the door is locked. A card with this attribute can be assigned any schedule, is not subject to anti-passback or expiration date limits. It can have a PIN code. If the door is in the "Lock" state, the controller does not grant access to an identifier with this attribute.

Anti-passback Disabled

Right to pass without considering anti-passback modes. Access to such a card will be granted regardless of the direction of previous passage, but taking into account the assigned schedule and other attributes assigned to the card.

Usage Variants and Output Modes

All controller outputs can be arbitrarily programmed for several usage variants: lock, siren, alarm, programmable output. Additionally, each output has a programmed operating mode: start-stop (the output remains active as long as the corresponding condition is met, for example, throughout the time the controller is in "Alarm" mode), pulse (the output is activated for a programmed time), trigger (the output is activated on the first event and deactivated on the next, etc.), continuous (the output is activated or deactivated by separate commands).

Communicator Operation

The U-PROX IP400 controller operates in automatic mode. After loading data from the server, it processes access rules for presented cards and sends notifications about access events to the server. The controller's communicator operates in notification mode, meaning that when an event occurs (passage, zone violation), data transmission to the ACS server is initiated.

The U-PROX IP400 controller can be connected to a computer network via a wired connection (Ethernet). In this case, operation within the local enterprise network (see Figure 3) and via the Internet (see Figure 4) is provided, allowing for the construction of distributed access systems of any scale.

Figure 3. Local network example

Figure 4. Distributed network example

When building a unified network of a central office and branches, it is recommended to use VPN technologies for additional protection, and routers with two different internet access channels for backup communication channels.

Local Network Operation Algorithm

1. After turning on the controller, it checks whether DHCP mode is enabled (device IP address 0.0.0.0) or if the device has received a static IP address.
2. If DHCP mode is enabled, the dynamic IP address assignment procedure will start.
3. Periodic update of the IP address status (continuation of the reserved IP address if DHCP mode is enabled).
4. Determination of the availability of the ACS server and the U-PROX IC A controller (by IP or DNS name).
5. Periodic sending of test signals.
6. Sending access event notifications.
7. Waiting for commands.

Internet Network Operation Algorithm (Wired Local Network)

1. After turning on the controller, it checks whether DHCP mode is enabled (device IP address 0.0.0.0) or if the device has received a static IP address.
2. If DHCP mode is enabled, the dynamic IP address assignment procedure will start.
3. Periodic update of the IP address status (continuation of the reserved IP address if DHCP mode is enabled).
4. Determination of Internet access possibility (availability of IP addresses of routers).
5. Determination of the availability of the ACS server and the U-PROX IC A controller (by IP or DNS name).
6. Periodic sending of test signals.
7. Sending access event notifications.
8. Waiting for commands.

Controller Auto-configuration in a Peer-to-Peer Network

The use of existing network infrastructure and standard network protocols (e.g., DHCP) allows implementing the "plug and play" principle. The auto-configuration mode for server addresses on devices significantly simplifies the deployment of the access control system (see Figure 5).

Figure 5. Device auto-configuration

Server Address Auto-configuration

1. After turning on the controller, it checks whether DHCP mode is enabled (device IP address 0.0.0.0) or if the device has received a static IP address.
2. If DHCP mode is enabled, the dynamic IP address assignment procedure will start.
3. If the ACS server address (IP or DNS name) is not set, the controller auto-configuration mode is activated:
1. The device sends out data packets announcing itself as a new device on the local network. Although this broadcast is widespread, it is limited to a peer-to-peer local network and active network equipment. Therefore, for networks with complex topology, ACS server IP addresses must be set manually.
2. Upon receiving a data packet from a new device, the system operator will receive a notification. The operator must then add the device to the database (DB).
3. After adding the device to the DB, the device receives a packet with a response from the ACS server. The server address is initialized in the controller's settings, and the broadcast transmission stops.
4. After configuring the controller parameters in the DB, the operator must load the device. The device will be linked to this ACS, which will prevent control interception.
5. To cancel controller binding, it should be reset to factory settings.
6. If the server address changes, the device will re-initiate auto-configuration, but data exchange will only be possible with the ACS to which the device was bound.

Global Anti-passback

The U-PROX IP400 controller can work as part of a global anti-passback system. In this case, the main controller of the U-PROX IC A series tracks the person's location based on passage through doors, receiving data from U-PROX IP400 controllers. The basis of global anti-passback operation is zone anti-passback. The facility's premises are divided into rooms – access zones. With this division, entering another zone is considered exiting the previous one. Passage to a zone is possible through different doors. The anti-passback controller tracks employee movement from zone to zone, receiving data from access controllers. This tracks the location of a person who may have multiple identifiers (see Figure 6).

Figure 6. Access zone distribution

Initially, the employee (person) has the status "Not defined" and only after the first presentation of the identifier to the reader is their location recorded by the U-PROX IC A controller.

The "Not defined" location is assigned during the registration of a new employee or after the system operator command "reset all locations".

The global anti-passback system allows preventing repeated passage, use of duplicate cards, unauthorized entry (unexpected appearance inside), transfer of identifiers to other persons, etc. (see Figure 7).

Figure 7. Violation tracking

If the connection with the ACS controller is lost, the door is breached, or the door enters free passage mode, etc., the anti-passback controller combines access zones into one, assuming that personnel may be present in both. When the door or controller connection is restored, the zones are separated. The actual location of personnel within them is determined by subsequent presentation of the identifier to the reader (see Figure 8).

Figure 8. Zone merging

If the connection with the U-PROX IC A controller is lost, U-PROX IP400 access controllers can be configured for two behavior options:

• Do not let anyone in.
• Allow passage according to the person's location data for local anti-passback.

Requirements for U-PROX IC A Controller Setup

The controller must have a static (fixed) IP address.

Requirements for U-PROX IP400 Controller Setup

• Global anti-passback involves only controllers for double-door doors (entry and exit by presenting an identifier).
• The primary ACS server address in the device's communication settings must be the address of the computer with U-PROX IP software.
• The secondary ACS server address in the device's communication settings must be the address of the U-PROX IC A controller.
• The "Global" anti-passback mode must be enabled for doors in U-PROX IP.
• The U-PROX IP access controller must specify the leading anti-passback controller and the reaction to loss of communication with it.

U-PROX IP400 controllers send access event notifications to two addresses simultaneously. The first address is the ACS server for displaying and storing events in the program database. The second address is the U-PROX IC A controller, which sends a command to deny or grant access in response. After presenting an identifier, the delay in granting or denying access can be up to 1 second, depending on the topology and network bandwidth.

Device Operation Procedure

The controller is supplied in a metal housing with a power supply unit. The overall dimensions of the device are shown in Figure 9.

Figure 9. Overall dimensions and mounting hole layout

Connection Procedure

1. Before installation, perform initial setup (i.e., set network parameters) of the controller using the "Configurator" utility via the USB port.
2. At the installation site, prepare for installation – mark and drill holes (see Installation Recommendations).
3. If necessary, provide power cable.
4. Provide cable for actuators (lock).
5. Install external readers and provide their cable connections.
6. Provide cable for sensors/buttons.
7. Provide Ethernet cable connection.
8. Lay mounting cables in the wall.
9. Install and secure the controller housing.
10. Connect the wires of the power supply unit, lock, reader, and controller inputs to the loops according to the sections below.
11. Connect the Ethernet cable to the port.
12. Close the cover and secure with a screw.
13. Connect the controller in the ACS software (according to the ACS manual).
14. Using the ACS, perform a full download (configuration of inputs, outputs, schedules, identifiers, etc.) of the controller.
15. The device is ready for operation.

Installation Recommendations

The controller should be placed in an easily accessible location for servicing. To install the controller on the wall, perform the following steps:

• Open the housing cover, place the housing against the intended mounting location, and mark the holes.
• Feed the wires through the holes in the housing.
• Secure the controller housing.
• Connect the wires.

External Reader Connection

The controller has two Wiegand interface ports for connecting readers. Various readers can work with the controller. Figure 10 shows an example of reader connection.

Figure 10. Reader connection

Wire color correspondence:

• White - data 1
• Green - data 0
• Blue - buzzer activation
• Brown - red indicator activation
• Orange - green indicator activation
• Black - GND
• Red - +12 V

Reader wire colors may vary depending on the manufacturer. Refer to the reader's operating manual for wire color correspondence. The current consumption of each external reader connected to the "+12V" terminals should not exceed 100mA. If high-range readers with a current consumption of over 100mA are connected to the controller, the power supply voltage for them must be provided from a separate source.

Loop Connection

The controller has eight inputs for connecting loops with current control. The purpose of each input is set during controller programming. Possible functions for inputs:

• Passage sensor (door contact)
• Exit request button
• Passage sensor (door contact) + exit request button
• Free passage (A, B, A+B)
• Locking (A, B, A+B)
• Sensor monitoring (alarm sensor)

The connection of different types of inputs is described below. After resetting the controller to factory settings, all loops are unassigned and not monitored. All loops work both on closing and opening. The use of termination resistors is mandatory.

Normal loop state - from 1.4 kOhm to 3 kOhm, short circuit (SC) of the loop - less than 1.4 kOhm, loop break - more than 3 kOhm.

Exit Request Button

The exit request button is used when passage through the door is controlled from only one side. Opening the door occurs when the exit request button is pressed and released. The exit request button can also be used as a button for remote door opening. For example, for manual door opening by a secretary or guard. Figure 11 shows an example of connecting normally open exit request buttons to contacts Z1 and Z2.

Figure 11. Exit request button connection

When programming, the correspondence is set as follows:

• Z1 – exit request button for passage point A
• Z2 – exit request button for passage point B

Using a button on the electric lock or a passage button on a turnstile to open the door results in a "DOOR BREACH" event. For correct operation, when programming, it is necessary to assign the connected loops as exit request button loops.

Passage Sensor (Door Contact)

Using the door contact, the controller determines the door status (open/closed) or the turnstile rotor position. If there is no door contact, the controller cannot detect unauthorized access or a situation where the door is held open for too long (passage of several people with one pass).

Figure 12 shows an example of connecting door contacts (normally closed) to inputs Z3 and Z4:

Figure 12. Door contact connection

When programming, the correspondence is set as follows:

• Z3 – door contact for passage point A
• Z4 – door contact for passage point B

Doors controlled by the access control system are recommended to be equipped with a door closer. For correct operation of the door contact, when programming, it is necessary to assign the connected loops as door contact loops.

The controller can operate without a door contact assigned. In this case, after presenting the identifier and granting access, the event "Passage occurred" is generated, the controller sends an unlocking pulse to the lock, and the passage time is counted.

Combined Loop - Exit Request Button and Passage Sensor (Door Contact)

Controller inputs can be configured for simultaneous use of the exit request button and the door contact. In this case, a loop break means a door contact violation, and a short press of the button means an exit request.

Figure 13 shows an example of connecting combined loops to inputs Z5 and Z6:

Figure 13. Combined loop connection

When programming, the correspondence is set as follows:

• Z5 – combined door contact and exit request button for passage point A
• Z6 – combined door contact and exit request button for passage point B

Any of the 8 inputs can be assigned as combined for servicing the door contact and the exit request button.

Integration with Fire and Security Alarm Systems

Thanks to the loops programmed as FREE PASSAGE and LOCK, the controller integrates fully into the fire and security alarm system (see Figure 14).

For joint operation with a fire alarm system, any loop must be programmed as "Free Passage". A fire alarm loop or the output of a fire alarm panel can be connected to this loop. When a fire alarm is triggered, the controller loop designated as "Free Passage" is violated, all doors controlled by the controller are automatically unlocked, and personnel can freely leave the fire zone.

Figure 14. Connection of lock and free passage loops

When programming, the correspondence is set as follows:

• Z7 - "Lock A+B"
• Z8 - "Free Passage A+B"

"Lock" can be assigned to passage points A, B, and A+B.

"Free Passage" can be assigned to passage points A, B, and A+B.

Zones of type Lock and Free Passage respond to both short circuit and open circuit.

For joint operation with a security alarm system, any loop must be programmed as "Lock". A security alarm loop or the output of a security alarm panel can be connected to this loop. When a security sensor is triggered or a security alarm is activated, the controller loop designated as "Lock" is violated, and all doors controlled by the controller are automatically locked. In this case, access to the protected premises will only be granted to the security service.

Actuators

To control actuators, the controller has four relays. Using the controller outputs, it can control an electric lock or bolt, manage a barrier or turnstile, or activate other auxiliary equipment.

Relays 1 and 2 have normally closed and normally open contacts. The relay contacts allow controlling actuators with a current consumption of up to 1A at 24V.

The use of diodes during the connection of actuators to an AC power supply is not allowed.

Voltage surges or drops during the simultaneous switching of all actuators should not cause controller malfunctions. Otherwise, a separate power source must be connected to power the actuators.

Electric Lock

The presence of normally closed and normally open relay contacts, as well as the ability to program the lock activation time within a wide range (from 1 to 255 seconds), allows the controller to manage almost any type of electric lock and bolt.

A special case is a time of 0. In this case, a pulse of 200 ms is applied to the relay.

Figure 15 shows an example of connecting actuators; the first is opened by applying voltage, the second by removing it.

Figure 15. Lock connection when using an external power supply

When using relay contacts to switch current through an inductive load, such as an electromagnetic lock, high-amplitude electrical pulses occur. To prevent damage to the relay contacts, inductive loads should be shunted with a diode connected inversely to the coil's supply voltage.

It should be noted that inexpensive electromagnetic bolts do not tolerate prolonged voltage application. For such bolts, the relay time should be programmed to prevent coil overheating.

For correct lock operation, when programming, it is necessary to assign the connected relay outputs as lock outputs.

Sirens and Bells

Electric bells (see Figure 16) are an inductive load for the voltage source. When connecting a bell to a DC voltage source, a protective diode is required (see warning about inductive load).

Figure 16. Electric bell connection

When connecting a siren, study the siren user manual. The siren's current consumption should not exceed 1 A.

When using non-standard actuators (magnetic starters, turnstiles, etc.), it is recommended to consult with your equipment supplier for connection advice.

For correct siren operation, when programming, it is necessary to assign the connected relay output as a siren output (alarm, etc.).

Communication

For communication with the ACS server, the U-PROX IP400 controller can use a wired computer network.

Device setup can be done via auto-configuration or manually from a PC using the "Configurator" software.

With appropriate configuration, the following is provided:

• Setting a static or dynamic (DHCP) IP address for the device.
• Operation with IP or DNS (computer domain name) address of the ACS server.

Wired Computer Network (Ethernet)

The Ethernet interface is used to connect system components (PCs and controllers) into a network. The length of an Ethernet cable without additional equipment can be up to 100 meters, providing a data transfer rate of up to 100 Mbit/s. Figure 17 shows examples of Ethernet cable connections.

Figure 17. Ethernet cable connection

Ethernet Communicator Setup

When configuring the controller's Ethernet communicator, perform the following:

• Controller network parameters setup (when using DHCP, they are not set):
  • IP address
  • Subnet mask
  • Gateway IP address (router) for Internet 1 (optional in a local network)
  • Gateway IP address (router) for Internet 2 (optional)
  • DNS server IP address 1 (if data transfer to a domain name is used)
  • DNS server IP address 2 (optional, if data transfer to a domain name is used)
• Communication setup with the server:
  • Server IP or DNS address 1
  • Server IP or DNS address 2 (U-PROX IC A address)
  • Access ports (read port and write port)
  • Channel check frequency (sending test signals)

Controller Programming Procedure

Service Maintenance

Reset to Factory Settings

To return the controller to factory settings, follow these steps:

1. Open the controller housing (violate TMP).
2. Disconnect power from the controller.
3. Install the FACT jumper.
4. Apply power.

Transition to Programming Mode

To switch the controller to programming mode, perform the following actions:

1. Without disconnecting power, open the controller housing (violate TMP).
2. Connect the USB cable to the connector and perform device setup using the "Configurator" software.

Device Firmware Replacement

1. Open the controller housing (violate TMP).
2. Disconnect power from the controller.
3. Install the FACT jumper.
4. Connect the USB cable first to the computer, and then to the controller.
5. Perform controller firmware replacement using specialized software.
6. After loading the software into the controller, wait at least 15-20 seconds (or if readers are connected, wait for six short beeps signaling successful firmware loading).

Attention! Firmware loading will only be allowed for the first 10 seconds after the controller starts.

Factory Settings

Communicator

DHCP enabled (controller IP not set), ACS server addresses not specified.

Inputs (Loops)

Z1 – Z8 – disconnected.

Outputs

Relay 1 – 4 - disconnected.

Readers

Wiegand 42bit.

Technical Maintenance and Repair

Warranty and post-warranty service for U-PROX IP400 controllers is performed by persons or organizations authorized by the manufacturer.

Warranty Obligations

The manufacturer guarantees that the U-PROX IP400 controller complies with the parameters described in this manual during the warranty storage period and the warranty operating period, provided that the storage and operating conditions specified in this manual are met.

Warranty storage period – 6 months from the date of manufacture.

Warranty operating period – 24 months from the moment of commissioning.

The supply of devices, personnel training, installation, commissioning, and warranty service of the U-PROX IP400 controller are carried out by the manufacturer or by organizations authorized by the manufacturer.

In case of commissioning work performed by an organization not authorized by the manufacturer, the consumer loses the right to warranty service.

Warranty repair is not carried out if the product fails due to:

• Incorrect connection.
• Non-compliance with the requirements of this manual.
• Mechanical damage.
• Force majeure.

The manufacturing company reserves the right to make changes to the product design that do not affect its main technical characteristics and reliability.