Building Automation Knowledge Base

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 EcoStruxure Building Operation - Sigma logging does not work. Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Sigma logging has been transitioned to EcoStruxure Building Operation, but does not work. Resolution  The Procedure is as follows; Import the log data sets from Sigma to EcoStruxure Building Operation. Highlight "Log Sets" in the system tree under the Sigma Interface and select to "Send log sets" To confirm that the controller has started logging, select the appropriate controller, and choose "Diagnostics" and "Log Set Statistics" where you can see the statistics which include the log set/object details. To upload the logging, highlight the required log set and select "Retrieve Logged values". To review the uploaded data, highlight the required log value and view it as required Once that the logging in the Sigma controllers is working correctly to EcoStruxure Building Operation, logging from the Sigma server should be disabled.

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 Missing LNS plugins for  EcoStruxure Buildings Operation Workstation Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Cause Plugins for EcoStruxure Buildings Operation are not included in these releases. Resolution Download the TAC Vista 5.1.9 tool pack and this will install the 100 series controller plugin and Z-Builder programming tool. Once this is installed EBO will be able to access these plugin when used with Open LNS. Download the TAC Vista 5.1.9 Toolpack - Software from Exchange Extranet. Direct Download also provided. 

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.  

Issue How can an Airlock door system be implement in Continuum? Product Line Andover Continuum Environment Continuum Cyberstation Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause Sample PE program is needed as a general guideline on how to implement an Airlock control system in Continuum. Resolution The use case and implementation details are documented in the comment section of the PE program.   Here is the actual PE code to implement, please note that this PE program is provided as a sample only, to serve as guidelines and proof of concept, considerable changes may be necessary to make the program adequate for your particular application and site.    Numeric Green Numeric Red Numeric StrikeTimer Line INIT Green = Unlocked Red = Locked 'LOCK ALL 3 DOORS PerimDrStriker = Locked IntDr1Striker = Locked IntDr2Striker = Locked 'MAKE ALL DOORS AVAILABLE FOR ACCESS TO THE AIRLOCK PerimeterDoor = Green InteriorDoor1 = Green InteriorDoor2 = Green 'ALLOW CREDENTIAL ACCESS PerimeterDoor DisRdrKpAccess = False InteriorDoor1 DisRdrKpAccess = False InteriorDoor2 DisRdrKpAccess = False 'ALLOW EXIT REQUESTS PerimeterDoor OpenOnExitReqst = True InteriorDoor1 OpenOnExitReqst = True InteriorDoor2 OpenOnExitReqst = True Goto Monitor1 Line Monitor1 If PerimeterDoor ValidAttempt or PerimeterDoor ExitRequest then 'ACCESS ATTEMPT AT PERIMETER DOOR StrikeTimer = PerimeterDoor DoorStrikeTime 'UNLOCK THE DOOR... Goto PerimActive 'AND MAKE THE PERIMETER DOOR ACTIVE Endif If InteriorDoor1 ValidAttempt or InteriorDoor1 ExitRequest then 'ACCESS ATTEMPT AT INTERIOR DOOR1 StrikeTimer = InteriorDoor1 DoorStrikeTime 'UNLOCK THE DOOR... Goto Interior1Active 'AND MAKE THE INTERIOR DOOR1 ACTIVE Endif If InteriorDoor2 ValidAttempt or InteriorDoor2 ExitRequest then 'ACCESS ATTEMPT AT INTERIOR DOOR2 StrikeTimer = InteriorDoor2 DoorStrikeTime 'UNLOCK THE DOOR... Goto Interior2Active 'AND MAKE THE INTERIOR DOOR2 ACTIVE Endif 'CHECK FOR FORCED ENTRY If PerimeterDoor DoorSwitch = Opened or InteriorDoor1 DoorSwitch = Opened or InteriorDoor2 DoorSwitch = Opened then Goto AirLockForced Line AirLockForced 'MUST HANDLE FORCED ENTRY HERE DUE TO VALUE OF DOOR BEING SET TO UNLOCK TO MAKE LED GREEN AirLockAlarm = 1 'SEND THE ALARM 'MAKE ALL DOORS UNAVAILABLE PerimeterDoor = Red InteriorDoor1 = Red InteriorDoor2 = Red If PerimeterDoor DoorSwitch = Closed and InteriorDoor1 DoorSwitch = Closed and InteriorDoor2 DoorSwitch = Closed then 'FORCED ENTRY CLEAR, RESET THE AIRLOCK AirLockAlarm = 0 Goto INIT Endif Line PerimActive 'ACCESS REQUESTED AT PERIMETER DOOR, DISABLE CREDENTIAL AND REX ACCESS AT THE INTERIOR DOORS InteriorDoor1 DisRdrKpAccess = True 'DONT ALLOW CREDENTIAL ACCESS AT THE INTERIOR DOORS InteriorDoor2 DisRdrKpAccess = True InteriorDoor1 OpenOnExitReqst = False 'DONT EXIT REQUESTS AT THE INTERIOR DOORS InteriorDoor2 OpenOnExitReqst = False InteriorDoor1 = Red InteriorDoor2 = Red 'UNLOCK THE PERIMETER DOOR PerimDrStriker = PerimeterDoor DoorStrikeTime 'WAIT FOR PERSON TO PHYSICALLY OPEN THE DOOR If PerimeterDoor DoorSwitch = Opened then Goto PerimInactive 'DOOR NEVER OPENED, RESET AIRLOCK If TS > PerimeterDoor DoorStrikeTime then Goto INIT Line PerimInactive 'HANDLE ACCESS REQUEST WHILE DOOR OPENED, EXTENDED DOOR UNLOCK TIME If PerimeterDoor ValidAttempt or PerimeterDoor ExitRequest then PerimDrStriker = (PerimDrStriker + 1) If PerimeterDoor DoorSwitch = Closed then Goto INIT 'WE'VE BEEN HERE TOO LONG, SEND ALARM If TM > 0 then AirLockAlarm = 2 Line Interior1Active 'ACCESS REQUESTED AT INTERIOR DOOR1, DISABLE CREDENTIAL AND REX ACCESS AT THE PERIMETER DOOR PerimeterDoor DisRdrKpAccess = True PerimeterDoor OpenOnExitReqst = False PerimeterDoor = Red InteriorDoor2 = Green 'UNLOCK THE INTERIOR DOOR1 IntDr1Striker = InteriorDoor1 DoorStrikeTime 'WAIT FOR PERSON TO PHYSICALLY OPEN THE DOOR If InteriorDoor1 DoorSwitch = Opened then Goto Interior1Inactiv 'DOOR NEVER OPENED, RESET AIRLOCK If TS > InteriorDoor1 DoorStrikeTime then Goto INIT Line Interior1Inactiv 'HANDLE ACCESS REQUEST WHILE DOOR OPENED, EXTENDED DOOR UNLOCK TIME If InteriorDoor1 ValidAttempt or InteriorDoor1 ExitRequest then IntDr1Striker = (IntDr1Striker + 1) If InteriorDoor1 DoorSwitch = Closed then Goto INIT 'WE'VE BEEN HERE TOO LONG, SEND ALARM If TM > 0 then AirLockAlarm = 3 Line Interior2Active 'ACCESS REQUESTED AT INTERIOR DOOR2, DISABLE CREDENTIAL AND REX ACCESS AT THE PERIMETER DOOR PerimeterDoor DisRdrKpAccess = True PerimeterDoor OpenOnExitReqst = False PerimeterDoor = Red InteriorDoor1 = Green 'UNLOCK THE INTERIOR DOOR2 IntDr2Striker = InteriorDoor2 DoorStrikeTime 'WAIT FOR PERSON TO PHYSICALLY OPEN THE DOOR If InteriorDoor2 DoorSwitch = Opened then Goto Interior2Inactiv 'DOOR NEVER OPENED, RESET AIRLOCK If TS > InteriorDoor2 DoorStrikeTime then Goto INIT Line Interior2Inactiv 'HANDLE ACCESS REQUEST WHILE DOOR OPENED, EXTENDED DOOR UNLOCK TIME If InteriorDoor2 ValidAttempt or InteriorDoor2 ExitRequest then IntDr2Striker = (IntDr2Striker + 1) If InteriorDoor2 DoorSwitch = Closed then Goto INIT 'WE'VE BEEN HERE TOO LONG, SEND ALARM If TM > 0 then AirLockAlarm = 4 Line E If TS > 30 then Goto INIT    See also attached dump file of program code.  

Issue What are the basics steps when setting up the Engage Mobile application to use it for the first time? Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) Cause The Engage mobile application enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. Resolution Below are the basic steps when setting up the Engage Mobile application to use it for the first time:  First create and configure the Occupant App Menu object. Make sure Bluetooth is enabled for the RP-C. Download the Engage mobile application and connect to the RP-C Available on App Store and Google Play To see details for every step please see video:  

Issue The Local Variables Pane in the Script Editor is not displaying local variables or arrays. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Local Variables Pane can only be used in debug mode, i.e. when pressing Start and then either Step or trace (Trace On) through the script. When the Script Editor is not in debug mode the Local Variables Pane is empty. Note that the debugger is not available at all when editing scripts in the RP-C or MP-X, or when using Script Event Programs.  Resolution Click Start in the Debug tool list at the top of the Script Editor (or press F5) to start debugging. The local variables will now be visible in the Local Variables pane. If you have arrays you can expand them by clicking the plus sign. Next use the Step button (or press F10) to step through the program. The values of the local variables will change as the script is executed line by line. ClickTrace On to automatically step through the program. ClickTrace Off to stop the automatic stepping. For troubleshooting purposes, values can also be updated directly by editing the entry in the Value column in the Local Variables pane. 

Issue Controller Health Status shows, "Controller (ID **) has too many Remote Controllers assigned." What does this message mean, and is it a cause for concern? Product Line Security Expert Environment Security Expert Client SP-C Controller Cause This error message is related to cross controller communication. When using cross controller communications, the maximum number of controllers that can be linked together is 64. For additional details on cross controller communications, see page 4 of AN 180 Security Expert - Cross Controller Operations - Integration Guide. Resolution The controllers that are not taking part in cross controller linking are the ones that are showing the "Controller (ID **) has too many Remote Controllers assigned." message. Evaluate what values/controllers are being shared to ensure your programming is performing as expected. See AN 180 Security Expert - Cross Controller Operations - Integration Guide for further details on cross controller communications and which values use this. Limit the number of sharing controllers to 64 or split the controllers up into two systems.

Issue When there are multiple displays, and the script editor is in the right window, the autocomplete popup window goes off-screen. *note* this only happens in full screen Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The issue depends on which way you assign the two monitors in the Windows settings or how you have the monitor cables hooked in the docking station/laptop. Resolution Swap the physical monitor plugs on the PC or docking station, allowing Windows to recognize your monitors synchronously from left to right Go into your Windows monitor settings and drag each screen to its proper position and hit apply.

Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions.  (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.