Issue When you select a trend chart from a Automation Server or a Enterprise Server the Internet Explorer Hangs and finally crashes. Product Line EcoStruxure Building Operation Environment WebStation 1.1 and 1.2 Internet Explorer 8 Cause The wrong version of Java is installed. StruxureWare 1.1 and 1.2 requires Java version 1.6 update 26 to function correctly. This error is the result of Java version 7 installed on the WebStation computer.  Resolution Note:  Java is no longer required from SBO/EBO version 1.7 and above.  Uninstall Java 7 and install the correct version of Java (Java version 1.6 update 26) stated on the WebStation data sheet. Refer to the Online Help Topic WebStation Specification Sheet and select the version of WebStation in use to determine the version of Java required.   

Issue What does a Card-View Plus device look like? Product Line TAC INET Environment Card-View plus Cause Ordering and identifying this equipment. Resolution See picture below:

Issue Power Monitoring Expert (PME) is able to make its data objects and alarms visible to EBO via EcoStruxure Web Services (EWS). But when viewed, the Alarms from these EWS objects only shows a number rather than its actual object name in PME. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server EWS Integration Cause There are two stages to bringing data via EWS into EBO.  The first is to create the EWS interface in EBO so that the EWS source (in this case PME) can be discovered.  However, if those discovered EWS objects are not then hosted in EBO, the Alarm Source details will be not complete. Resolution 1. First Identify an object in PME which is also in Alarm and will also be Alarming in EBO when hosted. The date and time of the actual Last Occurrence can be useful here. 2. Notice that the Source name and Source of the same Alarm in EBO is only a number. In this case 3 or EWS Client/3. 3. Now select Host EWS objects from the EBO Menu and host that point or controller onto the EWS interface 4. Note now that all Alarm references previously showing just a number now immediately update with the correct Source name and Source now that the point has been hosted in the EBO Database.  In this case PDU_2B_1_6A_ION9200 Note:At this point it would be very easy to simply decide to Host the entire PME Server onto the EBO Interface rather than a single object or controller as this would then update the sources of all alarmed objects.  However care must be taken that at this point not to overload the system.  Every hosted object will then be polled for value and alarm status periodically adding greatly to the comms between the PME and EBO systems and while the polling rate for Value and Alarm can be adjusted to sensible values there is an argument to only host those EWS objects that data is required from.

Issue Can I configure (translate) the I/NET Software into another language besides English? Is I/NET supported in different languages? I/NET Seven ver 2.41 supporting the user interface for either Chinese Language (Traditional) and Chinese Language (Simplify).   Product Line TAC INET Environment I/NET 2000 I/NET Seven Cause I/NET is provided in U.S. English language. Translation into other languages is possible with some limitations. Resolution There has been some success observed in translations using a product called Passolo. Although Passolo is not supported by Schneider Electric, you may employ it as a translation tool at your own discretion. More information is available at SDL/Passolo. Note: Passolo does not modify Windows® dialog boxes - this is managed by the language used during installation of the Operating System. This Customer Advisory CA-2001-09 - Update INET2000 and Languages.pdf discusses various items on this issue. Customer Advisory 2001-09 dated 10/1/2001. Within the I/NET Seven CD there is a folder called Inet7-Translation which contains the relevant file used with any translation software.  Update from 2011: for I/NET Seven Ver 2.41 and its support of the user interface for either Chinese Language (Traditional) and Chinese Language (Simplify). Answer: If you are talking about translating language then, yes, it should be translatable through the 3rd party translation program. Although we do not test translation in the lab. Update 2013: There are freelancers who could be of assistance to help your site. https://www.upwork.com site with potential low cost translators.  

Issue Access older I/NET 4.xx *.pag files from page markers in new pages made in I/NET 2000 Product Line TAC INET Environment I/NET 2000 Cause Access older files from new pages made in I/NET 2000. Resolution Go to the Graphic Editor, right click on the page-marker, then select Properties. The next screen is called Graphic Page Marker. In the File Details section check path of the file name of the file extension type If they are not correct then click on Destination page. Select and then open your file. (You may select *.pag or *.gpg files.) Make sure the correction is now in the File Details then click Okay. Save the graphic and close Graphic Editor. Test your page marker. Your page should appear. For conversion up to StruxureWare Building Operation, import the original pag files and convert to gpg. Then using the graphics converter from Building Operation, convert the graphics pages.

Issue Defined a Special Day for the door mode schedules, but no one gets access, not even a person with a 24/7 schedule. AMT shows Denied Entry Schedule Product Line TAC INET Environment I/NET Seven Cause In access control, there are two types of schedules:  Door Mode Schedules Personnel Schedules If there is a special day defined, there must be corresponding special day entries in all time schedules. Issue Special Days are causing the Elevator to show Denied Entry Schedule in AMT. Resolution Modify the existing personnel schedules Add an entry for the special day If it is a system that includes HVAC controls, their associated time schedules will need special day entries as well. If no instructions are given to them for what to do on a special day, they will do nothing. For further information on setting up Special Day schedules including screen captures, see Special Days Setup I7 updated.pdf.

Issue When upgrading an IMI Video system to the newer Datacard (ID Works) system, are there any files or utilities needed besides the ID Works software? Product Line TAC INET Environment I/NET Seven IMI Video system Datacard ID Works Cause Converting the IMI Video Badging system to Datacard system Resolution There are 3 files that you need. Click Convert.zip to download them. Also, INET Application Guide AG-2002-01.pdf has additional information on this process. When converting the IMI Video Badging system to Datacard system, the first step in the IMI system to begin the convert process is to re-index the database files before attempting to batch export the data. If you have multiple tenants you must perform this procedure for each tenant. ID Works ODBC String. Type the string as you see it including the case: UPDATE ACP001 SET FIELD16 = 'C:\Photo\' + cardnumber + '.JPG' Make sure the case and spaces are just like the above to avoid any problems. Make the path anything you like, but remember the C: string cannot exceed 50 characters.

Issue How to determine if SU (single-user), LAN, or WEBC (WebClient) license keys are required for your project. Product Line Andover Continuum Environment Continuum Cyberstation Continuum WebClient Cause The Engineer is unsure as to which Continuum License Keys are required for a new site or if additional Cyberstations or WebClient users can be added to an existing site. Resolution Depending on how large your system is and how many Cyberstations are required, you will have one of the four system configurations described below: A stand-alone system, which is comprised of up to three (3) PCs; (PC 1) Requires a SU key allowing SQL Express + Continuum. (PC 2) Requires LAN key allowing Continuum. (PC 3) Requires LAN key allowing Continuum. Note1: When changing from a LAN configuration to a SU configuration, an existing LAN key can be used in place of having to purchase a new SU key.) A stand-alone system with WebClient, which is comprised of up to three (3) PCs; (PC 1) Requires a SU key with WC1 or WC2 option allowing SQL Express + Continuum + one or two WebClient browser users. (PC 2) Requires LAN key allowing Continuum or no key allowing WebClient browser user connection. (PC 3) Requires LAN key allowing Continuum or no key allowing WebClient browser user connection. Note2:  In a stand-alone system there can be a maximum of 3 client connections; 3 Cyberstations OR 2 Cyberstations and 1 WebClient OR 1 Cyberstation and 2 WebClients. Note3:  When using this option of having WebClient running on the same system as the Cyberstation and SQL Server, make sure that the system has enough resources to adequately support these resource-hungry processes. A LAN system, which can be comprised of many PC's; (PC 1) No key required. Allows SQL Server only. In a LAN environment the Continuum Cyberstation is not installed on the same PC where SQL Server is installed). (PC 2) Requires LAN key allowing Continuum (PC 3) Requires LAN key allowing Continuum (PC 4) Requires LAN key allowing Continuum (PC 5) Requires LAN key allowing Continuum etc... A LAN system with WebClient, which can be comprised of many PC's; (PC 1) No key required. Allows SQL Server only. In a LAN environment, the Continuum Cyberstation is not installed on the same PC where SQL Server is installed. (PC 2) Requires WEBC key allowing WebClient on dedicated IIS server (up to 1, 2, 5, 10, 15, 20, or 25 WebClient user(s) licenses available). (PC 3) Requires LAN key allowing Continuum (PC 4) Requires LAN key allowing Continuum (PC 5) Requires LAN key allowing Continuum etc... Note4:  An SU key cannot be used in a LAN system as it does not allow a remote SQL connection. To connect to a remote SQL Server a LAN key is required.)   For more information on Cyberstation License Key part numbers and the different options available for these keys, see "CyberStation & web.Client v2.0 PA-00353" or similar on ExchangeOnline.

Issue How to configure Security Expert to fire an output when any user associated with a specific access level is granted access to a door Product Line Security Expert Environment Security Expert Controller Security Expert Server Cause There are various settings in different objects that must be correctly configured to accomplish use case of firing an output upon user associated with a specific Access Level being granted access to a door. Resolution In the Access Level object make the following configuration changes... In the General tab, in the 'Configuration' section, set the 'Time to Activate Output (seconds)' to the number of seconds you want to activate the output for and check the option labeled 'Reader Access Activates Output'  In the 'Outputs' tab, add the output(s) that you want to fire when a user is granted access to one of the doors associated with the Access Level In the reader expander, in the appropriate reader tab (1 or 2) under the 'MISC OPTIONS' section, check the box labeled 'Activate Access Level Output' With the above configuration, the specified output(s) will fire for the specified number of seconds each time a user is granted access to any of the doors associated with the Access Level object.

Issue Need to see when controllers go offline and then return online to understand how long a controller was offline. Product Line Security Expert Environment Security Expert Server Cause Need to show IT when the controllers go down and for how long. Resolution Create a new Event Filter Events > Event Filter Add new Event Filter by clicking the Add button Name it Controller Offline/Online and click save Event Types tab, uncheck Include All Event Types Click Add and type "Controller <controller_name> offline (event server)" in the search bar that pops up Click OK Click Add again and type "Controller <controller_name> online (event server)" in the search bar Click OK Save Go to the Reports tab > Setup > Event Click the Add button Name it Controller Offline/Online under Event Filters, delete all events and click add in the Event Filters pop-up, select Controller Offline/Online from the drop-down and check "Access All Record Groups" Click OK and Save Go to the Reports Tab > Event Change the Event Report to Controller Offline/Online and execute

Issue Unable to upgrade a JACE 8000 to I/A Series Niagara 4.8 or later due to insufficient memory allocation. Product Line TAC IA Series Environment I/A Series Niagara 4 I/A Series JACE 8000 Cause I/A Series Niagara 4.8 or later running on a JACE 8000 will consume approximately 40 MB more memory than Niagara 4.7 due to new features including a new OS (operating system) and JRE (Java Runtime Engine). Resolution The following information will help identify if there is sufficient system memory to upgrade to Niagara 4.8 or later and if not, how to tune memory parameters to increase required system memory. Use the following analysis to determine if a Niagara 4 platform, operating at release 4.7 or earlier, requires a memory allocation adjustment PRIOR to upgrading to version 4.8 or later. Determine the amount of Free Physical RAM in the embedded platform while running the current release (prior to a 4.8 or later firmware upgrade) Open the embedded platform with the Niagara Platform Administrator tools. Check the amount of Free Physical RAM that is currently available. The image below displays where the information is located. If the amount of Free Physical RAM is greater than 40,000 KB (40 MB), the JACE 8000 platform is ready to perform an upgrade to Niagara version 4.8.  If the amount of Free Physical RAM is less than 40,000 KB (40 MB), the platform will require adjustment to the NRE Memory allocation using the steps below. Determine the amount of memory allocation required Subtract the current amount Free Physical RAM (MB) from the required 40 MB allocation. In the example above, 40 MB – 26.3 MB = 13.7 MB. Round this value up 14 MB. Next, add a buffer value of 10 MB to the previous result for a new total of 24 MB. System memory will be freed by reducing size of RAM disk used for histories. Ensure that /mnt/aram0 contains at least this “allocation adjustment” free space.  Using the above example, there is 326,944 KB (approximately 326 MB) of available memory that can be re-allocated to satisfy the additional 24 MB requirement.  Note: If there is not enough free space available in the /mnt/aram0, please contact Product Support for more options. Adjust the NRE Memory allocation Use the Platform Administrator tool to locate and select the Configure NRE Memory button as shown below. Record the current memory allocations for Heap Space and Meta Space by reviewing the memory sizes shown below. Increase the Meta Space by using the Meta Space slider to provide additional working space. Slide the Meta Space adjustment shown below to add 40 MB to the existing value of 48 MB increasing the Meta Space to 88 MB. Increase the System Reserve by the required 24 MB calculated in the example above. Slide the System Reserve adjustment shown below to set the value to 24 MB. Return (increase) the Heap Space back to the original 384 MB size by adjusting the Heap Space slider shown below. The final adjustment will bring the Meta Space back the original 48 MB size by adjusting the Meta Space slider shown below. Save the changes and reboot the JACE 8000.  Using the information from Step 1, verify that the Free Physical RAM is now above 40 MB.  If confirmed, the JACE 8000 platform is ready to perform an upgrade to I/A Series Niagara version 4.8 or later.

Issue There are missing serial ports (COM ports) when viewing the 'SerialPortService' under 'PlatformServices' in a station. Some or all COM ports will be missing. Local serial ports and/or serial ports of the attached modules do not function. Product Line TAC IA Series Environment I/A Series AX Jace 8000 Cause This could show up for several reasons. This was found during an upgrade to Niagara 4.2. It was also experienced when converting a Jace8000 running N4.2 (or lower N4 version) to AX. This can occur with a new out of the box J8000 to AX conversion if you do not first commission the Jace8000 to Niagara 4.4 or above before converting to AX. All of these problems are due to older version USBbinary files not being properly updated during commissioning. The LON option module (side-car) might stop communicating on the LON trunk due to the same binary file issue. Resolution This can be fixed via serial shell; either by direct connecting with a mini-USB cable or via ssh after it is enabled from the Platform Administration view. It is recommended that PuTTY.exe be downloaded and used as the terminal program to access the shell. The directions below are CASE-sensitive and must be entered exactly as shown. We recommend that you do not type these commands, but rather use copy-and-paste to avoid typographical errors. This is especially true of the usbSerialNumber itself -- it is case-SENSITIVE. By default, PuTTY.exe uses mouse-left-click-drag-and-highlight as an automatic shortcut for copy. Mouse-right-click is the automatic shortcut for paste. Once logged in type: Display the USB serial number(s) sh [hit enter] $ ls /etc/usb [this will display the USB serial number(s), if nothing displays see the note* at the bottom] 85091090FPGGS41 [this is an example serial number] Display the available binary files $ ls -Rp /sys/images/usb [this will display the available binary files] /sys/images/usb/applet-flash-sam4s16.bin* /sys/images/usb/vid03eb/pid2404/Tridium232-1_r03.bin* /sys/images/usb/vid03eb/pid2425/Tridium485-2_r04.bin* Note: You could also see '_r05' instead of '_r04'. If this is your result, make sure to update using the line below. /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin* The USB ports unavailable is due to the 'Tridium485-2_r04.bin' (or Tridium485-2_r05.bin) file was not written to the USB serial number file. This can be corrected by updating the USB serial number file with the correct binary file using the statement below. Make sure to replace the X in the statement with the highest number binary found in 'STEP 2' above. $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r0X.bin > /etc/usb/<usbSerialNumber> Update the binary file Using the example serial number and USB binary file found in STEP 2: $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin > /etc/usb/85091090FPGGS41 Make sure to use the serial number found when 'ls /etc/usb' was called. If there is more than one serial number found, write the command multiple times, once for each serial number found. Also, make sure to use the highest USB binary file number found. Currently r05 is the highest number. If '_r05' is returned as the available USB binary file, make sure to use '_r05' when updating the USB serial number. After a reboot, check the SerialPortService to confirm the ports are restored. *Note: if no usb serial number was found using ls /etc/usb another method would be to call for the slog by typing: $ sloginfo An error would have been logged here during the last startup and will display the serial number; example output: Oct 10 13:42:06 1 6 0 serusb_is_device_supported: Device 2 on bus 0 unrecognized. Using CDC-ACM Class Oct 10 13:42:07 4 11111 0 error opening /etc/usb/85091090FPGGS41 rc=-1 In addition to the symptoms listed above, the inability to communicate with the LON option module may cause the any of the following messages in the Serial Shell and/or the Platform Administration System Logs: error opening /etc/usb/<serial number here> rc=-1 U50Read returned unknown rc = 8!!! io_write failed ldvRC=7, length=<various numbers of bytes> The Station will most likely show that the LON network is up, but the LON devices are down. The device fault cause may show "unable to write" or something similar.

Issues Need a report of cards/ users that has not accessed the facilities in some specified time. Product Line Security Expert Environment Security Expert Cause A customer requires a report for all users/ cardholders that has not accessed any door (Entry/ exit) for a certain amount of time Resolution Current Security Expert Software, v4.2.259.19 and v4.3.285.21, do not have this feature. An enhancement request is pending. The request number is QC#186

Issue Script editor shows blank canvas or shuts down immediately after launching. Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Cause User settings file contains information the Script Editor application can't process correctly. Resolution First, to confirm that the issue is indeed caused by information in the user settings file, navigate to the location where the file is located (i.e. C:\Users\Your User\AppData\Roaming\Schneider Electric EcoStruxure\Script Editor\3.1.2.29) and make a backup of the User.settings file then delete it. If the Script Editor launches fine after deletion of the file, and you need to narrow down which setting was causing the problem, you can put back the original file then open the file in a text editor such as Notepad++ and comment out suspected lines until you identify the exact setting causing the issue. You comment a line or block of lines by inserting <!-- at the beginning of a line and ending the line(s) with -->  (see below)

Issue What are the measures in the AS to protect the system in cases of network broadcast storm or Denial of Service attacks? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Cause Offline alarms received after excessive network traffic observed. Resolution The firmware in the AS will temporarily shut down its Ethernet connection when exposed to a broadcast storm or DoS attack in order to protect the application in terms of control programs and IO. A side effect of this is that the communication to external IP devices is temporarily unavailable during the storm/attack. The Automation Server will log the network storm event in its log journal file. (see screenshot below)

Issue Data Execution Prevention (DEP) might prevent some applications from executing. Product Line TAC Vista Environment Windows XP Windows Server 2003 Windows Server 2008 Cause In both Windows XP and Windows Server 2003/2008, there is a function called "DEP" (Data Execution Prevention). The default setting for DEP is to monitor Windows programs and services only. However, in Service Pack 1 for Windows Server 2003, this setting was changed to monitor all programs and services. This can prevent some applications from starting (like TAC Vista Workstation, TAC Vista graphic editor, RSPD etc.) Resolution Check that DEP is only monitoring Windows programs and applications only. How to access the DEP settings: In the system properties under the advanced tab, click the settings button for the performance. Select the data execution prevention tab. Here is a quick video of the DEP setting process.  

Issue TAC Xenta does not show the same time as TAC Vista. Product Line TAC Vista Environment TAC Vista Workstation Xenta programmable controllers Cause The time in the Xenta comes from the Vista server. However, it can be adjusted for time zones and daylight savings time settings. Resolution Check daylight savings time and time zone settings in TAC Xenta. The setting should be the same as in the Operating Unit (if they are in the same time zone). Check if a PVR object name XENTASYSREG is in the Menta application with a value of 2. This inverts Europe daylight setting and causes the controller to adjust its time. Note! This is NOT the regional settings on your PC, but the setting in the Vista object in your DB. Here is a quick video showing the regional setting process.

Issue Cannot read Mifare CSN, using Security Expert readers, from customer's existing Mifare cards  Product Line Security Expert Environment Security Expert Smartcard Reader [All] Cause The Security Expert readers will not read Mifare CSN by default. Resolution Configure the ability to do this through the RS485 menu or with a configuration card.   Older readers (firmware version 64 or lower) use an RS485 interface to modify reader configuration. Newer readers (with the -BT part numbers) require a Configuration Card purchased from Schneider Electric in order to modify the factory configuration of the reader to read the Mifare CSN. 

Issue How to setup OSDP Readers on Access Expert Product Line Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause Clear recommendations and instructions needed for the process Resolution OSDP Readers with Access Expert Overview OSDP stands for Open Supervised Device Protocol. It is the replacement of the older clock and data style and Weigand protocols that have been used across the industry for many years.OSDP is based upon an industry-standard from SIA (Security Industry Association) and has various levels.  The original version was called OSDPv1 which was followed by OSDPv2 then Secured Channel Communications was added to OSDPv2. This document will address how to add an OSDPv2 and/or OSDPv2 Secured Channel reader to an Access Expert system. As we move more into a data secured and encrypted environment, it is recommended that all deployments be installed based upon OSDPv2 at a minimum.  More information on OSDP can be found at https://www.securityindustry.org/industry-standards/open-supervised-device-protocol/. When compared to Weigand, OSDP offers various technological advancements with the increased level of security being one of the key benefits associated with OSDPv2 Secured Channel. More Security: OSDP v2 with Secure Channel protects readers against hacking using AES-128 encryption and OSDP constantly monitors wiring to protect against tampering. OSDP helps overcome the growing threat of “man in the middle” attack. More Functionality: OSDP uses fewer wires, allows for multi-drop installation, supervises connections to indicate reader malfunctions, and can disable the reader automatically when removed from the wall. Bidirectional communication: OSDP supports bidirectional communication. This means that the reader configuration can be set at the software and then sent to the reader via the intelligent controller More Interoperability: Using OSDP enables communication among different manufacturers' devices. More Consistency:  Not only does OSDP provide a concise set of commonly used commands and responses, but it also eliminates guesswork since encryption and authentication are predefined. Ease of Use: Low cost of implementation on an embedded device and simplification of the encryption and authentication process. Most readers come with both Weigand and OSDP support already available. Reader Wiring & Prerequisites Prerequisites: Readers wired for OSDP Readers that support OSDP HID Mobile Reader Manager App (iTunes or Google Play) HID Reader configured for OSDP and addressed It is possible to deploy OSDP readers on Access Expert without using the HID Reader Manager App provided you are not “stacking” readers on the same controller port.Stacking is a process of putting multiple readers on the same controller and the same port. If stacking is being used, the HID Reader Manager App will be required to set the 2 nd readers' address. As an example: Application Need Reader Port 1 Reader Port 2 Parking Garage The project will have 2 Parking gates where each will have dual readers Reader 1 on Port 1 is set to address 0 Reader 2 on Port 1 is set to address 1 Reader 1 on Port 1 is set to address 0 Reader 2 on Port 1 is set to address 1 When deploying OSDP, the reader and port address designation for each reader port will default to address 0. This means you can deploy a system without using the HID Reader Manager App provide only a single reader is being used per controller port. Note that the AX-MR62e supports a total of 4 OSDP readers but only has a single reader port. This means the HID Reader Manager App is needed to set the addresses accordingly for readers 2 through 4.   OSDP wiring is different from what most installers are accustom to. Rather than Weigand which takes 6 wires to the reader, OSDP is an RS-485 connection where 2 wires are used for data, and 2 are used for power as noted in the images below. These pictures show an HID R900 reader is connected to an AX-MR52-S3 controller for OSDP. The same wiring method is used when deploying OSDPv2 Secured Channel.  No additional wiring is needed for the reader to pick up additional signals such as Reader Tamper alarms.   Adding OSDP Readers to Access Expert To Add an OSDP Reader to your Access Expert system: Open the desired downstream controller or right-click the downstream and select Add OSDP Reader. Click “Add OSDP Reader”. Enter the Reader Display Name. Select the Address.  This field will default to 0 or 1and represents the controller port. Complete the Reader Information for the other fields similar to how a traditional Weigand Reader is configured. Click "Save & Close".   Take note of the Addressing being used on your system. The address is the Controllers Port address while OSDP Address is the Readers address and will vary when Stacking is being used. At this point, the OSDP reader is added to the Access Expert system without Secured Channel being enabled. Leaving the Assurance Profile to None and using the Default Baud Rate settings will leave the reader connected to the system without using the Secured Channel. It is recommended to set up as default first then enable Secured Channel.  OSDP readers have many of the same fields as a Weigand reader so the setup processes will be similar. Assurance Profile: This is used only by PIV class cards for FIPS deployments. Use Default: Using the default sets the Baud Rate to 9600, the address to 0, and does not use a secure channel. Use Secure Channel: To leverage the extra security that comes from OSDP readers, it is best practice to turn on a secure channel. Baud Rate: Because OSDP readers have bi-directional communication, the downstream and the reader need to be using the same rate of the communication (baud rate). Make sure this is set according to the reader's needs. It is recommended that 9600 be used for OSDPv2 and that Auto Negotiate be used for OSDPv2 Secured Channel. OSDP Address: Multiple OSDP readers can be connected to the same reader port on a controller. As an example, the MR-62E supports a total of 4 Readers on the controller but nly has one reader port.  When this is done, each reader on that port needs a unique address and is set in the HID Reader Manager App. Setting up OSDPv2 Secure Channel The reader must first be configured as an OSDP reader in Access Expert to be successfully configured for Secure Channel communications. Right Click the Reader and select View Live Monitoring. This will allow you to monitor the reader communications as you enable Secured Channel.   Check the "Use Secure Channel" option. Set baud rate to auto-negotiate. Click "Save" The reader will show as offline in the hardware tree. From the Reader setup page, Click Actions then Select Start Linking mode. The linking mode is automatic, and the process can be monitored from the Live Monitoring page. The reader will negotiate the secure communication with the controller and come online. With Secure Mode, if the Reader Tamper is in alarm, the reader will not process any card reads by design. How to - Remove Secure Channel on an OSDP reader At some point, you may need to remove an OSDP reader which has been connected to a system via Secured Channel. Uncheck Secure Channel. Click "Save". From the "Actions" drop-down menu, select "Send OSDP Command". Select the Manufacturer. Choose "Set Install Mode". Click "Execute". The LED on the reader should blink green once completed Note: The 'Send OSDP Command' modal has several OSDP Command options so make sure you are selecting the correct manufacturer and command. How to - Know if a reader is in Secure Channel There will be an event indicating the reader mode changed to card only after the start linking mode command. As the reader comes on/offline, you will notice an event/message that says “OSDP Secured Channel for, Reader Name, is Enabled but not Online or Encrypted” and “OSDP Secure Channel for, Reader Name, is Online and Encrypted.”

Issue Getting error 'One or more errors occurred' when transitioning Continuum access control related objects into AX sub instance.   In the screenshot above, the tool is attempting to transition objects into the PSS sub-instance under the root instance.   Product Line Access Expert Environment Access Expert Premise Software Access Expert Hosted Software Cause The transition tool GUI is misleading in terms of where specific information should be entered.  Resolution Due to an issue in the tool, only the instance field should be populated, in the case of a sub-instance specify the name of the sub-instance in the 'Instance' field.