Building Automation Knowledge Base

Issue Where is the RSTP setting on a MP-C or MP-V controller? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller (MP-C) Building Operation Multi-purpose VAV (MP-V) Cause Unable to find RSTP setting on MP-C or MP-V controller Resolution On the controller, find System > Settings, scroll down to Configuration and enable RSTP. ** Be sure to Warm start each controller after enabling RSTP or the setting will not be retained **

Issue Not able access a new MNB-1000 via its default IP address. It will not respond to when pinged. Product Line TAC IA Series Environment WorkPlace Tech all versions, WPT Version 1.50E and later Cause The ability to ping the MNB-1000 controller was removed starting in Firmware version 1.50E. All MNB-1000s are shipped with IP port disabled. Resolution Starting with firmware revision 1.50E, the ability to ping a MNB-1000 controller was removed; so any MNB-1000 controller at or above firmware Revision 1.50E will not respond to a ping. Reference Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E or higher for further details. All new MNB-1000 controllers are shipped from the factory with their IP and MS/TP ports disabled. The Ethernet port is the only port enabled. The MNB-1000 controller must first be accessed via its Ethernet port. Once gaining access, its BACnet/IP port can then be enabled.  Note: Both BACnet/Ethernet and BACnet/IP ports should not be enabled at the same time. So if BACnet/IP is being used and once the BACnet/IP port is configured and enabled, then disable the Ethernet port. NOTE:  Firmware 1.537 made the MNB-1000 visible via the ping command again.

Issue What is the latest specification For a Continuum PC Product Line Andover Continuum Environment Cyberstation SQL Server Cause Computer specification required. Resolution The PC specifications for a version does not change from the time of release, so there is no "Latest Specification" as such. For all versions the hardware requirements are defined in the installation guide (Installation.PDF) on the software CD, or in the downloaded zip file from The Exchange Download Center for the version to be used. This document will contain the minimum and recommended specification required for that Cyberstation version on a typical site, if any other software is to be installed on the computer or the computer is to be heavily loaded; the requirements should be increased accordingly. The same RAM and Processor requirements will also apply to the SQL Server on a typical LAN system. You also need to check the Software and Firmware compatibility matrix for older versions of the traditional product lines for details on the compatible operating system requirements for the version to be used. For a V2.01 system the recommended hardware for servers and workstations are: Intel 8 Cores, 2 GHz or better 8Gb RAM 30Gb Available HDD space (NTFS Partition) CD ROM Drive Video resolution: 1024 x 768 pixels Parallel or USB port For larger systems and where there will be a lot of Extended logging or Alarming, the Hard drive, RAM size and processor speed should be increased.  

Issue How to collect log files from the Project Configuration tool. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the Project Configuration tool, log files should be provided. Resolution Go to the PCT installation folder and run the program called LogCollector.exe located there. The default installation folder for versions 1.2 and higher is: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool" and "C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool" for previous versions. Click Collect logs A program log of what LogCollector has done is displayed. A zip-file containing the collected PCT logs is created on the desktop.

Issue What is the proper way to replace AS hardware for an existing node. Cannot get the AS to come online in the Enterprise Server after replacing the AS hardware for an existing node. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server - Classic (AS) Building Operation Automation Server - Premium (AS-P) Building Operation Automation Server - Bundled (AS-B) Cause To replace the AS hardware, a backup must have been made from the original AS while it was online.  Simply changing the controller name, IP information, and domain  information in the AS will not be sufficient for bringing the controller online in the ES. Before the new automation server can be brought online, the backup from the original controller must be restored to the new AS directly. Resolution This procedure assumes that a backup of the original AS is available. From Device Administrator and the USB interface, run the SetIP command to configure the following information in the new AS to match the original AS configuration. Note: You will have to use the version of Device Administrator that matches the replacement AS firmware. If necessary, use the appropriate version of Device Administrator to Upgrade or downgrade the firmware in the new AS so that it matches the Enterprise Server and/or the original AS hardware firmware. Install the AS then backplane. From StruxureWare workstation, log into the AS using the hardware's IP address for the Server field. Right click on the server name and select Restore. If the backup does not appear in the Available restore points window, click on Import Backup Set and browse to the backup file. Select Configuration only or All data in the window on the left. Select restore. Once the restore has completed the AS displays a solid green status light, log off the AS and log into the ES. The controller should now appear online in the ES.

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place) 

Issue Xenta Programmable Device is Offline in Vista, but Online in LonMaker. For LonWorks Devices refer to LonWorks Device is Offline in Vista but Online in LonMaker or NL220. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In an LNS system, Xenta programmable controllers have different methods of communication to the LNS server and the Vista server.  Communication with the LNS server indicates the wiring is connected, the neuron ID is set correctly, but does not guarantee communication with the Vista server.  An online condition for Vista is dependent on Xenta Group bindings and network description files in the device and the Xenta Group Master being online. Resolution Ensure that Vista Workstation is in Operating Mode vs. Engineering Mode. Refresh the Folders View - Highlight the root directory "TAC Vista" press "F5" or click the refresh icon. Ensure the device is physically Online in LonMaker even though the drawing displays as green. Check the status by right clicking on the device, select Properties. Commission Status should say "Current", and State should say "Online". Alternatively, right click on the device and select Manage / Test.  The state should read "configured online" if the device is online in LonMaker. Make sure that your Master Device in the corresponding Xenta Group in the System Plug-in is online. If the Master Device is online and displaying values, it is always necessary to download the application and parameters to the Xenta group after adding a new device. The entire Xenta Group must know there is a new device for proper communication to occur.  Download the applications and parameters to the entire group in the TAC System Plug-In. If all the above is true and there is still no data then use Verifying Xenta Group Bindings in an LNS system to verify that the Xenta Group Bindings are correct. If not, in the Vista system plug-in, click on the LNS Network tab choose Create Group Bindings and click Yes on the Resynchronize drawing to database (Fix-up Drawing). Ensure the Xenta Group name is less than 20 characters without any spaces. Note: Channel names can contain spaces (NL220) but still must stay under the 20 character limit. 

Issue How do I share data between standard Continuum controllers and Continuum BACnet controllers? What communication method is used (COV, Import/export, or point to point)? What problems can I encounter? Product Line Andover Continuum Environment Continuum Controllers (CX9200, CX9400, CX9900,CX9702, CX9680, bCX9640, ACX5720, ACX5740) Continuum BACnet Controllers (b4920, bCX4040) Cause All communication between Continuum controllers and Continuum BACnet controllers is done using point to point protocol. Since BACnet controllers do not support Import/export and Continuum controllers do not support COV, point to point is the only common method to communicate. Resolution The method of programming the data sharing can be the same as standard Continuum programming, however because of the point to point protocol a specific method should be used. Using typical Continuum programming techniques, you would create a mirrored point in the BACnet controller (a BCX for instance). You would then write a PE program in the BCX that mirrors the point, for instance: Line Mirror BCX DataPoint1 = CX/Infinet/DataPoint1 goto Mirror Line E: goto mirror This method would perform a point to point communication every BCX scan and retrieve the data whether it has changed or not. It will create a lot of unnecessary network traffic and slow the scans of both controllers. The line E is necessary because with a point to point communication, the program will disable if the target controller temporarily goes offline. Now consider if you were mirroring many points between the systems for instance you were using the BCX as a BACnet gateway for the Continuum system. That same program would have many points that are being transferred. You would also write multiple programs because of the number of points being polled. The net result of this programming method would be that the entire system would be brought to its knees! Extremely slow scan rates in both controllers because these point to point data requests have to be completed end to end during the scan. Congested Infinet communications because to get the Infinet points we go all the way down the 19.2K Baud Infinet to get the data. The system would just plain no longer function correctly. The only reasonable method to accomplish this type of data transfer would be for the owner of the data that you want to transfer to the other controller sends the data to that controller, and only on an as needed basis, such as a change in its value. Therefore in the scenario described above where you want to mirror points in a BACnet BCX from a Continuum system, you would write the transfer program(s) in the CX controller, and within that program use a local variable for each transferred point to allow you to know if its value has changed since the last transfer, and not retransmit if the value is the same, thereby significantly decreasing network traffic and burden on the system. This method has the added benefit of eliminating the need to clog up the Infinet network, because the program in the CX automatically creates an import/export relationship between the CX and the Infinet controller's points so the normal export broadcast will transfer the data to the CX. One example of the program in the CX to perform the data transfer is as follows: Numeric num1 Line Mirror If num1<>CX/Infinet/datapoint1 then set BCX dataPoint1 to CX/Infinet/datapoint1 num1 = CX/Infinet/datapoint1 endif goto Mirror Line E: if TS>5 then goto Mirror You could also streamline the programs using such methods as creating an InfinityFunction that would be called to minimize the redundant portions of the data comparison and transfer in the programs for multiple point transfers. The function could be named “Exporter” look like this: Arg 1 RemotePoint Arg 2 LocalPoint Arg 3 TestPoint If TestPoint<> LocalPoint then Set RemotePoint to LocalPoint TestPoint= LocalPoint endif Return And now any point that you want to be exported would call this function so the above program would be reduced to: Numeric num1, ..... numX Line Mirror Exporter (BCX dataPoint1, CX/Infinet/datapoint1, num1) . . Exporter (BCX dataPointX, CX/Infinet/datapointX, numX) goto Mirror Line E: if TS>5 then goto mirror After the initial scan when we send all the current data to the BCX, only changed data would be sent thereafter. This syntax would be repeated for each point that you wanted to mirror. This program is setup to be looping. You could create a similar program to be fallthru and trigger it from a minute or seconds system variable. If kept looping it would be recommended to go to a delay line between scans if there was a lot of data transfer going on. There should also be many programs like this if there is a lot of data to be transferred for a couple of reasons. First, if for some reason one of the points could not be transferred due to a temporary comm loss, the program would disable, go to line E and restart from the beginning, not executing any data transfer on the points below the one that failed. Second, if you were transferring many points, you would most likely exceed the maximum file size. Always be cautious as to how much data you try to transfer, and how often. There is no fixed limit per controller, but system performance will degrade proportionally to the speed and amount of data being transferred. As an additional note, it would also be extremely beneficial to put thresholds on the exported points to decrease un-necessary traffic.

Issue What is the correct procedure for replacing a Continuum bCX 4040 controller Product Line Andover Continuum Environment CyberStation bCX 4040 Cause Considering both Continuum and BACnet 'sides' replacing a bCX4040 can seem a complicated process. Resolution Commission new/replacement bCX through its default webpage just as the as old bCX except for the BACnet Configurable Properties section. Set the BACnet Device ID = The same ID in the old bCX (serial number of controller by default) Set the BACnet Port Number UDP = same as old bCX (BAC0 by default) Set the BACnet Network ID UDP = same as old bCX (1 by default) Set the BACnet Network ID Comm2 = same as old bCX (2765 by default) Set the BACnet MAC ID Comm2 = Same as old bCX (0 by default) Set the BACnet MS/TP Enhanced Mode = Same as old bCX (TRUE by default) Set BACnet BBMD Enabled/Disabled = Same as old bCX (False by default) Bring the bCX online in Continuum Explorer, Select menu item Options | Send to Controller options Select "Reload attached objects, but not attached controllers" - select ok Verify the bCX Comm2 settings and baud rate speeds. In Continuum Explorer, right click on the bCX and perform a "send to controller" Verify points and communications.

Issue Installation and configuration for SE8600 heat pump application Product Line EcoStruxure Building Expert Environment  SE8600 Cause Installation and configuration errors for heat pump application Resolution SE8600 terminal identification In typical HP application, you shall connect to following terminals below: Y2 = Compressor 2 | Y1 = Compressor 1 | G = Fan | RC = 24 Vac positive | C = Common << 24Vac common >> W1 = Auxiliary Heating stage | W2 = O/B = First stage heating | UI22 = Supply temperature sensor | UI23 = Outdoor temperature sensor Depend on specification document, the application may require addition controls and connections. Application shall be set to: HP for heat pump From winter to summer season, high BP is the outdoor temperature value ABOVE which the system transfer from auxiliary heat <> and maintain heating setpoint with the heat pump << default 32°C >>. Temperature shall be set per system geographical localization. From summer to winter season, low BP is the outdoor temperature value BELOW which the system transfer from heat pump <> and maintain heating setpoint with the auxiliary heat << default -24.5°C >>. Temperature shall be set per system geographical localization. * Outdoor temperature sensor shall be installed   Heat pump reversing valve operation O: energize valve in cooling operation << default position >> B: energize valve in heating operation Heat pump system

Issue Suprema Fingerprint Reader Integration Product Line EcoStruxure Security Expert Environment Security Expert Suprema Fingerprint Reader Cause Security Expert integrates with Suprema BioEntry, BioEntry Plus, and FaceStation devices. Enrolment is both quick and easy with users scanning their fingerprint or face at an enrolment reader. The Suprema reader uses the scanned data to create a credential template, including a card number, which it sends to the Security Expert Server. Security Expert then sends this template to any other Suprema readers that are attached to the system so that only one enrolment is required. Resolution The following information is available on integrating Suprema Fingerprint Readers with Security Expert A list of qualified Suprema devices and configuration details can be found in the Suprema Biometric Integration in Security Expert Application Note. There are some available help topics in the online help. In the Security Expert  Client go to ABOUT | HELP and search for "Biometric Readers" and "Suprema". Each Suprema reader requires a wiegand port on a controller / expander, a license (SX-BIO-SP) and an IP address. The amount of Suprema readers allowed is only limited by these numbers. 

Issue Satchwell ALi series Linear Actuator requires replacement. Environment Satchwell ALi series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Actuator type :- ALi series. Cause Obsolescence of Satchwell ALi series Linear Actuator. Resolution Replace Satchwell ALi series Linear Actuator with S-E M800 Linear Actuator and Linkage Kit :- ALi = M800 + L2SV (880-0124-000) Linkage Kit. N.B. Should the Satchwell ALi series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :- S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an S-E Forta M800 Actuator to replace an existing Satchwell ALi series Actuator. The S-E Forta M800 Actuator may be used to replace an existing Satchwell ALi series Actuator but it should be noted that where an existing Satchwell ALi series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) will also be required. (e.g. S-E Transformer Type TR60) Where an existing Satchwell ALi series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALi series Actuator (16VA) only. In such circumstances the existing independent Transformer will also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) (e.g. S-E Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here Details of the Schneider Electric L2SV Linkage Kit may be viewed here

Issue Need to mirror a switch port in order to capture controller data with Wireshark.   Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Cause Need a step-by-step guide to set up a mirrored port and an understanding of how it works.  Resolution View the attached video.   Use the link to the original post in Area360 to get written instructions.

Issue Procedure for installing PCC-10 or PCLTA20/21 network cards on a Windows 7 PC Product Line TAC Vista Environment Vista Menta LonMaker Windows 7 Cause Installation procedure differs from earlier versions of driver software. Resolution The PCC-10 and PCLTA-20/21 network cards work on Windows 7 (32 bit) PCs when the OpenLDV 4.0 driver is installed. This driver is installed automatically when Lonmaker Turbo SR4 is installed, but if this version of Lonmaker is not present the driver must be installed manually.  The latest drivers can be obtained from the Echelon download site: http://www.echelon.com/support/downloads Note: The PCLTA-20/21 card is only supported on 32bit windows operating systems. For 64bit systems use a NIC-USB as mentioned in this article: Computer will not recognize NIC709-USB. Install the drivers before fitting the card in the PC. Please note that OpenLDV4.0 requires .NET Framework 3.5 SP1.  This is not included as a subset of .NET Framework 4 or later, so must be installed separately.  You can have multiple versions of .NET framework installed on the same PC. The following description is for the PCLTA-21 but the PCC-10 is similar. To change the system image or perform diagnostics, you must go to Control Panel and open the Lonworks Interfaces application: Click Start on the taskbar, point to Settings, click Control Panel, and then open the LONWORKS Interfaces application. Click the PCLTA-21 interface in the list view on the left side of the user interface to display the interface's properties in the details pane in the right side. The details pane lists the PCLTA-21 card's system image and transceiver properties. To change the system image used by the PCLTA-21 card, click anywhere in the NI Application property, click the box to the right, and then browse to and select the desired system image from the LonWorks\Images\PCLTA21 folder. Note: For more information on configuring, testing, and diagnosing the PCLTA-21 network interface, see the LonWorks Interfaces online help.

Issue Is there support for the C-Bus protocol in StruxureWare Building Operation? How can we integrate C-Bus into StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0, 1.1 and 1.2. Cause Requirement to integrate C-Bus protocol into StruxureWare Building Operation, Automation Server or Enterprise Server. Clipsal C-Bus integrated service provide two gateways (BACnet / OPC), that may provide a suitable integration option. Resolution StruxureWare Building Operation does not directly support the C-Bus protocol at this point. Currently Schneider Electric Buildings integration with the C-Bus protocol is typically through the Xenta 913 (See Tip and tricks for communication between Xenta 913 and C-Bus on how this is achieved). When Interfacing the Xenta 913 to the Building Operation offerings you must create connection objects to and from the C-Bus objects via SNVTs, which need to be separately created within the Xenta 913 XBuilder project. Once these SNVTs are exposed, then the Xenta 913 can be added on the LonWorks network allowing the unit to be discovered as a LonWorks device (i.e. only acting as a third party LonWorks device). There are also two offerings provide by the Clipsal Integrated Services division that can be integrated with Building Operation, these are:   1. C-Bus BACnet Gateway (5000BACnet) The C-Bus BACnet Gateway is an embedded device that provides a field bridge between Clipsal C-Bus lighting control systems and the BACnet open protocol. The C-Bus BACnet Gateway provides 255 group addresses from a single application address. The C-Bus BACnet gateway supports the reading and writing of BACnet objects between C-Bus and BACnet and is supplied pre-configured from the (Clipsal) factory. Below is the link to detail of the C-Bus BACnet Gateway (5000BACnet) https://www.clipsal.com/Trade/Support/Software   2. C-Bus OPC Server For larger C-Bus systems (i.e. >255 group addresses) then the C-Bus OPC Server provides a gateway for C-Bus and the OPC Data Access protocols. Current releases of Building Operation does not support OPC, so you will require either an OPC to BACnet or OPC to LonWorks application which can be purchased through third party vendors. SCADA Engine is the preferred Clipsal BACnet OPC Client solution used. http://www.scadaengine.com/ Even though this solution is focused on BACnet, it may also be possible for a similar solution using LonWorks. Below is the link to detail of the C-Bus OPC Server https://www.clipsal.com/Trade/Support/Software There are additional requirements for each of these options that may need to be considered, it is best to discuss these directly with your regional Clipsal representative.

Issue When using mstpcap.exe to capture, it automatically stops after 65535 packets. Similarly, when using Wireshark, it will stop capturing if the dissector encounters an issue. This article provides a solution to continuously capture BACnet MS/TP traffic in a ring buffer and store it as files. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment Wireshark Any BACnet MSTP RS-485 network Cause Analyze BACnet traffic via capture files. Resolution Install Wireshark. Ensure TShark is checked when installing options.  Ensure Wireshark is installed with Npcap (default) or WinPCap has been installed by IA Series Workplace Tech. Install mstpcap.exe referencing BACnet MSTP Capture Application. Ensure that mstpcap.exe has been configured for the correct port and baud rate. Here is an example for Command Prompt and PowerShell: # Command Prompt cd "C:\Program Files\Wireshark\extcap" mstpcap.exe com3 38400 # PowerShell cd 'C:\Program Files\Wireshark\extcap' ./mstpcap.exe com3 38400 Run Tshark to determine the interface being used by mstpcap so that one can reference it by number. For this example, we are going to choose 9. COM3 (BACnet MS/TP on COM3). Please change the number below to the number of your interface.  Start Tshark capture by entering the following command, updating as needed. The commands below save Test01.pcap to the Username's desktop. Please store to a location that the user has access to write.  # Command Prompt cd "C:\Program Files\Wireshark" tshark.exe -i 9 -b duration:3600 -b files:72 -w "C:\Users\Username\Desktop\Desktop\Test01.pcap​"​ # PowerShell cd 'C:\Program Files\Wireshark' ./tshark.exe -i 9 -b duration:3600 -b files:72 -w 'C:\Users\Username\Desktop\Desktop\Test01.pcap​' Note: Change  -i 9  to the number of the interface on the capturing machine. Change  -b duration  to time in seconds (3600 is one hour). Change  -b files  to the number of files to cycle through (72 is 3 days of 1-hour captures, 3x24). Change  -w  to write to the location and filename you choose. Change  \Username\  to your Windows User, if you want to save to that user's Desktop Reference: tshark(1) Manual Page (wireshark.org)

Issue How can System Alarms be disabled? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are over 230 system alarms and at times they need to be turned off temporarily. There is no straight-forward method to gain access to the (intrinsic) system alarms, so an instruction on how to disable them is needed. Resolution You cannot stop system alarms from triggering. But if there are system alarms that trigger often, you might want to "turn these off". The way to do this is to disable the alarms, which would cause the alarms not to trigger again until they are enabled. An alarm has to trigger first in order for it to be disabled. To disable an alarm, right click on the alarm in the alarm list and choose Disable alarm. There is no menu or object to access the system alarms only. For a list of system alarms see What system alarms can occur in StruxureWare Building Operation?

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 Locating and downloading latest images Product Line Satchwell Sigma Environment 3.46.57 3.46.66 3.46.80 3.46.89 3.46.100 3.46.104 3.46.105 3.46.106 3.46.107 3.46.108 3.46.110 3.46.111 3.46.131 Cause Identifying the correct image version for different hardware versions. Resolution Sigma UNC/ (V53) = Firmware 6b Sigma Firmware UNC596 6.b - Release note   Sigma UNC3 (ARM7) = firmware build 1.p.0 Sigma Firmware 1.p.0 UNC3 - Release note   UNC 532 V25 = Firmware 6b Sigma Firmware UNC532 6.b - Release Note   IC-Modbus = Firmware V5h IC-Modbus v5h Release Note   IC3 Modbus = Firmware1.n.2 IC3 Modbus - Release Note   IC SNP = Firmware 5d IC-SNP Integration Controller v5d for Sigma Rel 3 - Release Note   IC3 SNP = Firmware 1.g.1 Sigma 4.05 Firmware Supplement - Release Note (there is no release note specific to SNP Firmware 1g.1).   IC York = Firmware V3e - Not available to download. IC-York Integration Controller v3e for Sigma - Release Note   IC3 York = Firmware 1.d.0 IC3 York = Firmware 1.d.0 – Release Note   Sigma IC3 Unifact 1.d.0 – Firmware Sigma IC3 Unifact (RTC) - Release Note Sigma IC3 Unifact pro 5h – Firmware Sigma IC3 Unifact pro 5h - Release Note  

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. 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 SP-C Controllers randomly going offline / online.  Restarting the controller resolves the issue for a short period of time. SP-C Controller ports showing TIME_WAIT when a netstat command is run. Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause Under normal conditions an SP-C needs to update the Security Expert Server with new data. During this time the IP Socket of the SP-C is in a Waiting State, refusing to communicate to anyone else while waiting for an opportunity to upload. Once the controllers data has been uploaded to the server however the controller releases the IP Socket and it is open again to new communication. In an extremely small number of cases the SP-C controller goes into this waiting state as usual but then never comes out of that state, holding onto the IP Socket forever and blocking any further communication until the controller is power reset. This only affects a very small percentage of SP-C controllers running Microsoft Windows CE OS Version 16. Resolution In these extremely rare cases the first step is to identify if the affected controllers are indeed running OS Version16.  For SP-C Firmware builds before 2.08.921 Log into the controllers configuration web page. Browse to the Configuration tab. Check the OS Version field at the bottom of the page. For SP-C Firmware build 2.08.921 and above the OS is now shown in a different location.   Once it is clear, that the OS is version 16, Product Support can be contacted to arrange to upgrade the controller OS to Version 20 (or greater) as is found in SP-C controllers shipping now. As this is a high risk procedure and can result in complete failure of the controller if anything goes wrong there are two options for upgrading the OS. Install the affected controller on a test bench with remote access for Product Support to remote in to and perform the update. Have the controller sent back to the factory to be updated and returned to site. Both options will require replacing the controller with temporary stock while the upgrade is being performed.

Issue A temperature input on one device is referenced in an external binding, e.g. a consumer value, in another (BACnet) device. The value on the consumer side is incorrect and seems to have been converted from Fahrenheit to Celsius although the units all show Fahrenheit. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (Premium) Building Operation Enterprise Server / Enterprise Central BACnet Device(s) supporting external binding (e.g. MP-X or IP-IO) Cause The probable cause is that the value of the temperature input is not configured to a specific unit. This means that the unit is decided by the electrical type of the thermistor. In most cases this is Temperature °C, which means that the values are stored in °C, and this is the value being transferred in the consumer binding. If the measurement system in Workstation is set to United States Customary Units (US), the input value will be displayed in Fahrenheit (°F) and one might think that the unit of the temperature input value is also configured to Fahrenheit, when in reality it is in Celsius. In this situation the value on the consumer side is in Celsius as it has no information about units. Furthermore, if the consumer value unit is configured to Fahrenheit, then we have the situation shown in the screenshot above. Resolution Start by changing measurement system in Workstation to As configured in object. (Refer to the Webhelp for more information about how to do this.) By doing this the values will be displayed unconverted. It is now clear that the temperature input in reality is in Celsius. The next step is to configure the input unit to Fahrenheit. Open up Properties for the Temperature input and click the gear wheel next to Value to configure. Check the box to the left of Unit and click the button with the three dots to the right. Select °F and click Select Click OK to confirm the changes in both open windows. Both the temperature input and the consumer value will now be displaying the correct value in Fahrenheit.