Building Automation Knowledge Base

Issue Metasys® N2 Integration to SBO Product Line EcoStruxure Building Operation Environment Struxureware Building Operation Metasys N2 Cause This Quick Start Guide will assist the Schneider Electric branch or dealer installation team with the basic steps to bring the virtual BACnet devices emulated by the S4 Open: BACnet-N2 Router into the SmartStruxure environment as part of a Johnson Controls Metasys® N2 integration into SBO. This document is not intended to be a full tutorial or user manual for either the S4 Open: BACnet N2 Router or the SmartStruxure system. Refer to the manufacturer’s documentation for each of these systems for detailed information. S4 documentation, the complete Device Template library, and support utilities can be found on the support CD delivered with your S4 Open appliance. Please contact the S4 group for any questions on this process.  Resolution Step 1:   Follow the installation instructions provided with the S4 Open: BACnet-N2 Router to discover and publish the N2 devices in the Metasys® installation to BACnet IP. All operations in SmartStruxure will be against these emulated BACnet IP devices each representing the underlying N2 device. Investigate before you integrate! Validate the N2 bus to make sure that it is electrically in spec and that all N2 devices are working properly before starting the integration process. Assign a unique BACnet virtual network number to each S4 Open: BACnet-N2 Router. N2 devices connected to this S4 Open appliance are published as emulated BACnet IP devices under that network. The Configure Wizard in the S4 Open Management Console will assist you with generating a unique BACnet Device ID for each N2 device. Point instance numbers are included as attributes in our Device Templates for all application-specific controllers. Either of these can be manually overridden in the S4 Open Management Console to meet unique requirements. The S4 Metasys® Configuration File Conversion Utility can be downloaded from the S4 Group web site and will assist you in creating custom Device Templates for DX-9100 devices or application-specific controllers. You will need the corresponding .DMO or .PRN files as input to this utility. A detailed understanding of Metasys® N2 devices, the Metasys® system, and the associated configuration and commissioning utilities are necessary to support successful integrations. If you don’t have this expertise in-house, The S4 Group can recommend a consultant to assist you. NOTE: We highly recommend that you attend a two-day S4 Boot Camp to make sure that you have all the skills necessary to install and configure the S4 Open: BACnet-N2 Router. Step 2: Bring up the SmartStruxure BACnet discovery tab and select BACnet devices. In this example, you can see that the S4 Open BACnet-N2 Router was defined in Network 1 and the N2 devices are in Network 122. The other device in Network 1 in this example is a JCI NAE. The best practice is to assign the S4 Open: BACnet-N2 Router to the BACnet network that you are using as your BACnet backbone. As with any BACnet device, the BACnet-N2 Router must be assigned a unique BACnet device ID. Step 3: Expand the navigation pane to expose the BACnet Interface / IP Network folder. Then select and drag the N2 devices from the Device Discovery tab to the IP Network folder. SmartStruxure will tell you that an Upload is required. Respond OK. Step 4: Navigate to the IP Network folder, select the properties page for each device, and request an Upload operation. This will bring the device properties and point list for each N2 device into SmartStruxure. SmartStruxure will respond with the following confirmation as each upload is completed. Step 5: When the Upload process is completed for all N2 devices and the S4 Open: BACnet-N2 Router, you can continue your SmartStruxure installation process as you would for any BACnet device. Note that there will be no points published under the S4 Open: BACnet-N2 Router itself but you will be able to confirm the Operational Status of the system from SmartStruxure. The Schneider Electric support organization will supply pre-sales engineering support and first-level technical support for the Metasys® N2 to SBO integration solution. The S4 Group will be available to provide 2nd level support to these integration projects.  

Issue How can a BACnet b4920 be reset back to its factory default IP address? Product Line Andover Continuum Environment BACnet b4920 Cause There is no Reset IP switch on the b4920 Resolution There are 2 ways of accomplishing this.   Method One - The first method resets the controller to factory default address settings: IP Address: 169.254.1.1 Subnet Mask: 255.255.0.0 Gateway: 0.0.0.0 Webserver Port: 80 Web User Name: acc Web User pwd: acc EnergyNet ID: 1 BacNetMstpNetId: 2764 BacNetUDPNetId: 2765 During controller startup, there is a 2 minute window in which the controller will be restored to factory defaults based on the following: Seconds since startup is < 120 A Ping packet is received by the controller with a matching Ethernet address but unmatched IP address. Ping payload size of 255 bytes. Prior to running the procedure, the controller must be on the same network as the PC that that is used to issue commands.  The engineer will need to have on hand (1) IP address that is both valid and NOT in use on the network that the PC and Controller are connected to.   Get the Controller's MAC Address Each controller has a 6 byte hardware address, also known as the MAC address or Ethernet address. The address is represented in HEX. The first three bytes of the MAC address are constant and represent Andover Controls vendor ID : 00-40-11 The last 3 bytes of the MAC address are derived from your controller’s serial number. The controller’s serial number is printed on the board and is represented as an Integer value. You must convert this value to HEX in order to obtain the last 3 bytes of your controllers MAC address. Ex. Integer Serial Number: 1033394 Converted to Hex: FC4B2 Controller’s MAC: 00-40-11-0F-C4-B2   Create a batch file Create a batch file named Acc.bat with the following content: arp -s %1 %2 ping -l %3 %1 arp -d %1   Restart the b4920 Controller Within 2 Minutes of restarting, run the batch file with the 3 arguments: Acc.bat IP_Address 00-40-11-XX-XX-XX 255 Where IP_Address = valid IP on the network Where XX-XX-XX = last 3 bytes of controller’s MAC Where 255 = Ping Payload size   After Issuing the command, the controller should restart, and the factory default address settings are restored.    Method Two - Capture the Controllers Currently Configured IP Address This second method is easier to do and is currently recommended because of its ease. Download and install a network sniffing application, such as Wireshark which can be downloaded from their website here. Connect a Cross over Ethernet cable between the b4920 and a PC running the network sniffing application. Start up the network sniffing application and then reset the b4920 by hitting the reset button on the controller. On start up, the controller will send out the IP address (Gratuitous ARP Packet) which it currently has assigned to it.  Once this IP address is captured with Wireshark etc the IP of the Workstation can then be changed to allow connection to the controller's web configuration page to change its IP address as required.  

Issue What is the difference between the XIF and NXE files in any LON controller? Environment LNS LON Controllers NL220 LonMaker Cause There are different files related to a LON device. The XIF and NXE files have completely different purposes. Resolution The XIF is a text-based file that defines the device’s network image to a network management tool (e.g. Niagara, LonMaker, etc.). The XIF along with files termed device resource files (DRFs) are used by the management tools to work with the LON device. Device resource files provide definitions especially when the manufacturer has not used standard SNVT types. When requesting a shadow object from Tridium, the XIF file must be provided as a minimum. If the manufacturer has defined their own variable types, the associated set of device resource files must also be provided. The only other alternative would be to use a dynamic device and hope that the device’s manufacturer implemented the files within the device correctly. When a dynamic device is commissioned, Niagara will upload the XIF from the device and attempt to create an object from the file’s definitions. The NXE is an abbreviation for (Neuron Executable file). Some devices allow the user to download an NXE or new application image file that changes the operation and / or network interface of the target device. New or different application firmware can be downloaded to the Neuron. This is the way some manufacturers upgrade their devices and / or the network interface portion of the device. If the LON device can support an NXE, this would have to be provided by the device’s manufacturer.

Issue How to upgrade the bin files and SAV files in controllers Product Line TAC INET Environment I/NET Seven 2.xx running in a Windows Environment. Cause The bin files for the controllers are not all current with the version of I/NET being used. The SAV files backup process and what gets overwritten. Resolution To upgrade the bin files in the controllers: Attach to the controller by selecting from the pull down menu in I/NET, Connect and drill down past your link NPR to the controller Select Edit/Controller/Station Save – this backs up the current programming on the controller and overwrites your .sav file Select Edit/Host Computer/Software Restore and put a check in the box for Software and select the button for Download –this pushes the latest bin file to the controller. If you select the Database box in the previous step, it will push the database to the controller as well. If you have SCU or DCU controllers, select the SCU/DCU button at the bottom of the window from step 3 and follow the same procedure. Note: BIN files are stored in the C:\INET Seven Data\Data folder   To upgrade the SAV files in the controllers: Attach to the controller by selecting from the pull down menu in I/NET, Connect and drill down past your link NPR to the controller Select Edit/Controller/Station Save – this backs up the current programming on the controller sav files are located on the C:\Inet Seven Data\SAV folder. To make a backup, simply copy this folder to another location Step 2(two) overwrites the current SAV file in the c:\INet Seven Data\SAV location To restore the current SAV file to the controller, select Edit/Controller/Station Restore and overwrite the database in the controller   KEY POINT: bin files are the software for the controller/device .sav files are the database

Issue Double clicking a .tgmlcomponentarchive file should automatically add the Component Archive to the Editor's component libraries. Sometimes it does not work and instead shows the following windows: TAC Vista Server Please wait while Windows configures TAC Vista Server Gathering required information... TAC Vista Server The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'TAC Vista Server.msi' in the box below. TAC Vista Server Error 1706.No valid source could be found for product TAC Vista Server. The Windows Installer cannot continue. Product Line TAC Vista Environment TGML Graphics Editor Cause There are five libraries that are included by default with every installation of the editor. They are: TAC Vista Symbols (EN) ISO Symbols DIN Symbols (EN) My Components Basic Controls If any of these libraries are removed by navigating to C:\Documents and Settings\All Users\Application Data\TAC Graphics Editor\Components and deleting the folder, attempts to add new libraries will fail. Resolution Navigate to the Buildings Business Extranet Go to Products > TAC Vista > Vista Software Click on the correct version of TAC Vista in the left-hand column. Choose Downloads Download the TAC Graphic Editor 1.1.X. Double click to install The directories are restored. Do not delete them.

Issue Encountered the error 'The Bcpv3 service is not installed under Config/Services' while trying to add a discovered BACnet device to the station database Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server / Workbench Cause The default view of the BacnetNetwork is now the 'Bcp Bacnet Device Manager' instead of the standard I/A Series G3 'Bacnet Device Manager'. This happens when the Distech Controls EC-NET-AX Support Package  v3.0.2.8 (I/A Series G3 support files for Proview) is installed on the computer running the station. Refer to BCP Device Manager showing up with the BACnet Device Manager. The Bcp Bacnet Device Manager is used to discover and add Distech devices. Using it to discover and add I/A Series BACnet controllers will result in the 'The Bcpv3 service is not installed under Config/Services' error. Third party non Distech devices may also exhibit the same symptoms. Resolution Discover and add BACnet devices using the 'Bacnet Device Manager' instead of the 'Bcp Bacnet Device Manager'. The 'Bacnet Device Manager' is now the 2nd view of the BacnetNetwork (right-click on the BacnetNetwork and go to 'Views' > ' Bacnet Device Manager').

Issue Need to change from the Small Number Format (Card Number) to the Large Number Format (Facility Code + Card Number). Requirement for Security Expert Transitions with I/NET Hardware.   Badging card on SCU1284 Reader using Security Expert, the reader event displays "Format error RD xx Port x Error Number of Bits" From Security Expert Client Events Product Line TAC INET, EcoStruxure Security Expert Environment I/NET Seven Security Expert Transitions Cause The I/NET system is limited to a maximum number of access cards, 32,000 per Tenant.  If a larger number is required, then I/NET must be configured to use large card numbers.  The Large card number format described in the Resolution MUST be completed before transitioning from I/NET to Security Expert and utilizing the I/NET SCU hardware as detailed in the Transition Guide Security Expert - INet Access Control to Security Expert - Reference Guide. Resolution To convert I/NET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this, use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Wiegand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can determine the Decimal number of the first card in the system (e.g., Card #970 Facility code 199) is the Decimal number 13042634, using a 26-bit Wiegand Excel spreadsheet.  This number will become the Source number in the Key/Card Translation table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the I/NET Seven Access Control editor.  This table will be removed after running the provided SQL Script.  The Key/Card Translation must contain: Source - Decimal number calculated in Step 3 above (13042634) Target - First Individual number shown in the Tenant (970) Count - Number of Individuals as shown in the Tenant (10000) Tenant - Tenant number this translation refers to (1) If there are multiple Tenants, then this process MUST be repeated for each Tenant Tenant Editor and Key/Card Translation Editor Shut down I/NET completely and run the attached SQL Script. Then once the script runs then, restart I/NET and look in the Individual Parameters editor, as shown below. Start I/NET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify a Hex number and the decimal number matching that from the Excel spreadsheet (Step 3) is seen in the Individual Editor Card section. NOTE: There may be multiple card entries here; the Last entry shown is that entered by the SQL Script.  It will depend on whether an existing Card entry was entered for the Individuals before running the SQL Script.  To have large numbers working on a site DipSw #7 has to be turned ON for the 7910/7920 DPUs. For the SCU1284 in the door editor, at the top center of that editor, there is a check box, "Card Translation," which has to be enabled for large numbers to work in the SCUs. An SLI “SAV” should then be done because that is where the Card numbers and Door settings are stored. Then perform an SLI restore. Followed by a DPU restore to all of the door controllers. NOTE: Steps 6d. and 6e. are NOT required when performing the transition to Security Expert as this information will be performed by the SP-C.   

Issue Automation Server CPU usage goes between 80-100% even with few programs, trends or alarms. Product Line EcoStruxure Building Operation Environment AS Automation Server Cause Cause 1: BACnet into AS uses a lot of resources Cause 2: The AS has bindings from a point to a variety of places Also check out the AS CPU and Memory Loading Quick-Help video on the Exchange. Resolution Example Resolutions in order: The issue described is Functions as Design in StruxureWare Building Operation. The AS results with high CPU percentage with just one point from BACnet interface loaded; however, it had no effect on AS performance. Check the propagation of values. An example would be a Space Temperature which is required by the field bus, the BACnet interface, LON interface, etc. Make sure to properly disseminate this value so to avoid overloading the CPU.

Issue How to subscribe to a topic in Azure IoT hub via MQTT protocol. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need to configure EBO MQTT interface and Azure IoT Hub, so EBO can subscribe to MQTT messages from Azure MQTT IOT Hub. Resolution The following video will illustrate how to: Create IoT interface and Azure MQTT client in EBO Configure the MQTT connection Create and configure MQTT data values Create and configure a data group Configure the subscription parameters Test the connection Things you need: EBO 2022 or later with valid MQTT license or demo license (Enterprise Server, AS-P or AS-B) valid Azure Subscription with possibility to use free account during testing. For each Azure subscription one IoT hub in the free tier can be created, refer to IoT Hub | Microsoft Azure Visual studio code to be used to test the connection between EBO and Azure IoT hub, can be download from: Visual Studio Code

Issue When trying to commission a controller into a LonWorks network in SmartStruxure you get a DST error. Product Line EcoStruxure Building Operation Environment WorkStation LonWorks Interface Cause The DST error occurs during the commissioning of the controller when the DST settings are attempted to be downloaded. Resolution TAC Xenta 280 and 300 series Controllers If the DST error occurs when commissioning a Xenta 280 or 300 series controller then check the label on the side of the controller. If there is no /N/P after the model number then it is not a network presentation controller and can not be commissioned in SmartStruxure. For more information see Xenta 280/300 without /N/P designation cannot communicate in a Network.

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 When trying to log on to an ES or AS using HTTPS, you get "No connection to server" or it takes a long time. Using HTTP it works fine. Version 1.6.0 and below you get "No connection to server" Version 1.6.1 and above you get in but it takes an extra 25 seconds compared to normal Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Workstation Cause The most common reason for this is that the port used for HTTPS is changed in the Software Administrator, and not added in Workstation when logging on. For a solution to that, please check Workstation Log on failure due to unidentified port. A more rare reason for this has been identified on sites with strict network policies or no connection to the internet. The reason this is happening is because an application using SSL or TLS (e.g. OpenSSL) is regularly checking for certificate revocation. That can normally only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang or fail to use SSL. For a deep explanation of certificate revocation check and the base of this article, read Citrix' article: Slow Web Interface\MMC console? CRL explained. The issue can be confirmed using Fiddler. Here is an example on how to identify the issue.: Another way to check it, is to enter the URL used to retrieve the list on the PC having the issue: http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab?baa88d4bbbfc38e4 When trying to access that URL from a PC having this issue, you should get "HTTP Error 502 Bad gateway". Resolution Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl Copy the two files to the PC having the issue Open a command prompt and navigate to the folder where the files are located Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

Issue What is Domain Name Service (DNS)? Product Line Andover Continuum,EcoStruxure Access Expert,EcoStruxure Building Expert,EcoStruxure Building Operation,EcoStruxure Security Expert,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment TCP/IP Networks Cause DNS is a distributed hierarchical system for resolving host names into IP address. Under DNS, there is no central database with all of the Internet host information. The information is distributed among thousands of name servers organized into a hierarchy similar to the UNIX file system. DNS has a root domain at the top of the domain hierarchy that is served by a group of name servers called the root servers. Source: TCP/IP Network Administration by Craig Hunt, O’Reilly & Associates, Inc. Resolution Short for Domain Name System (or Service or Server), an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they're easier to remember. The Internet however, is really based on IP addresses. Every time you use a domain name, therefore, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.example.com might translate to 198.105.232.4. The DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.  

Issue Warning - Platform running low on RAM disk space (Niagara G3 Release 3.2.5 and higher) Environment I/A Series G3 (typically embedded ENC/JACE platforms) Cause Low disk warning for history RAM disk A station fault will be generated if the free disk space on the history / alarm RAM disk falls below the minimum percentage specified on the PlatformServices property sheet. Resolution During station startup,  /niagara/bin/ramdisk.sh is invoked to create the RAM disk partition.   The RAM disk is named /aram0 and symbolic links are created from /alarm -> /aram0/alarm /history -> /aram0/history.  After the RAM disk is created it is populated with the contents of the alarm.zip and history.zip files.  During a station save or shutdown, the alarm and history files on the RAM disk are zipped and stored under the station directory in alarm/alarm.zip and history/history.zip.  If this fault occurs, users should take one or more of the following actions to prevent history/alarm data from being lost: Reduce number of histories that you are collecting Reduce number of records in each history Increase history RAM disk system (requires reboot). Action 3, above, will reduce the available system memory and should only be taken if there is sufficient free system memory.  Rather than writing history and alarm records directly to persistent storage, a Niagara G3 station stores history and alarm records in a RAM disk. This approach reduces the number and frequency of writes to flash.  Be careful not to increase too much otherwise you risk consuming all the available JACE free RAM causing the niagarad to crash.  Review the free system memory and make sure to leave a buffer of at least 1 MB of free RAM.  The RAM disk size is stored in /niagara/lib/platform.bog and can be adjusted using Services -> Platform Services. After reducing the number of histories, etc. the RAM disk will still indicate a low warning message until the unused histories are removed from the history storage.  Delete the unused histories using the Database Maintenance view on the history component view within the station.

Issue Users are getting two possible errors when trying to open WebReports page Error #1 - "The Web Site URL for Reports is not configured. Please contact the administrator" Error #2 -  "The webpage cannot be found" can also be generated. Product Line EcoStruxure Building Operation Environment Web Reports Cause These Errors can occur when the link to the Reports Server is not correct.  This is usually caused by having the Enterprise Server and Report Server on the same PC It should be noted that having both the Enterprise and Report Server's on the same PC is not recommended.   The reason the Workstation can not access the Web site / Web service URL's is because the Report Manager points to the "Localhost".  When you try to use a Workstation that is not local to the Report Server it can not locate this URL, hence the error.   This issue is not seen if when installing the Report Server on a different machine to the Enterprise Server as designed. Resolution Even though the Enterprise Server is local to the Report Server if access required by any other Workstation or WebStation you must enter the IP or PC Name of the Report Server within the Report Manager's Web site URL.  In this instance changing only the Web site URL will rectify the problem but it is recommended to change both the Web site and Web Service URL settings. This will allow any remote Workstation / Browser to find the Report Server. In workstation, Browse, to the System folder Click on System>Report Manager Set the Web site URL to http://localhost/SchneiderElectric/WebReports/Login.aspx Set the Web Service URL to http://localhost/SchneiderElectric/WebReportsService If the Enterprise Server resides on a different PC than the Reports Server, change "localhost" to the Report Server computer name or IP address After making this change WebReports should display correctly:

Issue What is the wiring for the RS-232 A, RS-232 B, RS-485 A, RS-485 C, and 10Base-T ports on a Xenta Server? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 BACnet/IP BACnet MS/TP M-Bus C-Bus Lon Modbus Cause The wiring and pin outs for the Xenta Server hardware is detailed in chapter 2.1.2 of the TAC Xenta 500/700/911/913 Product Manual . Resolution The ports and wiring is unique for each port. RS-232 A port For serial communication it is typical to only connect the RX, TX, and Ground pins. Pin 3 4 5 Serial Cable RX TX Ground  RS 232 B port   10 Base-T port (Web connection) Note: The Xenta 913 also supports BACnet/IP and Modbus TCP/IP on this port. RS 485 A port (Modbus) Note: The Xenta 913 also supports BACnet MS/TP on this port. If two wire communication is being used then only use pins 5 and 6. Pin 5 6   + - If four wire communication is being used then all four pins will be used. Pin 5 6 7 8   TX + TX - RX + RX - RS485 C port (I/NET) This port is used for I/NET communication. Pin 19 20   + -

Issue Receive the following errors when trying to restore a SQL database: ERROR MESSAGE #1 Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.1600. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #2 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #3 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 661. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #4 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #5 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 655. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #6 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. Product Line Other, TAC INET, TAC Vista Environment SQL Server 2008, SQL Server 2005 and SQL Server 2000 Enterprise, Standard, Express, MSDE Cause You cannot restore a backup created with a newer version of SQL Server on an instance running an older version of SQL Server. Unfortunately, the error messages that are displayed may not always tell you that it is a versioning problem. Here are various combinations of SQL versions and there associated error messages: SQL Server 2008 R2 to SQL Server 2008 Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.1600. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 R2 to SQL Server 2005 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 R2 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 661. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 to SQL Server 2005 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 655. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2005 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. Resolution Possibly the quickest and simplest solution may be to uninstall any software including SQL currently installed, then re-install any software along with the correct version of SQL. If this is not an option, then Microsoft does provide information on how to upgrade different versions of SQL. Links are provided below: How to: Upgrade to SQL Server 2005 (Setup) How to: Upgrade to SQL Server 2008 (Setup) Also check Software and Firmware compatibility matrix for older versions of the traditional product lines for supported Operating Systems and SQL versions.

Issue How to setup a Pelco DVR in Security Expert. Product Line Pelco, EcoStruxure Security Expert Environment Security Expert Pelco DVR Endura DVR Cause Unsure what the Service Port and DVR port settings are and how to configure the rest of the settings for a DVR object in Security Expert. Resolution When configuring your DVR in Security Expert you use the Custom DVR Type, all the preset DVR types are for legacy systems. In earlier builds of the software Video Services were integrated directly, these are now being run as separate services. When you install the Video Service you specify a Service Port – it can be any unused port whatsoever, the default is usually fine – take note of this port number. Once installed you need to manually start the service. In Security Expert you set the DVR Type to "Custom", set the IP Address, and then the Service Port same as above – the DVR Port is configured from the DVR software/Web interface, usually their documentation will cover this. Then just add the Username and Password used to login to the DVR. (See image below which shows the relevant settings highlighted in red.) If you make any changes to the DVR settings you will need to restart the Video Service and the Security Expert DVR B service for them to take effect. In Security Expert, add DVR objects by going to Monitoring > Setup > DVRS IP Address: IP of the DVR. DVR Port: Defined in the DVR software/Web interface. The default for the more recent Pelco DVRs is 60001, and the older models is 18772 (consult your specific DVR documentation for details). Service Port: Port configured during installation of Pelco Video Service. (This field appears when DVR Type is changed to Custom) DVR Type: Select Custom. Username / Password: Credentials for the DVR.   Also refer to Support for Pelco VideoXpert Integration and Pelco's partners website for up to date information on Pelco integrations with Security Expert.

Issue What Port numbers are used by the Sigma system? Product Line Satchwell Sigma Environment Ethernet communications Ports Port TCP UDP Cause Known port numbers should be set as exemptions in the system firewall. Resolution Sigma server to Sigma NNN / controller communications - User Datagram Protocol (UDP) uses port 49152. Sigma server to Sigma client communications - Transmission Control Protocol (TCP) uses ports 3614 and 8080. Sigma Web client communications - Transmission Control Protocol (TCP) uses ports 80 and 8080, but also uses port 3614.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When upgrading EcoStruxure Building Operation to version 2.0 or newer, the existing Power Manager software should also be upgraded to EcoStruxure Energy Expert to maintain compatibility Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Power Monitoring Expert (PME) Power Manager Cause The proper procedure is required when upgrading from older versions of Power Manager to the latest Energy Expert version. Guidance and best practices are needed for upgrading a PME server from PME 7.2 to PME 9.0. Resolution A Power Manager 1.0 site should be taken to 1.1 first, then upgraded to Energy Expert 2.0 Below are the recommendations for a side-by-side upgrade from PME 7.2 to PME 9.0: On the old server: Run the PME_8.2.iso file to do an in-place upgrade from PME 7.2.3 to PME 8.2 After completing that upgrade, the system will default to using a PME 8.2 trial license Install and run the PME 8.2 CM 2.1.0 Tool which will perform necessary actions for the side-by-side upgrade; we will use it to create a .zip file containing configuration components such as reports, dashboards, diagrams, users, devices, etc. Transfer this .zip file from the CM Tool to the new server On the new server: Run the PME_8.2.iso file to install PME 8.2 (this can be done while the above steps are performed on the old server) After transferring the .zip file from the old server, install and run the PME 8.2 CM 2.1.0 Tool on the new server and have it load the archived data from the .zip file into the program, and then write it to the system (essentially performing a PME 8.2 server to server migration) After that finishes, we can run the PME_9.0.iso file to upgrade from PME 8.2 to PME 9.0 After PME 9.0 is installed, we can activate the PME 9.0 license(s) in the Floating License Manager using the activation ID(s) that were already acquired, then remove the PME 9.0 trial license using License Manager (different from Floating License Manager) Running into issues with the install? Receiving error messages related to PME? Check out the Technical FAQ for a solution to your problem.  Links to relevant documentation and files: Where can I find documentation for Power Monitoring Expert 8.2 (PME 8.2)? Where can I download Power Monitoring Expert 8.2 installation files? Where can I find documentation for Power Monitoring Expert 9.0 (PME 9.0)? Where can I download Power Monitoring Expert 9 installation file? PME 8.2 CM Tool Exchange Community post  PME 9.0 CM Tool Exchange Community link