Building Automation Knowledge Base

Issue No Access events reported by controller on list view, event view or door access event tab, AccessLog has value of 0 Environment CyberStation ACX2 NC2 Cause The Access Server system value was set to an incorrect value. The value should be either... 1. CyberStation id value (191-254) to enable remote validation 2. The same as the ACCId of the controller. (to disable remote validation) In the case at hand the AccNetId of the ACX5740 was 19 but the AccessServer was set to 48. Resolution Set the AccessServer system variable to the correct value.

Issue Cannot establish CANbus communication between MPM controllers.   Environment MPM controllers, any version Cause The CANbus trunk is missing the end of line resistors on the two end MPM controllers.  Each of the MPM controllers which are at the end of the CANbus trunk must have an 120 ohm resistor installed. Resolution Install a 120 ohm resistor at both ends of the CANbus trunk.

Issue Unable to use Windows domain login to WebReports. Environment StruxureWare Building Operation WebReports Cause Windows domain login is not currently a feature that can be used with WebReports. Resolution The use of Windows domain login to WebReports has been entered as a future enhancement request but it is not currently assigned to a version.  UPDATE: As of EBO 2.0 the change request has NOT yet been implemented.

Issue Cannot discover wireless devices in MPM controller. Environment MPM controllers, any version Cause The Pan ID was set correct under the ZigBee Configuration property.  However when viewing the Pan ID setting under ZigBee Configuration, the Pan ID entered in the Settings box does not match the one displayed in the Current Configuration box.  The Zigbee Configuration Pan ID has somehow become corrupted. Resolution Reboot the MPM controller.  If a reboot does not clear the issue then the controller will have to be restored to factory default settings.  - Backup the MPM controller and then restore the MPM back to its original factory setting.

Issue Having trouble getting the stand-alone system to start-up Environment SmartStruxure Lite Multi-Purpose Manager Cause Communication between the SEZ7656 (Master) and one or multiple SEZ7260 (Slave) cannot be established Resolution 1 - SEZ7000 BACnet network commissioning (quick start-up) :   SEZ7656(E,F,H,R)1000B                       Rooftop controller: 1.  Press & hold (MENU) key until you see "Pswrd Set" 2.  Press (NO) to go to next parameter 3.  Leave "RTC MAC" to (4) 4.  Change "RTC Baud" to (38400) then press (YES) 5.  Press (NO), press (MENU), "Exit Menu" press (YES) 6. Get the installation manual, go through all the configuration parameters, take note of the required parameters per your application then repeat steps 1. and 2. enter your configuration parameters in the rooftop controller   Reference manuals:            II-SE7000-SEZ7656E-A4.EN.4.2013.v1               II-SE7000-SEZ7656F1045B-A4.EN.4.2013.v1               II-SE7000-BNETRTU-A4.EN.4.2013.v1     SEZ72(60)x5000B                                 Zone thermostats: 1.  Press & hold (Override) key until you see "Pswrd Set" 2.  Press (Override) to go to next parameter 3.  Set “Zone MAC” to 11 on the 1 st thermostat, then 12, 13, … 4.  Change "Zone Baud" to (38400) on all thermostats 5.  Leave Get From at (255) 6.  Leave "RTC MAC" to (4) on all thermostats 7.  Let the thermostat reset 8.  Within a minute the thermostat will display the outside air temperature, this confirms communication with RTU controller (OAT sensor must be connected to the RTU controller) 9.  Get the installation manual, go through all the configuration parameters, take note of the required parameters per your application then repeat steps 1. and 2. enter your configuration parameters in the zone controller   Reference manual:              II-SE7000-SEZ7260X-A4.EN.4.2013.vi   ----------------------------------------------------------------------------------------------------------------------------------------------   SEZ7000 ZigBee network commissioning (quick start-up) :   SEZ7656(E,F,H,R)1000W                      Rooftop controller: 1.    Press & hold (MENU) key until you see "Pswrd Set" 2.    Press (NO) to go to next parameter 3.    Leave "RTC MAC" to (4) 4.    Set “PAN ID” to (1) 5.    Change "Channel" to (15) 6.    Press (NO), press (MENU), "Exit Menu" press (YES) 7.    Get the installation manual, go through all the configuration parameters, take note of the required parameters per your application then repeat steps 1. and 2. enter your configuration parameters in the rooftop controller   Reference manuals:            II-SE7000-SEZ7656E1045W-A4.EN.1.2013.v1                II-SE7000-SEZ7656F1045W-A4.EN.4.2013.v1                II-SE7000-WRTU-A4.EN.4.2013.v1     SEZ72(60)x5000W                    Zone thermostats: 1.    Press & hold (Override) key until you see "Pswrd Set" 2.    Press (Override) to go to next parameter 3.    Set “Zone MAC” to 11 on the 1 st thermostat, then 12, 13, … 4.    Set “PAN ID” to (1) on all thermostats 5.    Change "Channel" to (15) on all thermostats 6.    Leave “Get From” at (255) 7.    Leave "RTC MAC" to (4) on all thermostats 8.    Let the thermostat reset 9.    Within a minute the thermostat will display the outside air temperature, this confirms communication with RTU controller (OAT sensor must be connected to the RTU controller) 10.   Get the installation manual, go through all the configuration parameters, take note of the required parameters per your application then repeat steps 1. and 2. enter your configuration parameters in the zone controller   Reference manual:              II-SE7000-SEZ7260X5x45W-US.EN.4.2013.v1   ----------------------------------------------------------------------------------------------------------------------------------------------   2 - SEZ7000 Troubleshooting :   Com Lost:       BACnet/ZigBee:                        Ensure RTU and Zone thermostats are compatible:             - Old models:                            SEZ7656(B)1000x only work with SEZ72(00)x5000x             - Current models:                      SEZ7656(E,F,H,R)1000x only work with SEZ72(60)x5000x   Ensure all thermostats have a unique MAC address.  If "RTC MAC" = 4, none of the Zone thermostats can use Zone MAC = 4     BACnet network wiring: -Daisy-chain only, no "T" connections -Use (+) and (-) terminals only, never use (REF) terminal -Use 2-22 low-capacitance shielded communication cable, attach shield at every junctions, tape and push back in the wall, only ground one side of the network -Install End-Of-Line, 1/4 watt, 120 Ohm resistor on both ends of network, install across (+) & (-) terminals)     3 - SEZ7260         FAQ's Q.   I only have access to the first few configuration parameters in the SEZ7260 zone thermostats. A.    Set "Get From" parameter to 255.   Q.   Some SEZ7200 don’t display outside air temperature. A.    If the thermostat display doesn’t scroll then set “Menu Scro” parameter to (On). The thermostat should scroll “Room Temp”, “Occupied”, “Out Temp” if Out Temp is missing then this thermostat doesn’t communicate with the RTU controller.  Verify the wiring and the network parameters.   Q.   Some SEZ7200 display outside air temperature at 0°F and this is not the right temperature. A.    This thermostat is randomly loosing communication with the RTU controller. Verify the wiring and the network parameters.   Q.   Floating damper does not open or close A.    This is probably cause the Common of the damper actuator is wired to Zone thermostat “24 Com” terminal, it should be wired to “24 Hot” since BO1 & BO2 terminals are switching Common.   Q.   BO5 reheat baseboard output doesn’t work. A.    Look at parameter “BO5 OALK” if outside air temperature is warmer than 32°F (default) then the output is disabled.  Look at “RehtConf” parameter.  Using a short wire, jump the BO5 – BO5 terminals, if the baseboard still don’t work then it’s something else, not thermostat related (wiring, relay …)   Q.    Can I use 24 Vac from another transformer (duct heater, baseboard relay …) on BO5 output? A.    Yes BO5-BO5 is an isolated triac contact, it can switch 24 Vac from another transformer.

Issue In for example TAC Vista it was possible to specify the subnet/node address when adding a Lon device, is it possible to do this in any way in StruxureWare Building Operation(SBO)? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.6.1 and earlier Cause In version 1.6.1, this is not possible. Resolution The plan is to add this functionality to SBO version 1.7.

Issue When using the SmartStruxure Interface, is it necessary to configure any DCOM or firewall settings to run TAC Vista and SmartStruxure on different computers? What protocol is used for communication between the SmartStruxure interface for TAC Vista and the ES? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista server TAC Vista SmartStruxure Interface SmartStruxure Enterprise Server (ES) Cause Communication issues between interface and SBO Resolution Only HTTP/HTTPS are used. You can configure the interface to use only one of the protocols. You can also configure what ports to use.

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 Continuum Add-on Reports will not launch Environment Continuum Add-on Reports Cause Workstation PE Programs disable and will not run Resolution 1.  Make sure there's Plain English program code in the workstation PE Program.   2.  Make sure the workstation PE Program (such as "Reports_Suite") is enabled.  3.  Make sure "Reports.exe" exists in the "..\Continuum_Reports" directory   4.  If the workstation OS is Windows 7 64-bit, make sure the "ReportPath" statement in the PE Program reads ReportPath = "C:\Progra~2\Continuum_Reports” and NOT ReportPath = "C:\Progra~1\Continuum_Reports”    If the PE program keeps disabling:   a.   Launch a DOS command prompt b.   CD \ c.   CD progra~2   If there's a DOS error stating that the directory cannot be found, 8-DOT-3 file names are not enabled and "Program Files (x86)" cannot be referenced as "progra~2".  If this is the case:   A.   Uninstall Continuum Reports B.   Install in C:\Continuum_Reports C.   Change the "Reports_Suite" PE program (and all other workstation PE programs)   ReportPath = "C:\Continuum_Reports" In General, make sure the C:\Continuum_Reports" Directory -> Properties -> Security tab has "Full Control" permission granted to all workstation “Users”. Make sure C:\Program Files (x86)\Continuum_Reports" Directory -> Properties -> Security tab has "Full Control" permission granted to all workstation “Users”. Questions / Problems can be send to COE.Support@Buildings.Schneider-Electric

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 How to select between the RS232 and RS485 port on a bCX1 controller when sending / receiving ASCII data. Environment Serial port Plain English Driver RAW Mode Bcx1 9640, 4040 Cause Unable to select RS485, the controller only transmits/ receives through RS232. Resolution There is no switch exposed to Plain English that allows you to use the RS485 port on Comm2 of a bCX.  A Netcontroller II would be able to do it as on Comm1 & 2, it has both RS232 & RS485 full circuits that work in parallel. So when you print from Plain English, the data goes out of both ports. You just need to control the RTS line of the port to switch between transmitting or receiving on the RS485 as it is half duplex. The way the bCX Comm2 is wired internally it defaults to RS232 but there is no exposed parameter to switch to RS485. In the Modbus RTU X Driver there is the special parameter (Function 99) that has to be set to switch between the ports, but this switch is at a level that only an X Driver can access. The options are: Use a Netcontroller II , or use a RS232/ RS485 converter (ensure it is not line powered), with the PE program sending / receiving on the RS232 port of the bCX. Possibly move to Comm1 of the bCX freeing up Comm2 for use with Infinet or BACnet controllers (assuming the node count is not 0).

Issue After upgrading from Version 4.07 to Ver 4.08, only the SIGMA USER is available when the user logs onto the system. All existing users and groups are lost. Product Line Satchwell Sigma Environment Sigma Server Cause During the install process there is an option to start the sigma server once the installation is complete. This will then create a default user file for the new installation. Resolution This release of Sigma (3.46.57) has a new file for storing the server details and user information. This file is GenCnfEx.rec. During the installation process there is an option to start the sigma server after the installation completes. Make sure this is not ticked if you are doing an upgrade as once the server starts it will create a new file with only the default user. When the install is complete without starting SigmaSvr, run the upgrade program, then start SigmaSvr. If the new file has been created in error, stop SigmaSvr, then delete the newly created GenCnfEx.rec file as it cannot be updated by simply running the upgrade program. Make sure you have your Ver 4.07 GenCnf.rec file  in the data folder and run the upgrade. This will then create the new file with the server details and user information.

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.