Building Automation Knowledge Base

  Issue PCT v1.3.3.75 fail to start SmartX server in versions 1.8.x and 1.9.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Defect, user can create SmartX server v1.8.x and 1.9.x but the servers can't start properly. Resolution Uninstall PCT v1.3.3.75 Install PCT v1.3.2.110 (Download), (Client Installer) Install server packages 1.8.x and 1.9.x

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 Is it possible to connect a number of Vista servers to the same SQL server instance? Environment TAC Vista 5.1.X in a multi server environment. Cause Customers with larger sites may wish to collect the log data from TAC Vista on one SQL server for ease of maintenance and security reasons.  Resolution There are a couple of conditions to observe when doing this: Each Vista server must have it's own database (ie. taclogdata1, taclogdata2, taclogdata3 etc). The SQL server machine must be able to handle the increased load. There must be sufficient space for all the databases. A maintenance plan must be put in place - regular defragmentations and rebuilds (See White Paper - SQL Server Best Practices).

Issue The documentation states in different ways that the sensors are both 0-95% and 0-100% RH range. Environment SHD100 006902321 SHD100-T 006902331 SHD101-T5 006902381 SHD101-T6 6902411 SHO100 006902361 SHO100-T 006902371 SHO101-T5 006902401 SHR100 006902340 SHR100-T 006902350 SHR100-T5 006902390 Cause Different RH (Relative Humidity) values are listed in the documentation, and needs to be explained.  Resolution Ranges are divided into "measuring range" and "working range".   Measuring range: 0…100% r.H. Working range:   10…100% r.H. ( non condensing )   Normally 100% r.H. is already water but it is possible to have 100% r.H. in air- or gas form. Sensor works at 100% r.H. in air but not if pure water is present. This is why “non condensing” is added. In this case working range is 10…100%. If we don’t add “non condensing”,  specification should read: 10…95% r.H.  Sensor will not become damaged because of condensing.

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"

Warning   Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Using sensors, other than the D?T range in a Sigma controller Product Line Satchwell Sigma Environment Sigma Release 4_05-SEB (Build 3_43_18) Sigma Release 4_05-SP2 (Build 3_42_48) Sigma Release 4_06 (Build 3_44_14) Sigma Release 4_06 SP1 (Build 3_44_16) Sigma Release 4_07 (Build 3_45_48) Sigma Release 4_07-SP1 (Build 3_45_51) Sigma Release 4_07-SP2 (Build 3_45_58) Sigma Release 4_08 (Build 3_46_57) Cause Using 10k Type 2 and type 3 Thermistor causes hardware alarm Resolution The lookup value for a Sigma resistance input is calculated as a percentage of a 2 volt signal (that's what is measured at the A/D convertor). If using a sensor other than a standard D?T range sensor, a calculation needs to made, to obtain the value to be entered in the input column (a % of 2 volts) of the look up table.   The calculation is as follows: - ( 10^6 * R1 )      /4000 ( 14700 + R1 ) Where R1 = resistance of the input 14700 =resistor on AI card The circuit shown below is a typical example of an AI channel for a resistance input.     It is suggested to put a 10K resistor in parallel therefore, the resulting circuit resistance can never be higher than 10K.   Attached is information for both the 10K type 2 and 10K type 3 sensors. Column C is the raw sensor resistance. Column D is the controller input resistance with a 10K shunt resistor connected. Column E and F example of the look up table.

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 37-bit cards not working correctly even though a Credential Type has been configured correctly for Infinity37 cards (as seen below), the site code and/or card number read does not match what is printed on the card or the expected value. Parity errors could also be seen if the card is not truly of the Infinity37 format. Product Line Security Expert Environment Security Expert Server Security Expert Controller Cause Various cards have 37-bit data lengths but different formats; some guidance is needed on how to differentiate the ACC Infinity37 cards.  Resolution There are two pieces of data that can be used to verify if a 37-bit card is ACC Infinity27 format.   ACC Infinity 37 card format includes a Manufacturer's Code field; the field is 4 bits long, starting on the second bit and ending on the fifth bit. The Manufacturer's Code field always has a value of 4, the first bit of the card is used for the ODD parity, so the first 5 bits of ALL ACC Infinity37 cards ALWAYS look like P0100.... If we see a raw bitstream of a 37-bit card like the one in the screen capture below, we can immediately determine that even though the card has 37 bits, it is NOT an Infinity37 card since bits 2,3,4 and 5 do not add up to a value of 4 See https://community.se.com/t5/Building-Automation-Knowledge/How-to-display-RAW-bit-data-stream-of-Wiegand-card-in-Security/ta-p/390720  We can not assume that because a 37-bit card has  0100 on bits 2-5 it is 100% evidence that the card is indeed an Infinity37 card since that pattern (0100) could be present on the card as part of a different field (i.e., Site Code) on a different 37-bit card format. The second piece of data that could help determine if the card is true of the Infinity37 format is the parity bits, Infinity37 card format has a somewhat unique interlaced parity scheme. If parity errors are seen when cards are presented to the reader, this should be taken as an indication that the 37-bit card might not be Infinity37 card format. The attached zip file contains an Excel sheet that can be used to calculate the parity bits of an ACC Infinity37 card by entering the raw bitstream of the card; if the calculated values for both parity bits (bits 1 and 37) do not match what the card has, then the card is NOT an Infinity37 card format.    

Issue How to create i2xxx and b3xxx controllers from a CSV dump file. Environment Continuum i2xxx Controllers b3xxx Controllers Cause In this scenario they wanted to create the beginning of a site database from CSV dump files before deploying on site.  Resolution It seems that when creating an i2 or b3 object, the path is also required when defining the comm port. Make sure to add the path to the Port field and this should allow the controller object to be created. See the original CSV I exported below, how it was modified, and then imported back in successfully. Original Export to CSV InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType i2_850,32,Comm1,Network1\ACX11_10th,11111,i2_850,i2920 Modified Import CSV InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920,i2920 Now, this import does complain about the CntrlType in the distribution Properties window but does create the controller and sets the type correctly. If you don't want any errors you can remove the CntrType attribute and the controller object will still be created but will default to a 240 controller. See below. Import CSV without CntrlType InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920   This can then be changed to whatever controller you require through the controller Device object dialog.  

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 SE7000/SE8000 controllers are randomly going offline or are undiscoverable on BACnet network. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 SSL SE8000 Cause Improper terminations of the BACnet MS/TP communication cable.   Resolution The REF (reference) Terminal is a BACnet Reference which is a voltage reference required by BACnet testing lab (BTL) and it is rarely used in the industry. If not used as a reference, The Ref terminal should be left empty. It is not a terminal to land a shield nor a ground.    At each thermostat (Cable Junction) : Connect the (+) and the (-) wires Twist the shields together Tape around the cable to prevent short-circuit. Ground the shield at one end only (usually on the BAS side) and leave the REF terminal empty Ensure that the shield wire is not connected to the REF (Reference) terminal.

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 Error "Job Failed  java.lang.NoSuchMethodError: com/tridium/install/BDaemonPlatform.getNiagaraR2Enabled()Z" when attempting to perform an I/A Series G3 Station Backup in version 3.6.31 after having installed the August 2012 security updates. Environment I/A Series G3 JACE or ENC with release 3.6.31 and security patches 3.6.47 installed. Cause Internal software error in the backup.jar file, version 3.6.47.2 Resolution Remove the backup.jar file, version 3.6.47.2 from the modules folder on the I/A Series G3 WorkBench computer. Remove the file backup.jar from the \niagara\niagara-3.6.31\sw\3.6.47.2 folder. Verify that the original 3.6.31 backup.jar file is in the  \niagara\niagara-3.6.31\modules folder.  Note that when replacing the backup.jar file, the 3.6.47.2 file should be renamed so that it can be restored later. Open the 3.6.31 Workbench and open the platform of the ENC / JACE. Run the Software Manager and note that a newer version of the is shown as installed as compared to the avail. version. Select the "backup" module by clicking on it then click the [Downgrade] button then click the [Commit] button. Acknowledge the warning that a reboot will be required by clicking the [Yes] button. Wait for the module commit process to complete, the station to reboot and restart. After the station has restarted you can log into the Station through Workbench and perform the backup to a .dist file using the standard station backup procedure (by right-clicking on the station name and selecting "Backup Station").

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 b3 Schedules Environment StruxureWare Building Operation site with b3 controllers Cause What actually takes place within the system to ensure the current weeks schedule is downloaded to the controller periodically and can this be adjusted by the user? The Enterprise Server and Automation Server may not even need weekly downloads of a schedule as they are of course servers, but b3 controllers will most certainly still require some kind of period download as they can only hold one weeks schedule at any one time. Resolution B3 devices hold their entire schedule configuration. All weeks, and all exception schedule events. The entire configuration is of a schedule is written to the device when it is modified by the user. There may be several schedule objects in the b3. As such, there is no periodic download. Note that compared to Continuum which performs a default download every Saturday at midnight and updates the schedule whether needed or not.  

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 Replacing VEX, MEX, FEX valves and AVX, AVM actuators Environment Thermic Valves Cause The valve and / or actuator requires replacement. Resolution The AVX and AVM are a 2 wire thermic valve actuator, its stroke length is 2.5mm short stroke. The valve actuator fitting is an industry standard 30mm x 1.5mm thread. To replace the valve use the VZ208 (2 port), VZ308 (3 port), VZ408 (4 port). To replace the actuator use either the MZ140-24T (24Vac) or the MZ140-230T (230Vac). Download the VEX, MEX, FEX, AVX, AVM datasheet here. Download the VZ208, VZ308, VZ408, MZ140 datasheet here.

Issue Using the IR Tool or RS 485 converter to communicate with the controller Environment NCP Palm IR Tool RS232 to RS485 converter. Cause Configuration and use of NCP Palm. Resolution Using the IR Tool to communicate with a Unifact Pro controller. Connect the IR Tool to your laptop and Unifact Pro controller. Start the NCP Palm programme. Select the correct serial communications port and uncheck the CTS / RTS selection boxes, then select OK. From the "File" menu select "Connect" Enter 0 for the Subnet address, 0 for the Node address, then select OK. This has now confirmed that you are connected to the IR Tool. To connect to the controller select the "File" menu and select "DisConnect" Select the "File" menu and then select "Connect". Enter 1 for the Subnet address, 1 for the Node address, then select OK. You are now connected to the controller. Using an RS 232/485 converter is similar to connecting to the controller, but the controller communications terminals are used instead of the IR Tool. For further details on NCP Palm, please click 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 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.