iDFace Max
The access controller iDFace Max has three types of custom signals: SecBox, internal relay and extension GPIOs. Each of these signals has its own particularities and customization possibilities to adapt to the most diverse needs.
SecBox
The Security Box (SecBox) is an External Drive Module (MAE) that connects to the iDFace Max via the four-pin connector on the back of the device.
These pins are used for the following functions:
| Pin | Color | Description |
|---|---|---|
| +12V | Red | Power supply +12V |
| A | Blue | Communication A |
| B | Blue/White | Communication B |
| GND | Black | Power supply ground |
SecBox offers a six-pin connector for external door/relay control, shown in the image below.
These six pins follow the following specification:
| Pin | Color | Description |
|---|---|---|
| DS | Purple | Door Sensor input |
| GND | Black | Ground (Common) |
| BT | Yellow | REX input |
| NC | Green | Normally Closed pin |
| COM | Orange | Common pin |
| NO | Blue | Normally Open pin |
SecBox Configuration
The external relay can be configured via API using the following parameters:
| Field | Type | Description |
|---|---|---|
| sec_box_out_mode | string | SecBox output mode: "0": Normal (Authorized) "1": Only Rejected "2": Bell "3": Alarm |
Each output mode set by sec_box_out_mode works as follows:
| Output mode | Value | Description |
|---|---|---|
| Normal (Authorized) | 0 | Triggers the SecBox when an action is performed that prompts normal authentication |
| Only Rejected | 1 | Triggers the SecBox when an action is performed that leads to a rejection of authentication on the device |
| Bell | 2 | Triggers the SecBox when an action is performed that activates the device's bell |
| Alarm | 3 | Triggers the SecBox when an action is performed that activates the device's alarm |
Example request for configuring the SecBox
The request must be made via the POST method to the /set_configuration.fcgi endpoint.
This request sets the output mode of the SecBox to operate in normal (authorized) mode:
$.ajax({
url: "/set_configuration.fcgi?session=" + session,
type: "POST",
contentType: "application/json",
data: JSON.stringify({
"general": {
"sec_box_out_mode": "0"
}
})
});
Internal relay
On the back of the iDFace Max you'll find a seven-pin connector.
This connector has the following pin configuration:
| Pin | Color | Description |
|---|---|---|
| GPIO1 | Yellow | Optional pin 1 |
| GPIO2 | Yellow | Optional pin 2 |
| GPIO3 | Yellow | Optional Pin 3 |
| GND | Black | Ground (Common) |
| NC | Green | Normally Closed pin |
| COM | Orange | Common pin |
| NO | Blue | Normally Open pin |
In addition to the external relay in the SecBox, iDFace Max has an internal relay that can be configured according to the needs of the installation. To access the internal relay, there are three important pins: NC, COM and NO. Using these three pins, you can attach an external module and trigger it according to the desired behavior.
Internal relay configuration
The internal relay can be configured via API using the following parameters:
| Field | Type | Description |
|---|---|---|
| relay_out_mode | string | Relay output mode: "0": Normal (Authorized) "1": Only Rejected "2": Bell "3": Alarm |
| relay1_enabled | string | "0": Relay disabled "1": Relay enabled |
| relay1_auto_close | string | "0": Auto close disabled "1": Auto close enabled |
| relay1_timeout | string | Timeout in milliseconds min: 100 max: 10000 |
Each output mode set by relay_out_mode works as follows:
| Output mode | Value | Description |
|---|---|---|
| Normal (Authorized) | 0 | Triggers the internal relay when an action is performed that prompts normal authentication |
| Only Rejected | 1 | Triggers the internal relay when an action is performed that leads to a rejection of authentication on the device |
| Bell | 2 | Triggers the internal relay when an action is performed that activates the device's bell |
| Alarm | 3 | Triggers the internal relay when an action is performed that activates the device's alarm |
Example request for configuring the internal relay
The request must be made via the POST method to the /set_configuration.fcgi endpoint.
This request enables the internal relay to operate in normal mode (authorized), with auto close enabled and opening timeout of 3 seconds:
$.ajax({
url: "/set_configuration.fcgi?session=" + session,
type: "POST",
contentType: "application/json",
data: JSON.stringify({
"general": {
"relay1_enabled": "1",
"relay_out_mode": "0",
"relay1_auto_close": "1",
"relay1_timeout": "3000"
}
})
});
Extension GPIOs
On the back of the iDFace Max you'll find a seven-pin connector.
This connector has the following pin configuration:
| Pin | Color | Description |
|---|---|---|
| GPIO1 | Yellow | Optional pin 1 |
| GPIO2 | Yellow | Optional pin 2 |
| GPIO3 | Yellow | Optional Pin 3 |
| GND | Black | Ground (Common) |
| NC | Green | Normally Closed pin |
| COM | Orange | Common pin |
| NO | Blue | Normally Open pin |
To extend the iDFace Max's operating possibilities, you can use the extension GPIOs. These consist of three pins: GPIO1, GPIO2 and GPIO3.
You can configure the individual behavior of these GPIOs, so that the device performs the desired action when it receives a signal via its respective pin.
Extension GPIOs configuration
The GPIOs can be configured via API using the following parameters.
| Field | Type | Description |
|---|---|---|
| gpio_ext1_mode gpio_ext2_mode gpio_ext3_mode |
string | Operation mode: "0": Disabled "1": Enable facial "2": Alarm "3": Emergency "4": Lockdown "5": Intercom "6": Interlock "7": Open relay "8": Open SecBox "9": Open relay/SecBox |
| gpio_ext1_idle gpio_ext2_idle gpio_ext3_idle |
string | Activation: "0": Active level 1, normally closed (NC) "1": Active level 0, normally open (NO) |
Each operation mode established by gpio_extN_mode (where N indicates the GPIO number) works as described in the table below.
Some signals are triggered by the end of the pulse, while others are triggered by the signal level. * Pulse: The expected operation cycle is: idle->active->idle. The action is executed on the falling edge of the pulse (i.e. active->idle transition). * Signal: The signal is expected to be supplied constantly. Active: executes the action continuously; idle: interrupts the action.
If the same operating mode is assigned to more than one GPIO, its operation will correspond to an OR logic, where at least one of the GPIOs needs to be activated for the respective operating mode to be executed. The Enable facial operating mode is an exception, because if more than one GPIO is configured as such, all those GPIOs must be activated for the functionality to take effect, corresponding to an AND logic.
| Operation mode | Value | Detection | Multiple GPIOs | Description |
|---|---|---|---|---|
| Disabled | "0" | --- | --- | GPIO does not perform any operations |
| Enable facial | "1" | Signal | AND logic | Activating the GPIO enables identification Identification remains disabled as long as GPIO is not active |
| Alarm | "2" | Pulse | OR logic | Activating the GPIO triggers the alarm |
| Emergency | "3" | Pulse | OR logic | Activating the GPIO puts the device into emergency mode |
| Lockdown | "4" | Pulse | OR logic | Activating the GPIO puts the device into lockdown mode |
| Intercom | "5" | Pulse | OR logic | Activating the GPIO connects the device to the configured SIP server |
| Interlock | "6" | Signal | OR logic | Activating the GPIO prevents the door from opening The door can receive commands to open normally while the GPIO is idle |
| Open relay | "7" | Pulse | OR logic | Activating the GPIO triggers the device's internal relay |
| Open SecBox | "8" | Pulse | OR logic | Activating the GPIO triggers the external relay in the SecBox |
| Open relay/SecBox | "9" | Pulse | OR logic | Activating the GPIO triggers the device's internal relay together with the SecBox's external relay |
Example request for configuring the extension GPIOs
The request must be made via the POST method to the /set_configuration.fcgi endpoint.
This request configures GPIO1 to open the relay with normally closed behavior, GPIO2 disabled and GPIO3 to open the SecBox with normally open behavior:
$.ajax({
url: "/set_configuration.fcgi?session=" + session,
type: "POST",
contentType: "application/json",
data: JSON.stringify({
"general": {
"gpio_ext1_mode": "7",
"gpio_ext1_idle": "0",
"gpio_ext2_mode": "0",
"gpio_ext3_mode": "8",
"gpio_ext3_idle": "1"
}
})
});