1. Manuals
  2. Brands
  3. EVVA Manuals
  4. Locks
  5. Xesar 3.0
  6. System manual

EVVA Xesar 3.0 System Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
System manual
Xesar 3.0
Version 3.0.216
1
KPM.X.Systemhandbuch_X3.0.EN.V1.9 | 05/2019 | Subjects to misprints and technical changes.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Xesar 3.0 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for EVVA Xesar 3.0

Summary of Contents for EVVA Xesar 3.0

  • Page 1 System manual Xesar 3.0 Version 3.0.216 KPM.X.Systemhandbuch_X3.0.EN.V1.9 | 05/2019 | Subjects to misprints and technical changes.

  • Page 2: Table Of Contents

    Identification media ..................37 Construction Card (construction site medium) ............ 38 System requirements .................... 39 Xesar 3.0 single-user system ................39 Xesar 3.0 multi-user system server ..............41 3.2.1 System requirements – Server ............41 3.2.2 System requirements - Admin PC with coding station and Admin Card ..43 3.2.3...
  • Page 3 Upgrade from Xesar 2.2 to Xesar 3.0 ..............50 4.1.1 Xesar upgrade compatibility ..............51 4.1.2 Upgrade instructions for Xesar 2.2 systems to Xesar 3.0 ......51 Preparation of the PC for the Xesar 3.0 Installation ..........53 4.2.1 Docker installation ................53 4.2.2...
  • Page 4 7.11 Identification media ..................154 7.11.1 New identification medium ..............154 7.11.2 Existing identification medium ............156 7.12 Adding a new EVVA access components ............159 7.13 Commissioning the Xesar network adapter ............159 7.13.1 PC configuration ................159 7.13.2 Commissioning a Xesar network adapter ..........
  • Page 5 Docker does not start automatically (autostart) ........200 8.21.3 Update to Xesar 3.0 ................. 200 8.21.4 Number of zones in Xesar 3.0 (compared with Xesar 2.2) ..... 200 8.21.5 Import from Xesar 2.2 (time zone) ............. 200 8.21.6 Calendar import ................200 8.21.7...
  • Page 6 8.21.17 No dashboard display in the browser ..........202 8.21.18 Blue screen after removing a medium from the coding station .... 202 8.21.19 Problems detecting media with Windows 10 Pro x64 Version build 1709202 8.21.20 Tablet synchronisation ..............202 8.21.21 Tablet synchronisation ..............

  • Page 7: General Information And System Overview

    1.1 General legal notes EVVA concludes the contract on the use of Xesar exclusively on the basis of its General Terms of Business (EVVA-GTB) as well as its General Licensing Conditions (EVVA-ALB) with regards to the software for the product. Please refer to http://www.evva.com/terms.

  • Page 8: Imprint

    1.2 Imprint 2nd English Edition, 05/2019 This edition shall not longer be valid upon publication of a new system manual. All rights reserved. This system manual must not be reproduced, copied or adapted neither in full or in part using electronic, mechanical or chemical methods or any other procedures without written consent by the publisher.

  • Page 9: Signs And Symbols Within The Xesar Software

    1.4 Signs and symbols within the Xesar software The following icons and symbols are used within the Xesar software, Xesar Installation Manager and Periphery Manager: Condition Visualisation Explanation Confirm/save Confirming or saving input Adding elements, e.g. new persons, installation location, etc. Discard entries Discarding an entry Deleting elements from the Xesar system, e.g.
  • Page 10 12 Filter Find potential filter settings here On Xesar dashboard runs an activity at the 13 Update/connect backend. In Xesar tablet app: connect to a connected door Not updated/waiting An update is available and can be downloaded for update/download using this icon update 15 Search Search for a specific event entry here...
  • Page 11 25 Displayed language Change the language here. Shows the number of KeyCredits to be deducted (e.g. as a result of changing authorisations or is- 26 Show KeyCredit units suing new identification media). Also shows the number of added KeyCredits Show Xesar Lifetime This icon is displayed if Xesar Lifetime KeyCred- KeyCredits its have been activated.

  • Page 12: Condition Of The Identification Medium

    1.5 Condition of the identification medium Visuali- No. Status Explanation sation Insecure disabled identification There are still insecure access points. medium Secure disabled identification me- There are no uncertain access points. dium Unauthorised identification The identification medium is not authorised. dium Currently valid Currently invalid...

  • Page 13: Hardware And Installation

    Hardware and installation Please check carefully to make sure the Xesar product you selected is suitable for your application. We have made the required data sheet available on our homepage: https://www.evva.com/uk- en/products/electroniclockingsystemsaccesscontrolsystems/xesar/ Figure 1: System architecture (sample image) 2.1 Xesar access components Xesar's versatility offers different components, such as different escutcheon, handle, cylinder shapes (including hybrid and cam locks), wall readers and padlocks.

  • Page 14: Xesar Escutcheon

    The interface is located on the front of all Xesar access components, behind the connector cover (EVVA logo). Slightly press towards the inside on the left-hand side of the EVVA logo (near the "E") with your finger and fold out on the right-hand side (near the "A") to access the interface.
  • Page 15 Reader unit The reader unit sensor is located on the outside of the Xesar escutcheon between the connector (EVVA logo) and visual indicator (LED). Functional principle The outside handle is disengaged by default – operating the outside handle will not change the position of the latch.
  • Page 16 Please note that specialist personnel must install Xesar access components as per the notes and information as well as the assembly manual enclosed with the product. EVVA provides a host of different installation tools to make installing your Xesar system easier. Visit our website.
  • Page 17 The drilling template is optionally available. Product code: E.ZU.BE.BS.V1 KPM.X.Systemhandbuch_X3.0.EN.V1.9 | 05/2019 | Subjects to misprints and technical changes.
  • Page 18 Xesar access components signal events. Repeatedly disregarding the "Battery low" warning may cause escutcheon malfunctions. At normal ambient temperatures, the first "Battery low" warning indicates that up to 1,000 actua- tions are still possible within the next 4 weeks. Temperatures deviating from normal ambient tem- peratures may cause the escutcheon to prematurely fail.

  • Page 19: Xesar Handle

    Please check carefully to make sure the Xesar product you selected is suitable for your application. We have made the required data sheet available in the download section of our homepage: https://www.evva.com/uk-en/products/electroniclockingsystemsaccesscontrolsystems/xesar/ 2.1.2.1 Xesar handle — functional description Visual signals...
  • Page 20 Reader unit The reader unit sensor is located on the outside of the Xesar handle between the connector (EVVA logo) and the LED. Functional principle The outside handle is disengaged by default – operating the outside handle will not change the position of the latch.

  • Page 21: Xesar Cylinder

    Xesar cylinders are available as half cylinders or double cylinders with one-sided or double-sided, electronic access. Please carefully check the Xesar cylinder you selected is suitable for your application. Please refer corresponding data sheet additional specifications https://www.evva.com/at-de/xesar/https://www.evva.com/uk-en/products/electroniclockingsys- temsaccesscontrolsystems/xesar/ KPM.X.Systemhandbuch_X3.0.EN.V1.9 | 05/2019 | Subjects to misprints and technical changes.
  • Page 22 Reader unit The reader unit sensor is located in the plastic cap of the Xesar cylinder thumb turn between the EVVA logo and the LED. Functional principle By default, the electronic outside thumb turn of the Xesar cylinder is disengaged. The cam remains disengaged upon operating the outside thumb turn and the outside thumb turn turns without en- gaging with the cam.
  • Page 23 Depending on the cylinder's protrusion beyond the escutcheon or any in-...
  • Page 24 //www.evva.com/at-de/xesar/ 2.1.3.3 Cylinder tool Figure 10: Cylinder tool (sample image) Xesar cylinders provide a special opening mechanism to protect from manipulation.
  • Page 25 Please note the instructions in the Xesar cylinder assembly manual watch video instructions: http://video.evva.com/tutorials/xesar/expzkzs/expzkz-s- 1/de/http://video.evva.com/tutorials/xesar/expzkzs/expzkz-s-1/de/ The cylinder tool is optionally available. Product code: E.ZU.PZ.ZW.V2 KPM.X.Systemhandbuch_X3.0.EN.V1.9 | 05/2019 | Subjects to misprints and technical changes.

  • Page 26: Xesar Wall Reader

    Please check carefully to make sure the Xesar product you selected is suitable for your application. We have made the required data sheet available in the download section of our homepage: https://www.evva.com/uk-en/products/electroniclockingsystemsaccesscontrolsystems/xe- sar/#tab6 2.1.4.1 Xesar wall reader — functional description...
  • Page 27 Reader area, ON/OFF status light The reader unit sensor is located behind the glass panel of the Xesar wall reader between the EVVA logo and the LED. The status light of the Xesar wall reader lights up continuously during on-going operation to facilitate localising the reader unit in dark environments.

  • Page 28: Xesar Wall Reader Control Unit

    2.1.5 Xesar wall reader control unit Figure 14: Xesar wall reader control unit (sample image) The Xesar control unit can be exclusively used in conjunction with Xesar wall readers. Each control unit can be connected to one or two Xesar wall readers. Xesar control units connected to Xesar wall readers must be installed indoors in zones protected from manipulation.

  • Page 29: Mains Adapter For Control Unit

    Please note that specialist personnel must install Xesar access components as per the notes and information as well as the assembly manual enclosed with the product. EVVA provides a host of different installation tools to make installing your Xesar system easier. Visit our website.
  • Page 30 Installation using drilling template Figure 17: Drilling template (sample image) EVVA provides a high-quality, metal drilling template to facilitate preparing the door for an assem- bly of any type of Xesar escutcheons and Xesar handles. An adjustable stop safeguards that holes are correctly aligned and it enables adaptations of the settings to match the requirements of any door situation.

  • Page 31: Xesar Access Components Signal Events

    Unlocking attempt signal is only output af- Signal 1 with authorised me- mmmmm ⚫⚫⚫⚫⚫ ter the last card is read dium (yes, no or no EVVA card) Signal 2 End of release ttttt ⚫⚫⚫⚫⚫ Rejected Signal 3 hh-hh-hh-hh ⚫⚫-⚫⚫-⚫⚫-⚫⚫...

  • Page 32: Xesar Coding Station

    The mini coding station cannot be used to operate the AdminCard Note: we have provided the driver required for the Xesar coding station in the download section of our homepage: https://www.evva.com/uk-en/products/electroniclockingsystemsaccesscon- trolsystems/xesar/#tab6 KPM.X.Systemhandbuch_X3.0.EN.V1.9 | 05/2019 | Subjects to misprints and technical changes.

  • Page 33: Xesar Tablet

    All Xesar access components feature an interface at the front, behind the connector cover (EVVA logo). Slightly press towards the inside on the left-hand side of the EVVA logo (near the "E") and fold out on the right-hand side (near the "A") to access it.
  • Page 34 We recommend that you regularly synchronise data at each Xesar access component to be able to quickly synchronise events with the software (at- tention: max. 1000 events per access component, after which the oldest events are overwritten again). If you have installed online components, the data is updated using XVN (see: →...

  • Page 35: Xesar Emergency Power Device

    Xesar tablet to once again enable access with all authorised identification media. The installed interface below the EVVA logo in conjunction with the emergency power device is intended for emergency power supply only and it is not required as part of normal operation.

  • Page 36: Admin Card

    2.7 Admin Card Figure 22: Admin Card (sample image) The Admin Card is a contact-type, electronic chip card in standard format. It enables to access the Xesar software and uniquely identifies the system. Any KeyCredits purchased to make changes to authorisations are saved on the card (also applies to KeyCredits Lifetime).

  • Page 37: Identification Media

    2.8 Identification media An identification media is a non-contact RFID chip based MIFARE DESFire EV1 with an overall memory capacity of 4 kB. Overview of available identification media: Figure 23 – Identification media overview Do not place more than one identification medium on the Xesar cod- ing station.

  • Page 38: Construction Card (Construction Site Medium)

    Please refer to the corresponding data sheet for additional specifications at https://www.evva.com/uk-en/products/electroniclockingsystemsaccesscon- trolsystems/xesar/ An identification medium can feature authorisations for a maximum of 96...

  • Page 39: System Requirements

    Xesar can be operated as a multi-user system and a single-user system. System requirements in the following section. 3.1 Xesar 3.0 single-user system We do not recommend PC single-user operation for 24/7 permanent operation and use with online components. If the single-user PC is not in operation, then the wall scanner is in offline mode and identification media are not updated.
  • Page 40 Xesar component wall reader ponents software. dealership It may be possible to implement the following solutions (please consult EVVA Technical Offices): • Installation manager operated on a virtual machine • Installation manager operated on a different Windows operating system •...

  • Page 41: Xesar 3.0 Multi-User System Server

    Hard disk space, SSD recommended: ≥ 40GB (note system size and planned runtime for dimensioning)  Direct Internet access without proxy to unlock KeyCredits and licences to access EVVA secured authentic and un-manipulated software delivery  Lokal LAN with low latency (ping<10ms, roundtrip <30ms) ...
  • Page 42 Service catalogue: Management of a Xesar 3 system See appendix: 3.4: Service/communication • Server – Admin PC • Server – Client PC • Server - Online wall reader Tested operating systems: OS type Version Virtualisation possible Ubuntu Linux 14.04 (Trusty, LTS) 16.04 (Xenial, LTS) 18.04.1 / 18.04.2 LTS Windows Server...

  • Page 43: System Requirements - Admin Pc With Coding Station And Admin Card

    Due to the large number of possible operating systems not all variants can be tested for compatibility by EVVA. If an operating system is to be used that is not tested by EVVA, please consult the re- sponsible EVVA technical office beforehand.

  • Page 44: System Requirements - Client Pc With Coding Station Without Admin Card

    10 Pro • Internet Explorer from version 11 It may be possible to implement the following solutions (please consult EVVA Technical Of- fices): • Operation of the periphery manager on a different Windows operating system, such as Windows Server 2012 R2 and Server 2016 data centre •...

  • Page 45: System Requirements - Client Pc Without Coding Station (Pc/Tablet/Smartphone)

    Internet Explorer from ver- Windows 10 Pro sion 11 It may be possible to implement the following solutions (please consult EVVA Technical Offices): • Operation on a different Windows operating system, such as Windows Server 2012 R2 and Server 2016 data centre •...
  • Page 46 Services provided by EVVA on the Internet: Service Configurable port Trusted Registry https://sfw.evva.com:443 https://sfw.evva.com:4443 Licence service https://licence.evva.com:8072 Services provided by Xesar 3.0 server within the local network: Service What Configura- ble port Docker Engine tcp://<IP Installation>:2376 Host Security-related https://<IP Installation>:8200...

  • Page 47: Attachment To The Project Checklist

    Attachment to the project checklist 3.3.1 Depiction of layout KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 48: Service/Communication

    Docker Trusted Regis- Docker Trusted Regis- Provision of signed Docker images Docker Client, Docker 443, 4443 443, 4443 HTTP try (container image try sfw.evva.com and verification of the signature Engine delivery) Licence service li- Register an installation/admin card 8072 8072...

  • Page 49: Communication, Client Pc - Server (Backend)

    Service catalogue: Server and workstations in multi-user system 3.5 Communication, Client PC - Server (backend) Default Port ad- Service Network Protocol Utilising components port dress Web service and deliv- Installation management, LAN/WLAN 8080 configurable HTTP ery of the web applica- Browser-based frontend web service tion for the browser...

  • Page 50: System Installations, Upgrade And Updates

    System installations, upgrade and updates 4.1 Upgrade from Xesar 2.2 to Xesar 3.0 Figure 25 – Important information for a software upgrade KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 51: Xesar Upgrade Compatibility

    Xesar 2.2 to Xesar 3.0 only". For upgrades from Xesar 2.2 to Xesar 3.0 only Proceed as follows to upgrade the Xesar software from Xesar 2.2 to Xesar 3.0: • Insert your Admin Card into the slot of the coding station and load the data from your Xesar 2.2 system (see section 6.1 Xesar Installation Manager, step 8;...
  • Page 52 You can continue to use any available identification media. For this purpose, you must update them at the coding station or an online wall reader. Prior to importing a Xesar 2.2 system to a Xesar 3.0 system it is necessary to enable •...

  • Page 53: Preparation Of The Pc For The Xesar 3.0 Installation

    If you reinstall Docker (Uninstall Docker and then reinstall it), all system data will be lost. This is why all containers musk be backed up before Docker is unin- stalled. This can be done as of version Xesar 3.0 SP1 with the manual or auto- matic backup function in the Installation Manager.
  • Page 54 4.2.1.2 Docker installation steps 1. Step: the installer automatically opens after the download. Figure 26 – Installing Docker Click "Yes" if a Windows warning message appears. Figure 27 – Installing Docker security notice 2. Step: Starting Docker a. The "Docker is starting…" status message automatically opens in the Windows task bar.
  • Page 55 Figure 29 – Docker starting progress 3. Step: "Docker is now up and running!" a. Once Docker has started a status window with the following message opens: "Docker is now up and running!". b. The status window closes automatically. c. Right-click the Docker icon to open the settings. Figure 30 - Docker status windowtime 4.
  • Page 56 5. Step: Checking the settings a. Make sure the following items have been activated: "Start Docker when you log in" b. "Automatically check for updates" c. Do not „Send usage statistics“ that are confirmed d. You may now close Docker's general settings with "X". Figure 32 –...
  • Page 57 Attention: With a new installation of Docker (uninstall Docker and then reinstall it), all system data will be lost. This means that all files must be secured before Docker is deinstalled. (See section Securing the Xesar system data in the Installation Manager) Figure 33 - Windows features...

  • Page 58: Coding Station Driverinstallation

    Figure 34 – Activating Hyper-V 4.2.2 Coding station driverinstallation The HID hardware driver is required to operate the Xesar coding station (HID Om- nikey 5421) on the PC. A driver installation is not necessary if you already use coding station version HID Omnikey 5422! You can directly continue with section 5 Xesar 3.0 - Programs Two driver installation types are possible: •...
  • Page 59 Figure 35 – Windows Device Manager 3. Step: Search the list for "Smart card readers" (potentially "Readers"). Click this entry and select the entry starting with "Microsoft…". Right-click the "Mi- crosoft…" entry and select "Update driver". Figure 36 – Updating the Microsoft driver KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 60 4. Step: Windows prompts you whether to "Automatically search for updated driver software". Please click this option. Figure 37 – Driver search 5. Step: the driver will now be automatically downloaded and installed by Windows Device Manager! Figure 38 – Coding station – automatic driver installation KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 61 6. Step: the driver has been installed. Click "Close". Figure 39 – Coding station – successful driver installation The reader used is now listed in the Device Manager. In this case: Omnikey 5422 Figure 40 – display of the coding station in the Device Manager KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 62 The coding station driver has been installed. Please skip to section: 5 Xesar - Programs, to continue the Xesar software installation. 4.2.2.2 Alternative: Manual driver search and HID driver installation Alternatively you can also manually search for the the driver and download it from the HID GLOBAL page.
  • Page 63 3. Step: Scroll to the Windows 10 Pro driver designated as "SELF-EXTRACTING AR- CHIVE". Figure 42 – Coding station download package You may see a warning message regarding EULA, please accept it! Click "Run" in the browser to directly open the file and start the process – conse- quently skip the next step in these instructions.
  • Page 64 5. Step: click "Accept" to continue the installation. Figure 44 – Coding station driver installer 1 6. Step: click "Extract" to install the driver. Figure 45 – Coding station driver installer 2 You have now successfully installed the HID driver! KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 65: Xesar 3.0 - Programs

    • Xesar Periphery Manager: enables operation of the coding station on the client computer. Download the Periphery Manager in the Xesar 3.0 software in the "Sup- port/update" tile. The download for the Xesar-Software (Installation Manager) can be found at our EVVA Website: https://www.evva.com/uk-en/products/electroniclockingsystemsaccesscontrol-...
  • Page 66 You will receive an email with a temporary download link! Click the link and the following window opens. Figure 47 – Download Installation Manager for software Download the file! Attention: The download of the Installation Manager may take up to 2 minutes! KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 67: Xesar Installation Manager

    5.1 Xesar Installation Manager 1. Step: right-click to unpack the ZIP file. Select "Extract all". The system creates a new, unzipped folder with the same name. !!Unpacking may take a while!! Figure 48 - Xesar Installation Manager ZIP file 2. Step: Double-click to open the new folder and  the application. Figure 49 –...
  • Page 68 The following warning may appear. Please click "Yes". Figure 50 – Installation Manager warning message 3. Step: Xesar Installation Manager opens. Figure 51 – Installation Manager window KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 69 4. Step: Load reading unit in the Installation Manager a. Click the "Admin Card" tab. b. The coding station can read and process contact-based media (Admin Card) and contactless CL (all Xesar identification media) smart cards. The contact-based reader is only required for the Installation Manager and reading the Admin Card. Attention: If synchronisation fails, select ...
  • Page 70 Click the  "Save" icon to save. Figure 53 – Installation manager tab: Admin Card – loading the card For UPGRADES from Xesar 2.2 to Xesar 3.0 only • Insert the Admin Card of your Xesar 2.2 system in the coding station The following is displayed.
  • Page 71 6. Step: Loading the most recent Xesar version a. Click the Settings tab. b. Confirm "Check TLS". c. Click "Synchronise". d. The most recent version is automatically loaded and selected for you. Select "Ver- sion" from the drop-down menu to check this and click "Save". Figure 55 –...
  • Page 72 7. Step: Creating a new system a. Click the  "Installations" tab and b. Click  "+". Figure 56 - Installation Manager, create new system 8. Step: System specifications  Enter a system name (with the exception of $ and “special characters can be used), an additional description can also be added.
  • Page 73 Figure 57 – Installation Manager system specification Notice: write down the web port. You will need it later to configure the Xesar tablet! KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 74 Only for UPGRADES from Xesar 2.2 to Xesar 3.0 Use the "Import" field for the data import of your Xesar 2.2 system. The file name is "aesssdb.h2" or "aesssdb.h2.db". Figure 58 – Installation Manager database import You have then successfully installed a Xesar 3.0 system! 9.
  • Page 75 Print out this information and keep it in a safe place! EVVA will be unable to restore the data if you lose this information! If the system information does not automatically open in a pop-up window: ...
  • Page 76 Alternatively, the information is available at: C:\Users\Xesar\.xesar-  1.0.43\Anlagenname Open the PDF here Figure 61 – Alternative system information 10. Step: Starting the system a. The installation has been completed successfully once the system appears as a  list entry. The " "...
  • Page 77 The progress icon indicates that the system is starting. Figure 63 - Installation Manager, the system loads 11. Step: System running a. The "☺" icon indicates that the system is running. Figure 64 - Installation Manager funktionen KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 78 Enter your  KeyCredits code (on the rear of the scratch card) in the field and click Confirm. Figure 66 – Entering the KeyCredits code You will receive the following messages from the EVVA licence server after having success- fully loaded KeyCredits: Figure 67 – Licencing successful...
  • Page 79 Attention: an active Internet connection to the EVVA licence service is required to redeem KeyCredits! Notice: The following appears after having redeemed a KeyCredits Xesar Lifetime licence: Figure 68 – KeyCredit Xesar Lifetime 13. Step: Opening the Xesar software dashboard a.
  • Page 80 14. Step: Warning from your browser: a. As soon as Xesar is started with the arrow in the Installation Manager, warnings will appear in the browser! Attention: the warnings may differ depending on the browser! b. Click Details. Figure 70 – Warning in browser 15.
  • Page 81 16. Step: Xesar software login: Log in with the admin user name and password and click the arrow . Example: User name: admin Password: FmJeWgKcFA Figure 72 - Login window Figure 73 – Xesar dashboard KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 82: Admincard Exchange

    5.2 AdminCard exchange: If the AdminCard is defective or is lost, then it can be replaced as follows: • Insert a new AdminCard in the coding station. • In the Installation Manager, select the desired system (1) and click on the key button (2).
  • Page 83 • Upon confirmation, a new installation information sheet will be generated. • Print this document again and keep it in a safe place. IMPORTANT: Make sure that you perform a manual backup in the Installation Otherwise, a restore will not fit the Manager after the AdminCard exchange.

  • Page 84: Software Update

    5.3 Software Update If a new Xesar software version is available, then the new software version will be indi- cated in the "Update" column in the Installation Manager. Select the system (1) and click on the edit button (2) to go to the settings page. KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 85 Click on the update download button (3) to start the software update As of version 3.0.212 updates can also be performed with open maintenance tasks. For data security, an automatic backup is performed before an update. If an update was unsuccessful, then this backup file can be used to perform a new system instal- lation (restore).
  • Page 86 Before a software update, all tablets in the system must be logged out. Confirm that all tablets are logged out All version changes are displayed in the software update. Confirm to begin updating. KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 87 An automatic system data backup is performed before the backup. Then an update of the individual versions is carried out. Progress is displayed. KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 88 The update is complete. Confirm to return to the Installation Manager. The new software version is now added to the version column KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 89 Installation Manager update If a new version of the Installation Manager is available then the following mes- sage appears when starting the Installation Manager: • Enter the target directory to install the new Installation Manager. • Unzip the download file and start the new Installation Manager. •...

  • Page 90: Periphery Manager

    5.4 Periphery Manager: The Periphery Manager enables the operation of the coding station on the client com- puter. The coding station is used to create, write to, read and update identification media. 1. Step: The Periphery Manager is on the Xesar workstation under the Xesar Support tile.
  • Page 91 2. Step: Click on „Download Periphery manager“. Figure 76 - Periphery Manager selection KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 92 3. Step: unpack the ZIP file. Figure 77 - Extracting the Periphery Manager ZIP file Figure 78 - Extracting the Periphery Manager ZIP file KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 93 4. Step: Double-click the "Periphery-Manager-x.x.x" folder and open the "Periphery Manager" application file Double-click the application file.→ Figure 79 – Xesar periphery application Windows may potentially show warnings: Please click "Additional information". Figure 80 – Xesar periphery application – warning KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 94 Click "Run anyway". Figure 81 – Xesar Periphery Manager, warning 2 You may see additional warnings, please accept them and continue. 5. Step: Xesar Periphery Manager opens. Figure 82 – Periphery Manager The Periphery Manager is now ready for use! KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 95: Linking The Coding Station To The Xesar Software

    5.5 Linking the coding station to the Xesar software Proceed as follows to use a connected coding station with the Xesar software: Figure 83 – Coding station on the dashboard 1. Step: creating the coding station: Click the coding station tile on the Xesar dashboard. Figure 84 –...
  • Page 96 2. Step: Click the "+" icon to add a new coding station. Figure 85 – Adding a coding station 3. Step:  Enter the name and potentially a description and click the "Confirm" icon. Figure 86 – Coding station, adding names 4.
  • Page 97 5. Step: Activating the coding station and downloading the configuration file a. Click the coding station's list entry b. Select the "Use coding station in this browser" option c. Click the "Download" icon and download the coding station's configuration file. d.
  • Page 98 6. Step: In the Periphery Manager click the  "+" icon to import the configuration file. The configuration file name ends with  "properties". Figure 89 - Add Periphery Manager configuration file Figure 90 - Select Periphery Manager configuration file KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 99 Your installation (name of your system) is now shown as a list entry in the Periphery Man- ager. Figure 92 – Xesar system in Periphery Manager KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 100 7. Step: select the "Configuration" tab. a. Select the reader unit designated as OMNIKEY with CL. b. Click the "Save" icon. Figure 91 – Periphery Manager, selection of the coding station 8. Step: Select the "Run" tab and  click the "Start" icon to start the Periphery Man- ager.
  • Page 101 9. Step: Linking to the software a. Update the Xesar interface in the browser (press F5 or CTRL+R). The coding station has now been linked to the browser. (Figure 96 – Coding station – connected status: Yes) b. Close the Periphery Manager (continues to run in the background). Figure 93 - Periphery Manager close Figure 94 –...

  • Page 102: Integrating Your Xesar Tablet Into Your System

    Initially prepare your tablet – as described in section 5.7.Manually uninstalling and in- stalling the Xesar app (upgrade from Xesar 2.2 to Xesar 3.0) The IP address of the computer in the WiFi network is provided in the tablet as the server address with the corresponding port no., e.g.: https:// 172.16.250.35:9090...
  • Page 103 2. Step: Finding the web port number You additionally require the port number for the IP address for the Xesar tablet. It is identical to the number configured in the Installation Manager or you may copy the number from your browser. For example: https:// 172.16.250.35:9090 Alternatively proceed as follows to find the web port number: Select the "Edit icon"...
  • Page 104 3. Step: Open the Xesar app on your Xesar tablet, click "Synchronise" and enter the following IP address in the "Xesar server" field: c. https://IPv4 address of your computer:Port no. of your Xesar system e.g.: https://172.16.250.35:9090 d. Enter the name of the Xesar tablet, e.g. "Maintenance engineer 1" e.
  • Page 105 Figure 99 - Xesar tablet certificate 2 The synchronisation process should only take a few seconds. Figure 100 – Xesar tablet authentication Depending on the quantity of data to be synchronised this process may take up to a few minutes. Figure 101 –...
  • Page 106 Figure 102 – Tablet APP home 5. Step: Xesar tablet tile on the dashboard shows the number of Xesar tablets added in the system. Figure 103 – Xesar tablet tile Now you have integrated your Xesar tablet into the system! You can now configure your system in the Xesar software.

  • Page 107: Manually Uninstalling And Installing The Xesar App (Upgrade From Xesar 2.2 To Xesar 3.0)

    5.7 Manually uninstalling and installing the Xesar app (up- grade from Xesar 2.2 to Xesar 3.0) For an upgrade from Xesar 2.2 to Xesar 3.0 it is necessary to manually uninstall the X2.2 app on a Xesar 2.2 tablet and manually install the Xesar 3.0 app.
  • Page 108 2. Step: Click Apps Figure 105 – Xesar tablet apps settings 3. Step: uninstall the Xesar 2.2 app and delete the .apk file from the download folder. For this purpose, open your tablet's file manager Figure 106 – Uninstalling the Xesar tablet Xesar app KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 109 4. Step: click OK. Figure 107 – Uninstalling the Xesar tablet app OK 5. Step: delete the .apk file from the download folder. For this purpose, open your tablet's file manager Figure 108 – Xesar tablet file manager KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 110 6. Step: click the Download folder and delete the .apk file here. Figure 109 – Deleting the Xesar tablet APK file Step:On the Xesar dashboard click the "Xesar support" tile. Figure 110 - Desktop - selecting support Figure 111 – Support tile KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 111 8. Step: The current Xesar app is found under "Update". Click "Download Xesar tab- let". Figure 112 - Periphery Manager selection 9. Step:Connect the Xesar tablet to your computer by USB and copy the file to your tablet's file manager. Figure 113 –...
  • Page 112 Step: Click the .apk file to install the Xesar app on your tablet Figure 114 – Xesar tablet – Xesar 3.0 APP Figure 115 – Xesar tablet – installing the Xesar 3.0 APP KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 113 11. Step: subsequently synchronise the tablet with the Xesar software. Figure 116 – Synchronising the Xesar tablet Step: Complete the integration of the Xesar tablet into Xesar 3.0 by continuing with the steps described in section 5.6 Integrating your Xesar tablet into your system.

  • Page 114: Securing The Xesar System Data With The Installation Manager

    Securing the Xesar system data with the Installation Manager Notice: An accessible backup location must be specified for a successful backup. 6.1 Manual backup It is always possible to create a manual backup. To do this, the AdminCard must be in- serted in the coding station and selected.
  • Page 115  2. Step: Name the backup path to specify where to save the backup files. An error message appears upon entering an incorrect path or if no path is entered. We do not recommend keeping the backup data on the system computer or sys- tem drive.

  • Page 116: Automatic Backup

    4. Step: The manual data backup is located at the backup location and is marked with an "M" at the end of the file name. All manual backups remain saved. 6.2 Automatic backup You can also create automatic backups in the Installation Manager. To do this, select one or more of the 3 options for an automatic backup under "Automatic backup"...

  • Page 117: Backup Files

    Backups on starting and stopping the system is only possible with the Ad- minCard inserted and selected. A backup at a defined time is only possible when the system and the Installa- tion Manager are running. Therefore, a time for the daily update must be cho- sen so that a successful backup can be created.

  • Page 118: Restore

    6.4 Restore The software must be reinstalled in the case of a technical error or when changing (PC) hardware. Secure data by making a backup before changing hardware To restore the system, the latest system data backup file is required. We recommend that you make regular backups of your Xesar system.
  • Page 119 2. Step: Delete the system by clicking on Confirm to accept the following warning: The successful deletion of the system data is confirmed. The following steps are necessary to restore successfully: 3. Step: Reinstall the Installation Manager and start it. •...
  • Page 120 4. Step: Add a new system. The new installation must have the same software version as the backup file. It may be necessary to select an older version from the Registry in the Installa- tion Manager to be able to reinstall the backup. The software update can be carried out after the backup installation has been completed.
  • Page 121 5. Step: Enter the system settings of the new systems in the appropriate fields:  • System name  • the path to the latest valid backup file that is to be reinstalled  • the new path for future backups ...
  • Page 122 The following display indicates progress status: • Confirm the successful creation of the system by clicking on • Subsequently you can select and start the system in the Installation Manager on the "Installations" page. • Thus, the system is restored as per the status of the backup file used. (Restored) KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 123: Commissioning Xesar Software

    Commissioning Xesar software Figure119 - Commissioning step by step 7.1 General information on commissioning • New settings or changes must be saved before leaving the respective page. If this is not done then the original settings are retained. • Export of lists: All list views can be printed and exported as .csv or .xls file.

  • Page 124: Settings

    7.2 Settings Figure120 - Tiles settings Security settings: Figure121 - Security settings Depiction of identification media validity and authorisation period: Figure122 - Validity and authorisation period KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 125 • Standard validity period of an identification medium: Preset period of time for which the identification medium is valid after updating at the coding station or at the online wall scanner. The duration can be individually adjusted when issuing identification media. After expiry of the period, the identifi- cation medium becomes invalid and must be updated again at the coding station or on the online wall scanner.
  • Page 126 • Daily execution time: Time of system synchronisation as well as further configu- ration settings of the online reader via the Xesar software (backend). Important: The execution time should be a time when the system is running and the online wall scanner has the online status! (e.g. office hours) •...
  • Page 127 Figure 126 - Settings for the programming device (Xesar tablet) KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 128: User Groups

    7.3 User groups: The user groups define authorisations for users. Figure127 - Tiles for user groups Users operate the Xesar software and manage the Xesar system. It is possible to add as many users as required with authorisation profiles that vary according to their function. These different authorisations are defined in the user groups.
  • Page 129 Example user group "Installation administrator": Has all reading and editing author- isations Figure 129 - User group Installation administrator The authorisations of these predefined user groups can not be changed. However, they can be copied, modified and saved under a new name, becoming the basis for a new user group.
  • Page 130 The authorisations are grouped as tiles on the dashboard. For all group authorisations, select between read authorisations or all authorisations. Figure 149 grouped authorisations KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 131 Figure 150 - User group reception main entrance Important: The user-defined authorisations can be easily assigned to predefined user groups. Special authorisation groups can be generated as required. Please contact your EVVA consultant or the EVVA technical office! KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 132 Possibility to restrict admission authorisation profile: Only the selected authorisation profiles can be assigned by users with the appropriate user groups. Thereby, e.g. users from the user group "Reception" can not assign the authorisa- tion profiles "Chief and Assistant", "Fire Brigade or Master Key authorisation profile" to an identification medium.

  • Page 133: User

    7.4 User Figure131 - Tiles - user Users operate the Xesar software and manage the Xesar system. It is possible to add as many users as required with authorisation profiles that vary according to their function. A new user can be added by the "Add" symbol or the "+". The number of created users is displayed in the tile.
  • Page 134 Figure134 – User overview New user: User name (mandatory): Specify user name and the new user. e.g. Administrator 1 Description: Optionally a description of the new user may be added. Password (mandatory): Enter a password for registration (login). (At least 6 characters, a rating of the password's security level is displayed) Repeat password (mandatory): The selected password must be entered again here.
  • Page 135 Figure135 - New user Download configuration Download the respective user certificate. This is required for secure third-party interface actions. For example, Person data import via the third-party system interface KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 136: Calendars

    7.5 Calendars Figure136 - Tiles calandars The calendar function is used to manage special days (e.g. Christmas, Easter, holidays, company holidays or other special days) during one calendar year. On these special days there are exceptions to the time profiles. The number of calendars is displayed in the tile. A maximum of 5 calendars with a total of 50 different special days can be used.
  • Page 137 Calendar view: Figure138 - Calendar Import calendar: Existing calendars can be imported and processed in .ics or .csv format. Figure139 - Import calendar ATTENTION: You can not import calendars where the current day is marked as a special day. KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 138: Time Profiles

    Furthermore, closing times are set for the automatic termination of a manual office mode (manual permanent opening). If an Office Mode time profile is not assigned to an EVVA access component, then only authorised identification media are allowed. If a time profile is not used in the creation of an identification medium, then there is no access time restriction for this identification medium and thus it has continuous access.
  • Page 139 The "Manual Office Mode" is activated by holding an authorised identification medium twice to the EVVA access component. This is confirmed by optical and acoustic signals. (see system manual) The "Manual Office Mode" is ended manually by connecting an authorised identification medium twice to an EVVA access component, or automatically at the defined closing time.

  • Page 140: Office Mode Add Time Profile ("Permanent Opening", Applies To Evva Access Components)

    7.6.1 Office Mode add time profile ("permanent opening", applies to EVVA ac- cess components) Access is possible without authorisation at the defined times. The EVVA access component is ready to open the door. You can create a maximum of 24 time series.
  • Page 141 This ensures that a manually started Office Mode is safely terminated at the defined time. The Manual Office Mode can only be activated on defined EVVA access components, using authorised identification media, by presenting the media twice to the EVVA access compo- nent.

  • Page 142: Add Time Profile (For Persons And Identification Media)

    e.g. closing time Sun - Sat 20:00 Figure147 – Closing time Exceptions of the closing time series: The closing time can be changed on special or public holidays. Figure148 - Exceptions to the time series 7.6.2 Add time profile (for persons and identification media) Limits to authorisations: You can create a maximum of 24 time series e.g.
  • Page 143 Time series exceptions: Time series exceptions define deviations from the defined time series. e.g. Holidays on which changed access times apply or when access is generally prohibited. e.g. "No time series" means no access during the holidays defined in the calendar. All existing calendars are displayed.

  • Page 144: Access Points

    7.7 Access points Figure 151 – Tile Access points All access points with EVVA access components of a Xesar system are created and defined under " Access points ". An access points can be a door or also another application, e.g. a lift.

  • Page 145: Describe Access Points

    "Long" is defined by the respective person or the ID medium and, if authorised, triggered on the EVVA access component. The assignment of the release period to the person and an identification media takes place in the Person & Identification settings.

  • Page 146: Zones

    Figure156 - Time profile (installation location) Office Mode Office Mode is the time-controlled permanent opening of the EVVA access compo- nent. Access is possible without authorisation at the defined times. For example, business traffic during business opening hours Shop Mode...
  • Page 147 Attention: The import of a Xesar 2.2 system with 96 zones does not function. Remedy: Remove an area from the Xesar 2.2 system and then import the system. Figure158 - View of zones Display „Offices“ zone: Name (mandatory): Name of the zone Description: For a more detailed explanation Access points Depiction of the selected access points Figure159 - Display "Offices"...

  • Page 148: Authorisation Profiles

    Selection of access points: The selection of the access points for the zone is made by marking the first column. Figure 160 - Selection of access points 7.9 Authorisation profiles Figure 161 – Authorisation profiles tile Authorisation profiles describe spatial and temporal access restrictions for indentification media.
  • Page 149 Description: For a more detailed explanation, e.g. shift worker on the late shift Manual Office Mode: When this mode is activated, all persons or identification media have the authorisation to activate the Manual Office Mode on authorised EVVA access com- ponents.
  • Page 150 Figure163 – Authorisation profile "example - shift worker" Selection of access points: Figure 164 - Selection of access points KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 151: Persons

    Access to the selected access points: Figure165 - Access to selected access points 7.10 Persons Figure166 - Persons The "Persons" area defines all relevant information on the persons authorised in the sys- tem. Persons in a system can be assigned one or more identification media with different authorisation profiles.
  • Page 152 Display persons list: Figure167 - Diaplay persons list Given name (mandatory): Person's given name Surname (manatory) Person's surname ID: Name as initials How many identification media are issued: Number of persons assigned identification media Standard authorisation profile: A selected profie from the authorisation profiles is taken as the standard authorisation profile and assigned to the person's identification medium.

  • Page 153: Add Person

    Release duration: "Short" or "Long" is selected and activated via authorised access to the EVVA access component Personal data (Event log): Type of event recording: Events can be recorded indefinitely...

  • Page 154: Identification Media

    Figure 169 - Tile identification media Identification media are used both to open doors when authorisation is available, and to transport system-specific security data between the EVVA access components and the management software via the virtual network XVN (Xesar virtual network).
  • Page 155 After confirmation, another page appears with the following display and input fields: Figure171 - Assign identification medium Status: Shows the current status regarding validity and actuality. Validity period: Indicates from when until when the identification medium is valid. Validity period Selection of the time period until when the identification medium has to be updated via the online wall scanner, or via the coding station (validity extended).

  • Page 156: Existing Identification Medium

    Figure172 - Individual authorisations 7.11.2 Existing identification medium Placing an existing identification medium on the coding station causes the following input window to open: Status: Status of the identification medium # Status Visualisation Explanation Insecure disabled identification There still insecure access medium points.
  • Page 157 The medium has been deactivated, Deactivated identification me- there are no unsafe access points dium more, and the calendar is no longer important. Validity period: Time range of validity and date until which the validity of the identification medium must be extended; this is done by stopping the online wall scanner or by placing the medium on the coding station.
  • Page 158 Figure174 - identification medium indiviudal authorisations „Issuing protocol“ button: An identification media issuing protocol with all relevant data is generated as a file in .pdf format. This can be printed out and confirmed by the recipient with his signature when taking over the identification medium.

  • Page 159: Adding A New Evva Access Components

    7.12 Adding a new EVVA access components The EVVA access components are delivered in construction mode. To start the Xesar sys- tem, the component must be added ("intoduced”) to the system. After defining the installation location in the Xesar software, the component is “Prepared for installation”.
  • Page 160 Figure 178: Windows | LAN connection • In the window, select Internet protocol version 4 (TCP/IPv4)  and click prop- erties . Figure 179: Windows | IP address (PC) • Now configure the IP address and the Subnet mask of the PC that you are using for the configuration....

  • Page 161: Commissioning A Xesar Network Adapter

    Please contact your system administrator if you encounter any issues during setup. 7.13.2 Commissioning a Xesar network adapter Figure 180: Xesar network adapter | Jumper position • Check the jumper position  of the Xesar network adapter. Both jumpers must be set to OFF (bottom position). Figure 181: Xesar network adapter | Connections •...
  • Page 162 • Now open your computer's Internet browser. • In the browser, enter the standard address of the Xesar network adapter - these can be found on the bottom of the device and are set to 192.168.0.100 by default. Notice: configuration page fails open,...
  • Page 163 192.168.100.1 Figure 184: Xesar network adapter | Parameter settings Attention: The number "100" may only be used once for "Local port, Socket mode" (serial + digital)! KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.
  • Page 164 You are now on the Xesar network adapter configuration page. As shown on the illustration, complete the white fields. Configure the fields highlighted in yellow as follows: • address defines address Xesar network adapter. Please note that changing this address and clicking Update (or confirming with the ENTER key) means the network adapter can exclusively be opened and configured using this ad- dress.

  • Page 165: Xesar System Management

    Xesar system management All installations (Xesar software, Periphery Manager, Installation Manager, etc.) have been completed successfully. The system management provides an overview of the daily use of Xesar software and its management interfaces (dashboards) and features. 8.1 Starting and quitting Xesar To start and stop Xesar, click the link (server) provided by your administrator or click on the "Go to"...
  • Page 166 The white field is the support field. It provides useful downloads, such as documents (e.g. this system manual) or files intended for exchange with your national EVVA technical office. KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 167: Xesar Filter Functions

    8.3 Xesar filter functions For a detailed evaluation or a simplified representation, lists in the various menu items can be filtered according to one or more criteria. In addition, filter settings that are commonly used can be saved for easier operation. 8.3.1 Manual filter: ...
  • Page 168 Apply preset filter:  click on the preset filter to deactivate it  Filter criteria are displayed  Display filter results as a list   click the Preset Filter button close the filter The number of Filter Presets per list is not limited. KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 169: Column View

    8.3.3 Column view The list view can be customised according to needs and the size of the display. Clicking on opens a selection window in which columns can be shown or hidden. Like- wise, the number of maximally displayed "lines per page" can be set. The settings can be saved or reset.

  • Page 170: My Profile

    8.4 My profile Figure 190 – My profile The "My profile" menu item is located in the top right corner of the Xesar dashboard. Figure 191 – My profile "My profile" directly provides information about which user has currently logged in (user name) and the system.

  • Page 171: Keycredits (Units)

    8.5 KeyCredits (units) Figure 192 - Display Keycredits The dashboard shows the current credit and KeyCredits to be deducted. Changes subject to a charge are: Creating new identification media Changing authorisations Notice: blocking or withdrawing authorisations is free of charge. Figure 193 –...
  • Page 172 After having confirmed you can carry out additional changes to authorisations and at the end you can confirm all KeyCredit deductions at once. The dashboard lists the current information: Figure 195215 – KeyCredits, changes subject to a charge See the following section for information about how to add KeyCredits: 12→Xesar Instal- lation Manager 12.

  • Page 173: Support

    Xesar version is installed together with the Installation Manager and Periphery Manager and the Tablet APP  Supplied firmware versions for Xesar components  Link to the general licence conditions of EVVA with download link Figure 198 - About Xesar KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 174: Xesar Help

     Link to the Xesar produkt page with information on the driver download for the coding station  Link to the Xesar EVVA support page. We would like to help you here. Figure 199 - Xesar help 8.6.3 Updates ...

  • Page 175: Maintenance Tasks

    Download of the support files Figure201 - Support information In case of an error, please download the anonymised system data file for error anal- ysis and send it to the EVVA Technical Office. 8.7 Maintenance tasks Figure 202 – Configuration tasks tile...

  • Page 176: Firmware Not Up To Date

    the access points is not needed. However, from a technical point of view, it is advanta- geous when the service technician has the access authorisation for the access points con- cerned. For this, he must be given an identification medium with the appropriate access authorisations.

  • Page 177: Coding Stations

    The "Battery warnings" field turns yellow and shows the components in which the battery is low and must be replaced. Notice: maintenance tasks are created for all affected components. 8.10 Coding stations Figure 205 – Coding stations tile The Coding stations sections illustrates all active and inactive coding stations in use. Attention: an active coding station is required to issue or update identification me- dia! Notice: In order for the Xesar software and thus your system to be connected to...

  • Page 178: Insecure Access Points

    8.11.1 Insecure access points Figure 207 – Insecure access points The insecure access points field turns yellow if an identification medium has been disabled and the blacklist at access points is not up to date. The current blacklists through the XVN (see: →8.15Xesar virtual network (XVN) or by synchronising the software and access components using the Xesar tablet.

  • Page 179: Identification Media - Bulk Processing

    8.12.1 Identification media – Bulk processing Xesar offers a function to quickly and easily add several identification media to the Xesar system. Bulk processing options have been described in "Identification media". Open the  " Add – bulk processing" menu item to open batch processing. Figure 209 –...

  • Page 180: Revoke Identification Medium

    Click "Stop bulk processing" to once again stop bulk processing. Figure 211 – Deactivating batch processing 8.12.2 Revoke identification medium Figure 212 – Withdrawing identification medium Identification media can only be revoked when it positioned on the coding station. Only then is the "Revoke"...

  • Page 181: Withdrawing Authorisations From Identification Medium

    8.12.3 Withdrawing authorisations from identification medium Figure 213 – Withdrawing authorisations from identification medium  "Withdraw authorisation" function is available for non-critical identification media (e.g. the identification medium is securely returned, but the user no longer has access, such as external companies within the building). Consequently, a blacklist entry is not created when authorisations are withdrawn from identification medium and a warning is not shown on the dashboard.

  • Page 182: Identification Media That Cannot Be Written To

    Figure 215 – Dashboard blacklist A maintenance task is created for each installation location and the "Unsafe installation location" and "Unsafe identification media" fields change to yellow. 8.12.5 Identification media that cannot be written to Figure 216 – Identification media that cannot be written to The menu item "Non-writable identification media"...

  • Page 183: Insecure Identification Media

    Tip: Grouping together zones increases identification media's memory capacity. 8.12.6 Insecure identification media Figure 217 – Insecure identification media Unsafe identification media are created by "Blocking" identification media. In this status, the disabled identification medium can still open access components. See: →8.12.4Blocking identification medium (adding them to the blacklist) 8.12.7 Identification media not up to date Figure 218 –...

  • Page 184: Event Logs

    8.13 Event logs Xesar distinguishing two types of event logs: Event log System event log 8.13.1 Event log Figure 220 – Event log The event log illustrates the log entries of events that have been triggered by interaction with electromechanical locking systems (e.g. access or rejection at access components). See: →...

  • Page 185: System Event Log

    8.13.2 System event log Figure 222 – System event log The system event log documents any actions users carry out. This means that it records events that are triggered by management tasks. In contrast to the event log it does not record events resulting from interaction with the electronic locking system.

  • Page 186: Xesar Tablet (Programming Unit)

    8.14 Xesar tablet (programming unit) Figure 224 – Xesar tablet (programming unit) Open the Xesar tablet menu item to view all programming units linked to the system. Figure 225 – Reporting loss  Use the "Report loss" button to remove the tablet from the system. 8.14.1 Xesar tablet app The home screen provides an overview of all unresolved maintenance tasks, shows the...
  • Page 187 Click the three small dots to open a drop-down menu for: • Show all All tasks are shown • Hide completed Any completed tasks are not shown • Hide synchronisation tasks Synchronisation tasks (collect logs, set time) are hid- den. Only configuration tasks (configuration changes) are displayed.
  • Page 188 8.14.1.1 Update firmware The firmware of access components can be updated both in construction site mode and when installed. Figure 229 - Update firmware Figure 228 – Requesting the firmware ver- sion If the component is in construction mode, connect the Xesar tablet to the access compo- ...
  • Page 189 8.14.1.2 Components' battery status Connect the programming unit to the component to manually check the battery status of a component using the programming unit. Figure 230 – Showing the battery status Select the button  Show battery status in the dropdown menu. The battery status is then shown on the programming unit.
  • Page 190 Figure 233 – Enter initionalisation PIN  Enter the initialisation PIN and a progress bar opens. Notice: the initialisation PIN is in: → 7.2Settings Figure 234 – Successful baptism KPM.X.Systemhandbuch_X3.0.EN.V1.9 | Subject to misprints and technical changes.

  • Page 191: Xesar Virtual Network (Xvn)

    8.15 Xesar virtual network (XVN) Xesar virtual network uses issued identification media exchange information between software and doors to always keep the system up to date. Figure 235: System overview | Virtual network Identification media are provided with update information (blacklist or online wall readers) from a central coding station.

  • Page 192: Transferring Access Events Using Identification Media

    8.15.1 Transferring access events using identification media The most recent access events (access granted, access denied, battery low, etc.) of the door component are transferred to identification media as part of every second identifica- tion process, e.g. when a door component is unlocked using identification media. As soon as the identification medium is held to the coding station or online wall reader, all events are transferred to the Xesar software and the memory on the medium is cleared.

  • Page 193: Transferring "Unlocking Attempt By Medium" Notifications

    8.15.3 Transferring "Unlocking attempt by medium" notifications A medium that has been disabled in the software can open the corresponding door com- ponents as long as it is still valid. This type of information is critical to security and the data is collected by other identification media within the system before it is transferred to the Xesar software using the coding station or online wall reader.

  • Page 194: Transferring The Battery Status Using Identification Media

    8.15.5 Transferring the battery status using identification media Battery information is also transferred to the Xesar software using the identification media circulation via the virtual network. As a result, administrators are notified in due time if batteries must be replaced. System administrators have the option to indirectly influence update cycles using identifi- cation media's...
  • Page 195 • In the AdminCard Operations window, select Exchange card and enter the instal- lation key, card number and card signature from the installation information sheet. These data can be found on the installation information sheet, which you printed out during the first installation. Figure 238 –...

  • Page 196: Revoking The Process Of Adding A Component

    IMPORTANT: Make sure that you perform a manual backup in the Installation Otherwise, a restore will not fit the Manager after the AdminCard exchange. new AdminCard. 8.17 Revoking the process of adding a component If you have added an incorrect component to the installation location, you can once again remove the component here.

  • Page 197: Removing Components (Resetting To Construction Mode)

    8.18 Removing components (resetting to construction mode) Select delete "EVVA component" if you would like to once again remove a component and continue to use it. Figure 241 - Removing components ATTENTION: if you would like to once again install the component in a system, do not click "Remove faulty EVVA component".

  • Page 198: Force Component Removal (Component Faulty)

    Force component removal (component faulty) If a component is faulty, go to Access points and select the corresponding installation location. Scroll down to the EVVA component and select "Remove faulty EVVA component". Figure 243 - Component defective - force removal 8.20...
  • Page 199 Figure 246 – Online wall reader event log Note: The Xesar 3.0 functionalities of the online wall reader are not available in X2.2 (e.g., online configuration, timed online configuration, door contact). Only the door button can also be used in X2.2, but the event is not displayed in the X2.2 software.

  • Page 200: Potential Errors

    Tip: Quit and restart the docker 8.21.3 Update to Xesar 3.0 After having imported a Xesar 2.2 system to Xesar 3.0, EVVA components may not be synchronised with the Xesar 2.2 system. After having successfully imported, you must consistently work with Xesar 3.0.

  • Page 201: Expired Certificates (Xesar Tablet, Browser)

    8.21.10 Xesar Lifetime in Xesar 2.2 Do NOT activate Xesar Lifetime in Xesar 2.2 (i.e. prior to export/import to Xesar 3.0)! Otherwise merely 17 KeyCredits would be added in Xesar 2.2. 8.21.11 Blocking the firewall / preventing the import As a rule, you must currently take into account three known aspects: •...

  • Page 202: Xesar Tablet Error (Ares Fx716M)

    Workaround: Close and restart the Installation Manager. 8.21.17 No dashboard display in the browser If the Xesar 3.0 software display no data on the dashboard, this may be due to unusually high CPU utilisation. Remedy: Stop and restart the installation in Installation Manager.

  • Page 203: Deactivate The "Certificate Propagation Service

    If you install a coding unit with 2 wall readers, the two access points are connected to each other. This connection will endure even if the EVVA components are removed. After the two EVVA components have been removed, the status "prepared for installation" for CU2WL is reached again.

  • Page 204: Table Of Figures

    Table of figures Figure 1: System architecture (sample image) ............13 Figure 2: Xesar access components (sample image) ..........13 Figure 3: Xesar escutcheon (sample image) .............14 Figure 4: Xesar escutcheon (sample image) .............15 Figure 5: Xesar handle (sample image) ..............19 Figure 6: Xesar handle (sample image) ..............19 Figure 7: Xesar cylinder (sample image) ..............21 Figure 8: Xesar thumb turn (sample image) .............22 Figure 9: Xesar cylinder (sample image) ..............24...
  • Page 205 Figure 47 – Download Installation Manager for software ..........66 Figure 48 - Xesar Installation Manager ZIP file ............67 Figure 49 – Installation Manager application ............67 Figure 50 – Installation Manager warning message ...........68 Figure 51 – Installation Manager window ..............68 Figure 52 –...
  • Page 206 Figure 113 – Xesar tablet APK file ................. 111 Figure 114 – Xesar tablet – Xesar 3.0 APP ............. 112 Figure 115 – Xesar tablet – installing the Xesar 3.0 APP .......... 112 Figure 116 – Synchronising the Xesar tablet ............113 Figure117 - Settings for system backup ..............
  • Page 207 Figure143 - View of Time Profiles................140 Figure144 - Error report time frame ..............140 Figure145 - Add Office Mode time profile ............... 141 Figure146 - Time series exception ................ 141 Figure147 – Closing time ..................142 Figure148 - Exceptions to the time series .............. 142 Figure149 - Add time profiles ................
  • Page 208 Figure 191 – My profile ..................170 Figure 192 - Display Keycredits ................171 Figure 193 – KeyCredits: no changes ..............171 Figure 194 – KeyCredits subject to a charge ............171 Figure 195215 – KeyCredits, changes subject to a charge ........172 Figure 196 –...
  • Page 209 Figure 239 – Replacing the Admin Card ..............195 Figure 240 – Revoking the process of adding a component ........196 Figure 241 - Removing components ..............197 Figure 242 – Remove Xesar tablet component ............197 Figure 243 - Component defective - force removal ..........198 Figure 244264 –...

Table of Contents