Building Automation Knowledge Base

Issue Every time the Time Sync service runs, an error is generated in the Application Director console window.  The message reads "Error:  NTP in use, RFC868 clients ignored".  What is NTP and why is the system reporting the error.  I have the Time Server function configured in the same manner and with the same servers that I always use. Environment I/A Series G3 release 3.4 or newer Cause Both the "Time" and "NTP" time sync services have been enabled in the system. Resolution The I/A Series G3 software was modified in Release 3.4 to allow the use of the use of NTP protocol time servers in addition to the older "TIME" protocol time servers. If the I/A Series G3 system software detects the use of the more accurate NTP protocol, the error message "Error:  NTP in use, RFC868 clients ignored" is reported and the attempt to synchronize the time to the TIME server will be ignored. The use of "TIME" protocol servers and clients are configured in the "TimeSyncService" service in the station services.  The use of "NTP" services is configured in the "NtpPlatformServiceQNX" under the Platform Services.  If you desire to use the TimeSyncService instead of NTP, you need to disable the "NtpPlatformServiceQNX" by opening the "Ntp Platform Service Editor QNX".  To disable the service, set "Enabled" to FALSE as shown below.

Issue When you open a trend you get the following message Environment Vista 5.x.x Cause The period selected in the trend chart does not exist in the trends associated with that chart. In the sample below the trend only store 1 days worth of information and the chart is requesting last weeks information. This would result in this type of error. Resolution Modify the period selected in the chart so that trend values that are logged will be displayed.

Issue Unable to access to ENC via its Ethernet port. Connection to the ENC's Serial Shell indicates the ENC is continuously rebooting which the following messages. Press to stop autoboot... Autobooting... Loading image from on-board nand flash Niagara JACE 4/5 IPL Version 0.78 Environment I/A Series G3 Enterprise Network Controller (ENC) Cause Unable to load NAND image Resolution The ENC cannot be recovered in the field. If the unit is still under warranty, contact Product Support and obtain a Return Authorization Number for warranty claims through your usual channel. If the unit is no longer under warranty, purchase a new unit for replacement or check with your local sales channel for the cost of repair.

Issue COVNotification messages in BACnet captures. Product Line EcoStruxure Building Operation Environment BACnet IP network BACnet MSTP network BACnet networks with controllers that support COV (Change of Value) Cause COV increment is an attribute that is available in several BACnet points that is settable and when this attribute COV Increment is left at a setting of zero can cause COVNotification messages appearing as broadcast storms creating un-necessary network traffic. Resolution It is suggested to set the value of the COV increment attribute to something other than the default zero or to a value that is pertinent to the point in question. The COVNotification services are uni-cast messages and can have a many to one relationship depending on how may clients are subscribing to the point. Example: Jobsite has a BACnet OAT (outside air temp) input point with the COV increment of zero. The OAT point is added to the watch window or a binding to a graphic or program. The OAT is changing ridiculously fast due to wind and intermittent clouds. The value is changing by 1/1000 of a degree and each COV (change of value) message is delivered out to any object that is referencing the point. But does the value need to display or do we care if the point changes by 1/1000 of a degree. Let's say that the sites requirement only needs value changes of 2 degrees or more. The COV increment can be set to 2.0 and now the UnconfirmedCOVnotification message would only be sent if the OAT changed by 2 degrees or greater. This alone would reduce 100's if not 1000's of network packets. Imagine a jobsite with the above scenario and 100 different points all with the COV increment of zero. Setting the COV increment to something other than the default of zero is one of many ways to improve BACnet communications and reduce what may appear as broadcast storms on the network.

Issue LonPort is discovered and shows as online but no Service Pin is received Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation ES 1.1 LConfig Cause Since StruxureWare Building Operation ES is running as a service, the legacy driver also has to be. Resolution Open LConfig Click advanced Change Legacy Driver to run as service

Issue .DAT files and what their purpose is. Another good practice for the Removal of the "DAT" files is this:  Anytime a Tech goes to a site, it is wise to remove all the "DAT" files Prior to attaching a Laptop to a new site. This way you will not corrupt this site routing tables with bogus IPs and Links.  Environment I/NET site with profiles, DLA or non DLA architecture DAT, .dat, profile,  Cause Profile corruption or Reference host issues can be resolved by renaming and then recreating the .DAT file. Resolution .DAT files contain the routing table that the Netcon gets the data from. Profiles: The I/NET Configuration program allows you to specify and save more than one set of configuration specifications. These specifications are called profiles. The majority of host workstations only require one profile. However, multiple profiles are useful if you work with several different TAC I/NET Seven environments, because you can change system parameters simply by selecting a different profile. Most of the configuration parameters are saved in the system registry and IP routing information specific to each profile is stored in a .DAT file. Note: There may be differences in the routing data for each configuration profile; consequently, you should not change configuration profiles in a stable TAC I/NET Seven network. Reference Hosts A host workstation, NPR, or Xenta 527/527-NPR must have knowledge of the other devices on the network in order to communicate with them. This knowledge is stored in what is commonly called a routing table. A routing table will contain the IP address of the devices known to the host workstation. When the host has data to route to another TAC I/NET Seven device, it uses the addressing information contained in the routing table to determine the destination path. I/O Server stores the routing table in a .DAT file.

Issue Description in List View editing causes error Environment StruxureWare Building Operation 1.1.xxx Cause 1. Enter a description in the List View. This can be for anything, I selected a folder in the following two screenshots. 2. Boiler1 Folder: Description is Boiler 3. Boiler2 Folder: Description is Chiller 4. Graphics Folder: Description is Chiller 5. When I cut Ctrl-X the Graphics description and them on down the list, (imagine I have a lot of folders or devices I am putting descriptions in) if I save when not in that field, the error below occurs.  Resolution Upgrade to StruxureWare Building Operation Workstation release 1.2.0.659 or higher.

Issue When using Sigma on a PC with firewall enabled, communication doesn't work. Product Line Satchwell Sigma Environment Sigma Server Sigma Client Firewall Cause In most cases Sigma is installed on a separate network and is not connected to any outside sources. The firewall is therefore turned off in some cases. Where Sigma is installed on an existing network or a corporate network it is usual for the firewall to be turned on. If this is the case then rules will need to be created to allow correct operation of Sigma. Resolution On a remote Sigma Client the first time you run SigmaClient there should be a popup to allow an exception to be created for SigmaClient. When asked select yes to this. Next task is to create rules to allow comms through the firewall. The next task is done on the remote client PC's and on the server PC. Open Windows Firewall configuration: Control Panel\All Control Panel Items\Windows Firewall Click on "Advanced settings" to the left Click on "Inbound Rules" and click on "New Rule..." From the selection choose Port, click Next From this point it is needed to do the rest once for UDP and once for TCP. The example will show UDP 49152, and needs to be repeated for TCP 8080 and TCP 3614. Chose UDP and enter 49152. Click Next. Select "Allow the connection". Click Next. Select the applicable networks. Click Next. Type in a name for the rule. Click Finish. Go to step 5 and repeat for ports TCP 8080 and TCP 3614

Issue Is it possible to sort the Vista Workstation alarms only by date, not by group in alarm viewer? Environment TAC Vista 5.x.x Workstation alarms Cause When you sort the Vista Workstation alarms in the alarm viewer by date, No matter how you sort them they are arranged by date and type OR by groups (Unacknowledged, Acknowledged and then Acknowledged Reset..etc). See the below picture for example; Resolution No, It is not possible to sort the active alarms just only by the date in Vista Workstation alarm viewer. This will sort by groups.

Issue File Equalization, what passes between the Filemaster and Equalized Client Environment I/NET with Filemaster and Equalized Client snapshot, equalize, tables Cause What transpires between the Filemaster and Equalized Client Resolution File equalization is essential in TAC I/NET Seven systems where multiple host workstations will be used to manage access control or TAC I/NET Seven’s network configuration. It allows host workstations connected to an Ethernet LAN to share certain database information while still maintaining their own TAC I/NET Seven database. File equalization is a function of the SQL server that is installed on TAC I/NET Seven workstations. The SQL server ensures that each individual workstation has up-to-date copies of equalized information. The equalized information includes: Network configuration (links, sites, stations, etc.) Host passwords Controller passwords Tenant data User-defined tenant field labels Individual records Group door assignments Elevator floor assignments Trend plot data The following tables are equalized: Tenants Individuals IndivCustomData IndivImages IamUser DoorsGroups Groups SecondaryGroups XRefTenantDoor XRefGroupDoor XRefIndivGroupDoor Cards CardTrans Floors FloorPoints Visitors Operators OpWindowPosition XRefOperatorDoor PwdHistory AmtFilters MultiPlot MultiPlotPnt PwDCU DpuRestore DoorScheduleTypes DoorSchedules PerSchedNames PerScheds GlobalOptions DispatchStrings Tools UserButtons NetConLink NetConSite NetConDCU NetConMCU NetConDoor

Issue When attempting to run reports it fails and generates an error. Receive "unrecoverable Error!" when trying to open Continuum Reports package after fresh installation or re-install of Reports. Error can be similar to below image.   This error is also generated if you try to run the Reports password reset batch file.   All other functions of Continuum Cyberstation function fine, only the Reports application is affected. Environment Continuum Cyberstation Continuum Reports Cause The Continuum_Reports folder security privileges are not set properly. Resolution Login with a windows user that has administrator privileges. Edit the properties for C:\Program Files\Continuum_Reports. Click on Security. Scroll down the list of Users and select "Everyone". Enable (check off) the missing properties (Modify and Write).  

Issue Cannot open the LonTrunk folder for a particular UNC station in WPP in the Enterprise Server.  Getting error: Environment I/A Series (Niagara) R2 Cause LonWorks jar mismatch between the Enterprise Server and the UNC. Resolution Alter the LonWorks jar in the Enterprise Server or the UNC's so they match.  It is recommended the Enterprise Server and it's subordinate UNC's be at the same software revisions. 

Issue Generating or importing one XBuilder project into another directly from Vista takes very long time Environment TAC Vista TAC XBuilder Cause In v5.1.7, a new feature was introduced that made it possible to import one XBuilder project into another directly from Vista instead of from a file. TAC XBuilder will by default do a project reference check to determine if the project is included in any other TAC XBuilder projects in the TAC Vista database. If it is included in any other project, the user will be notified in the TAC XBuilder output pane. The reference check will increase the time it takes for TAC XBuilder to generate the project; depending on the amount of TAC Xenta Servers that exist in the TAC Vista database. Resolution It is possible to disable this automatic check in the TAC XBuilder project settings. From the menubar click Project and then select Settings... In the Settings dialog box uncheck the box that says Check project references in TAC Vista database.

Issue The following message appears after approximately 30 seconds when you attempt to edit a Menta file from the system Plug-in. Environment Windows 7 Vista 5.1.5, 5.1.6 and 5.1.7 Cause The login screen does not come to the forefront when required Resolution Use the ALT - Tab key combination to scroll through the open windows. Select the logon screen and continue with the normal process.

Issue Unable to select extended trend logs in Trend Log Comparison Report. Environment StruxureWare Enterprise Server Cause Extended Trend Log property " Include in reports? " defaults to false. Resolution Extended Trend Log property " Include in reports? " must be set to true.  

Issue When VisiSat 2.1 Build 185 on some Windows XP pro / Visio 2003 computers the following error is displayed. Internal error 0x86DB08A9 VisiSat 2.1 Build 185 Cannot find VisiSat "CustomiseUI" add-on to Visio. Some or all the files required by VisiSat are missing. You may need to re-install Visio and/or VisiSat to clear the problem. Environment CustomiseUI Add on to Microsoft Visio 2003 VisiSat 2.1 Build 185 Cause Visio 2003 does not recognise or register VisiSat 2.1 Build 185 installation CustomiseUI Resolution Open Visio 2003 (Not VisiSat) On the menu bar, under tools select options.   Select the advance tab.   Select file paths.   Delete all entries. Then select OK   Select OK.   OK the next window Visio 2003 should now close.   Run up VisiSat VisiSat should run up OK now.   If you close VisiSat and open Visio 2003 the paths should now show.   VisiSat should open correctly now. Option: If you are running on Windows 7 you could consider upgrading the Visio 2003 software to Visio 2007 or Visio 2010. If you require further assistance, please contact Product Support.

Issue How to set up M-Bus for Heat meters using Westermo AD-01 Environment Continuum Cause The M-Bus Xdriver is often loaded on Comm1 of a NC, NC2 or bCX (RS-232) this if often then connected to a Westermo AD-01 M-Bus adapter. How is this set up Resolution Westermo Connection Details Westermo web site AD-01 1. The Westermo unit requires a separate power supply, see AD-01 datasheet for power supply connection details (Nominally 230Vac) 2. Connection to an RS232 Controller comm port (NC2 or bCX comm1 used in this example) NC2      AD01    or     AD01 RJ45     DTEtop        9pinD RJ45     Slave           (Female) 5-SG     1-SG             5-SG 6-RD     4-RD            2-RD 8-TD     3-TD             3-TD bCX      AD01     or     AD01 9pinD    DTEtop        9pinD (male)   Slave            (Female) 5-SG     1-SG              5-SG 2-RD     4-RD             2-RD 3-TD     3-TD              3-TD 3. AD-01 Connection to an MBus network Heat Meters. (AD-01 METER BUS MASTER Terminals 4 & 5 to Terminals 24 & 25 on heat meter (Kamstrup or SE unit) MBus Card) The MBus baud rate is often set to 300 when the heat meters are powered by battery, the baud rate is set on the comm port of the bCX or NC2, this is automatically used by the heat meters so these do not require setting up. The heat meter address can be found in the meter menu See the XDriver guide and software for further details of controller set up NOTE To test it is often best to leave parameter 3 at zero, to ensure the standard telegram is sent, then set parameter 2 to one. The value seen is usually the Meter Customer number. (It has been seen with some issues of this Xdriver, that the controllers needs to be reloaded before the telegram is received and populates the Numerics correctly) Typical Screens

Issue When I restored this database to the workstation (PC) it took a very long time and the following error came up: An error occurred while creating InetDb: Could not allocate space for object "(SYSTEM table id: -xxxxxxxx)' in database 'InetDb' because the 'PRIMARY' filegroup is full. Continue?  Selecting YES, it appeared to complete correctly Environment I/NET Seven SQL 2000 Desktop Edition (MSDE) Cause Key words in the error message refers to "could not allocate space".  When using MSDE the size limit is 2GB, with very large databases the size is very close to this limit, so usually both backups and restores occur correctly.  The problem arises when you attempt to perform an upgrade, during this upgrade the database may exceed the limit imposed by Microsoft and hence the error may appear. Even though the process has appeared to have completed correctly and selecting "Continue?".  It should NOT be assumed the database has completely been restored. Resolution To successfully use this database you can look at the following solutions: Upgrade the version of SQL to a version of that supports a larger database size.  Note that if you are using File Equalization, the file master must be using either Standard or Enterprise version of SQL Server 2005 / 2008. Restore the database back to the same version of I/NET that it was original installed on and perform an Archive (via Archive Configuration editor) so that the database is reduced in size allowing it to be successfully upgraded.

Issue When swiping card, the access is denied. The message shown in AMT is "Bad Card Read". Environment I/NET Cause There may be two causes for this message: The tenant code isn't correct when using Wiegand 26 format in the door parameter. The digit of card number exceeds the setting in the setting of card reader type. For example, the card format is Wiegand 35, but in the door parameter, the card reader length is set to 36 digits. Resolution For cause 1, enter the correct tenant code in the Tenant Editor. For cause 2, set the correct card reader type and digit.

Issue When the Xenta 102-AX plug-in is opened the following error is given, “Reply to ‘request for LonMark Object status’ message was not received” Environment LonMaker NL220 102-AX Plug-in Cause There is a bug in the certain beta versions of the LonMark/Echelon DRF-kit. LonMark resource files 13.04 and 13.10 will not work with the Xenta 102-AX plug-in. Resolution The solution for the Xenta 102-AX plug-in error is to install a LonMark resource file version other than 13.04 or 13.10. Shut down LonMaker Go to add and remove programs. Uninstall LonMark Resource Files (13.04 or 13.10). Go to http://www.lonmark.org/technical_resources/resource_files/ Download the latest LonMarkResourceFilesXXXX.exe Run the executable. Restart LonMaker. Verify that the 102-AX plug-in works without errors.