Building Automation Knowledge Base

Issue ID Works 5.1 badge printing error and I/NET Seven rev 1.16B. Product Line TAC INET Environment ID Works 5.1 I/NET Seven rev 1.16B Cause Attempt to save or print a badge in ID Works 5.1, the following error occurs:   Data Source Error A cursor with the name 'SQL_CUR06B8F1D0' already exists. State:37000,Native:16915,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] Resolution In order to correct this issue, contact Schneider Electric Product Support and ask for the “I/NET Seven 1.16B/IDW 5.1” patch. We will e-mail this patch to you. A better solution is to upgrade to I/NET Seven Rev. 1.17, which includes the patch in the software.

Issue Device driver open failure Echelon LonMaker Failed to open network interface device. (Subsystem: NI, #39) Environment LNS LonMaker Vista Cause NI error #39 is a network interface error. It indicates that the network interface driver failed to open the network interface. For the i.LON 10 or i.LON 100, this error occurs when the LonWorks Interfaces driver configuration on your computer does not match the network interface settings in your i.LON 10 or i.LON 100. Improperly seated PCMCIA PCC-10 LON Adapter. Can happen with some regularity when using a NIC852 and going onnet through LNS Server.  Subsequent attempts are usually successful Resolution If the LON Adapter is not properly inserted, you should try removing it and plugging it back in, or by using a second card temporarily and then switching back to the original card. If unsuccessful... To correct the error, open the LonWorks Interfaces Control Panel program and verify that the port setting, authentication key, hostname, and DNS suffix match the settings in your i.LON 10 or i.LON 100. To open LonWorks Interfaces, click Start, click Control Panel, double-click LonWorks Interfaces, and then click the RNI tab. Please reference the i.LON 10 or i.LON 100 user guides or online help for instructions in modifying the configuration of an RNI. When opening your network, make sure you select the correct network interface. For an i.LON 10 or i.LON 100 RNI, the name that you select in the LonMaker tool must match the name that you see on the LonWorks Interfaces RNI tab. Echelon Support KB515 .

Issue When editing a TGML error A generic error occurred in GDI+ appears Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista StruxureWare Building Operation TGML Graphic editor Cause This issue occurs after you install security update 3045171. You experience a crash when you use Windows GDI+ to create text outline-based path objects on a computer that is running Windows 7 Service Pack 1 (SP1) or an earlier version of Windows. Resolution Download the patch below from Microsoft https://support.microsoft.com/en-us/kb/3065979 It has been noted that this patch do not solves all the issues, if you still have issues with other applications uninstall the security update KB3045171.

Issue Echelon LON interface card installed in computer is not recognized by the LonWorks Plug and Play utility nor by the I/A Series software installed on the computer. Environment LON interface card PC Cause This problem is caused by not installing the Echelon driver for the PCLTA-10 / PCLTA-20 / PCLTA-21 / PCC-10 card before installing the card into the computer. Resolution Steps 14-20 of this procedure can be used to test the PCC-10 lon card and driver if the proper driver is believed to be installed.     Before attempting to reinstall the driver, verify that this Echelon file is available:  "OpenLDV340.exe", "153-0117-01C.zip" or "PCLTA21 Win2k XP.exe". If the .zip version is available, extract the .exe file from that .zip file, to the desktop.   To correct the problem and install the proper driver, use the following procedure. Open the Windows Control Panel and select SYSTEM then select the hardware tab. Select the Device Manager button. Check to see if the Echelon card is already installed -- look for the entry "Lonworks Network Interface" and click on that entry to open it then select the "Lonworks xxxx Network Interface" choice that was just displayed. (then continue with step 5 below.) If the Lonworks Network Interface was not shown, look for an entry with a yellow question mark -- a Lonworks entry so marked should be found. Select that entry. Right click on the Lonworks entry just selected and select "Uninstall…". Follow the prompts to uninstall the driver. Shut down Windows and power down the computer then remove the Echelon card from the computer. Power up the computer. Log into the computer using an account with full administrative rights. Run the Lonworks driver application file ("OpenLDV340.exe", "153-0117-01C.zip" or "PCLTA21 Win2k XP.exe") that was downloaded and extracted. This installs the driver into Windows. After the installation completes, close the prompt indicating that a reboot is required then shut down Windows and power down the computer. Reinstall the LON interface card. Power up the computer and log into Windows. The system will indicate that new hardware has been installed and will attempt to locate a driver for the new hardware. Allow the system to install the card driver. When the hardware installation wizard finishes, it may indicate that the computer must be restarted before attempting to use the new hardware. If so prompted, shut down windows and restart the computer, logging in again as an administrative user. Open the Windows Control Panel and select (double click) the "Lonworks Plug 'n Play" entry. Verify that the device selected is LON1. If not already selected, specify the NSIxxx application in the NI Application selection box. Click the "Diagnostics" button. Click the "Reset" button then click the "Restart" button. Click "Yes" to reset the card to its boot state. Click the "Test" button and verify that no errors are indicated. Click the "OK" button to leave the Diagnostics screen then click "OK" on the Lonworks Plug 'n Play screen to save the configuration information and exit the utility. The Echelon LON Interface Card is now ready to use.

Issue When upgrading to 1.4, the reference system will be changed to follow newer more strict rules. Product Line EcoStruxure Building Operation Environment Device Administrator Cause With the release of 1.4, StruxureWare now has a tighter control on bindings. This is to prevent users from creating bindings which hinder system communication. When a system is upgraded from 1.3, to 1.4 any bindings that do not follow the new rule set will be dropped. Here are the 3 major items for this new rule set. See Reference Guide and References beginning with 1.4.x for a full explanation. Public Signal bindings will be dropped Multiple bindings will be restricted to one Bindings to Local Node NVIs will be dropped during the upgrade. Resolution To upgrade the Automation Servers, follow these steps: NOTE: You will need to have a copy of Workstation at 1.3 in order to make changes to the Automation Server during the upgrade process. Use 1.4 Workstation after you have completed Perform a Manual Backup of the Automation Server. This backup must include historic data. Ensure that a copy of that backup is saved to an external disk as a recovery option. Open Device Administrator 1.4 Connect to and Select an Automation Server Click Upgrade Device. Please Read the warning in this pop up message. This will upgrade the most recent backup of the Automation Server. Any changes to the system made since the last backup will be lost at the end of this process. Note that the yellow Progress bar means that you MUST review warning in the conversion log. If the progress bar is Yellow or Red, proceeding may result in irreversible system changes. Click "Open" under the conversion log column. This is very difficult to read in Notepad. Perform a Save as .txt and open this file in either Word Pad or NotePad++ for easier reading Notice the Change in display when the information is viewed in WordPad Use the notes from Reference Guide and References beginning with 1.4.x and the conversion log analysis from AS Conversion Log Analysis to make sure that all objects with WARNINGS meet the new rules. This will require making changes to the system via workstation. Repeat steps 1-8 until you are happy with the conversion log. Please note, that you must perform a new backup to get an updated log. Click on "Download updated database to devices" Click Okay in the pop up Wait for the Installation to finish successfully. If any errors occur, be sure to get a screen shot and contact Product Support Note: If the upgrade doesn't complete correctly on one of the AS, cycle power on the AS, go back to the previous version and perform the upgrade again.

Issue How can a workspace be created that can see only a single graphic page at a time. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Workstation Cause While more complex workspaces can be created a kiosk or graphic page style interface could be the perfect workspace for the occasional user or touch screen style kiosk in a communal area. Resolution To create a workspace of this style it is important to use the Work Area Window instead of a Graphic pane since the Graphic pane will not fill the window area and has to be linked to a side of the workspace area. Open the StruxureWare Control Panel Select Account Management Click Add under Workspaces Specify the name of the Workspace ("Kiosk" for example) Click Next Click Add in the Content Window Highlight Work Area Window and  click Next Specify your initial path to be the default graphic you want to be presented such as a home page. Click Create Define what user interface options you want to restrict such as the history bar, toolbar, or address bar (Address bar for example can allow access to other parts of the database unless you restrict it with access rights or user permissions) Click Create Select your newly created workspace from the drop down menu and select  User Account groups Add the user account group you want to use this workspace to the right hand column. The graphic page only workspace should now be accessible or configured as the default workspace for a user both in Building Operation Workstation or Webstation.

Issue When troubleshooting SMTP email issues it is oftentimes handy to send a test email directly from Windows in order to narrow down the part of the system with the problem. Product Line Andover Continuum, EcoStruxure Building Operation Environment Windows Continuum SmartStruxure Cause Troubleshooting technique. Resolution Simple way to test SMTP email for testing purposes. Make sure telnet is turned ON in Windows. (If not, go to Control Panel > Programs > Turn Windows Features On or Off > turn ON the Telnet Client.) Open a command prompt and type telnet domain name (or IP address) and port. telnet 10.169.9.10 25​ Type HELO and identify the sending system helo MyPCName​ Type mail from: followed by an email address mail from: user@tac.com​ Type rcpt to: followed by destination address. (NOTE: must be an email account in the mail server) rcpt to: user@3indq.com​ Type data then ENTER key Type a message Type . (period) then ENTER to end NOTE: Type slowly and if you mistype something hit enter and after the error re-type the line. Using backup space appears to work but it doesn't. NOTE: Make sure Telnet server is installed on the SMTP server. Make sure Telnet service is enabled/running on the SMTP server

Issue After creating a new station using the "New Station Wizard" in Niagara G3 Workbench, it fails to copy into the ENC using the "Station Copier". This error message appears: "The local station database file config.bog is currently in use, and cannot be copied". Environment Niagara G3 Workbench Cause It's because a "Save Bog" was not done. Resolution Go back to Workbench and open the station, make a change and do a "Save Bog". The station should now copy without issue.

Issue A Niagara G3 jace-6 has been operational in a building for more than two months with no reported problems.  End customer reported no updates to related graphics screens.  The jace-6 stopped responding on both of its ethernet ports.  A serial shell connection displayed the following information: IPL for NPM 6-E (PPC440EP) v4.00-6.32 ECC Press to stop autoboot... Autobooting... npm6xx startup version 7.00-6.41 Welcome to QNX Neutrino 6.4 on the NPM 6xx (ppc440) Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:01:f0:8e:5f:70 media: Ethernet none full-duplex status: active inet 143.83.31.10 netmask 0xffffff00 broadcast 143.83.31.255 inet6 fe80::201:f0ff:fe8e:5f70%en0 prefixlen 64 tentative scopeid 0x2 ------------------------------------------------------------------------- NPM6-E with T2023 JACE-2 Base Board detected SRAM mounted successfully at /sramopt LON interface detected # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGILL (0x4) at pc=0xfe4a26dc, pid=1773598, tid=1 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_34-b28 mixed mode, sharing) # Problematic frame: # Memory fault   Environment Niagara G3 jace-600, jace-600E, jace-700 Cause Internal memory issue Resolution The jace-6 cannot be repaired with a reported memory fault.  Replace it.

Issue A Niagara R2/G3 UNC/JACE is rebooting every 15 minutes and the standard output window indicates AC Power status failed and a "Battery test failed" gets logged as well. Product Line TAC IA Series Environment I/A Series UNC, ENC or JACE chassis with Gel-cell backup battery Cause Marginal or failed battery or bad battery charging fuse Resolution The UNC automatically performs a battery load test every 15 minutes. If the voltage drops below a predefined value, the battery test indicates "battery test failed". If the voltage is higher than the predefined value, the battery test indicates "battery test passed". This message is only reported once unless the detected battery condition changes. A station alarm is generated only when the new outcome is different that the previous test. If a battery is marginal, the test may alternate between "passed" and "failed." Additionally, a bad or marginal battery has been known to cause random UNC reboots. Begin troubleshooting by checking the battery fuse (field replaceable only in the UNC-500/510 controllers), connections and voltage level.  If the battery voltage is low (less than 12 Vdc), disconnect the battery and monitor the UNC for errors or rebooting. If the errors or rebooting stops install a new battery.  After installing the new battery, measure the battery charging voltage.  The voltage reading should be between 13 and 14.5 volts DC if a good battery is connected.  If the installed battery is partially discharged, the charging voltage reading may be as low as 12.5 volts. In release 2.301.522, a change was made to how embedded controllers (UNC-410 / 500 / 510 / 520) perform the backup battery test.  Formerly, a "marginal" battery might result in continuous reboots. Now, the battery test is better coordinated with the AC power test. This prevents the scenario of repeated AC power fail shutdowns upon boot up if the battery is bad or weak.

Issue An error was detected while attempting to set an attribute in a remote Infinity object Infinity Controller error: No response from I/O module Environment 99xx 9680 Continuum Cause FTT-10 IOU modules are not compatible with RS-485 Netcontrollers RS-485 IOU modules are not compatible with FTT-10 Netcontrollers Resolution There are a few ways to determine what bus topology type was built into a IOU module or Netcontroller  Take a look at the original purchase order which will indicate the type Look at the inside cover of the IOU module(s) and in the model description RS-485 or FTT-10 may be indicated Inside the cover of the Netcontroller and the IOU module there is a black component on the circuit board that has Echelon FTT-10 on it near the comm bus connector if it is FTT-10 Get the serial number of each of the IOU modules and the Netcontrollers and let Product Support know what they are, PSS can cross reference the number to determine the topology scheme from when it was manufactured If this isn't the issue then try the IOU with only that IOU connect in a different part of the IOU bus or by itself on the Netcontroller Under the cover RS-485 version - CX9900 Netcontroller 1   Under the cover FTT10 version - CX9900 Netcontroller 1

Issue Xenta Server is offline in Vista and can not be reached via web interface. Product Line TAC Vista Environment Vista 5.1.9 Windows 7 Cause The PC has proxies configured. Resolution Open Internet Explorer Go to Tools > Internet options > Connections > LAN settings Disable "use a proxy server" Related Article: Xenta Servers are offline in Vista, although they can be reached via the web interface

Issue The SP-C Controller was deleted and recreated with the Controller wizard to create default objects. The Controller had previously been online and downloads were successful. After being recreated with the wizard, downloads are failing with a failed loading dat file error message seen in the Controllers Download Diagnostics Window. Failed to load DAT file. Path = 'C:\ProgramData\Schneider Electric\SecurityExpert\Download\13.dat' , Error code = 80070002 Product Line EcoStruxure Security Expert Environment Security Expert Client SP-C Cause The Controller still had configuration settings from the previous setup that were causing a conflict. Resolution Clear the Controller by factory defaulting it, then reconfigure. For instructions on how to default a controller, refer to the Hardware Configuration section Defaulting a Controller in the SP-C Installation Manual - System Controller.

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, 2008, or 2008 2. It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 

Issue After doing a save to database from a controller an attempt to reload the controller results in "Invalid Handle ID" or "Object not found in database" for every object in the controller. Environment CyberStation CX9xxx controller. Cause Bad object instance ID in the database. In the Continuum database each object in a controller contains the instance id of its owner controller in the ObjectIdHi field of its instance ID, this is illustrated in the screen shot below, Num1 is an InfinityNumeric created in the controller named NC2.42. You can see that the ObjectIdLo of NC2.42 becomes the ObjectIdHi of Num1 Somehow during the process of reloading a CX9200 via HyperTerminal followed by a save to database, all the objects end up with the wrong controller id in their ObjectIdHi resulting in the aforementioned error on reload. Resolution Put CyberStation in offline edit mode. Send the controller to ASCII file. Delete the controller. Import the file created in step 2 to re-create the controller and its objects. Put CyberStation online Reload the controller.

Issue Get error message 0x80004002 when trying to access objects under an OPC server in the Vista OPC tool. It is possible to see the OPC server but get the error when accessing the object under it. Environment Vista 5.1.5 Vista OPC tool Cause For some reason some important DLLs for OPC were not registered on the client PC. Resolution Register the following DLLs: opccomn_ps.dll opc_aeps.dll opchda_ps.dll opcproxy.dll

Issue Cannot see a SE7300 Room Controller when connected to a BACnet MS/TP network. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SE7000 Series SE7000, SE7200, SE7300, SE7600, SE76x7 Ex Viconics branding VT7000 Series Viconics room stats with BACnet communications Cause Units are shipped from the factory with the BACnet network disabled. Resolution Power up the unit. Press the middle button down for 8 Seconds (It is either the Override or °C/°F Button depending on model). Enter the password if it has been set, or leave as the default 0 for no password (as shipped from the factory). Use the down key to find the "Comm Addr" value. By default this is set to 254 BACnet communications disabled. Adjust this to the desired value within the valid range of 1 to 127, but also ensure it is in the range of your BACnet Max Master setting on the connected system. Once set, power off/ on the unit to change the address to the new value. The unit should now be visible on the BACnet MS/TP network.    Note: The SE7xxx Room controllers will auto baud to match your MS/TP network, there is no baud rate setting to adjust. Also any password set on the SE7xxx controller must be temporarily disabled to allow the middle button to operate correctly. For further information on installing the Room Controllers please see SE7000 Series Installation Instructions.

Issue No more address table slots for a device involved in the attempted connection. (Subsystem:  NS Connections, #15) Product Line TAC Vista Environment LonMaker 3.X NS Connections Error codes are not specific to any one LON environment, the display of the error may vary, but the steps to resolve should be the same.   Cause Every LON Neuron chip has 15 total address table slots inside, which store addressing information for SNVT communication.  Xenta programmable controllers utilize Address Table slots 0 and 1 for TAC and Xenta Group Binding information for reporting online status to the Vista Server and transferring TA Network Variables to each other.  This leaves 13 available address table slots in a Xenta programmable controller.  There are many scenarios by which address table slots are consumed (both in the sending and receiving controllers).  If you have exceeded the address table limitations, no further SNVT bindings (which would require additional address table slots) will be allowed.   Resolution The error message should indicate which controller has exceeded its address table limitations (sending or receiving).  First verify the current status of the address table. Right-click on the controller Select Properties Navigate to the Address Table tab.   This will tell you (a) if the address table is indeed full or (b) how many slots you have left.  Knowing this can help you determine the easiest recourse to the problem. If the address table is full in the sending controller: Information can only be sent via one-to-one bindings to 15 controllers (13 from a Xenta programmable).  Sometimes combining data into a one-to-many can save address table slots.  Instead of sending an individual occupancy to 20 VAVs, which consumes 20 address table slots, send them all the same one-to-many occupancy command, which consumes only 1 address table slot. Using a broadcast SNVT binding type will save on address table slots by only consuming one slot per receiving subnet instead of one per receiving controller.  This will increase network bandwidth, but allows one-to-one bindings to many controllers in the same subnet.  Xenta programmable SNVT output limits would be the only limiting factor. See Bind to more than 13 unique LON devices without running out of address table entries for details on creating Broadcast SNVT Bindings. If the address table is full in the receiving controller: If the binding is a one-to-one binding type: This is typically not an issue. The receiving controller does not normally have an address table slot consumed by a one-to-one SNVT binding. The only time a receiving controller has an address table slot consumed by a one-to-one SNVT binding is if that SNVT input is set to ""Poll."" (Unacknowledged, repeated, acknowledged profiles have no bearing on the number of address table slots consumed by one-to-one bindings.)   Unless dictated by the manufacturer of the device with which you are integrating, it is very rare to require polled inputs in a Menta file. Check the SNVT AI blocks in Menta and uncheck the "Poll" checkbox. Binding these inputs will no longer consume an address table slot in the receiving controller. If the binding is a one-to-many group binding type: Every member of the binding (sending or receiving) will have at least one address table slot consumed by the group binding. Freeing up address table slots may require some creative manipulation of the bindings. Options are: Convert to one-to-one bindings where the receiving controller will not lose an address table slot Do not customize every individual combination of group bindings (i.e. send the setpoint to the same controllers that are receiving outside air temp, even if they won't be using it). Every unique combination of controllers will constitute a new group and thus consume a new address table slot in each controller.

Issue Microsoft Outlook is not emailing alarms. Product Line Andover Continuum Environment Continuum 1.XXX Microsoft Outlook 2XXX Cause The created Contact folder used by Continuum Alarms to send emails was not being shown first.. Resolution Open Microsoft Outlook Select Tools > Address Book Select Tools > Options Once opened, select  "Show this address list first:" (It defaults to the Global Address List) Ensure the contact folder with the distribution list created for Continuum Alarms has been selected (Contact) Also see online help: Email, Creating an Event Notification List

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 Require details on how to migrate Users from an SP-C-WEB to Security Expert. Product Line Security Expert Environment SP-C-WEB Security Expert Cause Have a site that has outgrown it's SP-C-WEB installation and is upgrading to Security Expert to expand. Resolution Door configuration and programming cannot be migrated from an SP-C-WEB installation to Security Expert, but the User database can be exported to a CSV file and then imported into Security Expert to help with the migration. Exporting User database from SP-C-WEB to CSV file From the SP-C-WEB user interface navigate to Users | User Search. In the User Search page on the top right (under date) is the Export button. Clicking the Export button will generate a .csv file of all User details. (See attached example Exported Users.zip) Editing User CSV file for importing into Security Expert The Security Expert User import requires the CSV file to be in a specific format: FirstName,LastName,FullName,Facility,Card,PIN,AccessLevel The rules for this format are that: Each field must have a value however the firstname/lastname can be omitted if the fullname is used and vice versa. The facility can be omitted if it is prepended to the card number and separated with a colon (eg 123:4567). If a matching Access Level is not found, a new access level is created. The PIN and Card must be unique for each user. The file cannot contain a header row. Some examples of correctly formatted data are: Joe, Stanley,Joe Stanley,123,4587,1418,Warehouse Staff Georgia, Smith,,123,4654,6884,Warehouse Staff ,,Billy Randall,123,4727,3492,Warehouse Staff Frank,Powell,,,123:4639,3160,Warehouse Staff Importing Users from a CSV File into Security Expert In the Security Expert Client navigate to Sites | Import Users to launch the Import Users Wizard. Browse to and select the CSV File you wish to import the users from, then click OK. Figure 1 - User Import Dialog The Users records are created and a message is displayed to indicate the action was successful.