Building Automation Knowledge Base

Issue Is there a way to allow users station access, through a browser or JDE, in Niagara R2, without having to first sign-on without a user name and password? Environment Niagara R2 Cause Enable "Public Access" feature to bypass sign on.  Resolution Yes. Starting with Niagara release 2.3, a “public access” feature was added. The public access feature allows for configuration of a station to permit GxPage access without being prompted to enter a user name and password. When this feature is used, the “Sign On” dialog box is skipped and the GxPage is displayed as if user was already signed on. See “Niagara Web Solutions Guide” for detailed setup information.

Issue The Momentary Start / Stop (SS) object in a MNB controller is not working. The OutStrt output property remains ON and does not pulse off. Product Line TAC IA Series Environment MNB controllers Cause Application programming Resolution The OnPulse input property is set higher than the required minimum of 2 seconds.  In order for the logical outputs to work (OutStrt & OutStp), physical hardware tags must be assigned to the physical outputs (AddrStrt & AddrStp).  This is required when using the Momentary SS object in any MNB controller. The following logic can be used in place of the Momentary SS object to generate an equivalent OnPulse.  

Issue TS-7222 and TS-6722 30K thermistor sensor (no 11K shunt) resistance table Environment TS-7222 TS-6722 Cause Specification on the sensing element. Resolution   Temp (°C) Temp (°F) Ohms    25.0°     77.0°    30,000    26.0°     78.8°    28,806    27.0°     80.6°    27,678    28.0°     82.4°    26,598    29.0°     84.2°    25,566    30.0°     86.0°    24,582    31.0°     87.8°    23,637    32.0°     89.6°    22,737    33.0°     91.4°    21,873    34.0°     93.2°    21,048    35.0°     95.0°    20,256    36.0°     96.8°    19,500    37.0°     98.6°    18,774    38.0°     100.4°    18,081    39.0°     102.2°    17,415    40.0°     104.0°    16,776    41.0°     105.8°    16,167    42.0°     107.6°    15,582    43.0°     109.4°    15,021    44.0°     111.2°    14,481    45.0°     113.0°    13,965    46.0°     114.8°    13,470    47.0°     116.6°    12,993    48.0°     118.4°    12,537    49.0°     120.2°    12,099    50.0°     122.0°    11,679    51.0°     123.8°    11,274    52.0°     125.6°    10,887    53.0°     127.4°    10,515    54.0°     129.2°    10,155    55.0°     131.0°    9,813    56.0°     132.8°    9,480    57.0°     134.6°    9,162    58.0°     136.4°    8,856    59.0°     138.2°    8,562    60.0°     140.0°    8,280    61.0°     141.8°    8,007    62.0°     143.6°    7,746    63.0°     145.4°    7,494    64.0°     147.2°    7,251    65.0°     149.0°    7,017    66.0°     150.8°    6,792    67.0°     152.6°    6,573    68.0°     154.4°    6,366    69.0°     156.2°    6,165    70.0°     158.0°    5,970    71.0°     159.8°    5,784    72.0°     161.6°    5,604    73.0°     163.4°    5,430    74.0°     165.2°    5,262    75.0°     167.0°    5,100    76.0°     168.8°    4,944    77.0°     170.6°    4,794    78.0°     172.4°    4,650    79.0°     174.2°    4,509    80.0°     176.0°    4,374    81.0°     177.8°    4,242    82.0°     179.6°    4,116    83.0°     181.4°    3,996    84.0°     183.2°    3,879    85.0°     185.0°    3,765    86.0°     186.8°    3,654    87.0°     188.6°    3,549    88.0°     190.4°    3,447    89.0°     192.2°    3,348    90.0°     194.0°    3,252    91.0°     195.8°    3,159    92.0°     197.6°    3,069    93.0°     199.4°    2,982    94.0°     201.2°    2,898    95.0°     203.0°    2,817    96.0°     204.8°    2,739    97.0°     206.6°    2,661    98.0°     208.4°    2,589    99.0°     210.2°    2,517    100.0°     212.0°    2,448    101.0°     213.8°    2,382    102.0°     215.6°    2,319    103.0°     217.4°    2,256    104.0°     219.2°    2,196    105.0°     221.0°    2,138    106.0°     222.8°    2,081    107.0°     224.6°    2,026    108.0°     226.4°    1,973    109.0°     228.2°    1,921    110.0°     230.0°    1,871    111.0°     231.8°    1,822    112.0°     233.6°    1,775    113.0°     235.4°    1,729    114.0°     237.2°    1,685    115.0°     239.0°    1,642    116.0°     240.8°    1,600    117.0°     242.6°    1,560    118.0°     244.4°    1,520    119.0°     246.2°    1,482    120.0°     248.0°    1,445    121.0°     249.8°    1,409 

Issue TS-5722 and TS-6722 30 K thermistor sensors with 11 K shunt resistance table Environment TS-5722 Electronic Remote Temperature Sensors TS-6722 Electronic Remote Temperature Sensors Cause Specification on the sensing element. Resolution Temp (°C) Temp (°F) Ohms (11K shunt)    25.0°     77.0°   8,049   26.0°     78.8°   7,960   27.0°     80.6°   7,872   28.0°     82.4°   7,782   29.0°     84.2°   7,691   30.0°     86.0°   7,599   31.0°     87.8°   7,507   32.0°     89.6°   7,413   33.0°     91.4°   7,319   34.0°     93.2°   7,224   35.0°     95.0°   7,129   36.0°     96.8°   7,033   37.0°     98.6°   6,936   38.0°     100.4°   6,839   39.0°     102.2°   6,742   40.0°     104.0°   6,644   41.0°     105.8°   6,546   42.0°     107.6°   6,448   43.0°     109.4°   6,350   44.0°     111.2°   6,251   45.0°     113.0°   6,153   46.0°     114.8°   6,055   47.0°     116.6°   5,957   48.0°     118.4°   5,859   49.0°     120.2°   5,762   50.0°     122.0°   5,665   51.0°     123.8°   5,568   52.0°     125.6°   5,472   53.0°     127.4°   5,376   54.0°     129.2°   5,280   55.0°     131.0°   5,186   56.0°     132.8°   5,092   57.0°     134.6°   4,999   58.0°     136.4°   4,906   59.0°     138.2°   4,815   60.0°     140.0°   4,724   61.0°     141.8°   4,634   62.0°     143.6°   4,545   63.0°     145.4°   4,457   64.0°     147.2°   4,370   65.0°     149.0°   4,284   66.0°     150.8°   4,199   67.0°     152.6°   4,114   68.0°     154.4°   4,032   69.0°     156.2°   3,951   70.0°     158.0°   3,870   71.0°     159.8°   3,791   72.0°     161.6°   3,713   73.0°     163.4°   3,635   74.0°     165.2°   3,559   75.0°     167.0°   3,484   76.0°     168.8°   3,411   77.0°     170.6°   3,339   78.0°     172.4°   3,268   79.0°     174.2°   3,198   80.0°     176.0°   3,130   81.0°     177.8°   3,061   82.0°     179.6°   2,995   83.0°     181.4°   2,931   84.0°     183.2°   2,868   85.0°     185.0°   2,805   86.0°     186.8°   2,743   87.0°     188.6°   2,683   88.0°     190.4°   2,625   89.0°     192.2°   2,567   90.0°     194.0°   2,510   91.0°     195.8°   2,454   92.0°     197.6°   2,400   93.0°     199.4°   2,346   94.0°     201.2°   2,294   95.0°     203.0°   2,243   96.0°     204.8°   2,193   97.0°     206.6°   2,143   98.0°     208.4°   2,096   99.0°     210.2°   2,048   100.0°     212.0°   2,002   101.0°     213.8°   1,958   102.0°     215.6°   1,915   103.0°     217.4°   1,872   104.0°     219.2°   1,831   105.0°     221.0°   1,790   106.0°     222.8°   1,750   107.0°     224.6°   1,711   108.0°     226.4°   1,673   109.0°     228.2°   1,635   110.0°     230.0°   1,599   111.0°     231.8°   1,563   112.0°     233.6°   1,528   113.0°     235.4°   1,494   114.0°     237.2°   1,461   115.0°     239.0°   1,429   116.0°     240.8°   1,397   117.0°     242.6°   1,366   118.0°     244.4°   1,336   119.0°     246.2°   1,306   120.0°     248.0°   1,278   121.0°     249.8°   1,249

Issue No Values being displayed on an MR Environment I/NET MR Micro Regulator Controllers Cause Quick Poll not enabled. Resolution Connect to the controller. Select Edit/Controller/MCU Configuration. Select Station and check the QP (Quick Poll) boxes for the addresses with this issue. Close out the Editors and restart I/Net again.

Issue After adding an ASD driver to a Niagara G3 station off-line, there are no device objects in the tacASD palette. Environment Niagara G3 Cause Not documented Resolution After adding the ASDNetwork to a station, right click on the ASDNetwork and use the ASD Device Manager to add devices.  With the ASD Device Manager open click the "NEW" button at the bottom of the screen and a "NEW" window will be displayed to define the device type, number of devices to add and a starting address.

Issue When running Sigma 4.05 with a backup from a previous release of Sigma, the DeviceCnf.rec file is being over-written with a default DeviceCnf.rec file Environment Sigma 4.05 Cause The DeviceCnf.rec and gencnf.rec files use a different format in Sigma 4.05 than previous releases. Resolution When Sigma 4.05 checks these files and finds there not correctly formatted it automatically replaces the DeviceCnf.rec file with a default or blank file. Use the file C:\sigma\bin\SigUpgrade.exe to upgrade your data files to the correct formatting for Sigma version 4.05.

Issue Is the communications card in a UNC 126 the same as the NIU type 1? Environment UNC 126 outstation NIU Cause Need to replace the communications card of the UNC 126 with an NIU type 1. Resolution Yes, the communications card of the UNC 126 outstation can be replaced using the communications card from an NIU type 1.

Issue AMT not showing First Name and Last Name information in the Transactions Window   Environment I/NET running in a Windows Environment Xenta Server 527 / 731 Cause The Host PC is not listed as the SQL Host Number in the Xenta 527 / 731. Resolution In the configuration of the Xenta Router the Host PC has the default value of Zero. To fix this you must: Connect the Xenta 731/ 527 Server 24 VAC power. Refer to the TAC Xenta 527 Installation Instructions (0FL-3956). Connect a PC to the Xenta Serves. Attach a serial cable from the computer’s COM port to the RS-232 B port on the front of the Xenta Servers. Refer to TAC Xenta 511/527/911/913 Handbook (0-004-7870) for complete instructions. Set the Xenta Server communication parameters. Start a Hyper Terminal Session on your PC, once the cable is connected it will display the default information on the Xenta. Note: The factory default login/password is root/root, Hyperterminal into the Xenta and login with appropriate credentials. From the dsh/> prompt type inethost Hit the ENTER key sixteen times to get to the SQL Host Number. It’s default is 0 and should be changed to the HOST NUMBER for the Host PC. The host PC number can be found in the I/O Server at the top right hand side in the TCP/IP setting box. Log out and be sure to restart the Xenta Server for settings to change.

Issue After installation of G3 Workbench version 3.4.57 or 3.5.25, the Software Manager on the Localhost may display that the sun-jre-win-x86 VM module is out of date: Environment Niagara G3 version 3.4.57 or 3.5.25 Sun JRE VM Module Cause While this is not a fatal error condition, the module can be updated. NOTE: if the installed version is 3.5.25, replace path references to "3.4.57" in the paths with "3.5.25" Resolution Shut down Workbench Open Windows Explorer, and navigate to the C:\niagara\niagara-3.4.57 directory Rename the jre folder to jre.old Now, navigate to the C:\niagara\niagara-3.4.57\sw\1.6.0.20 directory. Using WinZip, open the sun-jre-win-x86.dist file (or the sun-jre-win-x64.dist file if using the 64-bit version of Workbench). Select all of the folders in the archive, and extract them to the C:\niagara\niagara-3.4.57 directory (see below). Make sure that the “Use folder names” (or equivalent) box is checked. After the extraction, a new jre folder is created. Run the Platform Daemon (Start > Programs > Enterprise Network Server 3.4.57 > Install Platform Daemon) Open Workbench, and then open the Software Manager in the Platform. The Sun VM will now show "Up to Date"  

Issue In Niagara G3, how can an objects value be displayed in a graphic and not its status? Environment Niagara G3 Cause Default BoundLabel properties of the object are set to display the value and status. It must be adjusted to display only the value. Resolution In the BoundLabel properties of the object, the default text format is %.% This displays the value and the status of the object. To display just the object's value, edit the format to %out.value% The object will then display only the present value in the graphic.

Issue Question on what to set the virtual memory to on a Continuum Workstation PC Product Line Andover Continuum Environment Windows XP Cause Question on what to set the virtual memory to on a Continuum Workstation PC Resolution Virtual Memory Requirements The virtual memory "Initial size (MB)" setting on your workstation PC should be set to a minimum of 1 GB. To make this change: Go to Start, Settings, Control Panel. In the Control Panel, double click System. The System Properties menu, shown on the next page, appears. Click the Advanced tab and click Settings in the Performance box. The Performance Options menu appears. Click the Advanced tab. In the Virtual Memory box, click on Change. When the Virtual Memory dialog appears, fill in the desired paging file memory size (initial and Maximum). Click OK as you back out of the dialogs.

Issue   The requested information is not available from the device. (Subsystem: NS, #28) Product Line TAC Vista Environment LonMaker 3.2 (Turbo) Cause The requested information is not available from an application node. For example, transceiver status, SI/SD data, and the network variable names are not always stored in the node. This error is a known issue with LonMaker 3.2 (Turbo). Resolution Navigate to http://www.echelon.com/support A username and password are required to access the download section, but it is free to register. Download LonMaker Turbo Service Pack 2 Install LonMaker Turbo Service Pack 2.

Issue Connecting to a Morpho Sigma Reader and getting an error using V-Sation from Schneider Electric Environment Continuum V 1.94 and above Morpho Sigma Reader BioBridge Cause V-Sation is not compatible with the Morpho Sigma Series Readers at this time. The Continuum Integration was done by  SafranMorpho and not by Schneider Electric using their Software called BioBridge and Secure Admin for configuration when in Legacy Mode. Resolution This application is not supported by Schneder Electric and all questions should be directed to SafranMorpho Tech Support.

Issue BACnet values drop out occasionally BACnet devices update slowly, or miss updates Xenta Server must be power cycled to restore communication Environment Xenta 913 BACnet Cause BACnet physical layer best known practices were not followed. Resolution The following must be verified on your installation. The physical BACnet layer must be wired as specified to have the wire grounded at each BACnet card and at the 913. The physical layer must be terminated with end of line terminators of the type specified in the documentation. It is recommended a BACnet segment should not exceed more than 15 per segment. It is recommended BACnet cards must be sequentially addressed leaving the 913 as Master node address 1. The 913 Xbuilder project and BACnet cards must reflect a "max master" setting of the last master address on the BACnet segment. A default baud rate of 38.4k may be attempted but it is safe to slow the network to 19.2k if you experience communication issues.

Issue When update Vista database through System Plug-in got error message saying “Update Vista database failed”. Open Workstation, in the alarm window, there is error message saying “unable to request license”. Environment CIRCON Network Integrator or other LNS network builder, customer license file Vista 5 Cause Vista cannot recognize the LNS server license. This happens when you use some LNS network builder besides LonMaker or NL-220, and you are using a purchased license file instead of a demo license file or an engineering dongle. Resolution If you get the “Update Vista database failed” error message in system plug in. Make sure you have done the group binding or redo the group binding. If the issue still exists, check the system plug-in output window and see if there is any error message before the “update vista database failed” message. If not, open TAC Vista Workstation and check the alarm window. If you see the error message says “unable to request license”, this means TAC Vista server cannot file the LNS server license. The TAC Vista demo license or an engineering dongle has a full version of all licenses which includes the LNS server license. You will see a line below in your demo license file: FEATURE Vista.Server.LNS taclic 5.1 31-oct-2010 uncounted HOSTID=DEMO However, the purchased customer license file does not have “Vista.Server.LNS” license included. The solution to this issue is either rebuilding the LNS network in LonMaker or NL-220, or purchasing an engineering dongle or using the demo license file.

Issue Remote Serial Port  Driver, RSPD, is not working. Environment Windows 7 Windows 2008 Cause Security in OS . Resolution Install and start the program as administrator. Right click on the program and select run as administrator.

Issue Xenta 121-FC SNVTs show up in LonMaker or NL220 but are missing in Vista Environment Xenta 121-FC LonMaker/NL220 Vista Workstation 4.5 System Plug-in Cause A problem has occurred with the import of the controller into the Vista database. Resolution In the Vista System Plug in, delete the controller from the TAC Network.  In the LNS network tab, right click on the controller and disable it from being updated in the TAC Network. Update the TAC Vista Database Refresh the Folder View in Vista Workstation.  Verify that the controller has been removed from Vista. In the Vista System Plug in, re-enable the controller to be updated in the TAC Network Move it back into its former location in the TAC Network Update the Vista Database a second time. Go to Vista Workstation, verify that the controller has returned and values are being properly displayed.

Issue An attempt has been made to create a database that already exists. The database path should be changed to point to a different location. Environment LonMaker Vista LNS   Cause Can not defrag a database in LonMaker.  While opening an LNS database or explicitly defragmenting a database using the CompactDb method of the Network and ObjectServer objects or the Defragment Database function in LonMaker it is possible to receive: Error opening LCA database. The database already exists. (Subsystem: LNS, #21)[DB #-2035]. The error indicates that a prior attempt to defragment the database was not complete. This is likely to happen when an application is killed using Task Manager during the defrag process. Resolution To resolve the error, first delete the objects.reo file from the database directory and defragment again. Larger databases may take minutes to defragment and may leave a single threaded application unresponsive during the process. Database directory by default is c:\lm\db\< NetworkName > Therefore, if your network name was "MyNetwork," then look for c:\lm\db\MyNetwork\objects.reo Do not kill the application. It is possible to use the Task Manager as an indicator. While defragmenting, watch the CPU utilization indicator to identify completion of the defrag operation if the software performing this call does not return a completion message to your screen. http://www.echelon.com/support/kb/solution.asp?solutionID=109

Issue There is no communication with the LNS Server. Environment NL220 Vista LNS Cause LNS server was shut down on the remote server prior to closing the drawing.  Resolution Close the drawing prior to shutting down the LNS server