Building Automation Knowledge Base

Issue How to modify the setting "initString" to change the number of rings for auto answer for a Niagara R2 UNC-520 internal modem Environment Niagara R2 UNC-520 Cause The Ring to Auto-Answer can't be change. Resolution The UNC-520 is shipped with factory defaults to pick up on the first ring. The internal modem does not answer, a service answers the call.  As a result, the "Ring to Auto-Answer" parameter is NON configurable.

Issue In the process of upgrading a Niagara G3 ENC from version 3.0  to version 3.1, the station fails to start due to an invalid license. Environment Niagara G3 ENC Cause In order to complete an upgrade to version 3.1, it is necessary to obtain a 3.1 license. Resolution Ensure that a new license is available to install in the ENC before upgrading. Once the ENC has been upgraded it cannot be downgraded back to 3.0 unless it is done by the factory.  If a new 3.1 license has not been installed, the ENC will be inoperable until it is installed.

Issue Can a Niagara R2 UNC be integrated with Microsoft's Active Directory (LDAP protocol) so IT departments can change the UNC password every 60 days? Environment Niagara R2 UNC Microsoft Active Directory Cause LDAP protocol is not supported on the Niagara R2 Resolution Unfortunately, Niagara R2 cannot integrate with Microsoft's Active Directory or the LDAP protocol. It is available with Niagara G3.

Issue A report has been copied from one PC to another and it is not working. Environment I/NET Seven Reports Cause This occurs because the linking for the report has been lost. Resolution Rename the report with the problem Copy the original report from the I/NET CD Paste it into I/NET Seven, Reports Right Click on the report and verify that it is not set for read only Run the report again  

Issue SIGNAL (any version) is installed on new computer hardware that has higher video resolutions. Now, the Monitor program's graphics are not aligned. Environment SIGNAL (all version) PC with high resolution graphic card Cause The new PC screen resolution is not set at the recommended resolution. Resolution All versions of SIGNAL support two video resolutions: 640 x 480, and 800 x 600. Shutdown SIGNAL and use Windows to modify the computer's video resolution to one of these two settings.

Issue What are the data sharing differences between the Wireless Infinet and the Hard Wired Infinet? Environment Wireless Infinet Hard Wired Infinet Cause Information on what is like to implement a wireless Infinet bus verse wired Infinet bus. Resolution Import/Export differences between a Wireless Infinet bus and a Wired Infinet Bus Below outlines what the differences are between a Wireless Infinet bus and a Wired Infinet bus when it comes to imported and exported values. Note: A point that is flagged as Exported will send it’s value out on any bus, wired or wireless, only when the point value changes. If the point value keeps changing rapidly, then every time the value changes it will be sent out on the bus. If the point value only changes rarely it still follows the same rule. It will only send the it’s value out on the bus when it changes no matter how often a program calls for the value. Programs that create an Import/Export relationship with the format PointA=ControllerB\PointA. Wired Infinet In a wired infinet bus when a point that is flagged to be exported changes it’s value it’s value will be broadcast as a single message on the Infinet bus. Any controller that hears that broadcast and has an Import/Export entry for that point will grab the value off the wire and update it’s Import/Export table. If a controller that needs that value does not get it due to Infinet bus problems then that controller will not update it’s Import/Export table and will miss the point value update. Again the above scenario is for a hard wired Infinet bus. Wireless Infinet In a wireless infinet bus when a point that is flagged to be exported changes it’s value it’s value will be sent as separate messages to each controller that has in Import/Export entry for that point. For example if a point is used on 10 different controllers and the point is flagged for export and also the point value changes then ten separate messages will be sent out, one to each controller. The for each one of those 10 messages the originating controller is expecting an acknowledgement back from the destination controller. If the sending controller does not get the “ACK” message it will retry sending the message again every 3 minutes until it does receive and “ACK”.   Programs that cause a re-transmission of a point that is flagged as exported with the format Set PointA Refresh=True. Wired Infinet In a wired infinet bus when a program sets the refresh attribute of a point equal to true then it will send out a single broadcast message on the Infinet bus. Any controller that requires that point’s value will grab the message off the bus and update it’s import/export table. This will send the value of the point out onto the bus regardless or whether the point value changes or not. Wireless Infinet In a wireless infinet bus when a program sets the refresh attribute of a point equal to true it will send individual messages to each controller that has an Import/Export entry for that point. For example if a point is used on 10 different controllers and the point is flagged for export then 10 separate messages will be sent out on the bus to each of the controllers that require that point value. For each of those 10 messages the originating controller is expecting an acknowledgment back from each of the destination controllers. If the sending controller does not get the “ACK” message it will retry sending the message. NOTE: In item 2 you need to be very careful if you are using a refresh program. When using refresh programs you do NOT want to make them looping. You especially do not want to make them loop through setting the refresh to true. A simple fall through program that is triggered off the Minute system variable should be fine. Also remember that a refresh program is a workaround for an underlying bus problem. This holds true whether it is a wireless bus or a wired bus. Since Wireless Infinet I/E is a guaranteed delivery, DO NOT use refresh programs in Wireless Infinet. The additional network traffic can choke the network and it is totally unnecessary. It is also important to put thresholds on exported points to avoid overloading the wireless network. If a wireless point is exported to many other devices, especially on another network whether wired or wireless, you should mirror that point in the BCX and let the BCX distribute it to the other network, by having the other devices reference the mirrored point.   Alarms being sent to the front end. Wired Infinet In a wired infinet bus when a point goes into alarm the alarm message will be broadcast as a single message to the BCX. If there is a problem with the bus, ie substandard installation, grounding problems, etc… , then there is a possibility that the alarm message does not make it to the BCX controller. Wireless Infinet In a wireless infinet bus when a point goes into alarm the alarm message will be sent as a point to point message to the BCX. If the sending controller does not get an “ACK” message from the BCX then the controller will retry sending the message again every 3 minutes until it does receive an “ACK” message from the BCX. Important note: Any point that has an alarm attached is tagged for export. This means that every change of the point's value will cause an export, even if the point is not in alarm. If you have points that change their value often you need to put a threshold on these points even if they only have an alarm attached on a wireless Infinet to avoid excessive traffic.

Issue Creating a new cardholder in webClient gives the error 'Response XML String is Corrupt' Environment webClient Cause A modification must be made to the ServerUtils.aspx file. Resolution Have all users log out of webclient On the webclient machine, go to c:\program files\webserver folder, make a copy of ServerUtils.aspx. Edit the existing copy of ServerUtils.aspx and add the following text to the first line. validateRequest='false' Note: There are brackets < >at each end of the following lines in the ServerUtils.aspx file Original line: %@ page language="c#" inherits="WebClient.ServerUtils, App_Web_w0emuixz" % Edited line: %@ page language="c#" inherits="WebClient.ServerUtils, App_Web_w0emuixz" validateRequest='false' %   Close Internet Explorer if it was open Log back into webclient and then create a new cardholder and no error will show.

Issue The following error appears in the Niagara R2 UNC Standard Output Window: Duplicate Server Sessions - kill (Enterprise Server Name). Environment Niagara R2 UNC Cause Running multiple R2 stations can cause issue with the subscription of the UNCs in the address book of the Enterprise Server station. Resolution An Enterprise Server has the ability to run multiple R2 stations at one time. Under normal circumstances only one station should be running on a server.

Issue When accessing MNL vav boxes from a computer running Workplace Pro, the following error appears:   ERROR.E_INVALID_ENUM_ORDINAL.(6) Environment Workplace Pro MNL VAV boxes Cause This is an indicator of a jar mismatch. Resolution Ensure the UNC has the same lonSiebe and lonWorks jars as the computer running WorkPlace Pro.

Issue The specification sheet for the UNC-510 (F-27001) lists the power supply input voltage as 24 Vac or 24 Vdc. Can this UNC use a DC power supply source? Environment  UNC-510 Cause The spec sheet listed 24vdc as a supported power source but the installation manual instructs to use AC power source. Resolution No. It was originally intended to use both AC and DC but it was never UL-listed or FCC-tested as a DC device. The UNC-510 installation instructions (F-27033) clearly indicates the use of an AC power source.

Issue When looking at my Access Distribution screen I have some personnel records that are perpetually waiting to distribute. What could be causing this? Environment Cyberstation web.Client Cause The most common reason for this is if you have personnel records that have an "Expiration Date" greater than the default of 12-31-2099 11:59:59.00 pm. Resolution If you have personnel with an expiration date greater than "12-31-2099 11:59:59.00 pm", it will hold up the distribution. The best way to correct this is to run a listview of personnel records which includes the expiration date. Sort the listview by Expiration Date in descending or and change all the Expiration Dates that are greater than the 2099 date to the 2099 date. Once this is done the records should automatically start distributing.

Issue What is the earliest revision of Niagara R2 that the ProView LON Display, jar files and software wizard will function with properly? Environment Niagara R2 ProView LON Display lonWorks jar file Distech wizard Cause Using Niagara R2 revisions outside of R2.301.428 through R2.301.529 will not function with the UNC and Distech wizard. Resolution The UNC and Distech wizard will function with Niagara R2 revisions R2.301.428 through R2.301.529. The required files are available from The Exchange Extranet. Run the provided executable.  Then edit file names in the emb, nt, and nre/modules folders. Keep the newest Distech files and the latest lonWorks jar file.

Issue UltiVist/NETWORK 8000, how to remove all or parts of the E: Segment. Environment NETWORK 8000 Cause Procedure on removing a segment. Resolution KILBRNCH is a powerful tool, before doing the following procedure, BACKUP THE DATABASE. In an OS/2 window, go to the FI directory and type SET NOFCS=TRUE (this command turns off communications so that the KILBRNCH command will only delete the elements in the E: Segment set to 'offline'). Press Return. After getting the x:\FI prompt back, type KILBRNCH FI (example KILBRNCH \FI\FI E:000.GCM_00.XXX_00.xxxxxxxx). This will delete (or kill) the database from that branch. E: is the Segment 000 is the Network ID GCM_00 is the area controller number XXX_00 is the LCM/ASD device type xxxxxxx is the block type After completion, go to FI directory and then type SET NOFCS=FALSE. Refresh the E: Segment.  

Issue Is there a Log file I can turn on to verify that downloads to controllers are working? Environment I/NET Site Cause desire to know if downloads to the controllers is working Resolution The BRDPEND Log, when it is activated will show you the listing of all items downloaded. The actual location of this Log file is in the following area on the hard-drive C:\Program Files\Inet Seven\Data. This log list all the DPU downloads, this to make sure all the entries actually get to the DPU's in the field. To activate this log requires you to get into the Windows Registry, I will list all the steps required to start and stop this log. BRDPEND steps: Go to the "run" section of windows and choose Regedit. Go to the Registry at this location – HKEY_LOCAL_MACHINE>Software>CSI – Control Systems International>I/Net 2000>Host Configuration. 2) Highlight the file “AuditDWPendFlag” and do a right mouse click. Choose the Modify option Change the "0" to a "1" This will start the Log file To Stop this log file do the steps above again, except in step 4 change the "1" back to "0". IMPORTANT you have to shut down the PC and restart the PC before the Log will start running. When you turn off this log, copy it to an e-mail and send this log to Product Support. Remember - Do not to let this log file run more than a couple of days. I/NET rev 2.31 and above only downloads changes made in four areas Card Number Group Individual Info Access Level Below rev 2.31 downloads all individuals again with each change. 

Issue TAC Vista Uninstall Process fails. Environment TAC Vista Server Installation Cause During the uninstall process, a key in the registry does not get deleted that should.  This flags that the application is already installed, so the uninstall process won't proceed.  It is also impossible to use the "Add/Remove Programs" wizard to uninstall the application. Resolution What needs to be done when this occurs is to open the Registry Editor (Start > Run > regedit) and do the tasks described below: NOTE: Make sure that you do a backup of the registry since modifications in the registry can make your system unstable. Also make sure that you have a backup of the TAC Vista database and other important project files. Vista Server (You should perform this step if you can't uninstall the application from the control panel) Delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{639465AE-9BAF-4D29-B824-D8BFD8615070} ToolPack (You should perform this step if you can't uninstall the application from the control panel) Delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5FFB2771-0543-42A6-AF2B-61FE41D880D4} These registry keys are the same regardless of versions (TAC Vista IV and later), just to prevent parallel installation of different TAC Vista versions. When those keys have been deleted, manually remove the program folder. (Default "C:\Program Files\TAC\TAC Vista X.X.X")

Issue Vista 5.0.3 Graphics Editor crashes when you right-click on a graphics page in Workstation and click edit. Here is the error message: Could not load file or assembly 'TAC.Interop.TacosOI, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) FileLoadException at TAC.Graphics.Windows.Vista.VistaSystemProxy.Create(String server, String user) at TAC.Graphics.Editor.EditorApplication.CreateApplicationForm(ReadOnlyCollection`1 commandLine) in C:\TAC\VistaSw\V5030\Graphics\Editor\EditorApplication.cs:line 90 at TAC.Graphics.Editor.SingleInstanceApplication.<>c__DisplayClass3.b__1(Object splashFormSender, EventArgs splashFormEventArgs) in C:\TAC\VistaSw\V5030\Graphics\Editor\SingleInstanceApplication.cs:line 79 at System.Windows.Forms.Form.OnShown(EventArgs e) at System.Windows.Forms.Form.CallShownEvent() at System.Windows.Forms.Control.InvokeMarshaledCallbackDo ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() Environment Vista Workstation 5.0.3 TAC TGML Graphics Editor 1.0.3 Cause An error occurred at installation and the Graphics Editor must be removed completely and reinstalled. Resolution Shutdown the Vista Server and Workstation. Uninstall the TAC Graphics Editor 1.0.3 from the Control Panel of the PC. Delete the entire C:\Program Files\TAC\GraphicsEditor directory that is left behind from the un-install. Download the TACGraphicsEditor103.exe from The Exchange. Re-install the TACGraphicsEditor103.exe

Issue Xenta 121-FC fan runs in cool mode even though cool mode is not used. Product Line TAC Vista Environment ZBuilder Xenta 121 Cause Previous settings configure the cooling in such a way that the Xenta 121 runs cooling outside of cooling mode. Resolution In ZBuilder > Sequences > Fan, confirm that "Run in min speed if no cooling is configured" is unchecked In ZBuilder > Sequences > Cooling, set the Cooling from "Not used" to "On/off" Change the Activate at from 0% to 100% TL Go back and set the Cooling to "Not used" Apply/Save changes and the fan should not cycle on in cool mode

Issue Erroneous subnet/node ID mismatch warning on a LonWorks unit in the System Plug-in Environment System Plug-In LonWorks Device Cause Subnet and node IDs have gotten mixed up in the Vista database and must be recreated from LNS. The error appears as subnet/node address mismatch in the system plug-in. Resolution In the System Plug-in, on the TAC Network side, find the LonWorks unit(s) that are generating this message Taking note what LonWorks group they are a part of Delete the LonWorks units. Update the TAC network.  The previously deleted controllers will be added back into a newly created group. Move the controllers out of this new group to the correct, desired group. Delete the empty group and update Vista. The mismatch error message should not be displayed any more.

Issue I/NET Seven fails to install with existing MSDE version of SQL. Environment I/NET MSDE Windows XP Cause MSDE may need to be installed manually Resolution Download MSDE2000 from Microsoft’s website. Run the downloaded program, and it extracts itself into another directory. At that directory, run drive:\directory its located in\Setup.exe SAPWD=”any password you make up” After the MSDE is installed, run the I/NET installation as usual.

Issue Upgraded Vista 3 to Vista 5 and Digital Points can not be changed on OGC graphic page Environment Vista 3 system upgraded to Vista 5 Digital points OGC Graphics Cause This behavior has only been seen after a upgrade from Vista 3 when following the recommended upgrade path and does not effect every single digital point. Resolution The inability to control a digital point in an OGC graphic page on Vista 5 Webstation can be fixed by opening the offending graphic page in the graphic editor and then saving it back to the Vista DB.