Label: ecostruxure access expert - Building Automation Knowledge Base

Issue How to Prepare a Server for Access Expert Premise Software Product Line Access Expert V2 On-Premise ONLY Environment Windows Server 2012 and above Cause There is no documentation on how to prepare a server for a Premise Install. Resolution In order to do this there are several pieces that needs to be followed on how to configure it correctly. First step is to install the server software, in this case Windows Server 2012: Configure the local server Add Roles and Features, Click Next Server Selection, select a server (should be the local machine) Click Next a few times, to complete this part Scroll down to the bottom and select WebServer IIS and add all features Click Next to complete this part Click on .net Framework 4.5 Features Check the box for ASP.net 4.5 Expand WCF Services Click on HTTP Activation, Add Features Scroll down to Message Queuing Expand and scroll down to SMTP Server - Add Feature, Click next a couple of times to install Once completed, Close and Exit Installing SQL Server Open media where software is located and launch the installer Select the option to Install a new instance and click Next Select Install DB Engine and Mgmt Tools, click Next Select Default instance, click Next Use same service accounts, click on Server Configuration Tab Add - License Administration as a Group Select the Data Directories Tab, change where the data files are stored by default Create new Folders for SQL Data, SQL Logs Change Directory Paths as well for Temp Create new folder for Backup Click on next and Install Once finished, close out to complete the install. Enable sysadmin in SQL for NTAuthority Installing Keep Here is a link of a video that goes through this process as well. Premise Installation of Keep for Access Expert Download Keep By Feenics software from the Software Downloads Tab on the Feenics training site http://www.feenics.com/training/courses/technical-certification/ Browse to the location and launch Keep Installer, click on Next When complete, Test Db Connection, once it passes, click on Next Make sure all elements are selected, click on Next to install Launch the Keep Instance Management, click on Connect Connect to the local Host Give the site a name that will used for the instance (if this name is changed, it would require a new instance license key to be generated) Give a url to the name db name with username and password (admin/admin) Change the path for file location and DB Log location from earlier steps Save configuration and Close On the Web Browser, Go to Tools - IIS Manager Add a new Binding, check the Box for "Do not show messages" Delete the default website Click on created website and select Bindings Click on Add - use same name in original browser Start IE Browser (url) created earlier Load license from Activation Code and Activate Log in to the system. Host File If the browser does not start and fails to open the page, then modify the Host File to contain the IP address of the server as well as the URL of the instance Go to C:\Windows\System32\drivers\etc hosts Modify the file by entering the IP address of the server as well as the URL Save and close. Open up the page again and it should allow the application to be started.

Issue During installation of the Keeps software an exception is thrown in ExtentPlaceholderCreator. Environment Keeps On Premise Cause Microsoft SQL Server issue. Problem has been seen with MS SQL SERVER EXPRESS 2012 SP3 Resolution Edit the 'c:\Websites\Feenics\'web.config' file and insert the text below at the exact location shown in the screen shot below. --INSERT THIS TEXT <dependentAssembly> <assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" /> <bindingRedirect oldVersion="1.0.0.0-11.0.0.0" newVersion="10.0.0.0" /> </dependentAssembly> --END OF INSERT TEXT                                                    

Issue Where to go to download the Access Expert Device Administrator application. Product Line Access Expert Environment Server 2012 SQL 2012 and above Premise Install V2 Hosted V2 Applet V3 Cause There is no documentation on where to go to download the Device Administrator and how to program the SSC to communicate with the selected application. Resolution The following steps describe where to go and download the software and how to use it to program an SSC: Go to the EcoBuilding Exchange In the search field type Device Administrator Select the Access Expert Device Administrator and download to any location Browse to location and double click execute to run and install the program Accept Agreement and click next to continue installation Click Next to start installing the software Select the location where the file will be installed Successfully loaded software To complete installation, click on Finish Connect the device to a network switch that is open to the internet and launch the application by opening Access Expert device Administrator from the Schneider Electric group in All Programs Launch the application  Right click on the usb line or click on the green arrow to the top left to upgrade the software Once upgraded successfully, Right click again on the line and select properties then select the Ethernet 1 ConfigurationTab Select applicable choice whether it is DHCP or Static addressing being used and click on OK. Once the device comes back Online, select the DIP Switches Tab and check the box for Default User Using the IP address given from step number 13, open up IE and browse to that address Once opened, configure the SSC per Setting up an SSC (System Security Controller), EP1501 and EP1502 Mercury Controllers.

Issue Need to mirror a switch port in order to capture controller data with Wireshark.   Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Cause Need a step-by-step guide to set up a mirrored port and an understanding of how it works.  Resolution View the attached video.   Use the link to the original post in Area360 to get written instructions.

Issue How to configure Global I/O across controllers in Access Expert Product Line Access Expert Environment Access Expert Win 8.1 and above Version 3 Cause There are no guidelines on how to control points across controllers on a Version 3 instance. Resolution Setting up Global I/O utilizes Alarm Definitions and behaves similarly to Triggers and Procedures. The event source of the Alarm Definition is the Trigger for the action. The Alarm Action will act as the Procedure that occurs after the trigger has been activated. Example: In the example below, when the input on controller 1 is activated, the output on controller 2 will be pulsed. The Alarm Action of pulsing the output is set up on the Alarm Actions page and uses a Trigger and Procedure to Execute the pulsing of the output. If you are attempting to do Global I/O in Version 2, this feature is not supported. It will only work in Version 3. For this example, we are pulsing the output on Controller 2 from input on Controller 1 for a duration and we need two triggers to accomplish it. The following steps will describe how to configure them:    Step 1: Create a Trigger and Procedure for the Input on the first controller and assign the source accordingly.   Step 2. Create the Second Trigger on the Second Controller. Step 3: Create an Alarm Action to Execute this procedure and assign it accordingly. Step 4: Create the Alarm Definition. The Event Source is the object that will do the “Trigger”, the Alarm Action is the “Procedure” and the Event type is the triggering action for the Source. In this example, the filter query is setting this action to only occur when the input is activated instead of any input status change. 5. Trigger the Alarm and look at Hardware Status and Live Monitoring Window.

Issue Unable to locate where to configure the SMTP Server in an Acess Expert V3 Instance. Product Line Access Expert Environment V3 Premise Cause The earlier versions of the on-premise server/client did not have SMTP functioning properly. As a result, the tab to Configure the SMTP server settings was left out of the software. Resolution Newer versions of the software have SMTP functionality working properly. After upgrading the Server and Client software to the newest versions available, the SMTP Configuratiuon tab will be available as shown below.  Note: For Instructions on how to upgrade the Premise Server and Client software, please see Upgrade Premise Software to Latest Version.

Issue Access Expert is able to communicate down to the SSC (a reboot works) but the SSC won't come online and its status shows as unknown. Product Line Access Expert Environment SSC Cause In IIS the binding has been configured incorrectly. (On Premise ONLY) Mercury port (3001) blocked.  Resolution This is what a properly configured binding looks like. (On Premise ONLY) Reference How to verify ports needed for AX-SSC communication with the Access Expert server are open from within the AX-SSC itself to check status of the Mercury port, if block work with IT department at the site to have it unblocked.

Issue It is unclear how to unlock a door from a graphic. Product Line Access Expert Environment V2   Hosted Instance & Premise Install See Premise Installs on Windows OS for supported Windows OS Cause In order to unlock a door from a graphic, the door reader must first be added to that graphic. Resolution To add a door reader to a graphic, do the following: From the “General Configuration” tab navigate to “Floorplans” and select the correct floorplan, then go to the hardware tab. Add the appropriate reader by clicking the green +, then drag it to the correct location on the floorplan graphic. Save the change to the floorplan graphic. From the “Access Control” tab navigate back to the newly updated floor plan. Now you can right-click on the reader and select “Unlock”. This will unlock the corresponding door.

Issue Where are the reports of fixed issues/bugs for the various product lines located? Product Line TAC Vista, TAC INET, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, EcoStruxure Building Operation, EcoStruxure Building Expert, Access Expert, Security Expert Environment Technical Product Announcements Cause TPAs contain information of changes made per version of the different product lines. A TPA may report enhancements and/or broken functionality. Resolution Navigate to Exchange Extranet to view all TAC Vista documents tagged as TPA. The documents will be listed in reverse chronological order. Log in to view these documents. See Register for The Exchange Download Center for more information on registration.

Issue Directions on how to commission an SSC and Mercury Controllers right out of the box. Product Line Access Expert Environment Windows 7 Windows 8 Windows Server 2012 Windows Server 2014 Version 2 Version 3 Cause No directions on setting up an SSC and Mercury Controllers to get it online. Resolution Commissioning the AX-SSC Here is a link to a video that describes how this should be done as well that can be accessed from the following link: Commissioning a new SSC 1. Connect the Access Expert Device Administrator to the SSC using USB cable then go to ‘Network settings’ to configure the device’s IP address etc. 2. In the ‘Ethernet 1 Configuration’ tab, configure the IP settings (In this example, we are using a static IP address). Make sure to configure the DNS so that the URL of your hosted instance can be resolved. Take note of the SSC’s MAC address which will have to be entered when adding the SSC in Access Expert. 3. Enable the default user in the SSC in order to be able to login with a web browser to configure additional communication parameters. NOTE: The default user will stay enabled for 5 minutes then the checkbox will automatically deselect. Once logged into the SSC you can create a new level 1 user so you don’t have to rely on the default user again. 4. Point a web browser to the SSC's IP address and login using the default user (admin/password). After logon, verify the IP settings configured from the Device Administrator, you can edit the settings here if necessary. 5. If using a Mercury EP1501 or EP1502 Controller, use the MAC address and connect to the device. Once logged in, go on to the next step 6. Go to the ‘Host Comm’ page. This is where you will configure the SSC to be able to communicate to the Access Expert database instance in the cloud. 7. Configure the connection type for ‘IP Client’. Enter the URL for your DB server instance or the hosted cloud server as shown in the above example. 8. For V3, the Host Name would be us.accessxpert.com (ax.accessxpert.com also works). If premise, then it would be the IP of the Server. 9. Note the port number used for communications and make sure this port is open; you can also configure an alternate host port as a backup. 10. Usually it is 3001, if that is blocked by the clients Network, then use Port 443. 11. Click Accept then ‘Apply Settings’ followed by ‘Apply Settings Reboot’.  

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue This is a project to support integration with the Schindler PORT system. It should be deployed on a customer site to directly connect to the Schindler PORT firewall and be configured to connect to the customer instance on the Access Expert (AX) side to add, update, or remove people from Schindler PORT based on which access levels they belong to in AX.  Product Line EcoStruxure Access Expert Environment Access Expert Hosted software Cause Please read all the instructions to properly deploy and configure this service. Resolution Card formats The Schindler reader produces a 16-digit hexadecimal value after reading a card and sends it to the Schindler Port system for validation. The value from the Schindler reader is a different value from what is entered as the encoded card number in AX. Therefore, there needs to be an additional entry of the hexadecimal value in AX in the Hex Value field of a card assignment. The Hex Value will be sent to the Schindler Port system as the card number so that it matches with the Schindler reader value to get access.   To find out what the Hex Value needs to be, the process was to send Schindler 10 cards from a particular project then they get back to us with the correct hexadecimal representation of those cards. This will need to be done between you and Schindler for your project.   Prior to version 22.3.1 of the AX Schindler service, the service was used to encode the Encoded Card Number from AX using a 16-digit value of 0100000020000000, then replace the zeroes at the end with the hexadecimal representation of the Encoded Card Number. The service will still do that if no Hex Value is specified for a card but that may not be the correct encoding for your project.   In short, you need to enter the Hex Value of a card assignment in AX as the value that is generated by the Schindler card reader. Deployment The Schindler service is deployed using Docker. If you are using Windows, we recommend having WSL2 installed and enabled for Docker. The installer needs to pull the images for both Seq (for logging) and the Schindler service from the Docker hub.   The installer also needs to create a Docker network called ax-net. To create the network, execute: docker network creates ax-net To get the Seq image: docker pull datalust/seq To get the Schindler service: docker pull feenics/feenics-keep-schindler To install Seq (replace /path/to/seq/data with the actual path of a directory on disk, this is the linux notation): docker run -d --name seq --restart unless-stopped --network keep-net -e ACCEPT_EULA=Y -v /path/to/seq/data:/data -p 5341:80 datalust/seq To install Schindler (env.txt is in the same directory where you are executing the docker run in this case): docker run -d --name feenics-keep-schindler --restart unless-stopped --network ax-net --env-file env.txt feenics/feenics-keep-schindler Environment configuration The following environment variables can be specified in a file (env.txt in the example above) that is passed to the container when launching it from Docker. In the file, each of these properties will be followed by an equal sign then its value. ClientInstance= ClientUsername= ClientEncryptedPassword= ClientWSS= ClientAddress= Company= TagName= SchindlerServerIp= SchindlerServerPort=   Below is the description of each property: ClientInstance - the name of the client instance ClientUsername - the username to login the client instance ClientEncryptedPassword - the encrypted password obtained from the service password utility ClientWSS - the address of the MQTT event publisher (for USA: wss://keepevents.feenicshosting.com/mqtt) ClientAddress - the address of the API (for USA: https://keepapi.feenicshosting.com) Company - the company name as configured in the PORT system TagName - the tag name that will be assigned to the Schindler access levels in Access Expert SchindlerServerIp - IP address of the Schindler PORT firewall SchindlerServerPort - Port to use to connect to the Schindler PORT firewall Password The password in the environment configuration needs to be encrypted. The service has an embedded encryption utility. If you start the service with an additional parameter called "password", it will run the password encryption utility instead. Copy the encrypted password and add it to the configuration. To run it, execute the following: docker run --rm -it --name feenics-schindler-utility feenics/feenics-keep-schindler password The --rm will remove this container after it exists so you do not have to delete it manually.   Permissions The service user needs to have permission to read access levels, read people, read event messages and publish all Schindler event types. This is done by creating a group that has those permissions and assigning that group to the service user in Access Expert. The service will monitor the changes in the current instance and all the instances below it in the hierarchy.   Operation The Schindler PORT integration limits the configuration capabilities that can be performed from AX. We are able to add, update, or remove people from profiles in PORT. The Schindler PORT system has profiles defined with particular access to certain floors. These profiles need to have access levels in AX with the exact same name as the profile in order to add, update, or remove people from these profiles in PORT automatically. An access level matching a profile needs to be tagged with a tag name agreed upon and configured in the Schindler service (TagName). A person can only be in ONE profile in the Schindler system. This means that a person can only be in one access level tagged for Schindler sync. If a person is in more than one Schindler tagged access level, only one of the access levels will be chosen. If a person needs to have access to additional Schindler access levels, this needs to be performed from the Schindler system by defining a profile with all the required access and then adding an access level in AX with that profile name and Schindler tag. The Schindler service listens to changes in people and checks if they belong to a Schindler tagged access level then sends an update to Shindler PORT (first name, last name, 3 card assignments, profile name, start and expiry date) PORT only supports one start and expiry date for all three cards so we take the union of the three The Schindler service also listens to changes in access levels that have the defined TagName, whether a Schindler tag was added or removed to either send or remove the people in that access level from the Schindler system Warning: DO NOT delete an access level that has a Schindler tag. You need to remove the tag first in order for the service to know which updates it needs to send to PORT. Schindler command and response numbers (logged in Seq) The first three numbers in the command are an index, it is incremented with each command sent, and the PORT systems reply with the same command index. The next two numbers are the command type or the reply type as follows: SendAlive = "00" SendAliveSuccess = "01" ChangeInsertPerson = "06" ChangeInsertPersonSuccess = "03" ChangeInsertPersonError = "07" DeletePerson = "08" DeletePersonSuccess = "05" DeletePersonError = "09"   Important Add a permission restriction that an access level tagged with the Schindler tag cannot be deleted. This is important because we need to remove the people in Schindler PORT before deleting the access level. The workflow would be to delete the Schindler tag first, then you are allowed to delete the access level.   Recommendations The enterprise should review all access levels tagged with the Schindler tag to audit the entities that are giving elevator access. The enterprise creates the profile (access level) in the PORT system. If the tenant has a shared instance, the enterprise informs the tenant of the access level name and the Schindler tag to automatically send their people to the PORT system.

Issue The Zenitel integration to Access Expert provides the ability to add Zenitel ICX-500 controllers and stations for interaction with intercom devices and monitoring Zenitel events. In the Access Expert Windows Client, Zenitel Exchanges are accessible from the Intercom tab within the Hardware Provisioning section. The associated list of stations will appear when selecting and opening an Exchange. Product Line EcoStruxure Access Expert Environment Access Expert Hosted software Cause While trying to integrate a Zenitel intercom system to Access Expert there are some very specific steps that need to be followed Resolution Zenitel Exchanges Exchanges are used to group together and connect a specific set of Zenitel Stations. Through the Exchanges list, the following functionalities and properties are accessible: Add an Exchange: To add an Exchange, navigate to the Exchanges list and click “Create Exchange” in the upper left-hand corner. A dialogue will appear, prompting for a Display Name and MAC Address. Additional properties and information are available for viewing on the Exchange document once it’s been added. Note: It is important that the MAC address is valid. This is how the stations connect and populate in the instance. Note: The MAC address is not editable in the Exchange document after creation. Stations List: Each Exchange document has a read-only list of Stations connected to it. The system automatically populates the list based on Stations with a connecting MAC Address. This list is automatically updated with the most current available stations.   Zenitel Stations Stations are used to make calls. Stations can be accessed via the Exchange to which it’s connected, the global search bar, or the hardware tree. The Station contains the following properties: Display Name (Editable): This is the editable display name associated with the station. Connected To (Read-Only): Display name of the connected Exchange Configured Name (Read-Only): This is the non-editable original display name of the station configured by the ICX-500. Exchange Number (Read-Only): Number of the associated Exchange. Directory Number (Read-Only): Number to dial to reach this station. Connected Reader (Editable): Reader associated with the Station. Users may specify a reader in case they need to perform actions on surrounding hardware. Cameras/Views (Editable): Multiple cameras and views may be added via the Cameras tab. Reader functionality: Within the Stations form, users may specify a connected reader. Associated functionality to the reader is accessible directly through the “Actions” dropdown list or in the context menu when right-clicking a station that has a connected reader attached.   Functionalities for the associated readers include: Pulse Connected Reader Turn Connected Reader to Online Mode Unlock Connected Reader Lock Down Connected Reader Reset Connected Reader Floor Plans Edit Floor Plan: Stations may be added to floor plans. In the left-hand list of Available Hardware, all stations within the current instance will appear and may be added using the plus button to the right. At the top of the available hardware, a station icon exists for filtering.   View Floor Plan: When viewing a floor plan with connected stations, the station's alarm status will appear in real-time. The appropriate statuses and line states of the stations are also displayed and changes occurring with the stations are updated on the floor plan accordingly.   Hardware Tree Stations can be accessed via the hardware tree and can be filtered from the top of the list via its icon. The color of the Station object is used to determine its state (Green for Online, Red for Offline). Status is also viewable via an icon that appears on the Station (Black “X” indicating that a station is busy, grey phone symbol indicating that a station is in a call). Since a standalone list of all stations is not available via the Windows client, the hardware tree is the only place all stations within the current instance can be viewed at once.   Licensing Licensing of the Zenitel integration is based on the number of stations. Instances may be licensed for any number of specified Stations and thus, the system will not allow Stations within the instance to exceed the amount in which it’s licensed. If the instance is not licensed for any stations, the “Intercom” section in the Hardware Provisioning tab will not be visible.

Issue Creating an email notification within Access Expert can be challenging if the correct steps are not followed.  Product Line EcoStruxure Access Expert Environment Access Expert Premise Software Cause If you don't follow specific steps, email notifications can be very difficult to write. Following the steps below, you can use pre-canned expressions which help to automate your notifications based on specific parameters. Resolution *Note* though you can add the Expressions tab by customizing the ribbon, no expressions can be found or used without following the process below. If you need to edit the notification to add more parameters then you will need to create a new template as editing an existing one will not expose the expressions. Trigger an event or alarm for what you would like a notification on. Right-click on the event or alarm in Event Viewer or Live Monitoring and select Add Email Template This will open up the template editor for you where you then will be able to select the necessary expressions based on your needs  Type the email message you would like to receive when the alarm triggers, click save    Type in the name you would like to use for the template and what you would like in the subject line of the notification you receive        Click on Alarm Actions, Add Alarm Action, and then Notification  Within the next dialogue box: Create a label for the notification Check the box next to "Send Email" Select the appropriate template Select Add Recipient Type in the name of the recipients you would like to receive the notification Click Save

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Proper configuration of supervised inputs, Mercury IO modules (i.e MR52) versus Continuum IO modules (AC1/AC1Plus) for transitioned Continuum sites. Product Line EcoStruxure Access Expert Environment Access Expert Controller Access Expert Reader Interface Access Expert Premise Software Access Expert Hosted Software Continuum AC-1 IO Module Cause Guidance is needed on the proper configuration of Access Expert custom EOL resistor tables in order to achieve full supervision of inputs associated with readers/doors. Full supervision in this context means not only being able to detect normal input operation (activation/deactivation) but also detection of attempts to tamper with the input's circuit (short circuit, open circuit, grounding, the introduction of foreign voltages, etc.) Please note that not all resistor configurations can detect all the various circuit issues, for example, a NO Series resistor configuration can't detect a cut in the wire given that the open circuit is the normal state for the Deactivated value of the input. The resistor configuration that provides the most supervision is the Series/Parallel configuration, using 2 resistors is possible to detect both short and open circuits. Resolution Continuum supported a fixed 10K Ohms resistance for supervised inputs, furthermore, Continuum IO modules (AC1/AC1Plus) transitioned to Access Expert under an AX-SSC controller continue to operate with Continuum firmware, this means that they do not support the custom EOL tables in Access Expert, the only configuration that is possible for AC1/AC1Plus modules is the mode of connection of the resistor (parallel, series or both).   Also, when using 2 resistor configuration, the placement of the resistor is different in Continuum compared to Mercury hardware   CONTINUUM When the switch is open only the resistor on the left is seen by the input. When the switch is closed, the two resistors are presented to the input in parallel with each other resulting in the input reading half the sum of the total resistance value.   SECURITY EXPERT       When the switch is open, the two resistors will be presented to the input in series with each other resulting in the input reading the sum of the two resistors value.  When the switch is closed only one resistor is presented to the input   For the above reasons, Continuum transitions sites where the AC1/AC1Plus has been replaced with Mercury hardware like the MR52 for example, need to configure one or more custom EOL table(s) for 10K resistors.   *** The sample tables provided below contain resistance values calculated to take into account wide variations in total supervised loop resistance due to wire distance, gauge etc., supervised loops should be installed in accordance to distance and gauge guidelines for wires as well as recommended resistor tolerance. It may be necessary to make adjustments to the resistance values in the tables on a site by site basis.   See below sample tables for all six possible 10K resistor configurations   Normally Open Parallel (10K-NO-P) Normally Closed Parallel (10K-NC-P) Normally Open Series (10K-NO-S) Normally Closed Series (10K-NC-S) Normally Open Series/Parallel (10K-NO-SP) Normally Closed Series/Parallel (10K-NC-SP)+ 1. Normally Open Parallel (10K-NO-P) 2. Normally Closed Parallel (10K-NC-P) 3. Normally Open Series (10K-NO-S) 4. Normally Closed Series (10K-NC-S) 5. Normally Open Series/Parallel (10K-NO-SP) 6. Normally Closed Series/Parallel (10K-NC-SP)+

Issue Instructions on how to configure a Bosch Integration on Version 3. Product Line Access Expert Environment Access Expert Version 3 Microsoft Windows 8.1 and above Access Expert Hosted software with Bosch integration Access Expert Premise with Bosch integration Cause Configuring a Bosch Integration on Version 3 to communicate to Access Expert. There are certain settings that need to be configured from both the Access Expert side and Bosch so that the integration can be seamless and function as designed. Resolution One of the first things when doing this Integration is to have the Bosch Appliance ordered and installed on the Network where the Bosch Panel resides. The device comes pre-configured from Feenics and all that is needed is to make the necessary changes in Access Expert using the following steps: 1. Verify that the connected instance does have the Bosch Services Enabled by going to the Hardware Provisioning and looking at the Bosch Services.  2. Click on the Bosch Services. 3. This entry would come up automatically as it was preconfigured into the Hosted Instance by Feenics. 4. Click on the Panels label and add the Bosch Panel Type from the dropdown. 5. Enter the necessary values on the various fields that correspond to the Bosch Panel, the Password must match what the Bosch Panel is using. 6. Import the Configuration and then save and close. 7. On the Bosch Panel verify that the Port is set for Port 7700, Automation Mode is set to 2 and the Firmware is 2.0 or greater If changes need to be made, you need to first connect to the Panel from RPS > make the changes > sync to the panel > disconnect from the panel Go into the appliance and stop/restart the Feenics Bosch Service within Windows Services 8. Make the necessary changes if needed then save and recycle power 9. Bring up the Hardware Tree and verify that the Panel is Online and communicating 10. All preconfigured Areas, Points, and Outputs will show up in Green, indicating that everything is working properly.

Issue OEM conversions allow for a non-Access Expert/Feenics Mercury board to be converted to an Access Expert board. This is only applicable to the IP level controllers and the AX-OEMC codes are not needed for the downstream controllers.  The process will change the OEM code within the Device info page of the controller. This allows the board to receive the correct firmware and operate within Access Expert.  Product Line EcoStruxure Access Expert Environment Access Expert Controller Cause Not all controller boards are compatible with Access Expert by default Resolution To perform the OEM conversion on an intelligent controller, an AX-OEMC code is needed per IP Controller connected to your system.  These are ordered through iPortal and will require some specific information from the customer's site.  With your order, please include (both are located on the white sticker located on the actual controller: Model of controller Serial number Email address for recipient The OEM flash code will be emailed to the person whose email address is used in the order as the recipient.  To convert the controller: Using IP Server. Connect directly to the controller with an ethernet cable Locate the IP address of the controller (The default IP address can also be used). Go to the 'Host Comm' section of the configuration manager. Set the connection type to 'IP Server'. Take note of the Port Data Security should be set to none or TLS if Available Save and apply changes. Open the OEM & firmware utility. Download Here Set the controller connection type of the utility to 'Server'. Enter the MAC address of the controller. Enter the IP address of the controller. Enter the TCP port used by the controller. Select 'Connect'. Once connected, enter the Authorization code provided by Schneider Electric. Select 'Convert'.   OEM conversion complete. Once the conversion has been completed, the panel will need to be set back to the IP client to connect to the Access Expert Mercury Communication Servers. See the Configuring Controllers for IP Client page for instructions.  

Issue Cannot generate a report from Access Expert V2. Getting an error when attempting to generate the report "Could not load file or assembly Microsoft.ReportViewer.WebForms, Version=11.0.0.0"   Product Line EcoStrucure Access Expert Environment Version 2 Report Viewer Windows Cause The ReportViewer files that are from Feenics's website contain version 11. Microsoft does have older and newer versions of the file (i,e 10 and 12) so there is a potential that these files will not work. Resolution To resolve this issue 1. Download the Microsoft Report Viewer (Feenics Training> Web App V2> Miscellaneous Downloads) http://www.feenics.com/Downloads/ReportViewer.zip 2. On the Access Expert application PC (Not the SQL Server PC in a 2 PC system)     Uninstall all versions of Report Viewer and SQLClrTypes from Windows> Control Panel> Programs and Features 3. Stop the Feenics Keep Render Service 4. Unzip the Download files (Report Viewer.msi  and SQLClrTypes.msi) and install both of them 5. Restart the Feenics Keep Render Service Test Reports 6. If they are still not working, reboot the Access Expert PC and test again. If this is still not working, contact your local country support.

Issue How to configure Custom 37-Bit as well as Infinity 37-Bit Card Format Product Line Access Expert Environment Access Expert Server 2012 and Above Version 2 Version 3 Hosted  Premise Cause When configuring Custom 37-Bit as well as Infinity 37-Bit Card Formats, the settings are different based on the Facility Code, Card Length and Card Formats. The HEX code generated in Live Monitoring can be deciphered to get the correct set of values required to make this work for your application. If you are unable to do so, please contact PSS and open a ticket so that they can help. Resolution The following settings on the screen shots show how to configure Custom, HID Formats and Infinity 37-Bit Formats, please pay attention to the one that will work for your specific application: Open and log on to the respective Access Expert Instance Select the tab Access Configuration to create a new Card Format Name the format accordingly in the description field, this can be used for Infinity 37-Bit if so desired Add the card range by clicking on the page Icon on the Number Range There is a Standard, HID Managed 37-Bit (not Infinity 37) in the drop down in the Card Format Presets This can be used by default but if you have a Custom 37-Bit Format and the Facility Code is known, however the Start Bit and Length will be different. An Infinity 3 Bit Format will use the Parity Bits Create the new format per the screen shots and configure accordingly. Once complete, click on Save or Save and Close, reboot the controller.

Issue Permissions are set with multiple tags as the following:      When the user logs into Access Expert and looks at the hardware tree, they are able then to see all the hardware on the instance rather than just those with the matching tags. Product Line EcoStruxure Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause The tags are meant to be on separate permissions and shouldn't be used on the same individual permission Resolution Tags and permissions should be set up as illustrated: