Building Automation Knowledge Base

Issue If the Xenta Server IP address is unknown or lost, how can the user retrieve or reset the IP address? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Once the Xenta Server IP address is lost, the user has to use a serial connection cable to connect the Xenta Server to the HyperTerminal in order to retrieve the IP address. The serial cable is a RS-232 to RJ10 cable which can be purchase from Schneider Electric order entry (Part number: 00730920). For some reason, if the cable need to be home made, please follow the steps below to connect correct pins. Note: some third party IP search/scan software can be used to search all IP addresses in a range. User can also use this type of software to retrieve Xenta Server’s IP addresses. Resolution Xenta Server serial cable guide: Connect RJ10 pin 1 to RS232 pin 2. Connect RJ10 pin 2 to RS232 pin 3. Connect RJ10 pin 4 to RS232 pin 5. Connect RS232 pin 1, 6, 4 together. Refer to IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for how to set up HyperTerminal in order to retrieve/setup Xenta Server IP address.

Issue After installed I/NET, DBCreate will never pop up to create a new database, which will cause I/NET never launches. Backup and Restore button are greyed out when opening DBCreate, which also will cause I/NET fails to launch. When restoring database, an error will show up, saying that version is incompatible with this server. When restoring the database, an access deny error will show up. Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause SQL default instance is not created correctly. SQL2005 BCM is not installed correctly if SQL2008 is used, or there is a database version mismatch for I/NET. This is usually caused by restoring new SQL database to old version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Windows permissions are not enough to do the restoring Functionality of the host pc and the database seems to be inconsistent. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution If you are using I/NET 2.4x, and already have a named SQL instance on the computer (for example, TAC Vista 5.1.7 or higher has been installed, with a named instance installed called TACVista), I/NET may fail to recognize it, while also fail to create a default instance. Similar kind of warning will pop up during the I/NET installation: Under this condition, use your current SQL server installer or browse to /SQLExpress folder of I/NET installation CD, to manually create a new default instance. You can refer to the guide within the /SQLExpress folder about how to create it. As long as the default instance is created, DBCreate will pop up immediately and a new database can be created. If 64 bit Operation System is used, refer to Installing I/NET Seven on a 64-bit operating system for the detailed guide. Also refer to Installation guidelines for installing I/NET and Vista on the same PC for more details about installing I/NET and TAC Vista on one computer. If SQL 2008 or SQL 2008 R2 is used, be sure to follow the correct steps about how to install them: I/NET Seven with SQL 2008: I/NET Seven with SQL 2008 Installing I/NET Seven on a 64-bit operating system: Installing I/NET Seven 2.42 or higher on a 64-bit operating system If SQL 2008 is installed correctly, please refer to Data Base maintenance before performing an upgradeto perform a forced upgrade for the database. Refer to Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate: Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate Refer to DBCreate backup access denied using Windows Server 2008 R2 Standard and Microsoft SQL 2008 R2: DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2. Refer to Unable to Create a backup in DBCreate: Unable to Create a backup in DBCreate. Refer to Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached: Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached.

Issue When logging into Xenta server using Internet Explorer 8 a certificate error is displayed as displayed below: When logging into the web server of a Xenta controller using Internet Explorer 8 an error message is shown stating that there is a problem with the website's security certificate. The error reads: There is a problem with this website's security certificate. The security certificate presented by this website was issued for a different website's address. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. We recommend that you close this webpage and do not continue to this website. Click here to close this webpage. Continue to this website (not recommended). More information How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Internet Explorer 8 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Internet Explorer 😎 cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution Click "Continue to Website" to continue to the screen shown below. Click on "Certificate Error" which is found on the right side of the address bar at the top. A dialog similar to the one below will open. Click "View certificates". The certificate dialog will appear. Click "Install Certificate." The Certificate Import Wizard will open. Click Next. Allow Windows to automatically select where to store the certificate. Proceed to Finish the Certificate Import Wizard. A notification appears indicating that the certificate was imported successfully. Restart Internet Explorer for the change to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Internet Explorer is uninstalled then reinstalled. The alternative is that a certificate issued by a Certificate Authority (CA) may be purchased. These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. See "This Connection is Untrusted" certificate error when logging in to a Xenta Server using Firefox for information on installing certificates into Firefox. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate.

Issue OPC Server with third party and alternatives Product Line Andover Continuum, TAC INET Environment System requiring third party connectivity Cause OPC Server to communicate between hardware and the iBMS (intelligent Building Management System). Resolution The OPC server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. OPC Client Servers are used to communicate between BACnet IP interfaces and iBMS (intelligent Building Management System) programs such as TAC I/NET or Andover Continuum. There is also no Continuum OPC Client software to use for a direct OPC link. The best way to integrate from 3rd party EIB or OPC protocols is using BACnet IP on Continuum; there are third party interfaces and gateways that will convert to BACnet/IP and others that go from OPC Client/ Server to BACnet/IP. I/NET OPC For I/NET a great solution is to install a Xenta 913 controller which gives the capability to go with Modbus or BACnet/IP to third party solutions. The I/NET to Xenta 913 allows communication with Continuum BCX, StruxureWare AS-B, and other 3rd Party solutions. Continuum OPC Standard 3rd party gateways are established to communicate between the protocols such as BACnet and Modbus. Andover Continuum has an OPC Server available here. The hardware requirements are Windows NT 4.0 or Win2K. If wanting to run on XP or newer operating systems, please be aware that no testing has not been done with these OS. For more info on the OPC and XDriver, please see OPC Server Integration. Only one instance of the OPC server on a computer. Each system would need a separate PC with license key to connect to the individual systems and host controllers. The Andover Controls OPC server must be running a separate 3rd Party OPC client computer and cannot be on the same computer as CyberStation. From there it is configured to retrieve point values from a the suggested dedicated Infinity (CX) Controller. It is suggested to install a OPC gateway Infinity Controller since this controller will constantly be busy with OPC traffic. Therefore it is the separate third party vendor computer which requires the ACC OPC Server security key, not Cyberstation security key. Both USB and parallel port keys are available. If no choice is available for OS, one alternative is to check on 3rd party OPC servers like Kepware and Matrikon. Note: For Continuum, determine which one of your controllers will become the “Primary Controller” The Server requires that you designate one external Andover Controls Infinity or Continuum controller located on the same network as its “Primary Controller.” This controller must have had the network taught to it prior to selection. (This is done through the “Teach” function in the workstation.) The Server gets its information about the network through this controller. This suggested single controller is designated as the interface through which all point access is obtained. Controller Type Select the type of network where the controller is located. For a NetController, b4920, CX9702 or upgraded Infinity controllers that can be connected to a Continuum network you would select “Continuum”. For older Infinity controllers, select Infinity. Works with any IP level controller. There is no limit on the quantity, but rather it depends on how you tune.

Issue Can the current revision of I/NET Seven Software CD key be used to install older revisions of I/NET Seven Software.  Site has a revision of I/NET installed older than the current release version and additional Site or Seat License is required for the site. Upgrade or revision changes. Product Line TAC INET Environment TAC I/NET Seven Cause Additional License Seats requested by site\customer. Resolution Only current revisions of I/NET seats are available for purchase. Current revision of I/NET Seven Software CD keys are backward compatible within the same major revision release (i.e. 2.40 CD keys are compatible with any 2.XX revision.) Every computer which has I/NET installed must have a I/NET CD regardless if the site is HVAC, Security or both. At a site which has a StandAlone with I/NET, it must have a Site License. If I make that a FileMaster and add one Equalized Client, a SEAT license must be purchased for that Equalized Client. If I add another Equalized Client(s) or perhaps Remote Client(s) additional SEAT licenses must be purchased for those.  The license key is registered to the site, see I/NET CD Key and software revision for more information. When looked up, it reveals how many licenses (Site or Seat) have been purchased for that site. After the initial purchase, any I/NET PC upgrade uses Part Number INETSEVEN24U If upgrading Site computer use Part Number INETSEVEN24U If upgrading File Master use Part Number INETSEVEN24U If upgrading Equalized Client computer use Part Number INETSEVEN24U If upgrading Remote Client computer use Part Number INETSEVEN24U If there is a separate database for a site, let's say they open a new building with INET install with a different db, then an additional Site license is required which would be a new license key. For the latest version information check Software and Firmware compatibility matrix for older versions of the traditional product lines   Upgrade orders can be placed using the following part number: P/N: INETSEVEN24U TAC I/NET Seven Software CD TAC I/NET Seven Getting Started - TCON298 Software License Agreements TAC I/NET Seven Software Box New software orders can be placed using the following part numbers: SEVENMAXR - HVAC & Security site license, w/ CD SEVENHVACR - HVAC only site license, w/ CD SEVENSECR - Security only site license, w/ CD SEVENADDHVAC - Add HVAC, site license only SEVENADDSEC - Add Security, site license only SEVENSEATR - HVAC & Security license for 1 workstation, w/ CD, site license required SEVENSEAT3 - HVAC & Security license for 3 workstations, w/ 3 CDs, site license required SEVENSEAT5 - HVAC & Security license for 5 workstations, w/ 5 CDs, site license required SEVENMANUAL - Manual set, 3 volumes. No CD   Example: The site is currently at I/NET Seven Software Revision 2.14 and requires the purchase of additional seat licenses. The newly purchased seat licenses are the current I/NET Seven Software Revision 2.47. Two options available: 1) Use the newly purchased I/NET Seven Software revision 2.47 seat licenses to install the I/NET Seven Software revision 2.14. Upgrade the sites original licenses from I/NET Seven Software revision 2.14 to 2.47 Older revision I/NET Seven Software can be obtained from either the original CD Media or can be downloaded from EcoBuilding Download Center. Example 2: A site has an existing Host File Master, and Five(5) SEAT licenses(Equalized Client or Remote Client). To upgrade, they would purchase six(6) INETSEVEN24U part numbers which is for each of those workstations. To add an additional I/NET workstation, they would purchase a SEVENSEAT, which is the additional SEAT license.  

Issue Replacement I/NET Controller NICAD Battery info., I/Net Batteries Product Line TAC INET Environment All I/NET controllers Cause Controller battery has failed, because the battery on the controller is over 5 years old   Resolution The 3 pin version Battery is used for the NPR2000 and the DPU48K (MIP Board) -- part number 3/V80H-SLF (Note this battery has to be order from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The 7910, 7920, 7930 7780 & 7940 use the 2 pin version -- part number 3/V80H-LPC (Note this battery has to be ordered from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The battery used on the 7700, 7716, 7718, 7728, 7720, 7928, 7793, 7798B, & 7798C (and like controllers) is the Dallas/INET part number 801288-07. This also can be ordered from the Rockford order entry using 01-2100-545 (Old CSI P/N 801288-07). This battery also has an outside Vendor source from Power-Sonic P/N - PCBM-3.6 Click here to view a PDF on this part. For battery testing process see How to test the NiCAD Battery on a Controller

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 Xenta Server reports it is in FAILSAFE mode without shorting out terminals 9 and 10. After connecting via HyperTerminal, restarting and trying to reset the IP address, the screen continues to scroll back to dsh/> Xenta Server has gone offline and can not connect directly to it using Ethernet. The Run light is flashing Green on first start up but then reverts to red and the LON light also flashes red. During boot up it pauses and reports an error (via HyperTerminal) in loading the RAM disk.  IP Address is set to 172.22.1.5 and can not change it.  Not able to load any firmware into the device – error received. "Error: Could not create remote directory." Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 527, 511, 555 Xenta Server 701, 721, 731 Cause Unknown corruption of the Xenta Server hard drive / flash drive, possibly due to electrical noise. Resolution To attempt to recover this device, try to format the device’s flash drive. To achieve this you can follow these steps using HyperTerminal or an equivalent application: (For further assistance with connecting to Xenta Servers and HyperTerminal refer to Connecting a serial cable to a Xenta 5/7/9xx controller).   Login and type the command FORMAT.  (May require device to be placed physically into the fail-safe mode by shorting terminals 9 and 10). The format command can take up to 3 minutes to complete but you should see the confirmation through HyperTerminal while this is occurring. If you have placed the device into Fail-safe mode, remove the link on terminal 9 & 10. Restart the device, by either cycling the power or typing the command RESTART through HyperTerminal. Set the IP address and IP settings (command SETIP). Install the latest firmware. You can download the latest firmware from The Exchange Extranet; ensure that you use the correct version since there various versions for the Xenta Servers. Run the firmware download to the device. During the download you may receive an error regarding "Failure to get the hardware version from the target device…", select OK Continue the installation The download will then occur, it will take some time and may appear that the software is not responding but this is normal. Be patient and if you don’t receive any errors then all should be ok. The device should now restart, after a 1-2 minute window the “RUN” LED should be a solid green. If after following these procedures, the device is still not responding as expected please send into Repairs via your normal repair process.

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 Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue Perform a complete 2.43 I/NET install on a clean workstation with integration with StruxureWare Building Operation 1.3.x or higher. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET 2.43 StruxureWare Building Operation 1.3 Cause Before starting the upgrade, please ensure the following: I/NET system installed is performing well Communications – reliable Alarms - Routing masks configured Application sequences - tuned Points - enabled and calibrated Devices - online Database - backed up If not, then these issues should be resolved before proceeding. SmartStruxure Solution will add functionality, but will not resolve existing performance issues. Verify architecture: All controllers, workstations, & the I/NET database can remain including: (for a complete list, see I/Net Controllers which are supported with StruxureWare Building Operation) All LAN Controllers All Sub-LAN Controllers HVAC and Security applications Replace all TAPS with dial-up connections with LAN connections: Xenta 527 Xenta 527-web NetPlusRouter 2000 (discontinued but supported) Verify I/NET system size is supported by the version of StruxureWare Building Operation to be installed Upgrade TAC I/NET software and firmware: I/NET Seven v2.43+ on a workstation v2.42 compatible controller firmware versions Note: All I/NET controllers will require this update For more information on version, compatibility see Compatible versions of I/NET and StruxureWare Building Operation software. Resolution Click here for a video summary of the integration process after all installations have been completed. Perform a complete I/NET install of build 23xx on a virgin machine Install I/NET build 23xx from CD Run "setup.exe" Enter the I/NET Subkey information Verify SQL database gets installed Run Dbcreate NOTE: If running I/NET Seven on 64-Bit Operation system, the path to the INET Seven folder is: C:\Program Files(x86)\INET Seven\ Make I/O Server runs as a Service Refer to the article Running INET Seven as a service on Windows Set I/O server to "Maintain" Set "Host" Mask" for your specified controllers --------->recommend reboot to ensure Inet7Iosrv is running as a service at this time<------- Ensure you have a current License file CD or provided by Order Entry Verify that you see the "StruxureWare_License_File.asr" (current name of file changes with each release of license file) Save the file to a folder on the workstation in License Tool Folder Perform an install of StruxureWare Building Operation License  Select build of interest ex 1.3.0.xx Locate and click the Licensing Tool folder Click on the StruxureWare.License.Administrator-1.3.0.xx.exe After the loading process completes, click “next” on the Welcome to the StruxureWare screen Click the “I agree” button at the License Agreement screen Uncheck the License Server component and Click the “Next” button at the Choose components screen Click “Install” at the License Server Configuration screen Once the install completes, click the “next” button Click “Finish” at the Completing the StruxureWare 1.3 screen Verify the License Administrator by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare License Administrator Verify License Administrator editor appears To load the License File select the “Licenses” tab Select the Add License drop down=>Add License from File Point to your License file and click “open” After License Load click the close button Verify the License file gets loaded and Status is Valid Click “Ok” Perform a complete install of Device Administrator Select Device Administrator.exe in build of interest On Welcome screen select Next Agree to End User License On Choose Components leave default and select Next After install select Next Finish the Device Administrator installation Perform a complete install of ES Select build of interest ex 1.3.0.xx Locate and click the WinES folder Click on the StruxureWare.Enterprise.Server-1.3.0.xx.exe After the loading process completes, click “next” on the Welcome to the StruxureWare screen Click the “I agree” button at the License Agreement screen Click the “Next” button at the Choose components screen Verify database location and Click the “Next” button at the Choose install Location for database Click the “Next” button at the Enterprise Server Configuration screen Click “Install” at the License Server Configuration screen Once install completes, click the “next” button Click “Finish” at the Completing the StruxureWare 1.3 screen Verify the Server is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Software Administrator Reboot PC to sync the services After reboot verify that the ES and I/O Server is running as a service. The ES is hardcoded when an I/NET interface is present; I/NET service is automatically started first. That is why when the system is restarted it always comes up in the correct order.   Perform a complete install of .Net Framework 4.0 "Microsoft .NET Framework 4 (Web Installer)"' Verify .net Framework 4.0 is not installed (look if listed in add/remove programs) Go to http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17851 Verify you are attempting to download "Microsoft .NET Framework 4 (Web Installer)" Verify download .exe is "dotNetFx40_Full_setup.exe" Click the "download" button Verify .net downloads successfully Perform a complete install of Workstation Select build of interest ex 1.3.0.xx Locate and click the NspClients folder Click on the StruxureWare.Workstation-1.3.0.xx.exe After the loading process completes, click “next” on the Welcome to the StruxureWare screen Click the “I agree” button at the License Agreement screen Click the “Next” button at the Choose components screen Verify Installation type and Click the “Next” button at the Workstation Installation Type Screen Click “Install” at the License Server Configuration screen Once the install completes, click the “next” button Click “Finish” at the Completing the StruxureWare 1.3 screen Verify the Workstation is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Workstation Verify "Building Operation workstation" screen appears Select either Windows or Other User, enter user name and password and select "log on" (for assistance, view Workstation Log on failure due to unidentified port) Select either the Administration or Engineering view Verify Workstation System tree screen appear Verify that Device Discovery + I/NET Devices shows all Links and controllers Select and Right-click on top of tree "Server 1" Object - example: "Server 1" within the System Tree Pane Click New => Interface Verify "Create Object" window appears Within the "name the object" select "I/NET Interface" Create a name - example: "I/NET Interface" Click "create Select Server 1 Select "Device Discovery" tab Click drop-down using the "Select device type" Select "I/NET devices" Verify Links and controllers appear in List view Verify that Drag and Drop and Upload (Get Configuration) works correctly Select Server 1 Select "Device Discovery" tab Click drop-down using the "Select device type" Select "Inet devices" Verify Links appear in list view Select desired Link and expand Link Verify DCU's appear within the Link Select the DCU within I/NET devices - example: "DCU 9551- DCU - 7728-x " Drag and drop the selected DCU into "I/NET Interface" Verify the DCU dragged successfully. Select the created DCU - example: "I/NET DCU (1)" within the System Tree Pane Click the "Properties" tab Go to the "Configuration" window within the "Properties" tab Verify the "Link Number"(LL) and 'Station Number"(SS) info Click the Actions => Upload" or right click=>Upload Select the "List View" tab Verify all of the Points objects for the DCU controller appears and is online. Verify that you can drag and drop and perform an Upload (Get Configuration) all point types and controllers Select Server 1 Select "Device Discovery" tab Click drop-down using the "Select device type" Select "Inet devices" Verify Links and controllers appear in list view Select desired Link/s and expand Link Verify controllers appear within the Link Select multiple controllers of different point types within I/NET devices Drag and drop the selected controllers into "I/NET Interface" Verify the controllers dragged successfully. Select "I/NET Interface" select the List view tab Select multiple controllers types within List view Click the Actions => Upload" or right click=>Upload Verify all of the Points objects for the DCU controller appears Perform an Update firmware (DCU Download) to a downloadable DCU type from StruxureWare Building Operation. Verify the Binary file for the selected DCU at the following location: C:\INET Seven Data\Data Copy the Binary file Rename the existing Binary file and make sure the file updates. Within StruxureWare, Right-click on the specified DCU Click the "Update firmware" Verify the Software Restore Editor appears. Locate the Link, Site and or station of the DCU Select the Software and Database options Verify software directory is C:\INET Seven Data\Data and Run in Dial Retry Mode is checked. Click "download" Verify the Software Restore Editor appears and starts the download. Verify the "Binary date" on the Software Restore editor matches the date of the updated Binary file. Verify the restore completes. Click Close. Validate that the Rev shown in the Summary Configuration view is the expected number. Perform a Backup (DCU Save) Verify that a current .SAV file exists for the DCU at the following location. C:\INET Seven Data\Sav Within StruxureWare, Right-click or select the specified DCU Click the "Backup" or Actions=> Backup Verify the status editor appear. Verify .SAV file date updates at the following location. C:\INET Seven Data\Sav Perform a Restore (DCU Restore) Verify that a current .SAV file exists for the DCU at the following location. C:\INET Seven Data\Sav Modify the .SAV file name to reflect as being old) Log into the Host Tool and locate your DCU Go to the point summary for the DCU and select "zoom" Delete 2 of the points Click yes to confirm Click close and save the DCU. Within StruxureWare, Verify the dirty flag appears in the DCU Select the DCU and Click the Actions => "Upload" or right click=>Upload Select the "List View" tab Verify the 2 Points objects are deleted from the DCU Go into C:\INET Seven Data\Sav and Modify the current .sav file name to reflect delete. Modify the former "old" .sav file name back to the original XXXX.sav Within NSP, Right-click on select the specified DCU Click the "Restore" Verify the Software Restore Editor appears and starts the download. Select "INET Interface" select the List view tab Verify the previously deleted points objects appear. Force a State change to a Point object using (StruxureWare) Make sure the screen is in split mode or split-screen.. (INET / StruxureWare) Using INET, Select your Discrete Alarm (DA) point type object from Controller Summary Make sure the Point value = off and Test is "on". Within StruxureWare, select the same Discrete Alarm (DA) point Right-click (Discrete Alarm (DA) point) =>properties Scroll down to Values Change the Value of the point to "on" by clicking the drop-down and selecting "1". (Value will vary upon Setup) Click ok Verify the state changes on the (Discrete Alarm (DA) point) object. Force a value change to a Point object using (StruxureWare) Make sure the screen is in split mode or split-screen.. (INET / StruxureWare) Using I/NET, Select your Analog Input (AI) point type object from Controller Summary Turn Test is "on" Within StruxureWare, select the same Analog Input (AI) point object Right-click Analog Input (AI) point type object =>properties Scroll down to Values Change the control value by entering a numeric value. Click ok Verify the value changes on the Analog Input (AI) point type object. Create a Global Point scenario between 2 points Setup a DLA configuration for 2 Discrete Output (DO) points Using I/NET, Go to DCU/Discrete Output (DO) point in Control Summary click "control" Verify the point control editor appear Make sure both Point values = off Go to StruxureWare, Locate the 2 Discrete Output (DO) points Change the view to Engineering. Locate and drag both Discrete Output (DO) points and drag them into the watch window Within INET, change the control state of the point to "on" by clicking the drop down and selecting "1". (Value will vary upon Setup) Verify both points change to the "on' status Within StruxureWare, change the control state of the point to "off" by clicking the drop down and selecting "0". (Value will vary upon Setup) Verify the that both point objects update and reflect the same state value in both StruxureWare and INET. StruxureWare Building Operation Commands Using I/NET, select Summary=> Controller Verify a "controller summary" window appears. select the first point type for the specified controller and select the "control" button Using StruxureWare, right click=>commands on the same point type as in I/NET Expand "Commands" Verify "manual," "Automatic," "Acknowledge," "Test On," "Test Off," "Point Control," "Alarm Configuration" appears per specific point types select "Point Control" Verify "point control" editor appears as in I/NET select "Download" Verify "value" = updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Manual" within the Commands (if applicable) Verify "manual = True" for property name Test within properties (Basic)... (note this is only if it was False previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. Create an Alarm Event (if applicable) Verify "UnAcknowledge = True" for property name Test within properties (Basic)... (note this is only if it was False previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Acknowledge" within the Commands Verify "UnAcknowledge = False" for property name Test within properties (Basic)... (note this is only if it was True previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Automatic" within the Commands Verify "Manual = False" for property name Test within properties (Basic).. (note this is only if it was True previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Test On" within the Commands Verify "Test = True" for property name Test within properties (Basic).. (note this is only if it was False previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Test Off" within the Commands Verify "Test = True" for property name Test within properties (Basic).. (note this is only if it was True previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. Select "Alarm Configuration" within the Commands (if applicable) Verify an Alarm Configuration editor appears containing Alarm/Messaging Complete steps 2-30 until all point types are verified. StruxureWare Building Operation EDITS Using INET, select Summary=> Controller Verify a "controller summary" window appears. select the first point type for the specified controller and select the "zoom" button Using StruxureWare, right click=>edit on the same point type as in I/NET Expand "Edits" Verify "Point Configuration", "Calculation", "Event", "Trend Configuration","Runtime", "Time Schedule", "Temperature Control", "Demand control", "Consumption", "Door", "Elevator","Alarm Inhibit","Unitary Control" appears per specific point types select "Point Configuration" Verify a Point Configuration editor appears containing the point info Within I/NET Verify that Point Configuration editor appears for the specified Point type Complete steps 4-9 until all point types are verified. StruxureWare Building Operation Point Extension Using I/NET, select Summary=> Controller => from the main menu. Verify Controller Summary page appears Select "Zoom" Within in StruxureWare, Select the DCU select the specified point (LL.SS.PP.BB xx) Click on the "properties" tab =>Extensions tab Verify correlating point extensions appear and are checked. Verify point extensions can not be updated in StruxureWare. Go into I/NET (Resident I/O) Locate the specified point (LL.SS.PP.BB xx) Verify that correlating point extensions in I/NET matches to the extensions in StruxureWare. Visit two extension editors (C, EV, RT, CN, AI, TS, TC, TR, or DC). Add or modify an entry Repeat for all Points types Verify that correlating point extensions in INET updates and matches to the extensions in StruxureWare. Force a value change to a Point object using the Point Control (HOST Tool) dialog (StruxureWare Building Operation) Make sure the screen is in split mode or split-screen.. (I/NET / StruxureWare) Using I/NET, Select your Analog Input (AI) point type object. click "control" Verify the point control editor appear containing the value. Within StruxureWare, Load/Configure DCU right click=>edits on the same point type as in I/NET Expand "Edits" select "Point Configuration" Verify a Point Configuration editor appears containing the point info Change the control value by entering a numeric value. Click the “Download” button Verify the value changes in (I/NET and StruxureWare) Force a State change to a Point object using the Point Control (HOST Tool) dialog (StruxureWare Building Operation) Make sure the screen is in split mode or split-screen.. (I/NET / StruxureWare) Using I/NET, Select your Discrete Alarm (DA) point type object. (video alarm) Make sure the Point value = off click "control" Verify the point control editor appear Within StruxureWare, select the same Discrete Alarm (DA) point Right-click (Discrete Alarm (DA) point) =>Commands=>point control Verify the point control editor appear Change the control state of the point to "on" by clicking the drop-down and selecting "1". (1 or 0 Values will vary according to setup) click ok Verify the state changes on the (Discrete Alarm (DA) point) object in both (I/NET / StruxureWare) StruxureWare Building Operation Time Schedule Update the ES Server to reflect your time zone by going to Tools=>Control Panel (Date and Time) Please see Time Synchronization of the ES and AS for more information.  Save your time zone Right click on Server1 => New=> Schedule Verify the Create Object editor appears Select "Digital Schedule" and click the "Create" button Verify the Digital Schedule object appears in the system tree Within "Digital Schedule" select "New schedule event" icon or Select the time period of choice Verify the "Schedule Event Properties" appear Create a schedule by selecting a Day of week and a Time and click the ok button.(Set the time to a future desired time) Save the schedule select "Digital Schedule" and right click=>"edit bindings" Manually Bind the Digital Schedule(Value) to Digital Point object(Control Value) Save and exit bindings. Switch your view to engineering view and drag your Digital Point object into the watch window. Verify the Digital Point object is set to "off" Take a look a the calendar and verify the time block is an "on" status Verify that when the start time is met, the Digital Point object updates to an "on" status I/NET Verify when the end time is met, the Digital Point object updates to an "off" status in I/NET. Create a Program Script in StruxureWare Building Operation (Digital) 1. Right-click on Server1 => New=> Program 2. Verify the Create Object editor appears 3. Select "Script Program" and click the "Create" button 4. Verify the Script Program object appears in the system tree 5. select "Script Program" and right click=>edit " 6. Verify the script editor opens up 7. Copy and paste the following script into the script program: Numeric Input pt1 Numeric Output DV1 if pt1 is True then turn on DV1 Else turn off DV1 Endif   Save the Script and minimize the script editor Verify no errors appear within the "check" box. Within the system tree, right-click on the "Script Program"=>edit bindings Manually Bind the DV1 Output to a Digital Point object (PVControl) Save the Script Program and exit binding. Switch your view to engineering view and drag your Digital Point object into the watch window. Verify the Digital Point object is set to "off" Select the Script Program and click on the "Input" tab Force the Numeric Input pt1 value to on or 1. Verify that your Digital Point object update to an on status. Verify that you can Convert an I/NET Graphic page using INET Conversion Tool (.gpg to .tgml) Within I/NET, Select "System=>New Graphic Page" Verify I/NET Seven Graphic Page appear Select "I/Net" from the main menu Select "Points" from the I/NET menu Choose a section of the page and left-click on the mouse. Verify the Point selection editor appears. Select a Point Object type and click OK Verify the Graphic appear Right-click on a graphic object and select properties Verify the "Point Object Drawing Styles Editor appear" Within the Editor locate Digital Point Style=> Icon plus value Within the Editor locate and fill in the applicable Options. ie……Display option Click Ok. Repeat steps 3 - 14 until all "……Point Style" on that Point object are used. Save the created graphic within I/NET, File=>Save As Verify the graphic file saves as .gpg file Within StruxureWare, Select "I/NET Interface and Actions=> "Convert graphics" Verify Export INET Graphics to StruxureWare Editor will appear Verify Source: c:\Program Files\INET Seven is populated Verify Look in a subfolder, Over-write existing files and Log conversion boxes are checked. Select the graphic page/s to be converted Verify Destination: c:\INET Seven Data is populated Click "Convert" button Verify the conversion completes Verify the graphic is converted from .gpg to .TGML format at the destination location. Verify that you can view the converted I/NET Graphic object in StruxureWare Building Operation Create a .sav file of the controller which you are converting. Within StruxureWare, Right-click Server 1=> New=> Folder Rename object as "INET Graphic" Verify the "INET Graphic" object appears in the system tree Right-click on "INET Graphic"=> Graphic Verify the Graphic "create object" editor appears. Click the "Next" button Verify the "Basic Settings" appears. Locate the converted files by clicking on the [...] symbol at the end file line. Point to the Graphic *.tgml to be opened Select the specified cell "Graphics Viewer" tab and select open Verify the Graphic file object appears Click "create" to process the Graphic object. Click on the Graphic object Verify the Graphic object/s appears in StruxureWare. Verify that the graphic object points can be controlled using the graphic property editor Double click on the graphic page Verify page editor appear Update the control state or value from the page editor Verify the Graphic updates in both StruxureWare and I/NET Verify that you can edit and save the .tgml (StruxureWare Graphic Editor) Launch the StruxureWare Graphic Editor Click on file=>open=>file Locate and select your .tgml file Click "open" and verify the .tgml graphic appears Update the graphics and click the save icon. Verify the graphic saves correctly close the Graphic Editor Right-click on "INET Graphic"=> properties Verify the Graphic "create object" editor appears. Click "Next" button Verify the "Basic Settings" appears. Locate the converted files by clicking on the [...] symbol at the end file line. Point to the Graphic *.tgml to be opened Select the specified cell "Graphics Viewer" tab and select open Verify the Graphic file object appears Click "create" to process the Graphic object. Verify the updated Graphic object appears in StruxureWare. Verify the creation and operation of all Display Windows Types - Verify that all these windows update with live data ***Ensure that the Host Masking and Message Masking is set*** Using I/NET, select Summary=> Controller => from the main menu. Verify AMT is running Verify a "controller summary" window appears. Select your Discrete Alarm (DA) point type object. (video alarm) Verify the Point Object is "off" Using StruxureWare, Select your Discrete Alarm (DA) point type object. (video alarm) Right-click on the point type object and select Properties (Value) Change the control state of the point to "on" or 1 Change view to engineering Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Verify all of the messages within the columns are parsed and are correctly filed Click on the "events" tab Verify alarm messages appear within the "Events" window Verify all of the messages within the columns are parsed and are correctly filed Using I/NET, Verify AMT receives the event message, Exit Alarms - renter - verify that all windows are returned to the same position per operator. Verify that all alarms and events are time-stamped to the nearest second. Verify add, remove and re-organize columns using (Add/Remove columns) Click on the "alarms" or "Events" tab Right Click on a column Verify the "Add/Remove columns editor appear Select a checkbox to add or Select to remove an attribute Click the Ok Button Verify columns are added and removed. To reorganize a column, select and drag the column either right or left Verify the column is re-organized Verify that an operator may acknowledge alarms Using I/NET, select Summary=> Controller => from the main menu. Verify AMT is running Verify a "controller summary" window appears. Select your Discrete Alarm (DA) point type object. (video alarm) Verify the Point Object is "off" Using StruxureWare, Select your Discrete Alarm (DA) point type object. (video alarm) Right-click on the point type object and select Properties (Value) Change the control state of the point to "on" or 1 Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Select the active alarm message and Click the Acknowledge icon Verify the message is acknowledged Verify that the operator may hide and unhide alarms from each alarm type window Using I/NET, select Summary=> Controller => from the main menu. Verify AMT is running Verify a "controller summary" window appears. Select your Discrete Alarm (DA) point type object. (video alarm) Verify the Point Object is "off" Using StruxureWare, Select your Discrete Alarm (DA) point type object. (video alarm) Right click on the point type object and select Properties (Value) Change the control state of the point to "on" or 1 Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Select the active alarm message and Click the Hide alarm icon Verify the message is hidden Click the show hidden alarm icon Verify the message is appears Select the message and click the unhide alarm icon Verify the message is appears Create a A Sample and/or D Sample in I/NET ***Verify that the time zone is updated to reflect your zone*** Using INET, select Edit => Controller => Point Extensions => Trend Sampling (TR) Verify the TR extension is set up. Set up Trend Definitions in INET for either (ASample or D Sample) Verify Trend Results in INET Using StruxureWare, Right click on INET Interface and select "New => Value" Verify "Create Object" window appears Verify "value appears in the name field. ie (Value PP.BB AI) Change the name "value" to "A Sample Trend log Value" Click the "Create" button Verify Newly created INET Trend Object (A Sample Trend log Value) appears in StruxureWare. Select Trend log Value Go to the "basic" tab or Right click on the Trend object and select "properties" Locate the "point to trend" Click on the "…" and select an point object to trend Click select button Verify the correct path appear Click "ok" button Verify the Trend Log Value Object appears within the INET Interface Tree Locate and right click on the newly Created Trend Log Value Object (LL.SS.PP.BB AI). Go to the "Actions=> view in" from the main menu or right click on the Trend object and select "view in" Select "Trend Log List"=>"New Trend Log List" Verify Trend entries appears in the Log info in StruxureWare click the save icon Verify the Save Object editor appears Point to Server 1 Name the Trend object "A Sample Trend log List and "save" Verify the newly created Trend log object appears and Trend log entries appears StruxureWare Verify that you can Add an A Sample and/or D Sample Trend chart Locate and select the newly Created INET Trend object (LL.SS.PP.BB AI). Go to the "Actions=> view in" from the main menu or right click on the Trend object and select "view in" Select "Trend Charts"=>"New Trend Chart" Verify Trend Chart and Chart Lines appears in the in StruxureWare click the save icon Verify the Save Object editor appears Point to Server 1 Name the Trend object "A Sample Trend Chart and "save" Verify the newly created Trend Chart object appears and Chart Lines are being plotted. Configuration and Log into Webstation Locate the StruxureWare machines IP address by typing (IPConfig) at the command prompt Make note of the IP Address (example: 10.159.XXX.XXX) log into the remote machine and run the browser (IE) On the remote machine enter the target StruxureWare machines IP address at the browser address line and click enter….(example: http://10.159.XXX.XXX) Verify "Welcome To StruxureWare" editor appears enter user name: admin, password admin and click "log on" Verify Webstation system tree view appear. DCU Tests (controlling Points) Select "INET Interface" select the List view tab Verify all of the Points objects for the DCU controller appears Select and Right click (Discrete Alarm (DA) point) =>properties Scroll down to Values Change the Value of the point to "on" by clicking the drop down and selecting "1". (Value will vary upon Setup) click ok Verify the state changes on the (Discrete Alarm (DA) point) object. Right click Analog Input (AI) point type object =>properties Scroll down to Values Change the control value by entering a numeric value. click ok Verify the value changes on the Analog Input (AI) point type object. Graphics Click on the Graphic object Verify the Graphic object/s appears in Webstation. Double click on the graphic page Verify page editor appear Update the control state or value from the page editor Verify the Graphic updates in both StruxureWare and INET Alarm and Messages Change view to engineering Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Select the active alarm message and Click the Acknowledge icon Verify the message is acknowledged Verify all of the messages within the columns are parsed and are correctly filed Click on the "events" tab Verify alarm messages appear within the "Events" window Verify all of the messages within the columns are parsed and are correctly filed Install StruxureWare/ES/I/NET up to 10 workstations (Windows 7 or Windows XP sp3). Connect multiple Stations to one ES Install only the StruxureWare Workstation Log into the Workstation is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Workstation Verify "Welcome To StruxureWare" editor appears Enter user name: admin, password admin Enter the IP address of the with the main ES, server: IP (XXX.XXX.XXX.XXX) Click log on" Select either the Administration or Engineering view Verify the Workstation System tree screen info from the main ES machine appears. Repeat steps 1-6 on multiple machines. Connect No ES StruxureWare client (w/o I/O server) to a ES StruxureWare client (with I/O server) Locate a machine that has StruxureWare Workstation/ES and I/NET (I/O server) installed and make note of the IP address Install only the StruxureWare Workstation on another machine Log into the Workstation is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Workstation Verify "Welcome To StruxureWare" editor appears Enter user name: admin, password admin Enter the IP address of the with the machine above Click "log on" Select either the Administration or Engineering view Verify the Workstation System tree screen info from the main ES and I/NET (I/O server) machine appears. Click on "INET Interface" and Actions=>"Launch INET" or right click=>"Launch INET" Verify the INET does not launch. Convert and Launch Customer Graphics Connect to a Host LAN tap Configuration (1200 and 9600 baud rate) Select Server 1 Select "Device Discovery" tab Click drop down using the "Select device type" Select "Inet devices" Verify the Host LAN Configuration appears in the list of Links in list view Connect to a 731 Device Select Server ES or AS Select "Device Discovery" tab Click drop down using the "Select device type" Select "Inet devices" Verify the 731 Device appears in the list of Links in list view

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. Resolution IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for step-by-step instructions for this process.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. If the device is new out of the box, or has attempted recovery after a format command, please see Default IP address following Xenta Server "format" command is different than from factory for the known default IP addressing. Resolution Preparation: You need to have an RS-232 serial cable (TAC Xenta Programming Serial Kit 0-073-0920-0). Plug the RS-232 cable in to the RS-232 B port. The RS-232 B port is the second left port at the front. Then connect the other end to the computer. Configuration steps: Go to Start > All Programs > Accessories > Communications > HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. Type the appropriate information for DHCP, IP-address, Subnet mask, Default gateway, DNS, Website name, Domain name, and Host name. Type “yes” for “Do you want to restart the IP interface”. Quit HyperTerminal when the restart is finished. See [Video] Setting the IP address of a Xenta 5/7/9xx through serial communication to watch a video of this process.

Issue When logging into the web server of a Xenta controller using Mozilla Firefox 4 an error message is shown stating that the website is using an invalid security certificate.  When logging into Xenta server using Firefox 4 a certificate error is displayed as displayed below: The complete error screen reads as follows: This Connection is Untrusted You have asked Firefox to connect securely to 192.168.1.152, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Get me out of here! Technical Details (IP Address of Xenta) uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for (IP Address of Xenta) (Error code: sec_error_ca_cert_invalid) I Understand the Risks If you understand what's going on, you can tell Firefox to start trusting this site's identification. Even if you trust the site, this error could mean that someone is tampering with your connection. Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification. Add Exception... How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Mozilla Firefox 4 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Firefox 4) cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution There are two possible resolutions: Install the self-signed certificate using the following steps: Expand the "I Understand the Risks" bullet then click the "Add Exception" button. Firefox will automatically retrieve the certificate from the Xenta server. Make sure to check "Permanently store this exception" and then click "Confirm Security Exception" The certificate is now installed and the warning screen will no longer show up when logging into the server. It may be necessary to restart Firefox for the changes to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Firefox is uninstalled then reinstalled. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate. Purchase a certificate issued by a Certificate Authority (CA): These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. Please see TAC Xenta Server - TAC Networks - Technical Manual for more information. See "There is a problem with this website's security certificate." when logging in to Xenta web server using Internet Explorer 8 for information on installing certificates into Internet Explorer.

Issue The Xenta 7xx from factory it has the default IP address 192.168.255.2, which also is stated in the manual. But when you run the “format” command on a Xenta 7XX, you will get IP address 172.22.1.5. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 527 NPR, 555, 701, 711, 721, 731, 901, 911, 913 Cause The format command will wipe all memory from the Xenta Server. Its IP address will need to be reset, system program will need to be reloaded, and XBuilder project will need to be redownloaded. Resolution The Xenta from factory has the default IP address 192.168.255.2 subnet mask 255.255.255.0 After the “format” command it will have IP address 172.22.1.5 subnet mask 255.255.255.0 See IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for instructions on setting the IP address to the desired address.

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue Can I take a 26 bit Wiegand Hexadecimal Card Number format and find out what the Facility Code and Card Number are? Product Line TAC INET Environment 26 bit Wiegand Hexadecimal Card Cause Need to discover the Facility Code and Card Numbers Resolution Yes you can do this. This document will show you the process on how to determine these values: 26 Bit Wiegand Format Also see Conversion from I/NET hexadecimal code to Continuum Facility/Card Number for an Excel utility to perform this conversion.

Issue Separate a 7792 or 7793 into two 7798C Split SAV files  Product Line TAC INET Environment I/NET Seven 779x Controllers Cause Need to replace a 7792 or 7793 which has two station addresses and replace with two 7798C Controllers which have one station address Resolution To split the required SAV Files: Download and Extract the attached SAV_Split_EXE.zip Make a backup of the I/NET Seven system using DBCreate. Perform Station Save to all the required controllers Copy the SAV files that need to be split to the same location where the ZIP file was extracted too in step 1. Run the SAV_Splt.exe The commands are showing the Sav_Splt.txt file contained within the ZIP file and shown below Purpose: Use this tool to create two 7798 SAV files from a dual-station 7793 SAV file. Syntax: Sav_Split.exe (with no parameters will check all save files in the current directory and split 2 station 7793s.) Sav_Split.exe LLSS (where LL = Link and SS = Station) Result: The resulting files will be named DCULLSS-0.SAV and DCULLSS-1.SAV. Rename these files appropriately to match the link and station of the 7798 into which each will be loaded. Example: SavSplit.exe 0906 Results: DCU0906-0.SAV and DCU0906-1.SAV     Finally check the split files using the "Work Offline" mode within I/NET Workstation. Any issues or additional questions please raise a case with your local support   For SAV file upgrade information see How to upgrade bin and SAV files in I/NET controllers.

Issue Some Windows OS do not come with Hyperterminal installed. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Vista Windows 7 Cause Hyperterminal was not included in the Operating System software package. Resolution Installing Original XP HyperTerminal Download this .zip file which contains the necessary executable and dynamic link library for running hyperterminal Unzip to local hard drive. Double click the hypertrm.exe to launch hyperterminal See Connecting a serial cable to a Xenta 5/7/9xx controller for proper cable connection and hyperterminal settings if needed. Alternatively, extract the two files from any XP installation and copy them to the new Windows OS. hypertrm.exe default installation is in C:\Program Files\Windows NT hypertrm.dll default installation is in C:\Windows\System32. Alternatively, from a Windows XP CD, both files reside in the i386 directory.

Issue AMT has stopped receiving data AMT is not receiving data A new link added to a system, is not sending messages or transactions Product Line TAC INET Environment I/NET Cause AMT can stop receiving data for several reasons. Connection between Remote Client with I/O and SQL is broken AMT is Paused Communication to the device is not functioning AMT Masking is not set correctly Host Masking is not set correctly Point Masking is not set correctly Door Editor Masking is not Set The software has frozen I/NET has reached its maximum online event size and FIFO is not working (very rare) Other Resolution Connection between Remote Client with I/O and SQL PC is broken. Check that no other I/NET PCs are connected to the SQL database. This may include an instance of I/NET installed on the SQL PC Restart the I/Net Remote Client with I/O to re-establish the connection with the SQL Server Wait several minutes for data to update. If this fails, ensure that there are no firewalls or communication failures between the 2 PCs. If using I/NET v2.42 there have been instances where this version does not pass events to the SQL Server.  This is fixed in v2.43 or greater. AMT is paused Right-click anywhere in an open Alarm/Transaction/Message window The bottom choice is either "Pause" or "Resume" If it is "Resume" click on that and AMT function will be restored Communication to the device is not functioning Minimize AMT and open I/NET Connect to the controller Select Summary>Controller If you see values and get no error messages this is not the issue If you cannot see values or get a "No Entries in Database" error, determine why communication is down AMT Masking is not set correctly In AMT Select Edit>Configuration Note the current settings, take a screen shot and save it if possible For troubleshooting purposes, select all of the check boxes under "Messages/Alarm" Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Host Masking is not set correctly (TCP/IP only) Right-click on the I/O server and select Configure Modify the Active Profile On the bottom of the screen click on "Host Masks" Select any NPR or 527 Note the current settings Check all boxes Click okay Repeat 4-7 for all NPR or 527 devices Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Point Masking not set correctly Connect to a controller that you expect to receive messages from Select Edit>Controller>Resident I/O Modify a point you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Messages and Alarms Click okay Go to the controller summary and attempt to trigger a message or alarm Door Editor Masking is not Set Connect to a controller that you expect to receive messages from Select Edit>Controller>Doors Modify a door you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Transactions and Alarms Click okay Attempt to trigger a message or alarm The software has frozen Restart the I/O server If this does not work restart the computer I/NET has reached its maximum online event size and FIFO is not working (very rare) Right Click on the I/O server and select Archive Configuration Enable Archiving if it is not enabled Increase the size of the maximum online events Restart the I/O server Trigger an Alarm or Event in I/NET Verify AMT  Other troubleshooting steps Force a Lan to reconfigure by changing the station address of the Xenta 527, then changing it back If AMT still will not function Repeat the above processes using an Event window with no filter.  It is possible messages are being received, just not to the open Window Close all open AMT windows Select System>New>Event Window Click Okay This opens an Event Window which will display all data coming into AMT Repeat the above troubleshooting processes The Controller LAN is having communication issues Cycle power on one of the Controllers on the Controller Lan to force a Lan Reconfigure Other solutions for this issue have been documented in these articles: No door transactions coming into AMT: Quick Poll is not enabled.  Typically applies to older sites. Transactions not Updating AMT Window using direct connect: For Direct Connect systems No Transactions or controller Events in AMT: Reliable Tap AMT messages stop after re-installing I/NET: Applies to recently upgraded sites.

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK.