Building Automation Knowledge Base

Issue Controller comm is lost after enabling Network Security after properly configuring the Controller and Workstation. Environment Network Security NCII CX9680 ACX5740 ACX5780 Cause Network security activation was being inhibited by the domain user security policies. Resolution In this case both the controllers and Windows network security policies had been configured properly for Continuum.  This fact was confirmed when the IT department got involved.  Once they relaxed some of the security policies on this machine Continuum network security began to work as expected, both from the controller and Cyberstation point of view. The customers IT personnel did not share with us what policies were responsible for the activation issues.

Issue Controller drops offline when reloaded or when an attempt to flash firmware is made. Environment Infinet MSTP Cause Massive CRC errors on the MSTP bus due to a bad controller on one leg of blink. Resolution In this case the problem was due to a bad controller on the bus.  The offending controller was located by segmenting the bus to determine which legs were introducing this problem. Once it was determined which controller was causing this issue, the controller was removed and a replacement installed.

Issue Upgrading a UNC 196 outstation. Environment UNC 196 296 Upgrade Cause Customer wishes to upgrade his BAS outstation to a Sigma controller. Resolution To upgrade the outstation the following cards will need to be replaced. Comms/CPU Card Power Supply Card. These can be purchased together as an S-x96-UPKIT If the outstation also contains a Maximum Demand card, this is replaced by a Digital Input card (S-UNC-DI).

Issue Importing a Xenta 121-FC controller into StruxureWare Building Operation. Environment Xenta 121FC Cause How do you setup the Xenta 121-FC using StruxureWare Building Operation only, as all the config needs setting for 1 Return Temp. Cooling Only (AO type). Fan On/Off   Resolution The original process would require the use of LonMaker and ZBuilder to configure the Xenta 121-FC controller onto the LON network, before adding it to the StruxureWare Building Operation LON interface. Version 1.4 introduces LNS device plug-in support to configure LonWorks® devices. StruxureWare Building Operation v1.4 supports third party software: OpenLNS. OpenLNS is only required on WorkStation machines used for configuration of LON® devices (e.g. WorkStation Pro machines). Automation Server and Enterprise Server databases are updated with any changes created with the plug-in. With LNS device plug-in support, now ZBuilder can be used with SmartStruxure solution. Plus, all Xenta controllers are supported, including the X100 series – e.g. Xenta 121.

Issue BCX9680 controller goes offline every five to ten minutes then returns online. Environment Infinity Controller BCX NC CX Cause Duplicate IP address on the network. Resolution Give the controller a unique IP address.

Issue The Web Server threw an exception. Please make sure the StruxurewareReportingAgent service is running and is set to run "Automatic" An error occurred on the Web Server while processing your request. If the problem persists, please contact your system administrator. Environment Webreport 1.4 upgrade Cause A WebReports installer must use an admin-level SQL Server Management Studio user account to log on to a computer running WebReports. This installer account also requires the addition of three database permissions that permit access to and control of the WebReports database during installs or upgrades. For example, an administrator can detach the database. In SQL Server Management Studio, verify that the Login Properties for the NTAuthority\IUSR and designated WebReports installer user accounts include the db_datareader, db_datawriter, and db_owner database role memberships. Resolution Use SQL management SQL studio and log in to the SQL. Use properties on the user NTAuthority\IUSR and make sure the following are included db_datareader, db_datawriter, and db_owner database role memberships.

Issue The jobsite will eventually have 4 RS-485 trunks each communicating Modbus.  Two option cards have been ordered with the Jace (part# TRD-NPB-2X-485). Does each port on the option cards need a separate Modbus driver purchased for each? Environment Niagara G3 Cause Ordering/licensing clarification Resolution Purchasing one Modbus driver (part# ENC-DRV-MOD) will cover all ports used for Modbus on the Jace-6/7.

Issue Continuously repeated errors in Standard Output Window of R2 (Niagara) station,  "Set timer for tag: (an integer) :400" and "Clear timer for tag: (same integer)" . The integer increments by one about every second until it reaches 128, then reverses the count, counting down by one into negative numbers. Environment I/A Series R2 UNC with the GCM driver Network 8000 GCM Cause The cause of the problem was resolved with the gcm-2.304.530b.v1.jar. Resolution This is considered a nuisance error, and was corrected in the gcm-2.304.530b.v1.jar.

Issue The customer is requesting a documentation on how the Alarm notification from Continuum works with MS Outlook to send out alarm email alerts to their facility engineers.   Environment MAPI MS Outlook CyberStation Email Cause The client is asking for information on how Cyberstation works with MS Outlook. Resolution Continuum uses the Enhanced MAPI messaging architecture to interface with MAPI compliant messaging applications/systems.  To understand this process in better, research Enhanced MAPI.

Issue What determines haw many active animations a graphic can have? Environment Cyberstation Pinpoint graphics. Cause Graphic updates will slow down if an excessive number of animations are configured. Resolution 50 Animations on a graphic is a good limit that should give a reasonable update rate on most systems. In the Pinpoint editor you can change the polling rate of each animation from the default 1000mS allowing less important points to be polled less, thus allowing the important points to be polled more. In Edit mode; go to Configuration, Object List to see the polling rates listed, each animation allows you to change its polling rate. It is generally better to have more graphics with fewer animations for faster updates. The rate at which you can poll for updates will also depend on your system layout, a system with many animations being polled from large slow MS/TP of Infinet field bus network will update much slower than a system with NetcontrollerII and IO modules with all points connected at the Ethernet level. No Pinpoint animations poll from the SQL database, all data is polled directly from the controller that holds the Animated object. When a graphic is opened the Workstation goes to the SQL Server to get the background file and the location of all polled objects, it will then directly poll the field controllers with no further need to connect to the SQL database.

Issue Does the short yoke Forta actuators fit on the current portfolio of valves?  Environment MG600C Venta Forta Cause With the new short stroke actuator MG600C soon available, will it work with the regular valves? Resolution The MG600C is designed to be used with the VG210R / VG310R valves that will be released in the near future. 

Issue LNS Plug-in for Viconics Thermostats Environment LNS NL220 Lonmaker Cause It is necessary to configure the Viconics VT7000 series controllers with an LNS Plug-in Resolution Download the latest Viconics Plug-in Here. Additional Information on the Viconics product offering can be found at http://www.viconics.com/.

Issue When using Conversion Coefficient slope m = 1.0, the return to normal (RTN) Alarm Limit on an AI point appears to have a built-in offset. Environment I/NET Seven - Analog Inputs (AI), all revisions. Cause There is a built-in hysteresis of 3 counts on the return-to-normal settings for both the low and high limit setting of an analog input (AI) point.  When using a conversion coefficient slope (M) of 1, this provides a 1:1 scale between counts and engineering units which could provide undesired results.  So this built-in hysteresis needs to be considered when using a slope (M) of one or higher on analog input alarm points.    Resolution Consider using a conversion coefficient slope (M) of 0.1.  Alternatively if this is not possible, creating an internal AI point (using a m = 0.1) or a DA and applying a calculation to reflect the points value or alarm state as required as a workaround.

Issue The Enterprise Server’s archives are not updating and the following message is displayed in the Standard Output Window:      ERROR: LogService.archive: SQL Exception: Container 1,342,197,790,972 not found.      ERROR: LogService.archive: Force close of Connection!      WARNING: Closed Pooled connection [ConnectionPool]      ERROR: XSCH1: Container 1,342,197,790,972 not found.   Environment Niagara R2 Enterprise Server – all versions Cause The “SQL Exception” error and “Closed pooled connection” warning appears to indicate a corruption within the Cloudscape SQL database. Resolution In this instance, the app folder became corrupt when copied between builds during an upgrade.  The original app folder was simply recopied. The second copy of the app folder copied without errors.   The following would apply in instances were the original app folder is corrupt:  First, try and recover the Cloudscape database and repair the corruption using the console and the dbadmin command.  After stopping the station, open the console and run the command at the prompt:            dbadmin >  recover  The software will search through the Cloudscape SQL database and attempt to clear the errors and recover the database.  If this is unsuccessful, you may have to remove the APP folder from the station and start over.    To remove the Enterprise Server’s app folder: Stop the server’s database and delete its app folder.  A new app folder will be created when the server is restarted.    Note: All archived information will be lost when the app folder is deleted.          

Issue Cannot find manual service pin location Environment Schneider Electric SE76xx, SE73xx and SE72xx Viconics VT76xx, VT73xx, VT72xx Ready7 Commissioning Neuron ID Lonworks ID Service Pin message Cause The Service PIN is used to identify the device at commissioning. There is not a visible service pin button located on the Viconics device. Resolution A Service Pin will transmit the program ID and the Neuron ID (LonWorks Unique ID) contained in the device to the commissioning or service tool. The Status LED will blink when the device accepts the Service PIN command. VT7600 device - Press simultaneously the “Yes” button and the “No” button located on the keypad interface VT7300 and 7200 device - Pressing simultaneously the “Up” button and the “Down” button located on the keypad interface.       Additional Information on Viconics VT7600 series can me found in this Viconics Lon Integration Manual. Additional Information on Viconics VT7300 and VT7200 series can me found in this Viconics Lon Integration Manual.

Issue Is there a replacement RJ-11 to BACnet MSTP cable for I/A Series Roam IA? Environment Roam IA, MNB-ROAM-IA Cause Need to replace cable. Resolution The part number for the replacement RJ-11 to BACnet MSTP cable for Roam IA is MNB-ROAM-CBL.

Issue In what positions can Continuum controllers be mounted? Environment Continuum Product Line Cause Not sure if the controllers can be mounted on both the vertical and horizontal plane. Resolution There may be some specific mounting instructions for some of the controllers, but for the most part they can be mounted in any direction in the vertical plane. Controllers with relays should not be mounted with the edge the outputs are on facing down. Consult the installation instructions (found here) for each controller for any specific mounting requirements.

Issue Can the gaskets included in the connection kits be ordered / purchased separately? Environment V241 V241 Venta Connection kit gasket Cause Gasket replacement requested if lost or worn out. Resolution Unfortunately the gasket part of the connection kit is not available separately and this can only be ordered as a complete kit.  

Issue I/A Series R2 station fails to send BACnet alarm to a third-party system.  The error indicates tridiumx.bacnet.BACnetException E_BACNET_UNRESOLVED_DEVICE_ADDRESS. Environment I/A Series R2, BACnet Cause A notification class and BACnet recipient have been configured with a BACnet device instance however an error is generated for each alarm attempt.  The error log indicates that there is an unresolved device address. tridiumx.bacnet.BACnetException E_BACNET_UNRESOLVED_DEVICE_ADDRESS   at tridiumx.bacnet.services.BACnetTransport.sendConfirmedRequestSimple (bytecode 21)   at tridiumx.bacnet.notification.BACnetNotification.sendRequest (bytecode 9)   at tridiumx.bacnet.notification.AsyncEventNotificationRequest.execute (bytecode 15)   at tridium.services.helpers.AsynchronousRequestHelper.processMsg (bytecode 4)   at tridium.services.helpers.MessageQueueHelper.run (bytecode 23)   at java.lang.Thread.run (line 5) Resolution For the alarm to work, the station must contain the associated BACnet device object for the target device.  This provides the information required to properly route the alarm (e.g. IP address, device instance, etc.).  In addition, the target device must be online and able to receive and process BACnet alarms.  Use the BACnet service BACnetUtility and learnNetwork command to create the BACnet device objects for the target devices. Additional details can be found in the I/A Series R2 BACnet Integration Reference Guide (Configuring for BACnet Alarm Generation) included with the R2 documentation.  These requirements and restrictions apply to Niagara BACnet alarm generation: Only Niagara objects that are exposed as BACnet objects can generate BACnet alarms. This means only alarms from Niagara AIs, AOs, BIs, BOs, MSIs, and MSOs can be routed to BACnet devices (Calendar and Schedule objects are not alarmable). This draws from the BACnet requirement that every alarm message must contain the BACnet object ID of its source. Only local objects in a station can generate BACnet alarms. Therefore, a Enterprise Server station cannot generate a BACnet alarm on behalf of an object in a subordinate station. If a subordinate station needs to generate a BACnet alarm, it must be configured with the BACnet service and the appropriate recipient(s). A separate BACnetRecipient must be created for each remote device to which BACnet alarms must be routed (one-to-one BACnetRecipient to device). Alarms are not regenerated. If a BACnet device is down when the Niagara system sends an alarm, the alarm is not saved for retransmission later. The Niagara system, of course, still maintains a record of the alarm in its buffer. The Niagara system does not support setting up a third-party BACnet system to receive BACnet alarms, configure its notification classes, and so forth. All alarm configuration and setup must be done using the system’s native tools.

Issue Previously the BACnet Device Id of the controller would default to the devices serial number, this is no longer possible due to the maximum BACnet Device Id being 4,194,303. Serial numbers greater than 800xxx can give an error 'Device Node id is out of range' (1 to 4,194,303) Environment Continuum BACnet Controllers Cause Concern about what the default BACnet Id will be set to a value higher than what is supported or to a value that has already been set to a previous controller. Will this conflict with existing controllers on a site when adding new controllers when all are using the default BACnet Device Id? Resolution There is an internal calculation done that uses the Serial number as a seed to then calculate the BACnet Device Id so that it falls within the 4,194,303 max. This calculated value will be unique to every other Continuum BACnet Devices default BACnet Device Id so you should be fine when newer controllers are being added to existing sites. If you want to ensure there are no address conflicts though you may want to set the value yourself when commissioning the controllers through creating the Device object manually and setting the BACnet Device Id at that time or if the device is already configured delete it from the BACnet side and then edit it from the Infinity side and enter a new and unique device id, then perform a find BACnet devices to bring the device back on the BACnet side with its new device id.