Building Automation Knowledge Base

Issue Customer has received some MNB-300 bases that have green connectors instead of the usual blue ones.  Are they interchangeable? Environment I/A Series MNB-1000, MNB-1000-15, MNB-70, MNB-300 and associated base part numbers MNB-BASE-15, MNB-BASE-1000 or MNB-BASE-300 Cause Manufacturing parts procurement variations. Resolution Bases are  fully interchangeable with other bases of the same part number, regardless of the color of the I/O colors. This color variation does not apply to the power or communications connectors.   Power is always a three-pin Green connector.   BACnet-MS/TP is always a three-pin orange connector.  MNB-1000-15 communications trunk and corresponding connector on the MNB-1000 is  three-pin Black connector.

Issue Request for Schneider Electric replacement actuator Environment Belimo BF24-T damper actuator Cause Customer wants to replace Belimo actuator with Schneider Electric equivalent Resolution Unfortunately, Schneider Electric does not have any matching actuator.

Issue Calendar entries from 3rd party BACnet devices viewable in WebStation Environment StruxureWare 1.1.0.362 Cause Are calendar entries from 3rd party BACnet devices viewable in WebStation? For calendar entries from third party devices that were not created through StruxureWare Building Operation, they are not shown in WebStation. For example: When integrated a 3rd party BACnet device in StruxureWare Building Operation the integrator of this device created a calendar object on their side. Also created are so sample entries like 24th of December. When uploaded this device and viewing the calendar from the Workstation everything was fine but when viewing WebStation, the calendar entries that were created from the integrator are not shown. Resolution In Webstation 1.1 we only support Single date exceptions. We will support date range and calculated events in 1.2.  

Issue CX controller going offline or exhibits intermittent communications problem. When the Infinet bus is disconnected from the controller the problem goes away. Environment All CX controllers that support Infinet field bus. Cause Malfunctioning infinet device disrupts the Infinet bus and brings down parent CX controller. Resolution Follow standard Infinet troubleshooting techniques to identify offending field bus device and remove/replace.

Issue Importing personnel object gives attribute name error. Environment CyberStation Cause Info1 - Info6 attributes were renamed, the export file contains the new attribute names. Resolution During the import process the system expects the original attribute names. Edit the export file and change names back to info1-info6.

Issue In Niagara G3, how can an ENC be diagnosed as overloaded? Environment Niagara G3 ENC-410 Niagara G3 ENC-520 Jace-6 Cause Programming guidelines needed to prevent overloading the ENC. Resolution The CPU usage should be less than 80% on a continuous basis. The heap.used should be less than 75% of the heap.max value.  Java heap is comprised of station objects operating under runtime conditions.  Objects are created as needed and destroyed via garbage collection (GC) when no longer needed.  Garbage collection is a mechanism provided by the Java Virtual Machine (JVM) to reclaim heap space from objects eligible for collection.  An object becomes eligible for garbage collection if its not reachable from any live threads or any static references (e.g. all references are null). A heap ratio (heap used to heap max) that exceeds 75% causes the JVM to allocate additional time to perform garbage collection and cleanup.  This in turn begins to increase CPU usage which slows down overall station processing and performance.  Eventually, a station watchdog can occur if the processing becomes too slow rebooting the unit due to a watchdog timeout. Note: Make sure to execute or manually trigger a garbage collection prior to evaluating the heap.max value. Using Workbench, right-click on the connected station and select Spy from the drop down menu.  Select util and gc to execute the garbage collection. Methods to decrease heap used: Removing objects from the station logic that may not be required. Reviewing custom objects or programs that may be memory hogs. Use of a controller with additional maximum heap.  The max heap of a ENC-410 or ENC-520 (non-extended memory 128 MB RAM version) is 48 MB.  The extended memory ENC-410 and ENC-520 versions increase the RAM to 256 MB and the maximum heap to 96 MB. The JACE-6E can be purchased with the extended memory option to increase the heap to 96 MB. Add another ENC or JACE controller. Histories can also affect the heap.used value. When the station needs to write a record to a history, it opens the specific history into the running station from the file system if PC based or the ram disk if QNX-based.  The open history does contribute to the heap.used of the station.  Remove unnecessary or unused histories by disabling the history within the extension, removing the associated history file, and removing the history extension.

Issue What do the LEDs indicate on a MSC-NC or MSC-NCM? Environment DMS Cause Communications is down on a jobsite.  Trying to troubleshoot the MSC-NCM. Resolution Here is the function of each LED: WDT:  indicates processor and MSC-NCM communication status.  One blink/second indicates that the MSC-NCM is communicating with at least one Microsmart controller.  Two blinks/second indicate that the MSC-NCM processor is functioning but the MSC-NCM is not communicating with any controllers.  If it is blinking very fast, the MSC-NCM processor is functioning but the MSC-NCM program has not been downloaded into the controller (hence, the system is down). ALARM:  indicates a service or point alarm condition exists somewhere on the controller trunk TxD:  indicates data transmitted RxD:  indicates data received DCD:  illuminates when the Data Carrier Detect signal is active (used with modems) RING:  illuminates when the modem detects an incoming call

Issue What type of surge protection comes with a MNB controller? (e.g. from a lightning strike) Environment MNB controllers Cause Job specification requirement Resolution All of the MNB controllers are tested to the IEC EN 61000 standard which is a rigid test for surge protection where all I/O, Power, and Communications are subjected to a 20KV surge. During design, this normally results in having to add in extra protection so as to pass the test. Communications within the controllers have optical isolation which protects the communications transceivers to transients.  

Issue How to run a controller program (InfinetProgram) when the controller first starts up? Environment Continuum Controllers Plain English Cause Need to be able to set specific parameters at startup time of the controller. For example, with a VAV controller, you may want to re-calibrate the closed position of a damper by having this done at power up. This will allow just a power cycle of the controller after been serviced locally. Resolution Have a program run at start-up of the controller that resets any required parameters back to default values. To do this, create a Program that sets these values and then configure that Program with a FlowType of 'FallThru' and with AutoStart set to 'True'. This will run the program only once at start-up of the controller.  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Reloading ACX2/NC2 produces error when reloading the following system variables AllowedCreds PersRecordCount PIVReaderFormat Environment CyberStation ACX5720 ACX5740 CX9680 Cause The system variables in question (AllowedCreds, PersRecordCount, PIVReaderFormat) only apply to versions 1.1xxxxx and 2.1xxxxx of the ACX2 and NC2 respectively. Resolution Make sure the controller is running the appropriate version of the firmware. If the problem persists even with the correct firmware version then... Export the controller to text file Edit the dump file and remove ALL system variables Delete the controller Import the file to re-create the controller (the system variables will be created when the controller is created) Reload the controller, the errors should not longer appear.

Issue Have a site that is located at 4000m + above sea level and concerned that they may be affected by being located at this high altitude. Environment Continuum controllers Cause Specification sheets for Continuum controllers do not specify altitude in Operation Environment. Resolution We do not do any specific testing for this but there should be no problems with our controllers working at different altitudes.  The only controllers that need any special considerations are VAV controllers that have an on-board Differential Pressure sensor for calculating Airflow. The Kavlico Airflow Sensor itself is not affected by altitude but the factor in the airflow calculation will need to be modified. User programs which convert Pressure readings to Air Velocity WILL be affected; there is a factor in this calculation which will change, depending on altitude. The VAV box manufacturers should be able to provide more detail on what this needs to be at your specific sites elevation.

Issue A local Sigma client does not display the background image of a Graphic, but a remote Sigma client does. Environment Local client Remote client Background Graphic Cause If a large image (bmp or jpg) has been used as the background in a Sigma graphic, the local client does not display the picture, but a remote clients or web clients do. Resolution Some older machines, because of their graphics capabilities cannot display some Sigma graphics. Netbooks or laptops may also have a similar issue. Users may also experience poor performance when opening graphics, animations and editing graphics. In a lot of cases it will be possible to purchase a graphics adapter card that can display these graphics, but where this is not the case the size of the graphics files will need to be reduced in order to display the graphics correctly. The recommended replacement Graphics adapter is as follows;  1GB graphics adapter which supports the appropriate version of DirectX (DirectX 11 for Windows 7 family). It should be noted that it will not always be possible to buy a graphics adapter that will be compatible with the specific machine that has the problem. In this case the PC should be replaced with a better specification machine.  To summarise.. Servers and Netbook computers will not be supported for Sigma Clients. A suitable graphics card will be required as specified above to display Sigma Graphics. Users may need to reduce the size of the graphics files where a suitable graphics card cannot be installed. Most modern workstation computers will be capable of displaying Sigma graphics. Most server machines will not be capable of displaying sigma graphics.

Issue Remote Alarm Manager running with TAC Vista loses the connection to the license file. Environment RAM pre 2.1 Remote Alarm Manager License file Cause Remote Alarm Manager fails to recover after its license management briefly loses a valid license from the TAC license server Resolution This issue is now corrected by installing the RAM Software Release 2.1 Then follow the upgrade options in the RAM Release 2.1 Release Notes documentation.

Issue Communications with the controllers is very slow. Environment Slow communications Displaying objects seem to lock up Globals V53 hardware Cause Communications with the controllers is very slow. Objects will display correctly once, but if the display is carried out several times, or if an object is overridden, the server appears to lockup. Resolution The issue was caused by two Sigma objects being globally transmitted at the rate of 12 per second. The two objects were Programmable and the programme had been incorrectly written as follows; 10 IF POINT 0|108 = 0.000000 THEN RETURN "Ch1  Off" 20 IF POINT 0|108 = 1.00000 THEN RETURN "Ch1 Start" 30 IF POINT 0|108 = 2.00000 THEN RETURN "Ch1 Running" 40 IF POINT 0|108 = 3.00000 THEN RETURN "Ch1 Shutdown" 50 IF POINT 0|108 = 4.00000 THEN RETURN "Ch1 Service" The above object is incorrect because it does not specify True or False. Because globals are transmitted on "change of state" the global was being transmitted with every scan of the object file. It is recommended that the object is changed as follows. 10 IF POINT 0|108 = 0.000000 THEN RETURN FALSE "Ch1  Off" 20 IF POINT 0|108 = 1.00000 THEN RETURN TRUE "Ch1 Start" 30 IF POINT 0|108 = 2.00000 THEN RETURN TRUE "Ch1 Running" 40 IF POINT 0|108 = 3.00000 THEN RETURN TRUE "Ch1 Shutdown" 50 IF POINT 0|108 = 4.00000 THEN RETURN TRUE "Ch1 Service"

Issue Will the Bond Sensor Input Channel contribute to the Door Forced and Door Ajar alarms? If so, does it have to be in conjunction with the Door Switch Input Channel? Environment Continuum Access Control Products CX9900 CX9680 AC1, AC1A, AC1Plus ACX5720, ACX5740 CX9702 ACX781 Cause Not sure how the Bond Sensor works in relation to the Door Switch and the various Door Alarm states. Resolution BondFailure is an attribute of the Door object that represents a fault with the Bond Sensor. The way this works is if Valid Access = True and the Door Switch = Open and the Bond Sensor = Open, then BondFailure = False. If Valid Access = False or the system sees the Door Switch = Closed but the Bond Sensor = Open then you will get a BondFailure = True. This is another attribute (BondFailure) that can be monitored with an AlarmEnrollment in addition to the DoorForced and DoorAjar attributes. A Door Switch needs to be used for the Bond Sensor to operate correctly, otherwise BondFailure will always be False after a ValidAccess if there is no Door Switch value. Note: The actual value of the BondSensor attribute in the Door object may not seem to update properly if monitoring with a ListView. For this to show the correct BondSensor value make sure that the attribute Source is set to "Live" instead of the default "Database". Note2: A bond senor (usually an output from a maglock) should not be used as an alternative to a door switch, as it does not give indication of the door position.  

Issue The Application Director output window displays an Engine Watchdog Timeout by issuing a thread dump and displaying App Failed.  This condition can occur when installing an upgraded station, after a reboot of the existing station, or during normal station operation. Environment I/A Series G3, Niagara Cause The software watchdog mechanism is designed to periodically report the station's engine cycle count to the platform daemon.  The main purpose is to detect and restart a "stalled" station when the control engine is believed to be in a deadlocked condition.  If the station’s engine cycle count stops changing and/or the station does not report a cycle count to the platform daemon within this defined period, the platform daemon causes the VM to generate a stack dump for diagnostic purposes, then takes the action defined by the Engine Watchdog Policy. Depending upon station operation, the watchdog timeout may need to be increased to compensate for transient conditions where the NRE engine thread is temporarily busy during a single execution cycle.  These conditions include simultaneous execution of multiple objects or point extensions that occur on the same time interval, archiving of log history, custom objects, etc. during normal operation.  The default timeout is 1 minute. Resolution Tuning may be required (increase of the default watchdog timeout value). Open the running station, expand Config, expand Services, right click PlatformServices - View - Platform Service Container Plugin, locate the Engine Watchdog Timeout property.  Increase the value by 30 second or 1 minute increments and monitor controller operation (adjust as required).  If the condition continues, contact Schneider Electric Product Support for further assistance. Watchdog policy selections include: Log Only — Generates stack dump and logs an error message in the system log.   Terminate — (Default) Kills the VM process. If “restart on failure” is enabled for the station (typical), the station is restarted.   Reboot — Automatically reboots the host JACE platform. If “auto-start” is enabled for the station, the station is restarted after the system reboots.   Engine Watchdog Timeout — Default is 1 minute, and range is from 0 ms to infinity.

Issue Communication Port does not come online in Vista Classic.  The port is correctly configured in Vista and Device Manager reports it as working correctly. Environment Vista Loytec NIC-USB Loytec NIC-709 Echelon PCLTA Echelon U10 Echelon U20 Lonworks network Cause The communication port must be connected to a Lonworks network before either object will appear online in Vista.  When the communication port is first created it will appear offline even if it is correctly configured. Resolution 1.  Create a communication port object in Vista Classic and configure it according to the manufacturers recommendations.  It will appear offline in Vista at this point. 2.  In Vista 4.5 and above, right-click on the communication port and select New>Device>Lonworks Network. 3.  In the Wizard which pops up, tick the box 'Use existing port/server. 4.  Ensure that the correct port is selected in the drop-down list. 5.  Click 'Finish' 6.  In Vista press F5 to refresh the display.  Both communication port and network are now online (green)

Issue When connecting the dongle, no driver is found and dongle does not work as supposed Environment TAC Vista Windows Hardware USB dongle 000857510 Cause No driver found when connecting dongle to PC, and no separate driver is available for download from Extranet or other source. Resolution The driver is included in the Windows driver package. If the dongle is not recognized correctly when connected, run a Windows Update with the dongle still in place. The correct driver will then be installed.

Issue An attempt was made to modify the protocol service type attribute, and that attribute was not specified as configurable. Environment Vista LonMaker SNVT binding types Cause For network variables, the service type can be specified in the connection information in the Neuron C variable declaration. The options are unackd, nackd_rpt and ackd. The keyword config is the default. This allows a network management tool to change the service specification at installation time. The keyword nonconfig indicates that the service type cannot be changed by a network management tool. Resolution Echelon requests to please refer to the Neuron C Reference Guide for more information. To see which binding type is necessary, open the .XIF in a text editor and look for the following definition: XIF Definition of Line 2, Field 5: Default service type to use for connections containing this variable. Set to 0 for acknowledged, 1 for repeated, or 2 for unacknowledged. Created bindings needs to match the type defined in the XIF file.  Right click on the SNVT and go to properties.  Go to binding type.  Ensure binding type is the same, i.e. you cannot bind a Repeated SNVT type to a point that was flagged for only Acknowledged bindings. 

Issue Is the an M-bus (meter bus) driver for UNC's? Environment UNC, I/A Series, niagara Cause Not applicable Resolution An M-bus driver does not exist for the R2 system.  There is a driver available in the G3 system.