Issue Implementing a pre-entry access card anti-passback using Plain English program Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause The anti-passback implementation in Continuum engages when the credential holder enters the area as detected by the door switch/contact. (if no door switch is configured, then the credential holder is considered to have entered the area immediately after access has been granted by the system) When doors are located in close proximity to each other, as is the case with a bank of turnstiles, for example, the built-in anti-passback scheme is easily defeated as a cardholder is able to unlock multiple nearby turnstiles before triggering the door contact and engaging the built-in anti-passback functionality. Resolution The simplest solution to the issue described above is to configure the door objects WITHOUT a door switch/contact, this, however, is not always possible depending on on-site requirements. A second solution is to take control of the doors using Plain English. The solution presented here is for a bank of three turnstiles, (A, B, and C), it uses a PE program per turnstile. The solution can easily be adapted for a bank of less or more turnstiles. NOTE: The PE programming here is provided as a sample, for guideline purposes only, the programs are not intended as a complete solution, significant modifications may be required for site deployment. Program code for door/turnstile A 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' |_____X______X______X______ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the 'initialization line which specifies which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileB, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_B, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_B, theLastCrdTime_C Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_A theTurnstileB = Turnstile_B theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_A_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileA_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM '------------------------------------------------------------------------------------------ Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile B 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of the following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_C '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_B theTurnstileA = Turnstile_A theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_B_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_B_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileB_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_B_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile C   'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileB 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_B, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_B '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_C theTurnstileA = Turnstile_A theTurnstileB = Turnstile_B 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_C_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_C_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum thisAlarmPoint = TurnstileC_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_C_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING         ... View more

Issue RTD-DI-16 temperature input range is -50C to 150C, some applications require a wider range. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation I/O Module 16 Ch RTD Cause Script program sample and guidelines needed for implementing resistance to temperature table lookup and further temperature calculation using linear interpolation. Resolution We will present two solutions, the first solution is very simple to implement but at the expense of accuracy. The second solution retains the 0.3C accuracy of the native RTD inputs. For simplicity, both solutions implement a range of -50C to 250C using the RTD Resistance electrical type to convert resistance to temperature, the program can be easily modified to implement a wider range.     SOLUTION #1 This solution simply uses the conversion settings of the RTD-Resistive input to convert from Ohms to Degrees C. Because the change in resistance is not exactly linear across the temperature range, the accuracy of the converted value varies across the range as much as +/- 4 degrees C      STEPS TO IMPLEMENT SOLUTION #1 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Change the units to degrees Celsius. Select the sensor class, in this example, we are using the pt100 sensor. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) Use values from step #4 to set the input's conversion electrical scale.  Set the engineering scale top/bottom to 250 and -50 respectively.    STEPS TO IMPLEMENT SOLUTION #2 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) In the Automation Server, create an Analog Value object. This object will receive the calculated temperature value from the Script program. Set the AV units to degrees C In the Automation Server create a Script program, this program will read the resistance from the input object, look up the corresponding temperature range in the table, and then using linear interpolation calculates the temperature to an accuracy of +/- 0.3C. To ensure the program when runs when necessary, configure the program's flow type for fall thru and trigger the program off of the RTD-2W-Resistive input. Bind the RTD-2W-Resistive input and the Analog Value in the Script program as Numeric Input and Numeric Output respectively.  Here is the code for the script program   'This program uses RTD temperature vs. resistance table combined with linear interpolation 'to implement RTD temperature input over the range -50C to 250C 'Program Flow Type is FallThru 'Program is triggered by the RTD resistance input. 'This program is provided as a sample for illustration purposes, it is not intended to be a complete solution 'SE PSS v1.0 101010111110 Numeric Input RTD_Raw 'the RTD Resistance input where the RTD sensor is connected Numeric Output RTD_Temp 'Analog Value that receives the calculated temperature Numeric RTD_R[31]'Resistance to Numeric RTD_T[31]'temperature table for 100 Ohms based sensor 'NOTE: Since the resistance value changes in a nearly linear way over any 10 degree section 'of the table, we can use 10 degree increments of resistance/temperature values and apply linear 'interpolation to calculate readings in between those values, this method greatly reduces the size 'of the table in the program while maintaining very good accuracy. 'Accuracy is +/-0.3C for 100 Ohms based sensors and can be improved to +/-0.03C if 1000 Ohms based sensor used. Numeric n, sLow, sHigh,sMid Line INIT 'Due to limitations in Script we will use 2 arrays to implement the resistance to temperature table. RTD_R[1]=80.31 RTD_R[2]=84.27 RTD_R[3]=88.22 RTD_R[4]=92.16 RTD_R[5]=96.09 RTD_R[6]=100 RTD_R[7]=103.9 RTD_R[8]=107.79 RTD_R[9]=111.67 RTD_R[10]=115.54 RTD_R[11]=119.4 RTD_R[12]=123.24 RTD_R[13]=127.08 RTD_R[14]=130.9 RTD_R[15]=134.71 RTD_R[16]=138.51 RTD_R[17]=142.29 RTD_R[18]=146.07 RTD_R[19]=149.83 RTD_R[20]=153.58 RTD_R[21]=157.33 RTD_R[22]=161.05 RTD_R[23]=164.77 RTD_R[24]=168.48 RTD_R[25]=172.17 RTD_R[26]=175.86 RTD_R[27]=179.53 RTD_R[28]=183.19 RTD_R[29]=186.84 RTD_R[30]=190.47 RTD_R[31]=194.1 'The temperature array could be easily omitted since once we have the first array index (n) we could easily calculate 'the corresponding temperature value, I have kept it for the purpose of simplicity. RTD_T[1]=-50 RTD_T[2]=-40 RTD_T[3]=-30 RTD_T[4]=-20 RTD_T[5]=-10 RTD_T[6]=0 RTD_T[7]=10 RTD_T[8]=20 RTD_T[9]=30 RTD_T[10]=40 RTD_T[11]=50 RTD_T[12]=60 RTD_T[13]=70 RTD_T[14]=80 RTD_T[15]=90 RTD_T[16]=100 RTD_T[17]=110 RTD_T[18]=120 RTD_T[19]=130 RTD_T[20]=140 RTD_T[21]=150 RTD_T[22]=160 RTD_T[23]=170 RTD_T[24]=180 RTD_T[25]=190 RTD_T[26]=200 RTD_T[27]=210 RTD_T[28]=220 RTD_T[29]=230 RTD_T[30]=240 RTD_T[31]=250 n=0 sLow = 1 sHigh = MaxItem(RTD_R) 'Initialize to the size of the table Line calculateTemp 'Bottom of range If RTD_Raw <= RTD_R[1] then RTD_Temp = -50.0 Stop Endif 'Top of range If RTD_Raw >= RTD_R[sHigh] then RTD_Temp = 250.0 Stop Endif 'Find the resistance input reading in the table using a binary search 'NOTE: 'In our case, what we are looking for is the lower value of the resistance range in the table that 'the input reading falls under. 'EXAMPLE if input value is 160.9 Ohms then it is in the range of RTD_R[21]=157.33 AND RTD_R[22]=161.05 'so the binary search will give us 21 While(1) If sHigh < sLow then n=sHigh 'the input value is not in the table but we now have RTD_R[n] of the range it is within break Endif 'calculate the mid point sMid = Round(sLow + (sHigh - sLow) / 2) if RTD_R[sMid] < RTD_Raw then sLow = sMid + 1 'if read value is larger then look again in upper half if RTD_R[sMid] > RTD_Raw then sHigh = sMid - 1 'if read value is smaller then look again in lower half if RTD_R[sMid] = RTD_Raw then n = sMid 'we've located the input value in the table, this is actually the exception Break endIf EndWhile 'Now, use linear interpolation to calculate the temperature If n > 0 Then RTD_Temp = (RTD_T[n+1]-RTD_T[n])*(RTD_Raw-RTD_R[n])/(RTD_R[n+1]-RTD_R[n])+RTD_T[n] Endif Stop Line E stop   NOTE: The accuracy of the temperature reading can be further improved by the use of 1000 Ohms based sensors as well as the use of 3 wire sensors so that the resistance of the leading wires can be taken into account. If 1000 Ohms based sensors are used then the resistance values in the table implemented in the Script program must be multiplied by 10 ... View more

Issue In Access Expert's 'View All Hardware' window, the status of controllers does not update. For example, controllers say 'Online' even though they are actually 'Offline' and vice versa. Live Monitoring window does not show disconnect/online events. Seq log shows error: Failed to Publish event.Moniker:MonikerItem {"Namespace":"MercuryServiceEvents","Nickname":"mercury:15-12-1"} Product Line Access Expert Environment Access Expert Premise Software Cause Enterprise Administrator group, under root, is missing permissions for Mercury service. Resolution Log into the Root instance, edit the Enterprise Administrator group, in the "Event Types" tab, make sure permission is granted to the Mercury Service and Mercury Commands ... View more

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Introducing a previously commissioned Continuum IOU module such as an AC-1 to an Access Expert or Security Expert site can cause communication issues in the LON bus due to duplicated node id. Product Line Andover Continuum, Security Expert, Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller Cause When IOU modules are commissioned in a Continuum system, the Net Controller assigns each module a Node ID, this is in addition to the LON Module ID that is unique to each module hardware, the purpose of the Node ID, is to decouple the identifier used by Continuum for communication from the specific piece of hardware, this in order to facilitate the replacement of a failed module without the need to change its Continuum identifier. The module stores the Node ID in nonvolatile memory so that it persists across power loss. If a Continuum IOU module is introduced to a LON network (Security Expert SP-AC1 or Access Expert AX-SSC) without clearing its Node ID, there is a risk of creating a duplicate Node ID condition that will prevent the LON network from operating properly. IMPORTANT This should not be an issue during the normal transition of Continuum site to Security Expert or Access Expert, as all the modules on the running LON bus should have unique Node IDs, this is only a problem when adding a module, or replacing a module with one that has been used before. Resolution In order to signal its presence on the LON network, each module will transmit on resetting its status network variable. If upon receiving this message, the Net Controller determines that the module is NOT in its local database, the controller will decommission the module by setting its Node ID to zero. Before introducing a Continuum IOU module that has been previously commissioned to the LON network of an SP-AC1 or SX-SSC controller, decommission the IOU module using the steps below: Attach the module to an empty Net Controller that is powered down with its battery removed. For a Net Controller II, in order to be absolutely sure that the Net Controller has an empty database, you may need to clear its backup in flash from a browser or by the use of the reset IP switch. See LL on how to use the controller's reset IP switch to clear its flash backup https://community.exchange.se.com/t5/Building-Automation-Knowledge/How-to-clear-the-controller-flash-backup-from-the-hardware-using/ta-p/5877 Power up the Net Controller Once the CPU led on the Net Controller starts blinking, press the 'Reset' button on the IOU module. Wait 30 seconds to make sure the decommissioning process has completed. Power down the Net Controller Remove the IOU module ... View more

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue When transitioning Continuum access control to Security Expert or Access Expert the Continuum power supply may need to be configured for auxiliary IO power mode.  Product Line Security Expert Access Expert Environment Continuum AC-1 IO Module Security Expert Controller Access Expert Controller Cause The UPS versions of the 120/240 AC Continuum power supply include two status signals that are meant for use by a CPU module. When connecting directly to an I/O module you must disable these signals. If signals are left enabled they will cause communication issues between the AC-1 IO modules and the Security Expert or Access Expert controller. Resolution This applies  ONLY to the UPS models of the Continuum power supplies (PS 120/240 AC 50-U, AC 65-U and AC 85-U)   Remove power from the unit. On the Continuum power supply, press both cover removal tabs inward simultaneously and pull up. Locate the Mode switch using the diagram below. *** With the tip of a small screwdriver, carefully slide the switch to the AUX position. Replace the cover.   NOTE: On older versions of the power supply, instead of a switch, two jumper components must be removed from the printed circuit board.   ... View more

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. ... View more

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) ... View more

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.   ... View more

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.   ... View more

Issue How to use Plain English programming to mirror the output controlling the door's striker to a second output on the Continuum controller. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 2 Controller Cause Sample PE program needed for guidance. Resolution Here are three samples of the same program for guidance on how to accomplish the desired application 'This program makes the Auxiliary output of the AC1 (Out chan 2) mirror the value of the output that controls the door 'striker (Out chan 1) 'Program is Looping/Autostart 'The MODE variable is used to control when Out2 should mirror Out1 as follows... ' '1=Always including manual override '2=On valid card or REX only Numeric MODE Line Init AuxOutput = 0 MODE = 2 Basedon MODE Goto Always, ValidAndRex Line Always AuxOutput = Door1 OverrideValue * 65535 Line ValidAndRex AuxOutput = Door1 * 65535 Line E If TS > 10 then Goto Init Program code has also been supplied in the attached dump file below. ... View more