Building Automation Knowledge Base

Issue When submitting a license request for a G3 SoftJace installation, because the HostID provided is for an Enterprise Network Server instead of a SoftJace. Environment I/A Series G3 SoftJace version 3.7.106 I/A Series G3 SoftJace version 3.8.x Cause Installer error.  The nre.properties file is not created properly during the installation. Resolution The nre.properties file should be edited to remove the duplicate softjace product type definition. The file to be edited is c:\niagara\rel\lib\nre.properties which will contain the following text: ######################################################## # # File: nre.properties # # This file contains properties which used # the NRE launch executable # # Revision History # 17 Feb 04 Brian Original # ######################################################## # The list of options separated by spaces to pass thru to the VM java.options=-Xmx256M -XX:MaxPermSize=128M -Dfile.encoding=UTF-8 -Xss256K # This property is used to toggle how the hostid is calculated # for the current installation. If true on a Window's box, then # the hostid will be prefixed with "WinSJ" softjace=false #This is a SoftJace softjace=true To correct the issue, open the file in a text editor and delete the line that reads: softjace=false After saving the file, you can verify that the SoftJace HostID is now generated properly by using the following procedure. Open the SoftJace console window by selecting "Console" under the "TAC IA Series ENC SW" entry in the Windows start menu. In the console window enter the following command: nre -hostid Verify that the displayed HostID begins with WinSJ-  instead of Win-

Issue Cannot interface to the GE Lighting Control Panel PSLP Object nviPattern and nvoPatternFb with G3 lonGe-3.8.37.  Network variables nviPattern, nvoPatternFb, and nciChannelCfg are missing from the proxy points within the object definition. Environment I/A Series G3 - 3.8.37 Cause Network variables nviPattern, nvoPatternFb, and nciChannelCfg are based upon manufacturer types (GEPatternType and GEChType) and are not properly defined in the lonGe 3.8.37 module. The pslp object within the lonGe module generates warnings when added. WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nviPattern WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nvoPatternFb WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_0 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_1 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_2 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_3 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_4 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_5 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_6 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_7 Resolution Upgrade to lonGe-3.8.38.1.   The updated module is available for download from the Schneider Electric Download Center. https://ecobuilding.schneider-electric.com/search?documentUUID=c52247c8-921b-4f51-90cf-d8d79adc93b7&title=lonGe%203.8.38.1%20-%20G3%20Firmware

Issue What are the definitions for the enumerated value representing CTSTS (control status) for the Network 8000 MicroNet FLO2 controller? Environment IA Series G3 tacAsd driver Cause CTSTS is displayed as an enumerated value and the associated definition is not provide. Resolution The definitions for CTSTS (control status) are: Hex - Decimal - Definition 0x00 0  CAL 0x01 1  UNOFF 0x02 2  WRMUP 0x03 3  REV 0x04 4  COOL 0x05 5  CLMX 0x06 6  CLMN 0x07 7  HEAT 0x08 8  HTMX 0x09 9  HTINT 0x0A 10  FOPN 0x0B 11  FCLS 0x0C 12  FMX 0x0D 13  FMN 0x0E 14  FFAN 0x0F 15  GFOPN 0x10 16  GFCLS 0x11 17  FGMX 0x12 18  GFMN 0x13 19  CALDP 0x14 20  DIAG

Issue Integrating a SE7200F5045E to Niagara G3 / AX. The tenant can change the occupied heating or cooling setpoint locally.  Which snvt can be used to display the current setpoint? Environment Niagara G3 Niagara R2 SE7200 series Cause Application question - wants to plot the proper setpoint on the graphic Resolution The nciSetpts snvt displays the current setpoints used by the SE7200 for heating and cooling in both occupied and unoccupied modes. Note:  The tenant can only change the occupied heating and cooling setpoints from the local keypad / display.

Issue A job site is being retrofitted for SmartStruxure. It currently uses Network 8000. When the GCM is removed, the existing MicroFlo II controllers must control individually until a SmartStruxure AS is ready. Can the EMSCO attribute be used to switch to local control until the AS is online? Product Line TAC IA Series Environment Network 8000 MicroFlo II controller Cause Standalone control requirements Resolution From the MicroFlo II Engineering Manual (F-23119): EMS CONTROL [EMSCO] * default = OFF If this input is ON, the MICROFLO II controller will operate from the GCM's setpoints. If this input is OFF, the local setpoints are used. If the input goes ABNORMAL or NOT ACTIVE the controller will treat it as an OFF. Under typical operation, EMSCO is ON and setpoints from the GCM are used. The moment it switches to OFF (ie: loss of communication to a GCM), the local setpoints will be used. At this job site, ensure the local setpoints are identical to the GCM-based setpoints so that when the GCM is removed and EMSCO switches to OFF, the MicroFlo II continues to control. This will provide temporary control until an AS is brought online. There are other 'EMS'-based attributes that should also be reviewed depending on how applicable they are to VAV control at a job site. See the engineering manual for more information.

Issue Does the Niagara R2 Transition Tool convert graphics? Environment Niagara R2 StruxureWare Building Operation Cause Product inquiry Resolution The tool does not convert graphical images.  It does convert bindings to inputs of a GxPage.  See the R2 Transition Guide (F-27835) for more details.  An excerpt from the guide follows: 3.4.3 GxPage The TAC I/A Series R2 GxPage object is converted to a Building Operation Graphic object. The converted Graphic object contains a Dynamic Text object for each dynamic Gx object at the coordinates of the corresponding Gx object from the GxPage. The Dynamic Text objects in the Building Operation Graphic are named to match the corresponding Gx objects from the GxPage. Graphical images from the GxPage are not converted to the Building Operation database. Bindings to inputs of the GxPage are converted to the Building Operation database as links to the corresponding Dynamic Text objects within the converted Graphic.

Issue Niagara R2 Transition Tool list of R2 Functionality that transitions and does not transition Product Line EcoStruxure Building Operation, TAC IA Series Environment Niagara R2 StruxureWare Building Operation Cause Quick Reference Resolution From page 15 of the R2 Transition Tool Guide (F-27835): TAC I/A Series R2 Functionality That is Transitioned Certain functionality is transitioned to Building Operation: Common control functions BACnet/IP network BACnet MS/TP networks 1 and 2 BACnet MS/TP networks 3 and 4 as routed networks BACnet device objects BACnet shadow objects Container and object tree structure LonWorks Service LonWorks networks LonWorks device objects V2.x Standard MNL LON devices V3.x Standard MNL LON devices V4.x Standard MNL LON devices and associated application files MNL-800 LON devices and associated application files R2 Local LON Device SNVTs Many type conversion, LON multiplexer and demultiplexer objects IbsASDNetwork Service ASD network ASD Device objects TAC I/A Series R2 Functionality Not Transitioned Not all UNC functionality can be transitioned to Building Operation. This functionality is listed in the Objects report. Functionality that is not transitioned includes: BACnet Ethernet network User accounts Address book Security Trigger mechanisms TRIPL program object runtime Object bundling Command objects Right-click commands Communications other than BACnet, ASD, or LonWorks Configurable routers and repeaters LON manufacturer specific control and conversion objects External LON Network Management Tool support UNC physical points (UNC-410 NDIO)

Issue Does the MNB-1000 have a point archiving feature? Environment MNB-1000 (all firmware revisions) Cause Field request (for troubleshooting) Resolution The MNB-1000 does not come with any point archiving features.  That would have to be provided at the network level (i.e. SmartStruxure AS).

Issue The sending MicroSmart controller has revision 9 firmware.  The receiving MicroSmart controllers have revision 10 and revision 11 firmware.  How can a point value be broadcast? Environment MicroSmart controllers Cause Peer-to-peer sharing of data was introduced to the MicroSmart controllers with revision 10 firmware. In this scenario, the revision 9 controller cannot broadcast (or receive) peer-to-peer. Resolution Link the sending point and the receiving points to the DMS. Depending on the programming, use the sending DMS point with the receiving DMS point and the value will be available down in the MicroSmart controller.

Issue WorkPlace Tech will not recognize the Echelon U10 USB Lon Network Interface adapter. The “Loading Device Driver” is displayed but nothing happens after that. Environment WorkPlace Tech 5.8.x Cause LON1 port may have been previously assigned to another LON interface. Resolution 1. Make sure the Echelon Open LVD 4.0 is installed on PC. 2. Close WorkPlace Tech if open 3. Disconnect the Echelon Lon USB adapter from the PC. 4. Open Control Panel and open LonWorks Interfaces 5. Select View from the Menu and check “Show Detached Interfaces” 6. Highlight LON1 in the tree and click the “Remove” from the menu        - Click Yes in the “Confirm Removal” window to remove the detach device 7. While in same widow, reconnect the Echelon USB Lon Adapter to the PC        - The messages: “Installing device driver” will display in the system tray followed by “Echelon USB Network Interface Installed.        - The LON1 interface should now be displayed You can test the communication if you like Now open WorkPlace Tech and you should be able to discover the LON devices.  

Issue Getting an "Invalid status code: 401 Access Denied" error when doing a "Save Runtime DB" of the localhost or a "Get" to save a remote UNC station to the localhost. The errors read: Error when doing a “Save Runtime DB” of localhost station:  tridium.nre.net.HttpException: Invalid status code: 401 (Access denied)            at tridium.ui.admintool.DbAdminConfigPanel.doRemoteBackup(DbAdminConfigPanel.java:1100)            at tridium.ui.admintool.DbAdminConfigPanel$Worker.run(DbAdminConfigPanel.java:1224) Error when doing a “Get” of a remote UNC station:            java.io.FileNotFoundException: c:\niagara\r2.301.535\stations\anystation\config.sns (Access is denied)            at java.io.FileOutputStream.open(Native Method)            at java.io.FileOutputStream.(Unknown Source)            at java.io.FileOutputStream.(Unknown Source)            at tridium.ui.admintool.DbAdminConfigPanel.doOnlineGet(DbAdminConfigPanel.java:848)            at tridium.ui.admintool.DbAdminConfigPanel.doGet(DbAdminConfigPanel.java:764)            at tridium.ui.admintool.DbAdminConfigPanel$Worker.run(DbAdminConfigPanel.java:1216) Product Line TAC IA Series Environment WorkPlace Pro ES UNC Cause Either the username or password, or both, being used are invalid. A valid username and password must be entered to perform a "Save Runtime DB" of the localhost, or a "Get" to save a remote station to the localhost. Resolution Use a valid station username and password to perform these functions on the localhost.  

Issue Can R2 BACnet alarms be sent to and acknowledged from a G3 Server console. Environment Niagara R2 UNC, Niagara G3 ENS Cause Want to be able to view and acknowledge R2 BACnet Alarms from in a G3 console. Resolution This can be accomplished by using the BACnetRecipient object in R2. Follow the steps listed in the “Configuring for BACnet Alarm Generation” section of the R2 BACnet Integration Reference guide. The part most forget is adding the G3 station as a BACnet device under the R2 BACnetService, and adding the UNCs as a BACnet device under the G3 NiagaraNetwork  

Issue G3 station will not email alarms to intended recipients. Getting “java.security.cert.CertificateException: failed certificate validation” error in the station Application Director window. The error reads: mail.MessagingException: Could not connect to SMTP host: outbound.att.net, port: 465; nested exception is: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: failed certificate validation, at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1972) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:642) at javax.mail.Service.connect(Service.java:317) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.baja.email.BOutgoingAccount.pollQueue(BOutgoingAccount.java:769) at javax.baja.email.BOutgoingAccount.poll(BOutgoingAccount.java:715) at javax.baja.email.BEmailAccount.doPoll(BEmailAccount.java:567) at javax.baja.email.BEmailAccount.access$0(BEmailAccount.java:36) at javax.baja.email.BEmailAccount$Poller.run(BEmailAccount.java:617) Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: failed certificate validation, at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1884) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868) at sun.security.ssl.Handshaker.process_record(Handshaker.java:804) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1323) at com.tridium.crypto.core.io.CryptoCoreClientSocketFactory$NSSLSocket.startHandshake(CryptoCoreClientSocketFactory.java:334) at com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:548) at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:352) at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:207) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1938)   Environment Niagara G3 3.8.37, ENS, ENC Cause The security certificate for the SMTP server has not been accepted/approved. This error was seen when attempting to connect to the outbound.att.net SMTP server. It may apply to other SMTP server as well. Resolution Check to see if there’s a certificate for the mail server and if it has been approved. - Open the station’s Platform and select ‘Certificate Management’. - Select the Allowed Hosts tab. - Look for host named ‘outbound.att.net’ (it’s probably has not been approved) - Right-click on it and select ‘Approve’ - Select ‘Yes’ for the messages ‘Are you sure you want to approve the selected exemption(s)?’ To send or clear queued emails: - Double-click on the station’s ‘EmailService’ - Right-click on the OutgoingAccount and select ‘Actions’ and then ‘Send’ or ‘Clear Alarms’ If it was a certificate issue, you should now be able to send emails to the SMTP server.  

Issue One graphic is not the same on the InVue client computer as it is on the InVue server.  InVue Viewer has been re-started on the client computer which initiates an automatic file transfer from the server.  But the graphic is still different.  How can the graphic be updated on the client? Environment InVue Cause The graphic is not considered a 'modified' graphic so it doesn't automatically transfer to the client computer. Resolution Open InVue Developer and modify the graphic slightly and then save it.  Use 'Notify Clients' under the 'Special' dropdown to propagate the modified graphic to the client computer.

Issue When converting a station from R2 v522 to v535 getting error: "Link is not valid: Link invalid for unknown reason". Environment R2 UNC and WPP Cause The v535 LonExtras jar is not correctly handling converting  links that reference SNVT type FlexSnvtTempSetpts. Resolution Download and Install the v532a LonExtras jars in WPP.   Convert the station successfully then install v532a lonExtras jar and the station in the UNC.

Issue Can WorkPlace Tech operate on a pc with a local Windows account not assigned administrative privileges? Environment WorkPlace Tech 5.8 Cause A customer wants to assign non-administrative Windows accounts to the maintenance staff. Resolution A local Windows account with Power User rights has worked with the basic commands in WorkPlace Tech (i.e. upload, download, save, edit, and compile).  Extensive testing has not been done.  Schneider-Electric continues to recommend local Windows accounts with administrative privileges.

Issue G3 station will not email alarms to intended ATT email recipient. “Authentication errors” are being displayed in the station’s Application Director Window. Environment Niagara G3 3.8.37, ENS, ENC Cause The ATT email account being used is a new account. It had never been signed onto to complete its setup configuration. The account needs to be setup first before it can receive emails. Resolution Sign-on to the new ATT user account via ATT’s email portal and complete the setup process for the new account. Open Niagara and try resend emails. To send Queued Emails: - Double-click on the station’s ‘EmailService’ - Right-click on the OutgoingAccount and select ‘Actions’ and then ‘Send’ or ‘Clear Alarms’ If it was an issue with the new account not being initialized, you should now be able to send now.

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 How do I put a different application in an existing MNL controller under an AS? Environment AS with MNL controllers Cause An incorrect application has been installed in a device. Resolution First, the correct application must exist in the WorkPlace Tech editor list.   Expand the System Tree to expose the MNL device to be changed and the Application file under it.  Right click on Application and select delete.  Now right click on the MNL controller select MNL and Assign application and assign the correct application from the list. Once assigned right click on the controller select MNL and select Download application.

Issue Site has no server, just a single stand-alone jace.  It has histories.  How can the data be exported? Environment Niagara G3 / AX any jace model running version 3.x Cause Viewing historical data without the benefits of an Enterprise Server Resolution Do a manual export from the 'History Table' view: Expand the history space in the tree. Select the history to export. Right click and select View-> 'History Table'. Look over on the upper right corner of the history table. There is the tiny icon that looks kind of like a table with a little upside down triangle. Click that. Select Export. Then select the exporter in the drop down -  HistoryTable to CSV. Select 'Save to File' and then browse to a folder and enter a desired file name. Press OK.

Issue Customer site is currently installed with Niagara R2.  A defective UNC has been replaced with the hybrid jace (-603 or -645) and is running the Niagara R2 station from the UNC. In the future, if the customer converts the building to Niagara G3 / AX, what has to be done to the jace to convert it from R2 to G3? Environment Niagara R2 Niagara G3 / AX jace-603 jace-645 Cause Future considerations Resolution If the site upgrades to Niagara G3 / AX, the customer orders part # TRD-G3-6XX for the hybrid jace. This will transfer the R2 license to the G3 environment. It will include any optional drivers (like Modbus) as well as Schneider-Electric proprietary drivers (like ibsASD).  Physically, the board remains as is.