Skip to main content

Control iD Integration

The integration with Control iD devices enables the use of facial recognition and biometric equipment in ACCELERO access control.

Licensing Requirement

This feature requires the Control ID module enabled in the license. See Licensing.

Overview​

The Control iD integration offers advanced identification features:

FeatureDescription
Facial Recognition (IDFace)Automatic synchronization of facial templates, with direct integration with the IDFace
Fingerprint BiometricsSynchronization of fingerprints
Compatibility with IDBlock turnstilesSupport for the IDBlock turnstile line
QRCodesSynchronization of QRCodes generated by ACCELERO (optional)
AdministratorsRegistration of users with administrative privileges on the devices
Photo CaptureUse of the devices to capture photos during registration
Architecture

The integration is done through ACCELERO/CONTROL ID communication gateways (IONGRADE product). The gateway bridges the ACCELERO servers and the Control iD devices.

Navigation path: Settings > ControlID

The Control ID screen groups the integration into four tabs: Devices, Gateway, Settings and Synchronize templates.

Homologated models

The list of approved models, the integration mode of each one (Direct × Neon Controller) and the minimum firmware live in a single place, the Homologated Equipment matrix. It is the official source; a model that is not listed there has not been approved.

Architecture and Requirements​

The integration with Control iD devices uses:

  1. ACCELERO/CONTROL ID Gateways (IONGRADE product)
  2. Control iD Devices (biometric and/or facial)
  3. ACCELERO Server with the module enabled

Data flow:

ACCELERO → Gateway → Control iD Devices
        ← Status ←

General Settings​

Path: Settings > ControlID > Settings

Settings tab of the Control iD integration, with the categories, the additional identifier types, the Synchronize QRCodes and Always identify users switches, the administrator categories and the Fingerprint Biometrics section

Main Parameters​

FieldDescription
Categories that must have facial recognitionDefines which categories will have facial templates generated and distributed.
Example: disable for temporary visitors
Additional identifier types to synchronizeIdentifier types (e.g., Permanente / PIN) sent to the devices in addition to the templates, for use on the built-in reader
Automatically remove templates for the following categoriesCategories whose templates are automatically deleted after passing through controllers with "Automatic visitor removal"
Except if the person has at least one of the following categoriesException categories - people with these categories will never have their templates removed automatically
Synchronize QRCodesEnables sending ACCELERO QRCodes to the Control iD devices
Categories to register as administratorPeople with these categories will be registered as administrators on the Control iD devices
Always identify usersCritical operation mode - defines how the system applies access rules
Rule for synchronizing fingerprint templates (Fingerprint Biometrics section)Defines which people have their fingerprint sent: Same settings as facial recognition (follows the categories above) or Synchronize all templates

QRCode Synchronization​

When to enable:

  • If you want to use QRCodes generated by ACCELERO on the Control iD readers
  • QRCodes can be sent to the devices for offline reading

Requirements:

  • QRCode format: Plain text
  • Numbering suitable for physical connections with controllers (usually Wiegand)

Configuration:

  1. Enable the "Synchronize QRCodes" flag
  2. Configure the QRCode format in Global Settings
  3. Check the Wiegand connection between Control iD and the controllers
When to Use

Useful for systems where visitors need to use QRCodes on the Control iD readers, keeping them working even in case of a network failure.

Categories as Administrator​

People registered as administrators on the Control iD devices have:

  • Access to special functions of the equipment
  • The possibility of performing local configurations
  • Effects on the equipment's operation mode

Usage example:

Categories as administrator: SECURITY, OPERATORS

Result:
- People with the SECURITY category: registered as admin
- People with the EMPLOYEES category: registered as normal users
Careful Use

Only configure as administrators the categories that really need privileged access to the devices. Avoid configuring overly broad categories.

"Always Identify Users" Mode​

This is a critical parameter that defines the behavior of the access control system.

✅ Enabled (Recommended)​

Behavior:

  • The person's ID is always transmitted to the controller via Wiegand
  • Access rules are applied by ACCELERO (server)
  • The person always sees "Access authorized" on the Control iD display
  • Access control centralized on the server

Advantages:

  • Centralized control of access policies
  • Complete logs in ACCELERO
  • Flexibility to change rules without reconfiguring devices
  • Consistency with other types of identifiers

When to use:

  • Whenever possible (recommended mode)
  • Systems with complex access policies
  • Need for centralized logs

❌ Disabled​

Behavior:

  • People are registered on the Control iD with their categories and time ranges
  • If the person is outside the schedule:
    • Control iD shows "Access denied"
    • The information is NOT transmitted to the controller via Wiegand
    • The event is NOT recorded in ACCELERO
  • If the person is within the schedule:
    • It works normally

Disadvantages:

  • Loss of logs of access attempts outside the schedule
  • Need to re-synchronize when changing time ranges
  • Decentralized control

When to use:

  • Only if a specific project requirement
  • Very simple systems without the need for complete logs
Recommendation

Always use "Always identify users" enabled, unless there is a specific project requirement that justifies otherwise.

Disabled mode results in loss of auditing and makes troubleshooting harder.

Registering Gateways​

Path: Settings > ControlID > Gateway

Click New gateway, fill in the fields below and click Add:

FieldDescription
Serial numberSerial number of the gateway (obtain from the physical equipment).
CRITICAL: The information must be correct or communication will fail
DescriptionName/description of the gateway

Gateway tab of the Control iD integration, with the add form open and one registered gateway

The list shows the Serial number and Description of each gateway. This screen does not show the communication status of the gateway or of the subordinate devices.

Registering Devices​

Path: Settings > ControlID > Devices

Click New device to add the device and then click the edit icon on its row to fill in all the fields:

Editing an IDFace Control iD device, with the network data, the gateway, photo capture, the physical channel, the area, the category filter and the virtual controller

FieldDescription
DescriptionName/location of the device
TypeControl iD device model: IDFlex, IDFace, IDBlock, IDBox or iDUHF
ActiveIf disabled, the device will not receive registration/deletion commands
IP addressIP of the device on the network
Communication portTCP port for communication
GatewayCommunication gateway to which the device is subordinate
UserUser for authentication on the device
PasswordAuthentication password. The field is locked when editing: click the icon next to it to change it
DeviceIDDevice identifier, required and unique among Control iD devices. The IDBox shows its ID in base 36 on its own screen; the system converts it to decimal when sending it to the gateway
Capture timeoutMaximum time (in seconds) that the registration screens will wait for the template to be returned after starting capture
Capture messageMessage displayed on the Control iD display during the capture process
Enable photo captureIf enabled, the device will appear as an option in the capture camera lists
Passage confirmationWhen off, the passage is recorded automatically when access is released. On the iDUHF the passage is always automatic
SecboxShown only for the IDFace type. Tells the gateway that the device works with the Secbox module
Associated physical channelChannel of the physical controller the device is wired to (only when there is a physical controller)
AreaDestination area controlled by the device
Synchronize only these categoriesAdditional filter of categories (in addition to the global filter). When empty (Synchronize all), it receives all of them
Associated virtual controllerVirtual controller through which the device queries ACCELERO (Direct mode). When empty (None), the device works through the physical controller
Double Category Filter

The category filter works on two levels:

  1. Global (Settings): Defines allowed categories in the system
  2. Per device: Further filters which categories go to that specific device

Only categories that pass both filters will be synchronized.

Photo/Template Capture​

Control iD devices can be used to capture templates during person registration.

Configuration:

  1. Enable "Enable photo capture"
  2. Configure "Capture timeout" (recommended: 30-60 seconds)
  3. Configure a custom message (e.g., "Position your face")

Capture flow:

  1. The operator starts the capture on the person registration screen
  2. Selects the Control iD device from the list
  3. The system sends a command to the device
  4. The message is displayed on the display
  5. The person positions themselves for capture
  6. The template is captured and sent to ACCELERO
  7. The photo/template is saved to the registration
Capture Timeout

Configure a timeout suitable for the environment:

  • 30 seconds: Experienced operators
  • 60 seconds: General use
  • 90+ seconds: Environments with slow traffic

How Synchronization Works​

Automatic Synchronization​

After the settings, synchronization happens automatically:

  1. When saving a person's registration:

    • The system checks whether the person has a category configured for facial recognition
    • If so, it generates a template from the first photo of the registration
    • It distributes the template to all active devices

  2. Visual indicators on the photo:

    • 🔴 Red icon: Templates not yet fully distributed
    • 🔵🔵 Two blue icons: Templates distributed successfully
Photo Quality

The first photo of the registration is always used for synchronization. Make sure:

  • ✓ Good capture quality
  • ✓ Good lighting
  • ✓ Frontal framing of the person
  • ✓ Neutral background (if possible)

Manual Synchronization (Resend)​

Path: Settings > ControlID > Synchronize templates

Synchronize templates tab of the Control iD integration with two devices selected and the action buttons

When to use:

  • Replacing a device in the field
  • Restoring after a failure
  • Bulk update

How to do it:

  1. Select the desired devices in the Control ID field
  2. Click Resend templates
  3. Wait for completion (it can take considerable time)
ButtonWhat it does
Test template sendingOnly reports how many records would be sent. Sends nothing
Resend templatesSends to the selected devices every record that should be on them (faces, fingerprints and, on the IDBox and iDUHF, the cards). Asks for confirmation with a verification code
Cancel synchronizationStops the synchronizations in progress
Delete allDeletes all templates from the selected devices. Irreversible

Devices with Active turned off are not included in the resend.

Processing Time

The resend time depends on the number of photos and biometrics. For large systems, the process can take hours.

Automatic Visitor Removal​

ACCELERO can automatically delete visitor templates after their exit.

When the deletion occurs:

  1. When passing through a barrier with the "Remove visitors" flag:

    • The system checks whether the person has a category from the "Automatically remove" list
    • It checks whether the person does NOT have a category from the "Except if..." list
    • If the conditions are met, it deletes the template from the devices

  2. When closing/deleting an event:

    • The same check above is performed
    • Templates are removed automatically

Configuration example:

Automatically remove: VISITORS, CONTRACTORS
Except if the person has: EMPLOYEES, RESIDENTS

Result:
- Pure visitor: template will be deleted after exit ✓
- Visitor who is also an employee: template kept ✗
Memory Management

Automatic removal is essential to:

  • Avoid exhausting device memory
  • Keep only active registrations
  • Ensure recognition performance

Best Practices​

Planning​

  1. Define categories before configuring:

    • Which categories will have facial recognition/biometrics?
    • Which categories will have automatic removal?
    • Which categories will be administrators?

  2. Choose the operation mode:

    • Always use "Always identify users" = YES
    • Only disable it if a specific project requirement

  3. Plan template capture:

    • Control iD devices for capture?
    • Webcams? Dedicated cameras?
    • Train operators on the process

  4. QRCodes:

    • Do you need to synchronize QRCodes?
    • Configure the appropriate format
    • Test the Wiegand connection

Operation​

  1. Photo quality:

    • Train operators on the importance of the first photo
    • Use adequate lighting
    • Always frontal framing

  2. Monitor synchronization:

    • Check the status icons on the photos
    • Investigate failures quickly
    • Use resend only when necessary

  3. Manage memory:

    • Enable automatic removal for visitors
    • Configure exception categories correctly
    • Monitor device memory usage

  4. Template capture:

    • Use a timeout suitable for the environment
    • Configure clear messages for users
    • Test capture before production operation

Maintenance​

  1. Check communication status:

    • Gateway ↔ ACCELERO
    • Gateway ↔ Devices
    • Resolve network problems quickly

  2. Back up before changes:

    • Back up before reconfiguring gateways
    • Document configuration changes
    • Test after changes

  3. Device replacement:

    • Use the template resend function
    • Verify complete synchronization
    • Test recognition after replacement

  4. Firmware updates:

    • Consult IONGRADE before updating Control iD firmware
    • Check compatibility
    • Test in a controlled environment first

Troubleshooting​

Templates do not synchronize​

Possible causes:

  • Gateway without communication with ACCELERO
  • Gateway without communication with the device
  • Device marked as inactive
  • Person without a category configured for facial recognition
  • Network/credential problems

Solution:

  1. Check the communication status on the gateways screen
  2. Confirm that the device is active
  3. Check whether the person has the correct category
  4. Test the access credentials to the device
  5. Use manual resend if necessary

Template capture timeout​

Possible causes:

  • Timeout configured too low
  • Person not positioned correctly
  • Lighting problems
  • Communication failure

Solution:

  1. Increase the capture timeout
  2. Guide the person on correct positioning
  3. Improve lighting
  4. Check the gateway ↔ device communication
  5. Try again

QRCodes do not work​

Possible causes:

  • "Synchronize QRCodes" not enabled
  • Incorrect QRCode format
  • Numbering incompatible with Wiegand

Solution:

  1. Enable "Synchronize QRCodes" in the settings
  2. Set the format to "Plain text"
  3. Check the Wiegand numbering
  4. Consult the configuration in Global Settings
  5. Resend templates after adjustments

Access denied even within the schedule (disabled mode)​

Cause:

  • "Always identify users" mode is disabled
  • Time ranges not synchronized on the devices

Solution:

  1. Recommended: Enable "Always identify users"
  2. Alternative: Resend templates to synchronize the time ranges
  3. Check the category's time range configuration

Device memory full​

Solution:

  1. Enable "Automatic template removal"
  2. Configure the correct categories
  3. Use resend to clear and re-synchronize
  4. Consider increasing memory capacity (hardware)

Integration with Controllers​

Control iD devices usually connect to ACCELERO controllers via Wiegand.

Typical configuration:

[Person] → [Control iD] → Wiegand → [NEON Controller] → ACCELERO

Important points:

  1. Identifier numbering:

    • The Control iD's Wiegand output must use compatible numbering
    • Configure it in Identifiers

  2. Device area:

    • Configure the "Area" field in the Control iD device registration
    • It must match the physically controlled area

  3. "Always identify users" mode:

    • If enabled: ID always transmitted via Wiegand
    • ACCELERO applies the access rules
    • Recommended for consistency

Next Steps​