Issue How to manage the trend files stored on the SmartStruxure™ Lite Manager flash memory. Examples and guidelines for the FTP transfer of trend files. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) 2.4.3 and above Lua program Cause All data points collected by a TL object are saved in a text file stored on the SmartStruxure™ Lite Manager SD memory card (which has a storage capacity of 2 GB). This file is accessible at [ipaddress]/root/data/trend.csv. The trend.csv file contains the log of all TL objects on a SmartStruxure™ Lite Manager. It logs new data until it reaches a size of ~10 MB, when it will be renamed trend_date.csv for backup. A new trend.csv file will be created to record the new data.  In the context of your application, it may be of interest to retrieve the trend.csv file from the SmartStruxure™ Lite Manager for analysis.   It is also important to remove these excess trend files since there is a risk of filling the SD card on the Manager. An example of storage requirements are listed below: A Manager with 10 trend logs recording data every 10 minutes will record ~50 kB of data each day, for a total of ~350 kB per week. A Manager with 20 trend logs recording data every 30 seconds will record ~2 MB of data each day, for a total of ~14 MB per week. Resolution The simplest way to automate this process is to use a Lua script to initiate a FTP file transfer to an FTP server on an event of your choice. The example shown in the application note below, the file transfer is initiated by a SmartStruxure™ Lite scheduler. Once the file is transferred to the FTP server, you can rename the file to create a backup. Data collection will then continue in a new and empty trend.csv file. This way, any new transfer of the trend.csv file to the FTP server will be a complement of the preceding file. This application note discusses the management of the trend files stored on the SmartStruxure™ Lite Manager flash memory, and provides examples and guidelines for the FTP transfer of these files. Lua script examples can be found here

Issue The XML Automation Server application on the WebClient Server does not open when a remote WebClient browser tries to access WebClient. WebClient does work from the browser on the WebClient server itself but can't be accessed from another PC. The XM Automation Server keeps closing by itself. Environment WebClient Windows Server 2003, Windows Server 2008, Windows 7 Cause DCOM Permissions have not been set properly to allow access to these WebClient components. Resolution Confirm that DCOM permissions have been set properly. Follow the steps detailed in the section "Configuring DCOM Default Security Settings" starting on page 100 in the WebClient Installation Guide, paying particular attention to the NETWORK SERVICE account. Please see the link below for the relevant section from the WebClient v1.94 Installation Guide. DCOM Permissions excerpt from 30-3001-835 webClient Planning and Installation Guide

Issue CX level controller was once online and now appears as offline Product Line Andover Continuum Environment Continuum Netcontroller CX ACX BCX Cause From time to time issues will be reported that controllers are offline at the IP level. Resolution Troubleshooting steps to perform:   From one of the existing sites Cyberstations perform a ping of the controller. If there are responses, verify that the response is from the controller and not another device. Verification of the response can be done via Wireshark capture if the CX appears to be responding. If there are responses to the ping, then attempt to open up the web-configuration page for second generation controllers. Verify the site’s Cyberstation is online itself. (Right-Click/edit the workstation and view the Comm Status. It will be either Online or Offline.) With CyberStation installed on technician’s laptop with the same version as the site version. Plug an Ethernet cable into the same hub the controller is plugged into. Connect to the site database with the local laptop's CyberStation and start Continuum. Check the controller in Continuum Explorer to see if it shows offline to the local laptop's CyberStation. If the controller is online to the local laptop's Cyberstation, then it is clearly a site network issue. At that point we will need to make sure all the IP address info is correct; there is no port blocking, subnet masks, gateways etc… Standard network troubleshooting. If the controller shows offline to the local laptop's CyberStation, then look at the CPU lights on the controller for activity. Watch the link light, CPU, IO bus lights if there is IO modules, etc… If those look abnormal and you have a smart phone it will be worthwhile to try and get a video of them to send into support for review. If there is no link light then try disconnecting the Ethernet cable from the NETWORK SWITCH and plug it back in to check if it brings the controller back online. If that does not bring the controller back online try disconnecting the Ethernet cable from the CONTROLLER and then immediately put it back and check if the controller comes back online. If all of the above fail then the next step will be to power cycle the controller to try and bring it back online. If communications cannot be established, contact support and open up a case for additional troubleshooting to determine if the controller needs to be sent to repair. If communications is restored and further investigation is required, please retrieve the following information and open a case with support for review. Controller error log Controller offline listview exported to CSV A Wireshark LAN capture at the controller level with peak traffic occurring Additional information may be requested including a controller core dump. This is a very intensive process. Support will supply the Core Dump Utility if needed.   Please click HERE for a copy of these instructions in PDF format.

Issue On an upgrade or other circumstances, the Continuum.mnu points to C:\program Files instead of C:\program files (x86) on a 64 bit PC. Product Line Andover Continuum Environment Windows 7 64 bit Windows 2008 64 bit Cause On an upgrade or other circumstances, the Continuum.mnu file points to C:\program Files instead of C:\program files (x86) and doesn't find the files being used. Resolution Under certain circumstances the Continuum.mnu file doesn't point to the correct folder. All of the buttons in the file point to C:\program Files instead of  C:\program files (x86). Use the following file to copy to each of the PCs that the menus are not working. The path of the Continuum.mnu is c:\program files\continuum\userprofile\continuum.mnu . This can be changed per Cyber by editing the Workstation in Cyberstation then clicking the preferences tab. The path for the entry can be edited. The Continuum.mnu that can be download from the web site has the default  (x86) paths in it. Continuum x86 Mnu file download Make a copy of the existing Continuum.mnu (Copy of Continuum.mnu) Delete the existing Continuum.mnu Download the file from the link above to the C:\Program Files (x86)\Continuum\UserProfile\continuum.mnu Restart cyber *** The path within the Continuum.mnu files must be correct and the path to the Continuum.mnu must reference the .mnu file with the path that you need

Issue What is the I/A Series product suite? What I/A Series devices will be connected to or talking on my network? Does I/A Series support DHCP, DNS, and dynamic DNS? Which software protocols and RFCs (Request for Comments) does I/A Series support? I use Netscape Navigator as a browser, are there any ActiveX compatibility issues that I need to be concerned with? How do I back up this device? What LAN network management tools do I use to manage these devices? When does a UNC controller communicate with the Enterprise Server and vice versa? What does a system of UNCs and a Enterprise Server do to my network traffic and bandwidth? How do I access an UNC or Enterprise Server over the Internet? Can I access the entire I/A Series network if only the Enterprise Server is exposed to the Internet? How will I/A Series tie in to my security policy? How is the UNC protected from viruses? How do I protect someone from hacking into my I/A Series system? How do I set up / use a VPN? How does your system work with firewalls and proxy servers? What firewalls does your system work with? What LAN network management tools do I use to manage these devices? “I use Netscape Navigator as a browser, are there any ActiveX® compatibility issues that I need to be concerned with?” “I use Netscape Navigator as a browser, are there any ActiveX® compatibility issues that I need to be concerned with?” “Which software protocols and RFCs (Request for Comments) does TAC I/A Series support?“Which software protocols and RFCs (Request for Comments) does TAC I/A “I use Netscape Navigator as a browser, are there any ActiveX® compatibility issues that I need to be concerned with?” Series support?”“Which software protocols and RFCs (Request for Comments) does TAC I/A Series sup Environment I/A Series R2 Cause Frequently asked IT related questions for I/A Series R2. Resolution There is a document 'F-27407-4 IT Manager’s Frequently Asked Questions' that answers common IT related questions on the I/A Series R2 system. This document can be downloaded here. Frequently Asked Questions

Issue Is there any way to get calibration certificates for the Kamstrup meters and auxiliary equipment associated to the meters? Environment Kamstrup Heat meters cool meters flow meters Cause To fulfill the requirements of some standards, calibration certificates on the equipment may be required.  Resolution All new meters are delivered with approval and initial verification according to the standard for heat meters EN1434, and the European Measuring Instrument Directive MID. This warrants that each meter is within the Class and MPE stated by the standard. Kamstrup can provide certified calibration results for individual meters upon request. Please order these certificates through your regular Orders channels, and please confirm the meters/sensors serial number by filling in the Order form that can be downloaded here. Temperature sensors, calculator and flow part has each their own certificate, and can be replaced individually if broken or damaged. Please make sure to state serial number for each part when requesting the certificate(s).  

Issue Can the MNL-200 controller's analog output be used to turn a relay on and off?  Can you recommend a brand/model of relay? Product Line TAC IA Series Environment I/A Series MNL Controllers Cause The application requires additional digital outputs Resolution At 500 ohms and 20mA, the analog output produces 10 Vdc.  The voltage can go as high as11 Vdc by using a 550-ohm resistor instead. A common brand and model is from Kele (model # KEL-RIBU1C) and it's available on iPortal.  The coil pulls in at 10 Vdc and drops out at 3 Vdc.  Click here for the datasheet.

Issue Replacement an AF24-S Actuator? Environment AF24-S Damper Cause Customer requires a replacement actuator for a AF24-S. Resolution The AF24-S is a 24v power open, spring return damper actuator, it has a torque of 15 Newtons. To view the data sheet, please click HERE. The replacement actuator range is the MD10SR/MD20SR ranges. The MD10SR damper actuators have a torque of 10 Newtons (dampers up to 2m2) and are available in the models shown below. To view the full data sheet, please click HERE.   The MD20SR damper actuators have a torque of 20 Newtons (dampers up to 4m2) and are available in the models shown below. To view the full data sheet, please click HERE. In the specific case of the AF24-S the replacement would be the MD20SR-T or -TS if auxiliary switches are required.

Issue IAC Touchscreen passwords. Environment IAC Touchscreen 600 IAC600 Cause Customer did not know the passwords. Resolution The password that will allow you to read point values via the Touchscreen is 1234. The password that will allow you to make changes to point values via the Touchscreen is 4321. There is also a maintenance password available, but unless the operator knows the Touchscreen operation well, this should not be used. Please refer to Product Support Services if this password is required. To view the Touchscreen User Guide, please click HERE.

Issue Requests for information on a wireless access control solution Environment Continuum Schlage Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Easy access to documentation for the Schlage Wireless Access Control Solution Resolution 09-17-2012 The Security Center of Excellence is pleased to announce the integration between Schlage AD-Series locks and Andover Continuum Netcontroller II and ACX 57XX family of controllers. This integration will provide a cost effective and scalable access control solution. Schlage AD-Series locks combine all of the components typically found around the door such as the door position switch and the request to exit switch into one unit which simplifies installation and saves money. Since they are designed to be modular Schlage AD-Series locks can easily be upgraded in the future to meet changing security and technology requirements. Within Continuum Cyberstation the Schlage locking device will look and function like a normal door and an XDriver at the controller level will provide access to these devices. This solution is ideal for education and healthcare facilities but can also be used in a wide range of other applications. For more information please contact COE@Buildings.Schneider-Electric.com.   Schlage Data Sheet Final.pdf Andover Continuum _ Schlage Integration Offer Final.pdf Andover Continuum _ Schlage Integration Training Final.pdf

Issue List of Tables and Offsets for MicroNet 50 series, 100 series, and IACs Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment VisiSat VisiView MicroNet View Cause Need to define the Tables and Offsets for MicroNet 50 series, 100 series, and IACs. Resolution Click here to download the list of tables and offsets for the MicroNet range of controllers. Click here to download the list of tables and offsets for the IAC range of controllers. Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 and PA-00528 

Issue Cannot find a wiring diagram for the ETR800 Temperature Sensors Product Line TAC IA Series Environment ETR-800 temperature sensors Cause Not available in the Publication Zone Resolution Click the link to view and download the wiring diagram:  F-27619 ETR800 Sensors Wiring Instructions Click the link to view and download the data sheet (also available in the Publication Zone):  F-27601 ETR800 Sensors Data Sheet

Issue LonWorks Zone Controller SE7200F5545E Environment Site requiring information or literature regarding this zone controller Cause Cannot find information on: Part Number: SE7200F5545E Part Name: ZNCTRL LONWORKS 2X0-10V PIR Part Short Description: LonWorks Zone Controller :2 Analog 0-10V Outputs, PIR Cover Installed. Part Long Description: LonWorks Zone Controller:2 Analog 0-10V Outputs with PIR Cover Installed   Resolution Please find the following guides: SE7000 Series Room Controller Brochure SE7200 Series Room Controller Data Sheet SE7200 Room Controller with Integrated PIR Motion Sensor Data Sheet PIR Ready SE7200 Series Installation Guide SE7200 and SE7300 Series LonWorks Integration Manual

Issue I/A Series R2 and G3 MIB files Environment I/A Series R2 SNMP integration I/A Series G3 SNMP integration Cause A Management Information Base (MIB) describes a database of objects that can be monitored by a network management system. SNMP uses standardized MIB formats that allow any SNMP tool to monitor any device defined by a MIB. The Tridium MIB defines the information that can be exposed for a I/A Series Niagara station running the SnmpService. The third party system is having trouble reading the SNMP traps from I/A Series using the MIB file that was sent to them. Resolution Ensure that the correct MIB file is used. Starting in I/A Series R2 version 2.301.528 and above, a new TridiumR2-MIB was created that is supported by R2 Snmp stations. This was created because of the need to differentiate Tridium MIB object identifiers between R2 and G3. I/A Series G3 versions 3.4 and earlier uses TridiumR3-MIB.my MIB file. To view this file in WorkBench, go to 'File' > 'Open' > 'Open Ord' (or shortcut Ctrl + L) and key in 'local:|module://snmp/tridiumMib/TridiumR3-MIB.my'. Starting from I/A Series G3 versions 3.5 and above, there is a Workbench function (right-click menu on the local SNMP device) to create a MIB. See 'About locally generated MIBs' on page 3-17 to 3-21 of the Niagara Ax 3.5 SNMP Driver Guide.

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.    

Issue How to enable the “Disable Card if Not Used In” feature that shows on the Privileges tab of the Personnel Editor object? The option is greyed out and no values can be entered. Environment Continuum Personnel Editor Cause The feature has not been enabled and there are currently no plans to implement this feature.   Resolution The feature is not implemented. At the time of writing this, the documentation and online help had not been updated to reflect this and are misleading. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Although, it is possible to create this functionality through a Plain English program that looks for cards that haven't been used in a certain amount of time and then disables those cards. See these sample programs below. They are not an exact solution but provide the methodology to be used. Dead Report Expire Disable Cards   Depending on how large your Personnel list is will determine how much success you will have with this PE solution. The OpenList command can have issues and lock up if the list being searched takes too much time to go through.  

Issue How to set up a Mantrap Product Line TAC INET Environment I/NET Access Control Site Interlocked Doors Person Trap Anti-Passback (APB) Cause What is a mantrap? A mantrap is a security device that monitors and controls two or more interlocking doors to a small room that separates a non-secured area from a secured area. These interlocking doors allow only one door to be open at any time. What are interlocking doors? “Interlocking doors” is a security term used to describe how two or more doors are interfaced with each other and locked. Doors that are interlocked cannot be opened at the same time. Either door can be unlocked and opened as long as the other door is locked and closed and no other alarm condition exists. What types of locations require a mantrap? Mantraps are used at high-value or critical security areas where only authorized persons are allowed to enter. Typical areas include sensitive data processing areas, cash handling areas, critical research labs, security control rooms, and automated airline passenger entry portals. Why would my company consider a mantrap? Typically, security personnel are posted in high-security locations to control access into the area. An automatic mantrap used in this same location would control the access to the area, allowing security personnel resources to be available for other tasks. What is the difference between a mantrap and an interlocking door control system? Regarding controlling two doors within a vestibule, “mantrap” and “interlocking door controller” can be used interchangeably. Once the number of doors controlled by a single controller exceeds two, then the term interlocking door controller should be used. Resolution I/NET has three ways to do a mantrap: Event sequences and calculations -- limit to 5-7 SCUs per 7798C due to system loading Use a "standalone" third-party device that is wired to the door and is not attached to I/NET at all Use the interlock wiring diagram that uses relay logic to function. This is also part of the I/NET System. I/NET Seven allows configuring a door to have both an entry and an exit reader and uses the selection of Anti-pass back/Anti-tailgate to set up Zones or areas with stricter control over access. However, even with the Anti-pass back option set to Hard, which denies access to successive reads at the same reader, it does not prevent multiple persons from entering and exiting together, and it does not provide real-time accounting for the number of people in a Zone. Besides having a guard at the door, the usual method of implementing Zones does not prevent violations.   The example below presents some thoughts about improving the Zone's security in an I/NET Seven system. There needs to be a way to restrict the number of people gaining access to the door. There needs to be a way to keep up with how many people are in the Zone. One method to accomplish the first goal is to use a two-door egress system, as is often used in jails and similar security setups. For a medium security setup where the intent is not to prevent people from leaving, only one door needs a card reader. Such a design is illustrated below: Notes: Electric strike normally energized. Low walls or fences. The area should be small enough to limit how many people or things are in it at one time. Gate with normally de-energized bolt. The gate could swing both ways, so one would only have to push it to open it. It should have a spring to close it. The door “a” would have both an Entry and Exit reader, so an Anti-pass back/Anti-tailgate can be implemented. The strike on the door “a” would normally be energized and opened by a valid reader transaction.   The bolt on the gate would be normally de-energized, allowing the gate to open freely. When the strike on the door “a” is de-energized, the bolt on the gate would be energized, preventing the gate from opening. This is designed to allow only one person to simultaneously move into or out of the Zone.   An added level of security would be accomplished by mounting IR emitter/receiver pairs along the low wall or fence at regular intervals. A person would interrupt the light at a limited number of receivers, so if more than expected are interrupted, it would violate one person at a time, and necessary action could be taken.   If material needed to be moved through the door, the gated area could be made large enough to allow for a dolly or whatever might be needed. A different access level would be provided to those who are moving material, thus preventing the alarm for too many people going through the door.   This approach would restrict movement into and out of the Zone, and the example given in the AIC note could be implemented to allow real-time monitoring of occupancy levels in the Zone.   Design thoughts:   To calculate whether more than one person is in the gated area, sum the number of receivers that are detecting and compare it to a minimum, e.g., four of six must be detecting if only one person is in the area. If material is in the gated area, generate an alarm if an authorized card is not read. Use the alarm delay for the point to give an individual time to make a card read before sounding the alarm. The AIC scheme described in the AIC note would have to be duplicated for the material mover individuals to change the calculation of a person in the gated area. For material movers, the detection would be (sum of detectors < minimum), whereas for regular individuals, the detection would be (sum of detectors > minimum). Remember, the SLI connected to this door can have only 64 AIC’s and this door now has used 2 of them. Use an inter-card delay long enough to let the person exit the gated area before another card can be read. For personnel safety, there must be a way to de-energize the strike. One method would be to mount an emergency exit button located far enough away from the door so a single person could not reach it and a second emergency exit button on the outside of the Zone so someone could keep the strike de-energized until everyone is evacuated. Most codes probably require that all strikes be de-energized in case of smoke or similar emergency to provide another fail-safe.   Here is a pdf document which explains the setup using an SCU Click here to download third-party ManTrap information.

Issue The FDA requires Building Automation systems to meet their standards which are outlined in Chapter 21 CFR and FDA Part 11. Environment Vista I/NET Andover Continuum TAC I/A-series Satchwell Sigma Cause Finding documentation on Schneider Electric Building Automation Systems which comply to The Food and Drug Administration rules. Resolution Vista 21CFRPart11 support in TAC Vista 5.pdf FL-VISTA-REGIND-A4 mod RO.pdf I/NET - currently unavailable Andover Continuum With the addition of the 21 CFR Part 11 compliance pack, Continuum can meets these requirements. Satchwell Sigma SoftwareOverview.pdf Advanced Security Module.pdf Note: Validation to 21CFR Part 11 can only be performed on whole operational systems and as such, a sub-system comprising the Satchwell Sigma building management system cannot be validated in it own right. Satchwell Sigma would normally be validated as part of a whole operational system. TAC I/A Series - currently unavailable

Issue Replacement I/NET Controller NICAD Battery info., I/Net Batteries Product Line TAC INET Environment All I/NET controllers Cause Controller battery has failed, because the battery on the controller is over 5 years old   Resolution The 3 pin version Battery is used for the NPR2000 and the DPU48K (MIP Board) -- part number 3/V80H-SLF (Note this battery has to be order from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The 7910, 7920, 7930 7780 & 7940 use the 2 pin version -- part number 3/V80H-LPC (Note this battery has to be ordered from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The battery used on the 7700, 7716, 7718, 7728, 7720, 7928, 7793, 7798B, & 7798C (and like controllers) is the Dallas/INET part number 801288-07. This also can be ordered from the Rockford order entry using 01-2100-545 (Old CSI P/N 801288-07). This battery also has an outside Vendor source from Power-Sonic P/N - PCBM-3.6 Click here to view a PDF on this part. For battery testing process see How to test the NiCAD Battery on a Controller

Issue How is Continuum configured to validate FIPS 201 PIV card credentials? Environment CyberStation CX9680 ACX5740 ACX5720 Cause Questions on how to configure a Continuum physical access control system to validate FIPS 201 PIV credentials at the door. Resolution Configuring Continuum for FIPS PIV card credentials Click here for instructions on creating a custom FIPS-PIV card format Versions needed for FIPS-201