Building Automation Knowledge Base

Issue How to determine which version of the CPU card (GCMA-112-x) of the GCM-84000 series supports the GCS, ASD, or other communication protocol. Environment GCMA-112-x, CPU printed circuit board for the GCM-84000 series Cause Cross reference purposes.  Resolution   CPU Part No. Bus Type GCMA-112-000 GCS (standard) GCMA-112-001 GCS (standard) GCMA-112-002 ASD GCMA-112-003 CCL GCMA-112-010 GIM-21000 GCMA-112-011 GIM-MTECH This table shows which version of the GCM CPU card supports the different firmware and bus types.

Issue In an I/A Series R2 (Niagara) UNC station, not able to link to the output of a SIM block, receive error "java.lang.NullPointerException". The SIM block is from a SIM-CCN, TYPE = 44. Environment I/A Series R2  UNC with the GCM driver Network 8000 SIM-CCN, containing SIM blocks with TYPE = 44 Cause The SIM-CCN, containing SIM blocks with TYPE = 44, can be  highly  "customized", so the inputs and /or outputs of the block may be "data species" that the GCM driver in the UNC does not recognize. The GCM driver has not been tested with any of the SIMs (SIM-CCN, SIM-MTECH, SIM-TRANE, SIM-YORK, LNC-100). Resolution 1. Try using appropriate Shadow Objects of type GcmAvParam, GcmDateParam, GcmDvParam, GcmEnumParam, GcmIntParam, GcmStringParam, or GcmTimeParam. 2. Try adding APT or DPT blocks to the SIM-CCN database to correctly interpret the SIM block outputs for the GCM driver in the UNC.

Issue Does Niagara G3 provide a way to route alarms from multiple ENCs to the ENS, and then send emails alarms from the ENS? Environment Niagara G3,  all versions Cause NA Resolution The alarm generated in the ENC must to be forwarded to the ENS. The following are steps for accomplishing this. It is assumed that Email service is already configured in the ENS. Drag an AlarmClass object from the Alarm Palette to the AlarmService of both the ENC and ENS. These Alarm Classes are for alarms which will be emailed. Name both the ENC and ENS AlarmClass the same. Both names must be the same. Drag a StationRecipient from the Alarm Palette to the AlarmService of the ENC. Open the property sheet of the StationRecipient Select the ENS from the Remote Station dropdown list. (must have an established NiagaraNetwork connection) - Save In the ENC AlarmService, connect the Alarm output of the Alarm Class to the StationRecipient’s Route Alarm input. Open the NiagaraNetwork of the ENS and select the ENC NiagaraStation. Expand the ENC station and select Alarms Right-click on Alarms and select Property Sheet For Alarm Class, select “Use Existing” from the dropdown list - Save Setup is now configured to send alarm email via the ENS Note: StationRecipient class receives Alarms and formats them for another station. The StationRecipient is available in the Alarm Module. This object along with AlarmClass will be used in this setup. Alarms from a remote station are routed to any "matching" AlarmClass, that is, one with identical name as the "alarmClass" field in each alarm record. If no local "matching" AlarmClass is found, the station's default AlarmClass is used.

Issue New computer hardware was provided for SIGNAL.  The SIGNAL folder from the previous hard drive was copied and pasted to the new computer's hard drive.  When SIGNAL is started, a pop-up error message appears:  User Build error, Btrieve # 910  INI path error Environment SIGNAL all versions Cause New computer hardware provided and the original floppy diskettes are not available. Resolution The following two things cause this error: Windows User Account must have administrative privileges the \windows folder must have the bti.ini and signal.ini files

Issue I/A Series G3 ASD driver Microzone II controller object point values indicate active override conditions when no overrides have been applied. Environment I/A Series G3, Microzone II, ASD, tacAsd Cause tacAsd driver / Microzone II firmware compatibility issue Resolution Due to compatibility issues, use of the tacAsd driver with Microzone II firmware below Version 2.0 will cause the associated Microzone II point values to indicate false override conditions. For proper operation, the Microzone II device firmware must be upgraded to V2.0.  The V2.0 firmware kit can be ordered using part number MZ2A-119-200.

Issue When attempting to start InVue Developer, an error message appears preventing it from proceeding: The application cannot be edited.  Process "WindowMaker" on computer "PCNAME" is editing this application. The Invue jobsite graphics and tagname database were last modified on a different computer.  Invue creates a "lock" file which prevents the application files from being changed on any other engineering computer than the original. Environment Wonderware for Intelligent Buildings (WIBS) or InVue version 1.1 Cause The application (graphics generation) was done on a different computer than the current one. Resolution In the application directory, find and delete the appedit.lok file and re-start InVue Developer.

Issue I/A Series R2 Enterprise Server station fails to start.  Error indicates "fatal boot - file is used by another process station VM." Environment I/A Series R2 Enterprise Server Cause There may be multiple stations running on the server, or write protection settings on the PC may be preventing the desired operation. Resolution Verify that only one station is running on the server (e.g. autostart). Verify that the station is not open offline when attempting to start. The Enterprise Server database and software is attempting to open, create, or write into a file as part of normal operation (e.g. config.db.lock, a properties file, etc.) and the file or directory is write protected.  Verify that all files under the Niagara directory are not set to read only or blocked for writing by the software.

Issue Getting the error message: "You may only install 3.301.529.v1 with this version of the wizard." when trying to install 529 to new UNC. WorkPlace Pro will not proceed with install. Environment Niagara R2, all versions Cause The wrong installation folder was selected in the Installation Wizard.  The nre folder was selected in place of the emb folder.   Resolution Run the Installation Wizard again this time selecting the emb folder.

Issue The Mail Service in a Niagara R2 UNC station is configured correctly however the MailRecipients are not receiving emails. The following errors appear in a Niagara R2 UNC Standard Output Window: ERROR: Cannot send mail [/Acme/services/MailService] javax.mail.SendFailedException: Sending failed;   nested exception is:     javax.mail.SendFailedException: Invalid Addresses;   nested exception is:     javax.mail.SendFailedException: 550 5.7.1 Unable to relay     at javax.mail.Transport.send0 (bytecode 611)     at javax.mail.Transport.send (bytecode 9)     at tridium.services.MailService.sendImpl (bytecode 29)     at tridium.services.MailService.checkOutbox (bytecode 101)     at tridium.services.MailService.run (bytecode 78)     at java.lang.Thread.run (line 5) Turning on the MailService debug feature reveals the follow errors: DEBUG SMTP SENT: RCPT TO: DEBUG SMTP RCVD: 550 5.7.1 Unable to relay . . Invalid Addresses johndoe@anyconmpany.net DEBUG SMTPTransport: Sending failed because of invalid destination addresses DEBUG SMTP SENT: RSET DEBUG SMTP RCVD: 250 2.0.0 Resetting DEBUG SMTP SENT: QUIT   Environment Niagara R2,  UNC-510, UNC-410, UNC-520, Enterprise Server Cause The SMTP server is not setup to forward email. In the above error message, joedoe@anyconpany.net does not have an email account on the server, so the email is not relayed. Resolution The important thing to note in both error messages is the “Unable to relay” verbiage. This indicates that the SMTP server received the email from R2. However, it can not relay it to an email address if the email account is not on the server itself. The SMTP server must be setup to relay email messages outside of its own SMTP accounts. Contact the sites IT department for assistance with this. Note: If an EmailRecipient is configured with multiple email addresses and if any one of the email addresses can not be relayed by the STMP server, then none of the emails will be sent. Not even an email with a valid address on the SMTP server itself.  

Issue After installing WorkPlace Tech Tool software version 5.8, only version 5.0 is shown in the Purchase License program product list. Environment WorkPlace Tech Tool software release 5.7.6 and later, including release 5.8 Cause The displayed list of software products shown in the Products list does not show version 5.7 or 5.8 Resolution The Purchase WorkPlace Tech Software license request program has been updated to include some additional licensing options. The licensing program product Part Number list was also revised to eliminate some confusion that has occurred in the past regarding license upgrades. The license product list now contains entries only for the major releases (4.0, 5.0, etc) instead of indicating the version that was current at the time the license product file was last updated.   One intent in this change was to eliminate the confusion regarding the need to purchase a WorkPlace Tech Tool upgrade license. When the WorkPlace Tech Tool software versions 5.7.6, 5.7.7 or 5.8 (or later 5.x.x release) has been installed on the computer, the following list shows two of the products that appear in the Purchase WorkPlace Tech Software license package list screen: WP-TECH-50     WorkPlace Tech 5 WP-TECH-50U  Workplace Tech 5 Upgrade The product code "WP-TECH-50U" is used to request a WorkPlace Tech Tool software license upgrade from release 4.0.x to any 5.x.x release of the WorkPlace Tech Tool software.  As a reminder, when ordering an upgrade license, proof of purchase of WorkPlace Tech version 4.x.x must be included with the license request form.  Suggested proof of purchase is the license request form for the previous version that was sent to the customer showing the generated unlock code. The product code "WP-TECH-50" is used to order a new customer license for any 5.x.x release of the WorkPlace Tech Tool software. Remember that a license upgrade is not required when a minor WorkPlace Tech Tool software upgrade is installed.  The major version upgrades are designated by a change in the first field of the release number, i.e., 4.0.3 is a version of major release 4.x and 5.7.6 or 5.8 are both versions of major release 5.x.x.

Issue Unable to directly launch Workbench on an I/A Series G3 ENC-SW (Soft JACE). The application continues to request new license without success. Environment I/A Series G3, ENC-SW, Soft JACE Cause Licensing Resolution The ENC-SW (Soft JACE) can only be licensed for embedded Workbench (i.e. Workbench via browser). Attempting to launch Workbench (Java Desktop Environment) will cause the software to attempt connection to the license server as the feature for direct Workbench is not included in the license.  Connect to the Soft JACE platform using the Workbench included with the Enterprise Network Server or a TIP licensed engineering workstation.

Issue I have noticed that sometimes when learning BACnet objects AVCOV and BVCOV they will show up in fault (orange).  What causes this? Environment I/A Series R2 (Niagara) Cause BACnet objects AVCOV and BVCOV are used to share data peer to peer between MNB-1000's, MNB-300's, MNB-70's, MNB-V1 and MNB-V2's controllers.  If these objects have yet to be linked to anything with Link Builder they will display in fault (orange) at the UNC. Resolution Go to Link Builder and link these objects to the desired objects in the other controller(s).  Once the link is established the fault will go away and the AVCOV or BVCOV objects at the UNC will display the value being passed.

Issue Cannot locate manuals for the ASD, DMS, GCM and MS G3 drivers. Environment I/A Series G3 (Niagara) Cause The driver documents are not included with the G3 software documents. Resolution Most of the G3 documentation is shipped with the software.  However, at the time of this publication these manuals are not included with the G3 documentation.  The best place to locate all product documentation is the Publication Zone; which can be accessed through iPortal under the Links menu.  The latest versions of these documents can be downloaded from there.

Issue When running the I/A Series R2 "Niagara App Tunneling" on a Windows 7 computer, all display fields on the LON or Serial tunnel screen are blank.  If data is entered then the form redisplayed, it comes up blank. Environment Microsoft Windows 7 Professional operating system. I/A Series R2 Niagara Application Tunneling (serial and/or LON) Cause Insufficient Windows permissions. Resolution There is no direct solution to this problem with the current version of the I/A Series R2 Niagara Application Tunneling client application, however, there is a workaround. Open the "My computer" Windows explorer window and locate the file c:\Windows\System32\natconfig.cpl.  Right-click on the natconfig.cpl file and select "Copy". Right-click on the computer desktop and select "Paste Shortcut". Rename the shortcut to "Niagara R2 Tunneling". Open the Windows Control Panel.  If the Windows Control Panel is configured as "View by Category", open the "View by" pulldown box and select "Large Icons". Locate and click on the "User Accounts" entry.  The "Make changes to your user account" window will open. Click on "Change User Account Control settings". Note the position of the notification slider.  If it has already been set to the lowest or second lowest setting, no change is needed.  If the slider is to "Always Notify" or Default (second position), use the mouse to move the slider to the third position.  Click [Ok] to exit the User Account Control window. (optional) If the Control Panel display was changed in step 5, above, change the "View by" selection to "View by Category" To run the Niagara R2 Tunneling control panel applet from the shortcut, right-click on the shortcut and select "Run as Administrator".  The current tunneling settings will then be displayed and any changes will be properly saved.

Issue WorkPlace Tech version 5.7.2 menus do not appear when the StruxureWare Building Operation workstation is installed on the same computer. Environment Computer with both WorkPlace Tech version 5.7.2 and StruxureWare Building Operation workstation installed. Cause WorkPlace Tech 5.8.2 and later support coexistence with SmartStruxure. Resolution Install WorkPlace Tech 5.8.2 or later. The proper procedure for performing this upgrade is: Uninstall StruxureWare Building Operation Install the latest version of the WorkPlace Tech Tool software. Reinstall Building Operation.

Issue When trying to backup an I/A Series R2 UNC (Niagara) station, receive an error, "*** BACKING UP: Station Name [192.168.7.242] *** FAILED: Station Name [192.168.7.242]: java.lang.NullPointerException" Environment I/A Series R2 UNC (Niagara) station Cause One cause of this error is that all of the Threads are being used. Resolution 1. Increase Thread Count from 15 to 30 (Admin Tool - Host - Edit File - System Properties) 2. Reboot the UNC

Issue The LoopSingle block in LON and BACnet controllers contains an input called OutputReference.  Is this input intended to be used only if Integral (iGain) is not used or can they be used simultaneously? Environment MNL LON Controllers MNB BACnet controllers Application programming created using any controller compatible version of the WorkPlace Tech Tool software. Cause In the Loop Single block, is the Output Reference only used if the Integral is not used or could/should they be used simultaneously?   Resolution The "Output Reference" sets the balance point for the loop, i.e., the loop output when the input matches the setpoint. The Output Reference function operates with or without integral. If Integral is being used, its calculation can and will shift the output in the same manner as if the Output Reference were specified to be zero. The Output Reference is usually set to an initial value that is expected to cause the loop to balance, for example, 50%. The loop is then tuned by widening the TR and using Integral and if needed Derivative. Once stability is achieved, the Output Reference is adjusted to match the output of the loop.  

Issue Notification Class 150 (or any Notification Class) alarms cannot be found in EVENT.EVENTHISTORY Environment I/A Series R2 Cause Notification Class 150 was not added to the Enterprise Server station and UNC station's NotificationService containers. As such, objects configured for alarming at notification class 150 will not have its alarms archived to Enterprise Server. Resolution Add a new Notification Class to the UNC station's NotificationService container. In the Notification Class properties, go to the Config tab and set the notificationClass to 150*. Copy this Notification Class and paste it into the Enterprise Server station's NotificationService container. Configure the notificationClass to 150* (the notificationClass setting does not remain when you copy and paste the Notification Class object). * This resolution does not apply just to Notification Class number 150. It applies to any Notification Class with a similar problem.

Issue I’m using Niagara WorkPlace Pro version 514 with an Echelon USB Lon adaptor and OpenLDV4.0 driver, but I’m unable to communicate a Lon network. The following message is displayed in the Standard Output Window when attempting to start the Enterprise Server: Error opening driver LON1 java.lang.Exception: ldvRead() failed - rc = 3, *************************************************************** ERROR: Cannot startService [Sys: LonWorksService [10] LonWorksService] java.lang.IllegalStateException: Unable to open lonworks driver   at tridiumx.lonworks.services.LonLinkLayer.start(LonLinkLayer.java:89)   at tridiumx.lonworks.services.LonWorksService.startService(LonWorksService.java:196)   at tridium.foundation.Sys.startServices(Sys.java:438)   at tridium.foundation.Station.startStation(Station.java:364)   at tridium.foundation.Sys.boot(Sys.java:643)   at tridium.foundation.Sys.bootLocalLoad(Sys.java:616)   at tridium.tools.StationMain.attemptBoot(StationMain.java:214)   at tridium.tools.StationMain.bootPStore(StationMain.java:181)   at tridium.tools.StationMain.doIt(StationMain.java:145)   at tridium.tools.StationMain.main(StationMain.java:262)   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)   at java.lang.reflect.Method.invoke(Unknown Source)   at tridium.nre.Nre.mainImpl(Nre.java:663)   at tridium.nre.Nre.main(Nre.java:603) tridiumx.lonworks.LonException E_LON_COMM_SERVICE_NOT_STARTED   at tridiumx.lonworks.services.LonCommService.doLonCommSendRequest(LonCommService.java:300)   at tridiumx.lonworks.services.LonCommService.lonCommSendRequest(LonCommService.java:276)   at tridiumx.lonworks.services.LonCommService.lonCommSendRequest(LonCommService.java:209)   at tridiumx.lonworks.util.Neuron.readMemory(Neuron.java:425)   at tridiumx.lonworks.util.Neuron.readMemory(Neuron.java:415)   at tridiumx.lonworks.util.Neuron.isNMAuthSet(Neuron.java:312)   at tridiumx.lonworks.util.Neuron.isNMAuthSet(Neuron.java:300)   at tridiumx.lonworks.devices.LocalLonAppDevice.verifyDevice(LocalLonAppDevice.java:935)   at tridiumx.lonworks.services.LonWorksService.stationReady(LonWorksService.java:222)   at tridium.foundation.Sys.stationReady(Sys.java:459)   at tridium.foundation.Station.startStation(Station.java:380)   at tridium.foundation.Sys.boot(Sys.java:643)   at tridium.foundation.Sys.bootLocalLoad(Sys.java:616)   at tridium.tools.StationMain.attemptBoot(StationMain.java:214)   at tridium.tools.StationMain.bootPStore(StationMain.java:181)   at tridium.tools.StationMain.doIt(StationMain.java:145)   at tridium.tools.StationMain.main(StationMain.java:262)   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)   at java.lang.reflect.Method.invoke(Unknown Source)   at tridium.nre.Nre.mainImpl(Nre.java:663)   at tridium.nre.Nre.main(Nre.java:603) MESSAGE: Station started successfully. (HTTP port=80) [/WoodMode Environment Niagara R2, WorkPlace Pro Version 514 Cause The Echelon USB Lon adaptor was first supported in Niagara R2 build 522. Resolution Niagara version 514 does not support a Lon USB adapter. If possible, upgrade to Niagara version 522 or later. In cases where upgrading is not an option and an USB adapter must be used, then the following should be applied. Stop the Enterprise Server station. Open Windows Explorer and browse to niagara.r2.301.514/nre/bin folder. Find the lon.dll file and rename it lon.dll.old. Copy the lon.dll from a later Niagara Build, i.e. 522 or later. Paste copied lon.dll to Niagara.r2.301.514/nre/bin folder. Restart the station. The Lon Service should now start and Lon communication should be established.

Issue Unable to open I/A Series R2 Workplace Pro or the R2 Admin Tool on a specific computer.  No error window popups are seen.  When you attempt to open the program, it flashes its opening screen briefly then dies. Environment I/A Series R2 WorkPlace Pro I/A Series R2 Admin tool Cause Insufficient computer memory to allow standard 1024mb to be reserved for the Java heap. Resolution To resolve this issue, you can adjust the Java heap settings in the nre.properties file. It is important that you only make the changes as detailed below. Make a backup copy of this file before proceeding. Locate the file nre.properties in \niagara\ \nre\lib Open the nre.properties file using a text editor program (Notepad). Modify the java.options=-Xmx1024MB to java.options=-Xmx768MB leaving other parameters in the file unchanged. Save, close the file and restart the software.