Building Automation Knowledge Base

Issue VTRA valve is leaking and requires a stuffing box Product Line Field Devices Environment VTRA Stuffing Box 080488305 0804883005 Cause The data sheet indicates that the replacement part number is 080488305, but that part number is not found. Resolution The VTRA data sheet indicate that the Stuffing Box part number is 080488305, but this incorrect. The correct part number is 080-4883-005, for ordering purposes the part number 0804883005 without the hyphens (-) may have been used.

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 Sigma 4.08, Access Class 17 to 32 do not display object values Environment Sigma 4.08 Cause In Sigma 4.08 Build 3.46.57, if an Index or Object is assigned an Access Class of 17 to 32. The object does not display a value. Resolution Request Hot Fix 3.46.86 from Product Support Services. The Hot Fix will need to be installed at each local and remote client. When the Hot Fix is deployed, each object that has been assigned an Access Class of 17 to 32 will need to be opened in Object Editor, exit, saved and finally downloaded to the controller. Single object download without opening in Object Editor or Point File download is not sufficient.

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 Tips to speed up saved searches in StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Workstation Cause Searches take a large set of objects and check them against text matching and then against conditions. The more you can eliminate before checking text or conditions the better. Resolution Whenever possible use the following methods to speed up searches Use the 'In folder' field to avoid searching too large a section of the system Do not include properties or sub-servers when they are not needed Specify the smallest subset of type you are able to. For example, if you only want Extended Trend Logs, do not use the Base Trend Log object.

Issue When installing SE7000/SE8000 Room Controllers to connect them to a BACnet MS/TP network, multiple issues can arise: Leaving the Room Controller's COM address at 254 (default value out of the box) will make the room controller undiscoverable by the front end. Choosing a Com address value between 128 to 253 will cause the front end system to convert the com address to 127, causing duplicates when working with multiple Room Controllers. Room controllers with COM address set to 0 will prevent the front end from discovering any devices Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Other Environment SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350, SE8600 Viconics branding VT8000 Series SE7000 Series Controllers, VT7000 Series Controllers, 7600, 7300, 7200 Cause Master devices, those who participate in the token-passing protocol, must be addressed from 1 to 127. Addresses from 128 to 253 are reserved for slaves who do not participate in the token passing; however, they can occupy lower addresses as well. Resolution COM address must be changed to a value in the range of 1-127.

Issue Unable to control an I/NET DO object from a TGML graphic in HTML5, works in Workstation and Java based webstation Environment WebStation Cause The data type may not be correct.  The value should be written to PvControl as either a 0 or a 1.  If this is set as a string data type, Workstation can correct for this error, but HTML5 is less forgiving. Resolution locate the line of javascript where you write the value to the bind. this is typically a setValue(bind, value) function. bind = the full bind name of the pvControl binding. value = the value that is intended to be written to the pvControl bind. One line before the setValue command, enter the line " parseFloat(value)"  - This will convert that value to float. If the value is a 0 or a 1, the setValue command will now correctly set the I/NET value.

Issue Having difficulties determining which firmware/hardware version supports which feature. Some of main questions are: Is an SE8000 compatible with an MPM's firmware Can zigbee NYCE sensors be paired with MPMs Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350, SE8600 Ex. Viconics branding VT8000 Series Cause Firmware versions are frequently updated to introduce new features Resolution   Room Controller Firmware Zigbee-Module Application MPM's Firmware Comments Lua4RC 1.0.7 N/A 2.13.4 and up A script must be uploaded via BACnet or USB cable in order to view the "LUA" Menu. ZigBee NYCE Sensors 1.0.6/1.0.7 051 - 0131R05 and up 2.13.4 and up   SE8650   1.2.0 051 - 0131R06 and up 2.17 and up   SE8600   1.0.7 051 - 0131R05 and up 2.13.4 and up   SE8300/ SER8300 1.0.7 051 - 0131R02 and up 2.12.4 and up No label on ZigBee Module 1.0.6 051 - 0131R02 and up 2.7.2 and up No label on ZigBee Module

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 SmartStruxure Lite Demo Case SSSB-SK1 and SSSB-SK2 Environment SmartStruxure Lite Demo Case Cause The part numbers SSSB-SK1 and SSSB-SK2 are no longer available for sale.  Resolution There are currently no demo cases available for sale for the SmartStruxure Lite product range. You can purchase the products and build a demo case/kit. Contact you local Schneider Electric sales offices for assistance. 

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 Reading a card on a new door and getting an Invalid Attempt in the Events Window. Environment Continuum version 1.94 and above using the Aperio Assa Abloy integration. Cause Controller running an older version of firmware as well as the version of X Driver. Resolution To resolve the issue, the following steps need to be followed: Verify that the card being used is in the database and that it does have access to the necessary door. In Continuum Explorer Window, right click the controller, select open, verify that the firmware version for the NCII if older than 2.100035 and the ACX 57XX 1.101038, then upgrade to this version. The driver is now fully supported in the ACX5740/20 firmware version 1.100042 and NCII version 2.100041 available on the Exchange site. Right Click on Comm port 1 for the ACX 57XX and Comm 2 for the NCII and verify that the latest version of X Builder is running, which is Aperio2ndGen_100022. If you don't have this then please send an e-mail to the COE support group. Once all firmware have been upgraded and re-sent to the controller, retry the card again at the door. A Valid Entry should be given once the door has been opened.

Issue Replacing a card for an individual and it does not allow the user to get access to the Elevators. Environment All versions of Continuum. Cause The Elevator string has to be activated for the new card and disabled for the old one. Resolution To resolve this issue the following steps need to be followed: Open up the Personnel Manager for that user and change the card number to 0 then apply to save. Now open up the Elevator Template and give no access and save. Open up Personnel Manager again, put in the new card number and save. Open up Elevator Template again and give access, then save.

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 Getting a Bad Card Parity error in the Live Event Viewer when using a valid finger. Environment All versions of Continuum. Cause The bit parity settings on the device was was inverted and needed to be changed. (SecureAdmin Software) Resolution To resolve this issue, the following steps needs to be followed: In Device Settings select the reader causing the errors. In the Weigand settings tab press the Custom Weigand Settings button. Then press the edit button on the custom format (Weigand 26 in this case). The Weigand Format window opens. For Weigand26 the parity mask is supposed to be Even for the first half and Odd for the second half. Somehow that was inverted. Change the Bit Position 0 mask to Even, apply and make sure the parity mask field updates. Change the Bit position 25 mask to Odd, again making sure the Parity Mask field updates. Apply the changes.

Issue Pairing SED-WIN and SED-Dor (wireless window/door contacts) with a SE8000, SE7000, and a MPM. Environment MPM SE7000 series SE8000 series Cause Quick reference / clarification Resolution The SE8000 can be paired to the wireless contacts with or without being networked to a MPM. The SE7000 must be networked to a MPM prior to being paired to wireless contacts. Always ensure the latest firmware is installed in the MPM.

Issue Is it possible to use the TAC Xenta 110-D device with room unit STR150? Environment STR150 TAC Xenta 110-D Cause It is not possible to use STR150 together with the TAC Xenta 110-D device. Resolution TAC Xenta 110-D does not support STR150.

Issue Customer has an issue where he is getting an Invalid Attempt on a card read when he tries to read a Valid card at a door. Environment All versions of Continuum. Cause The area is corrupted for that door, once it is changed to another Area it gets distributed and the card works fine. Resolution To resolve this issue, the following steps need to be done: Assign the Reader to a different Area Delete the corrupted Area Recreate the new Area Resend to the Controller

Issue Is it supported to do an export from for example StruxureWare Building Operation version1.4 and import into version 1.6? Environment StruxureWare Building Operation Cause It is always allowed to export from an earlier version and import to a later version but not the opposite way. With one exception in StruxureWare Building Operation version 1.7 exports from version 1.0, 1.1 and 1.2 will not be supported. The workaround if having a export file this old is to import it in version 1.6 and then export from there to 1.7. Resolution It is allowed to export from an earlier version and import to a later version but not the opposite way

Issue Values in graphics from Xenta and Lon devices under a Xenta 911 network are not updated. Some values show database values and some values are showed with red crosses. When clicking on the value in the graphic the value is shown correct.  Environment TAC Vista 5.9 with a Xenta 911 as Lon network interface. Cause This could happen if many Lon and Xenta devices under the Xenta 911 is offline. When Vista do a online poll for a Xenta or Lon device and don't get a reply the communication will be halted for 3 seconds because of retransmission and time outs. This would not be a problem if a Loytec interface was used as it can handle more then one communication thread at the time but the Xenta 911 only use one communication thread. In this case it is possible to see the correct value when clicking on it in the graphic as that is a user command with much higher priority than updating values in a graphic have. Resolution Try to minimize the number of offline devices which reside under a Xenta 911 network in the Vista database as these devices will slow down the communication on the Lon network.