Building Automation Knowledge Base

Issue Reload of BCX receives error "Infinity controller error: Controller has no assigned Infinet port An error was detected while attempting to set an attribute in a remote Infinity object" Product Line Andover Continuum Environment Continuum Cyberstation BCX 9640 BCX4040 Infinet controller b3 Cause Reloading of a BCX 9640 resulted in error "Infinity controller error: Controller has no assigned Infinet port.  An error was detected while attempting to set an attribute in a remote Infinity object"   Suspected that a learn on the commport was performed or infinet controllers were manually created causing no assigned comm port. Resolution As with any edit of the Continuum system, please make sure to backup the database.   Follow these steps: Send BCX to text file  Add commport to each Infinet controller entry as below Import newly edited text dump file into the BCX. Reload BCX   Example of an original dump file exported in step 1 and the new dump file after the commport is added in step 2. Original Dump File New Dump File Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   SerialNum : 12345   VersionNum : 2.160000  EndObject   Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   Port : comm2   SerialNum : 12345   VersionNum : 2.160000  EndObject  

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

Issue In order to troubleshoot random network issues, it is sometimes necessary to set up Wireshark to capture network traffic for an extended period of time. As Wireshark runs it decodes packets and its data structures grow. This causes performance issues and eventually, Wireshark may simply run out of virtual memory and stop capturing or crash. Product Line Andover Continuum, EcoStruxure Building Operation Environment Wireshark Cause Need to capture network traffic using Wireshark for an extended period of time. Resolution Open Wireshark and follow these instructions: From toolbar, select Capture -> Options On the Input tab, select input adapter. If necessary set capture filter. On the Output tab, perform the following: Browse capture file location and provide a filename. A timestamp will be added to the filename as a suffix. Ensure output format = pcapng Check Create a new file automatically Check After 1 and change seconds to hours Check when time is multiple of 1 and change seconds to hour Check use a ring buffer with X files. (Recommended settings are 96 hours (4 days) or 168 hours (1 week) so can retrieve files after long weekend or 1 week, respectively).  On the Options tab, perform the following Check last selection and change to 744 hours. (Recommended to capture for 31 days without stopping).  When an event happens, gather a capture with the timestamp before and after the event. One can ZIP the .pcapng files to save space when transferring.   NOTE: More recent versions of Wireshark ( 2.4.1.21317 ) make it very easy to set up a ring buffer from the Output tab of the Capture options. For older versions of Wireshark 1.x use the steps below When capturing data, Wireshark actually uses a capture utility called DumpCap to do the actual data capture. DumpCap does not decode packets as they come in and thus has a smaller memory footprint which remains constant. The only remaining concern is the size of the capture file or files which can be specified when starting the ring buffer to keep them from growing too big. DumpCap is found at the location where the Wireshark program resides which can be seen if you go to Help\About Whireshark\Folders Determine the index to the Ethernet adapter you need to capture on. In this example, the traffic seen by the Broadcom NetXtreme Gigabit Ethernet adapter will be captured. Index 1 is specified when starting DumpCap. Execute DumpCap with the following options dumpcap -i 1 -b files:3 -b filesize:10 -w C:]temp\abe.pcapng -i 1 specifies tp capture on the network adapter with an index of 1 -b file: 3 specifies to use a 4 file ring buffer. -b filesize:10 specifies to limit the file size to 10 KB (*** for a real life capture this number would be much bigger like say 100/200 MB) -w c:\temp\abe.pcapng specifies location and prefix for the three files In the screenshot below we can see the files in the ring buffer being used, once a file reaches the specified limit, the capture continues at the next file, files are names using the specified prefix as well as a date-time stamp that is updated each time utility dumps captured data in the file. Care should be taken to stop the capture as soon as possible once the issue under investigation takes place and before the ring buffer wraps around and overwrites the data.

Issue A network level controller is shown offline. Can a flash upgrade (Update OS) be done to it? Product Line Andover Continuum Environment BCX ACX5720 ACX5740 NC2 CX9900 Cause A bCX needed a flash upgrade but was offline in CyberStation. How can we update the OS? Resolution The Update OS function can sometimes be completed even if the controller indicates that it is offline. If it cannot be pinged from CyberStation, it will not likely be able to be upgraded in its current state and may require returning for repair. But if it can be pinged it, try doing the Update OS. Follow the progress in the Distribution window. If it completes, the controller will likely come back online a few minutes after the update is complete Completing this "Blind Update OS" can often restore to normal operation a controller that has its Operating System corrupted not allowing the Web page to be accessed, as long as you know the ACCNet ID and IP address (a reset IP can be performed) this process may be attempted. It is also possible to flash an offline controller if it has reverted to the default IP address (169.254.1.1) and ACCNet ID of 1 if the Workstation is set to be in the same subnet so it can ping the controller and these default settings are used for the controller configuration. If after a full cold restart and at least 2 attempts to flash the controller fail, then the controller may need to be returned for Repair. Some possible causes of this problem are listed in What can cause a controller to reset, cold start or lose data.

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver. Product Line Andover Continuum Environment Modbus Protocol Cause Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver according to the modbus protocol. Resolution The maximum number of nodes is 254. The address range for points is 1 through to 65535. The number of addresses is limited by the controller memory. We have had ~6000 points but please note the Modbus is a polled protocol so the more points you have the longer the poll rate.   Specific Modbus RTU Details Our Modbus RTU XDriver supports the node range from 0-255. According to the Modbus specification, the node range is from 0 – 255, with 0 being the master, 1-247 being the slaves, and 248-255 being reserved addresses. After 32 nodes (1 master + 31 slaves), you may need RS-485 repeaters to ensure proper communications. This depends on a number of different items, including if the RS485 transceivers are full or quarter load. You can find the Modbus serial standard at the link below for further details. http://www.modbus.org/docs/Modbus_over_serial_line_V1.pdf

Issue Unable to connect to a BCX configuration page Product Line Andover Continuum Environment Continuum BCX9640 and 4040 Cause 404 Page not found error accessing the configuration page using the controller IP in a browser Resolution Note: This document is for troubleshooting help, it is not a comprehensive BCX setup guide. Please refer to the BCX1 Technical Reference for detailed setup instructions.   Using a LAN or a cross-over cable? If the BCX is on a LAN and was working before, remove the LAN cable from the BCX and try to ping the BCX. If you get a response then you have a duplicate IP. Same subnet? Make sure DHCP is disabled on your computer. Use a straight-through or cross-over cable to access the BCX directly. Has this cable been used successfully before? Reset the BCX to the default IP. The button is under the cover, top right. Be sure to hold down the IP reset button for about 20 seconds Is the controller in bootloader mode? This can be seen by observing the CPU light flashing rapidly, approximately two times a second (2 Hz at 50% duty). Flashing the application through Cyberstation may fix this and enable you to get back into the controller. Even though access to the config page is not available, the update OS button in Continuum using the controller's Network setting and ACCNet ID may be accessible to perform a firmware upgrade. Ping the IP from a DOS prompt, can the BCX be pinged? Ex. Ping 169.254.1.1 Use Ipconfig /all to see your PCs network settings. The best case scenario is to be on the same subnet or connect directly. Are there multiple NIC cards on the PC? (Ex. Ethernet and wireless on a laptop) Disable the wireless adapter or other adapters. Continuum does not support a multiple NIC card configuration. Run Wireshark to get a capture between the BCX and The PC. Remove power from the BCX and reapply power. When the BCX starts it sends a gratuitous ARP that will indicate the IP address within the BCX. It may be a different IP than expected. Did the issue of not accessing the web page happen after a power outage? Is the CPU light flashing amber and it was flashing green before and no one has flashed the controller? Is the CPU light solid amber? If so, contact support for assistance.

Issue BACnet MSTP Capture Application Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP capture application provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution Download the latest version. Browse to Steve Karg's  BACnet Protocol Stack - Browse /bacnet-tools at SourceForge.net Select the version folder Select bacnet-tools-[n.n.n].zip file to download it From the zip file, extract mstpcap.exe Now you can use it via command prompt as described below or install it in C:\Program Files\Wireshark\extcap if want to use with modern Wireshark version.   To capture data follow these steps: Unzip file Open command prompt with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Bluetooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further information or instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue An error is received 'Error connecting to server' while testing a Digital Sentry DVR connection with Cyberstation 1.90 or 1.91. Product Line Andover Continuum Environment Continuum 1.90 Continuum 1.91 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The DS Connex version of newer Digital Sentry DVRs are not compatible with Continuum 1.90 or 1.91 Resolution The DSConnex version of newer Digital Sentry DVRs are not compatible with Continuum 1.90 or 1.91 unless the following hotfix is applied. Click here to download the hotfix

Issue Cannot Delete Personnel  Product Line Andover Continuum Environment Continuum  1.8X & 1.9X Windows XP Windows 2003 Server Continuum ACX5740 Microsoft SQL 2005 Cause Stored Procedure packPersonneldeletion failed to run Resolution Duplicate personnel.   Remove Areas from the personnel object. Delete duplicate personnel objects.

Issue Want a method to show all the Access Events that a Personnel has had during a specific period of time. Environment Continuum Access Control Cause A method to search Access Events for a specific Personnel during a specific period of time. Resolution One method to do this would be to use Listviews. There are a number of default Listviews already available in a default ContinuumDB, one of these can be used as a basis for our new Listview. This is done by adding a database qualifier to a copy of the default Events_Today Listview. Make a copy the Events_Today Listview  Add the prompt for a card number search using: DBQualifier : (CardNumber is Prompt("Please Enter a Card number", 0) and Template = False) This will return all the events today for the card number that the user inputs in the prompt box when running the Listview.  

Issue Where can I find information on LCX89x controllers. Environment LCX89x LCX890, LCX898 Cause While LCX89x controllers are being sold by Schneider Electric as of April 19, 2013, there is not a lot of information on the LCX line at the Extranet website. Resolution Series LCX 890 Infinet Controllers       Part Number Description     01-0008-036 LCX 890 Lighting Controller, 8 outputs w/RR9 relays     01-0008-037 LCX 890 Lighting Controller, 8 outputs no relays     01-0008-039 LCX 891 Lighting Controller, 16 outputs w/RR9 relays     01-0008-040 LCX 891 Lighting Controller, 16 outputs no relays     01-0008-042 LCX 892 Lighting Controller, 24 outputs w/RR9 relays     01-0008-034 LCX 892 Lighting Controller, 24 outputs no relays     01-0008-081 LCX 898 Lighting Controller, 48 outputs no relays     01-0008-083 LCX 898 Lighting Controller, 48 outputs w/RR9 relays   LCX890 Series Controller Installation Guide

Issue Editing a point on the MPM in Continuum via BACnet will result in the follwoing error message:  "Communications failure due to routing device not available" Product Line Andover Continuum Environment SmartStruxure Lite Multi-Purpose Manager, Building Expert, CyberStation Cause Known Bug Resolution To resolve the issue, CyberStation must be updated. Option 1: Upgrade CyberStation to 2.0. Option 2: Download and apply the 921 hotfix to v1.94 SP1

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue Proper way to 'activate' portions of Personnel Import Utility (PIU) XSL files. Product Line Andover Continuum Environment CyberStation with PIU Cause Difficulty in getting transformation file to import records Resolution Transformation files used with the PIU are located in the \Continuum directory. These are XSL files and are built in a way that features are commented out in the file and those features can be 'activated' by uncommenting. XSL is a language for expressing style sheets. An XSL style sheet is a file that describes how to display an XML document of a given type. When the XSL files are opened with Internet Explorer (IE) you see color-coding and bold text. The bold text is activated, the light grey is not. You can only view the code in IE, not edit it. Use an advanced text editor like Notepad ++ (https://notepad-plus-plus.org/) and you can easily see and edit the file to activate portions of it. Note: Make sure when 'activating" the syntax option in the file by removing the leading  - <!--   you also remove the trailing   --> .  The following is what the file CSVToContinuumTransformation.xsl looks like.   <?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:TAC="http://www.tac.com/TAC" extension-element-prefixes="msxsl" exclude-result-prefixes="TAC"> <!-- - define the Javascript or C# or VBScript functions that you want to include within a msxsl:script element. - language indicates the scripting language - implements-prefix gives the namespace prefix that you declared for your function (i.e. TAC) - Use the functions where ever you want. For example <alias> <xsl:value-of select="TAC:today()" /> </alias> --> <msxsl:script language="C#" implements-prefix="TAC"> <!-- it's often helpful to use a CDATA section so you don't have to worry about escaping less-than signs or anything --> <![CDATA[ public string today() { return "abcdefs"; } ]]> </msxsl:script> <!-- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes"/>--> <xsl:template match="SourceUsers"> <SourceUsers> <xsl:apply-templates select="SourceUser"/> </SourceUsers> </xsl:template> <!-- Need to include only the mapped personnel attributes or if every thing everything is added remove the ones that are included below in XSLT tags--> <xsl:template match="SourceUser"> <!-- You can declare variables, parameters --> <xsl:param name="allPhoneNumbers" select="HomePhone"/> <xsl:copy> <xsl:copy-of select="ADA|Address|AllowEntEntEgr|Blood|CardNumber|CardType|City|Country|DateOfBirth|DefaultClearanceLevel| Department|DepartmentCode|EmergencyContact|EmergencyPhone|EmpNumber|ExecutivePrivilege|ExpirationDate|EyeColor| FirstName|HairColor|Height|HomePhone|Info1|Info2|Info3|Info4|Info5|Info6|JobTitle|LastName|LicenseNumber| LostCard|MiddleName|NonABACardNumber|OfficeLocation|ParkingSticker|PIN|SecurityLevel|Sex|SiteCode| SocSecNo|StateOfResidence|StartDate|Supervisor|VehicleInfo|Visitor|Weight|WorkPhone|Zip|FipsAgencyCode|FipsOrgId| FipsSystemCode|FipsCredentialNumber|FipsCredentialSeries|FipsOrgId|FipsCredentialIssue|FipsOrgCategory|FipsPersonId| FipsPersonOrgAssociation|FipsPivState|FipsPivControlled|FipsExpirationDate|PhotoFile|Signature|ResponseTransaction|State|FipsHmac"/> <!--<Adding OwnerFolder to personnel object. This is must other wise it won't create or update any objects>--> <OwnerFolder>Root\CardHolders</OwnerFolder> <!--<Adding OwnerFolder to personnel object end>--> <!--<Alias is necessary to create or update object and it should be unique in the system>--> <Alias> <!-- By default, we'll use the employeeNumber + samaccountname as an alias (16 chars max). --> <!-- On newer systems, the logon name is userPrincipalName --> <!-- One Way --> <!-- <xsl:value-of select="concat(samaccountname,EmpNumber)"/> --> <!--<xsl:value-of select="concat(FirstName,LastName)"/>--> <!--In IDMS system Serial Number is a unique number. Use this as Alias added to a Character or a group of characters to generate a valid alias. See the Example --> <xsl:value-of select="concat(FirstName,LastName)"/> <!--<xsl:choose> <xsl:when test="string-length(EmpNumber)=0"> <xsl:value-of select="samaccountname"/> </xsl:when> <xsl:otherwise> <xsl:value-of select="concat(LastName,EmpNumber)"/> </xsl:otherwise> </xsl:choose> --> <!-- Other Ways --> <!-- This option combines the last name and EmpNumber --> <!--<xsl:value-of select="concat(substring(LastName,1,12),substring(EmpNumber,2,5))"/>--> <!-- This option combines the EmpNumber last and first name from CyberStation --> <!--<xsl:value-of select="concat(EmpNumber,FirstName,LastName)"/> --> <!-- This option combines the last name and FirstName --> <!--<xsl:value-of select="concat(LastName, FirstName)"/>--> </Alias> <!-- Example of using User defined functions --> <!-- <alias> <xsl:value-of select="TAC:today()" /> </alias>--> <!--<Adding departmentcode DepartmentCode to personnel object if it contains only numbers>--> <!--<<xsl:value-of select="number(department)"/>--> <!-- <DepartmentCode><xsl:number value="Department" /></DepartmentCode> --> <!--<Adding CardType>--> <!--<CardType>AC4plus432</CardType>--> <!--<Adding SiteCode>--> <!--<SiteCode>15</SiteCode>--> <!--<Adding Signature, PhotoFile, FingerPrint use firstname.jpg or Lastname.jpg or Firstname+LastName.jpg. Use the combination depending upon the jpg files stored on the hard drive. A few examples below >--> <!--<Adding Signature>--> <!--<Signature>D:\picsForSri\signatures\LISASIG.BMP</Signature>--> <!--<Signature> <xsl:value-of select="concat('D:\',FirstName,'.jpg')"/> </Signature>--> <!--<Signature> <xsl:value-of select="concat('c:\',Lastname,'.jpg')"/> </Signature>--> <!--<Adding FingerPrint>--> <!--<FingerPrint>D:\picsForSri\Fingerprints\Finger.jpg</FingerPrint>--> <!--<Adding photofile>--> <!--<PhotoFile>D:\picsForSri\pics\Elmer1.jpg</PhotoFile>--> <!--Assigning default areas to the imported personnel--> <!-- To implement Area Links, uncomment the section below before the <AreaLinks> tag and after the </AreaLinks> tag--> <!-- To add more areas, copy the <AreaLink></AreaLink> tags and everything between them and paste after the first </AreaLink> tag--> <!-- State can be Enabled or Disabled, Preload is Workstation Only and can be True or False, AreaId example - Root\MyPersonnelFolder. --> <!-- This is line 1 of 2 to remove to implement Area Links <AreaLinks> <AreaLink> <AreaId><![CDATA[Full Path To Area Here]]></AreaId> <SchedId>Full Path To Schedule Here</SchedId> <State>Enabled</State> <Preload>False</Preload> <ClearanceLevel>0</ClearanceLevel> </AreaLink> </AreaLinks> This is line 2 of 2 to implement Area Links --> <!--<Adding Templates to personnel object>--> <!--<Adding Templates to personnel object with Department name>--> <!--<RefTemplate> <xsl:value-of select="concat('Root\Templates\Personnel Templates\', Department)"/> </RefTemplate>--> <!--<Adding Templates to personnel object based on department>--> <!--<Can do the same way with departmentCode DepartmentCode>--> <!--<xsl:value-of select=AreaTemplate1000/> same as <xsl:text>AreaTemplate1000</xsl:text>--> <!--<RefTemplate> <xsl:choose> <xsl:when test="StateOfResidence='MA'"> <xsl:text>Root\Templates\Personnel Templates\AllAccess</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='NY'"> <xsl:text>Root\Templates\Personnel Templates\PowerUser</xsl:text> </xsl:when> <xsl:otherwise> <xsl:text>Root\Templates\Personnel Templates\StandardUser</xsl:text> </xsl:otherwise> </xsl:choose> </RefTemplate>--> <!--<Adding one personnel Template to personnel object >--> <!--<RefTemplate> Root\Templates\Personnel Templates\PT1</RefTemplate>--> <!--Template> <xsl:choose> <xsl:when test="StateOfResidence='MA'"> <xsl:text>Root\Templates\Personnel Templates\All Access</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='PA'"> <xsl:text>Root\Templates\Personnel Templates\Power User</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='NY'"> <xsl:text>Root\Templates\Personnel Templates\Standard User</xsl:text> </xsl:when> </xsl:choose> </RefTemplate>--> <!--<Adding one personnel Template to personnel object >--> <RefTemplate>Root\Templates\Personnel Templates\Standard User</RefTemplate>--> <!-- Manipulate states--> <!-- If the attribute is using here don't add it at the <xsl:copy-of select--> <!-- <StateOfResidence> <xsl:choose> <xsl:when test="StateOfResidence='Massachusetts'"> <xsl:text>MA</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='New Hampshire'"> <xsl:text>NH</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='Washington DC'"> <xsl:text>DC</xsl:text> </xsl:when> <xsl:when test="StateOfResidence='Connecticut'"> <xsl:text>CT</xsl:text> </xsl:when> <xsl:otherwise> <xsl:value-of select="StateOfResidence"/> </xsl:otherwise> </xsl:choose> </StateOfResidence>--> <!-- Manipulate phone numbers--> <!--</telephonenumberFormat>--> <!-- <WorkPhone> <xsl:choose> <xsl:when test="contains(WorkPhone,'-')"> <xsl:value-of select="WorkPhone"/> </xsl:when> <xsl:when test="string-length(WorkPhone)=0"> <xsl:value-of select="WorkPhone"/> </xsl:when> <xsl:otherwise> <xsl:value-of select="concat(substring(WorkPhone,1,3),'-',substring(WorkPhone,4,3),'-',substring(WorkPhone,7,4))"/> </xsl:otherwise> </xsl:choose> </WorkPhone> --> <!--Replacing the linefeed in the adress --> <!-- Unicode of linefeed &#xA; (is line break \n), Unicode of tab &#x9;--> <!-- <xsl:value-of select="translate(Address, '\n', ' ')"/> Won't work --> <!-- <Address> <xsl:value-of select="translate(Address, '&#xA;', ' ')"/> </Address> --> <!--************************************************************** --> <!--These are the examples of how to parse Multi valued Active Directory attributes after mapping them to Continuum attributes --> <!-- Use Continuum attributes names instead of these dummy attribute names, variables names can be at as your wish --> <!-- This example takes the first element from the list, it shows the use of a variable --> <!--<HomePhone> <xsl:variable name="phoneNumbers" select='HomePhone'/> <xsl:value-of select="substring-before($phoneNumbers, ',')"/> </HomePhone>--> <!-- This example takes the second element from the list. --> <!-- It uses a param at the top of the file. after the line <xsl:template match="SourceUser">--> <!--Or use a local variable between phone2 tags<xsl:variable name="allPhoneNumbers" select='HomePhone'/>--> <!-- <Phone2> <xsl:variable name="after-first-comma" select='substring-after($allPhoneNumbers,",")'/> <xsl:variable name="second-comma" select='substring-before($after-first-comma,",")'/> <xsl:value-of select="$second-comma"/> </Phone2> --> <!-- This example outputs a xml tag if the element exists in the list --> <!-- <memberOf> <xsl:variable name="memberGroups" select="memberOf"/> <xsl:if test="contains($memberGroups, 'Engineering')"> Engineering Lab1 </xsl:if> </memberOf> --> <!--************************************************************** --> </xsl:copy> </xsl:template> </xsl:stylesheet>

Issue When trying to open web pinpoint on a remote client session the users receive the error below: Product Line Andover Continuum Environment MS Server 2008 and newer Windows 7 and newer Continuum 1.9x and 2.x webClient Remote Desktop Cause This issue is caused when a remote desktop connection is made on a Windows 7, Windows 2008 server or newer Operating Systems.  The console becomes locked.  It will stay locked until the local session is restored with a logon. Resolution  Resolution: 1)      Create a Bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console ***********************************************************************************************   2)      Place this file on the desktop of the Web Server system. 3)      When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be ran “As an Administrator” This will disconnect the session and restore the console.

Issue Is it possible thru PE or any other means to have more than 4 site codes assigned to a door in Continuum? A developer of a multi-tenant building has more than 4 clients all using HID proximity cards but each with different site codes. The main entrance is common to all tenants. How can the developer put a card reader on it with Continuum? Product Line Andover Continuum Environment CyberStation AC-1 family ACX family Cause Is it possible thru PE or any other means to have more than 4 site codes assigned to a door in Continuum? Resolution A single door object in Continuum is limited to the 4 site codes. If you do not need alarms, i.e, you just need an electronic key then there is a hardware workaround. Add a reader distribution amp like the RDA1 from ETS of Albuquerque, NM. The input of the RDA1 is wired to the card reader at the door. The outputs of the RDA1 are wired to multiple Continuum reader ports (AC-1s or ACX). Create another door object with the same arealink. Now you have 4 more site codes. You'll need to do some input and output re-wiring and every card read will give you at least one invalid attempt (invalid site code on one of the two door objects). If you can live with that, you're all set.  

Issue Upgraded Site to Continuum 2.01, now get %N and %D in Alarm Message as seen in the message field in the snapshot below: Product Line Andover Continuum Environment Cyberstation Keywords %D %N Cause This is caused by the Enhanced Alarm Logging and Enhanced Alarm Delivery being unchecked Resolution This can be resolved by using the following steps: Close all the cyberstations Initialise the database making sure you have Enhanced Alarm Logging and Enhanced Alarm Delivery ticked as shown below:  

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the statistics from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2)

Issue When you're having issues with Continuum you need to check if the Windows account you are logging on with is part of the Local Administrators Group. Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows 2008 Server Continuum 1.9X Cause Permission issues running or installing Continuum 1.9X Resolution Download the attached TestUserAdmin.zip file unzip the TestUserAdmin.exe file to your Desktop Open the Command window (DOS prompt) and run the TestUserAdmin.exe  The program will indicate if the logged on Windows user is a member of the Local Administrators Group or not.