What are Ecards, how to use them, and how to configure using them.

Ecards (also known as Emergency Cards) are a feature, available for both legacy and Controller Continuity-enabled hardware, that when used properly can help ensure there will be access to doors and devices when communication is lost between the controller and Cloud Node. This is in addition to Controller Continuity, a feature only available with Red-series controllers. For more information regarding Controller Continuity, please refer to the article 'What is Controller Continuity?' for more information.

The use of Ecards is highly recommended for every Cloud Node system, regardless of the size of the system. If a Controller loses network or wireless connection with the Cloud Node system, the Controller will either switch to Ecard-operations or to Controller Continuity mode, depending on the model of the Controller. 

Legacy Controllers (non-Red series Controllers): These controllers will switch to Ecards operations if the communications loss extends beyond four (4) minutes. 

Red-series Controllers: These controllers will switch to Controller Continuity, using the settings configured in the Config Tab in Configuration. This can result in close-to-normal operations continuing for a specified timeframe or reverting to Evard operations immediately.

Accessing and Assigning Ecards 

Ecards can either be credentials that are only used as Ecards or credentials which have been assigned to users under People. Each credential has a number assigned and printed on the front or back of the card.

From the Cloud Node dashboard, tap/click the Configuration icon which is shown below.

Then tap/click the Config tab. The Active Card Format will need to be configured to match the format for the credentials and Ecards that are being used on the Cloud Node system.

In the Ecards section, tap/click a field and then enter the credential number to be used as an Ecard. Up to 10 card numbers may be entered and once entered. tap/click the Write button. These card numbers are then saved in the hardware of all currently configured and communicating controllers.