Building Automation Knowledge Base

Issue Datacard ID Works gives an ODBC error. Examples shown below: Microsoft SQL Server Login Connection failed: SQLState: '01000' SQL Server Error: 53 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState: '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. Data Source Error Data source name not found and no default driver specified State:IM002,Native:0,Origin:[Microsoft][ODBC Driver Manager] Product Line TAC INET Environment I/NET Seven all versions Datacard ID Works video badging software Cause The "IDWorksView" driver uses a ODBC Connection to allow the ID Works Software to communicate to the I/NET SQL Database. If for some reason this ODBC gets corrupted, you will get an error anytime you try to run the ID Works software. Resolution Go to Start > Control Panel > Administrative Tools Select Data Sources (ODBC) Select the System DSN tab Highlight Seven ODBC SQL Server in the list and hit the Configure button Make sure the settings are as follows: Name: Seven ODBC Description: ODBC Connection for I/NET Seven Server: (local) Hit Next Before you actually login to this window, choose the Client Configuration button and make sure these settings are correct. Network libraries: TCP/IP Connection parameters: Dynamically determine port Note that the InetThirdParty password changed in I/NET Seven rev 2.4X to PassInetDb3p_SE. If you try to use this in this process it will fail on you. Instead of using the InetThirdParty and the password here, use the Username and Password that you use for the DbCreateEditor. Then select the Next button. Verify the settings below, then hit Next: Change the default database to: InetDb Verify the settings below, then hit Finish Perform translation for character data

Issue Trying to get a schedule working in a MNB-1000 and getting the following error message: Schedule Setup Wizard will not run: Not supported for this application's type of device. Device type: 971 Environment MNB-1000 MNL controllers Workplace Tech Cause New to programming the MNB controller line Resolution A 7-day schedule object is available for the MNB-1000 (only) and is part of the Schedule Control stencil. The Schedule Setup option under the Application drop-down menu only applies to MNL applications.

Issue Get "Value does not fall within expected range" error message when trying to view values from a Vista node in webstation. Environment Vista 5.1.X Webstation 5.1.X Vista in network (master with at least 1 slave) Cause This is a COM error caused by a difference in regional settings on the Vista servers. E.g. 100 000.00 may be retrieved as 100,000.00 if other settings are used on another server. This will cause a mismatch. Resolution Ensure that the settings for digit grouping and decimal symbol are the same on all Vista servers. Click on Start\Control Panel\Regional and language options. Select Customize and check the settings on the Numbers tab. Compare these settings with the other Vista servers.

Issue What are the values named Temp_FBValue Environment StruxureWare Building Operation Site with Function Block Cause Site is wondering about the values named Temp_FBValue. What is the meaning and why you cannot bind them.   Resolution A function block variable with the name XXX_FBValue is an output variable from an Input block (e.g. RI- BI- II- PI- block). It’s an internal variable and ought to be hidden, but it’s not so today. It should not be possible to bind theses variables.

Issue Import/Export in TAC Vista Workstation does not work. Nothing happens when trying to start the import/export. Environment TAC Vista Cause The $DatabaseExport and $DatabaseImport objects in the Vista database has been removed, probably during an upgrade. Resolution In the instructions below, we assume that TAC Vista is installed in the default location. Replace the version number (5.1.6) with the actual version you have installed, and the Vista Server name (VistaServer) with the actual name of your Vista Server. This procedure requires that TAC Vista Server is running as an application, and not as a service. 1. Make sure TAC Vista Server is stopped -- First we need to change a file to allow creation of these objects -- 2. Browse to C:\Program Files\Schneider Electric\TAC Vista 5.1.6\$cfg 3. Find a file named "objtmpl.cfg", make a copy, just in case. 4. Edit the file with notepad and find the strings FI_EXPORT and FI_IMPORT. 5. Remove AB on each of the two lines, (stands for abstract object), save and close. 6. Browse to the TAC Vista database folder, and open the folder $thisdb. 7. Change the name of the file TacVista.cfg, to TacVistaOld.cfg 8. Start TAC Vista Server. -- Now we need to create the missing objects -- 9. Open the testclient (testclt.exe) located in the folder C:\Program Files\Schneider Electric\TAC Vista 5.1.6 10. In the menu, click "Session-->Log in" 11. In the menu, click "Services-->Create" 12. In the ID field, write "VistaServer-DatabaseExport" and in the type field write "FI_EXPORT" 13. Click "Create". 14. In the ID field, write "VistaServer-DatabaseImport" and in the type field write "FI_IMPORT" 15. Click "Create". -- Now we have to change the name of the created objects to $DatabaseExport and $DatabaseImport -- 16. In the menu, click "Services-->Access" 17. In "Enter ID:" write "VistaServer-DatabaseExport.$name" 18. Click "Request" 19. Write "$DatabaseExport" in the "New Value" field, and click "Poke". 20. In "Enter ID:" write "VistaServer-DatabaseImport.$name" 21. Click "Request" 22. Write "$DatabaseImport" in the "New Value" field, and click "Poke". 23. Reenter AB on each of the two lines in "objtmpl.cfg" previously edited in step 4, save and close.  

Issue The sensor in the BACnet controller is open or shorted and the value at the ENC shows "nan" but no fault is annunciated? Environment I/A Series G3 (Niagara) Cause If the analog object in question is being polled, by default only the "present value" is retrieved and therefore the "nan" is displayed but the status remains as ok.  A polled point can be made to retrieve the "statusFlag" data also by altering its "facets" as shown in the Resolution.  Resolution It is normal for the MNB controller analog input present value to change to "nan" when the sensor is shorted or open.  To annunciate a fault at the ENC: Add the "OutOfRangeAlarmExt" to the analog input object and program it to have the "fault" conditions annunciated.  If this object is defined to use COV notification the "present value" and "status flags" are reported by default.  Therefore,  the "nan" value is displayed and handled as a fault condition and annunciated.  However, if the analog object is being polled, by default only the "present value" is retrieved and therefore the "nan" is displayed but the status remains as ok.  A polled point can be made to retrieve the "statusFlag" data by altering its "facets".  With the object properties displayed on the Facets property click on >> and add a key as shown below.

Issue There are a number of TGML link or binding objects with the name ??128 in a folder in Vista workstation. They cannot be deleted. An error message "Could not delete the object. Attempt to delete an abstract object" appears. Product Line TAC Vista Environment TAC Vista Workstation 5.1.X Cause Sub-objects from a TGML graphic have not been removed from the database when the graphic has been deleted. This may be an indication that the database is corrupt. The error from Vista is "nonexisting object in request/advise/poke". Resolution It may be possible to delete the folder that the objects are in and thereby remove the sub-objects. Otherwise a backup of the Vista database (from a time before the objects appeared) will need to be restored.

Issue Vista hangs when navigating between TGML graphics. The screen dims, Vista workstation stops responding and an error message is displayed. In the event viewer the following event description is displayed: Description: Application: TACVistaExplorer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException Stack:    at java.lang.String.instancehelper_length(System.String)    at SE.Graphics.DOM.TGML.TgmlTextShape.setAttribute(System.String, System.String)    at SE.Graphics.DOM.TGML.TgmlBind.internalSetAttribute(System.String, System.String)    at SE.Graphics.DOM.TGML.TgmlBind.executeBind(System.Object, System.String, System.String, Int32)    at SE.Graphics.GraphicsServices.Dynamics.BindUpdater.executeBinds(SE.Graphics.GraphicsServices.GraphicsDocument)    at SE.Graphics.GraphicsServices.GraphicsDocument.UpdateBinds()    at SE.Graphics.Viewer.Windows.GDIPlus.GraphicsViewerControl.UpdateDynamics()    at TAC.Graphics.Windows.Vista.VistaGraphicsViewerControl.UpdateView()    at .CODEChildTgmlGraphics.UpdateView(CODEChildTgmlGraphics*)    at ._WinMainCRTStartup()   Environment Vista Workstation 5.1.6 TGML graphics Cause Workstation crashes when the TGML graphic updates it's content. It's suspected that at the same time as the TGML graphic is updating it's content, the graphic is changed, which means that it's not there anymore to receive the updates. Resolution Change the registry key HKEY_LOCAL_MACHINE\SOFTWARE\TAC\TAC Vista Workstation\5.1.X\MaxTGMLFPS  (max TGML frames per second) to 0.

Issue The Xenta 121-FC/HP controller will not build a terminal load when in unoccupied night setup mode. Environment ZBuilder 5.1.6 Xenta 121-FC Xenta 121-HP Cause The “Cooling interlocked to fan” setting prevents the unit from building cooling terminal load in unoccupied mode. Resolution This issue will be corrected in a future upgrade but for now this is a work around. Open ZBuilder Go to the Configuration tab > Control > Fan > Interlock Uncheck the box called “Cooling interlocked to fan”. Click Apply at the bottom of the window to update the settings in the controller.  

Issue Using a nciState Lon network variable to set operational modes of a MNL-800 application.   Needs to be able to allow these inputs to be set from the GUI. Environment MNL-800 application program Graphical User interface built with the I/A Series (Niagara) R2 system. Cause Desire to allow a user at the graphical head end of the BMS system to configure the individual bits of a LON state type network variable. Resolution The following discussion is based on the user interface engineering work being done within the WorkPlace Pro engineering tool of the I/A Series R2 system. The "DynamicCmd" control object found in the "conversion" folder of the Lonworks jar file can be linked to a SNVT_State type Lonworks network variable.  After linking the DynamicCmd control object to the desired controller shadow object nci type network variable, the DynamicCmd object learns the configuration information for the linked network variable.  The next step in configuring this object for this type of use is to set a name for each control bit element of the network variable.  These defined names are displayed when the GUI user clicks on the control point.  The user then selects the bit field name (from the displayed list) to command and then selects the binary value (True or False)to be written to that bit field. The following is an example of this control logic where the dynamic device is the MNL-800 controller with the network variable nci_cmd as the input constant and nvo_stat as an output state variable that allows the display of 16 internal bit state variables. This image shows the configured list of boolean bits that will be configurable via this DynamicCmd_1 object: When the GUI user selects this command object, the following field list is displayed: And after selecting the "Fan2-S/S" enable selection, the following popup window is displayed allowing the user to specify the boolean state for that command bit.  The value will be written to the controller when the [OK] button is clicked.

Issue How to use door alarm to trigger buzzer, including "Door Open Too Long" or "Door Forced"? Environment I/NET Cause This is a normal application for access control system, which is needed for some customers. Resolution The following steps need to be followed: Set Event Definition for the strike point. Choose the Event type to "Door Open Too Long" or "Door Forced". If the buzzer needs to be reset automatically after alarm disappears, another sequence should be triggered by “Door Normal” event. Define the Event Sequence to trigger buzzer point. After setting, when there is door alarm, the buzzer will be triggered.

Issue Considerations to make when using the economizer function in a Xenta 121. Environment Xenta 121-FC Xenta 121-HP Vista Workstation ZBuilder LonMaker NL220 Cause The economizer / outside air damper function of the Xenta 121 requires that certain considerations be made in order for it to work properly. This includes the wiring and display of a mixed air temperature sensor. Resolution Some things to consider when using the economizer in Xenta 121: The Xenta 121 application requires that a mixed air temperature sensor be used when the economizer mode is set up. This is to keep the application from bringing in too much cold air and freezing a coil. It is not possible to bypass this requirement in the software, but installing a ~1.8K ohm resistor in place of the mixed air temperature sensor will fulfill this requirement. The control method for the economizer can either be selected as Space temperature controlling against cooling setpoint or Mixed air controlling against setpoint value. Even if the space temperature method is selected the application still requires a mixed air temp sensor for safety lockout purposes. By default, the mixed air temperature is not displayed on the front end even if it is being used by the economizer. In order to display the mixed air temperature, navigate to the SNVT menu while on the Configuration tab of ZBuilder. Check the box at the bottom that says nvoGenericTemp. When the cursor is hovered over the text a tool tip pops up and indicates that this is used for displaying the mixed air temp. Next, select the I/O Setup tab and the Mixed Air Temperature point will appear and can now be dragged to the desired point assignment.

Issue In TreeTech, can a LCM be uploaded and downloaded? Environment LCM-84000 LCM-88000 Cause On a jobsite with a Network 8000 installation dating back to the 1990s and trying to do database backups. Resolution A networked LCM can be uploaded / downloaded, with TreeTech, via a serial connection to the GCM to which it is wired.  In situations where the GCM is not easily accessible (i.e. in a locked room), a serial connection to any one of the networked LCMs will provide access to the entire network as if it was the GCM.  Uploads/downloads of any networked LCM can be done via this serial connection too. A standalone LCM can be uploaded / downloaded, with TreeTech, using a direct serial connection.  Due to limitations in TreeTech, the standalone LCM must be configured as network 1 and address 1.

Issue MNL-V3 application configured with an external actuator of 390 seconds drive time shows an excessive setpoint deadband of almost 20% of control range. Environment MNL-V3 controller Cause Unknown - Issue has been reported to product management. Here is an application fragment showing the issue.  Note the 390 second drive time. Resolution Use the following application fragment in your application to eliminate the excessive >22%) deadband. Here is an application fragment showing a suggested workaround:

Issue Xenta Server Log Error contains the error line: Generic OS: Too Many Semaphores. 5326 02-Dec-2011 12:47:33 AM fatal  undef  httpdd           1      Generic OS: Too many semaphores.   (Error#:8202) Environment Xenta Server System Error Log Xenta 701, 711, 721, 731 Cause An Application in Xenta 700 consumes too many internal semaphores which cause a fatal error resulting in repeated coldstarts. Resolution Corrected in release 5.1.0 and documented on page 6 of TPA-MALR-08-0009.00. Upgrade to Vista version >5.1.0.

Issue Error indicates - Invalid or inaccessible view "pxEditor:pxEditor" when attempting to view px pages through I/A Series G3 embedded Workbench via browser. Environment I/A Series G3 ENC Cause Incorrect licensing or missing pxEditor module Resolution Look in the ENC's license file under the License Manager, and look for this line: <feature expiration="never" name="web" parts="ENC-520-WEB, ENC-WB" ui="true" ui.wb="true" ui.wb.admin="true"></feature> If any of the "ui" fields are "false", then you need to have the ENC licensed for Embedded Workbench. Purchase part number ENC-WB. In the Software Manager, look for a module called pxEditor. If pxEditor is not installed, install using the Commissioning Wizard.

Issue Instructions for finding the version of LonMaker and LNS Server on a machine. Environment Echelon LonMaker Cause Knowing the version of LonMaker and LNS are necessary for many troubleshooting techniques. Support representatives may ask you to have this information available in order to assist you better. Resolution Please follow these steps to find the version of LonMaker and LNS server on the machine: Open LonMaker, then pick and completely open a network. Choose the LonMaker menu in the menu bar, then about LonMaker: This is the about LonMaker window that should be shown. As you can see in this screen capture, LonMaker 3.1 is being run with the LNS server version 3.27.

Issue When doing Xenta server to Xenta server communication, via other projects network, a good troubleshooting technique is to determine if the two Xenta servers are truly communicating to one other over TCP-IP. This is possible via the online status of the imported Xenta server in the project tree. Environment Xenta 511, 527, 555, 701, 711, 721, 731, and 913 Cause Two Xenta servers are set up to communicate to one another, but they are not passing data properly. Troubleshooting step number one should be to determine if the two Xenta servers are online to each other on the TCP-IP Resolution To  check the online / offline status of a Xenta server follow these steps: Login to the web browser of the Xenta server that that is configured to receive data. Navigate to the project tree similar to the image below. 3.  Within the project tree, browse down to the Xenta servers and check the online status as shown here:

Issue Editing a Sigma object causes an error message. Environment Sigma Object edit 4.04 4.05 Error Cause The network connection to a remote Sigma client fails. Resolution This issue is caused by a network connection failure on a remote Sigma client, and although not caused by the local client, once it has occurred, it will affect the local client as well. The issue can be overcome by restarting the Sigma server. To correct this issue, it is recommended that the site be upgraded to Sigma 4.05 SEB or later. Sigma 4.05 SEB is available for download.

Issue Basic setup tips for the I/A Series G3 (Niagara) GCM driver, tacGcm. Environment ENC-520-2 ENC-410 I/A Series G3 GCM driver, tacGcm Network 8000 GCM (GCM-84000 series, GCM-86000 series) Cause This article is a work in progress. The intent is to provide information proven to be helpful, and add to it as we learn more. Resolution G3 GCM (tacGcm) driver setup basics: Serial communications between the UNC/ENC and GCM-84000 series must use GCM Port 2. The GCM-84000 series Port 1 is not buffered and cannot be used for network communications. The GCM participates on a network that includes 27 other GCMs. The recommendation is one UNC/ENC per GCM and to share data between the UNC/ENC devices with peer to peer links. The baud rate on the serial port is limited to 9600 and all communications (UNC/ENC, ASD, LCM, GCM to GCM, MMI, etc.) all share the same internal GCM communications buffers. It is this buffer on the GCM-84000 series that can easily be overwhelmed. Use Poll On Demand (POD) containers (G3 uses proxy points without history or alarm extensions) where possible. To optimize the use of the communications bandwidth, route alarms to the GCM serial port used by the GCM driver only as needed. Exceptions and Trend reports (and other reports generated by the GCM hardware) should never be routed to this port, as this data is not used and will utilize precious bandwidth. Only one HMI should be connected and active on the network.  Issues may occur when using the UNC / ENC GCM driver to poll a GCM network while simultaneously polling the same system with another HMI (e.g. Host, InVue, UltiVist, Signal, etc.). GCM-84000 series and ENC communications (tuning) Communications can greatly affect GCM operation and stability. As  indicated previously, all communications is process by a common communications buffer further affecting the GCM system RAM. Log into the GCM and review the current SYSRAM. It is recommended the GCM-84000 System RAM is stable and operating above 18K bytes. Low RAM will cause the GCM to appear to lockup, stop processing messages, and even reset. Review delta times for the blocks. Check the DETIM (Delta Time) attribute of a random sampling of blocks, especially those that have low update times assigned or involve device communications. Update times for blocks such as SNET, RNET, SGCM, RGCM, SLCM, and RLCM should especially be reviewed and increased as needed. These blocks default to 5 seconds and should be increased to a reasonable timeframe (e.g. 30 seconds). For other blocks, if the DETIM value is greater than the UPTIM value by more than a couple of seconds, the system may potentially be experiencing system throughput problems. This should be monitored as changes are made to the system to determine if it improves. Adjustment of update times should also be done in the other GCMs that may be requesting data via global type blocks. If the RAM has not stabilized and is below 18K bytes, decrease the GCM driver maxMessages from 5 towards 3 or 2. This controls the number of messages requested simultaneously from the ENC Note: DETIM block output is normally hidden. In order to see it, login to the GCM as user = BCFLD, password changes every day. Contact PSS - Rockford for a current password. Verify  that the "Write on Start", "Write on Up", and "Write on Enabled" are all set = false in the default Tuning Policy of the GCM Network.