Freedom Smart Bridge has 2 operating modes

1. Bridge Mode - Smart Bridge works as a Freedom Bridge and is able to work with two Freedom Servers - a primary and a secondary. This is the default mode that the Edge is running on. This is also the only mode available when there is no SQLite database present in the CM4 OS.

2. Controller Mode - When both Primary and Secondary Freedom Servers are not present, Smart Bridge will revert to Controller Mode. The onboard SQLite database will provide Access Control information. The onboard database is a mirror image of the database on the Freedom Server. In addition, this database will only mirror one site’s worth of Access Control data (e.g. Devices, Schedules, Controlled Areas, Groups).

Operating Mode Details:

Bridge Mode

1. Freedom Smart Bridge supports 2 Wiegand readers, 3 relays, up to 9 (DTLM) supervised inputs, and 3 tamper sensors. Access Control decisions (e.g. card swipes), DHO/DFO, Port Triggers, Multi-Swipe, and First-Person-In functions are all handled by Freedom Server(s).

2. Event Logs are sent to Freedom via MQTT connection in real-time. In case of a Freedom server outage, Smart Bridge will buffer logs internally until Freedom Server returns to service.

3. Smart Bridge has the option to connect to Freedom Server via TLS link. The default TLS port address is 46678.

4. Freedom Server can use either UDP or MQTT to scan and configure Edge Device’s primary/secondary IP/DNS addresses and a number of other parameters.

5. The existing Win32 App “BridgeUtil” can scan Smart Bridge Devices on the network and configure their primary and secondary server IP addresses (IP only, no DNS names). This is useful when Freedom Server is not on the same network as the Smart Bridge Devices (e.g. Freedom Server running on AWS).

Controller Mode

1. Freedom Server needs to propagate an SQLite database to Smart Bridge Devices in order for Controller Mode to be functional. This SQLite database is a mirror copy of Freedom Servers database but is restricted to contain Access Control Data for one “Site”.

2. This SQLite database can hold up to 500K credentials.

3. It supports the same readers and IO points as when it is running in Bridge Mode, the only difference is that Access Decisions are made locally based on its SQLite database.

4. Event Logs are buffered internally in the SQLite database and will be uploaded to Freedom Server when it is back online. The maximum capacity of the buffer is 50,000 events.

5. Event Logs are uploaded to Freedom Server via MQTT.

SQLite Database Synchronization

1. Freedom server can synchronize SB devices’ database periodically as frequently as once an hour. By default, the server always sends database updates to all SB devices at midnight.

2. Freedom configuration such as users, card numbers, and user group assignments are pushed to SB devices in real-time. This will enhance the readiness of the onboard database.

Smart Bridge Software Upgrades

1. End users can download TRN files to upgrade Smart Bridge OS or Application. 

2. Application TRN also contains firmware for Smart Bridge’s device module board.

Multi-Color LED Status Indicator

1. Smart Bridge has a Multi-Color LED indicator that reflects the device’s current operation status.

2. Common LED patterns are:

   1. Startup - green, fast blinking

   2. Waiting for connection - green, blinks twice, pause for a second, then repeat

   3. Connected to Server - cyan, fade in and out every 2 seconds

   4. Identity/Ping - alternating red, green and blue lights for 30 seconds

NTP Clock Sync

1. Smart Bridge has an NTP client that can reach out to NTP servers on the internet.

2. Regardless of NTP client being enabled or not, the Freedom server will always send time updates to Smart Bridge Devices.

3. In case public NTP servers are not available, Smart Bridge will synchronize with the Freedom Server clock instead.

4. If the NTP client is not enabled, Smart Bridge will synchronize with the Freedom server clock when:

   1. A new connection is made to the server

   2. At midnight.

5. NTP corrections are done gradually.

Limitations

...

Multi-factor support for Exit readers.

...

Buzzer line not implemented yet.

...

Freedom server does not sync first-man-in status with SB. So when the server is down, users may experience inconsistency with unlock schedules.

...

Not all DB records are synchronized with SB in real-time. Only users, card data, and user access group assignments are getting live updates.

...

IDENTIV EG-2 (Model 50-40-SB) Beta Version 1.2 Release Notes

Version 1.0 – Beta Release Wednesday, July 5, 2023

IDENTIV EG-2 (Model 50-40-SB) is compatible with Primis and Primis Cloud Version 11.4 Only (Not supported on Freedom or Freedom Cloud)

IDENTIV EG-2 (Model 50-40-SB) Overview

The new IDENTIV EG-2 (Model 50-40-SB) is an IT-based door controller designed to manage all local access control seamlessly while integrating with any existing IT network infrastructure. Powered by 24 VDC or PoE+, the IDENTIV EG-2 (Model 50-40-SB) can connect with any Primis Cloud or Primis on-premise cube, regardless of its location, offering a wide variety of distributed topologies to suit any requirements. While connected to a Primis instance, the IDENTIV EG-2 (Model 50-40-SB) stores all the information required to provide access to its managed doors. In the event of a loss of connection to Primis, the IDENTIV EG-2 (Model 50-40-SB) retains its information, ensuring no downtime in operations or access for cardholders.

Specifications

New Features

KEY FEATURES IN THIS BETA RELEASE

• Support for up to 2 readers (2 OSDP or 2 Wiegand).

• Support for up to two doors with entry readers only or one door with entry/exit readers.

• Support for 3 relays, two doors relays and one auxiliary relay.

• Support for up to 9 supervised inputs (Three per door and Three auxiliary) using IDENTIV DTLM3 and/or MELM3 modules.

• Support for Identiv DTLM1, DTLM2, DTLM3, MELM1, MELM2 and MELM3 line modules.

• Support for up to 500,000 credentials.

• Support for log capacity of 100,000 transactions when offline from Primis.

• Support for Enclosure tamper detection.

• Support for Reader tamper detection.

• Support for 24VDC or PoE+ input.

• Support for 24VDC and 12VDC outputs for Lock Power.

• Support for LED status indicators for Readers, Inputs, Outputs, EG-2 state, Network, Power, and OSDP RS485 status.

• Support for software and firmware updates from Primis.

• Support for Global Input/Output linking - peer to peer communications among IDENTIV EG-2 (Model 50-40-SB).

• Support for secured TLS/MQTT network communications.

• Support for TLS Certificate management.

• Support for continued local operations while offline from Primis.

• Support for OSDP V2.1.5 or later Secure Channel.

• Support for the IDENTIV Bridge Utility configuration tool.

• Support for direct NTP server configuration.

• Support for Primary and Secondary Server configuration.

• Support for Name Server configuration and resolution.

• Support for Principal and Replica IDENTIV EG-2 (Model 50-40-SB) configuration.

• Support for onboard logging.

• Support for PoE voltage, input voltage, door current, clock battery, and IDENTIV EG-2 (Model 50-40-SB) temperature monitoring in Primis.

• Support for locating ping.

• Support for IDENTIV EG-2 (Model 50-40-SB) remote reboot.

• Support for IDENTIV EG-2 (Model 50-40-SB) remote software and firmware upgrade.

• Support for configurable IDENTIV EG-2 (Model 50-40-SB) sync schedules.

• Support for RS485 OSDP address conflicts displayed in Primis.

• Compliant with (pending) UL294, UL2043, FCC Part 15 Class B, ICES-003, KS C 9832, EN 55032, TAA.

Known Issues

• The IDENTIV EG-2 (Model 50-40-SB) is Not UL Listed at the time of beta.

• The reader buzzer managed by the IDENTIV EG-2 (Model 50-40-SB) is not supported in this release.

• Exit reader multi-factor is not supported in this release.

• Not all database records are synchronized in real-time, they are scheduled.

• OSDP readers do not function when IDENTIV EG-2 (Model 50-40-SB) does not have a database downloaded.

• IDENTIV EG-2 (Model 50-40-SB) displays erroneous “Up Time” during boot-up and when the MQTT connection is not ready.

• Special day schedules are not supported in this beta release.

• The silkscreen on the top case will differ from that shipped in the Release Item.