Building Automation Knowledge Base

Issue After setting up a REST gateway in SmartConnector, how can it be tested to see that it is working using the built in test client called Swagger? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central SmartConnector   Cause Swagger is a built in test REST client which can be used to read and set values in EBO. So it can be used instead of a "real" REST client to test the REST gateway in the SmartConnector and test that the connection between SmartConnector and EBO is working. Resolution The objective in this video is to set up a REST gateway in SC and show how we can test that the gateway is working using the built in test REST client called Swagger. Please see video.

Issue What process do the bCX and b3 controllers use to automatically establish their communication bus speed. Product Line Andover Continuum Environment bCX b3 Auto Baud MSTP Cause Having issues with b3 controllers selecting the wrong bus speed. Resolution The process by which the b3 controllers establish their communication speed is as follows. When the b3 controllers power up, they listen to the network for 2.5 seconds If they hear communication at their last known Baud rate, they start talking when they hear the poll for master. If they hear no communication after 2.5 seconds, they start their own poll for master at their last known Baud Rate. If they hear garbled communication during the 2.5 second listen mode, they begin hunting different Baud Rates while listening until they have synced to the Baud Rate they are listening to. Then they join the token passing when they receive the Poll for Master. Note:  There was a issue with the autobaud process in earlier versions of the b3 and BCX40xx controllers which would cause them to set the communication speed incorrectly.  This issue was corrected in the following firmware versions. BCX40xx ==> 4.500053 b3xxx      ==> 4.500064 b-3xxx-V ==> 4.501064

Issue The ES crashes during startup   SE.EnterpriseServer.exe - Application Error occurs, and the Building Operation Enterprise Server service cannot be started.  Error contains "The memory could not "written"".   The port fields in software administrator shows a red indication on one or more of the ports Environment Enterprise Server Software Administrator IP ports Cause A program is already using the ports defined for the Enterprise Server     In general   You can check which program it is, by entering the following command in a command prompt, replacing ":port number" with the number you want to check, e.g. "0.0.0.0:80" for port 80: netstat -aonb | find "0.0.0.0:port number"     Now in the task manager, enable the coloumn "PID (Process Identifier)", and look for the process ID you get to the far right when running the command above. That will show what program is taking the port.       Skype   If you are running Skype on the Enterprise Server PC there could be a conflict between the default IP port settings and the IP port settings in Software Administrator. The default ports for SmartStruxure Enterprise Server are 80 and 443. By default, Skype will "use port 80 and 443 as alternatives for incoming connections" if the configured port is unavailable. When Skype is launched it appears to search for an open IP port. If it cannot find an open port within a period of time it may default to ports 80 and 443 as a backup. This behaviour appears to be intermittent.    TeamViewer In newer versions of TeamViewer this is no longer an issue, but it's good practice to select "Use UDP" in the advanced settings of TeamViewer Resolution In general, you can change the ports used by the Enterprise Server in the Building Operation Software Administrator.   If the issue is Skype do the following: In the Skype tools menu go to “Options…” Expand the “Advanced” settings on the left hand side. Click “Connection” in the Advanced section. Uncheck the setting that says "Use port 80 and 443 as alternatives for incoming connections"

  Issue List of Mercury Controller Types and Features Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Mercury Controller Types and features to use with Access Expert Resolution Overview Mercury controllers are an open architecture controller made by Mercury Security. Feenics currently supports the LP series boards, the series 2 and series 3 MR SIO series boards.   Mercury Controllers   Equivalent Features FN-C1501 EP1501 The EP1501 is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 240,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Readers 1 SIO bus (note: connects via Reader Port 1) FN-C3202 EP1502 The EP1502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings. 240,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Reader Ports 1 SIO bus FN-C3200 EP2500 The EP2500 is an intelligent controller for managing up to 64 doors/openings. 600,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 SIO Buses FN-C4502 EP4502 The EP4502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings and complies with the BACnet standard. 2,000,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Readers 2 SIO Buses FN-LP1501 LP1501 The LP1501 is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 240,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 130 inputs and 130 Outputs 2 Onboard Readers 1 SIO bus (note: connects via Reader Port 1) FN-LP3202 LP1502 The LP1502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings. 240,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 520 inputs and 516 Outputs 2 Onboard Reader Ports 1 SIO bus FN-LP3200 LP2500 The LP2500 is an intelligent controller for managing up to 64 doors/openings. 600,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 1024 inputs and 1024 Outputs 2 SIO Buses FN-LP4502 LP4502 The EP4502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings and complies with the BACnet standard. 2,000,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 1024 inputs and 1024 Outputs 2 Onboard Readers 2 SIO Buses FN-M5-IC M5-IC An intelligent control device for the replacement of the Casi PX, PXN and PXNplus CPU controller. The single controller supports up to 64 readers across multiple enclosures. 128 Access Levels per cardholder FN-M5-ICS M5-ICS A multi-device interface panel that is a direct retrofit of Software House’s Pro GCM module. A 64 reader capacity 600,000 Cardholders Mercury - PW6K1IC Prowatch 6000  The PW6K1IC is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 15,000 Cardholders 10,000 Transaction buffer 32 Access Levels per cardholder   EP Controllers - End of Life  Feenics used to support the EP Series controllers, however, they have been replaced with the LP series. Related article - Updating Mercury Firmware https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-Updating-Firmware-on-an-SSC-or-Mercury-Controller/ta-p/410961  

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 for assistance. Issue During the installation of the EBO package, an error is displayed about PCT_temp.vbox already in existence.   ERROR_(3), UNABLE_TO_EXECUTE__COMMAND(99), reason=VBo xManage.exe: error: Machine settings file Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Leftover folder/file from previously failed installation Resolution Close PCT if running Take note of the folder/file that the error refers to, in this case "C:\Users\sesaxxxxxx\.VirtualBox\PCT_temp\PCT_temp.vbox Make a backup of the folder/file as a precaution (in case it has to be put back) Delete the folder or file, in this case, delete the PCT_temp folder Re-launch PCT and attempt to install the EBO package once again

Issue How to transfer EBO 2022 or higher data to Azure IoT hub via MQTT protocol Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to configure EBO MQTT interface and Azure IoT Hub, so EBO can send MQTT messages to Azure MQTT IOT Hub. Resolution The following video will illustrate how to: Create Azure IoT hub and IoT device using Azure Portal Create IoT interface and Azure MQTT client in EBO Configure the MQTT connection Create and configure a data group Test the connection Things you need: EBO 2022 or later with valid MQTT license or demo license (Enterprise Server, AS-P or AS-B) valid Azure Subscription with possibility to use free account during testing. For each Azure subscription one IoT hub in the free tier can be created, refer to IoT Hub | Microsoft Azure Visual studio code to be used to test the connection between EBO and Azure IoT hub, can be download from: Visual Studio Code

Issue How to disable UNC power monitoring Environment I/A Series R2 Universal Network Controller (UNC) I/A Series Niagara R2 version 2.301.318 or later Cause UNC that is installed with I/A Series Niagara R2 version 2.301.318 or later has power monitoring enabled. UNC-410 and UNC-520 have the following parameters monitored. Power Loss - alarm on AC power loss Battery fail - alarm if backup battery test fail There could be situations where the monitoring of these parameters needs to be disabled.  Resolution You can disable the UNC's power monitoring function by editing the UNC's driver.properties file.  To access the driver.properties file, in WorkPlace Pro Admin Tool, connect to the UNC and go to the 'Installation' tab. Click on the 'Edit drivers.properties' button.  The line 'power.enabled=true' enables the power monitoring. To disable power monitoring, change the line to 'power.enabled=false'.  After the change, save the changes (File > Save) and reboot the UNC.   For more details, refer to the Niagara System and Power Monitoring Engineering Notes. 

Issue When a Bacnet alarm from BACnet controller (BCX and b3 controller) is acknowledged,  alarm recipient Continuum WS sends out Change-Of-Bitstring packet to the 3rd party BACnet Operator Workstation (BOWS) when the 3rd party BOWS is registered as one of the recipients in the EventNotification of the alarm. Environment Continuum WS. BCX. B4920. B3 controllers.. Cause This packet shows some proprietary behavior of Cyberstation we refer to as the "workstation to workstation ack", that happens in addition to the normal workstation to controller acknowledgement. Cyberstation uses the information in the Recipient List of the NotificationClass object of the original alarm to determine which other devices receive the original alarm, and therefore, should receive the proprietary alarm ack. Resolution As a workaround is as below: From the existing EventNotification, remove all the 3rd party devices from its recipient list. Create a new EventEnrollment & EventNofitication for the same alarming point, and add only the 3rd party devices to its recipient list.

Issue Cannot do a backup to flash on bCX4040. Distribution Properties indicates "The flash for this controller does not need to be backed up." Product Line Andover Continuum Environment bCX4040 Cause ACCStatusBackup is set to ACCBackupInactive when ACCRestartMode is set to ACCWarmStartOnly. This occurred when a bCX9640 was flashed to a bCX4040.  ACCWarmToCool is the default ACCRestartMode for the bCX4040. Resolution Change ACCRestartMode to ACCWarmToCool and then try the backup. For more information on the ACCRestartMode refer to Chapter 5 of the bCX1 Series Controller Technical Reference document # 30-3001-890.

Issue When ordering Veris products through Schneider Electric, SE part numbers must be used. Environment Veris products Cause Cross reference needed between Veris and Schneider Electric part numbers. Resolution   Veris Part no SE Part no H708 3240100000 H709HV 3240101000 H308 3240102000 H608 3240103000 H908 3240104000 H909HV 3240105000 H800 3240106000 H300 3240108000 H600 3240109000 H900 3240110000 H721LC 3240201000 H721HC 3240202000 H921 3240203000 H722LC 3240204000 H722HC 3240205000 H723LC 3240206000 H723HC 3240207000 H922 3240208000 H923 3240209000 H221 3240210000 H321 3240211000 AH01 3240301000 AH-27 3240302000

Issue ODBC used with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause ODBC (Open Database Connectivity), a standard C programming language middleware API. is used to access database management systems (DBMS). Resolution ODBC is not supported with the current or previous releases of EcoStruxure Building Operation.

Issue SEZ7000 Commercial zoning systems Environment Need for commercial application with zone controlling Cause What does the SEZ7000 series unit provide? What would be a comparable replacement for an obsolete Trend IQ222 Resolution The SEZ commercial zoning system has been specifically designed to bring a simple scalable solution to mid-market commercial applications without the cost associated with a typical DDC zoning system. Models include roof top and heat pump units controlling analogue heat, CO2 levels, and indoor air quality. Zoning controllers that provide floating and analogue damper control are also available. A single central controller unit can support up to 64 individual zone controllers. All zoning system controllers can be ordered with an on-board passive infrared (PIR) occupancy sensor cover that allows for advanced occupancy strategies, enabling greater energy savings to zones during scheduled events when no occupants are present.

Issue Are the Infilink and B-Link interchangeable or can they be converted? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infilink 200 B-Link Cause Both units are RS-485 repeaters; is there a difference? Resolution You cannot convert from an Infilink 200 to a B-Link. They are both RS-485 repeaters, but the circuitry is slightly different to handle the electrical requirements of the BACnet MS/TP and the Infinet. You must use the correct unit for the network type you have. The multiple ports on both repeaters (Infilink and B-Link) allow you to construct a star topology configuration, but note that devices in each spoke (port on the repeater) MUST be connected in a daisy chain topology. Neither product contains any firmware that can be changed.

Issue The pressure drop across the valve is required. Environment Valve Pressure Drop Cause Customer needs to know what the pressure drop across a 32mm valve will be. Resolution Example: two 32mm V211T valves with flows of 0.549 l/s and 0.483 l/s through them. To calculate the pressure drop use this formula - Pressure drop = (Flow rate in M3/Hr / KVs) squared. Flow rate of 0.549 l/s 32mm V211T has a KV of 16 Converting flow to M3/Hr - 0.549 * 3.6 = 1.9764 Pressure Drop = 1.9764 / 16 = 0.123525 squared = 0.015258 Bar * 100 = 1.526 kPa Flow rate of 0.483 l/s 32mm V211T has a KV of 16 Converting flow to M3/Hr - 0.483 * 3.6 = 1.7388 Pressure Drop = 1.7388 / 16 = 0.108675 squared = 0.0118102 Bar * 100 = 1.181 kPa To review the Satchwell Valve sizing data sheet, please click HERE.

Issue Previously the BACnet Device Id of the controller would default to the devices serial number, this is no longer possible due to the maximum BACnet Device Id being 4,194,303. Serial numbers greater than 800xxx can give an error 'Device Node id is out of range' (1 to 4,194,303) Environment Continuum BACnet Controllers Cause Concern about what the default BACnet Id will be set to a value higher than what is supported or to a value that has already been set to a previous controller. Will this conflict with existing controllers on a site when adding new controllers when all are using the default BACnet Device Id? Resolution There is an internal calculation done that uses the Serial number as a seed to then calculate the BACnet Device Id so that it falls within the 4,194,303 max. This calculated value will be unique to every other Continuum BACnet Devices default BACnet Device Id so you should be fine when newer controllers are being added to existing sites. If you want to ensure there are no address conflicts though you may want to set the value yourself when commissioning the controllers through creating the Device object manually and setting the BACnet Device Id at that time or if the device is already configured delete it from the BACnet side and then edit it from the Infinity side and enter a new and unique device id, then perform a find BACnet devices to bring the device back on the BACnet side with its new device id.

Issue How to disable credential access on Doors at different controllers using a single variable. Product Line Andover Continuum Environment Continuum Access Control Cause Require a method of securing multiple Doors at the same time. Resolution The best way to secure a number of Doors from a single variable is to use the Door Force Lock Schedule attribute in the Door object. This is accomplished by adding a numeric to the attribute on the Options tab of the Door object; IMPORTANT: The attribute name Door Force Lock is misleading, it DOES NOT lock the door in any way, all it does is disable credential access at the door. For Area/Door Lockdown refer to the linked KB article And also on the Entry Reader or Exit Reader tabs, ticking the checkbox under either Normal and/or Comm Fail for Door Forced Lock Schedule. Setting this Door Force Lock Schedule field to a local or remote InfinityNumeric point will provide the following conditions: When the Numeric is on, access is permitted to all personnel by card swipe and/or keypad entry. (Allow use of the door.) When the Numeric is off, card reader and keypad access are denied to all personnel. (No Access) You could have this numeric located in a central controller and all the rest of the controllers reference this numeric from the Door objects. No other points or plain English is required. If you want to ensure that the updates are received, you can force the IE entry for this numeric to update on a regular interval, see Use just one schedule to control doors or access to areas across different controllers that discusses how to accomplish this.  

Issue Availability of SLC-82XX and SLC-83XX Environment Site with Single Loop Proportional Temperature Controller with Sensor Cause Obsolescence of the SLC-82XX and SLC-83XX Resolution The SLC-82xx and/or SLC-83xx are obsolete. These are old analog technology controllers which have been obsolete since January 01, 2011 There is no replacement for these items. The only suggestion would be to do a complete re-control with digital equipment. To do this one of Schneider Electric's Partners would need to visit the site to see what is needed to control the space. This would require new controllers, thermostats, actuators and other items. Since it is such a major re-control we do not have a single solution that will allow you to use some of the older equipment. Contact your Regional Manager in your area to provide a contact for the site upgrade.  The manual for the SLC-82xx and SLC-83xx is available here.

Issue   A calibration certificate is sometimes requested by the end customer Product Line Field Devices Environment Veris sensors Cause   To ensure that a sensor is keeping measurement values within specification, a certificate is sometimes requested by the end customer. Resolution Calibration certificates are available for some Veris models and must be requested at the time of ordering by selecting  “N” in NIST block for 1% and 2% humidity transmitters. Temperature transmitters can be ordered with 1 or 2 point calibration certificates by selecting 1 or 2 in the in the Temp Cert Block. The following example shows how the model numbers are built up: As can be seen in the second example above the model HD2NVCTC2 has a 2% accuracy RH element with a NIST traceable certificate, it also has a 1K platinum RTD with a 2 point  calibration certificate. For information on NIST traceability see the National Institute of Standards and Technology website

Issue There is a need to be able to display pdf files from within a webpinpoint graphic Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause instructions to open a pdf file with webpinpoint Resolution Within a graphic in Cyber Pinpoint, add a Windows Control> Web Browser object Edit the object and go to object properties and select the .pdf to display (Change the file type drop down to all files from .htm)  It is recommended to place the pdf files in C:\program files\Continuum\NewGraphicsFiles for permissions reasons.  Once that object has been selected, it can be saved and run in Cyber Pinpoint The same object will open up webpinpoint and the pdf will display.

Issue Vulnerability affecting certain versions of OpenSSL. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment OpenSSL Cause Software vulnerability Resolution Information and Customer Statement located at the following link on the community: Schneider Electric Security Statement Regarding the Heartbleed Vulnerability. A corporate statement on this can also be found here: Schneider_Electric_Heartbleed_Customer_Statement_APR_15_2014.pdf.