Building Automation Knowledge Base

Issue SCU 1284 won’t communicate to the controller when you turn power on to the device Environment SCU 1284 Cause Product Support Services investigation of SCU12xx field failure returns has revealed that the significant majority of the returns are due to a failure of the RS-485 transceiver IC. Most of the failures are also being described as initial installation failures or "out of the box" failures. Close examination of the failed circuits and the conditions that will prompt failure of the RS-485 IC currently in use on the SCU indicates a significant probability that many, if not most, of the failures are the result of momentarily connecting the TB1 terminal block onto the SCU header with it shifted 1 position to the right. Connection of the TB1 block in a shifted manner will typically cause some relay buzzing noise prompting the installer to recognize the error and correct the position. Unfortunately the RS-485 transceiver will be damaged before you ever hear the relays buzz. Other than TB1 misconnection, the predominant other candidate would be induced transients on the LAN. However, the frequent description of the problem occurring during installation or out-of-the-box tends to point toward TB1 misconnection. Resolution Caution your installation personnel to pay extra close attention to the connection of the TB1 terminal block in order to reduce the SCU failures being precipitated by misconnection. TAC will also be investigating RS-485 transceiver selection and the use of more tolerant versions, and possible end caps on TB1 to inhibit misconnection.

Issue Storage Temperatures for TAC BCX/I2/b3 Controllers Environment TAC BCX/I2/b3 Controllers Continuum SmartSensor Cause Example: This information was for units stored in Antarctica with no heat. Resolution All i2/b3 with and without LCD: -30°C to 80°C (-22°F to 176°F) BCX: Less than 30 days @ -40°C to 65°C (-40°F to 149°F) The specification for the BCX battery indicates a recommended minimum temperature of 20°C when the battery is discharging, with no time limitation. The battery could be potentially be stored at -20°C for longer than 30 days with no problems. As a side note, the minimum charging temperature is 0°C, so be careful to let the units warm up before applying power to the BCX to avoid battery damage. Continuum SmartSensor: -20°C to 65°C (-4°F to 149°F)

Issue If power is removed from a UNC, how long before the UNC shuts down? Environment UNC Cause A UNC will not immediately shut down after power is removed. Resolution By default, the number of seconds to elapse after detecting an AC power failure and beginning the shutdown of the UNC or ENC is 60 seconds. This can be adjusted by opening the drivers.properties file and changing the value referenced in the power.shutDownDelay entry. For more information refer to the NiagaraSysmonEngNotes.pdf

Issue When creating links between an Enterprise Server and a UNC, the process takes 2 to 3 minutes per link. Why? Environment Enterprise Server UNC (Universal Network Controller) Cause The Enterprise Server station's address book may contain a UNC (or more than one) that does not exist or is offline. Resolution If a UNC no longer exist or is offline, it will slows down the link creation process. Remove the entry from the address book and restart the station, or, enable the UNC so that it is online.

Issue A UNC-5x0 fails to start its station and reports the error "Driver failed to load license". How can this be corrected? Environment UNC-5x0 Cause The error indicates a failure in the flash memory. Resolution Field repair of the UNC-5x0 is not possible. Contact Product Support Services to obtain a return authorization (RA) number.

Issue Personnel Picture control uses an older image after that specific personnel image has been changed through the Personnel editor. Environment CyberStation Cause Clearing cached on a station and then restarting it, is known to show the original image even if the image was replaced. Resolution To reproduce the issue, a graphic was created in Pinpoint with a Personnel Picture control attached to the LastPersonEntrd attribute of a door. When a valid card with a Personnel Photo attached is presented to a card reader, the Personnel Picture control will display the personnel photo. The same Personnel Object is then opened with Badge Manager and a new Photo image is saved to the personnel object, replacing the original image. If you shut down Pinpoint and CyberStation to clear any cached data. Now, restart Cyberstation and then Pinpoint, opening the panel created earlier. Now present the same card to a card reader. You will see that the original image persists. The new image will not displayed. This issue will be addressed in a future release, but there is a work-around that is simple to implement. If you have a Personnel Object that will have a new photo that must be attached, you can first delete the Personnel Object and recreate it. Or you can, disable the personnel object and create a new Personnel Object.

Issue Running a listview is giving a mfc error Product Line Andover Continuum Environment Continuum Listview Cause mfc42.dll version conflict Resolution Turn off Anti-Virus and the Windows Firewall during Cyberstation installation Turn off Anti-Virus when using Listviews to see if it is affecting operation If that isn't helping, run a virus and a spyware scan on the hard drive and determine that the drive is clean. If the hard drive is virus and spyware free and the issue remains, search the hard drive for the file mfc42.dll. Start > Search > For Files and Folder > All Files and Folders More than likely several of the files will show up including in the Continuum folder. Check the versions of these files by right clicking on the file > select properties > version tab. If there are at least 2 different versions, rename all of the mfc42.dll files to mfc42.old, except the one in C:\Windows\System32 Retry the Continuum listview to verify this fixed the problem. There are a few programs that install mfc42.dll which may create a version conflict including Norton Utilities, 3D Mark 2001 and SE, HP printer drivers and software, Nero Easy CD Creator, Max Payne, Ulead Photo Explorer, Logitech Mousewares, Creative SBlive Playcenter, some Creative Labs drivers and others.

Issue Receiving error “Could not connect to server. Cause: System.Runtime.Remoting.RemotingException:Requested Service not found opening graphics in webclient Environment Windows XP Windows Server 2003 Windows Server 2008 Cause This issue usually happens after uninstalling and reinstalling IIS. The webclient and newgraphicsfiles virtual directories may have been added, but DNWACServerFactory was not. Since the DNWACServerFactory virtual folder is missing, it keeps trying to create itself, but it can't and it generates the error. Resolution Get all users out of webclient In IIS (Internet Information Services Manager) Right click on Default Web Site, select New> Virtual Directory Click Next In the Alias field type: DNWACServerFactory, Click Next Click Browse and navigate to C:\Progam Files\ Continuum\DNWACServerFactory Click Next For access permissions, keep read, run scripts and select browse Click Next, Click Finish Restart webclient and test out graphics

Issue In a Niagara R2 / MicroSmart integration, what's the optimal method to transfer data from a UNC station to all the MicroSmart controllers connected to its RS-485 port? Environment Niagara R2, Niagara G3 MicroSmart controllers (versions 10 & 11) Cause Sharing data between controllers Resolution The MSGlobalDataOut object will transmit data, from a UNC station, onto the MicroSmart (RS-485) bus using a MicroSmart global broadcast channel. Then, within each controller, a point can be programmed to access the data from that specific channel number. Only controllers with firmware revision 10 & 11 support MicroSmart global broadcast channels. MicroSmart controllers with a capacity of 64 points, like the MSC-MPC, can receive information on all 122 global channels. MicroSmart controllers with a capacity of 48 points, like the MSC-P1500 series, can only receive information on global channels 1 – 24. See the MicroSmart Driver Engineering Guide (F-27327) for more details on the MSGlobalDataOut object. See the DMS Operator Interface User’s Guide (F-25467) for more details on MicroSmart Global Broadcasting.

Issue BACnet binary value objects will pulse an Infinity output when they are used to set its value instead of turning it on. Environment BACnet binary value object Infinity output Cause People who are unfamiliar with programming for BACnet controllers may find it difficult to code their programs based on BACnet point values. Resolution When coding for Andover BACnet controllers, it is important to consider the differences between BACnet and Infinet point types. If you create a Numeric (configured as a binaryvalue) in a b3, b4 or BCX BACnet controller and you import that value into another controller for use in controlling an Infinity output, the output will pulse once on change of state (equivalent to output=1)and then shut off. Also, when changing the binaryvalue from inactive to active will cause the output to pulse as well. When an Infinity output is set to Digital The default display format is $###. When the display format has been set to $### , values greater than zero will be displayed as ON, zero value will display as OFF and values less than zero will display as -ON if it is a tristate output. Changing this display format to ###.## will show the exact value of the output. On/Off or the analog value sent to it. Use the blue BACnet folder and check that the source point is defined as a Binary Value and the Output is a Binary Output. If an Infinity Numeric was originally created as the default Analog Value and sent to database in the BACnet folders, it will have to be deleted and re-sent to database to get it into the correct Binary Value folder. Example 1: The program below in the importing controller is a one-line looping program as follows: output1= B4/B3/BinaryValue A possible use for this would be a global occupancy point being used to turn the lights on. Example 2: Write a PE program to copy a binaryvalue (BV) to a binaryoutput (BO). Set the BV to Inactive. Observe that the BO is Inactive. Set the BV to Active. Observe that the BO pulses for one second. In order to import BACnet Binary values into another controller and use these points to drive an output on that controller you must use the BACnet point objects in your Plain English program as per below: "Full BACnet Path" Binary Output Name = "Full BACnet Path" Binary Value Name This will ensure that when the binary value is true, or "1", that the Binary output will go to "ON" and not pulse for 1 second.

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 LonMaker makes you wait in a 'transaction queue' before it will process any commands that require communications to the network. Environment Echelon LonMaker Cause This problem seems to arise when changes are made to the structure of a large network in which the majority of controllers have been commissioned, but not yet installed. LonMaker then tries to continuously update these controllers of the network changes that have been made, but it can't since they are not online. Thus, when any requests are made by the user, they must wait in line until LonMaker gets to their requests. Resolution The problem has two solutions: The first, and most simple, is to bring all of the commissioned controllers on the network online. This will allow LonMaker's updates to be propagated to them all, causing an end to the cycle. The second solution is to decommission any controllers on the entire Network that are not online, but have been commissioned prior to the network changes. This will eliminate LonMaker's desire to update these controllers. These solutions must be applied to the entire network, and not just the channels that have actually had the network changes performed on them.  

Issue XBuilder crashes when a LNS network is inserted Environment XBuilder LNS Network Cause XBuilder will crash when a LNS network is inserted that contains a XIF file which has multiple signals with the same name. Resolution If Vista 5.0.0 or higher is being used you can create a Vista database solely for the purpose of inserting it into XBuilder to avoid this problem. Otherwise the XIF file will need to be modified to remove the duplicate names and the template replaced with the new XIF file.  

Issue Windows XP is requiring you to log in and you do not know password after installing Vista 4.3.0 - 5.0.0. Environment Vista 4.3.0 - 5.0.0 Windows XP Cause Vista 4.3.0 - 5.0.0 creates local accounts on your computer when you install the software. These accounts are used by the SQL server portions of the software. However if the computer was still using the default Administrator account then the next time you boot up the computer it will ask you for the password on either the TACA_PCNAME or TACM_PCNAME accounts. The passwords are randomly generated and should not be used to log into Windows. Resolution To get back into your computer: Press the Ctrl-Alt-Del keys twice to get to the traditional Windows 2000 log in screen. This will allow you to use the Administrator account to log into the computer. Once logged in you should create an account that will be used for normal operation. To avoid this problem you can restrict your installations to Vista 5.0.1 which will not use local PC accounts for SQL administration, but SQL Server accounts instead which will not effect the normal computer login process.

Issue Visio will open but LonMaker menu is missing from the toolbar, the features are unavailable. Error: "unable to launch visio with file lonworks.vst". Product Line TAC Vista Environment Echelon LonMaker 3.0 Echelon LonMaker 3.1 Echelon LonMaker Turbo (Ver 3.2) Cause Configurations must be set to link LonMaker and Visio so they run together. Resolution Please consult Echelon's bulletin on this matter at Echelon's website. The bulletin states that only the following should be in the Add-ons field: C:\LonWorks\LonMaker;1033\Solutions; To fix the problem, you also need to add: C:\LonWorks\LonMaker\Visio It is also necessary for the following to be enabled (Macro Security). In the Tools > Options > Security menu, verify that all options below are selected: Enable Microsoft Visual Basic for Applications Enable Microsoft Visual Basic for Applications project creation Load Microsoft Visual Basic for Applications projects from text Enable COM add-ins Enable Automation events

Issue Downloading a 7793 save file to a 7798 Controller Running into a problem when trying to download a 7793 save file to a 7798 Controller Keep getting an error when it tries to download the I/O Configuration Product Line TAC INET Environment I/NET Seven 7793 7798 Cause The I/O Configuration for both of these controllers is different. The 7793 Controller is a dual station device while the 7798 Controller is a single station. Resolution In order to fix this, contact Product Support. We will provide you with the time required to convert these files and a Price Quote for the work involved. 

Issue Shutting Down I/O Server while running as a Client Environment I/NET Seven rev 2.X and above I/O Server Cause Running I/NET I/O Server as a service and need to shut it down in order to do a backup or to run DBCreate. Resolution Close I/NET, since I/O Server will still be running, it can’t be closed. Open I/O Configuration Editor, if you right click on I/O Server, the Exit button will be grayed out. Close I/O Configuration Editor, right click on I/O Server again and this time the Exit button will become available and it can be selected. Select Exit and I/O Server will now be closed. To restart I/O Server again, either restart the PC or launch it through Administrative Tools > Services > MSQL Agent  

Issue Issue with DPUs after an upgrade to the system. If you have upgraded and changed out the EPROMs on the board, but it does not seem to be getting any Transactions or Time Schedules to work properly. Environment I/NET site with Access Control Cause Upgrading DPU controllers Resolution Connect to the controller, select Edit/ Host Computer/Network Configuration Penetrate the Link Summary, Penetrate the Controller, penetrate the DPUs At this point the rev level will be different, do not modify it to put the correct rev level. Instead leave it blank and the software will fill it in automatically.

Issue How can BACnet objects be learned as "full" objects and not "lite" objects in Niagara R2? Environment Niagara R2 Cause "Use lite objects" is enabled and need to be disable (uncheck the box) "Use Lite Objects" setting using BACnet Utilities. Resolution From the BACnet Utilities window, when performing either a "network - learnNetwork" or "device - learnDevice" command, clicking the Execute button will generate a pop-up window. In this window, uncheck "Use lite objects", and click OK to proceed.

Issue How can an AI object be scaled to display to 4 decimal places in Workplace Tech? Environment MNL controller MNB controller Workplace Tech Cause The AI object in a MNL or MNB controller can only display to 2 decimal places and this cannot be increased. Resolution Change the "scaled high value" and "scaled low value" represented by the input signal. For example: Given a transmitter that provides 0 to 5 VDC representing 0.0 to 0.1 inches of water column. Rather than putting in a "scaled low value" of 0.0 and a "scaled high value" of 0.1 make the "scaled high value" 100. Then take that value up to a Niagara station and divide it by 1000 to convert it back to inches of water column.  This will display it to 4 decimal places.