Building Automation Knowledge Base

Issue The Sigma help file cannot be displayed. Environment Sigma 4.05 or greater Windows 7 Internet Explorer 8 Internet Explorer 9 Compatibility View Cause Sigma now displays its help file though the web browser, but it is not displayed on IE8 and IE9 systems.. Resolution Compatibility View. When a web site says that it supports modern web standards, Internet Explorer 8 respects that and displays the site using its most standards compliant mechanism. In the majority of cases, this works correctly. However, every once in a while, a page that says “display me using modern standards” really means “display me like Internet Explorer 7 used to display modern standards pages”. This is where Compatibility View comes in. There are a number of changes in Internet explorer 8, but the main points to know are – Sites on the public internet still display in IE8 Standards Mode by default. Switching in and out of Compatibility View (between IE7 and IE8 modes) happens on the fly without a browser restart. Compatibility View is domain specific. A new UI button located in the navigation bar just to the right of the address bar (next to the refresh button) controls the Compatibility View feature. From the Sigma help file point of view, if the help file does not display, change the compatibility mode. An alternative to manually changing the mode is a new entry in the ‘Tools’ menu which allows for advanced configuration of the feature.

Issue Sigma Graphics window freezes. Error message when logging off from Sigma : Sigma must be shutdown by using the Operators Panel Only. Environment Sigma 4.05 SEB Sigma 4.06 Cause When a User logs off from Sigma, an dialogue box appears. If not accepted or "OK" then the dialogue box disappears and the graphic window freezes. Any further attempts to "OK" the dialogue box when logging on or logging off does not have any effect. Resolution In Sigma: Go to: System Setup > General > Graphics The startup graphic has been set to 0 (none). Change the startup graphic to any number other than 0, preferably to an overview graphic. If one does not exist, then create a graphic.

Issue Is it possible to specify a TCP port for the communication between Vista and the SQL server? Environment Vista 5.1.7 SQL server 2008 Cause  The default SQL Server port is 1433, and client ports are assigned a random value between 1024 and 5000.   Resolution It is possible to specify which port that should be used by the SQL server. Start the SQL Configuration Manager Expand SQL Server Network Configuration Click on Protocols "Instancename" Click on TCP/IP and open the tab IP addresses Go to the bottom fields "IP All" take away everything in the field  "TCP Dynamic port" Specify a port which SQL should use in "TCP Port" Now open the Vista server setup To specify which port Vista should use when communicating with the SQL server add a comma after the name of the SQL server and then enter the port number, in this case 27035 which also was specified in the SQL server. 

Issue Creating a shape and then filling it with colour. Environment Sigma Graphics Combine Fill shape Cause Customer wants to design a shape and then fill it with colour. Resolution A shape created from a number of lines which have been combined into an object, does not allow you to fill it with colour. A possible way around for this problem is to use the Polygon tool, this is more difficult to use, but when the shape is finished, "Connect Closed" can be selected, and the shape can then be filled. The shape is created as follows; Create the required shape as required. Select the Polygon tool and click in each corner to copy your original shape. Press the "Escape" key to terminate the Polygon function, the shape will disappear. Save the graphic, close and then reopen it. Delete the original shape. Highlight the new shape and select "Connect closed" from the RH menu. Using the RH menu again, select "Shape fill" and choose the required fill colour. The completed shape.

Issue When trying to download application and parameters in the TAC Vista System Plug-In, the message in the Output pane says 0 device(s) selected for download. The download window in the system plug-in does not open. Environment Vista NL220 LonMaker System Plug-in Cause When the system plug-in displays zero devices selected for download, it is seeing the Xenta controller as a LonWorks device. There are a couple of possible causes for this issue. The neuron ID set for this device may be wrong. The correct device template was not browsed in when the node was created in NL220/LonMaker. Resolution First check the neuron ID of the controller and verify that it is correct. If it is correct, follow these steps. In the System Plug-in, on the TAC Network side, select the Xenta controller that is not being recognized and delete it. Take note of which group the controller belonged too. Update the TAC network.  The previously deleted controller will be added back into a newly created group. Move the controller out of this new group to the correct, desired group. Delete the empty group and update Vista database. Now select the controller and download application and parameters.

Issue Unable to move graphics to a different drive. Environment I/NET Graphics Editor Cause When using the full path for links between I/NET graphics pages, the exact path must be preserved in order for the link to work.  If the graphics are every moved to a new PC or new location, the exact graphic path, including the drive letter must remain unchanged.  A simple process can prevent this extra work from being required, and allow graphics to be moved freely between machines and hard drives. Resolution Setup - Create a root graphics folder.  Label it "Graphics" or anything you like. Create a single layer of sub-folders to help you organize graphics. (i.e. "Floor Plans" "Building1" "bmp images" etc.) If you are working on an existing system, you obviously cannot move everything to a new location, but at least try to establish a root graphics folder moving forward. Linking Create a new graphics page called Home.gpg in the Graphics folder Edit Home.gpg Create a new link between pages by using the Page Marker tool and clicking Click on the "Select" button next to Destination page to choose the page you wish to link to A default absolute path will show up. For this example I'll link to C:\Program Files\INET Seven\Graphics\floorplan.gpg To use relative linking I have to know that both the graphic I am editing and the one I am liking to are in the same folder C:\Program Files\INET Seven\Graphics.  So in this case, I can change the link from "C:\Program Files\INET Seven\Graphicsfloorplan.gpg" to "floorplan.gpg" If I wanted to link to a page in sub-folder, for example C:\Program Files\INET Seven\Graphics\building1\VAVs.gpg, I would just change the link to "building1\VAVs.gpg" In order to link from VAVs.pgp to Home.pgp, I would have to edit the VAVs.gpg and use link with the text ..\home.gpg.  The ..\ tells the computer to look up one directory. In order to link from C:\Program Files\INET Seven\Graphics\building1\VAVs.gpg to C:\Program Files\INET Seven\Graphics\building2\AHUs.gpg, I would have to use the link "..\building2\AHUs.gpg". This tells the computer to look up one directory, then go into the building2 folder and find the AHUs.gpg Once all graphics are set to use relative linking instead of absolute, only the self contained folder structure within the graphic folder has to stay the same. Everything can be zipped and moved to any other drive.

Issue Inactivated alarm messages are received by recipients, the message will be similar to that shown below. Environment Sigma RAM Remote Alarm Manager Inactivated Cause Sigma alarms are not acknowledged in the Sigma Alarm Manager. Resolution These aren't nuisance messages, they are caused because Sigma alarms have not been acknowledged via the Sigma alarm manager. The Inactivation messages occur after 3 days (default setting), and this happens because a Sigma alarm has not been acknowledged. You cannot stop this message, but you can extend the time before the alarm is removed from the RAM active alarm list. Please see attached screen shot. This screen shot is taken from the Sigma R4 interface configuration, set to the number of days required.  

Issue Analogue Input card configuration jumpers. Environment AI Analogue Input Configuration links Jumpers Cause What is the correct configuration of the jumpers? Resolution The jumper configuration allows the use of three different inputs, these are Resistance, Voltage and Current. The screen shot shows the configuration jumps and explains their use.  

Issue When using I/A MNL800 controllers in Vista classic network (without using LNS database), an issue will happen when commissioning and downloading the controller: Local Network Management Failure, Info: nci_Location. The xif file has been updated to the newest version of the WPT program. Environment WPT version higher than 5.7.2 Vista 5.1.6 Cause The possible cause is that the WPT version is too high for Vista classic network to integrate. Resolution Firstly it isn't recommended to use I/A LonWorks controllers in Vista system. And there is no specific compatible matrix for Vista and WPT. Currently the proved version of WPT that can be used with Vista 5.1.6 is 5.7.2. The version higher than this will has this issue. So the only solution is to use the xif file generated by WPT 5.7.2 in Vista classic network.

Issue Start TAC Vista Comm. Log Product Line TAC Vista Environment TAC Vista Server Cause Sometimes to solve a problem we need to record the communication to and from TAC Vista. Resolution Start the TAC Vista server Open workstation and close all graphics, charts, etc., that are not needed to reduce traffic and make the log easier to read. Log in to TAC Vista Server. Go to Log > Comm. Log Set Physical layer to active Click Ok  The log will be created in the $log folder in the TAC Vista db.

Issue Getting error "Cannot find distribution platform" when attempting to start new I/A Series R2 Enterprise Server software. Environment I/A Series R2 Enterprise Server and WorkPlace Pro Cause The I/A Series R2 Enterprise Server software was installed without selecting the Program Files checkbox within the Select Modules dialog box. The Program Files include the distribution files required by the software. Resolution During the installation process, click the check box next to each module required or click Select All to select all modules at once.  At a minimum, the Program Files check box must be selected to install the core Niagara modules.   Reference the Installation Instructions provided with the Niagara CD or software zip.

Issue Naming a point in Menta results in a pop up error Warning Syntax error Product Line TAC Vista Environment Menta Cause Special characters are not permitted in the names of Menta signals. Resolution Remove all of the following characters from the Menta signal name: space . period, ? question mark - dash (hyphen) !, @, #, $, %, ^, &, *, (, ) \ backslash denotes the Menta module name separated from the Menta signal name. One is permitted, the second will cause a syntax error The best rule to go by is to use nothing but alphanumeric characters and (_) underscores in Menta naming conventions.

Issue Definition clarifications for Thermistor Type in Technical Reference Guide for StruxureWare Building Operation Environment StruxureWare Building Operation site with Thermistor temp sensors Cause In the image below of the technical reference guide for StruxureWare Building Operation on page 3164 the accuracy of the supported thermistors seems to be difficult to decipher or at least very hard to figure out what accuracy goes to what thermistor type. The issue is the input specifications does not clearly separate the Thermistor type (Continuum, I/NET, etc) with the accuracy. If there was a line or something to separate the accuracy definitions from each other that would help. What defines one set of values from the next? The ending of the parenthesis defines the end of the information for each sensor type, but this is not clear.  Resolution A defect has been recorded and it has been requested that in the next release of the Technical Reference Guide for StruxureWare Building Operation, this be corrected and offer clarification as to the accuracy with a Hard Return. The lines are actually separated by the end of the parenthesis, but this is difficult to decipher.  

Issue Get "Type error: cannot call method "toFixed" of null" error message when opening a TGML graphic, upgraded to Vista 5.1.7   A TGML script has stopped working after upgrading to Vista 5.1.7 Environment TAC Vista Workstation 5.1.7 TGML editor 5.1.7 219 Cause Javascript method toFixed can only be used with numerical values. The TGML engine in TGML 5.1.7 is stricter than the older versions, so an upgraded script may have worked in previous versions. Resolution An example when using convertCustom element. Original script: function convert(value) { value = value.toFixed(2); return value; } should be: function convert(value) { value = Number(value).toFixed(2); return value; }  

Issue Digital Output interface module wiring connections.  Environment Sigma X96 696 796 Controllers Digital Outputs Command Modules Digital Output modules Cause Unsure of wiring details. Resolution UNC 696/796 controllers provide digital outputs via "Digital Output Interface modules". These modules are connected to the controller either using hard wiring or via a ribbon cable. The UNC 796 is most likely to be connected using "hard wiring", whilst the UNC696 may use a combination of the two. UNC696 This controller is contained in a robust metal case and is commonly used in a stand alone situation. The case is sufficiently large to incorporate two "Digital Output Interface modules", these are located internally, one on each side. A ribbon cable is used to connect each module to the motherboard. These modules are associated with the I/O slot 1, I/O's 1-8 being the left module and 9-16 being the right.. These modules can only be used with slot 1, if additional modules are required, they must be hard wired. UNC 796 Digital Output Interface modules are normally hard wired to the controller slots, ribbon cables can be used, but seldom are.  

Issue Cannot connect MD20B-230 actuator to MBX4451 valve, using a 914-1071-000 linkage. Product Line Field Devices Environment MD Actuator MB valve MBX valve Linkage Cause The existing documentation is very unclear and shows the wrong bracket. Resolution The issue arises initially in that a different bracket is shown in the current documentation. The second issue is that there is a circlip on the back of the actuator which must be positioned before fitting the bracket. Below is a picture showing the correctly circlip and bracket. Please take note of the circlip position. Revised documentation will be available in due course.

Issue Where are communications modules located? Environment Upgrade NIU Type 3 Comms modules Cause There are three module locations available, how do these relate to the port numbers. Resolution The top location is associated with port 1 and this port is normally used for connection to the sub-lan. The middle location is associated with port 5 and the port is normally used as the connection to the main network. The bottom location is associated with port 6 and the port is used as the connection to the backup network. In the screen shot below, the DNN (Ex-NIU) has an ARCnet module fitted into port 1 (Top). An Ethernet module is fitted into port 5 (Middle), and the lower location port 6 is not used.

Issue AMT Event Messages Environment I/NET Seven AMT Cause AMT messages are used to diagnose certain system problems. This table can be used to interpret data when an alarm comes in, or needs to be acknowledged, the user can easily reference what is going on. This table was taken from TCON300.  This TCON is updated regularly, so to view the version which works best with your release of I/NET, select START>All Programs>I/NET>Technical Reference Guide. Look on page 3-26. Resolution Note: Most AMT Message "Event Types" are appended with the I/NET Users initials as defined in the Host Passwords.  It is also possible to see the "root" user name appear here, this is when you are using a Xenta Server that is controlling points in the I/NET system.  For example you may see the term "Control root" under the Event Type column.  This indicates that the associate I/NET point has been control by a Xenta Server.   Use this table to interpret AMT messages  

Issue Site has 75 Microsmart controllers each with a Mode Control Type 21 point doing unoccupied control of the connected fan system.  The customer has asked that the unoccupied high and low temperature setpoints be made available to adjust from a Niagara R2 graphic screen. The setpoints are assigned to a PVALU element in the point's configuration (see below). Environment Niagara R2 with Microsmart Driver Microsmart controllers (all) Cause Request for setpoint control during unoccupied hours Resolution Create the shadow object for the Mode Control Point using the Niagara Point List Manager. Move it from the Temp folder to a new container created under the controller shadow object (labeled 'Testing' in the figures below). Add two MsElement objects from the ibsMs jar file - one for the Scheduled Off High Limit and the other for the Scheduled Off Low Limit.  Note:  The MsElement objects can be created directly under the Mode Control point's shadow object or in a container (as shown in the figures below). On the config tab for each MsElement object, modify the parameters highlighted by the red box in the figures below. Link them to a graphic and a right-click will present the user with the commandString field ('New value:' was used in the figures below).

Issue How can the default graphic for the Monitor Screens be modified in SIGNAL? Environment SIGNAL (all versions) Cause A re-installation of SIGNAL from floppy restores a default graphic called _MAINMAP.SSF when clicking on the Monitor Screens. Resolution Sign onto SIGNAL with administrative privileges and click on the Edit drop-down menu.  Select Edit Button. The mouse changes to a hand with an index finger pointer.  Select the Monitor button.  The pop-up below will appear:   Change the filename _MAINMAP.SSF to the desired ssf file and click Save/Done.