Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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

  1. Multi-factor support for Exit readers.

  2. Buzzer line not implemented yet.

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

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

  5. Controlled Area states (e.g. Open/Close, First Man in) are not synchronized when Smart Bridge reconnects to the Freedom server after an outage.

  • No labels