Building Automation Knowledge Base

Issue Programming a 7798C controller with a Virtual HHC Console Environment 7789C HHC Hand Held Console Cause The 7798C controller can only be programmed with the Emulated HHC Console (The TacHHC.exe is located in the support folder of the INET install CD) using CBL 082 connected to the PC and RS 232 port on the controller. Resolution Before following these steps, make sure you have closed down I/NET, AMT and the InetIOServer applications.    Locate the HHC file on the I/Net CD, Support Folder and copy it to the Root of I/NET. Once copied, double click on the file to launch it, I/NET should not be running at this time. Connect the CBL 082 (Grey shroud connects to the PC)  The virtual HHC is displayed at this time. Right Click and Select the Com Port and Baud Rate. To Set the Controller Type: On the HHC, select Code 90, Enter to set the Controller Type. To Set the Controller Address Select "DCU Address" Enter he desired Address To Set the Baud Rate Code 06 for C-LAN Code 91 for Sub-LAN baud rate. To Direct Connect Once completed, disconnect the CBL 082 from the PC and replace it with CBL 072 for a direct connect to the controller. Start I/NET and open the configuration editor, create a new profile for a direct connect, if it has not been created already. Make this configuration active, close the configuration editor down as well as I/Net, and then restart it again. At this time communications should be established with the controller and the user can start programming the controller. 

Issue What is its part number of the power fuse of an i2/b3 controller? Product Line Andover Continuum Environment Power fuse replacement i2 and b3 controllers 24VAC supply Cause Most controller fuses are not supplied through the factory. Resolution Faulty controllers can be repaired through the regular repairs process, but power fuses can be purchased through local suppliers. The power fuse for the following 24VAC controllers is: Type: Surface Mount Fuse NANO2® Very Fast-Acting, 448 Series Datasheet Ratings: 2A Rating: i2/b3867, i2/b3850 series. 3A Rating: bCX1, i2/b3810 series, i2/b3800 series, i2/b3600 series. 5A Rating: ACX5740, ACX5720 Note: Fuses are fitted to protect the controllers from damage, when replacing one always replace it with an equivalent rating. Also determine the reason why a fuse has blown before replacing, under normal operation a fuse should never blow.  Additional Information CX9702 (115 VA) Main Power Fuse: 250 VAC 1.5Amp Outputs: 125 VAC 3.5Amp replaceable Inputs/Outputs: Surface mount non-replaceable i2/b3814 outputs: see What is the part number of the i2814's output fuse? Note: The part numbers that used to be listed in iPortal have been removed from this article since they are no longer available from Schneider Electric. The fuses may be obtained from third-party vendors such as Littelfuse or Digikey.

Issue How to calculate the required disk space that will be used by WebReports? How to know if SQL 2008 R2 Express (with Advanced Services) will have adequate storage space for the sites Reporting requirements? Product Line EcoStruxure Building Operation Environment WebReports 1.9 / 2.0 Cause Require the ability to forecast how much space will be required to store and retain data within the Building Operation WebReports database. Resolution The attached Excel Spreadsheets can be used to forecast how much space is needed to store and retain the Building Operation WebReports database. WebReports_DB Usage Calculator.zip WebReports_DB Growth Estimator 2.0.zip Note that SQL 2008 R2 Express only allows a database size of 10 GB, so if your configuration is more extensive than that you should probably consider using the full SQL Server 2008 R2 editions. As a quick indicator here are the record sizes for each object type stored in the report server database: Object Type Size per record (bytes)   WebReports versions <1.8 >1.9   Ext. Trend 140 165   Meter 170 140   Alarm 900 500   Event 400 520  

Issue BACnet Broadcast Device Table (BDT) on a BACnet Broadcast Management Device (BBMD) becomes corrupted after a server version upgrade, only if the BACnet BDT was taught from another BBMD The following upgrades have this issue v1.5 to v1.6, v1.6 to v1.7, v1.7 to v1.8 Product Line EcoStruxure Building Operation Environment BACnet Broadcast Device Table BBDT BDT Management BBMD Cause When a BDT is manually built (or BBMD first created), BDTE00001 is always set to the Server IP address. In the example this is 192.168.1.15 When the BDT is taught from another BBMD, the BDT is changed and BDTE00001 is modified. When a Server (Enterprise or Automation) is upgraded (V1.5-1.6, 1.6-1.7, 1.7-1.8), then BDT entry BDTE00001 is changed to it's own IP address. Thus the Servers BBMD BDT can be corrupted with the Server IP address appearing twice in the BDT Resolution The taught BDT can either be set manually, before the upgrade, so it does not get corrupted by the upgrade process or be corrected following the upgrade. Option 1: Change the BDT before the upgrade The BDT Entry BDTE00001 should be set to the IP address the Server that contains it. The BDT Entry (BDTE00002 in the simple example above) that held the IP address of the Server should be set to the value that was in BDTE00001. Option 2: Correct the BDT after the upgrade For the first Server being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries, Then manually reenter in all the BDT entries. For all remaining servers being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries From the First Server BBMD do a teach Verify the BDT table is in the Server Below would be the first upgraded Server as option 2 or a corrected as option 1   NOTES Versions 1.8 and beyond include a fix so that the "BDT Teach" Mechanism does not allow the BDTE00001 to be changed. A hotfix will be available in V1.7 Upgrading to a fixed version will not correct the issue, one of the two resolutions above will still need to be completed.

Issue It is not possible to select a "Trend 10K3A1" Thermistor when configuring a central or onboard IO input point. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server (AS-P) Central IO Building operation Automation Server Bundled (AS-B) Onboard IO Cause The specific thermistor type is not available to be selected. Resolution Configure an input as a resistive Input with reliability level, electrical scale and engineering scale set to: Upper/Top: 0 Lower/Bottom: 587628 Then use a Function Block 10K3A1-Ohm-To-C sample program or Script program to convert from resistance to °C. NOTE Satchwell and Trend both use 10k3A1 Thermistors but the shunt resistance used within it will vary.

Issue Unexplained network and communication errors IT department may have set up IP blocking or set up IP switches incorrectly or there may be an issue with the Continuum setup Product Line Andover Continuum Environment IP network Cause Problems in the IP network, port blocking or incorrectly setup in IP switches IT departments may say their system is set up correctly, but this may need to be tested. Resolution See Router required open port numbers to run a Continuum system for IP port requirements See Continuum Controllers and IP Managed switches for other IP switch settings Get all the problematic equipment connect to a simple non managed IP switch (this will probably involve temporarily moving PCs and/or controllers) Disconnect from the site IP switches if possible (this may not be possible, depending on the site setup, eg. SQL server may be in a server room) PC and Controller settings (IP address, subnet mask, default router) may also need to be temporarily modified depending on the original site set up. Test the system with this temporary setup, if all is ok then the problem lies with the site IP network, if the problem persist then  look at the Continuum setup (Cyberstation install, database, operating systems, hardware issues)

Issue Many customers still have a requirement to run Lonmaker 3.13, but have project specific issues related to software fixes in newer version of LNS Server, and an LNS Server upgrade is required. Product Line TAC Vista Environment Echelon Lonmaker LNS Cause Older versions of Lonmaker 3.1 and LNS server had multiple defects that were addressed in later version of Lonmaker Turbo and LNS Server Turbo. However, it is possibly to run Lonmaker 3.1 and only upgrade the LNS server engine to take advantage of software fixes over time. Resolution NOTE: Any LNS Server version older than 3.10 needs to first be upgraded to 3.2x before 3.2x service packs can be installed. Also, please take into consideration that after upgrading the LNS Server on a system that any other system that needs to open that same database will have to be at the same version or higher. For example: a database upgraded to 3.27 can not be opened on the machine running 3.08.   Please follow these steps for upgrading LNS server to 3.22 and finally up to 3.27: Identify what version of Lonmaker and LNS server are currently running on the system. Please see How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS Server currently running. As seen in the screen shot below the system is running Lonmaker 3.13.10 with LNS Server version 3.08. Download LNS Server 3.22. Once this file is downloaded please unzip all of the contents to the desktop of the local machine. Run setup.exe from the extracted files in the LNS Server 3.22.zip, and step through the installation process. Once the installation of 3.22 is complete please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.22. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.22 like below: Now that the system is upgraded from LNS Server 3.08 to 3.22, service pack 7 should be installed to upgrade the system to LNS Server 3.27. Please download LNS Server/Turbo edition Service Pack 7 file to your local machine. Unzip the contents of the LNSServerTurboSp7.zip to the desktop of the local machine, and run the LNSturboServerSp7.exe file. Step through the installation process. When the installation is completed please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.27. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.27 like below:

Issue When using SigmaX as the method to unlock sigma sometimes the PC ID of the machine running the server can change and prevent any clients from connecting Environment Sigma - All Versions Cause When using SigmaX to unlock Sigma due to the number of network ports now available on modern PC's sometimes when connecting to sigma the Pc ID of the machine can change. This is usually caused by a different network port being used for the main network connection. Resolution After installing SigmaX make sure that the PC is being connected via the local area connection (Wired). This will be used when generating the PC ID. To ensure this connection is used this connection can be made to be the first to be accessed. To do this open Control Panel>Network Connections>Advanced>Advanced Settings. Using the up/down arrows on the right hand side, select the Local Area Connection and move it to the top of the list. It will then be the 1st priority when connecting to a network. You should then be able to use a wireless connection without the PC ID changing.

Issue The IC-GEN OPC server does not communicate with a third party OPC client across Ethernet. Environment Sigma IC-GEN OPC (all versions) Cause The IC-GEN OPC only supports a local IP address configured in the gateway.txt file. Resolution The IC-GEN OPC server can only be connected to third party OPC clients located on the same PC. For more information see Release Note, click here An example using an EIB I/O server, click here

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 Alarms cannot be sent to recipient CyberStation (Workstation) when controller has lost the link to the CyberStation in regard to the alarmed point in Import/Export table. The new alarm shows up in Active Alarm View only after the CyberStation is rebooted Product Line Andover Continuum Environment Workstation, CyberStation NetController (CX99xx, CX96xx) Cause Import/Export table in the NetController does not have the link to the workstation for the alarmed point. Resolution Backup current DB. Shutdown Continuum from all the CyberStations. Execute ImpExpFixupUtil.exe from Continuum install folder (C:\Program Files\Continuum). Reload all the NetController with the "Do not reload attached objects" option.

Issue Without knowing the Device ID / Device Instance these devices cannot add to the MSTP network in the AS or ES. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment Automation Server Enterprise Server BACnet SE7000 Cause Only the MAC ID / Com Address is shown in the display but not the Device ID / Device Instance. Resolution SE7200x Models Default Device ID is set to: 72000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7200F5045B controller with a MAC address of 41 is connected to a network, its default Device Name will be SE7200F5x45B-41 and its default Device ID will be 72041. SE73xxx Models Default Device ID is set to: 73000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7300C5045B controller with a MAC address of 63 is connected to a network, its default Device Name will be SE7300C5x45B-63 and its default Device ID will be 73063. Click here for the Integration Manual. Please refer to the SE7300 series BACnet controller does not come online in StruxureWare Building Operation if SE7300 controller does not come online.

Issue Create smooth rotation for an object in a Vista TGML graphic Product Line TAC Vista, EcoStruxure Building Operation Environment TGML Graphics Editor Cause If the "CalcMode" is set to "Discrete" the object will rotate the full specified range instead of taking the duration time to slowly move around it.  Resolution Add a <rotate> tag to the object that will be rotating. Add an <animate> tag to the rotation. Set the properties for the animation: Animation = default state (Start/Stop), if a binding is ultimately used to control when the animation occurs, bind to this attribute. AutoReverse = should the animation continue in one direction or get to the end of the animation and then come back to the beginning? (True/False) CalcMode = determines whether the animation is smooth or jumps from end point to end point of the animation. For rotation, choose Linear. (Linear/Discrete) Duration = the amount of time in seconds that the animation should take. Higher numbers result in slower animation. Freeze = if true, the animation will pause at the last position when Animation is set to False. Otherwise it will revert back to the starting position. (True/False) Repeat = how many times should the animation occur. Default value is "Forever" but this value can also be set to any integer number (1, 2, 3, 4...) From, To = depend on the desired animation and target attribute. For rotation 0 to 360 is typical. Attribute = for rotation, the Angle property of the <rotate> tag is animated from 0 to 360 degrees. For more information on CalcMode see ‘Animation Overview’ in the Help.

Issue In the event of a lost or broken connection between the Vista Server and SQL server, the Vista Server will begin to queue up its events and log values in the $queues\insertevents and $queues\insertlogvalues directories. Once your connection has been re-established those queued files will then be written to the Vista DB, however this process can take an extremely long time,  and possibly cause the Vista server to hang at start up and even crash.  Product Line TAC Vista Environment Vista 4.3.0 or higher with SQL  Cause Broken SQL connection between Vista and local or remote SQL server. Resolution If you are not in the need to this queued event and log data you can manually delete all of these queued files. Opening this directory with Windows, highlighting all files and deleting them usually does not work, because of the enormous amount of files that may be stored in their respective directories. The best way to delete these files is to use DOS. Remember stopping both TAC Vista Server and the DSS Writer service before deleting the files.   Method 1: The proper steps to delete these files with DOS using the "rmdir" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues Type "rmdir /S /Q insertevents" - all files and folders including the "insertevents" folder will be deleted Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5.   Method 2: The proper steps to delete these files with DOS using the "del" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues C:\Projects\School\VistaDB\$queues>cd insertevents C:\Projects\School\VistaDB\$queues\insertevents> Type "del *.*" and then "Y" to confirm that all files on that directory will be deleted. C:\Projects\School\VistaDB\$queues\insertevents>del *.* C:\Projects\School\VistaDB\$queues\insertevents\*.*, Are you sure (Y/N)? y Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5. Now both of these directories should be emptied and if your SQL connection issue has been rectified your events and logs will write as normal to SQL.     Alternatively, this utility will split the queued files into folders of 4,000 files each.  Windows can handle each of these folders and make the task of deleting the queued files more manageable.  Click the screen capture below to download the utility.  

Issue Converting I/NET Symbol Libraries to TGML Components Environment I/NET TGML Graphics Converter Cause Many users want to continue using the same graphic libraries they had in I/NET while in StruxureWare. The TGML conversion tool, will convert these libraries to TGML components. Resolution From Either I/NET or StruxureWare Workstation, open the I/NET graphics Conversion tool Select the Symbols check box on the right hand column Browse to the source and destination folders Select the files you wish to convert. Click Convert In Windows Explorer Browse to the destination folder. You can double click on each component to automatically add it to your "My Components" Component Library. NOTE: Be sure the TGML Editor is closed while you do this. Once you have finished this, open the TGML Editor and note that your My Components Library is now full. If desired, you can change the name of this library for sorting purposes or future exporting.

Issue There is no built-in Credential Type for the HID 37-Bit badge with no site code (H10302). Product Line Security Expert Environment Security Expert Server Access Card Format Cause Security Expert does not have the HID 37-Bit badge (H10302) with no site code as a built-in available Credential Type. Resolution 1) In the Security Expert Client, select Sites -> Credential Types 2) Create a new Credential Type with a name of your choosing. 3) Under Configuration, select the Format as Wiegand. 4) In the field labeled Wiegand or TLV Format, enter the following exactly as written:                                                        A,FACILITY,0,MSB,BIN__B,CARD,35,MSB,BIN__PBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBP_EXXXXXXXXXXXXXXXXXX.................._..................XXXXXXXXXXXXXXXXXXO 5) Save   NOTE: This article assumes that the reader is familiar with creating and deploying Custom Credentials, If this is not the case, then please reference the Complex Transition Programming section of the Transitioning Continuum Sites to Security Expert - Transition Guide

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 Services for assistance. Issue When running the stored procedure sp_changedbowner to change the dbowner to "andover97", the following error message is received: "The proposed new database owner is already a user or aliased in the database". Product Line Andover Continuum Environment Continuum Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008 (Keywords: drop user ) Cause The Andover97 user already has access to the database through an existing alias or security account within the database. This can occur when the DB is not restored properly to the SQL server. The database may have been detached and then attached again, which is not the preferred method of restoring a ContinuumDB. Resolution Under the ContinuumDB there is a "security" and then "users" folder. Check to see if the Andover97 user is in this folder. Continuum does not put this user in this folder. If it is there, then it will need to be dropped from the database before trying to change the dbowner. Do the following: Do a complete full backup of your ContinuumDB. Run the following SQL script to drop the user from the ContinuumDB. USE [ContinuumDB] GO DROP USER [Andover97] GO Re-run the stored procedure to change the db owner below. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO To minimize the chance of this occurring again, the correct procedure for moving or restoring a Continuum database is to do the following: Create a new ContinuumDB with Continuum's Database Initialization. This creates the DB, SQL jobs, stored procedures, adds Andover97 as an admin and a lot of behind the scenes security settings. Restore a previous backup over top of the ContinuumDB created in step 1. Change the db owner with the above query using the sp_changedbowner stored procedure. Re-initialize the Cyberstation into the Database using Continuum's Database Initialization.

Issue Graphics do not display correctly in Sigma 4.06 or above How to upgrade Sigma graphics to Sigma 4.06 or above Environment Sigma 4.06 or above Sigma Graphics Cause Sigma 4.06 or above has been installed and after the graphics have been converted from the SGI or the DRW format to SWC format, the graphics do not display and are blank. Resolution Upgrading from earlier releases of Sigma or BAS. BAS (drw format) Place drw files into C:\bas\data\graphics\slides, the images need to be placed in the appropriate directories as if they are in BAS i.e. animations or pictures. In Sigma 4.06, go to  C:\sigma\binutils and run DrwSWCConvrt.exe. Copy the original drw files into a safe place for archiving/backup. In Sigma 4.06 go to C:\sigma\binutils and run SigUpgrade.exe. Before 4.05 (sgi format) Place sgi files into C:\sigma\data\sgi\slides, the images need to be placed in the directory where they are mapped to in the sgi graphic. In Sigma 4.06 go to C:\sigma\binutils and run SgiConvert.exe. Copy the original sgi files into a safe place for archiving/backup. In Sigma 4.06 go to C:\sigma\binutils and run SigUpgrade.exe. At 4.05 (swc format) In Sigma 4.06 or above go to C:\sigma\binutils and run SigUpgrade.exe. For further detail regarding the upgrade process download Sigma 4.06 Release Note

Issue BACnet Interface has "!" with unresolved references Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v2.0 or later Building Operation Multi-purpose VAV Building Operation Multi-purpose Controller Cause During the startup of a Smart-X controller, the auto-association feature fails and the data becomes corrupted Resolution Go to BACnet Interface -> Time Sync Recipients Find any devices listed as DEVICE_<Instance ID>, select & delete Verify all devices listed are configured as follows: SmartX controllers Recipient Type: Reference Recipient Device Object Reference: <Device in System Tree> If Recipient Name does not match, copy from Object Reference and paste in the field. This helps humans troubleshoot the issue. DO NOT set Recipient Type = MAC Address, Network ID = Global Network or Local Network, Mac Address = Broadcast. This will set time on other ES/AS with BACnet Interface on the BACnet System.

Issue Room controller shows up in the Discovery (Bind) window but will not go online after clicking on “Bind device”. Status in the ZVC object shows “offline (-2)” error. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 SSL SE7000 Cause An invalid value is being overwritten continuously to a local point (to the Room Controller) by a dashboard widget or a third-party device(e.g. via Bacnet). Resolution The invalid value must be corrected before proceeding with the binding process. Example: A value of 0 is being written to the Occupancy command point which only take values of ([1 = Local Occupancy], [2 = Occupied] or [3 = Unoccupied]). The write and read traffic generated prevents other room controllers from joining the network.

Issue Daylight Savings time changed in the U.S. and methods are needed to synchronize time Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Methods for synchronizing controller time Resolution The following document was email out when Daylight Savings changed in the U.S. and contains 2 methods for synchronizing time Click Here to download the pdf document.